Compaq BL10e HP ProLiant BL e-Class System Setup and Installation Guide - Page 116

When the Server Blade Does Not Start, Diagnostic Adapter LEDs in Appendix E

Page 116 highlights

Troubleshooting When the Server Blade Does Not Start This section provides systematic instructions on what to try and where to go for help for the most common problems encountered during initial POST of a ProLiant BL e-Class server blade. The server blade must first complete this test each time you power up, before it can load the operating system and start running software applications. If you have the same problem with several server blades, you may have an enclosure problem. See "When the Enclosure Does Not Start" section in this appendix. If the server blade does not start: 1. If the server blade is rebooting repeatedly, be sure that the server blade is not rebooting due to a problem that initiates an ASR-2 reboot. You can enable ASR-2 to reboot the server blade. Should a critical error occur, ASR-2 logs the error in the IML and restarts the server blade. - Refer to the HP Servers Troubleshooting Guide on the Documentation CD that ships with the enclosure for other continuous rebooting problems. 2. Restart the server blade. IMPORTANT: If the server blade does not restart, proceed to Table D-9 of the "Server Blade Diagnostic Steps" section in this appendix. 3. Check the server blade for the normal power up sequence. Do this by checking that the sever blade health LED turns to solid green. For location and function of the sever blade health LED, see the "Server Blade and Diagnostic Adapter LEDs" section in Appendix E, "LEDs and Switches." 4. Check the monitor (installed to the server blade using the diagnostic adapter) for the following messages that ensure that the ProLiant BL e-Class ever blade meets the minimal hardware requirements and is powered up during normal operations: - ProLiant logo - Memory test - ROM information - Copyright information D-14 HP ProLiant BL e-Class System Setup and Installation Guide

  • 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
  • 152
  • 153
  • 154
  • 155
  • 156

Troubleshooting
When the Server Blade Does Not Start
This section provides systematic instructions on what to try and where to go for help
for the most common problems encountered during initial POST of a ProLiant BL
e-Class server blade. The server blade must first complete this test each time you
power up, before it can load the operating system and start running software
applications.
If you have the same problem with several server blades, you may have an enclosure
problem. See “When the Enclosure Does Not Start” section in this appendix.
If the server blade does not start:
1.
If the server blade is rebooting repeatedly, be sure that the server blade is not
rebooting due to a problem that initiates an ASR-2 reboot.
You can enable ASR-2 to reboot the server blade. Should a critical error occur,
ASR-2 logs the error in the IML and restarts the server blade.
— Refer to the
HP Servers Troubleshooting Guide
on the Documentation CD
that ships with the enclosure for other continuous rebooting problems.
2.
Restart the server blade.
IMPORTANT:
If the server blade does not restart, proceed to Table D-9 of the “Server
Blade Diagnostic Steps” section in this appendix.
3.
Check the server blade for the normal power up sequence.
Do this by checking that the sever blade health LED turns to solid green. For
location and function of the sever blade health LED, see the “Server Blade and
Diagnostic Adapter LEDs” section in Appendix E, “LEDs and Switches.”
4.
Check the monitor (installed to the server blade using the diagnostic adapter) for
the following messages that ensure that the ProLiant BL e-Class ever blade meets
the minimal hardware requirements and is powered up during normal operations:
— ProLiant logo
— Memory test
— ROM information
— Copyright information
D-14
HP ProLiant BL e-Class System Setup and Installation Guide