HP Integrity rx4640 Windows Integrity Management Agents Reference - Page 88

7867 7871 7873 7874 7875 7877 7878 7879 7880 7891 7892 Input power has created some fault conditions. This will be evident by the presence of several chassis codes in theError Log within the same time frame. TheError Log must be reviewed carefully for the root cause of the errors. There is almost always a single cause, even if many events are reported. The MP is not communicating with the CLU. The MP bus (USB) is not functioning. There should be many entries in theError Log with the same type of error message. They will point to MP bus errors. Also, try the GSP "PS" command. This will display status of entities within a cabinet. Contact HP Support personnel to troubleshoot the problem. If this is the only READ failure in this timeframe, replace the SBCH board following the SBCH Board Remove + Replace Procedures as soon as possible. If there are other READ failures in this same cabinet, replace the Utilities The CLU cannot read the data contained in the Board following the Utilities Board Remove and EEPROM on the SBCH board in the same cabinet. Replace Procedures. Attempted access to read the UGUY FRUID EEPROM failed. If there is only one FRUID that can't be read, replace that FRU as soon as possible. If there are a lot of log entries for different FRUs, suspect the Utilities Board or the Utilities cable to those FRUs. For example, if the failures are all associated with a Master IO Backplane, the failing FRU is probably the Utilities cable to that backplane. Could possibly be a bent pin on the System Backplane Utilities cable connectors. Check the connectors at each end of the cable for bent or broken pins. If the connectors and cable are good, replace the System Backplane following the System Backplane Remove and Replace procedures. NOTE: System Backplane replacement is a major undertaking. Ensure all other possibilities have been explored before The I2C bus into the System Backplane EEPROM replacing the backplane. You should have WTEC is bad. approval before replacing the backplane. The I2C controller on the Utilities Board (CLU section) is bad. This will be shown by many I2C failure codes in theError Log. These codes should identify entities on both the System Backplane Replace the Utilities board (UGUY) following the and the Master IO Backplane. Utilities Board Remove and Replace procedures. Check and reseat the System Backplane Utilities The 100 pin cable from the Utilities Backplane to cable. If no help, replace the System Backplane the System Backplane is bad, or is not properly utilities cable following the Backplane Utilities connected. Cable Remove and Replace procedures. Check other log entries around this time for other events. If there are other events, analyze for best troubleshooting approach. Check the log carefully as a shorted ASIC could cause many errors to While running normally, the CLU microcontroller occur. These errors will not necessarily point to detected a fault on the I2C Bus from the system the ASIC. If none, replace failed Backplane Power Backplane LPM. Board. The CLU was unable to write to the voltage margin register on the System backplane. Try re-margining the system backplane and check connections. If many I2C access events are occurring inspect the UGUY utilities board. The entity being written to is not powered up. Power the entity with the PE command. The CPU fan identified by the attached physical Contact HP Support personnel to troubleshoot location has failed. problem 88 Management Agents Event Tables