HP Integrity Superdome SX2000 HP Insight Manager WBEM Provider Events Referenc - Page 41

Waiting for the XBC Global Semaphore has timed out. Probable Cause: XBC Key

Page 41 highlights

Event ID Event Severity 7673 Error 7674 Error 7684 Warning 7685 Warning 7686 Warning 7690 Error 7718 Warning 7732 Error 7733 Error 7734 Error 7758 Error Event Description Waiting for the XBC Global Semaphore has timed out. Probable Cause: XBC Key Contention. Hardware Failure Recommended Action: Look for other chassis codes that indicate XBC Key contention. Check XBC. Check Links/Flex Cables. WBEM EventID: 608. WBEM ProviderName: FPL_IndicationProvider. A timeout occurred while attempting to release the XBC semaphore. Probable Cause: XBC Key Contention. Hardware Failure Recommended Action: Look for additional chassis codes that would explain the failure. Check XBC. Check Link/Flex Cables. WBEM EventID: 609. WBEM ProviderName: FPL_IndicationProvider. Management Processor Firmware Battery Failure or NVRAM change. Probable Cause: Determine if the firmware was recently upgraded. This is often the reason for the NVRAM to change. If not, and the A/C power has been removed, than it's possible the battery is indeed going bad and would need to be replaced. WBEM EventID: 610. WBEM ProviderName: FPL_IndicationProvider. Management Processor Firmware Software Error. Probable Cause: A software error was detected and is being logged. The internal data is connected to the location and module where the error occurred. The Forward Progress Log will receive additional (lower alert level) event entries with more data associated with this event. WBEM EventID: 611. WBEM ProviderName: FPL_IndicationProvider. Management Processor detected an I2C Communication Error with BMC. Probable Cause: An I2C Communication failure with the Baseboard Management Controller was detected. Without I2C communication, the system cannot be powered on/off or reset. Check the I2C communication via the 'SR' command or the 'PS' command. If it is indeed down, look for hardware reasons. It's possible resetting the Management Processor firmware ('XD' command option 'r') or completely cycling AC power of the system will restore the communication. WBEM EventID: 612. WBEM ProviderName: FPL_IndicationProvider. A CRC error was discovered when verifying the ROM. Probable Cause: Either the ROM was programmed incorrectly or has gone bad. Reprogram the Flash on the cell board. WBEM EventID: 613. WBEM ProviderName: FPL_IndicationProvider. (HWE) IO backplane type unknown. Probable Cause: This is an alien IO backplane. IO discovery will fail. I/O for the cell will not be initialized. Recommended Action: Replace I/O backplane or chassis or update firmware. WBEM EventID: 1757. WBEM ProviderName: FPL_IndicationProvider. CPU Revisions did not match. Probable Cause: 2 cpus are at different revisions. Replace incompatible cpu. WBEM EventID: 638. WBEM ProviderName: FPL_IndicationProvider. 2 cpus are running at mismatched frequencies. Probable Cause: There is a CPU or Cell compatibility problem. Verify that all cpus are clocked at the same frequency and have the same ratios set. WBEM EventID: 639. WBEM ProviderName: FPL_IndicationProvider. A cpu is being overclocked. Probable Cause: A cpu is being clocked at a rate higher than it is rated for. Replace the cpu or cell board. WBEM EventID: 640. WBEM ProviderName: FPL_IndicationProvider. Copy of complex profile on sub and cells don't match. Probable Cause: MP NVRAM was erased by removing MP from system without setting 'NVRAM SAVE' switch to on. MP was replaced with cabinet's AC Breakers 'off'. Either of first two causes and replacing or installing a cell board with cabinet's AC Breakers 'off'. Recommended Action: Remove cell board causing problem. Power complex on and allow cells to distribute their copy of complex profile to MP, then add new cell following proper OLA procedures. Remove improper cell board. Execute MP Handler 'CC' command and choose 'Last Profile'. This will load the sub with what should be the same copy as the cells. Then add new cell board. WBEM EventID: 641. WBEM ProviderName: FPL_IndicationProvider. Platform Events 41

  • 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

Event Description
Event
Severity
Event ID
Waiting for the XBC Global Semaphore has timed out. Probable Cause: XBC Key
Contention. Hardware Failure Recommended Action: Look for other chassis codes
that indicate XBC Key contention. Check XBC. Check Links/Flex Cables. WBEM
EventID: 608. WBEM ProviderName: FPL_IndicationProvider.
Error
7673
A timeout occurred while attempting to release the XBC semaphore. Probable Cause:
XBC Key Contention. Hardware Failure Recommended Action: Look for additional
chassis codes that would explain the failure. Check XBC. Check Link/Flex Cables.
WBEM EventID: 609. WBEM ProviderName: FPL_IndicationProvider.
Error
7674
Management Processor Firmware Battery Failure or NVRAM change. Probable Cause:
Determine if the firmware was recently upgraded. This is often the reason for the
NVRAM to change. If not, and the A/C power has been removed, than it's possible
the battery is indeed going bad and would need to be replaced. WBEM EventID: 610.
WBEM ProviderName: FPL_IndicationProvider.
Warning
7684
Management Processor Firmware Software Error. Probable Cause: A software error
was detected and is being logged. The internal data is connected to the location and
module where the error occurred. The Forward Progress Log will receive additional
(lower alert level) event entries with more data associated with this event. WBEM
EventID: 611. WBEM ProviderName: FPL_IndicationProvider.
Warning
7685
Management Processor detected an I2C Communication Error with BMC. Probable
Cause: An I2C Communication failure with the Baseboard Management Controller
was detected. Without I2C communication, the system cannot be powered on/off or
reset. Check the I2C communication via the 'SR' command or the 'PS' command. If
it is indeed down, look for hardware reasons. It's possible resetting the Management
Processor firmware ('XD' command option 'r') or completely cycling AC power of
the system will restore the communication. WBEM EventID: 612. WBEM
ProviderName: FPL_IndicationProvider.
Warning
7686
A CRC error was discovered when verifying the ROM. Probable Cause: Either the
ROM was programmed incorrectly or has gone bad. Reprogram the Flash on the cell
board. WBEM EventID: 613. WBEM ProviderName: FPL_IndicationProvider.
Error
7690
(HWE) IO backplane type unknown. Probable Cause: This is an alien IO backplane.
IO discovery will fail. I/O for the cell will not be initialized. Recommended Action:
Replace I/O backplane or chassis or update firmware. WBEM EventID: 1757. WBEM
ProviderName: FPL_IndicationProvider.
Warning
7718
CPU Revisions did not match. Probable Cause: 2 cpus are at different revisions.
Replace incompatible cpu. WBEM EventID: 638. WBEM ProviderName:
FPL_IndicationProvider.
Error
7732
2 cpus are running at mismatched frequencies. Probable Cause: There is a CPU or
Cell compatibility problem. Verify that all cpus are clocked at the same frequency
and have the same ratios set. WBEM EventID: 639. WBEM ProviderName:
FPL_IndicationProvider.
Error
7733
A cpu is being overclocked. Probable Cause: A cpu is being clocked at a rate higher
than it is rated for. Replace the cpu or cell board. WBEM EventID: 640. WBEM
ProviderName: FPL_IndicationProvider.
Error
7734
Copy of complex profile on sub and cells don't match. Probable Cause: MP NVRAM
was erased by removing MP from system without setting 'NVRAM SAVE' switch to
on. MP was replaced with cabinet's AC Breakers 'off'. Either of first two causes and
replacing or installing a cell board with cabinet's AC Breakers 'off'. Recommended
Action: Remove cell board causing problem. Power complex on and allow cells to
distribute their copy of complex profile to MP, then add new cell following proper
OLA procedures. Remove improper cell board. Execute MP Handler 'CC' command
and choose 'Last Profile'. This will load the sub with what should be the same copy
as the cells. Then add new cell board. WBEM EventID: 641. WBEM ProviderName:
FPL_IndicationProvider.
Error
7758
Platform Events
41