IMM I2C test
Use this information to resolve IMM I2C test errors by referencing the error codes and following the suggested corrective actions.
Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved.
| ||
---|---|---|
Error code | Description | Action |
166-000-xxx | Passed the IMM I2C test | |
166-801-xxx | IMM I2C test stopped: the IMM returned an incorrect response length. |
|
166-802-xxx | IMM I2C test stopped: the test cannot be completed for an unknown reason. |
|
166-803-xxx | IMM I2C test stopped: the node is busy; try later. |
|
166-804-xxx | IMM I2C test stopped: invalid command. |
|
166-805-xxx | IMM I2C test stopped: invalid command for the given LUN |
|
166-806-xxx | IMM I2C test stopped: timeout while processing the command. |
|
166-807-xxx | IMM I2C test stopped: out of space. |
|
166-808-xxx | IMM I2C test stopped: reservation canceled or invalid reservation ID. |
|
166-809-xxx | IMM I2C test stopped: request data was truncated. |
|
166-810-xxx | IMM I2C test stopped: request data length is invalid |
|
166-811-xxx | IMM I2C test stopped: request data field length limit is exceeded. |
|
166-812-xxx | IMM I2C Test stopped a parameter is out of range. |
|
166-813-xxx | IMM I2C test stopped: cannot return the number of requested data bytes. |
|
166-814-xxx | IMM I2C test stopped: requested sensor, data, or record is not present. |
|
166-815-xxx | IMM I2C test stopped: invalid data field in the request. |
|
166-816-xxx | IMM I2C test stopped: the command is illegal for the specified sensor or record type. |
|
166-817-xxx | IMM I2C test stopped: a command response could not be provided. |
|
166-818-xxx | IMM I2C test stopped: cannot execute a duplicated request. |
|
166-819-xxx | IMM I2C test stopped: a command response could not be provided; the SDR repository is in update mode. |
|
166-820-xxx | IMM I2C test stopped: a command response could not be provided; the device is in firmware update mode. |
|
166-821-xxx | IMM I2C test stopped: a command response could not be provided; IMM initialization is in progress. |
|
166-822-xxx | IMM I2C test stopped: the destination is unavailable. |
|
166-823-xxx | IMM I2C test stopped: cannot execute the command; insufficient privilege level. |
|
166-824-xxx | IMM I2C test stopped: cannot execute the command. |
|
166-901-xxx | Failed the IMM I2C test due to a failure in the host/H8 bus - BUS 0. |
|
166-902-xxx | Failed the IMM I2C test due to a failure in the blade server temperature sensor and light path bus - BUS 1. |
|
166-903-xxx | Failed the IMM I2C test due to a failure in the CPU bus - BUS 2. |
|
166-904-xxx | Failed the IMM I2C test due to a failure in the I2C MUX bus (one of the expansion cards) - BUS 3. |
|
166-905-xxx | Failed the IMM I2C test due to a failure in the SMB bus - BUS 4. |
|
166-906-xxx | Failed the IMM I2C test due to a failure in the PCI-E DDR2 bus - BUS 5. |
|
166-909-xxx | Failed the IMM I2C test due to a failure in the scalable memory interconnect A and C - memory drawer BUS 0. |
|
166-910-xxx | Failed the IMM I2C test due to a failure in the scalable memory interconnect B and F - memory drawer BUS 1. |
|
166-911-xxx | Failed the IMM I2C test due to a failure in the scalable memory interconnect D and E - memory drawer BUS 2. |
|
166-913-xxx | Failed the IMM I2C test due to a failure in the light path bus - memory drawer BUS 4. |
|
166-916-xxx | Failed the IMM I2C test due to a failure in the temperature sensor and VPD bus - memory drawer BUS 7. |
|
Give feedback