OneCLI common return codes
This section describes OneCLI common return codes.
| Return codes | Description |
|---|---|
| 0 | Success. |
| 1 | Generic failure. |
| 3 | Invalid application. |
| 4 | Invalid command. |
| 5 | Invalid parameter. |
| 6 | File does not exist. |
| 7 | Invalid file. |
| 8 | Failed to create directory. |
| 9 | Failed to open file. |
| 10 | Failed to read file. |
| 11 | Failed to write file. |
| 12 | Authentication failed. |
| 13 | Connection failed. |
| 14 | Ping failed. |
| 15 | Upload failed. |
| 16 | Download failed. |
| 17 | Internal error. |
| 18 | Time-out. |
| 19 | Failed to get BMC account through KCS. |
| 20 | Users are running on an IBM system. Do not use proxy tool in onecli extract path when set the executable binary of legacy ToolsCenter path in global.config. |
| 21 | LAN-over-USB device is disabled on BMC side. Enable it manually. |
| 22 | The BMC default internal IP conflicts with external machine. Correct the problem, and try again. |
| 23 | Failed to restart host system. |
| 24 | Failed to restart BMC. |
| 25 | Function is not supported on target system. |
| 26 | LAN-over-USB device is not detected, make sure RNDIS is correctly installed. |
| 27 | BMC internal error. |
| 28 | No applicable hardware component found. |
| 29 | SMM internal error |
| 30 | Failed due to current command requires administrator permission. Switch to administrator user then try again. |
| 31 | Failed due to current command requires root permission. Switch to root user then try again. |
| 32 | Users are running on an older system. Make sure legacy ToolsCenter path is set correctly to the executable binary of legacy ToolsCenter in global.config. |
| 33 | No available LAN-over-USB device or host IPv4 IP. Ensure the device exists and the IPV4 protocol setting of the device is enabled. |
| 34 | Failed to update due to ESXI internal error. |
| 35 | CMM internal error. |
| 36 | Failed to verify the certificate/fingerprint for the connection(s) specified. |
| 37 | Manually quit OneCLI. |
| 38 | Invalid file folder. |
| 39 | Failed to encrypt/decrypt. |
| 40 | Failed to find the matching credential. |
| 41 | Failed to find the matching tool package for remote machine. |
| 42 | Remote operation not support this remote machine. |
| 43 | Could not find credential file. |
| 44 | The path behind the --remoteos option does not exist. |
| 45 | Attended or unattended mode conflict. |
| 46 | Passphrase error. |
| 47 | Interrupted by user. |
| 48 | Encrypted file is not exist. |
| 49 | Encrypted file is invalid. |
| 50 | Failed to connect KCS. If the system is in Enterprise Strict Mode, users should change the mode, enable ipmi-over-lan and enable ipmi-over-kcs, then try this case again. |
| 51 | Unable to access IPMI service with a password over 20 characters according to IPMI standard. |
| 52 | There is no RESTful service for the target server. |
| 53 | Check the format of input for connection parameter. For credential encrypt user, can't find crypt.json. |
| 54 | The password provided for this account must be changed before access is granted. |
| 55 | BMC CIM Over HTTPS is disabled. |
| 56 | Invalid BMC/CMM/SMM address. |
| 57 | Check BMU requirement failed. |
| 58 | One or more tasks failed. |
| 59 | One or more tasks skipped. |
| 60 | Failed to get data from the Rest interface of BMC. |
| 61 | Failed to get Redfish account on AMD 1S. |
| 62 | Failed to setup filesystem in Maintenance Mode OS. |
| 63 | Unable to establish IPMI v2 / RMCP+ session, which may be caused by authentication failure or insufficient privilege level. |
| 64 | Failed to enable SMM IPMI over LAN. Confirm whether the target system supports. |
| 65 | Function not supported on target system. The Security Mode of target system is Enterprise Strict mode. Users should change the mode and try this case again. |
| 66 | There is no CIM service for the target server. |
| 67 | Function isn't supported when Power on password is enable. |
| 68 | Unsupported interface to the target device. |
| 69 | Interprocess conflict. The desired resource may be currently occupied by another process. |
Give documentation feedback