Matrix for OneCLI V2.3.0 and OneCLI V2.4.0 return codes
This section describes the matrix for OneCLI V2.3.0 and OneCLI V2.4.0 return codes.
| V2.3.0 | V2.4.0 | ||
|---|---|---|---|
| Return codes | Description | Return codes | Description |
| 0 | Success. | 0 | Success. |
| 1 | Invalid command. | 4 | Invalid command. |
| 2 | Generic failure. | 1 | Generic failure. |
| 3 | XML file is missing. | 6 | Local file does not exist. |
| 4 | Restart OS Failure. | 23 | Failed to restart host system. |
| 5 | Failed to connect. | 13 | Failed to connect. |
| 6 | Platform error. | 25 | Function not supported on target system. |
| 7 | Input xml file format error. | 7 | The file is not valid. |
| 8 | OPEN DLL FAILURE. | 17 | Internal error. |
| 9 | GET NULL POINTER. | 17 | Internal error. |
| 10 | NO INTERFACE FOUND. | 17 | Internal error. |
| 11 | RETURN INVALID RESULT. | 17 | Internal error. |
| 12 | Unknown exception. | 1 | Generic failure. |
| 13 | Invalid parameter. | 5 | Invalid parameter. |
| 14 | Local file does not exist. | 6 | Local file does not exist. |
| 15 | Failed to create directory. | 8 | Failed to create directory. |
| 16 | Failed to read or write file. | 9 | Failed to open file. |
| 17 | Ping BMC failed. | 14 | Ping failed. |
| 18 | Fail to get XCC account through KCS. | 19 | Fail to get XCC account through KCS. |
| 19 |
| 26 |
|
| 20 | No package needs update. | 110 | No package needs update. |
| 21 | Users are running on a blue system. Do not use proxy uxspi in onecli extract path when set the executable binary of UXSPI path in global.config. | 20 | Users are running on a blue system. Do not use proxy uxspi in onecli extract path when set the executable binary of UXSPI path in global.config. |
| 22 | Authentication with BMC failed. | 12 | Authentication failed. |
| 23 | Authentication failed by FTP server. | 12 | Authentication failed. |
| 24 | Fail to create directory or put file in FTP server: No such file or directory, or permission denied for the specified user name. | 15 | Upload failed. |
| 25 | LXCE has no enable permission. Enable BMC Lan Over USB device manually. | 21 | LAN-over-USB device is disabled on BMC side. Enable it manually. |
| 26 | Fail to upload data to specified FTP server. | 15 | Upload failed. |
| 27 | Fail to connect through IPMI. | 13 | Failed to connect. |
| 28 | Ping CMM failed. | 14 | Ping failed. |
| 29 | Fail to get driver information. | 1 | Generic failure. |
| 30 | Fail to get machine type. | 0x01/1 | Generic failure. |
| 31 | Fail to get firmware information. | 1 | Generic failure. |
| 32 | Fail to read inventory XML. | 10 | Failed to read file. |
| 33 | Fail to write inventory XML. | 11 | Failed to write file. |
| 34 | Fail to write inventory HTML. | 11 | Failed to write file. |
| 35 | UXSP xml do not exist. Check the UXSP package. | 6 | Local file does not exist. |
| 36 | Time-out. | 18 | Time-out. |
| 96 | Failed to run the command. | 1 | Generic failure. |
| 97 | Failed to get information. | 125 | Failed to get information. |
| 98 | Failed to set the setting items. | 124 | Failed to set the setting items. |
| 99 | Failed to open the file. | 9 | Failed to open file. |
| 100 | Failed to read the file. | 10 | Failed to read file. |
| 101 | Failed to write the file. | 11 | Failed to write file. |
| 102 | Failed to generate/export/import/delete certification. | 123 | Failed to generate/export/import/delete certification. |
| 103 | Failed to reconnect to BMC after the command is executed successfully. Users could try another method to check the result. | 122 | Failed to reconnect to BMC after the command is executed successfully. Users could try another method to check the result. |
| 104 | One or more commands are not valid in the batch file. | 121 | One or more commands are not valid in the batch file. |
| 105 | Failed to show the instance setting. The instance should be created at first. | 120 | Failed to show the instance setting. The instance should be created at first. |
| 106 | Invalid value for set command. | 119 | Invalid value for set command. |
| 64 | Update error: Acquire command failed. | 1 | Generic failure. |
| 65 | Update error: Scan command failed. | 1 | Generic failure. |
| 66 | Update error: Query command failed. | 1 | Generic failure. |
| 67 | Update error: Compare command failed. | 1 | Generic failure. |
| 68 | Update error: Flash command failed. | 1 | Generic failure. |
| 69 | Update error: File related error occurred, see log/xml for more information. | 11 | Failed to write file. |
| 70 | Update error: CIM service fails. See log/xml for more information. | 1 | Generic failure. |
| 71 | Update error: There is something wrong with the device. See log/xml for more information. | 120 | Update error: There is something wrong with the device. See log/xml for more information. |
| 72 | Update error: Failed to generate common_result.xml. | 11 | Failed to write file. |
| 73 | Could not get OS type using scan command. | 111 | Failed to get OS type. |
| 74 | Invalid/unsupported machine type. | 104 | No applicable update available on the repository for specified machine-type/OS. |
| 75 | Invalid/unsupported OS. | 112 | Current Operating System is not supported. |
| 76 | Authentication failed, unable to validate userid/password. | 12 | Authentication failed. |
| 77 | Update error: Flash finished running, however multiple packages failed to be flashed. Check flash status xml for more information. | 11 | Failed to write file. |
| 78 | Users are running on an IBM system. Make sure that UXSPI_PATH is set correctly to the executable binary of UXSPI in global.config. | 114 | Users are running on an IBM system. Make sure that UXSPI_PATH is set correctly to the executable binary of UXSPI in global.config. |
| 79 | Users are running on an IBM system. But the current command is not supported in UXSPI. | 109 | Users are running against an IBM system, but the current command is not supported. |
| 80 | Update blue not supported. | 109 | Users are running against an IBM system, but the current command is not supported. |
| 81 | UXSPI does not run successfully, to trace error, see log relate to UXSPI. | 17 | Internal error. |
| 82 | Update module was not able to write to XML file. | 11 | Failed to write file. |
| 83 | Update flash module failure: failed to run flash with ESXi. See log/xml for more detail information. | 1 | Generic failure. |
| 84 | Update flash module failure: failed to run flash with IOSwitch. See log/xml for more detail information. | 1 | Generic failure. |
| 85 | Update flash module failure: failed to run flash with CMM Update. See log/xml for more detail information. | 1 | Generic failure. |
| 86 | Update flash module failure: failed to run flash with OOB. See log/xml for more detail information. | 1 | Generic failure. |
| 87 | Update flash module failure: Error occurred when running xFirmware for in-band flash. | 1 | Generic failure. |
| 88 | Update flash module failure: Error occurred when running Option Update for in-band flash. | 1 | Generic failure. |
| 90 | Update flash failure: Error payload file does not exist. | 7 | Local file does not exist. (dynamic message) |
| 91 | Update flash failure: Error backup does not support. | 108 | Backup bank does not exist. |
| 92 | The BMC default internal IP conflicts with external machine. Correct the problem, and try again. | 22 | The BMC default internal IP conflicts with external machine. Correct the problem, and try again. |
| 94 | Update flash failure: current BMC does not support internal SFTP for this case. | 123 | Current BMC version does not support this package. Upgrade BMC to the latest version, and try again. |
| 95 | Update application fails to run. | 1 | Generic failure. |
| 208 | Download SMM FFDC error: setup environment failed. | 125 | Download SMM FFDC error: setup environment failed. |
| 209 | Download SMM FFDC error: start dump failed. | 124 | Download SMM FFDC error: start dump failed. |
| 210 | Download SMM FFDC error: query failed. | 123 | Download SMM FFDC error: query failed. |
| 211 | Download SMM FFDC error: tar ffdc files failed. | 1222 | Download SMM FFDC error: tar ffdc files failed. |
| 212 | Download SMM FFDC error: upload path does not exist. | 15 | Upload failed. |
| 213 | Download SMM FFDC error: upload failed. | 15 | Upload failed. |
| 214 | Download SMM FFDC error: tftp server is not found. | 121 | Download SMM FFDC error: tftp server is not found. |
| 215 | Download SMM FFDC error: time-out. | 18 | Time-out. |
| 216 | Download SMM FFDC error: unknown error. | 1 | Generic failure. |
| 217 | FFDC log is uploaded to the specified FTP/TFTP server, but fails to download FFDC log from FTP/TFTP server. | 120 | FFDC log is uploaded to the specified FTP/TFTP server, but fails to download FFDC log from FTP/TFTP server. |
| 218 | Failed to get FFDC log. | 119 | Failed to get FFDC log. |
| 176 | Raid config fails to operate. | 125 | Raid config fails to operate. |
| 177 | Raid config ini file error. | 124 | Raid config ini file error. |
| 178 | Raid config has no config to operate. | 123 | Raid config has no config to operate. |
| 179 | Raid config does not need make good. | 122 | Raid config does not need make good. |
| 180 | Raid config does not need make jbod. | 121 | Raid config does not need make jbod. |
| 52 | Fail to trigger diags. | 18 | Fail to trigger diags. |
| 53 | Fail to get status of diags. | 124 | Fail to get status of diags. |
| 54 | Fail to get result file. | 123 | Fail to get result file. |
| 55 | Diagnostics time-out. | 18 | Time-out. |
| 128 | Failed to run the command. | 1 | Generic failure. |
| 129 | The FoD key file is not valid. | 125 | The FoD key file is not valid. |
| 130 | Specified machine type or serial number is not valid. | 124 | Specified machine type or serial number is not valid. |
| 131 | The FoD key file is not found. | 123 | The FoD key file is not found. |
| 132 | Authentication failed. | 12 | Authentication failed. |
| 133 | The FoD key is not found from target key repository. | 122 | The FoD key is not found from target key repository. |
| 134 | The FoD key ID is not valid. | 121 | The FoD key ID is not valid. |
| 135 | Active key exists in KMS Web site. | 120 | Active key exists in KMS Web site. |
| 136 | Authentication code does not exist. | 119 | Authentication code does not exist. |
| 137 | Unique identifier is not valid. | 118 | Unique identifier is not valid. |
| 138 | Failed to install the FoD key. | 117 | Failed to Install the FoD key. |
| 139 | Failed to uninstall the FoD key. | 116 | Failed to export the FoD key. |
| 140 | Failed to export the FoD key. | 115 | Fail to export the FoD key. |
| 141 | Failed to report the FoD key. | 114 | Failed to report the FoD key. |
| 142 | Failed to get current tier. | 113 | Failed to get current tier. |
| 160 | MODULEMANAGER_ERROR | Deprecated | |
| 161 | MODULEMANAGER_NO_NEWER_UPDATE | Deprecated | |
| 162 | MODULEMANAGER_XML_PARSE_ERROR | Deprecated | |
| 163 | MODULEMANAGER_DOWNLOAD_ERROR | Deprecated | |
| 164 | MODULEMANAGER_INCOMPATIBLE_ERROR | Deprecated | |
| 165 | MODULEMANAGER_COPY_ERROR | Deprecated | |
| 221 | Switch does not support EHCM or the CMM build is not supported to check EHCM. | 118 | Switch does not support EHCM or the CMM build is not supported to check EHCM. |
| 222 | Check EHCM time-out because the EHCMState is busy or setting up. | 18 | Time-out. |
| 223 | Reseat failed. | 1 | Generic failure. |
Give documentation feedback