HPE ProLiant Gen9 Troubleshooting Manual
  1. Manuals
  2. Brands
  3. HPE Manuals
  4. Server
  5. ProLiant Gen9
  6. Troubleshooting manual

HPE ProLiant Gen9 Troubleshooting Manual

Hide thumbs Also See for ProLiant Gen9:
1
2
Table Of Contents
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
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
Table of Contents

Advertisement

Quick Links

See also: User Manual
HPE ProLiant Gen9 Troubleshooting Guide
Volume II: Error Messages
Abstract
This guide provides a list of error messages associated with HPE ProLiant servers, Integrated
Lights-Out, Smart Array storage, Onboard Administrator, Virtual Connect, ROM, and Configuration
Replication Utility. This document is intended for the person who installs, administers, and
troubleshoots servers or server blades. Hewlett Packard Enterprise assumes you are qualified in
the servicing of computer equipment and trained in recognizing hazards in products with
hazardous energy levels.
Part Number: 795673-005
Published: January 2018
Edition: 6

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the ProLiant Gen9 and is the answer not in the manual?

Questions and answers

Related Manuals for HPE ProLiant Gen9

Summary of Contents for HPE ProLiant Gen9

  • Page 1 Volume II: Error Messages Abstract This guide provides a list of error messages associated with HPE ProLiant servers, Integrated Lights-Out, Smart Array storage, Onboard Administrator, Virtual Connect, ROM, and Configuration Replication Utility. This document is intended for the person who installs, administers, and troubleshoots servers or server blades.
  • Page 2 © Copyright 2012, 2018 Hewlett Packard Enterprise Development LP Notices The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services.

  • Page 3: Table Of Contents

    Contents Introduction....................6 Overview..............................6 Troubleshooting resources........................6 HPE ProLiant server errors.................7 Array Diagnostics error messages...................... 7 HPE Smart Storage Administrator Diagnostics Utility error messages........7 POST error messages........................35 Introduction to POST error messages..................35 100 Series..........................36 200 Series..........................38 300 Series..........................69 400 Series..........................103 500 Series..........................103...
  • Page 4 Message identifiers 24725-24749..................206 Message identifiers 24750-24774..................210 Message identifiers 24775-24799..................215 Message identifiers 24800-24808..................222 Smart Array Windows driver errors....................223 HPE Onboard Administrator errors............225 Onboard Administrator error messages..................225 SysLog messages........................... 239 Alertmail log messages......................239 Authentication and startup log messages................240 CGI log messages........................ 241 CLI log messages.........................
  • Page 5 CONREP screen output........................301 HPE iLO messages, traps, and errors........... 302 iLO POST LED indicators........................302 Event log entries..........................302 RIBCL messages..........................311 HPE Insight Management Agents for Servers for Windows....319 Event log messages associated with SNMP traps................319 ® Windows NT event log format......................319 Agent descriptions...........................

  • Page 6: Introduction

    Introduction Overview This guide is part of a two-volume set. HPE ProLiant Gen9 Troubleshooting Guide, Volume I: Troubleshooting provides procedures for resolving common issues. This guide, HPE ProLiant Gen9 Troubleshooting Guide, Volume II: Error Messages, provides a list of error messages and information to assist with interpreting and resolving error messages on ProLiant servers and server blades.

  • Page 7: Hpe Proliant Server Errors

    Array Diagnostics error messages HPE Smart Storage Administrator Diagnostics Utility error messages This section contains a complete alphabetical list of all error messages presented by the HPE Smart Storage Administrator Diagnostics Utility in the Array Diagnostics Report. Array status: The array has failed Symptom Array status: The array has failed.
  • Page 8 Action Replace the spare drive with a drive that is at least the size of the smallest data drive in the array. For more information, see the product maintenance and service guide on the Hewlett Packard Enterprise website. Cache module: The cache for this controller is temporarily disabled since a snapshot is in progress Symptom Cache module: The cache for this controller is temporarily disabled since a snapshot is in progress.
  • Page 9 For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website. Cache module: The cache is disabled because a flash memory or capacitor hardware failure has been detected Symptom Cache module: The cache is disabled because a flash memory or capacitor hardware failure has been detected.
  • Page 10 For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website. Cache module: The cache is disabled because the batteries are low Symptom Cache module: The cache is disabled because the batteries are low. Cause The batteries are not charged. Action Replace the batteries if the batteries do not recharge within 36 powered-on hours.

  • Page 11: Cache Module

    Action 1. Update the controller to the latest firmware. For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. If the issue persists, contact Hewlett Packard Enterprise support.
  • Page 12 Action Obtain the latest version of HPE SSA. For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. Controller State: The array controller contains a volume that was created with a different...
  • Page 13 Action 1. Identify the drives that contain the lost logical volumes. 2. Do one of the following: • Move the drives to another controller where the logical volumes can be recreated. • If a drive contains a valid logical volume that is in use and a lost logical volume, then do not move that drive to another controller.
  • Page 14 c. If the issue persists, power down the and move the drives back to the original controller. d. If the issue persists, contact Hewlett Packard Enterprise support. Controller State: The array controller contains redundant connections to one or more physical drives that are not supported in the current configuration Symptom Controller State: The array controller contains redundant connections to one or more physical drives that are not supported in the current configuration.
  • Page 15 a. Upgrade the firmware on this controller. b. Make sure that the cache module is installed. Install the cache module if not present. c. If the issue persists, power down the and move the drives back to the original controller. Solution 2 Action 1.
  • Page 16 a. Upgrade the firmware on this controller. b. Make sure that the cache module is installed. Install the cache module if not present. c. If the issue persists, power down the and move the drives back to the original controller. Solution 2 Action 1.
  • Page 17 For more information, see the user guide on the Hewlett Packard Enterprise website. Controller State: The array controller is operating without a memory board and has a bad volume position Symptom Controller State: The array controller is operating without a memory board and has a bad volume position. Any configuration command (e.g.
  • Page 18 The HBA does not have an access ID. Action 1. Upgrade the HBA. For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. If the issue persists, contact Hewlett Packard Enterprise support.
  • Page 19 SSA. Cause The erase process has failed. Action Re-enable the physical drive using HPE SSA. Drive Offline due to Erase Operation: The physical drive is currently queued for erase...
  • Page 20 For more information, see the HPE Smart Storage Administrator User Guide on the Hewlett Packard Enterprise website. Drive Offline due to Erase Operation: The physical drive is offline and the erase process has completed Symptom Drive Offline due to Erase Operation: The physical drive is offline and the erase process has completed. The drive may now be brought online through the re-enable erased drive command in SSA.
  • Page 21 For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. Solution 2 Cause An issue exists with the controller, as specified on the diagnostic report. Action 1. Reboot the server.
  • Page 22 For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. Logical drive state: Background parity initialization is currently queued Symptom Logical drive state: Background parity initialization is currently queued or in progress on this logical drive. If background parity initialization is queued, it will start when I/O is performed on the drive.
  • Page 23 A logical drive is not configured. Action Refresh the system using the HPE SSA. For more information, see the HPE Smart Storage Administrator User Guide on the Hewlett Packard Enterprise website. Logical drive state: The logical drive is not yet available Symptom Logical drive state: The logical drive is not yet available.
  • Page 24 A logical drive has a high physical drive count and a high stripe size value that can lead to a controller lockup. Action Migrate the stripe size to a lower value using the HPE SSA. For more information, see the HPE Smart Storage Administrator User Guide on the Hewlett Packard Enterprise website. NVRAM Error: Board ID could not be read Symptom NVRAM Error: Board ID could not be read (Read-Only Table failed checksum test).
  • Page 25 Action 1. Update the controller firmware. For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. If the update does not complete, contact Hewlett Packard Enterprise support.
  • Page 26 Action 1. If this drive is part of a non-fault-tolerant configuration: a. Back up all data on the drive. b. Replace the drive. c. Restore all data to the new drive. Solution 2 Action 1. If this drive is part of a fault-tolerant configuration: a.
  • Page 27 Action Replace the physical drive with a drive supported by the controller. To locate a supported option, review the product QuickSpecs on the Hewlett Packard Enterprise website. Physical Drive State: The data on the physical drive is being rebuilt Symptom Physical Drive State: The data on the physical drive is being rebuilt.
  • Page 28 Action Replace the physical drive with a drive supported by the controller. To locate a supported option, review the product QuickSpecs on the Hewlett Packard Enterprise website. Physical Drive State: This drive is not supported for configuration Symptom Physical Drive State: This drive is not supported for configuration and should be disconnected from this controller.
  • Page 29 Action Replace the physical drive with a drive supported by the controller. To locate a supported option, review the product QuickSpecs on the Hewlett Packard Enterprise website. Physical Drive State: This physical drive is part of a logical drive that is not supported by the current configuration Symptom Physical Drive State: This physical drive is part of a logical drive that is not supported by the current...
  • Page 30 Action No action is required. Redundancy State: This controller has been setup to be part of a redundant pair of controllers Symptom Redundancy State: This controller has been setup to be part of a redundant pair of controllers but redundancy is disabled.
  • Page 31 Action Check the storage box I/O module and cables to restore redundant paths to the logical drive. Redundant Path Failure: The physical drive is degraded due to the loss of a redundant path Symptom Redundant Path Failure: The physical drive is degraded due to the loss of a redundant path. Cause •...
  • Page 32 Action Monitor the drive frequently and replace the drive before wearout. Smart SSD State: SSD has less than 2% of usage remaining before wearout Symptom Smart SSD State: SSD has less than 2% of usage remaining before wearout. It has less than an estimated 56 days before it reaches the maximum usage limit and should be replaced as soon as possible.
  • Page 33 For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website. Smart SSD State: SSD has less than an estimated 56 days before it reaches the maximum usage limit for writes (wearout) Symptom Smart SSD State: SSD has less than an estimated 56 days before it reaches the maximum usage limit for writes (wearout) and should be replaced as soon as possible.
  • Page 34 For more information, see the maintenance and service guide for your product on the Hewlett Packard Enterprise website. Storage Enclosure: One or more fans have failed Symptom Storage Enclosure: One or more fans have failed. Cause One or more fans have failed. Action Replace the fan.

  • Page 35: Post Error Messages

    Cause • The power supply is not seated correctly. • The power cable is not connected correctly. • The power supply has failed. Action 1. Reseat the power supply. 2. Make sure that the power cable is connected correctly. 3. If the issue persists, replace the power supply. For more information, see the maintenance and service guide for your product on the Hewlett Packard Enterprise website.

  • Page 36: 100 Series

    WARNING: To avoid potential issues, ALWAYS read the warnings and cautionary information in the product documentation before removing, replacing, reseating, or modifying system components. IMPORTANT: This guide provides information for multiple servers. Some information may not apply to the server you are troubleshooting.
  • Page 37 1. Press the F1 key to enter UEFI System Utilities. 2. Run the server setup utility to change the configuration. For more information, see "UEFI System Utilities" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website.

  • Page 38: Series

    For more information, see "UEFI System Utilities" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 200 Series 207-DIMM configuration errors Symptom 207-DIMM configuration errors. Cause An Advanced Memory Protection DIMM configuration error occurred.
  • Page 39 Action 1. Make sure the processor is correctly installed and seated. For more information, see "Processor issues" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. If the issue persists, make sure that the processor socket is not contaminated.
  • Page 40 Action Make sure the processor is correctly installed and seated. For more information, see "Processor issues" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 217-Processor cannot cache all installed memory...
  • Page 41 Action Check the video output or the Integrated Management Log for additional information. For more information, see "Integrated Management Log" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 224-Power fault detected – FlexLOM X Symptom 224-Power fault detected –...
  • Page 42 • For non-blade or non-SL-series server, unplug the server. • For blades or SL-series servers, remove the server. 3. Locate and reseat the indicated FlexibleLOM. For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website. 225-Power fault detected –...
  • Page 43 CAUTION: Before removing or replacing any processors, be sure to follow the processor troubleshooting guidelines in "Performing Processor Procedures in the Troubleshooting Process" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I: Troubleshooting. Failure to follow the recommended guidelines can cause damage to the system board, requiring replacement of the system board.
  • Page 44 For more information, see the user guide on the Hewlett Packard Enterprise website. 230-DIMM Configuration Error – Processor X, Channel Y Symptom 230-DIMM Configuration Error – Processor X, Channel Y – Only 2 DIMMs can be installed on a channel containing Quad-Rank DIMM(s). –...
  • Page 45 For more information, see the user guide on the Hewlett Packard Enterprise website. 232-Memory initialization error – Processor A, DIMM B failed Symptom 232-Memory initialization error – Processor A, DIMM B failed. Cause Installed DIMMs did not pass the memory test. Action Replace the DIMMs.
  • Page 46 CAUTION: Before removing or replacing any processors, be sure to follow the processor troubleshooting guidelines in "Performing Processor Procedures in the Troubleshooting Process" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I: Troubleshooting. Failure to follow the recommended guidelines can cause damage to the system board, requiring replacement of the system board.
  • Page 47 238-DIMM Configuration Error – Processor X, DIMM Y Symptom 238-DIMM Configuration Error – Processor X, DIMM Y – Quad Rank DIMMs must be installed in the first socket of any memory channel in which they are populated. – System Halted! Cause Quad-rank DIMMs are installed on the memory channel after SR or DR DIMMs.
  • Page 48 CAUTION: Before removing or replacing any processors, be sure to follow the processor troubleshooting guidelines in "Performing Processor Procedures in the Troubleshooting Process" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I: Troubleshooting. Failure to follow the recommended guidelines can cause damage to the system board, requiring replacement of the system board.
  • Page 49 For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website. 243-Unsupported Option Card configuration Symptom 243-Unsupported Option Card configuration. The option card installed in Slot X is not supported in that slot with the current server configuration. Action: Move the Option Card to a different slot. Cause The option card is installed in an unsupported configuration.
  • Page 50 The amount of available Option ROM space has been exceeded. Action Disable any unnecessary option ROMs (such as PXE). For more information, see "UEFI System Utilities" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 247-Memory Initialization Error Symptom 247-Memory Initialization Error –...
  • Page 51 248-Unsupported Option Card configuration. The option card installed in Slot X is only supported in Slot Y. Action: Move the option card from Slot X to Slot Y. Cause The option card is not supported in slot X. Action Remove the option card from Slot X and move it to Slot Y. For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website.
  • Page 52 For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website. 250-Unsupported Processor Configuration Detected Symptom 250-Unsupported Processor Configuration Detected. The installed processors are only supported in single processor configurations. Action: Remove Processor 2. Cause Two processors are installed in a configured for a single processor. Action Remove Processor 2.
  • Page 53 Action Verify that all installed processors have the same level of FlexCompute support. For more information, see the user guide on the Hewlett Packard Enterprise website. 253-IMPORTANT: The PCI-e Device installed in Slot X has no corresponding processor installed and will not function Symptom 253-IMPORTANT: The PCI-e Device installed in Slot X has no corresponding processor installed and will not function.
  • Page 54 For more information, see the user guide on the Hewlett Packard Enterprise website. Solution 2 Action Install a license supported by the installed processors. For more information, see the user guide on the Hewlett Packard Enterprise website. 255-An attempt to increase the frequency or core count of a FlexCompute capable processor without installing the appropriate license has been detected Symptom 255-An attempt to increase the frequency or core count of a FlexCompute capable processor without...
  • Page 55 CAUTION: Before removing or replacing any processors, be sure to follow the processor troubleshooting guidelines in "Performing Processor Procedures in the Troubleshooting Process" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I: Troubleshooting. Failure to follow the recommended guidelines can cause damage to the system board, requiring replacement of the system board.
  • Page 56 Firmware Flash Component to update this firmware. Cause A firmware update is available. Action Update the firmware. For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 262-Redundant ROM Error Symptom 262-Redundant ROM Error: The Backup System ROM is invalid.
  • Page 57 Action Flash the System ROM to restore redundancy. For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 263-Redundant ROM Error Symptom 263-Redundant ROM Error: The Primary System ROM is invalid. The system is operating on the Backup System ROM.
  • Page 58 266-Non-Volatile Memory Corruption Detected. Configuration settings restored to defaults. If enabled, Secure Boot security settings may be lost. Action: Restore configuration settings. Contact support if issue persists. Cause An HPE ProLiant c-Class server blade was interrupted while writing to NVRAM by: • A sudden removal of power •...
  • Page 59 For more information, see the user guide on the Hewlett Packard Enterprise website. 3. If the issue persists, contact Hewlett Packard Enterprise support. For more information, see "Accessing Hewlett Packard Enterprise support." 269-IMPORTANT: Default configuration settings have been restored Symptom 269-IMPORTANT: Default configuration settings have been restored per user request.
  • Page 60 For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website. 2. Install DIMMs in a supported configuration. For a list of supported options, see the product QuickSpecs on the Hewlett Packard Enterprise website. 273-Unsupported Option Card Configuration Symptom 273-Unsupported Option Card Configuration.
  • Page 61 Action Confirm the system has firmware or software that supports Secure Boot and has not been compromised. For more information, see "Secure Boot Configuration" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 278-Secure Boot Authentication Failure Symptom 278- Secure Boot Authentication Failure.
  • Page 62 Action Update the software or firmware to a revision with a valid certificate. For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 279-Cable Error Symptom 279-Cable Error - An internal cable routed to the LED Board is not plugged in or plugged in incorrectly. Action: Plug in the internal cable correctly.
  • Page 63 Action Enter the correct values for these fields in BIOS/Platform Configuration (RBSU). For more information, see "Re-entering the server serial number and Product ID" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 283-Memory Address/Command Parity Error Detected Symptom 283-Memory Address/Command Parity Error Detected –...
  • Page 64 A DIMM has failed. Action Attempt to isolate the DIMM experiencing the error and replace it. For more information, see "General memory issues" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 285-DIMM Failure Symptom 285-DIMM Failure –...
  • Page 65 Action Attempt to isolate the DIMM experiencing the error and replace it. For more information, see "General memory issues" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 286-IMPORTANT: The removal of a storage device has been detected Symptom 286-IMPORTANT: The removal of a storage device has been detected.
  • Page 66 Action No action is required. 289-IMPORTANT: A new network or storage device has been Symptom 289-IMPORTANT: A new network or storage device has been detected. This device will not be shown in the Legacy BIOS Boot Order options in RBSU until the system has booted once. Cause A new network or storage device has been connected to the .
  • Page 67 Action 1. Check the hardware and software for issues. For more information, see "POST issues flowchart" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. If the issue persists, contact Hewlett Packard Enterprise support.
  • Page 68 For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website. 2. If the issue persists, contact Hewlett Packard Enterprise support. For more information, see "Accessing Hewlett Packard Enterprise support." 295-DIMM Failure – Memory Board X, DIMM Y Symptom 295-DIMM Failure –...

  • Page 69: 300 Series

    For more information, see the user guide on the Hewlett Packard Enterprise website. To locate a supported option, review the product QuickSpecs on the Hewlett Packard Enterprise website. 297-IMPORTANT: The iLO Security switch is set to the ON position Symptom 297-IMPORTANT: The iLO Security switch is set to the ON position.
  • Page 70 Action 1. Be sure that the keyboard is in working order. For more information, see "Mouse and keyboard issues" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. If the issue persists, replace the keyboard.
  • Page 71 For more information, see "Mouse and keyboard issues" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. If the issue persists, replace the keyboard. 303-Keyboard controller error Symptom 303-Keyboard controller error Cause •...
  • Page 72 Action 1. Flash the Primary and Backup System ROMs to the appropriate revisions. For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. If the fails to boot, perform the flash update via iLO.
  • Page 73 For more information, see the user guide on the Hewlett Packard Enterprise website. 2. If the issue persists, update the iLO firmware. For more information, see the user guide on the Hewlett Packard Enterprise website. 3. If the issue persists, contact Hewlett Packard Enterprise support. For more information, see "Accessing Hewlett Packard Enterprise support."...
  • Page 74 For more information, see the user guide on the Hewlett Packard Enterprise website. 310-IMPORTANT: Fan Solution Not Redundant Symptom 310- IMPORTANT: Fan Solution Not Redundant. The system does not have the minimum required operating fans for redundancy. Cause The number of fans installed in the does not meet minimum requirements for redundancy. Action Install additional fans if redundancy is required.
  • Page 75 Action 1. Verify that the battery is installed correctly. For more information, see "HPE Smart Storage Battery issues flowchart" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. If the issue persists, contact Hewlett Packard Enterprise support.
  • Page 76 The chassis firmware needs to be updated. Action Update the chassis firmware. For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website.
  • Page 77 For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 318-Trusted Platform Module (TPM) Self-Test Error Symptom 318-Trusted Platform Module (TPM) Self-Test Error. Cause • The TPM is unavailable to the .
  • Page 78 • "Using Onboard Administrator for remote troubleshooting of server blades" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. • HPE BladeSystem c-Class Enclosure Troubleshooting Guide on the Hewlett Packard Enterprise website. 321-HP Dual microSD Device Unsupported Configuration Symptom 321-HP Dual microSD Device Unsupported Configuration –...
  • Page 79 Action Enter System Utilities and configure the primary microSD card using the System Configuration options. For more information, see "UEFI System Utilities" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 326-HP Dual microSD Device Error Symptom 326-HP Dual microSD Device Error –...
  • Page 80 The power management controller firmware needs to be updated. Action Update the power management controller firmware. For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 329-Power Management Controller FW Error Symptom 329-Power Management Controller FW Error –...
  • Page 81 2. If the issue persists, reset the power management controller firmware by removing AC power. 3. If the issue persists, update the power management controller firmware. For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website.
  • Page 82 Modified, or 401-Unauthorized) as a response to a GET request from the BIOS. Action Restore Manufacturing Defaults in RBSU. For more information, see "UEFI System Utilities" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 335-HP RESTful API Error Symptom 335-HP RESTful API Error –...
  • Page 83 Action 1. Reset the RESTful API. 2. If the issue persists, reset the iLO API. For more information, see Managing Hewlett Packard Enterprise Servers Using the RESTful API on the Hewlett Packard Enterprise website. 336-HP RESTful API Error Symptom 336-HP RESTful API Error – One or more configuration settings could not be applied. Cause The BIOS configuration change was consumed through the RESTful API and one or more of the requested changes resulted in an error.
  • Page 84 For more information, see "UEFI System Utilities" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 340-NVDIMM Error – Backup Error Symptom Persistent data backup failed and data is not available. Action: Replace NVDIMM if error persists.
  • Page 85 Action 1. Be sure that the Smart Storage battery is installed and functioning. For more information, see "HPE Smart Storage Battery issues flowchart" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. Reseat the NVDIMM.
  • Page 86 2. Replace the NVDIMM. 3. Sanitize the new NVDIMM. 4. Copy the preserved data to the new NVDIMM. For more information, see the HPE 8GB NVDIMM User Guide on the Hewlett Packard Enterprise website. 346-NVDIMM Error – Arming Error Symptom 346-NVDIMM Error –...
  • Page 87 For more information, see the HPE 8GB NVDIMM User Guide on the Hewlett Packard Enterprise website. 347-NVDIMM Population Error Symptom 347-NVDIMM Population Error – X NVDIMMs are present in the system. Only Y NVDIMMs are supported. Action: Install a maximum of Y NVDIMMs in the system.
  • Page 88 NVDIMMs and RDIMMs are not installed in the correct order. Action Follow the population guidelines for installing DIMMs and NVDIMMs in a . For more information, see the HPE 8GB NVDIMM User Guide on the Hewlett Packard Enterprise website. 351-IMPORTANT: HPE Smart Storage Battery is not charged sufficiently Symptom 351-IMPORTANT: HPE Smart Storage Battery is not charged sufficiently to support the NVDIMMs installed in the system.
  • Page 89 352-IMPORTANT: HPE Smart Storage Battery is not charged sufficiently Symptom 352-IMPORTANT: HPE Smart Storage Battery is not charged sufficiently to support the NVDIMMs installed in the system. Action: System configured to not wait for battery to charge. NVDIMMs not armed to support backup.
  • Page 90 The NVDIMM was selected for sanitization and the was rebooted. Action No action is required. The reboots according to the Santitize/Erase on Next Reboot Policy settings. For more information, see the HPE 8GB NVDIMM User Guide on the Hewlett Packard Enterprise website. 356-NVDIMM Error – Sanitization Error Symptom 356-NVDIMM Error –...
  • Page 91 For more information, see the user guide on the Hewlett Packard Enterprise website. When HPE 8 GB NVDIMMs are installed in a , all regular DIMMs in the must be RDIMMs. For more information, see the HPE 8GB NVDIMM User Guide on the Hewlett Packard Enterprise website.
  • Page 92 Before removing or replacing any processors, be sure to follow the processor troubleshooting guidelines in "Performing Processor Procedures in the Troubleshooting Process" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I: Troubleshooting. Failure to follow the recommended guidelines can cause damage to the system board, requiring replacement of the system board.
  • Page 93 Cause The NVDIMM controller firmware is corrupt. Action Update the firmware. For more information, see "Firmware updates" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 365-Backplane Configuration Error Symptom 365-Backplane Configuration Error – A storage controller is installed in the incorrect drive backplane. The controller will not be usable.
  • Page 94 Solution 2 Action Sanitize all NVDIMMs on Processor X to begin using the NVDIMM in this . For more information, see the HPE 8GB NVDIMM User Guide on the Hewlett Packard Enterprise website. 372-NVDIMM Error – Processor X, DIMM Y Symptom 372-NVDIMM Error –...
  • Page 95 For more information, see the HPE 8GB NVDIMM User Guide on the Hewlett Packard Enterprise website. 373-NVDIMM Error Symptom 373-NVDIMM Error – NVDIMM(s) have been removed from Processor X. All NVDIMMs on Processor X have been disabled. Action: Re-install missing NVDIMM or sanitize all NVDIMMs on Processor X.
  • Page 96 2. Sanitize the NVDIMM. 3. If the error persists, replace the NVDIMM. For more information, see the HPE 8GB NVDIMM User Guide on the Hewlett Packard Enterprise website. For removal and replacement procedures, see the maintenance and service guide on the Hewlett Packard Enterprise website.
  • Page 97 For more information, see the HPE 8GB NVDIMM User Guide on the Hewlett Packard Enterprise website. 377-NVDIMM Error – Processor X, DIMM Y Symptom 377-NVDIMM Error – Processor X, DIMM Y. NVDIMM set for interleaving enabled but system configured for interleaving disabled.
  • Page 98 The NVDIMM was moved or installed in the wrong location, and NVDIMM-N Memory Interleaving is enabled. Action Install the NVDIMM in Processor A, DIMM B to preserve data. For more information, see the HPE 8GB NVDIMM User Guide on the Hewlett Packard Enterprise website. Solution 2 Action Sanitize all NVDIMMs on Processor X.
  • Page 99 The NVDIMM was moved or installed in the wrong location, and NVDIMM-N Memory Interleaving is disabled. Action Install the NVDIMM in Processor A, DIMM B to preserve data. For more information, see the HPE 8GB NVDIMM User Guide on the Hewlett Packard Enterprise website. Solution 2 Action Sanitize the NVDIMM.
  • Page 100 QPI Snoop Configuration setting. Action Change the QPI Snoop Configuration setting to Cluster on Die. For more information, see the HPE 8GB NVDIMM User Guide on the Hewlett Packard Enterprise website. Solution 2 Action Sanitize all NVDIMMs on Processor X.
  • Page 101 The NVDIMM was previously installed in a that had Channel Interleaving enabled. The current has Channel Interleaving disabled. Action Disable Channel Interleaving in System Utilities. For more information, see the HPE 8GB NVDIMM User Guide on the Hewlett Packard Enterprise website. Solution 2 Action Sanitize all NVDIMMs on Processor X.
  • Page 102 For more information, see the HPE 8GB NVDIMM User Guide on the Hewlett Packard Enterprise website. 388-Memory Failure – Uncorrectable Memory Error Symptom 388-Memory Failure – Uncorrectable Memory Error – The failed memory module could not be determined. Action: Inspect the IML for another event that may indicate what memory module has failed.

  • Page 103: 400 Series

    Both external and internal ports are assigned to parallel port X. Action Run the server setup utility and correct the configuration. For more information, see "UEFI System Utilities" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 404-Parallel Port Address Conflict Detected Symptom 404-Parallel Port Address Conflict Detected.

  • Page 104: 1500 Series

    Action Move the PCI card to the correct slot. For more information, see the user guide on the Hewlett Packard Enterprise website. 1500 Series 1500-iLO 4 configuration is temporarily unavailable Symptom 1500-iLO 4 configuration is temporarily unavailable. Cause iLO is busy or unresponsive to the software that is running on the system. Action 1.

  • Page 105: 1600 Series

    To locate the system maintenance switch bank, see the user guide on the Hewlett Packard Enterprise website. 2. Use the iLO RBSU to enable and reset iLO. For more information, see the user guide on the Hewlett Packard Enterprise website. 1503-iLO 4 ROM-based Setup Utility is disabled Symptom 1503-iLO 4 ROM-based Setup Utility is disabled.
  • Page 106 Action Make sure that all required fans are installed correctly and spinning. For more information, see "Fan issues" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1611-CPU Zone Fan Assembly Failure Detected Symptom 1611-CPU Zone Fan Assembly Failure Detected.
  • Page 107 Action Make sure that all required fans are installed correctly and spinning. For more information, see "Fan issues" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1611-Fan X Failure Detected (Fan Zone CPU) Symptom 1611-Fan X Failure Detected (Fan Zone CPU).
  • Page 108 Action Make sure that all required fans are installed correctly and spinning. For more information, see "Fan issues" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1611-Fan X Not Present (Fan Zone I/O) Symptom 1611-Fan X Not Present (Fan Zone I/O).
  • Page 109 Action Replace the fan to provide redundancy, if applicable. For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website. 1611-Primary Fan Failure (Fan Zone System) Symptom 1611-Primary Fan Failure (Fan Zone System). Cause A required fan is missing or not spinning. Action Replace the fan.
  • Page 110 A redundant fan is missing or not spinning. Action Make sure that all required fans are installed correctly and spinning. For more information, see "Fan issues" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1616-Power Supply Configuration Failure Symptom 1616-Power Supply Configuration Failure –...

  • Page 111: Power Supply Failure

    • Install the power supply. • Replace the power supply. For more information, see "Power supply issues" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1625-Unsupported Power Supply Configuration Symptom 1625-Unsupported Power Supply Configuration – Unsupported Power Supply Mismatch. Action: Ensure the Power Supply configuration is valid.
  • Page 112 The current power supply is not sufficient to operate the . Action For more information, see "Insufficient power supply configuration" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1628-IMPORTANT: The system contains multiple types of power supplies Symptom 1628-IMPORTANT: The system contains multiple types of power supplies.

  • Page 113: 1700 Series

    Cause The HPE Smart Storage Battery has not been installed. Action Install and charge the HPE Smart Storage Battery. For more information, see the user guide on the Hewlett Packard Enterprise website. 1702-SCSI Cable Error Detected Symptom 1702-SCSI Cable Error Detected.
  • Page 114 1. Examine the cable connectors for bent pins. 2. Be sure all cable connections are secure. For more information, see "Resolving loose connections" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 3. If the issue persists, replace the cables.
  • Page 115 Action If this occurs when a particular application is loaded, check for an updated version of that application. For more information, see "Software issues" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1707-Slot X Drive Array Controller Symptom 1707-Slot X Drive Array Controller - Bootstrap NVRAM checksum invalid.
  • Page 116 1. Reboot the server. 2. If the issue persists, update the controller firmware. For more information, see "Firmware updates" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1709-One or more attached hard drives could not be authenticated Symptom 1709-One or more attached hard drives could not be authenticated as a genuine HP hard drive.
  • Page 117 The stripe size is too large for RAID 5 or 6 logical drives. Action Perform RAID migration to a smaller stripe size using HPE SSA. For more information, see the HPE Smart Storage Administrator User Guide on the Hewlett Packard Enterprise website. 1712-Slot X Drive Array – RAID 5 volume(s) present Symptom 1712-Slot X Drive Array –...
  • Page 118 Flash ROM is failing. The controller detects a checksum failure, but is unable to reprogram the backup ROM. Action 1. Update the controller to the latest firmware version. For more information, see "Firmware updates" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. If the issue persists, replace the controller.
  • Page 119 The controller has failed. Action 1. Update the firmware. For more information, see "Firmware updates" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. If the issue persists, replace the cache module. 3. If the issue persists, replace the controller.
  • Page 120 Action 1. Check the fans and be sure the air flows over the drive. For more information, see "Fan issues" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. Install the access panel, if removed.
  • Page 121 Action 1. Update the controller to the latest firmware version. For more information, see "Firmware updates" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. If the issue persists, replace the controller. For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website.
  • Page 122 The logical drive configuration has been updated automatically following physical drive position changes. Action Reassign spare drives using HPE SSA. This action is required only if there are inactive spare assignments. For more information, see the HPE Smart Storage Administrator User Guide on the Hewlett Packard Enterprise website.
  • Page 123 1728-Slot # Drive Array – Abnormal Shut-Down Detected with Write Cache Enabled. Cause The HPE Smart Storage Battery is not installed or is not connected correctly, but caching was enabled. Any data that might have been in the cache module memory has been lost due to the controller power loss.
  • Page 124 Action Run the server setup utility and correct the configuration. For more information, see "UEFI System Utilities" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1731-Fixed Disk 1 Does Not Support DMA Mode Symptom 1731-Fixed Disk 1 does not support DMA Mode.
  • Page 125 Action 1. Be sure that the battery is connected and functioning. For more information, see "HPE Smart Storage Battery issues flowchart" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. Replace the HPE Smart Storage battery.
  • Page 126 Action Request a new system board and TPM board from an authorized service provider. For more information, see "HPE Trusted Platform Module issues" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1737-Slot X Drive Array – Redundant Cabling Configuration has excess Device Paths Symptom 1737-Slot X Drive Array –...
  • Page 127 For more information, see the user guide on the Hewlett Packard Enterprise website. • Update the firmware. For more information, see "Firmware updates" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1738-Slot # Drive Array – Storage Enclosure Redundant Cabling Problem Detected Symptom 1738-Slot # Drive Array –...
  • Page 128 Action Run the server setup utility and correct the configuration. For more information, see "UEFI System Utilities" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1741-Fixed Disk 1 failed set Block Mode Symptom 1741-Fixed Disk 1 failed set Block Mode.
  • Page 129 Solution 3 Action To re-enable the drives, use HPE SSA. For more information, see the HPE Smart Storage Administrator User Guide on the Hewlett Packard Enterprise website. 1743-Slot # Drive Array – Logical Drive Erase Operation in Progress Symptom 1743-Slot # Drive Array –...
  • Page 130 For more information, see the HPE Smart Storage Administrator User Guide on the Hewlett Packard Enterprise website. 1743-Slot # Drive Array – Logical Drive Erase Operation(s) are Queued Symptom 1743-Slot # Drive Array – Logical Drive Erase Operation(s) are Queued. Logical drives will temporarily go offline while being erased.
  • Page 131 1. Replace each drive in the list or re-enable each drive in the list using one of the following methods: • Use HPE SSA. For more information, see the HPE Smart Storage Administrator User Guide on the Hewlett Packard Enterprise website. •...
  • Page 132 3. Run HPE SSA to discard the current array and create a new configuration. For more information, see the HPE Smart Storage Administrator User Guide on the Hewlett Packard Enterprise website. 4. If access to specific drives has been disabled, do one of the following: •...
  • Page 133 A fixed drive error was detected. Action Run the server setup utility and correct the configuration. For more information, see "UEFI System Utilities" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1751-Fixed Disk 1 failed ID command Symptom 1751-Fixed Disk 1 failed ID command.
  • Page 134 Cause An unsupported controller is installed. Action Replace the Smart Array controller with a supported model. For a list of supported options, see the product QuickSpecs on the Hewlett Packard Enterprise website. 1753-Slot X Drive Array – Array Controller Maximum Operating Temperature Exceeded Symptom 1753-Slot X Drive Array –...
  • Page 135 The current controller firmware does not support the attached cache module type. Action 1. Update the firmware. For more information, see "Firmware updates" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 2. If the issue persists, replace the cache module.
  • Page 136 The System ROM is not the latest version. Action Run the FWUPDATE utility. For more information, see "FWUPDATE utility" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1768-Slot X Drive Array – Resuming logical drive expansion process Symptom 1768-Slot X Drive Array –...
  • Page 137 Expansion Progress Data Could Not Be Read From Cache Module. Verify that the cache module is seated correctly. Replace if necessary. • Expansion Aborted due to Unrecoverable Drive Errors. Verify failed disks using HPE SSA and replace as necessary. •...
  • Page 138 Action Update all drives to the latest firmware version. For more information, see "Firmware updates" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1774-Slot X Drive Array – Obsolete data found in Cache Module Symptom 1774-Slot X Drive Array –...
  • Page 139 Action Remove internal and external storage connections from any ports with both connected. For cable configuration information, see the controller documentation. 1777-Slot X Drive Array – Storage Enclosure Problem Detected Symptom 1777-Slot X Drive Array – Storage Enclosure Problem Detected (followed by one or more of the following): •...
  • Page 140 Link Errors Detected by Expander 1. Reseat the I/O modules. 2. Reseat the I/O module cables. 3. Replace the cables, if damaged. 4. If the issue persists, replace the I/O modules. Incorrect Bay Information Received from Enclosure HPE ProLiant server errors...
  • Page 141 1. Reseat the I/O modules. 2. Reseat the I/O module cables. 3. Replace the cables, if damaged. 4. If the issue persists, replace the I/O modules. Installed drives not detected, only I/O module 2 present 1. Reseat the I/O modules. 2.

  • Page 142: Slot X Drive Array Controller Failure

    Procedure 1. Do one of the following: • Press the F1 key to continue with logical drives disabled. • Press the F2 key to accept data loss and re-enable logical drives. 2. Resolve any issues that disabled the drive. 3. If the drive is replaced, restore data from the backup. Be sure the system is always powered up and down correctly: •...
  • Page 143 2. Be sure all drives are fully seated. 3. Determine which drive is defective using HPE SSA. Then, replace the defective cables, drive, or both. For more information, see the HPE Smart Storage Administrator User Guide on the Hewlett Packard Enterprise website.
  • Page 144 2. Be sure all drives are fully seated. 3. Determine which drive is defective using HPE SSA. Then, replace the defective cables, drive, or both. For more information, see the HPE Smart Storage Administrator User Guide on the Hewlett Packard Enterprise website.
  • Page 145 Action 1. Do one of the following: • Press the F1 key to continue with recovery of data to the drive. Data will be automatically restored to the drive when a failed drive has been replaced, or to the original drive if it is working again without errors.

  • Page 146: Slot X Drive Array Reports Incorrect Drive Replacement

    Guide, Volume I on the Hewlett Packard Enterprise website. 2. Be sure all drives are fully seated. 3. Determine which drive is defective using HPE SSA. Then, replace the defective cables, drive, or both. Depending on the fault-tolerance level, all data might be lost if another drive fails.
  • Page 147 For more information, see the HPE Smart Storage Administrator User Guide on the Hewlett Packard Enterprise website. 2. Be sure the cable is routed correctly. For more information, see the product user guide on the Hewlett Packard Enterprise website. 1789-Slot X Drive Array Disk Drive(s) Not Responding Symptom 1789-Slot X Drive Array Disk Drive(s) Not Responding.
  • Page 148 2. Perform orderly system shutdowns to avoid leaving data in the cache. 3. If the data is corrupt, restore previous backup data. 4. If the issue persists, replace and charge the HPE Smart Storage Battery. 1794-Slot X Drive Array – Cache Module Battery is Charging Symptom 1794–Slot X Drive Array –...
  • Page 149 1. To discard this data, select the F9 key to access System Utilities while the system ROM is booting. 2. From the System Utilities menu, select System Health View > System Health. 3. Select the HPE Smart Array controller. 4. Select Health Status: Configuration Required.
  • Page 150 For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website. Action 1. Use iLO to verify that the HPE Smart Storage battery is charged, and that the charge is sufficient to enable caching 2. Verify that the cache module is seated properly.
  • Page 151 Hard parity error detected while reading data from posted-writes memory. Action 1. Use iLO to verify that the HPE Smart Storage battery is charged, and that the charge is sufficient to enable caching 2. Verify that the cache module is seated properly.
  • Page 152 Action Replace the cache module. For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website. 1799-Slot X Drive Array – Drive(s) Disabled due to Cache Data Loss Symptom 1799-Slot # Drive Array - Drive(s) Disabled due to Cache Data Loss. Select “F1”...

  • Page 153: 1800 Series

    Cause A license key is missing or has expired. Action Enter a new or valid HPE Smart Array Advanced Pack License Key. 1803-Slot X Drive Array – Cache Module is not installed Symptom 1803-Slot X Drive Array – Cache Module is not installed. IMPORTANT: Unsupported Configuration: Controller performance and supported configurations are limited.
  • Page 154 Action Install the cache module to remove the limitations. For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website. 1804-Slot X Drive Array – Cache Module critical error Symptom 1804-Slot X Drive Array – Cache Module critical error. Action: Replace Cache Module (Controller is disabled until this problem is resolved).
  • Page 155 Cause The master key is incorrect or was not retrieved from the remote key manager. Action Use the HPE Enterprise Secure Key Manager to correct the issue. 1811-Slot X Encryption Failure Symptom 1811-Slot X Encryption Failure-Drive Keys not retrieved from the Remote Key Manager. Dependent encrypted logical drives are offline.
  • Page 156 Cause Drive keys could not be retrieved from the remote key manager. Action Use the HPE Enterprise Secure Key Manager to correct the issue. 1812-Slot X Encryption Failure Symptom 1812-Slot X Encryption Failure-Invalid Drive Keys on Remote Key Manager. Encrypted logical drives may be offline.
  • Page 157 Encrypted logical drives are offline. Action: Use HP Smart Storage Administrator to enable encryption. Cause Controller encryption is not enabled. Action Use HPE SSA to enable encryption. For more information, see the HPE Smart Storage Administrator User Guide on the Hewlett Packard Enterprise website. 1817-Slot X Encryption Failure Symptom 1817-Slot X Encryption Failure-Encryption is enabled for the controller but the Master Key name is not set.
  • Page 158 The is running an unsupported system ROM. Action Update the system ROM to a version that supports encryption. For more information, see "Keeping the system current" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 1820-Slot X Encryption Failure Symptom 1820-Slot X Encryption Failure-Encrypted logical drives are offline.
  • Page 159 Encrypted logical drives are offline due to a missing Local Master Key. Action Use HPE SSA to enter the Local Master Key. For more information, see the HPE Smart Storage Administrator User Guide on the Hewlett Packard Enterprise website. 1823-Slot X Encryption Failure Symptom 1823-Slot X Encryption Failure-Unsupported iLO FW detected.
  • Page 160 For more information, see the HPE iLO 4 User Guide on the Hewlett Packard Enterprise website. 1824-Slot X One or more storage cables has failed Symptom 1824-Slot X One or more storage cables have failed preventing discovery of attached storage. Action: Turn OFF power and re-attach the failed cables (run SSA to determine failed cables).
  • Page 161 For more information, see the maintenance and service guide on the Hewlett Packard Enterprise website. 2. Update the firmware. For more information, see "Firmware updates" in the HPE ProLiant Gen9 Troubleshooting Guide, Volume I on the Hewlett Packard Enterprise website. 3. Configure the controller encryption to bring the encrypted drives online.
  • Page 162 1832-Slot X One or more physical drives are not exposed Symptom 1832-Slot X One or more physical drives are not exposed to the host due to presence of logical unit metadata. Action: Run HPE SSA to manage these drives. Cause Drives contain logical unit metadata.

  • Page 163: Integrated Management Log Error Messages

    IML, which can be viewed through different tools. The error messages in this section might be worded slightly different than as displayed by the . For more information on the IML, see the HPE iLO 4 User Guide on the Hewlett Packard Enterprise website.

  • Page 164: Operating System Failure: Cause [Nt]

    Before removing or replacing any processors, be sure to follow the processor troubleshooting guidelines in HPE ProLiant Gen9 Troubleshooting Guide, Volume I: Troubleshooting on the Hewlett Packard Enterprise website. Failure to follow the recommended guidelines can cause damage to the system board, requiring replacement of the system board.

  • Page 165: System Power Supplies Not Redundant

    System Power Supplies Not Redundant Event Type: Power supply not redundant Action: Add a power supply or replace the failed power supply. System Power Supply Failure (Power Supply X) Event Type: Power supply failure Action: Replace the power supply. Uncorrectable Memory Error (Slot X, Memory Module Y)..Uncorrectable Memory Error (System Memory) Uncorrectable Memory Error (Memory Module Unknown) Event Type: Uncorrectable error...

  • Page 166: Hpe Proliant Gen9 Power Fault Codes

    HPE ProLiant Gen9 power fault codes Front panel LED power fault codes When a power fault occurs, the following front panel LEDs flash simultaneously: • System power LED • Health LED • NIC LED • UID LED For more information about the LED locations on your , see the server user guide in the Hewlett Packard Enterprise Information Library.

  • Page 167: Hpe Smart Array Errors

    HPE Smart Array errors Controller runtime LEDs To determine the controller status, see the appropriate controller-specific section. P440ar controller LEDs Immediately after you power up the server, the controller runtime LEDs illuminate briefly in a predetermined pattern as part of the POST sequence. At all other times during server operation, the illumination pattern of the runtime LEDs indicates the status of the controller.

  • Page 168: P440 Controller Leds

    P440 controller LEDs Immediately after you power up the server, the controller runtime LEDs illuminate briefly in a predetermined pattern as part of the POST sequence. At all other times during server operation, the illumination pattern of the runtime LEDs indicates the status of the controller. Item Color Name...

  • Page 169: P840 Controller Leds

    Item Color Name Interpretation Green Heartbeat When the controller is in good health, this LED flashes at 1 Hz. During power-up, this LED is solid for up to 2 seconds. Amber Fault When an error occurs, this LED is on. During power-up, this LED is solid for up to 2 seconds.

  • Page 170: Cache Module Leds

    Item Color Name Interpretation Green Heartbeat When the controller is in good health, this LED flashes at 1 Hz. During power-up, this LED is solid for up to 2 seconds. Amber Fault When an error occurs, this LED is on. During power-up, this LED is solid for up to 2 seconds.
  • Page 171 The battery is not connected to the system per second per second board. Flashing twice Flashing twice The battery has been charging for 10 per second per second minutes, but has not reached sufficient charge to perform a full backup. Table Continued HPE Smart Array errors...

  • Page 172: Smart Array Windows Event Log Messages

    Smart Array controller events to the Windows system event log, ProLiant Integrated Management Log (IML) and Integrity System Event Log (SEL) will not occur until the software is updated. To upgrade your software, please visit http://www.hpe.com/support/drivers Message ID: 24581 Severity: Informational Log message: The Smart Array SAS/SATA event notification service <status message>.
  • Page 173 • HARDWARE_ERROR - Drive is returning a Hardware Error sense key; controller unable to get drive back online. • ABORTED_COMMAND - Drive is returning an Aborted Command sense key; controller unable to get drive back online. HPE Smart Array errors...
  • Page 174 • GDP_VPD_INQUIRY_FAILED - Could not read drive serial number after multiple retries. • GDP_MODE_SENSE_FAILED - Could not read certain mode pages after multiple retries. • DRIVE_NOT_IN_48BIT_MODE - SATA drive is not supported in 48-bit LBA mode. HPE Smart Array errors...
  • Page 175 SMART trip state that indicates the drive has reached 0 percent usage left. Indicates that the drive has a SMART wear error and is approaching the maximum usage limit for writes (wear out). The drive should be replaced as soon as HPE Smart Array errors...
  • Page 176 Log message: Array controller <controller name / slot information> has reported that more physical devices were detected than the controller is currently capable of supporting. Some physical drives will not be accessible. Message ID: 24594 Severity: Warning HPE Smart Array errors...
  • Page 177 • WRITE_PROTECTED - Drive is returning a sense key indicating it is write protected. • SPIN_UP_FAILURE_IN_RECOVER - “Start Unit” command failed during error recovery • REBUILD_WRITE_ERROR - Drive failed write command after multiple retries during rebuild. HPE Smart Array errors...
  • Page 178 DRIVE_TYPE_MIX_IN_HOT_PLUG - Attempt to hot-add a SATA drive as a replacement in a SAS-only volume, or vice versa. • DRIVE_TYPE_MIX_IN_LOAD_CFG - attempt to use a SATA drive as a replacement in a SAS-only volume, or vice versa. HPE Smart Array errors...
  • Page 179 Log message: The <drive type> physical hard drive located in bay <bay number> is not supported <not supported reason>. This drive can be found in box <box number> which is connected to port <port number> of the array controller <controller name / slot information>. <not supported reason> values: HPE Smart Array errors...
  • Page 180 “DISABLED DUE TO SCSI ID CONFLICT” • “EJECTED” • “ERASING” • “UNKNOWN” Message ID: 24599 Severity: Warning Log message: Logical drive <logical drive number> of array controller <controller name / slot information> has encountered a status change from: HPE Smart Array errors...

  • Page 181: Message Identifiers 24600-24624

    Status: <previous status> Status: <current status> <previous status> and <current status> values: • “OK” • “FAILED” • “NOT CONFIGURED” • “INTERIM RECOVERY MODE” • “READY FOR RECOVERY” • “RECOVERING” • “WRONG PHYSICAL DRIVE REPLACED” • “PHYSICAL DRIVE NOT PROPERLY CONNECTED” •...
  • Page 182 The physical drive that reported the read error is located in bay <bay number> of box <box number> which is connected to port <port number> of array controller <controller name / slot information>. Message ID: 24604 HPE Smart Array errors...
  • Page 183 <box number> was removed from port <port number>. This connection was through I/O module number <module number> on the storage box. This event can occur when either a sole I/O module or data cable is removed. Message ID: 24610 HPE Smart Array errors...
  • Page 184 <port number> and box <box number>. <firmware information>. Please check the cabling and ensure that a supported configuration is being used. <firmware information> values: HPE Smart Array errors...
  • Page 185 Severity: Informational Log message: Fan number <fan number> in box <box number> was <inserted / removed>. Box <box number> is attached to port <port number> of array controller <controller name / slot information>. Message ID: 24620 HPE Smart Array errors...

  • Page 186: Message Identifiers 24625-24649

    Severity: Informational Log message: Fan number <fan number> located on fan module <fan module number> in box <box number> was <inserted / removed>. Box <box number> is attached to port <port number> of array controller <controller name / slot information>. Message ID: 24621 Severity: Error Log message: Fan number <fan number>...
  • Page 187 Log message: Array controller <controller name / slot information> has reported that its cache batteries are missing. Message Id: 24635 Severity: Warning Log message: Array controller <controller name / slot information> has reported that its cache batteries have failed. Message Id: 24636 Severity: Informational HPE Smart Array errors...
  • Page 188 Message Id: 24644 Severity: Error Log message: The Smart Array controller <controller name / slot information> is not redundant because it is of a different firmware revision than its partner controller. HPE Smart Array errors...

  • Page 189: Message Identifiers 24650-24674

    Message Id: 24645 Severity: Error Log message: The Smart Array controller <controller name / slot information> is not redundant because it is using a different cache size than its partner controller. Message Id: 24646 Severity: Error Log message: The Smart Array controller <controller name / slot information> is not redundant because its partner controller has reported a cache failure.
  • Page 190 Log message: Restore operation of SnapShot ID <ID number> of logical drive <logical drive number> on <external specification> array controller <controller name / slot information> failed due to possible data corruption. <external specification> values: • “the external controller attached to” • "" Message Id: 24656 Severity: Warning HPE Smart Array errors...
  • Page 191 <added to / removed from> the SAS fabric. Message Id: 24661 Severity: Informational Log message: Surface analysis parity/consistency initialization forced complete for logical drive <logical drive number> on Smart Array controller <controller name / slot information>. Message Id: 24662 Severity: Informational HPE Smart Array errors...
  • Page 192 Log message: Snapshot resource volume of logical drive <logical drive number> on <external specification> array controller <controller name / slot information> has been deleted. <external specification> values: • “the external controller attached to” • "" Message Id: 24672 Severity: Error HPE Smart Array errors...

  • Page 193: Message Identifiers 24675-24699

    Log message: Snapshot resource volume of logical drive <logical drive number> on <external specification> array controller <controller name / slot information> has reached its limit. <external specification> values: • “the external controller attached to” • "" Message Id: 24673 Severity: Informational Log message: Power supply number <power supply number>...
  • Page 194 <block address 1> and logical block address <block address 2>. The host will be unable to read some blocks between this address range until the blocks are overwritten. The logical drive rebuild is continuing so that the volume can HPE Smart Array errors...
  • Page 195 Log message: A SAS link error has been detected between port <port number> of array controller <controller name / slot information> and I/O module number <module number> located in box number <box number>. Please check this data path and the associated hardware. Message Id: 24692 HPE Smart Array errors...
  • Page 196 Log message: A SAS link error has been detected in bay <bay number> of box <box number> which is connected to port <port number> of array controller <controller name / slot information>. Please check this data path and the associated hardware. Message Id: 24698 Severity: Warning HPE Smart Array errors...

  • Page 197: Message Identifiers 24700-24724

    Log message: A SAS link error has been detected between array controller <controller name / slot information> and the switch expander connected to port <port number> of this controller. Please check this data path and the associated hardware. Message Id: 24699 Severity: Warning Log message: A SAS link error has been detected between a switch expander and I/O module <module number>...
  • Page 198 Log message: The external Smart Array controller located in the MSA chassis labeled as <chassis label> is reporting a drive failure notification for the <drive type> physical hard drive located in bay <bay number>. The failure reason received from the Smart Array firmware is: <firmware error code>. HPE Smart Array errors...
  • Page 199 SCSI bus. • REMOVED_IN_HOT_PLUG - Drive has been hot-removed. • INIT_REQUEST_SENSE_FAILED - “Request Sense” command failed during device discovery/initialization. HPE Smart Array errors...
  • Page 200 FAULTY_ID_BAY_EMPTY - Drive responds to SCSI ID, but the corresponding bay is empty. • FAULTY_ID_BAY_OCCUPIED - Bay is occupied by a drive that does not respond to the corresponding SCSI ID. • FAULTY_ID_INVALID_BAY - Drive responds to an ID that doesn’t have a valid corresponding bay. HPE Smart Array errors...
  • Page 201 <controller name / slot information>. <previous status> and <current status> values: • “OK” • “FAILED” • “NOT CONFIGURED” • “INTERIM RECOVERY MODE” • “READY FOR RECOVERY” • “RECOVERING” • “WRONG PHYSICAL DRIVE REPLACED” • “PHYSICAL DRIVE NOT PROPERLY CONNECTED” HPE Smart Array errors...
  • Page 202 • “WRONG PHYSICAL DRIVE REPLACED” • “PHYSICAL DRIVE NOT PROPERLY CONNECTED” • “HARDWARE IS OVERHEATING” • “HARDWARE HAS OVERHEATED” • “EXPANDING” • “NOT YET AVAILABLE” • “QUEUED FOR EXPANSION” • “DISABLED DUE TO SCSI ID CONFLICT” HPE Smart Array errors...
  • Page 203 • “HARDWARE IS OVERHEATING” • “HARDWARE HAS OVERHEATED” • “EXPANDING” • “NOT YET AVAILABLE” • “QUEUED FOR EXPANSION” • “DISABLED DUE TO SCSI ID CONFLICT” • “EJECTED” • “ERASING” • “UNKNOWN” Message ID: 24713 Severity: Informational HPE Smart Array errors...
  • Page 204 <bay number 1> of the MSA chassis. The physical drive that reported the write error is located in bay <bay number 2> of the MSA chassis. The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>. HPE Smart Array errors...
  • Page 205 The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>. Message ID: 24723 Severity: Warning Log message: The external Smart Array controller located in the MSA chassis labeled as <chassis label> has reported that its cache batteries have failed. HPE Smart Array errors...

  • Page 206: Message Identifiers 24725-24749

    The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>. Message ID: 24724 Severity: Informational Log message: The external Smart Array controller located in the MSA chassis labeled as <chassis label> has reported that an error log update has occurred for the physical drive with BMIC device index <device index>.
  • Page 207 <chassis label> is reporting that no redundant array controller is installed. The external Smart Array controller reporting this event is attached to the host side Smart Array controller <controller name / slot information>. Message Id: 24735 HPE Smart Array errors...
  • Page 208 <chassis label> are no longer redundant because both array controllers cannot see all the physical drives. The external Smart Array controller reporting this event is attached to the host side Smart Array controller <controller name / slot information>. Message Id: 24741 Severity: Error HPE Smart Array errors...
  • Page 209 This error has been detected between port <port number> of the external controller and I/O module number <module number> located in box number <box number>. Please check this data path and the associated hardware. HPE Smart Array errors...

  • Page 210: Message Identifiers 24750-24774

    The external Smart Array controller reporting this event is attached to the host side Smart Array controller <controller name / slot information>. Message Id: 24747 Severity: Warning Log message: The external Smart Array controller located in the MSA chassis labeled as <chassis label>...
  • Page 211 (re-added after a previous failure). The external Smart Array controller reporting this event is attached to the host side Smart Array controller <controller name / slot information>. Message Id: 24757 HPE Smart Array errors...
  • Page 212 The external Smart Array controller reporting this event is attached to the host side Smart Array controller <controller name / slot information>. Message Id: 24762 Severity: Informational Log message: HPE Smart Array errors...
  • Page 213 <battery pack number> located on controller number <controller number> has been <inserted / removed>. The external Smart Array controller reporting this operation is attached to the host side Smart Array controller <controller name / slot information>. Message Id: 24766 HPE Smart Array errors...
  • Page 214 <chassis label> has reported that fan number <fan number> located on fan module <fan module number> is reporting a degraded condition. The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>. Message Id: 24772 HPE Smart Array errors...

  • Page 215: Message Identifiers 24775-24799

    Severity: Informational Log message: The external Smart Array controller located in the MSA chassis labeled as <chassis label> has reported that fan number <fan number> located on fan module <fan module number> is now operational. The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>.
  • Page 216 • INIT_RESET_RECOVERY_ABORTED - Unable to communicate with drive during initialization after multiple bus resets and retries; may be due to this drive or another drive that is corrupting the parallel SCSI bus. HPE Smart Array errors...
  • Page 217 FR_ATI_TEST_FAILED_WRITE - Drive failed write command while checking for errors. • OFFLINE_ERASE - Drive is offline due to a Secure Erase operation. • OFFLINE_TOO_SMALL - Drive is offline because it’s a replacement drive that is too small. HPE Smart Array errors...
  • Page 218 <logical drive number> by updating the parity data to match the data drive contents. The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>. Message ID: 24780 Severity: Warning HPE Smart Array errors...
  • Page 219 <chassis label> has reported that fan module <fan module number> is now operational. The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>. Message ID: 24785 Severity: Informational HPE Smart Array errors...
  • Page 220 (wear out). The drive should be replaced as soon as possible. The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>. Message ID: 24791 HPE Smart Array errors...
  • Page 221 Log message: The external Smart Array controller located in the MSA chassis labeled as <chassis label> is indicating that a previously existing temperature condition on the controller from sensor <sensor number> has been corrected. All of the temperature sensors are now reporting acceptable temperature levels. HPE Smart Array errors...

  • Page 222: Message Identifiers 24800-24808

    Log message: The <drive type> physical drive located in bay <bay number> could not be authenticated as a genuine HPE hard drive. This drive's status LEDs will not be controlled. This drive can be found in box <box number> which is connected to port <port number>...

  • Page 223: Smart Array Windows Driver Errors

    The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>. Message ID: 24803 Severity: Warning Log message: Array controller <controller name / slot information> has reported that it previously locked up with code <lockup code>. Message ID: 24804 Severity: Warning Log message: The external Smart Array controller located in the MSA chassis labeled...
  • Page 224 Severity: Error Log message: The controller (bus %2, device %3, function %4) failed to post. Message Id: 5006 Severity: Error Log message: The controller (bus %2, device %3, function %4) failed with lockup code=0x%5 LED status=0x%6. HPE Smart Array errors...

  • Page 225: Hpe Onboard Administrator Errors

    HPE Onboard Administrator errors Onboard Administrator error messages • Soap Response Errors—These are the general errors reported by the gSoap service for validation errors, device failures, and so on. These errors are organized into two categories: ◦ User Request errors ◦...
  • Page 226 58 Shutting down the enclosure failed. 59 Getting the enclosure information failed. 60 Getting the enclosure names failed. 61 Getting the enclosure status failed. 62 Setting the enclosure name failed. 63 Setting the enclosure asset tag failed. HPE Onboard Administrator errors...
  • Page 227 101 Could not find the starting boundary in the RIBCL response. 102 Could not find the ending boundary in the RIBCL response. 103 Could not determine the IP address of the management processor for the requested blade. HPE Onboard Administrator errors...
  • Page 228 148 The other Onboard Administrator is not present. 149 No redundant Onboard Administrator found. Cannot failover. 150 The user could not be authenticated. 151 Invalid parameter for setting blade one time boot. 152 Invalid parameter for setting the blade boot priority. HPE Onboard Administrator errors...
  • Page 229 188 Error clearing blade signature. 189 Error setting blade signature. 190 Request is valid only for server blades. 191 Request is valid only for ProLiant server blades. 192 The string entered is not a valid netmask. HPE Onboard Administrator errors...
  • Page 230 233 This feature requires the iLO Select Pack License or iLO Advanced Pack License on the server blade when LDAP is enabled on the Onboard Administrator. 234 Invalid characters detected. 235 Onboard Administrator is initializing. Login disabled. 236 Cannot retrieve Onboard Administrator media device array. HPE Onboard Administrator errors...
  • Page 231 271 Cannot delete the last CA with two-factor authentication enabled. 272 The Onboard Administrator cannot communicate with iLO. 273 An EBIPA configuration error occurred. 274 Link Loss Failover intervals must be between 30 and 86400 seconds. 275 Network speed must be either 10Mbit or 100Mbit. HPE Onboard Administrator errors...
  • Page 232 307 Wrong number of bays specified for enclosure while setting capping bays to exclude. 308 The number of bays opted out exceeds the maximum allowed. 309 Enclosure Dynamic Power Cap feature is not allowed. 310 Enclosure Dynamic Power Cap is set. HPE Onboard Administrator errors...
  • Page 233 347 The requested set of bays to exclude cause the Derated Circuit Capacity to be outside the allowable range. 348 The requested set of bays to exclude cause the Rated Circuit Capacity to be outside the allowable range. 353 IPv6 is currently disabled. Cannot download certificate from the specified address. HPE Onboard Administrator errors...
  • Page 234 OA and the Insight Remote Support receiver. 389 This action cannot be performed in FIPS MODE ON/DEBUG. 391 No Variable Name-Value pairs are provided for substitution. 392 Attempted to substitute more than 25 variables. 395 Trying to substitute the same variable twice. HPE Onboard Administrator errors...
  • Page 235 442 This enclosure is incapable of performing a reset on a non-redundant Onboard Administrator. 444 Power cap configuration locked due to active group management. REMOTE SUPPORT TIER2 445 Remote Support receiver temporarily unavailable. Please retry later. HPE Onboard Administrator errors...
  • Page 236 472 Deleted device. This device has been previously deleted from the Insight Remote Support user interface. Please unregister and re-register device. 473 Unhandled Error. HPE Onboard Administrator errors...
  • Page 237 518 Password is required. Please retry registration. 519 HP Passport user ID is invalid. Please retry registration with a valid user ID. 520 HP Passport account is locked out due to excessive login authentication failures. Please reset your password and retry registration. HPE Onboard Administrator errors...
  • Page 238 566 Invalid IPv6 static route gateway. Route gateway must not be empty and must not contain prefix length. 567 IPv6 static route destination already exists. 568 Unable to add IPv6 route. The maximum number of IPV6 static routes already exist. HPE Onboard Administrator errors...

  • Page 239: Syslog Messages

    569 IPv6 static route not found. 570 Invalid IPv6 static route destination. The route destination must be a valid IPv6 address. 571 All items cannot be disabled. 572 This action requires the OA to be in FIPS Mode ON/DEBUG. 573 Must set MINRATE option if using timeout range. 574 Minimum data rate must be larger than 0.

  • Page 240: Authentication And Startup Log Messages

    Alertmail: Failed to get initial enclosure status Alertmail: Failed to read cooling info Alertmail: Failed to read enclosure info Alertmail: Failed to read enclosure names Alertmail: Failed to read enclosure status Alertmail: Failed to read event from mgmt subsystem Alertmail: Failed to read LCD status Alertmail: Failed to read powersupply measurements Alertmail: Failed to read rack topology information Alertmail: Failed to read status of fan [value]...

  • Page 241: Cgi Log Messages

    sulogin: Normal startup sulogin: System Maintenance Mode CGI log messages Log type: LOG_ERR, Failure type: SW cdrom.iso: There was a problem reading from /dev/cdrom, however we cannot back out now. CLI log messages Log type: LOG_WARNING, Failure type: Info OA: [value] logged out of the Onboard Administrator Log type: LOG_INFO, Failure type: Info OA: ProLiant iLO firmware update attempted by user [value] Interconnect bay log messages...

  • Page 242: Enclosure-Link Log Messages

    OA: dhcpRelease: sendto: [value] OA: dhcpStart: bind: [value] OA: dhcpStart: fcntl: [value] OA: dhcpStart: interface [value] is not Ethernet or 802.2 Token Ring OA: dhcpStart: ioctl SIOCGIFFLAGS: [value] OA: dhcpStart: ioctl SIOCGIFHWADDR: [value] OA: dhcpStart: ioctl SIOCSIFFLAGS: [value] OA: dhcpStart: setsockopt: [value] OA: dhcpStart: socket: [value] OA: dhcpStop: ioctl SIOCSIFFLAGS: [value] OA: error executing [value] [value] [value]: [value]...
  • Page 243 Enclosure-Link: Found new elink topology. Notifying subsystems Enclosure-Link: Found new Topology: [value] enclosure added to chain ([value] total) Enclosure-Link: Found new Topology: [value] enclosure removed from chain ([value] total) Enclosure-Link: Found new Topology: New enclosure connected ([value] total) HPE Onboard Administrator errors...

  • Page 244: Non-Volatile Configuration Log Messages

    Enclosure-Link: Got new TOPOLOGY event on enclosure [value:IpAddress] Enclosure-Link: Initial topology scan completed successfully Enclosure-Link: Service started Non-volatile configuration log messages Log type: LOG_WARNING, Failure type: SW CLI: Error accessing User Configuration Files Log type: LOG_ERR, Failure type: SW envtools: Block [value] failed encoding envtools: Error in default gateway envtools: Error in DNS1 address envtools: Error in DNS2 address...

  • Page 245: Firmware Flash Log Messages

    envtools: Downgrading NVRAM version from 26 to 25. envtools: Downgrading NVRAM version from 27 to 26. envtools: Factory Settings Restored. envtools: NVRAM downgraded from [value] to [value]. envtools: NVRAM downgraded to version [value] envtools: Updating NVRAM version to 19. envtools: Updating NVRAM version to 20. envtools: Updating NVRAM version to 21.

  • Page 246: Flash Certificate, Configuration, And Storage Log Messages

    OA_Flash: Only one flash instance can run at a time. OA_Flash: Out of memory while decoding flash image. OA_Flash: The firmware image provided is older than the current firmware and OA settings cannot be preserved. The force downgrade option must be used. Please re-try with the force option to flash and go back to factory defaults.

  • Page 247: Dns Network Configuration Log Messages

    CERTS: Failed to stage data CONFIG: [value] has wrong file permissions CONFIG: [value] has wrong permissions. Please reset to factory defaults CONFIG: Failed to compute MD5 CONFIG: Failed to open flash CONFIG: Failed to open input file CONFIG: Fail to open the file to be flashed CONFIG: Failed to open output file CONFIG: Failed to read data from flash CONFIG: Failed to read system files...

  • Page 248: Lcd Log Messages

    netreg: DDNS: Not implemented netreg: DDNS: Not in zone netreg: DDNS: Server failure netreg: DDNS: Unable to create socket netreg: DDNS: Update refused by DNS server netreg: Error starting DDNS thread netreg: Error starting NetBIOS thread netreg: NETBIOS: Refreshed WINS registration Log type: LOG_NOTICE, Failure type: Info netreg: DDNS: Registered with Dynamic DNS netreg: DDNS: Update successful...
  • Page 249 OA: KVM Bay [value:bladeNumber] - Must wait 5 minutes before attempting to acquire the console. OA: KVM Bay [value:bladeNumber] - Session acquired by different user. OA: KVM Blade [value:bladeNumber] console session closed due to ILO firmware upgrade HPE Onboard Administrator errors...

  • Page 250: Operational Log Messages

    Operational log messages Log type: LOG_EMERG, Failure type: SW OA: Internal System Firmware Error. Rebooting. Log type: LOG_WARNING, Failure type: SW FWSync: OA firmware sync failed to create firmware image from the Active Onboard Administrator FWSync: OA firmware sync failed to create firmware image from the Standby Onboard Administrator FWSync: OA firmware sync of the Active Onboard Administrator failed FWSync: OA firmware sync of the Standby Onboard Administrator failed...
  • Page 251 Log type: LOG_NOTICE, Failure type: SW FWSync: Sync failed because the Active and Standby OAs do not have the same hardware version. OA: unable to run [value:mount] OA: Warning: Unable to ping the remote oa_syslog server [value:Address] HPE Onboard Administrator errors...
  • Page 252 OA: EBIPA Server domain for bay [value:bladeNumber] set to [value] by user [value:username] OA: EBIPA Server first DNS IP for bay [value:bladeNumber] set to [value] by user [value:username] OA: EBIPA Server gateway for bay [value:bladeNumber] set to [value] by user [value:username] HPE Onboard Administrator errors...
  • Page 253 OA: Enclosure Name was changed to [value:Enclosure Name] by user [value:username] OA: ENCRYPTION changed to [value:mode] by user [value:username]. OA: Error: iLO Select license is not in place for this Single Sign-on attempt by the LDAP authenticated user OA: Factory defaults restored by [value] HPE Onboard Administrator errors...
  • Page 254 [value:username]. OA: LDAP search context [value:number] was cleared by user [value:username]. OA: LDAP server address was changed from [value:ipaddress] to [value:ipaddress] by user [value:username]. OA: LDAP server SSL port was changed to [value:port] by user [value:username]. HPE Onboard Administrator errors...
  • Page 255 OA: Static TCP/IP settings was modified by user [value:username]. OA: TCP/IP settings was set to DHCP - DynamicDNS by user [value:username]. OA: TCP/IP settings was set to DHCP by user [value:username]. OA: Tcp timeout set to [value:number] minutes. HPE Onboard Administrator errors...
  • Page 256 OA: Changing VLAN ID [value:number] name to [value:name] OA: Deleting VLAN ID [value:name]. OA: Waiting DHCPv4 server response. Log type: LOG_INFO, Failure type: SW OA: ERROR: Event [value] with location [value] sent Log type: LOG_INFO, Failure type: Info HPE Onboard Administrator errors...

  • Page 257: Linux Log Messages

    OA: Blade #[value:bladeNumber] boot order settings changed by user [value:username]. OA: Blade #[value:bladeNumber] boot order settings changed by user [value:username]. First Boot Device: [value]. Boot Agent: [value]. OA: Blade [value:bladeNumber] DVD connection changed by user [value:username] to '[value:URL]'. OA: Cold Boot virtual command enacted on blade[value:bladeNumber] by user [value:username].
  • Page 258 OA: Error reading Fru Board Info for the LCD. OA: Error reading Fru information for the LCD. OA: Error reading Fru Internal Use Area for the LCD. OA: mgmt: Failed to acquire enclosure semaphore. Log type: LOG_CRIT, Failure type: Info HPE Onboard Administrator errors...
  • Page 259 OA: Blade [value:bladeNumber] Main Logic Board fault...state is DEGRADED. OA: Blade [value:bladeNumber] needs a partner device. OA: Blade [value:bladeNumber] over temperature...state is CRITICAL. OA: Blade [value:bladeNumber] over temperature...state is DEGRADED. OA: Blade [value:bladeNumber] PCI device missing...state is CRITICAL. HPE Onboard Administrator errors...
  • Page 260 OA: Internal health status of interconnect in bay [value:slotNumber] changed to Unknown OA: Management Processor on Blade [value:bladeNumber] appears unresponsive. OA: Mixing different fan models is not supported. The fan in bay #[value:fanNumber] must be replaced with the proper part number. HPE Onboard Administrator errors...
  • Page 261 OA: Blade [value:bladeNumber] requires a proper mezzanine card to partner. OA: Blade [value:bladeNumber] requires partner in bay [value:bladeNumber] to be powered on first. OA: Blade [value:bladeNumber]: SMBIOS data carries more than [value] CPU records which cannot be processed with this OA firmware version. HPE Onboard Administrator errors...
  • Page 262 OA: Blade [value:bladeNumber] has been denied power but iLO is reporting the blade is powered on. OA: Blade [value:bladeNumber] Internal Temperature Sensor state is OK. OA: Blade [value:bladeNumber] Internal Temperature state is OK. HPE Onboard Administrator errors...
  • Page 263 OA: Server Power Reduction - Activated OA: Server Power Reduction Mode - Disabled OA: Server Power Reduction Mode - Enabled OA: Server Power Reduction Mode - Enabled OA: TRAY microcode updated from UNKNOWN version to version [value:version] HPE Onboard Administrator errors...

  • Page 264: Oa Internal Log Messages

    OA: TRAY microcode updated from version [value:version] to version [value:version] Log type: LOG_INFO, Failure type: HW OA: Interconnect removed from bay [value:slotNumber] Log type: LOG_INFO, Failure type: SW OA: A USB Key was inserted into the Onboard Administrator. OA: A USB Key was removed from the Onboard Administrator. OA: A CD-ROM Drive was inserted into the Onboard Administrator.
  • Page 265 Log type: LOG_NOTICE, Failure type: SW OA: Internal communication problem detected. OA: Internal communications restored. Log type: LOG_NOTICE, Failure type: Info OA: Internal communications restored. Log type: LOG_INFO, Failure type: SW OA: Can't read main mgmt process id. HPE Onboard Administrator errors...

  • Page 266: Ldap Log Messages

    LDAP log messages Log type: LOG_ALERT, Failure type: SW LDAP: pam_get_item returned error to ldap-read-password Log type: LOG_WARNING, Failure type: Info OA: LDAP [value:username] logged into the Onboard Administrator OA: LDAP [value:username] logged into the Onboard Administrator from [value:remoteHost] OA: LDAP [value:username] logged into the Onboard Administrator from Enclosure Link OA: LDAP [value:username] logged into the Onboard Administrator on [value] OA: LDAP [value:username] logged into the Onboard Administrator on the OA KVM.

  • Page 267: Sso Log Messages

    Redundancy: Failed automatic Onboard Administrator failover as a result of network link loss on the Active OA board Log type: LOG_ERR, Failure type: SW Redundancy: Couldn't get random seed Redundancy: Error communicating via ethernet with the other Onboard Administrator (heartbeat). Redundancy: Error communicating via ethernet with the other Onboard Administrator (timeout).

  • Page 268: Fips Log Messages

    Log type: LOG_WARNING, Failure type: Info OA: Two Factor: [value:username] logged into the Onboard Administrator from [value] using Two-Factor OA: Two Factor: [value:username] logged into the Onboard Administrator from Enclosure Link using Two-Factor OA: Two Factor: Unable to create session for user [value:username]: the maximum number of sesssions has been reached.

  • Page 269: Onboard Administrator Snmp Traps

    OA: May need to reboot the interconnects to pick up new IP address or wait until DHCP lease expires OA: VLAN ID for interconnect bay [value] changed to [value]. May need to reboot the interconnect to pick up new IP address or wait until DHCP lease expires OA: VLAN ID for OA changed from [value] to [value] OA: VLAN ID for server bay [value] changed to [value] OA: VLAN is disabled...

  • Page 270: Enclosure Event Notifications

    Trap ID Trap name Description 22037 cpqRackEnclosureManagerDegraded Onboard Administrator degraded 22038 cpqRackEnclosureManagerOk Onboard Administrator OK 22039 cpqRackEnclosureManagerRemoved Onboard Administrator removed 22040 cpqRackEnclosureManagerInserted Onboard Administrator inserted 22041 cpqRackManagerPrimaryRole Onboard Administrator is Active 22042 cpqRackServerBladeEKeyingFailed Blade eKeying config failed 22044 cpqRackNetConnectorRemoved Interconnect removed 22045 cpqRackNetConnectorInserted Interconnect inserted...
  • Page 271 Power Supply Inserted A power supply has been inserted. Power Supply Removed A power supply has been removed. Power Supply Redundancy Change The power supplies are either now redundant or are no longer redundant. Table Continued HPE Onboard Administrator errors...
  • Page 272 User Rights The privilege level of a user on the was changed. If you are logged in as this user, you are disconnected from the . You can log in again with your new privilege level. HPE Onboard Administrator errors...

  • Page 273: Hpe Virtual Connect Errors

    HPE Virtual Connect errors SNMP overview SNMP is a protocol used by network management systems to monitor devices on a network. It works by querying device objects, such as an interface status or port state. Virtual Connect supports SNMPv1, SNMPv2, and SNMPv3.
  • Page 274 Enet IF-MIB LinkDown VC-Enet Port INFO IF-MIB Status Enet IF-MIB LinkUp VC-Enet Port NORMAL IF-MIB Status Input utilization above high-water VC-Enet Port WARNING VCM-MIB mark Threshold Input utilization below low-water VC-Enet Port NORMAL VCM-MIB mark Threshold Table Continued HPE Virtual Connect errors...
  • Page 275 VCM-MIB Status Only supported by HPE VC 8Gb or 16Gb 24-Port FC modules The VC Module MIB has the capability to send traps when certain bandwidth and throughput utilization thresholds are reached. The counters are sampled at a fixed interval of 30 seconds and neither sample interval nor threshold values are configurable in this release.
  • Page 276 connUnitPortStatus value Severity unknown INFO unused INFO ready NORMAL warning WARNING failure CRITICAL nonparticipating INFO initializing INFO bypass INFO MAJOR other INFO VC Module MIB traps The following table lists traps in the VC Module MIB. Trap name Trap data Description vcModRoleChange moduleRole...
  • Page 277 OK, the port may be disabled to protect the VC module Port protection status from further service degradation. Administrative action is required to recover the port from this condition. Table Continued HPE Virtual Connect errors...
  • Page 278 Trap name Trap data Description vcModPortProtectionConditionCle The port is recovered from port Port index to the ifTable (ifIndex) ared protection condition to Port index to the normal operational state. vcModulePortTable Port protection status vcSwitchMemParityErrorEvent Error counter The switch hardware has detected vcSwitchMemParityErrorCount a parity error.
  • Page 279 The sFlow network state is failed or Enet modules have sFlow IP address issues. vcDomainSflowDegraded The sFlow network state is degraded or Enet modules have sFlow IP address issues. vcDomainPortMonitorIndirectlyDisabled PortMonitor is indirectly disabled by the VCEM. Table Continued HPE Virtual Connect errors...
  • Page 280 Port enc0:iobay5:d3:v1 loop detected and automatically disabled The module managed status ReasonCodes are provided in the following table. Module reason code Description vcEnetmoduleOk The Ethernet module is functioning normally. vcEnetmoduleEnclosureDown The module is unable to communicate with the enclosure/OA. Table Continued HPE Virtual Connect errors...
  • Page 281 1 of 2 uplink ports are abnormal on BackupSAN fabric The following is an example of an FC fabric RootCause string: 1 of 2 uplink ports are abnormal on BackupSAN fabric The FC fabric managed status ReasonCodes are provided in the following table. HPE Virtual Connect errors...
  • Page 282 The profile is normal. vcProfileServerAbnormal The server the profile is assigned to is abnormal. vcProfileAllConnectionsFailed All connections in the profile have failed. vcProfileSomeConnectionsUnmapped One or more connections in the profile are not mapped to a physical port. Table Continued HPE Virtual Connect errors...

  • Page 283: Virtual Connect Manager Syslog Events

    Profile reason code Description vcProfileAllConnectionsAbnormal All connections in the profile are abnormal. vcProfileSomeConnectionsAbnormal Some connections in the profile are abnormal. vcProfileUEFIBootmodeIncompatibleWithServer UEFI bootmode is assigned to non-UEFI capable server. vcProfileConnectionInvalidPXEBootOrder One of the ethernet connection in the profile has invalid PXEBootOrder. vcProfileConnectionDuplicateIscsiInitiatorIP Profile has iSCSI Connection configured with duplicate initiator IP.

  • Page 284: Domain Events (1000-1999)

    • FC Interconnect modules (4000–4999) • Servers (5000–5999) • Profiles (6000-6999) • Ethernet Network (7000–7999) • FC Fabric (8000–8999) • Unknown module (9000-9999) The events are categorized by severity which reflects the functional state of the component. The severity will guide you on the kind of attention you should give to taking an action in the occurrence of the event.

  • Page 285: Domain State Failed

    ◦ OA errors ◦ Hardware failures ◦ Rogue DHCP server • The VC management application has detected that the OA firmware version is below the acceptable limit. Action: Do the following if the communications failure is persistent: • Update the OA firmware if required. •...

  • Page 286: Enclosure Events (2000-2999)

    1. Export a support package from VC for Hewlett Packard Enterprise analysis. 2. Capture the output of the OA show all command for Hewlett Packard Enterprise analysis. 3. Contact Hewlett Packard Enterprise customer support with the previously gathered information. 1023 - Domain state PROFILE_FAILED Severity: MAJOR Description: This event is occurs when at least one profile is not in an OK state.

  • Page 287: Enclosure State Failed

    • Provide valid OA credentials (IP/user/password) if requested by VC. • Make sure that the user has interconnect bay access privileges. • Verify OA and VC have been assigned IP addresses and that the IP addresses do not conflict with other assignments on the network.
  • Page 288 • Check all Ethernet modules that are in the not OK or Degraded state. Replace if necessary. • Check all Servers that are in the not OK or Degraded state. Replace if necessary. • If hardware replacement does not correct the issue: 1.

  • Page 289: Ethernet Module Events (3000-3999)

    1. Export a support package from VC for Hewlett Packard Enterprise analysis. 2. Capture the output of the OA show all command for Hewlett Packard Enterprise analysis. 3. Contact Hewlett Packard Enterprise customer support with the previously gathered information. Ethernet Module events (3000-3999) 3009 - Enet Module OA CPU Fault Event Severity: MAJOR Description: The Onboard Administrator has reported to the VC management application that the indicated...

  • Page 290: Enet Module State Missing

    • Only similar VC modules can reside in adjacent horizontal bays. • If a VC-Enet module is installed in an interconnect bay, the only module that can be installed in the horizontally adjacent bay is another VC-Enet module of the same type. •...
  • Page 291 Possible causes: • Configuration of IP addresses/network topology is preventing communication between the primary VC- Enet module and the identified VC-Enet module. • An unexpected error has occurred while sending a configuration update to the module or while requesting status information from the module. This error may be due to TCP/IP communications interruption/timeout or due to a software generated failure.

  • Page 292: Fc Module Events (4000-4999)

    3102 - Port was disabled because a pause flood was detected Severity: MAJOR Description: Because a pause flood is detected on an Ethernet port, it has been disabled to avoid further service degradation. Possible cause: Bad NIC on the server. If too many pause frames are detected on a port, then the port is disabled with this state.

  • Page 293: Server Events (5000-5999)

    • The module is running outdated FW. It might be running either an older or newer version than Virtual Connect manager expects. • The module is not compatible with a module running in an adjacent bay in either double-dense or single- dense mode.
  • Page 294 Action: Verify that communication between VC and Onboard Administrator for the affected server is operational. Verify that the server is in a good state (not failed or faulted). 5014 - Server state INCOMPATIBLE Severity: MAJOR Description: The VC management application has determined that the server BIOS version does not support the minimum capabilities required for Virtual Connect.

  • Page 295: Profile Events (6000-6999)

    Description: The VC management application has determined that the server BIOS version does not support the minimum capabilities required for Virtual Connect. Possible cause: The server has a down-rev BIOS version. Action: Update the BIOS on the server to latest version. 5056 - Unable to release power hold on the server.

  • Page 296: Ethernet Network Events (7000-7999)

    Description: A profile has iSCSI boot enabled on an unsupported Flex-10 NIC. Possible cause: An administrator has incorrectly configured the boot settings for the profile. Actions: • Correct the specified profile settings to enable the iSCSI boot on a supported NIC. •...

  • Page 297: Fc Fabric Events (8000-8999)

    • All of the uplink ports associated with the network are unlinked. • The user disables all the uplink ports associated with a non-shared network. • The user disables all the uplink ports in a shared uplink set associated with a shared network. Action: •...

  • Page 298: Enet Uplinkset Events (17000-17999)

    • Re-insert a module of the same type back into the bay that is marked as missing. • Make modifications to the domain to eliminate the dependencies on the missing module. Once the dependencies have been removed, resetting VCM should clear the missing module indication. 9014 - Unknown Module state INCOMPATIBLE Severity: MAJOR Description: An unknown module is incompatible with the current domain configuration.
  • Page 299 Possible cause: All the uplink ports in the shared uplink set associated with the network are unlinked or all uplink ports in a shared uplink set associated with a shared network have been disabled. Actions: • Connect the uplink ports. •...

  • Page 300: Conrep Errors

    CONREP errors Using CONREP The CONREP utility generates a system configuration XML file used to duplicate the hardware configuration of one ProLiant server onto another. The CONREP utility uses the hardware configuration XML file to identify and configure the system, which defaults to conrep.xml. You can change the default using the -x option. The actual system configuration file is captured as an XML data file.

  • Page 301: Conrep Screen Output

    Value Meaning The command was completed successfully. The hardware definition data file (conrep.xml) is corrupt or not found. The system configuration data file (conrep.dat) is corrupt or not found. The Health Driver is required for this operation but is not loaded. The system administrator password is set.

  • Page 302: Hpe Ilo Messages, Traps, And Errors

    HPE iLO messages, traps, and errors iLO POST LED indicators During the initial boot of , the POST LED indicators flash to display the progress through the boot process. After the boot process is complete, the HB LED flashes in one second intervals. LED indicators (1 through 6) illuminate after the system has booted to indicate a hardware failure.
  • Page 303 The default language settings were modified by the listed user. Deleted group [group name] by: [user name] The listed directory group was deleted by the listed user. Deleted user: [user name] The listed user account was deleted. Table Continued HPE iLO messages, traps, and errors...
  • Page 304 Firmware upgrade via XML failed Firmware upgrade via RIBCL script failed. Make sure the firmware image file is correct. Firmware upgraded to version [version] Firmware was successfully updated to the listed version. Table Continued HPE iLO messages, traps, and errors...
  • Page 305 RBSU exited. iLO RBSU login failure An attempt to login to iLO via the iLO RBSU failed. iLO RBSU login: [user name] The listed user logged in to iLO via the iLO RBSU. Table Continued HPE iLO messages, traps, and errors...
  • Page 306 An error occurred while iLO attempted to update the language pack. License activation error by: [user name] The license activation key cannot be installed. Possibly the activation key was invalid or not supported. Table Continued HPE iLO messages, traps, and errors...
  • Page 307 The server console lock needs to be done manually. Remote console computer lock Enabled by: [user The remote console auto-lock setting was enabled. name] The server console will be automatically locked when the remote console session ends. Table Continued HPE iLO messages, traps, and errors...
  • Page 308 Serial CLI logout: [user name] The listed user logged out of iLO via the Serial CLI. Serial CLI session started A Serial CLI session started. Serial CLI session stopped A Serial CLI session stopped. Table Continued HPE iLO messages, traps, and errors...
  • Page 309 An attempt to login to iLO using SSO was rejected because the SSO certificate was not trusted. SSO rejected: not enabled An attempt to login to iLO using SSO was rejected because SSO was not enabled. Table Continued HPE iLO messages, traps, and errors...
  • Page 310 Update of Power Management Controller failed An attempt to update the Power Management Controller failed. Update of Power Management Controller from The Power Management Controller update was version [version number] starting. started. The current version is listed. Table Continued HPE iLO messages, traps, and errors...

  • Page 311: Ribcl Messages

    Event log display Event log explanation Update of Power Management Controller to version The Power Management Controller has been [version number] complete successfully updated to the listed version. User [user 1] added by [user 2] A user account was added. User [user 1] deleted by [user 2] A user account was deleted.
  • Page 312 The board will be reset after the operation. 0x001A The Remote Insight Board is being reset. 0x001B The server is being reset. 0x001C The Integrated Lights-Out Event Log is being cleared. Table Continued HPE iLO messages, traps, and errors...
  • Page 313 0x002F License is already active. 0x0030 Login is currently being delayed. 0x0031 A firmware update is already in progress. 0x0032 LENGTH does not match post-translated length of VALUE. 0x0033 Problem manipulating EV. Table Continued HPE iLO messages, traps, and errors...
  • Page 314 This setting can not be enabled unless a trusted CA certificate has been imported. 0x004A The value specified is invalid. 0x004B No data available. 0x004C Power management is disabled. 0x004D Feature not supported. Table Continued HPE iLO messages, traps, and errors...
  • Page 315 0x0061 RIBCL parser is not active. No output is being generated. 0x0062 VLAN configuration is available on Shared Network Port(SNP) only. Either modify this script to enable SNP or do it manually. Table Continued HPE iLO messages, traps, and errors...
  • Page 316 - Missing required parameter for direct connect model setup. 0x0084 eRS - Missing required parameter for IRS connect model setup. 0x0085 eRS - No connect model specified. 0x0086 There are missing parameters in the xml script. Table Continued HPE iLO messages, traps, and errors...
  • Page 317 Power capping has been disabled in the ROM by the user. 0XA0 Incorrect URL. 0XA1 Failed to connect to the URL. 0XA3 Failed to update the hot key. 0XA4 Invalid number of keystrokes. Table Continued HPE iLO messages, traps, and errors...
  • Page 318 This feature requires an advanced license key. 0XB1 There was an error on reading the data. 0XB2 There was an error on setting the data. 0XB3 Invalid port. Port assignments must be unique. 0XB4 HPE iLO messages, traps, and errors...

  • Page 319: Hpe Insight Management Agents For Servers For Windows

    This section contains a listing of the Microsoft Windows Server Event Log messages associated with SNMP traps, which are generated by the HPE Insight Management Agents for Servers for Windows. Each event entry has the corresponding SNMP trap number used by the agents.

  • Page 320: Agent Descriptions

    Agent descriptions • Foundation/Host Agent—cpqhsmsg • Sever Agent—cpqsvmsg • Storage Agent—cpqstmsg • NIC Agent—cpqnimsg Foundation agents Event Identifiers 1105-1808 NT Event ID: 1105 (Hex)0x44350451 (cpqhsmsg.dll) Log Severity: Information (1) Log Message: %1 SNMP Trap: cpqHo2GenericTrap - 11003 in CPQHOST.MIB Symptom: Generic trap. Supporting SNMP Trap Data: •...
  • Page 321 Supporting SNMP Trap Description: “[cpqMeAlarmOwner]: Variable [cpqMeAlarmVariable] has value [cpqMeAlarmValue] <= [cpqMeAlarmFallingThreshold].” NT Event ID: 1164 (Hex)0x8435048c (cpqhsmsg.dll) Log Severity: Warning (2) Log Message: Critical Rising Threshold Passed. SNMP Trap: cpqMeCriticalRisingAlarmExtended - 10007 in CPQTHRSH.MIB HPE Insight Management Agents for Servers for Windows...
  • Page 322 • cpqMeAlarmOwner • cpqMeAlarmSeverity • cpqMeAlarmExtendedDescription Supporting SNMP Trap Description: “[cpqMeAlarmOwner]: Variable [cpqMeAlarmVariable] has value [cpqMeAlarmValue] <= [cpqMeAlarmFallingThreshold].” NT Event ID: 1166 (Hex)0x8435048e (cpqhsmsg.dll) Log Severity: Warning (2) Log Message: %1 HPE Insight Management Agents for Servers for Windows...
  • Page 323 Log Severity: Warning (2) Log Message: The cluster network %4 has become degraded. SNMP Trap: cpqClusterNetworkDegraded - 15007 in CPQCLUS.MIB Symptom: This trap is sent any time the condition of a cluster network becomes degraded. HPE Insight Management Agents for Servers for Windows...
  • Page 324 Log Message: The cluster service on %4 has failed. SNMP Trap: cpqClusterNodeFailed - 15004 in CPQCLUS.MIB Symptom: This trap is sent any time the condition of a node in the cluster has failed. HPE Insight Management Agents for Servers for Windows...
  • Page 325 Processor Time of [cpqOsCpuTimePercent] percent.” NT Event ID: 1175 (Hex)0x84350497 (cpqhsmsg.dll) Log Severity: Warning (2) Log Message: The Cache Performance Instance, '%4' is degraded with Cache Copy Read Hits of %5 percent. HPE Insight Management Agents for Servers for Windows...
  • Page 326 Log Message: The PagingFile Performance Instance, '%4' is degraded with PagingFile Usage of %5 percent. SNMP Trap: cpqOsPageFileUsageDegraded - 19005 in CPQWINOS.MIB Symptom: The PagingFile Usage performance property is set to degraded. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqOsPagingFileIndex • cpqOsPagingFileInstance • cpqOsPageFileUsagePercent HPE Insight Management Agents for Servers for Windows...
  • Page 327 Log Message: The Logical Disk Performance Instance, '%4' is failed with Disk Busy Time of %5 percent. SNMP Trap: cpqOsLogicalDiskBusyTimeFailed - 19008 in CPQWINOS.MIB Symptom: The LogicalDisk BusyTime performance property is set to critical. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags HPE Insight Management Agents for Servers for Windows...
  • Page 328 Log Message: The Foundation SNMP Agent service is not running. The agent has determined that the Foundation Agents service is not running. Stop the SNMP service and restart the Foundation Agents service. If the error persists, reinstalling the Management Agents may correct this error. HPE Insight Management Agents for Servers for Windows...

  • Page 329: Event Identifiers 2048-2359

    Event identifier: cpqhsmsg.dll - 1808 (Hex)0x44350710 (Service Event) Log Severity: Information (1) Log Message: The agent could not deliver trap %1. The agent was unable to use Asynchronous Management to deliver a trap. This can be caused by a failure in the Remote Access Service or by a missing or invalid configuration.
  • Page 330 Log Severity: Warning (2) Log Message: The Threshold Agent could not set an event. The data contains the error code. Event identifier: cpqhsmsg.dll - 2312 (Hex)0x84350908 (Service Event) Log Severity: Warning (2) HPE Insight Management Agents for Servers for Windows...
  • Page 331 Log Message: The Threshold Agent could not set the variable because the value is invalid or out of range. The data contains the error code. Event identifier: cpqhsmsg.dll - 2359 (Hex)0x84350937 (Service Event) Log Severity: Warning (2) HPE Insight Management Agents for Servers for Windows...

  • Page 332: Event Identifiers 3072-3876

    Log Message: The Threshold Agent is not loaded. Sets are not available. The data contains the error code. Event Identifiers 3072-3876 Event identifier: cpqhsmsg.dll - 3072 (Hex)0x84350c00 (Service Event) Log Severity: Warning (2) Log Message: Could not read from the registry sub-key. This error can be caused by a corrupt registry or a low memory condition.
  • Page 333 Event identifier: cpqhsmsg.dll - 3859 (Hex)0x84350f13 (Service Event) Log Severity: Warning (2) Log Message: Could not enumerate the cluster's resources. The Cluster service may not be running. Try to restart the Cluster service. HPE Insight Management Agents for Servers for Windows...
  • Page 334 Log Severity: Warning (2) Log Message: The Agent could not open the Cluster service. The Cluster service may have been stopped. Try to restart the cluster service. Event identifier: cpqhsmsg.dll - 3871 (Hex)0x84350f1f (Service Event) HPE Insight Management Agents for Servers for Windows...

  • Page 335: Event Identifiers 4352-4626

    Log Severity: Warning (2) Log Message: The Agent could not open the Cluster service registry key. Event identifier: cpqhsmsg.dll - 3872 (Hex)0x84350f20 (Service Event) Log Severity: Warning (2) Log Message: The specified storage class is not supported by the Agent. The Agent only supports the disk resource class.
  • Page 336 Log Message: The External Status MIB Agent could not create an SNMP session. The data contains the error code. Event identifier: cpqhsmsg.dll - 4403 (Hex)0x84351133 (Service Event) Log Severity: Warning (2) Log Message: The External Status MIB Agent SNMP request failed. The data contains the error code. HPE Insight Management Agents for Servers for Windows...
  • Page 337 Log Message: Could not read from the registry sub-key: “%1”. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqhsmsg.dll - 4623 (Hex)0x8435120f (Service Event) HPE Insight Management Agents for Servers for Windows...

  • Page 338: Storage Agents

    Log Severity: Warning (2) Log Message: The Agent could not access WMI. The WMI support may have not been started or installed. Restart or Install WMI service and restart the agents. Event identifier: cpqhsmsg.dll - 4624 (Hex)0x84351210 (Service Event) Log Severity: Warning (2) Log Message: The Agent requires WMI service to be running.
  • Page 339 Log Severity: Warning (2) Log Message: The Storage Agents service could not create the registry key “%1”. The data contains the error code. Event identifier: cpqstmsg.dll - 273 (Hex)0x84350111 (Service Event) Log Severity: Warning (2) HPE Insight Management Agents for Servers for Windows...
  • Page 340 Log Message: Unsupported storage system. The ProLiant storage system %1 is not supported by this version of the Storage Agents. Upgrade the agents to the latest version. Event identifier: cpqstmsg.dll - 527 (Hex)0x8435020f (Service Event) HPE Insight Management Agents for Servers for Windows...

  • Page 341: Event Identifiers 1061-1098

    Log Severity: Warning (2) Log Message: The Drive Array Agent storage system table is full. Event identifier: cpqstmsg.dll - 574 (Hex)0x8435023e (Service Event) Log Severity: Warning (2) Log Message: The Drive Array Agent failed to get capacity on SCSI drive because SCSI pass through IOCTL failed.
  • Page 342 The variable cpqDaSpareStatus indicates the current spare drive status. User Action: If the spare drive status is failed, replace the drive. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqDaSpareStatus • cpqDaSpareCntlrIndex HPE Insight Management Agents for Servers for Windows...
  • Page 343 The current status is represented by the variable cpqDaAccelStatus. User Action: If the accelerator board status is permDisabled(5), you may need to replace the accelerator board. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 344 Symptom: Accelerator Board Battery Failed. This trap indicates that the agent has detected a battery failure associated with the array accelerator cache board. User Action: Replace the Accelerator Cache Board. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 345 Symptom: Logical Drive Statues Change. The Storage Agent has detected a change in the status of a SCSI logical drive. The current logical drive status is indicated in the cpqScsiLogDrvStatus variable. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqScsiLogDrvStatus • cpqScsiLogDrvCntlrIndex • cpqScsiLogDrvBusIndex • cpqScsiLogDrvIndex • cpqScsiLogDrvOsName HPE Insight Management Agents for Servers for Windows...
  • Page 346 User Action: If the fan status is degraded or failed, replace any failed fans. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqSsBoxFanStatus Supporting SNMP Trap Description: “Storage System fan status changed to [cpqSsBoxFanStatus].” NT Event ID: 1076 (Hex)0xc4350434 (cpqstmsg.dll) HPE Insight Management Agents for Servers for Windows...
  • Page 347 Symptom: Storage System temperature OK. The temperature status has been set to OK. The storage system's temperature has returned to normal operating range. It may be reactivated by the administrator. User Action: None. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...

  • Page 348: Event Identifiers 1101-1199

    • sysName • cpqHoTrapFlags • cpqSsBoxTempStatus Supporting SNMP Trap Description: “Storage System temperature ok.” Event identifier: cpqstmsg.dll - 1098 (Hex)0x4435044a (Service Event) Log Severity: Information (1) Log Message: Drive Array Physical Drive Monitoring is not enabled. The physical drive in slot %4, port %5, bay %6 with serial number “%7”, does not have drive threshold monitoring enabled.
  • Page 349 • cpqTapePhyDrvBusIndex • cpqTapePhyDrvScsiIdIndex • cpqTapePhyDrvStatus Supporting SNMP Trap Description: “Status is now [cpqTapePhyDrvStatus].” NT Event ID: 1119 (Hex)0x8435045f (cpqstmsg.dll) Log Severity: Warning (2) Event Title: SCSI Tape Drive Head Needs Cleaning. HPE Insight Management Agents for Servers for Windows...
  • Page 350 User Action: The drive should be scheduled for replacement. For detailed information on a component replacement, see the appropriate Maintenance and Service Guide. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqIdeIdentIndex Supporting SNMP Trap Description: “IDE drive [cpqIdeIdentIndex] has become degraded.” HPE Insight Management Agents for Servers for Windows...
  • Page 351 • cpqSsChassisTime • cpqFcaLogDrvBoxIndex • cpqFcaLogDrvIndex • cpqFcaLogDrvStatus • cpqFcaLogDrvOsName • cpqFcaLogDrvFaultTol • cpqFcaLogDrvSize Supporting SNMP Trap Description: “Status is now [cpqFcaLogDrvStatus].” NT Event ID: 1146 (Hex)0xc435047a (cpqstmsg.dll) Log Severity: Error (3) HPE Insight Management Agents for Servers for Windows...
  • Page 352 The variable cpqFcaSpareBusNumber indicates the SCSI bus number associated with this drive. User Action: If the spare drive status is failed, replace the drive. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqSsChassisName • cpqSsChassisTime • cpqFcaSpareBusNumber HPE Insight Management Agents for Servers for Windows...
  • Page 353 Array Accelerator Cache Board that has lost battery power. If data was being stored in the accelerator memory when the system lost power, that data has been lost. User Action: Verify that no data has been lost. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 354 Symptom: External Array Controller Status Change. This trap indicates that the agent has detected a change in the status of an External Array Controller. The variable cpqFcaCntlrStatus indicates the current controller status. HPE Insight Management Agents for Servers for Windows...
  • Page 355 Log Severity: Warning (2) Event Title: Storage System Power Supply Status Change. Log Message: Storage system “%4” power supply in bay %5 has a new status of %6. SNMP Trap: cpqSsEx2PowerSupplyStatusChange - 8021 in CPQSTSYS.MIB HPE Insight Management Agents for Servers for Windows...
  • Page 356 Supporting SNMP Trap Description: “Storage system power supply UPS status changed to [cpqSsPowerSupplyUpsStatus].” NT Event ID: 1155 (Hex)0x84350483 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Storage System Temperature Sensor Status Change. HPE Insight Management Agents for Servers for Windows...
  • Page 357 Log Message: The SCSI tape library with SCSI target %6 connected to SCSI bus %5 of the controller in slot %4 has recovered from errors. SNMP Trap: cpqTape3LibraryOkay - 5011 in CPQSCSI.MIB Symptom: Tape Library Okay. The Insight Agent has detected that an autoloader unit has recovered from errors. HPE Insight Management Agents for Servers for Windows...
  • Page 358 Log Message: The SCSI tape library with SCSI target %6 connected to SCSI bus %5 of the controller in slot %4 has a closed door and is now operational. SNMP Trap: cpqTape3LibraryDoorClosed - 5014 in CPQSCSI.MIB HPE Insight Management Agents for Servers for Windows...
  • Page 359 User Action: If the board status is generalFailure(3), you may need to replace the controller. If the board status is cableProblem(4), check the cable connections between the controller and the storage system. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqDaCntlrSlot HPE Insight Management Agents for Servers for Windows...
  • Page 360 User Action: If the tape controller status is offline, access to the tape library and tapes has been lost. Check the tape library and all Fibre connections for problems. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags HPE Insight Management Agents for Servers for Windows...
  • Page 361 The variable cpqFcTapeLibraryScsiTarget indicates the SCSI ID of the tape library. User Action: If the tape library door is open, close the tape library door. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags HPE Insight Management Agents for Servers for Windows...
  • Page 362 Symptom: Fibre Channel Tape Drive Cleaning Required trap. The agent has detected a tape drive that needs to have a cleaning tape inserted and run. This causes the tape drive heads to be cleaned. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqFcTapeCntlrWWN HPE Insight Management Agents for Servers for Windows...
  • Page 363 User Action: Check the partner controller for problems. If this was the result of a user initiated switch-over, no action is required. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqSsChassisName • cpqSsChassisTime • cpqFcaCntlrBoxIoSlot HPE Insight Management Agents for Servers for Windows...
  • Page 364 The variable cpqDaTapeLibraryScsiTarget indicates the SCSI ID of the tape library. User Action: If the tape library door is open, close the tape library door. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqDaTapeLibraryCntlrIndex • cpqDaTapeLibraryScsiBus HPE Insight Management Agents for Servers for Windows...
  • Page 365 Symptom: Tape Drive Cleaning Required trap. The agent has detected a tape drive that needs to have a cleaning tape inserted and run. This causes the tape drive heads to be cleaned. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqDaTapeDrvCntlrIndex HPE Insight Management Agents for Servers for Windows...
  • Page 366 Fibre Channel Host Controller. The variable cpqFcaHostCntlrStatus indicates the current controller status. User Action: If the controller status is failed, replace the controller. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqFcaHostCntlrSlot • cpqFcaHostCntlrStatus • cpqFcaHostCntlrModel • cpqFcaHostCntlrWorldWideName HPE Insight Management Agents for Servers for Windows...
  • Page 367 User Action: If the logical drive status is failed(5), examine the array for failed drives that need replacement. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqIdeControllerModel • cpqIdeControllerSlot • cpqIdeLogicalDriveControllerIndex HPE Insight Management Agents for Servers for Windows...
  • Page 368 User Action: If the temperature status is degraded or failed, shut down the storage system as soon as possible. Be sure that the storage system environment is being cooled properly and that no components are overheated. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags HPE Insight Management Agents for Servers for Windows...
  • Page 369 Log Message: The tape library with SCSI target %6 connected to SCSI bus %5 of the controller in slot %4 has a new status of %7. SNMP Trap: cpqTapeLibraryStatusChange - 5018 in CPQSCSI.MIB HPE Insight Management Agents for Servers for Windows...
  • Page 370 • cpqTapePhyDrvBusIndex • cpqTapePhyDrvScsiIdIndex • cpqTapePhyDrvLunIndex • cpqTapePhyDrvName • cpqTapePhyDrvFwRev • cpqTapePhyDrvSerialNumber • cpqTapePhyDrvStatus Supporting SNMP Trap Description: “Status is now [cpqTapePhyDrvStatus].” NT Event ID: 1193 (Hex)0x843504a9 (cpqstmsg.dll) Log Severity: Warning (2) HPE Insight Management Agents for Servers for Windows...
  • Page 371 This causes the tape drive heads to be cleaned. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqFcTapeDriveCntlrIndex • cpqFcTapeDriveScsiBus • cpqFcTapeDriveScsiTarget • cpqFcTapeDriveScsiLun • cpqFcTapeDriveModel • cpqFcTapeDriveFWRev HPE Insight Management Agents for Servers for Windows...
  • Page 372 User Action: If the RSO status is noSecondary(6) or linkDown(7), Be sure that the secondary server is operational and that all cables are connected properly. If the RSO status is secondaryRunningAuto(8) or secondaryRunningUser(9), examine the primary server for failed components. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags HPE Insight Management Agents for Servers for Windows...
  • Page 373 External Tape library. The variable cpqFcTapeLibraryDoorStatus indicates the current tape library door status. User Action: If the tape library door is open, close the tape library door. HPE Insight Management Agents for Servers for Windows...

  • Page 374: Event Identifiers 1200-1294

    Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqFcTapeLibraryCntlrIndex • cpqFcTapeLibraryScsiBus • cpqFcTapeLibraryScsiTarget • cpqFcTapeLibraryScsiLun • cpqFcTapeLibraryModel • cpqFcTapeLibraryFWRev • cpqFcTapeLibrarySerialNumber • cpqFcTapeLibraryLocation • cpqFcTapeLibraryDoorStatus Supporting SNMP Trap Description: “The door is [cpqFcTapeLibraryDoorStatus] for tape library.” NT Event ID: 1199 (Hex)0x843504af (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Drive Array Controller Status Change.
  • Page 375 Log Severity: Warning (2) Event Title: Drive Array Physical Drive Status Change. Log Message: The physical drive in %4, port %5, bay %6 with serial number “%7”, has a new status of %2. HPE Insight Management Agents for Servers for Windows...
  • Page 376 User Action: Replace the physical drive. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqDaCntlrHwLocation • cpqDaPhyDrvCntlrIndex • cpqDaPhyDrvIndex • cpqDaPhyDrvBusNumber • cpqDaPhyDrvBay • cpqDaPhyDrvModel HPE Insight Management Agents for Servers for Windows...
  • Page 377 If data was being stored in the accelerator cache memory when the server lost power, that data has been lost. User Action: Verify that no data has been lost. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags HPE Insight Management Agents for Servers for Windows...
  • Page 378 The variable cpqDaTapeLibraryStatus indicates the current tape library status. The variable cpqDaTapeLibraryScsiTarget indicates the SCSI ID of the tape library. User Action: If the tape library is failed, check the tape library front panel. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags HPE Insight Management Agents for Servers for Windows...
  • Page 379 NT Event ID: 1209 (Hex)0x843504b9 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Drive Array Tape Drive Status Change. Log Message: The tape drive in %4, SCSI bus %5, SCSI target %6 has a new status of %7. HPE Insight Management Agents for Servers for Windows...
  • Page 380 This causes the tape drive heads to be cleaned. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqDaCntlrHwLocation • cpqDaTapeDrvCntlrIndex • cpqDaTapeDrvBusIndex • cpqDaTapeDrvScsiIdIndex • cpqDaTapeDrvLunIndex • cpqDaTapeDrvName • cpqDaTapeDrvFwRev • cpqDaTapeDrvSerialNumber HPE Insight Management Agents for Servers for Windows...
  • Page 381 The variable cpqSsBoxFanStatus indicates the current fan status. User Action: If the fan status is degraded or failed, replace any failed fans. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqSsBoxCntlrHwLocation • cpqSsBoxCntlrIndex • cpqSsBoxBusIndex • cpqSsBoxVendor HPE Insight Management Agents for Servers for Windows...
  • Page 382 The variable cpqSsBoxFltTolPwrSupplyStatus indicates the current power supply status. User Action: If the power supply status is degraded, restore power or replace the failed power supply. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 383 Event Title: Drive Array Physical Drive Status Change. Log Message: The physical drive in %4, %5 with serial number “%7”, has a new status of %2. SNMP Trap: cpqDa7PhyDrvStatusChange - 3046 in CPQIDA.MIB HPE Insight Management Agents for Servers for Windows...
  • Page 384 The variable cpqDaSpareStatus indicates the current spare drive status. User Action: If the spare drive status is failed, replace the drive. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqDaCntlrHwLocation • cpqDaSpareCntlrIndex • cpqDaSparePhyDrvIndex • cpqDaSpareStatus HPE Insight Management Agents for Servers for Windows...
  • Page 385 User Action: If the temperature status is degraded or failed, shut down the storage system as soon as possible. Be sure that the storage system environment is being cooled properly and that no components are overheated. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags HPE Insight Management Agents for Servers for Windows...
  • Page 386 NT Event ID: 1221 (Hex)0x843504c5 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: SAS/SATA Physical Drive Status Change. Log Message: The physical drive in %4, %5 with serial number “%6”, has a new status of %7. HPE Insight Management Agents for Servers for Windows...
  • Page 387 Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqSasHbaHwLocation • cpqSasLogDrvHbaIndex • cpqSasLogDrvIndex • cpqSasLogDrvStatus • cpqSasLogDrvOsName Supporting SNMP Trap Description: “Status is now [cpqSasLogDrvStatus].” NT Event ID: 1223 (Hex)0x843504c7 (cpqstmsg.dll) HPE Insight Management Agents for Servers for Windows...
  • Page 388 User Action: Check the partner controller for problems. If lost communication with the partner controller is the result of a user initiated action, no remedial action is required. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqDaCntlrHwLocation • cpqDaCntlrIndex HPE Insight Management Agents for Servers for Windows...
  • Page 389 Log Message: The physical drive in %4, %5 with serial number "%6", has a new solid state wear status of %7. (Drive status values: 1=other, 2=ok, 3=fiftySixDayThreshold, 4=fivePercentThreshold, 5=twoPercentThreshold, 6=ssdWearOut) SNMP Trap: cpqSasPhyDrvSSDWearStatusChange - 5026 in CPQSCSI.MIB HPE Insight Management Agents for Servers for Windows...
  • Page 390 User Action: If the SSD wear status is ssdWearOut(6), replace the drive. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqDaCntlrHwLocation • cpqDaPhyDrvCntlrIndex • cpqDaPhyDrvIndex • cpqDaPhyDrvLocationString • cpqDaPhyDrvType • cpqDaPhyDrvModel • cpqDaPhyDrvFWRev HPE Insight Management Agents for Servers for Windows...
  • Page 391 Log Severity: Warning (2) Log Message: Could not write the registry subkey: “%1”. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. HPE Insight Management Agents for Servers for Windows...

  • Page 392: Event Identifiers 1343-4613

    Event identifier: cpqstmsg.dll - 1283 (Hex)0x84350503 (Service Event) Log Severity: Warning (2) Log Message: Could not read the registry subkey: “%1”. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqstmsg.dll - 1284 (Hex)0x84350504 (Service Event) Log Severity: Warning (2) Log Message: Could not write the registry subkey: “%1”.
  • Page 393 This can be caused by a failure in the Remote Access Service or by a missing or invalid configuration. Use the HPE Insight Management Agents control panel to verify the Asynchronous Management configuration settings. Use the Network control panel to verify the Remote Access configuration.
  • Page 394 Log Severity: Warning (2) Log Message: The IDE Agent got an unexpected error code while waiting for multiple events. The data contains the error code. Event identifier: cpqstmsg.dll - 3599 (Hex) 0x84350e0f (Service Event) HPE Insight Management Agents for Servers for Windows...
  • Page 395 Log Message: Could not read the registry subkey: “%1”. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqstmsg.dll - 4612 (Hex) 0x84351204 (Service Event) Log Severity: Warning (2) HPE Insight Management Agents for Servers for Windows...

  • Page 396: Server Agents

    Log Message: Could not read the registry subkey: “%1”. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqstmsg.dll - 4613 (Hex) 0x84351205 (Service Event) Log Severity: Warning (2) Log Message: Could not read the registry subkey: “%1”.
  • Page 397 Log Message: The Server Agents service encountered a fatal error. The service is terminating. The data contains the error code. Event identifier: cpqsvmsg.dll - 400 (Hex)0x44350190 (Service Event) Log Severity: Information (1) Log Message: The Server Agents service version %1 has started. HPE Insight Management Agents for Servers for Windows...
  • Page 398 Symptom: A cache accelerator parity error indicates that a cache module needs to be replaced. The error information is reported in the variable cpqHeEventLogErrorDesc. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags HPE Insight Management Agents for Servers for Windows...

  • Page 399: Event Identifiers 1025-1092

    Supporting SNMP Trap Description: “Cache Accelerator errors may require a replacement module.” Event Identifiers 1025-1092 NT Event ID: 1025 (Hex)0x84350401 (cpqsvmsg.dll) Log Severity: Warning (2) Log Message: The Advanced Memory Protection subsystem has detected a memory fault. The Online Spare Memory has been activated.
  • Page 400 Log Message: The Fan Sub-system has returned to a redundant state. SNMP Trap: cpqHe3FltTolFanRedundancyRestored - 6055 in CPQHLTH.MIB Symptom: The Fault Tolerant Fans have returned to a redundant state for the specified chassis. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 401 Value 0 for CPU means memory is not processor- based. User Action: Be sure that the board, cartridge, or riser memory is installed correctly, and then re-install the memory board, cartridge, or processor. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 402 Value 0 for CPU means memory is not processor- based. User Action: Replace the indicated board or cartridge or Riser. SNMP Trap Data: • sysName, • cpqHoTrapFlags • cpqHeResMem2BoardSlotNum HPE Insight Management Agents for Servers for Windows...
  • Page 403 Symptom: The fault tolerant power supply AC power loss for the specified chassis and bay location. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqHeFltTolPowerSupplyChassis • cpqHeFltTolPowerSupplyBay • cpqHeFltTolPowerSupplyStatus • cpqHeFltTolPowerSupplyModel • cpqHeFltTolPowerSupplySerialNumber • cpqHeFltTolPowerSupplyAutoRev • cpqHeFltTolPowerSupplyFirmwareRev • cpqHeFltTolPowerSupplySparePartNum • cpqSiServerSystemId HPE Insight Management Agents for Servers for Windows...
  • Page 404 Symptom: The temperature status has been set to degraded. The server's temperature is outside of the normal operating range. The server is shut down if the cpqHeThermalDegradedAction variable is set to shutdown (3). Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 405 '%4'. SNMP Trap: cpqHe3ThermalSystemFanDegraded - 6021 in CPQHLTH.MIB Symptom: The system fan status has been set to degraded. An optional system fan is not operating normally. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 406 Symptom: The CPU fan status has been set to OK. Any previously non-operational processor fans have returned to normal operation. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags Supporting SNMP Trap Description: “CPU fan is now OK.” HPE Insight Management Agents for Servers for Windows...

  • Page 407: Event Identifiers 1103-1183

    NT Event ID: 1090 (Hex)0x44350442 (cpqsvmsg.dll) Log Severity: Information (1) Log Message: The server is operational again. The server has previously been shut down by the Automatic Server Recovery (ASR) feature and has just become operational again. SNMP Trap: cpqHe3AsrConfirmation - 6025 in CPQHLTH.MIB Symptom: The server is operational again.
  • Page 408 Log Message: The Remote Insight Board has detected self test error '%4'. SNMP Trap: cpqSm2SelfTestError - 9005 in CPQSM2.MIB Symptom: Remote Insight/Integrated Lights-Out Self Test Error. The Remote Insight/Integrated Lights-Out firmware has detected a Remote Insight self test error. HPE Insight Management Agents for Servers for Windows...
  • Page 409 Symptom: Keyboard Cable Disconnected. The Remote Insight keyboard cable has been disconnected. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags Supporting SNMP Trap Description: “Remote Insight keyboard cable disconnected.” NT Event ID: 1114 (Hex)0x8435045a (cpqsvmsg.dll) HPE Insight Management Agents for Servers for Windows...
  • Page 410 Supporting SNMP Trap Description: “Processor in Slot [cpqSeCpuSlot] status change to [cpqSeCpuStatus].” SNMP Trap: cpqSeCpuPowerPodstatusChange - 1007 in CPQSTDEQ.MIB Symptom: This Trap is sent if CPU Power Pod status changes. User Action: None. HPE Insight Management Agents for Servers for Windows...
  • Page 411 Log Message: The Remote Insight Board has detected that the mouse cable is disconnected. SNMP Trap: cpqSm2MouseCableDisconnected - 9009 in CPQSM2.MIB Symptom: Mouse Cable Disconnected. The Remote Insight mouse cable has been disconnected. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 412 • cpqSiServerSystemId Supporting SNMP Trap Description: “The Power Supply is OK on Chassis [cpqHeFltTolPowerSupplyChassis], Bay [cpqHeFltTolPowerSupplyBay], Status [cpqHeFltTolPowerSupplyStatus], Model [cpqHeFltTolPowerSupplyModel], Serial Num [cpqHeFltTolPowerSupplySerialNumber], Firmware [cpqHeFltTolPowerSupplyFirmwareRev].” NT Event ID: 1123 (Hex)0x84350463 (cpqsvmsg.dll) HPE Insight Management Agents for Servers for Windows...
  • Page 413 Log Severity: Error (3) Log Message: The Fault Tolerant Power Supply Sub-system is in a failed state. Restore power or replace the failed power supply. SNMP Trap: cpqHe4FltTolPowerSupplyFailed - 6050 in CPQHLTH.MIB HPE Insight Management Agents for Servers for Windows...
  • Page 414 Log Message: Fault Tolerant Power Supply Inserted. A hot-plug fault tolerant power supply has been inserted into the system. SNMP Trap: cpqHe3FltTolPowerSupplyInserted - 6033 in CPQHLTH.MIB Symptom: A Fault Tolerant Power Supply has been inserted into the specified chassis and bay location. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 415 Log Message: The Fan Sub-system is in a failed state. Replace the fan. SNMP Trap: cpqHe3FltTolFanFailed - 6036 in CPQHLTH.MIB Symptom: The Fault Tolerant Fan condition has been set to failed for the specified chassis and fan. HPE Insight Management Agents for Servers for Windows...
  • Page 416 Log Message: Fan Removed. A hot-plug fan has been removed from the system. SNMP Trap: cpqHe3FltTolFanRemoved - 6039 in CPQHLTH.MIB Symptom: A Fault Tolerant Fan has been removed from the specified chassis and fan location. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 417 • sysName • cpqHoTrapFlags • cpqHeThermalDegradedAction • cpqHeTemperatureChassis • cpqHeTemperatureLocale Supporting SNMP Trap Description: “Temperature out of range on Chassis [cpqHeTemperatureChassis], Location [cpqHeTemperatureLocale]. Shutdown may occur.” NT Event ID: 1136 (Hex)0x44350470 (cpqsvmsg.dll) HPE Insight Management Agents for Servers for Windows...
  • Page 418 SNMP Trap: cpqHe3PowerConverterFailed - 6044 in CPQHLTH.MIB Symptom: The DC-DC Power Converter condition has been set to failed for the specified chassis, slot, and socket. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqHePwrConvChassis HPE Insight Management Agents for Servers for Windows...
  • Page 419 Log Message: Hot Plug PCI Board Inserted. A hot plug PCI adapter has been inserted into the system. SNMP Trap: cpqSiHotPlugSlotBoardInserted - 2009 in CPQSINFO.MIB Symptom: Hot Plug Slot Board Inserted. A Hot Plug Slot Board has been inserted into the specified chassis and slot. HPE Insight Management Agents for Servers for Windows...
  • Page 420 Each of the server blades in each of the enclosure within the rack is updated to reflect the new rack name. It may take several minutes for the rack name change to be propagated throughout the entire rack. User Action: None. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqRackName HPE Insight Management Agents for Servers for Windows...
  • Page 421 SNMP Trap: cpqRackEnclosureRemoved - 22003 in CPQRACK.MIB Symptom: The enclosure has been removed. This trap indicates that an enclosure has been removed from the rack. User Action: None. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqRackName HPE Insight Management Agents for Servers for Windows...
  • Page 422 SNMP Trap: cpqRackEnclosureTempFailed - 22005 in CPQRACK.MIB Symptom: The enclosure temperature status has been set to failed. This trap indicates that an enclosure temperature sensor has been tripped, indicating an overheat condition. HPE Insight Management Agents for Servers for Windows...
  • Page 423 • cpqRackCommonEnclosureSerialNum • cpqRackCommonEnclosureTempLocation • cpqRackCommonEnclosureSparePartNumber • cpqRackCommonEnclosureTrapSequenceNum Supporting SNMP Trap Description: “The enclosure [cpqRackCommonEnclosureName] temperature sensor in rack [cpqRackName] has been set to degraded.” NT Event ID: 1149 (Hex)0x4435047d (cpqsvmsg.dll) HPE Insight Management Agents for Servers for Windows...
  • Page 424 This may result in the enclosure overheating. User Action: Replace the fan as soon as possible. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqRackName • cpqRackUid • cpqRackCommonEnclosureName • cpqRackCommonEnclosureSerialNum • cpqRackCommonEnclosureFanLocation HPE Insight Management Agents for Servers for Windows...
  • Page 425 Symptom: The enclosure fan status has been set to OK. This trap indicates that an enclosure fan has returned to normal operation. User Action: None. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags HPE Insight Management Agents for Servers for Windows...
  • Page 426 Event Title: Rack Enclosure Fan Inserted Log Message: The enclosure fan has been inserted. SNMP Trap: cpqRackEnclosureFanInserted - 22012 in CPQRACK.MIB Symptom: The enclosure fan has been inserted. User Action: None. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 427 Supporting SNMP Trap Description: “The power supply [cpqRackPowerSupplyPosition] in enclosure [cpqRackPowerSupplyEnclosureName] in rack [cpqRackName] has been set to failed.” NT Event ID: 1156 (Hex)0x84350484 (cpqsvmsg.dll) Log Severity: Warning (2) Event Title: Rack Power Supply Degraded HPE Insight Management Agents for Servers for Windows...
  • Page 428 Symptom: The power supply status has been set to OK. This trap indicates that a power supply has returned to normal operation. User Action: None. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqRackName • cpqRackUid • cpqRackPowerSupplyEnclosureName • cpqRackPowerSupplySerialNum • cpqRackPowerSupplyPosition • cpqRackPowerSupplyFWRev HPE Insight Management Agents for Servers for Windows...
  • Page 429 Event Title: Rack Power Supply Inserted Log Message: The power supply has been inserted. SNMP Trap: cpqRackPowerSupplyInserted - 22017 in CPQRACK.MIB Symptom: The power supply has been inserted. User Action: None. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 430 Event Title: Rack Power Subsystem Input Voltage Problem Log Message: The rack power supply detected an input line voltage problem. SNMP Trap: cpqRackPowerSubsystemLineVoltageProblem - 22019 in CPQRACK.MIB Symptom: The rack power supply detected an input line voltage problem. HPE Insight Management Agents for Servers for Windows...
  • Page 431 • cpqRackPowerEnclosureName • cpqRackCommonEnclosureSparePartNumber • cpqRackCommonEnclosureSerialNum • cpqRackCommonEnclosureTrapSequenceNum Supporting SNMP Trap Description: “The power subsystem in enclosure [cpqRackPowerEnclosureName] in rack [cpqRackName] is in an overload condition.” NT Event ID: 1163 (Hex)0xc435048b (cpqsvmsg.dll) HPE Insight Management Agents for Servers for Windows...
  • Page 432 User Action: Check power connections or add power supplies. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqRackName • cpqRackUid • cpqRackServerBladeEnclosureName • cpqRackServerBladePosition • cpqRackServerBladeSparePartNumber • cpqRackCommonEnclosureSerialNum • cpqRackCommonEnclosureTrapSequenceNum HPE Insight Management Agents for Servers for Windows...
  • Page 433 User Action: Check server enclosure connections or add power supplies. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqRackName • cpqRackUid • cpqRackServerBladeEnclosureName • cpqRackServerBladePosition HPE Insight Management Agents for Servers for Windows...
  • Page 434 SNMP Trap: cpqRackServerPowerOnManualOverride - 22026 in CPQRACK.MIB Symptom: Server power on via manual override. The server blade was powered on by a manual override. User Action: None. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags HPE Insight Management Agents for Servers for Windows...
  • Page 435 Log Message: The server blade has been removed from the enclosure. SNMP Trap: cpqRackServerBladeRemoved - 22028 in CPQRACK.MIB Symptom: Server blade removed. The server blade has been removed from the enclosure. User Action: None. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 436 Supporting SNMP Trap Description: “Server blade [cpqRackServerBladeName] inserted into position [cpqRackServerBladePosition], in enclosure [cpqRackServerBladeEnclosureName], in rack [cpqRackName].” NT Event ID: 1172 (Hex)0x84350494 (cpqsvmsg.dll) Log Severity: Warning (2) Event Title: Rack Power Subsystem Not Load Balanced HPE Insight Management Agents for Servers for Windows...
  • Page 437 • cpqRackUid • cpqRackCommonEnclosureName • cpqRackCommonEnclosureSerialNum • cpqRackCommonEnclosureSparePartNumber • cpqRackCommonEnclosureTrapSequenceNum Supporting SNMP Trap Description: “Power subsystem DC power problem in enclosure [cpqRackCommonEnclosureName], in rack [cpqRackName].” NT Event ID: 1174 (Hex)0x84350496 (cpqsvmsg.dll) HPE Insight Management Agents for Servers for Windows...
  • Page 438 Supporting SNMP Trap Description: “Unknown power consumption in rack [cpqRackName].” NT Event ID: 1176 (Hex)0x84350498 (cpqsvmsg.dll) Log Severity: Warning (2) Event Title: Power Subsystem Load Balancing Wire Missing Log Message: The power subsystem load balancing wire missing. HPE Insight Management Agents for Servers for Windows...
  • Page 439 Supporting SNMP Trap Description: “Power subsystem has too may power enclosures [cpqRackCommonEnclosureName], in rack [cpqRackName].” NT Event ID: 1178 (Hex)0x8435049a (cpqsvmsg.dll) Log Severity: Warning (2) Event Title: Power Subsystem Configuration Error HPE Insight Management Agents for Servers for Windows...
  • Page 440 SNMP Trap: cpqHeManagementProcReady - 6062 in CPQHLTH.MIB Symptom: The Management processor is ready. The management processor has successfully reset and is now available again. User action: None Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...
  • Page 441 Log Message: USB storage device '%5' removed. The data contains the error code. SNMP TRAP: 1009 in CPQSTDEQ.MIB Symptom: The USB key has been removed from the server. User Action: None required. Supporting SNMP Trap Data: HPE Insight Management Agents for Servers for Windows...

  • Page 442: Event Identifiers 1539-3352

    • sysName • cpqHoTrapFlags • cpqSeUSBDeviceType • cpqSeUSBDeviceName Supporting SNMP Trap Description: This trap is sent when a attached USB storage device is removed. Symbolic Name: CPQ_STD_USB_DEV_REMOVED Event Identifiers 1539-3352 Event identifier: cpqsvmsg.dll - 1539 (Hex)0xc4350603 (Service Event) Log Severity: Error (3) Log Message: Unable to write to the registry.
  • Page 443 Log Message: Could not read the registry sub-key: “%1”. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqsvmsg.dll - 3333 (Hex)0x84350d05 (Service Event) Log Severity: Warning (2) HPE Insight Management Agents for Servers for Windows...

  • Page 444: Event Identifiers 5632-5684

    Log Message: Could not read the registry sub-key: “%1”. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqsvmsg.dll - 3342 (Hex)0x84350d0e (Service Event) Log Severity: Warning (2) Log Message: The Remote Insight Agent got an unexpected error code while waiting for multiple events.
  • Page 445 Log Severity: Warning (2) Log Message: The Rack And Enclosure MIB Agent could not set the variable because the value is invalid or out of range. The data contains the error code. HPE Insight Management Agents for Servers for Windows...

  • Page 446: Nic Agents

    Event identifier: cpqsvmsg.dll - 5684 (Hex)0x84351634 (Service Event) Log Severity: Warning (2) Log Message: The Rack And Enclosure MIB Agent is not loaded. Sets are not available. The data contains the error code. NIC agents Event Identifiers 256-299 Event identifier: cpqnimsg.dll - 256 (Hex)0x84350100 (Service Event) Log Severity: Warning (2) Log Message: The NIC Management Agent detected an error.
  • Page 447 Log Message: There were no physical adapters in team: “%1.” This error can be caused by improperly installed drivers. Remove all device instances associated with the team and re-install the drivers and team. Event identifier: cpqnimsg.dll - 274 (Hex)0x84350112 (Service Event) Log Severity: Warning (2) HPE Insight Management Agents for Servers for Windows...
  • Page 448 Event identifier: cpqnimsg.dll - 290 (Hex)0x84350122 (Service Event) Log Severity: Warning (2) Log Message: The NIC Agent service could not start agent “%1”. The data contain the error code. Event identifier: cpqnimsg.dll - 291 (Hex)0x84350123 (Service Event) HPE Insight Management Agents for Servers for Windows...

  • Page 449: Event Identifiers 300-1293

    Log Severity: Warning (2) Log Message: The NIC Agent service detected an invalid state for agent *”%1”. The data contain the state. Event identifier: cpqnimsg.dll - 292 (Hex)0x84350124 (Service Event) Log Severity: Warning (2) Log Message: The NIC Agent service could not stop agent “%1”. The data contain the error code. Event identifier: cpqnimsg.dll - 293 (Hex)0x84350125 (Service Event) Log Severity: Warning (2) Log Message: The NIC Agent service could not terminate agent “%1”.
  • Page 450 Log Message: Unable to load a required library. This error can be caused by a corrupt or missing file. Reinstalling the Insight Agents or running the Emergency Repair procedure may correct this error. Event identifier: cpqnimsg.dll - 1036 (Hex)0x8435040c (Service Event) Log Severity: Warning (2) HPE Insight Management Agents for Servers for Windows...
  • Page 451 Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqNicIfPhysAdapterSlot • cpqNicIfPhysAdapterPort • cpqNicIfLogMapAdapterOKCount Supporting SNMP Trap Description: “Redundancy increased by adapter in slot [cpqNicIfPhysAdapterSlot], port [cpqNicIfPhysAdapterPort].” NT Event ID: 1283 (Hex)0xc4350503 (cpqnimsg.dll) HPE Insight Management Agents for Servers for Windows...
  • Page 452 User Action: None required. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqNicIfPhysAdapterSlot • cpqNicIfPhysAdapterPort • cpqSiServerSystemId • cpqNicIfPhysAdapterStatus • cpqSePciSlotBoardName • cpqNicIfPhysAdapterPartNumber • ipAdEntAddr • cpqNicIfLogMapIPV6Address HPE Insight Management Agents for Servers for Windows...
  • Page 453 Failed condition. The cpqNicConnectivityRestored trap is sent instead. This can be caused by replacing of a faulty cable or connecting a cable that was disconnected. User Action: None required. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqNicIfPhysAdapterSlot HPE Insight Management Agents for Servers for Windows...
  • Page 454 • cpqNicIfPhysAdapterSlot • cpqNicIfPhysAdapterPort • cpqSiServerSystemId • cpqNicIfPhysAdapterStatus • cpqSePciSlotBoardName • cpqNicIfPhysAdapterPartNumber • ipAdEntAddr • cpqNicIfLogMapIPV6Address • cpqNicIfLogMapAdapterOKCount Supporting SNMP Trap Description: “Redundancy decreased by adapter in slot [cpqNicIfPhysAdapterSlot], port [cpqNicIfPhysAdapterPort].” HPE Insight Management Agents for Servers for Windows...

  • Page 455: Support And Other Resources

    Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: http://www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: http://www.hpe.com/support/hpesc Information to collect •...

  • Page 456: Customer Self Repair

    IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. You must have an HPE Passport set up with relevant entitlements. Customer self repair Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience.

  • Page 457: Regulatory Information

    Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.

  • Page 458: Acronyms And Abbreviations

    DHCP Dynamic Host Configuration Protocol domain name system environment variable FBWC flash-backed write cache host bus adapter HPE SSA HPE Smart Storage Administrator Integrated Lights-Out Integrated Management Log Integrated Remote Console nonmaskable interrupt network time protocol NVRAM nonvolatile memory POST...
  • Page 459 Power-On Self-Test QuickPath Interconnect RBSU ROM-Based Setup Utility RIBCL Remote Insight Board Command Language reserve information sector serial attached SCSI SATA serial ATA SMART self-monitoring analysis and reporting technology SR-IOV Single root I/O Virtualization solid-state drive Secure Shell Secure Sockets Layer single sign-on Service Pack for ProLiant Selective Storage Presentation...
  • Page 460 Virtual Connect Acronyms and abbreviations...

Table of Contents

Save PDF