HP Integrity rx2620 Windows Integrity Management Agents Reference - Page 73
Update SFW. Contact HP support to troubleshoot, Unexpected return to SAL_CHECK.
View all HP Integrity rx2620 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 73 highlights
5266 5268 5270 5278 5279 5280 5335 5354 5359 5360 5361 5365 5366 5376 5380 5383 5403 5404 5405 5406 5407 5408 5411 5416 A PDH register has failed. Reboot if necessary, if problem persists contact your HP representative for support. The handler for SAL_CHECK has failed for an Reboot if necessary, if problem persists contact unknown reason. your HP representative for support. The handler for SAL_INIT has failed for an unknown reason. Reboot if necessary, if problem persists contact your HP representative for support. FW encountered a fatal interleaving error. Update SFW. Contact HP support to troubleshoot the problem Unexpected return to SAL_CHECK. Reboot if necessary, if problem persists contact your HP representative for support. Reboot if necessary, if problem persists contact SAL_INIT has been unexpectedly returned to. your HP representative for support. A CPU that is not fully functional is installed in the cell board. Replace cpu indicated in data field of event. Decode the ASCII string in the data field to determine what resource is missing. Examine earlier chassis codes to determine why that resource is unavailable. A bad complex profile exists. Correct and redistribute. Either a hardware connection problem exists, or fabric was unable to be routed. Verify hardware and reset. This cell took to long completing previous steps to rendezvous. A bad complex profile could also cause this problem. Mixed CPU types are installed in the same partition. Remove them. Cell too slow. Could be bad hardware. Check for If assistance is required, contact the HP Support other errors and reset. Center. Fabric problem, Connection problem or timing problem. Reset the PD. No cells have a functioning core IO card. Add a core IO card to a cell in the PD and reset. Communication with utilities is broken. Check for earlier errors or NVRAM problems. The registry is corrupt or the ROM is incomplete. Reset. Hardware problem. Check connections and reset. Bad hardware. Check crossbar revisions and ensure all installed Bad hardware configuration, different revisions crossbar revisions are the same. Replace the of crossbars are installed. crossbar that is not in rev with the others. Fatal configuration. Reconfigure the hardware. The previous monarch may be suspect. SRAM cannot be located or used on the cell board. Replace the cell board. Platform Events - Table 2 (Windows System Log Event ID, Cause, Recommended Action) 73