HP Integrity rx2800 HP Insight Management WBEM Provider Events Reference Guide - Page 49

Read command on System Backplane I2C bus failed. Probable Cause: The I2C

Get HP Integrity rx2800 - i2 PDF manuals and user guides View all HP Integrity rx2800 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 49 highlights

7867 7871 7873 7874 7875 7877 7878 7879 7880 Error Warning Warning Warning Warning Warning Warning Error Error IO Power Board Fault. Probable Cause: The named power brick on the named IO Chassis has failed. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 691. WBEM ProviderName: FPL_IndicationProvider. Voltage Margin on IO Power Board failed. Probable Cause: The IO Power Board LPM is not communicating with the CLU. Recommended Action: Some troubleshooting will be involved here. Is it the IO Power Board LPM, or the CLU. You'll have to check the Error Log for other entries related to either CLU communications problems or the IO Power Board LPM. If there are messages about other HIOPB_VOLT_MRGN_FAIL entries as well as SYS_BKP_VOLT_MRGN_FAIL, it is pointing to the CLU. WBEM EventID: 692. WBEM ProviderName: FPL_IndicationProvider. Failure to read data from a SBCH FRUID EEPROM. Probable Cause: The CLU cannot read the data contained in the EEPROM on the SBCH board in the same cabinet. Recommended Action: 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. WBEM EventID: 694. WBEM ProviderName: FPL_IndicationProvider. Failure to read data from a UGUY FRUID EEPROM. Probable Cause: Attempted access to read the UGUY FRUID EEPROM failed. Recommended Action: 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. WBEM EventID: 695. WBEM ProviderName: FPL_IndicationProvider. Read EEPROM failed. Probable Cause: The I2C bus into the System Backplane EEPROM is bad. Recommended Action: 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. WBEM EventID: 696. WBEM ProviderName: FPL_IndicationProvider. Read command on System Backplane I2C bus failed. Probable Cause: The I2C controller on the Utilities Board (CLU section) is bad. This will be shown by many I2C failure codes in the Error Log. These codes should identify entities on both the System Backplane and the Master IO Backplane. Recommended Action: Replace the Utilities board (UGUY) following the Utilities Board Remove and Replace procedures. WBEM EventID: 697. WBEM ProviderName: FPL_IndicationProvider. Write command on System Backplane I2C bus failed. Probable Cause: The 100 pin cable from the Utilities Backplane to the System Backplane is bad, or is not properly connected. Recommended Action: 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. WBEM EventID: 698. WBEM ProviderName: FPL_IndicationProvider. System Backplane Power Fault. Probable Cause: While running normally, the CLU microcontroller detected a fault on the I2C Bus from the system Backplane LPM. Recommended Action: 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. WBEM EventID: 699. WBEM ProviderName: FPL_IndicationProvider. System Backplane voltage margin failed. Probable Cause: The CLU was unable to write to the voltage margin register on the System backplane. Recommended Action: Try re-margining the system backplane and check connections. If many I2C access events are occurring inspect the UGUY utilities board. WBEM EventID: 700. WBEM ProviderName: FPL_IndicationProvider. Platform Events 49

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
IO Power Board Fault. Probable Cause: The named power brick on the named IO
Chassis has failed. Recommended Action: Contact HP Support personnel to
troubleshoot the problem. WBEM EventID: 691. WBEM ProviderName:
FPL_IndicationProvider.
Error
7867
Voltage Margin on IO Power Board failed. Probable Cause: The IO Power Board
LPM is not communicating with the CLU. Recommended Action: Some
troubleshooting will be involved here. Is it the IO Power Board LPM, or the CLU.
You'll have to check the Error Log for other entries related to either CLU
communications problems or the IO Power Board LPM. If there are messages about
other HIOPB_VOLT_MRGN_FAIL entries as well as SYS_BKP_VOLT_MRGN_FAIL,
it is pointing to the CLU. WBEM EventID: 692. WBEM ProviderName:
FPL_IndicationProvider.
Warning
7871
Failure to read data from a SBCH FRUID EEPROM. Probable Cause: The CLU cannot
read the data contained in the EEPROM on the SBCH board in the same cabinet.
Recommended Action: 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. WBEM EventID: 694. WBEM ProviderName:
FPL_IndicationProvider.
Warning
7873
Failure to read data from a UGUY FRUID EEPROM. Probable Cause: Attempted
access to read the UGUY FRUID EEPROM failed. Recommended Action: 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. WBEM
EventID: 695. WBEM ProviderName: FPL_IndicationProvider.
Warning
7874
Read EEPROM failed. Probable Cause: The I2C bus into the System Backplane
EEPROM is bad. Recommended Action: 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. WBEM EventID: 696. WBEM ProviderName:
FPL_IndicationProvider.
Warning
7875
Read command on System Backplane I2C bus failed. Probable Cause: The I2C
controller on the Utilities Board (CLU section) is bad. This will be shown by many
I2C failure codes in the Error Log. These codes should identify entities on both the
System Backplane and the Master IO Backplane. Recommended Action: Replace the
Utilities board (UGUY) following the Utilities Board Remove and Replace procedures.
WBEM EventID: 697. WBEM ProviderName: FPL_IndicationProvider.
Warning
7877
Write command on System Backplane I2C bus failed. Probable Cause: The 100 pin
cable from the Utilities Backplane to the System Backplane is bad, or is not properly
connected. Recommended Action: 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. WBEM EventID: 698. WBEM
ProviderName: FPL_IndicationProvider.
Warning
7878
System Backplane Power Fault. Probable Cause: While running normally, the CLU
microcontroller detected a fault on the I2C Bus from the system Backplane LPM.
Recommended Action: 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. WBEM
EventID: 699. WBEM ProviderName: FPL_IndicationProvider.
Error
7879
System Backplane voltage margin failed. Probable Cause: The CLU was unable to
write to the voltage margin register on the System backplane. Recommended Action:
Try re-margining the system backplane and check connections. If many I2C access
events are occurring inspect the UGUY utilities board. WBEM EventID: 700. WBEM
ProviderName: FPL_IndicationProvider.
Error
7880
Platform Events
49