HP Integrity rx1620 Windows Integrity Management Agents Reference - Page 94

PAL_SET_PROC_FEATURES to escalate future

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

Page 94 highlights

8721 8722 8723 8745 8747 8752 8756 8757 8758 8761 8762 8763 8768 8771 8772 8784 8787 8797 8798 8806 8807 Unable to configure the LBA replace I/O backplane Could not scan the card in a populated slot. Typically caused by an improperly installed or faulty PCI card. Reseat or replace the faulty card. Unable to obtain semaphore reset Update to latest recipe System firmware was unable to lock either the global or the micro semaphore. Allow the OLA cell to reboot to BIB, then try the OLA operation again. Or, collect IPMI event logs and contact HP Customer Support for assistance. Probably caused by lots of PDT entries, or no main memory present. Cell was issued an OLA command without first updating the complex profile to reflect its slot as Update the complex profile to include the new configured in the partition. cell. Invalidate NVRAM and reset. Couldn't communicate with OLA cell. Collect IPMI events and contact HP Support. Firmware is taking too long to process requests. The PDH FPGA IPR is not cleared after a MAX_RD_CLR_IPR_TRIES on a cell. Contact HP Support personnel to troubleshoot the problem. PDH FPGA IPR is not cleared after a number of Contact HP Support personnel to troubleshoot PDC attempts. the problem. Core cell data could not be accessed/fabric connections went bad Collect IPMI events and contact HP Support. the specified echelon is not fully populated and is not usable add or replace dimms in the specified echelon An invalid port number has been provided. The port number will be converted to an internal port Contact HP Support personnel to analyze the and processing should continue. fabric. An invalid port number has been provided. The port number will be converted to an internal port Contact HP Support personnel to analyze the and processing should continue. fabric. Many possible causes, repair / replace the appropriate part. Service / replace the appropriate part of, or the entire backplane. Needed information could not be obtained. Reset the MP. FW MCA code uses this PAL_SET_PROC_FEATURES to escalate future MCA to BINIT. This event id when emitted during an MCA processing means that any subsequent global MCA would not cause all the processors in the PD to MCA again. This happens because of the NVRAM is full with unconsumed error logs. Clear the error logs. This shouldn't be occur. But in case it does than clear the error logs of this event type from the nvram. 94 Management Agents Event Tables

  • 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
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
replace I/O backplane
Unable to configure the LBA
8721
Reseat or replace the faulty card.
Could not scan the card in a populated slot.
Typically caused by an improperly installed or
faulty PCI card.
8722
reset Update to latest recipe
Unable to obtain semaphore
8723
Allow the OLA cell to reboot to BIB, then try the
OLA operation again. Or, collect IPMI event logs
and contact HP Customer Support for assistance.
System firmware was unable to lock either the
global or the micro semaphore.
8745
Probably caused by lots of PDT entries, or no
main memory present.
8747
Update the complex profile to include the new
cell.
Cell was issued an OLA command without first
updating the complex profile to reflect its slot as
configured in the partition.
8752
Invalidate NVRAM and reset.
8756
Collect IPMI events and contact HP Support.
Couldn't communicate with OLA cell.
8757
Firmware is taking too long to process requests.
8758
Contact HP Support personnel to troubleshoot
the problem.
The PDH FPGA IPR is not cleared after a
MAX_RD_CLR_IPR_TRIES on a cell.
8761
Contact HP Support personnel to troubleshoot
the problem.
PDH FPGA IPR is not cleared after a number of
PDC attempts.
8762
Collect IPMI events and contact HP Support.
Core cell data could not be accessed/fabric
connections went bad
8763
add or replace dimms in the specified echelon
the specified echelon is not fully populated and
is not usable
8768
Contact HP Support personnel to analyze the
fabric.
An invalid port number has been provided. The
port number will be converted to an internal port
and processing should continue.
8771
Contact HP Support personnel to analyze the
fabric.
An invalid port number has been provided. The
port number will be converted to an internal port
and processing should continue.
8772
Many possible causes, repair / replace the
appropriate part.
8784
Service / replace the appropriate part of, or the
entire backplane.
8787
Needed information could not be obtained. Reset
the MP.
8797
FW MCA code uses this
PAL_SET_PROC_FEATURES to escalate future
MCA to BINIT. This event id when emitted
during an MCA processing means that any
subsequent global MCA would not cause all the
processors in the PD to MCA again.
8798
This happens because of the NVRAM is full with
unconsumed error logs. Clear the error logs.
8806
This shouldn't be occur. But in case it does than
clear the error logs of this event type from the
nvram.
8807
94
Management Agents Event Tables