Firmware Compliance Reports enables you to maintain consistent firmware versions across the datacenter. The Firmware Report feature compares the firmware images specified in a firmware profile to the firmware images installed on hardware assets.
The report indicates whether the firmware on the asset complies with the profile's specifications. You can update the firmware on any non-compliant asset by clicking the Make Targets Compliant button in the Interactive report.
To create a Firmware Report, perform the following steps:
Select Reports in the Navigation pane.
Select Firmware Reports.
Select Create Firmware Report from the Actions pane. The Create Firmware Report Wizard is displayed.
Define the report parameters, including:
Report Name: The name of the report.
Description: A description of the report.
Schedule: If you do not plan to create this report routinely, deselect the Create Schedule option.
Output Format: Select the output format of the report result. CSV and PDF formats are available.
Profile: Select the firmware profile for a service processor or for a storage component, such as a RAID controller, expander, or disk.
Click Next to display the Select Targets.
Select the targets you want to test against the profile. Select the asset from the Available Items hierarchy and click Add to Target List. When you have selected all the targets, click Next to display the Schedule page.
Select a desired schedule to run and generate the report.
Click Next to display the Summary.
Review the summary and click Run and Close to create the report job.
The report job starts at the time you specified and compares the values in the profile to the existing values on the targets you selected. The report displays whether a target asset is compliant, not compliant, or not applicable:
A compliant asset has the firmware images specified in the profile.
A non-compliant asset does not have the same firmware images as specified in the profile.
A non-applicable asset indicates that a firmware image in the profile does not match the model of service processor in the asset. This condition can occur when either the profile does not recognize the model that the service processor is reporting or the profile includes firmware images that are not designed for the service processor.
Compare the model of the service processor displayed in the asset's Summary tab with the model of the service processor included in the profile. If they are different, add the name in the profile to the asset's data.
When the firmware profile was created, only images that matched the service processor could be included. However, if the service processor did not report all the firmware types it supported, an image that did not match the service processor could have been included in the profile. To update the software with all the service processor's supported firmware types, use the Refresh action to update the information about the service processor. When the job is completed, view the service processor's Summary tab to see all firmware types.
Repeat the procedure to create a firmware report.