HP ML350 HP ProLiant Servers Troubleshooting Guide - Page 119

Audible Beeps, Possible Cause, Action, Description

Page 119 highlights

Network Server Mode Active and No Keyboard Attached Audible Beeps: None Possible Cause: A keyboard is not connected. An error has not occurred, but a message is displayed to indicate the keyboard status. Action: No action is required. NMI - Button Pressed! Audible Beeps: None Possible Cause: The NMI button was pressed, initiating a memory dump for crash dump analysis. Action: Reboot the server. NMI - Undetermined Source Audible Beeps: None Possible Cause: An NMI event has occurred. Action: Reboot the server. Node Interleaving disabled - Invalid memory configuration Description: Each node must have the same memory configuration to enable interleaving. Action: Populate each node with the same memory configuration and enable interleaving in RBSU. No Floppy Drive Present Audible Beeps: None Possible Cause: No diskette drive is installed or a diskette drive failure has occurred. Action: 1. Power down the server. 2. Replace a failed diskette drive. 3. Be sure a diskette drive is cabled properly, if a diskette drive exists. No Keyboard Present Audible Beeps: None Possible Cause: A keyboard is not connected to the server or a keyboard failure has occurred. Action: 1. Power down the server, and then reconnect the keyboard. 2. Be sure no keys are depressed or stuck. 3. If the failure reoccurs, replace the keyboard. Error messages 119

  • 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
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188

Network Server Mode Active and No Keyboard Attached
Audible Beeps
: None
Possible Cause
: A keyboard is not connected. An error has not occurred, but a message is displayed to
status.
NMI - Button Pressed!
emory dump for crash dump analysis.
oot the server.
Audible Beeps
: None
Possible Cause
: An NMI event has occurred.
Action
: Reboot the server.
ode I
alid memory configuration
ach node must have the same memory configuration to enable interleaving.
the same memory configuration and enable interleaving in RBSU.
No Flo
Possible Cause
: No diskette drive is installed or a diskette drive failure has occurred.
diskette drive.
abled properly, if a diskette drive exists.
No Key
rred.
, and then reconnect the keyboard.
re depressed or stuck.
indicate the keyboard
Action
: No action is required.
Audible Beeps
: None
Possible Cause
: The NMI button was pressed, initiating a m
Action
: Reb
NMI - Undetermined Source
N
nterleaving disabled - Inv
Description
: E
Action
: Populate each node with
ppy Drive Present
Audible Beeps
: None
Action
:
1.
Power down the server.
2.
Replace a failed
3.
Be sure a diskette drive is c
board Present
Audible Beeps
: None
Possible Cause
: A keyboard is not connected to the server or a keyboard failure has occu
Action
:
1.
Power down the server
2.
Be sure no keys a
3.
If the failure reoccurs, replace the keyboard.
Error messages 119