Compaq ProLiant 1000 ProLiant Server Troubleshooting Guide - Page 131

Initiating Diagnostics

Page 131 highlights

Error Recovery Initiating Diagnostics Initiating Diagnostics is only supported on systems that use the System Configuration Utility. When a critical error occurs and you have enabled ASR-2 to initiate Diagnostics, the operating system-specific Health Driver logs critical error information in the IML, and ASR-2 restarts the server. When the system reinitializes, ASR-2 starts Diagnostics from the hard drive. If Dial-In status is enabled, the modem is placed in auto-answer mode. If you enable Dial-Out status, you are automatically enabled for Dial-In status. If Network Status is enabled, the appropriate network support software (IP or IPX, depending on the network protocol) is loaded. This software allows remote access through the network. IMPORTANT: Diagnostics are loaded from a specially created system partition on the hard drive. This partition was configured during server configuration. You can access the server and view the Server Health Logs: • In servers not supporting the IML • Remotely by non-PCI modem • In-band over the network • Directly from the server For modem access, you must have either Insight Manager 2.0 or later, or have a VT100 or ANSI terminal-type device. You can use a standard CRT with VT100 or ANSI emulation capability, or you can use a personal computer (PC) with a VT100 or ANSI terminal emulation package. The communication parameters must be set for 8-data bits, no parity, and 1-stop bit. You can also enable ASR-2 to allow network access by using the Network Status feature in the System Configuration Utility. You must have either Insight Manager 2.0 or later or a Novell Virtual Terminal (NVT) emulator on an IPX network to use this feature. You must also have version 2.24 or later of the System Configuration Utility. For IP access, you must have either Insight Manager 2.10 or later, or a Telnet Terminal Emulator to use this feature. You also must have version 2.24 or later of the System Configuration Utility. 5-10 HP Servers Troubleshooting 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
  • 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
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307

Error Recovery
5-10
HP Servers Troubleshooting Guide
Initiating Diagnostics
Initiating Diagnostics is only supported on systems that use the System Configuration
Utility. When a critical error occurs and you have enabled ASR-2 to initiate
Diagnostics, the operating system-specific Health Driver logs critical error
information in the IML, and ASR-2 restarts the server. When the system reinitializes,
ASR-2 starts Diagnostics from the hard drive.
If Dial-In status is enabled, the modem is placed in auto-answer mode. If you enable
Dial-Out status, you are automatically enabled for Dial-In status.
If Network Status is enabled, the appropriate network support software (IP or IPX,
depending on the network protocol) is loaded. This software allows remote access
through the network.
IMPORTANT:
Diagnostics are loaded from a specially created system partition on the hard
drive. This partition was configured during server configuration.
You can access the server and view the Server Health Logs:
In servers not supporting the IML
Remotely by non-PCI modem
In-band over the network
Directly from the server
For modem access, you must have either Insight Manager 2.0 or later, or have a
VT100 or ANSI terminal-type device. You can use a standard CRT with VT100 or
ANSI emulation capability, or you can use a personal computer (PC) with a VT100
or ANSI terminal emulation package. The communication parameters must be set for
8-data bits, no parity, and 1-stop bit.
You can also enable ASR-2 to allow network access by using the Network Status
feature in the System Configuration Utility. You must have either Insight
Manager 2.0 or later or a Novell Virtual Terminal (NVT) emulator on an IPX
network to use this feature. You must also have version 2.24 or later of the System
Configuration Utility. For IP access, you must have either Insight Manager 2.10 or
later, or a Telnet Terminal Emulator to use this feature. You also must have
version 2.24 or later of the System Configuration Utility.