OneCLI features supported on the ThinkSystem-Hyperscale servers
This section provides the supported OneCLI features and specific limitations for the ThinkSystem-Hyperscale servers.
Supported features
In-band and out-of-band features:
| Features | Reference |
|---|---|
| Collect FFDC. | ffdc command |
| Collect inventory. | Inventory |
| Collect service data from BMC. | servicedata command |
| Collect system health status. | syshealth command |
| Configure BIOS/BMC settings. | Configuration |
| Encrypt data. | encrypt command |
| Manage BMC password. | bmcpassword command |
| Manage BMC reboot. | rebootbmc command |
| Manage the LED status of hard disk drive. | hddlocate command. |
| Manage OS power. | ospower command |
| Manage system logs. | logmgr commands |
| Manage virtual media. | vm commands |
| Update the firmware. | Update |
In-band features:
| Features | Reference |
|---|---|
| Manage USB LAN. | usblan command |
Multiple systems management features:
| Features | Reference |
|---|---|
| Collect FFDC logs from multiple BMC. | multiffdc command |
| List, mount, or unmount virtual media on multiple BMC. | multivm commands |
| Manage firmware update on multiple BMC. | multiflash command |
| Manage password on multiple BMC. | multibmcpassword command. |
| Manage service data on multiple BMC. | multiservicedata command. |
| Obtain the BMC FFDC logs from multiple servers. | multiffdc command |
| Remotely collect system health information for multiple systems. | multisyshealth command |
| Remotely show or change the system configuration for multiple servers. | Multiple configuration |
| Turn on, turn off, and restart the server, and obtain the server power state. | multiospower commands |
Limitations
- For the ThinkSystem HS350X V3 (7DBM) server, RAID volume information is not included in OneCLI inventory results because BMC Redfish doesn’t have RAID volume data.
- Workaround: Users can retrieve the Broadcom RAID adapter information in OS through Storcli.
- When using OneCLI to update BMC firmware in in-band mode, the progress bar might remain at 99% for a long time and finally return failure. This is because OneCLI polls the flash status every 5 seconds by default, but BMC might restart before OneCLI can obtain the BMC completion status. Actually the BMC firmware is updated successfully, but user might receive a failure message.
- Workaround: Set the RESTFLASH_QUERY_WAIT_TIME value as 1 in the global.config file, then OneCLI can get the correct completion status and return successfully.
- The servicedata command only supports to get the latest failure screen, but not retrieve health report information.
- On HS350X V3 server, the RAID storage information in OneCLI syshealth/inventory function does not work properly due to the BMC Redfish interface doesn’t support it. The limitation includes:
The Disk/Storage Controller information is misclassified.
The information about the volumes related to the disks and the firmware is shown repeatedly.
The RAID controller information is lost.
The disks/volumes under the RAID controller cannot be associated with the RAID controller.
- OneCLI does not support the default syshealth command without the --device or -d option because there is no activelog event. In this case, the general health information will not be displayed.
- For out-of-band firmware update, OneCLI only supports the BMC/BIOS/FPGA/Backplane firmware, but not the I/O adapters firmware.
- The BIOS and FRU configurations will be lost after the BMC loaddefault.
- Workaround: Restart the OS before running other OneCLI commands.
- The version of Backup UEFI Image will be displayed as N/A after the BMC FW is updated because BMC cannot retrieve the backup UEFI image information. It will not impact the UEFI function.
- Workaround: Update the backup UEFI image again.
- OneCLI does not support to set a single setting for LDAP-related settings.
- Workaround: Use the batch command to configure all the LDAP-related settings.
- If users update the BMC firmware without preserving BMC configuration, the configurations will not be saved.
- Workaround: Restart the system to make the configuration and operations take effect, and then run BMC firmware update without preserving the configuration.
Give documentation feedback