HP Integrity rx4640 Windows Integrity Management Agents Reference - Page 75

No Action Required. Firmware can allocated, Unsupported I/O configuration.

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

Page 75 highlights

5485 5490 5491 5492 5493 5494 5496 5498 5499 5500 5501 5502 5503 5505 5507 5509 5510 5511 5514 5515 5518 5521 Reset Determine the failing component or hardware from the data field as described and replace. Report the IP to the firmware team. Reset the system. This cannot be worked around in the field. Bad NVRam, replace the bad chip. Firmware/software error Check for new version of firmware/OS Contact HP Support Decode the hex vales to ASCII to determine the mode. Other errors will determine action. Reset system to clear the semaphore Try reinitializing NVRAM. If problem persists, contact engineering. Clear NVRAM and reset. No Action Required. Firmware can allocated space for the block. Retry the operation. No action required. NVRAM cannot be used. It must be initialized first. Firmware will attempt the initialization. Band NVRAM/ reinitialize. This can be caused by many conditions including a bad complex profile, a bad hardware configuration, a cell arriving late to the rendezvous point. A cell not being able to rendezvous. Reconfiguration from partition manager is recommended. Verify communications with the utilities system. An error occurred which triggered system firmware to cease making forward progress. The CPU is put into a spin loop so that external debugging can take place. See earlier event ids to help determine the cause of the error. Also note that theError Response Mode is likely to have directed firmware to HALT. DUI was entered before the console is available. DUI will exit and processing will continue. Decode the ASCII message and correct the problem. Delay the request for reconfiguration until after the PD has been released from Sinc BIB. Fabric wasn't able to route to all cells described in the complex profile correctly due to a hardware problem. Some of the cells are unreachable. Update the complex profile or correct the hardware problem. Unsupported I/O configuration. Remove the I/O cards below the specified PCI-to-PCI bridge. Debugging event, not for release. Platform Events - Table 2 (Windows System Log Event ID, Cause, Recommended Action) 75

  • 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
Reset
5485
Determine the failing component or hardware
from the data field as described and replace.
5490
Report the IP to the firmware team. Reset the
system. This cannot be worked around in the
field.
5491
Bad NVRam, replace the bad chip.
5492
Check for new version of firmware/OS Contact
HP Support
Firmware/software error
5493
Decode the hex vales to ASCII to determine the
mode. Other errors will determine action.
5494
Reset system to clear the semaphore Try
reinitializing NVRAM. If problem persists,
contact engineering.
5496
Clear NVRAM and reset.
5498
No Action Required. Firmware can allocated
space for the block.
5499
Retry the operation.
5500
No action required.
5501
NVRAM cannot be used. It must be initialized
first. Firmware will attempt the initialization.
5502
Band NVRAM/ reinitialize.
5503
This can be caused by many conditions including
a bad complex profile, a bad hardware
configuration, a cell arriving late to the
rendezvous point. A cell not being able to
rendezvous. Reconfiguration from partition
manager is recommended.
5505
Verify communications with the utilities system.
5507
An error occurred which triggered system
firmware to cease making forward progress. The
CPU is put into a spin loop so that external
debugging can take place. See earlier event ids
to help determine the cause of the error. Also note
that theError Response Mode is likely to have
directed firmware to HALT.
5509
DUI was entered before the console is available.
DUI will exit and processing will continue.
5510
Decode the ASCII message and correct the
problem.
5511
Delay the request for reconfiguration until after
the PD has been released from Sinc BIB.
5514
Fabric wasn't able to route to all cells described
in the complex profile correctly due to a hardware
problem. Some of the cells are unreachable.
Update the complex profile or correct the
hardware problem.
5515
Remove the I/O cards below the specified
PCI-to-PCI bridge.
Unsupported I/O configuration.
5518
Debugging event, not for release.
5521
Platform Events – Table 2 (Windows System Log Event ID, Cause, Recommended Action)
75