Windows Integrity Management Agents Reference

Make sure Onboard Administator has the
appropriate number and configuration of power
supplies. Reduce power required by the blade
(for instance, remove some memory or a CPU.)
Or, if there are powered-on blades that are not in
use, power them off.
A forced power on occurred. Usually this is
performed when a normal power on request is
denied. The Onboard Administrator may now
be running in a non-redundant or over-budget
power configuration.12165
The communication loss may have been
temporary and nothing needs to be done if the
communication is now working. Check the Fault
LED on the enclosure manager. Reset the
enclosure manager. Reset the management
processor. Replace the enclosure manager
The MP has repeatedly requested communication
with the Onboard Administrator and has not
received a response. This may be because the EM
has a fault condition, or is busy, being reset, or
removed.12168
Collect the entire FPL, SEL, console logs and
forward them to the SFW team. Also note all
activities around the time of this event. The entire
logs must analyzed by the SFW team before
further actions can be taken. The system must be
cold reset to resume normal operation
A CPU has tried to acquired the same semaphore
twice which resulted in a deadlock. This is an
internal SFW error and is not recoverable.12193
Collect the entire FPL, SEL, console logs and
forward them to the SFW team. Also note all
activities around the time of this event. The entire
logs must analyzed by the SFW team before
further actions can be taken. The system must be
cold reset to resume normal operation
A CPU has tried to acquired the same semaphore
twice which resulted in a deadlock. This is an
internal SFW error and is not recoverable.12194
Collect the entire FPL, SEL, console logs and
forward them to the SFW team. Also note all
activities around the time of this event. The entire
logs must analyzed by the SFW team before
further actions can be taken. The system must be
cold reset to resume normal operation
A CPU has tried to acquired the same semaphore
twice which resulted in a deadlock. This is an
internal SFW error and is not recoverable.12195
Collect the entire FPL, SEL, console logs and
forward them to the SFW team. Also note all
activities around the time of this event. The entire
logs must analyzed by the SFW team before
further actions can be taken. The system must be
cold reset to resume normal operation
A CPU has tried to acquired the same semaphore
twice which resulted in a deadlock. This is an
internal SFW error and is not recoverable.12196
Push out new complex profiles and reset.
The Group A or Group C complex profiles didn't
match on all cells in the partition.12199
Replace the specified location with the supported
Core I/O card.
Either an I/O device on the Core I/O has failed or
the wrong card is plugged into the location of the
expected Core I/O.12204
Contact HP support.
OS has not fully set up GPE enable bits with the
FSHWA interface12207
Contact HP support.
OS incorrectly set up the IOSAPIC redirection
entry through the FSHWA interface.12208
Determine why operating system did not reset
the timerOperating system has not reset watchdog timer.12210
Analyze the dump + logs for cause. If necessary
contact HP Support for assistance.An MCA or INIT occurred.12217
Analyze the dump + logs for cause. If necessary
contact HP Support for assistance.An OS has panicked.12218
Contact your HP Customer Support
Representative to update all firmware entities to
revisions that are appropriate for the system type.
Following an in-the-box system type upgrade, or
after a UGUY board was replaced, the CLU FW
may not have been updated to an appropriate
revision for the system type.12222
122 Management Agents Event Tables