HP NetServer AA 4000 HP NetServer AA 6200 Solution Release 3.0 Administrator&a - Page 20

Table 1-1, Continued, HP NetServer AA Server Benefits

Page 20 highlights

Chapter 1 Introduction Table 1-1 HP NetServer AA Server Benefits (Continued) Benefit Automatic reconfiguration Local and remote management Event reporting Online repair Description When a fault condition occurs, or after that fault is corrected and the failed component is returned to service, the server automatically reconfigures and, if needed, synchronizes the components affected by the fault. This can include CPU processing, including CPU memory; the server's operating system and associated applications; and any system data, including data stored on mirrored devices. The redundancy of the components in the server is transparently restored after most failures. The server includes a complete server management tool, the Endurance Manager. This tool has a GUI from which you can monitor and configure your server. You can use Endurance Manager locally or at a remote Windows NT server. Note: Most detected events and failures are reported and logged into the Windows NT event log. This enables log entries to be viewed locally or remotely using standard Windows NT procedures. Events are easily identified because they have a unique identifier. Because standard event reporting is implemented, you can integrate standard third-party alarm notification applications to help manage your server. Note: Other detected events are displayed in Windows NT blue screens, in pop-up windows, or in a window on the Endurance Manager as they occur. For complete documentation of messages, refer to the online book HP NetServer AA Solution Messages. You can repair and replace many hardware components while the server remains online and operational. 4

  • 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

Chapter 1
Introduction
4
Automatic reconfiguration
When a fault condition occurs, or after that fault is corrected and the failed
component is returned to service, the server automatically reconfigures
and, if needed, synchronizes the components affected by the fault. This
can include CPU processing, including CPU memory; the server
s
operating system and associated applications; and any system data,
including data stored on mirrored devices. The redundancy of the
components in the server is transparently restored after most failures.
Local and remote management
The server includes a complete server management tool, the Endurance
Manager. This tool has a GUI from which you can monitor and configure
your server. You can use Endurance Manager locally or at a remote
Windows NT server.
Event reporting
Note: Most detected events and failures are reported and logged into the
Windows NT event log. This enables log entries to be viewed locally
or remotely using standard Windows NT procedures.
Events are
easily identified because they have a unique identifier. Because
standard event reporting is implemented, you can integrate standard
third-party alarm notification applications to help manage your
server.
Note: Other detected events are displayed in Windows NT blue screens, in
pop-up windows, or in a window on the Endurance Manager as they
occur. For complete documentation of
messages, refer to the online
book
HP NetServer AA Solution Messages
.
Online repair
You can repair and replace many hardware components while the server
remains online and operational.
Table 1-1
HP NetServer AA Server Benefits
(Continued)
Benefit
Description