Managing device firmware and drivers. Dell EMC OpenManage Enterprise

Add to My manuals
215 Pages

advertisement

Managing device firmware and drivers. Dell EMC OpenManage Enterprise | Manualzz

8

Managing device firmware and drivers

Use the firmware and driver catalog available on Dell.com to create firmware and driver baseline, compare if devices comply to the baseline and generate a compliance report, and then fix compliance issues. Use the Configuration > Firmware/Driver

Compliance screen to manage the firmware of all the managed devices that are discovered out-of-band using iDRAC. You can also update drivers of the 64-bit Windows-based servers that are discovered and managed in-band using the SSH protocol.

NOTE:

● Ensure you have the necessary user privileges as described in

Role and scope-based access

.

● To perform Windows driver update, ensure that the Windows servers are discovered in-band using the supported protocol. To update both drivers and firmware, you must additionally discover the servers out-of-band using iDRAC.

● The device firmware or driver version, if earlier than baseline version, is not automatically updated and the user must initiate the update.

● It is recommended that the firmware and driver updation is done during the maintenance windows to prevent the devices or environment going offline during business hours.

● To manage a device's firmware and/or driver, the Onboarding status of the system should be either 'Managed' or

'Managed with Alerts'. See

Onboarding devices

● Currently, the catalog contains drivers for only the 64-bit Windows-based devices.

By using the firmware/driver feature, you can:

Use a firmware and driver catalog from Dell.com either directly or after saving it on a network path. See Add a catalog by using Dell.com

or

Creating a firmware catalog by using local network

.

● Create a firmware and driver baseline by using the available catalogs. These baselines serve as benchmarks to compare the firmware and driver version on the devices against the version in the catalog. See

Creating the firmware baseline .

● Run a compliance report to check if the devices associated with the baseline comply to the baseline firmware and driver versions. See

Checking firmware compliance

. The COMPLIANCE column displays:

○ OK — if the target device's firmware and/or driver version is same as the baseline.

○ Upgrade — if the target device's has one or more versions earlier than the baseline's firmware or driver version. See

Updating the device firmware version

○ Critical — If the component's current firmware/driver version is lower than the baseline version and if the importance assigned is either Recommended or Urgent.

○ Warning

Optional.

— If the component's current version is lower than the baseline version and the importance assigned is

○ Downgrade — if the device firmware and/or driver is later than the baseline version.

○ Export the compliance report for statistical and analytical purposes.

○ Update device firmware and/or driver version by using the baseline. See

Update the device firmware and drivers by using baselines .

NOTE:

● When a firmware/driver baseline with many devices is checked for compliance, the warning alerts CDEV9000 on the

Alerts page is logged for only one random non-compliant device from that baseline.

● The firmware or driver compliance status of network switches, modular IOAs, and Dell storage devices is displayed as

Unknown as these are not updatable using the Dell catalog. It is recommended to perform individual firmware or driver updates for these devices using their respective individual Update package. To perform individual firmware or driver updates, select a device on the All Devices page, and click View Details > Firmware/Drivers and select the individual package option. For more information about the list of unsupported devices, refer

Devices with unknown compliance status

.

You can update firmware version of a device also on the:

● All Devices page. See

Update the device firmware and drivers

.

Managing device firmware and drivers 111

● Device Details page. In the Devices List, click the device name or IP address to view device configuration data, and then edit.

See

View and configure individual devices .

NOTE: Updating a device using the Individual Package workflow only supports executable (EXE) based Dell Update

Packages. When updating an FX2 CMC, the executable DUP must be installed via one of the sleds in the chassis.

The summary of all the baselines is displayed in the working pane, and the compliance of a selected baseline is displayed in the right pane by using a Donut chart. A Donut chart and list of items in the baseline changes based on the baseline you select from the Baseline list. See

Donut chart .

Topics:

Manage firmware and driver catalogs

Create a baseline

Edit a baseline

Delete a baseline

Check the compliance of firmware and drivers

View the baseline compliance report

Update the device firmware and drivers

Manage firmware and driver catalogs

Use firmware and driver catalogs (update packages) to create baseline and check baseline compliance to reduce the overall device management process time.

Catalogs are bundles of firmware and drivers based on device types. All the available catalogs (update packages) are validated and posted to Dell.com. You can use the catalog directly from the online repository or it can be downloaded to a network share.

Using these catalogs, you can create firmware/driver baselines for the discovered devices and check their compliance. This reduces the extra effort of administrators and device managers and also reduces the overall updating and maintenance time.

Administrator users can view and access all the catalogs in OpenManage Enteprise, however, device managers can only view and manage catalogs that they created and own. See,

Role and scope-based access

.

For field definitions on the Catalog Management page, see Catalog Management field definitions

. The sources of catalog that you can currently access are:

NOTE:

● Firmware catalog management using Dell.com or a local network path is limited to only the Enterprise Server Catalog.

● OpenManage Enterprise supports UI internationalization, however, it is recommended that the functional content such as the file names and catalog content are entered only in English.

● Catalogs with base location pointing to 'Downloads.dell.com' can be used without the Dell Update Packages (DUPs) while importing catalog OpenManage Enterprise from a network share. During the firmware upgrade process, the DUPs will be downloaded directly from https://downloads.dell.com.

● Latest component versions on Dell.com

: Lists the latest firmware and driver (64-bit Windows) versions of devices. For example, iDRAC, BIOS, PSU, and HDDs that are rigorously tested and released and posted to Dell.com. See

Creating a firmware catalog by using Dell.com

.

● Network Path : Location where the firmware and driver catalogs are downloaded by the Dell Repository Manager (DRM) and saved on a network share. See

Creating a firmware catalog by using local network

.

Add a catalog by using Dell.com

Based on your requirements, create a firmware catalog that can pick the latest components versions from Dell.com.

Prerequisites

● To perform any tasks on OpenManage Enterprise, you must have the necessary user privileges. See

Role and scope-based access .

● Ensure to enable CIFS (>v1) in the SMB Settings before you begin any firmware tasks which need communication with

any chassis or the PowerEdge YX2X and YX3X servers that have iDRAC version 2.50.50.50 and earlier. See Manage console settings

and

PowerEdge server naming conventions

for more information.

112 Managing device firmware and drivers

● OpenManage Enterprise supports UI internationalization, however, it is recommended that the functional content such as the file names and catalog content are entered only in English.

Steps

1. On the Catalog Management page, click Add .

2. In the Add Update Catalog dialog box: a. In the Name box, enter a firmware catalog name.

b. For the Catalog Source , select the option Latest component versions on Dell.com

.

c. In the Update Catalog box, select either Manually or Automatically .

d. If Automatically is selected in the Update Catalog box, Update Frequency need to be selected as either Daily or

Weekly followed by time in the 12-hour format with AM/PM.

NOTE: To get the latest firmware information in the baseline, click on Check for Update on the relevant catalog.

Optionally, if your catalog is updated on schedule, the firmware information will be updated with the scheduled catalog update.

e. Click Finish .

The Finish button appears only after you have entered all the fields in the dialog box

A new firmware catalog is created and listed in the Catalog table on the Catalog Management page.

3. To go back to the Firmware/Driver Compliance page, click Return to Firmware/Driver Compliance .

Add a catalog to the local network

Create a firmware catalog on a local network. Currently, CIFS, NFS, HTTP, and HTTPS protocols are supported.

Prerequisites

● For local network shares using Windows 2019 or later, the catalog must be generated using DRM version 3.3.2 and later.

● OpenManage Enterprise supports UI internationalization, however, it is recommended that the functional content such as the file names and catalog content are entered only in English.

About this task

Catalog containing the firmware and drivers (64-bit Windows) can be downloaded using the Dell Repository Manager (DRM) and saved on a network share.

Steps

1. On the Catalog Management page, click Add .

2. In the Add Update Catalog dialog box: a. In the Name box, enter a catalog name.

b. For the Catalog Source, select the option Network Path .

The Share Type drop-down menu is displayed.

c. Select one of the following:

NOTE: Ensure to enable SMBv1 in the SMB Settings before you begin any firmware tasks which need communication with any chassis or the PowerEdge YX2X and YX3X servers that have iDRAC version 2.50.50.50

and earlier. See Manage console settings

and

PowerEdge server naming conventions

for more information.

● NFS i.

In the Share Address box, enter the IP address of the system where the firmware catalog is stored on the network.

ii. In the Catalog File Path box, enter the full file path of the catalog file location. Example path: nfsshare\catalog.xml

● CIFS i.

In the Share Address box, enter the IP address of the system where the firmware catalog is stored on the network.

ii. In the Catalog File Path box, enter the full file path of the catalog file location. Example path:

Firmware\m630sa\catalog.xml

iii. In the Domain box, enter the domain name of the device.

Managing device firmware and drivers 113

iv. In the User Name box, enter the user name of the device where the catalog is stored.

v. In the Password box, enter the password of the device to access the share. Type the username and password of the shared folder where the catalog.xml file is stored.

● HTTP i.

In the Share Address box, enter the IP address of the system where the firmware catalog is stored on the network.

ii. In the Catalog File Path box, enter the full file path of the catalog file location. Example path: compute/ catalog.xml

.

● HTTPS i.

In the Share Address box, enter the IP address of the system where the firmware catalog is stored on the network.

ii. In the Catalog File Path box, enter the full file path of the catalog file location. Example path: compute/ catalog.xml

.

iii. In the User Name box, enter the user name of the device where the catalog is stored.

iv. In the Password box, enter the password of the device where the catalog is stored.

v. Select the Certificate Check check box.

The authenticity of the device where the catalog file is stored is validated and a Security Certificate is generated and displayed in the Certificate Information dialog box.

d. After you have entered the Share Address and the Catalog File Path , the Test now link is displayed. To validate a connection to the catalog click Test now . If the connection to the catalog is established, a Connection Successful message is displayed. If connection to the share address or the catalog file path is not established, Connection to path failed error message is displayed. This is an optional step.

e. In the Update Catalog box, select either Manually or Automatically .

If the Update Catalog is selected as Automatically , select either Daily or Weekly as the update frequency and enter time in the 12-hour format.

NOTE: To get the latest firmware information in the baseline, click on Check for Update on the relevant catalog.

Optionally, if your catalog is updated on schedule, the firmware information will be updated with the scheduled catalog update.

3. Click Finish . The Finish button appears only after you have entered all the fields in the dialog box.

A new firmware catalog is created and listed in the Catalog table on the Catalog Management page.

4. To go back to the Firmware/Driver Compliance page, click Return to Firmware/Driver Compliance .

Related tasks

Delete a catalog

SSL Certificate Information

If you create a firmware catalog on the Create Baseline page, you can view the SSL certificate information when you download catalog files from the support site or DRM.

The catalog files for firmware and driver updates can be downloaded from the Dell support site, Dell Repository Manager

(Repository Manager), or a website within your organization network.

If you choose to download the catalog file from the website within your organization network, you can accept or decline the SSL certificate. You can view details of the SSL certificate in the Certificate Information window. The information consists of the validity period, issuing authority and the name of the entity to which the certificate is issued.

NOTE: The Certificate Information window is displayed only if you create the catalog from the Create Baseline wizard.

The following actions are available:

Accept

Cancel

Accepts the SSL certificate and allows you to access the website.

Closes the Certificate Information window without accepting the SSL certificate.

114 Managing device firmware and drivers

Update a catalog

The existing firmware and driver catalogs can be updated from the Dell.com site (base location).

Steps

1. On the Catalog Management page, select a catalog.

2. Click the Check for update button that is located in the right pane of the Catalog Management page.

3. Click YES.

If the selected catalog was an online catalog, it is replaced by the most up-to-date version that is maintained at the Dell.com

site. For the local network catalogs, all the latest firmware and drivers available in the base location are considered for computing the baseline compliance.

Edit a catalog

Edit the catalog properties such as share location folder path and catalog file path.

About this task

OpenManage Enterprise supports UI internationalization, however, it is recommended that the functional content such as the file names and catalog content are entered only in English.

Steps

1. On the Catalog Management page, select a catalog.

The catalog details are displayed in the <catalog name> right pane.

2. Click Edit in the right pane.

3. In the Edit Update Catalog wizard, edit the properties.

The properties that you cannot edit are grayed-out. For field definitions, see Add a catalog by using Dell.com

and

Add a catalog to the local network .

4. Enter the Share Address and the Catalog File Path , the Test now link is displayed. To validate a connection to the catalog click Test now . If the connection to the catalog is established, a Connection Successful message is displayed.

If connection to the share address or the catalog file path is not established, Connection to path failed error message is displayed. This is an optional step.

5. In the Update Catalog box, select either Manually or Automatically .

If the Update Catalog is selected as Automatically , select either Daily or Weekly as the update frequency and enter time in the 12-hour format.

6. Click Finish .

A job is created and run immediately. The job status is indicated in the REPOSITORY LOCATION column of the Catalog

Management page.

Delete a catalog

Delete catalogs that are not associated with a baseline.

Steps

1. On the Catalog Management page, select the catalogs, and then click Delete .

The catalogs are deleted from the list.

2. To go back to the Firmware/Driver Compliance page, click Return to Firmware/Driver Compliance .

NOTE: Catalogs cannot be deleted if linked to a baseline.

Related information

Add a catalog to the local network

Managing device firmware and drivers 115

Create a baseline

A baseline is a set of devices or group of devices that are associated with a firmware/driver catalog. A baseline is created for compliance evaluation of the firmware and drivers for the devices in that baseline against the versions specified in the catalog.

Prerequisites

● To perform any tasks on OpenManage Enterprise, you must have necessary role-based user privileges and scope-based operational access to the devices. See

Role and scope-based access

.

● Device manager user can only view and manage the firmware/driver baselines that the respective device manager created and owns. Also, while creating baselines, the target groups or devices (capable of firmware update) that are only in the device manager's scope are displayed.

● A non-compliant device with a firmware and/or driver version earlier than the catalog version, is not automatically updated.

You must update the firmware version. It is recommended to update device firmware during maintenance windows to prevent the devices or environment going offline during business hours.

Steps

1. Under Firmware , click Create Baseline .

2. In the Create Update Baseline dialog box: a. In the Baseline Information section: i.

From the Catalog drop-down menu, select a catalog.

ii. To add a catalog to this list, click Add . See

Manage firmware and driver catalogs

.

iii. In the Baseline Name box, enter a name for the baseline, and then enter the baseline description.

iv. (Optional) Select the Select only components with no reboot required check box to create a firmware/driver baseline that consists of only the components of the target devices that don't require a reboot of the target devices.

v. Click Next .

b. In the Target section:

● To select the target device(s): i.

Select Select Devices , and then click the Select Devices button.

ii. In the Select Devices dialog box, all the devices monitored by OpenManage Enterprise, IOMs, and devices under static or query group are displayed in respective groups.

iii. In the left pane, click the category name. Devices in that category are displayed in the working pane.

iv. Select the check box corresponding to the device(s). The selected devices are listed under the Selected Devices tab.

● To select the target device group(s): i.

Select Select Groups , and then click the Select Groups button.

ii. In the Select Groups dialog box, all the devices monitored by OpenManage Enterprise, IOMs, and devices under static or query group are displayed in respective categories.

iii. In the left pane, click the category name. Devices in that category are displayed in the working pane.

iv. Select the check box corresponding to the group(s). The selected groups are listed under the Selected Groups tab.

3. Click Finish .

A message is displayed that a job is created for creating the baseline.

In the Baseline table, data about the device and baseline job is displayed. For field definitions, see

Firmware baseline field definitions

.

Edit a baseline

The baselines on the Configurations > Firmware/Driver Compliance page can be edited as follows:

Steps

1. Select a baseline, and then click Edit in the right pane.

2. Modify data as described in Creating the firmware baseline

.

The updated information is displayed in the Baseline list.

3. To go back to the Firmware/Driver Compliance page, click Return to Firmware/Driver Compliance .

116 Managing device firmware and drivers

Delete a baseline

The baselines on the Configurations > Firmware/Driver Compliance page can be deleted as follows:

Under Firmware , a list of available firmware baselines is displayed. Select the check box corresponding to the baseline and click

Delete . The firmware baseline is deleted and removed from the baseline list.

Check the compliance of firmware and drivers

On the Configuration > Firmware/Driver Compliance page, you can check for the compliance of the firmware and drivers of baseline devices against the associated catalog, view the report, and update the firmware and drivers of non-compliant devices.

Prerequisites

● To perform any tasks on OpenManage Enterprise, you must have necessary role-based user privileges and scope-based operational access to the devices. See

Role and scope-based access

.

● The firmware and drivers (64-bit Windows) for the non-compliant devices in the baseline are not automatically updated and must be updated by the user. It is recommended to update device firmware and drivers during the maintenance windows to prevent the devices or environment going offline during business hours.

● To collect the inventory information, the Inventory Collector and Dell System Update must be available on the Windows server. If these components are not available on the server, then initiate an inventory job and select Collect driver inventory . The discovery job also collects driver inventory information, but only the inventory job installs the necessary components on the server. To collect the driver inventory information, create or edit an inventory job and select the Collect driver inventory check box. For more information, see

Create an inventory job

and

Edit an inventory schedule job .

Steps

1. Select the check box corresponding to the baseline(s), and click Check Compliance .

The baseline compliance job is run.

NOTE: If the devices are not associated to a catalog, the compliance is not verified. A job is created only for the devices

that are associated and listed in the Compliance table. To associate a device to a catalog, see Create a baseline

.

In the Baseline table, data about the device and baseline job is displayed. For field definitions, see

Firmware baseline field definitions

.

2. To view the Compliance report and to upgrade the firmware and driver version of device(s), click View Report in the right pane.

See

View the baseline compliance report

.

NOTE: Rollback is not supported for drivers.

View the baseline compliance report

View if a firmware baseline complies to the catalog it is associated with, and then make it compliant if necessary.

About this task

On the Configuration > Firmware/Driver Compliance page, the compliance status of the baselines is indicated. A Donut chart provides a summary of baselines' compliance to their respective catalogs. When more than one device is associated with a baseline, the status of the least compliant device to the baseline is indicated as the compliance level of that baseline. For example, the compliance level of a baseline with only one device with compliance as 'critical, is indicated as 'critical' most of the devices are compliant.

even if

You can view the firmware and driver compliance of individual devices associated with a baseline and choose to either upgrade or downgrade the firmware and/or driver version on that device. To view the baseline compliance report:

● Select the check box corresponding to the baseline and click View Report in the right pane.

On the Compliance Report page the list of devices associated with the baseline and their compliance level is displayed. By default, the devices in Critical and Warning statuses are displayed.

Managing device firmware and drivers 117

NOTE: If each device has its own status, the highest severity status is considered as the status of the group. For more information about Rollup Health status, see the Managing The Rollup Health Status By Using iDRAC On The Dell 14th

Generation And Later Poweredge Servers white paper on the Dell TechCenter.

● COMPLIANCE : Indicates the compliance level of a device to the baseline. For more information about symbols used for

device firmware/driver compliance levels, see Managing device firmware and drivers

.

● TYPE : Type of device for which the compliance report is generated.

● DEVICE NAME/COMPONENTS : By default, the Service Tag of the device is displayed.

1. To view information about components in the device, click the > symbol.

A list of components and their compliance to the catalog is displayed.

NOTE: For all the devices (except the MX7000 chassis) which are fully in compliance with the associate firmware baseline, the > symbol is not displayed.

2. Select one or more check boxes corresponding to the devices whose firmware compliance status is 'Critical' and requires an update.

3. Click Make Compliant

. See Update the device firmware version by using the baseline compliance report

.

● SERVICE TAG : Click to view complete information about the device on the <device name> page. For more information about tasks you can complete on this page, see

View and configure individual devices

.

● REBOOT REQ : Indicates if the device must be restarted after updating the firmware.

● Info : Symbol corresponding to every device component is linked to the support site page from where the firmware/ driver can be updated. Click to open the corresponding Driver Details page on the support site.

● CURRENT VERSION : Indicates the current firmware version of the device.

● BASELINE VERSION : Indicates the corresponding firmware and driver version of the device available in the associated catalog.

● To export the compliance report to an Excel file, select the check boxes corresponding to the device, and then select from

Export .

● To go back to the Firmware page, click Return to Firmware .

● To sort data based on a column, click the column title.

● To search for a device in the table, click Advanced Filters , and select or enter data in the filter boxes. See Advanced Filters in

The OpenManage Enterprise GUI .

Update the device firmware and drivers

After you run a firmware or driver compliance report, if the firmware or driver version on the device is earlier than the version on the catalog, the Compliance Report page indicates the device firmware or driver status as Upgrade ( or ).

Prerequisites

● To perform any tasks on OpenManage Enterprise, you must have necessary role-based user privileges and scope-based operational access to the devices. See

Role and scope-based access

.

● You must create an inbound firewall rule to allow communication with port 22.

● If HTTP and HTTPS shares were configured using the proxy settings, ensure that these local URLs are included in the proxy-exception list before initiating any update tasks.

● Only one update task can be initiated on the target machine at a given time.

About this task

The firmware and driver version of the associated baseline devices is not automatically updated, hence, the user must initiate the update. It is recommended to update the device firmware and/or driver during the maintenance windows to prevent the devices or environment going offline during business hours.

Device managers can run firmware/driver update only on the devices which are in their scope.

NOTE: Inventory collection and the firmware update on chassis storage sleds is not supported in OpenManage Enterprise if they are managed via chassis device management.

● The Reset iDRAC function is not supported for the devices under an MCM chassis that are in a 'Proxied' onboarding state and for updating only the drivers of the devices. For more information about onboarding states, see

Onboarding devices

.

118 Managing device firmware and drivers

● The firmware or driver compliance status of network switches, modular IOAs, and Dell storage devices is displayed as

Unknown as these are not updatable using the Dell catalog. It is recommended to perform individual firmware or driver updates for these devices using their respective individual Update package. To perform individual firmware or driver updates, select a device on the All Devices page, and click View Details > Firmware/Drivers and select the individual package option. For more information about the list of unsupported devices, refer

Devices with unknown compliance status

● When compliant devices (that is, devices marked with a green check) are selected for a Make Compliant job that contains associated components those updates will be re-applied to the devices. If any of those components require a restart the devices will be restarted to complete the compliance operation.

● After submitting this job for execution the console will first try and verify the service tag of the intended target to ensure the operation is performed on the correct system. If the verification fails the job will complete with errors, and the task execution history detail will show the following:

Running

Verifying if the device Service Tag is valid.

The device Service Tag could not be verified.

Task Failed. Completed With Errors.

Please check the system to ensure the IP address has not changed since the last discovery was completed. Remediate by discovering the system with the updated IP address, and retrying the operation.

If the multi-chassis management (MCM) group is managed using OpenManage Enterprise-Modular versions lower than 1.30.00, you must consider the following before updating the firmware and/or drivers of MX7000 chassis and sleds :

● Chassis and sled firmware updates must be undertaken separately.

● The lead chassis must be updated separately as the final step after updating all the member chassis.

● Firmware can be updated for only up to 9 member chassis at a time.

● Firmware update is supported on a maximum of 43 sleds at a time irrespective of onboarding state (Managed or Proxied).

The driver updates are available only on devices discovered as 64-bit Windows servers. Before updating the drivers, do the following:

● Be aware that the rollback of the driver updates is not supported.

● To perform Windows driver update, ensure that the Windows servers are discovered in-band using the supported OpenSSH protocol. To update both drivers and firmware, you must additionally discover the servers' out-of-band using iDRAC.

● Driver updates on third party SSH hosted on Windows, such as the CygwinSSH, are not supported.

● To collect the inventory information, the Inventory Collector and Dell System Update must be available on the Windows server. If these components are not available on the server, then initiate an inventory job and select Collect driver inventory . The discovery job also collects driver inventory information, but only the inventory job installs the necessary components on the server. To collect the driver inventory information, create or edit an inventory job and select the Collect driver inventory check box. For more information, see

Create an inventory job

and

Edit an inventory schedule job .

Steps

1. On the Configuration > Firmware/Driver Compliance page, select the check box corresponding to the baseline to which the device is attached, and then click View Report in the right pane.

On the Compliance Report page, the list of devices associated with the baseline and their compliance level is displayed. For field descriptions, see

View the baseline compliance report .

2. Select the check box corresponding to the device(s) whose firmware or driver must be updated. You can select more than one device with similar properties.

3. Click Make Compliant .

4. In the Devices/Components Confirmation > Options section:

● Select Update Now to apply the firmware/driver updates immediately.

● Select Schedule Later to specify a date and time when the firmware and/or driver version must be updated. This mode is recommended if you do not want to disturb your current tasks.

● Under Server Options, choose Reboot server immediately to reboot the server(s) immediately after the firmware/ driver update, and select one of the following options from the dropdown menu:

○ Graceful reboot without forced shutdown

○ Graceful reboot with forced shutdown

○ PowerCycle for a hard reset of the device

Or, select Stage for next server reboot to trigger the firmware/driver update when the next server reboot happens.

Managing device firmware and drivers 119

NOTE: If the firmware update/driver jobs are created with the 'Stage for next server reboot' option, to collect the latest inventory, wait till the firmware update completes on the target device (That is, after the scheduled reboot).

After the update is complete and the target device is in a steady state, manually run an

Inventory Job to collect the

latest device software details. Optionally, you can wait for the system scheduled inventory job to run. Click on Check

Compliance ( Configuration > Firmware/Driver Compliance ) upon completion of the Inventory job. This action will refresh the Baseline Software Components with the most recent component version's provided by the target device.

● Select Reset iDRAC to initiate a reboot of the iDRAC before the update job is initiated.

NOTE: This function is not supported for updating the drivers.

● Select Clear job queue to delete all jobs (scheduled, completed, and failed) on the target device, before the update job is initiated.

NOTE: This function is not supported for updating the drivers.

5. Click Finish to proceed or click Cancel to discard the previous selections.

Results

A firmware/driver update job is created to update the device's firmware and/or driver. You can view the status of the job on the

Monitor > Jobs screen.

120 Managing device firmware and drivers

advertisement

Related manuals

Download PDF

advertisement

Table of contents