Now we need to perform the firmware, BIOS, and iDRAC validation on the HLH server.
- If you haven’t done so already on the OME VM, browse back to C:\ComplianceTools and double-click on the Load Compliance Tools shortcut, which brings up the Select Load Compliance Tools PowerShell window.
- Perform the HLH firmware compliance checks:
“Invoke-CheckFirmwareBaseline –IPAddresses <HLH iDRAC IP address> –iDRACCredential (Get-Credential) -oemExtensionPath “DUPS” –ManagementServerAddress < OME VM OS IP > –ManagementServerCredential (Get-Credential)”
Figure 33. HLH firmware compliance
Note: If remediation is necessary, follow the same manual process that was followed with the scale unit nodes. That is, clear the iDRAC job queue, upload the HLH firmware updates one at a time to the iDRAC in the order they were listed in the Catalog.xml file, and apply.
- Perform HLH server BIOS compliance checks:
“Invoke-CheckBIOSSettings –IPAddress <HLH iDRAC IP> –iDRACCredential (Get-Credential)”
Figure 34. Performing HLH server BIOS compliance checks
Note: If any of the BIOS settings come back with required changes to be applied, simply run the same command with the “-remediate” parameter. If required, the HLH will automatically reboot.
Note: The scripts will error with a message if the node being worked on is not in a powered-down state and the “-remediate” parameter is used.
“Invoke-CheckBIOSSettings –IPAddresses <single IP address of current scale unit node’s iDRAC> –iDRACCredential (Get-Credential) -remediate”
- Perform HLH server iDRAC compliance checks:
“Invoke-CheckiDRACSettings –IPAddress <HLH iDRAC IP> –iDRACCredential (Get-Credential)”
Figure 35. Performing HLH server iDRAC compliance checks
Note: The iDRAC settings function automatically validates and remediates since a change to the iDRAC settings does not reboot the server.
Return to Patch and update overview for the order of operations.