CAUTION:
When you reset iLO to the factory default settings, all iLO settings are erased, including user
data, license data, configuration settings, and logs. If the server has a factory installed license
key, the license key is retained.
Events related to the reset are not logged to the iLO Event Log and Integrated Management Log
because this step clears all the data in the logs.
2.
Reboot the server operating system.
During the reset to the factory default settings, SMBIOS records are cleared. Memory and network
information will not be displayed in the iLO web interface until the server OS reboot is complete.
Disabling SuiteB mode
Procedure
1.
To disable SuiteB mode do one of the following:
• To disable SuiteB and continue using the FIPS security state, change the security state from
SuiteB
to
FIPS
.
• To disable SuiteB and FIPS, set iLO to the factory default settings.
You can perform this task by using RIBCL scripts, the iLO RESTful API, or the iLO 5 Configuration
Utility.
CAUTION:
When you reset iLO to the factory default settings, all iLO settings are erased, including user
data, license data, configuration settings, and logs. If the server has a factory installed license
key, the license key is retained.
Events related to the reset are not logged to the iLO Event Log and Integrated Management
Log because this step clears all the data in the logs.
2.
If you reset iLO to the factory default settings, reboot the server operating system.
During the reset to the factory default settings, SMBIOS records are cleared. Memory and network
information will not be displayed in the iLO web interface until the server OS reboot is complete.
iLO security states
Production (default)
When set to this security state:
• iLO uses the factory default encryption settings.
• The system maintenance switch setting to bypass iLO security (sometimes called the iLO Security
Override switch) disables the password requirement for logging in to iLO.
HighSecurity
When iLO is set to this security state:
Disabling SuiteB mode
261
