Miscellaneous limitations
The limitations listed in this section are specific to the miscellaneous application.
- OneCli may report failure when booting to setup a server if the target server's host OS is RHEL or SLES.
When the OS of the target system host is RHEL or SLES, the following message might be displayed after running OneCli ospower boottosetup --bmc USERID:PASSW0RD@10.240.X.X:
Failed to enter BIOS setup, waiting OS system status timeout.In this case, do the following:- For Red Hat® Enterprise Linux (RHEL) v7 and later versions:
Manually configure the operating system to change the power status to power off. For instructions, see https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/desktop_migration_and_administration_guide/setting-behavior-of-particular-buttons
Run the command OneCli ospower boottosetup --bmc USERID:PASSW0RD@10.240.X.X again.
- For SUSE Linux Enterprise Server (SLES):
Manually power off the server through the local SLES interface, enter the root password on the SLES session, select Remember authentication, or check the security policy to confirm whether the mandatory authentication can be disabled.
Run the command OneCli ospower boottosetup --bmc USERID:PASSW0RD@10.240.X.X again.
- OneCLI could not run the raid clear command for the ThinkServer systems.
- When running the raid clear command in the ThinkServer systems and error message
The request failed due to an internal service error. The service is still operational.
is displayed, do one of the following:If the target volume is not deleted, run the raid clear command again to delete the target volume.
If the target volume is deleted, ignore this error message.
- Long time might be consumed in physical drive secure erase (speed: about 0.38GB/min) for the ThinkSystem servers installed with 4350/5350/9350 HBA/RAID adapters.
- OneCLI could not perform secure erase on SATA SSD connected to Marvell RAID controllers.
There is an internal time-out of 9 seconds in the Marvell RAID firmware, and the SSD might not respond to the command in time. Then, the Marvell RAID firmware will reset the SSD, the secure erase will fail, the SSD will be locked and could not work. In this case, run the following command to unlock SSD:
hdparm --user-master u --security-unlock user123 %diskName%
It is also recommended to do the following:For 7mm SATA SSDs, connect to Broadcom RAID controllers to perform secure erase.
For M.2 SATA SSDs, connect to Enablement Kit without Marvell RAID firmware (for example, ThinkSystem M.2 SATA/NVMe 2-Bay Enablement Kit) to perform secure erase.