Windows Integrity Management Agents Reference

Either the ROM was programmed incorrectly or
has gone bad. Reprogram the Flash on the cell
board.7690
Replace I/O backplane or chassis or update
firmware.
This is an alien IO backplane. IO discovery will
fail. I/O for the cell will not be initialized.7718
2 cpus are at different revisions. Replace
incompatible cpu.7732
There is a CPU or Cell compatibility problem.
Verify that all cpus are clocked at the same
frequency and have the same ratios set.7733
A cpu is being clocked at a rate higher than it is
rated for. Replace the cpu or cell board.7734
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.
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".7758
Turn off AC breakers to cabinet with duplicate
number. Check all other cabinet numbers in the
complex for validity. Set cabinet number switch
on UGUY-PCB in new cabinet (s) to proper
cabinet number. Turn on AC breakers for
cabinet(s).
When adding a new cabinet to the complex or
replacing the UGUY, the cabinet number switch
was set to a number already in use.7760
If "cc" command is selected, choose "last good
profile" instead of genesis profile, or remove
illegal cell(s), power up and follow OL* Rules.
MP lost its profile by being replaced with power
off ,or, "NVRAM save" switch was not enabled
and MP was removed and replaced. Also, at the
same time, a cell was replaced or added while
power was off. Both scenarios are violations of
OL* Rules. A complex_profile_incoherent code
was issued. The "cc" command was run and
genesis profile was selected.7767
Replace battery as per MP Battery Remove and
Replace procedures.
MP was running on battery for too long. Someone
didn't set "NVRAM Save" switch to "off".7771
Find out why the partition's OS had hung. The
cause could be bad HW that crashed the partition,
or in rare cases, a combination of events that
caused the OS to be unable to refresh the
watchdog timer. Look for other events preceding
the timeout for clues to the root cause of the
partition being unresponsive.
The watchdog mechanism triggers the MP to reset
a partition if its OS becomes unresponsive. An
unresponsive OS is detected when the OS fails to
refresh the watchdog timer before it expires. PA
systems refresh the watchdog timer by emitting
an event with data field set to activity
level/timeout, and the timeout field specifies the
desired timeout. IPF systems refresh the
watchdog timer using the IPMI clear watchdog
command. The MP emits this event when timer
expiration triggers resetting the partition.
OS-specific and platform-specific procedures are
used to enable/disable the watchdog timer from
resetting the partition. See platform and OS
documentation for details.7773
Even though the PDHC will reset itself without
interrupting the cell, HP Support personnel
should be contacted to troubleshoot the PDH
daughtercard and/or cell board as soon as
possible.PDHC Firmware hung; causing inactivity.7774
Correct local environmental problemEnvironment immediately surrounding cabinet.7781
Platform Events – Table 2 (Windows System Log Event ID, Cause, Recommended Action) 85