Windows Integrity Management Agents Reference

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.
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.7867
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.The MP is not communicating with the CLU.7871
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
Board following the Utilities Board Remove and
Replace Procedures.
The CLU cannot read the data contained in the
EEPROM on the SBCH board in the same cabinet.7873
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.
Attempted access to read the UGUY FRUID
EEPROM failed.7874
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
replacing the backplane. You should have WTEC
approval before replacing the backplane.
The I2C bus into the System Backplane EEPROM
is bad.7875
Replace the Utilities board (UGUY) following the
Utilities Board Remove and Replace procedures.
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
and the Master IO Backplane.7877
Check and reseat the System Backplane Utilities
cable. If no help, replace the System Backplane
utilities cable following the Backplane Utilities
Cable Remove and Replace procedures.
The 100 pin cable from the Utilities Backplane to
the System Backplane is bad, or is not properly
connected.7878
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
occur. These errors will not necessarily point to
the ASIC. If none, replace failed Backplane Power
Board.
While running normally, the CLU microcontroller
detected a fault on the I2C Bus from the system
Backplane LPM.7879
Try re-margining the system backplane and check
connections. If many I2C access events are
occurring inspect the UGUY utilities board.
The CLU was unable to write to the voltage
margin register on the System backplane.7880
Power the entity with the PE command.The entity being written to is not powered up.7891
Contact HP Support personnel to troubleshoot
problem
The CPU fan identified by the attached physical
location has failed.7892
88 Management Agents Event Tables