Page 1: Troubleshooting Guide
Abstract This guide provides a list of error messages associated with HP ProLiant servers, HP Integrated Lights-Out, HP Smart Array storage, HP Onboard Administrator, HP 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 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Page 3: Table Of Contents
Contents Introduction ..........................8 Overview ..............................8 Troubleshooting resources ........................8 HP ProLiant server errors ........................ 9 ADU error messages ............................. 9 Introduction to ADU error messages ..................... 9 ADU version 8.0 through 8.28 error messages ................... 29 POST error messages and beep codes ......................39 Introduction to POST error messages ....................
Page 4 Message ID: 4169 ........................... 98 Message ID: 4190 ........................... 98 HP ProLiant Gen9 power fault LEDs ..................... 100 Power fault LEDs ............................100 HP Smart Array errors ....................... 101 Controller runtime LEDs ..........................101 P440ar controller LEDs ........................101 P440 controller LEDs ........................102 P441 controller LEDs ........................
Page 5 Unable to connect to the iLO IP address .................... 246 Blocked iLO ports ........................... 246 Troubleshooting alert and trap issues ......................246 Unable to receive HP SIM alarms (SNMP Traps) from iLO ..............246 Unable to login with emergency access .................... 246 Incorrect authentication code ......................247 Troubleshooting directory issues .........................
Page 6 Unable to pass data through an SSH terminal ................... 254 Troubleshooting miscellaneous issues ......................254 Cookie sharing between browser instances and iLO ................254 Unable to get SNMP information from HP SIM .................. 256 Unable to upgrade iLO firmware ..................... 256 iLO network failed flash recovery ..................... 257 Issues generating a keytab using ktpass.exe ..................
Page 7 NIC agents .............................. 389 Event Identifiers 256-299 ........................ 389 Event Identifiers 300-1293 ......................393 Support and other resources ...................... 399 Before you contact HP ..........................399 HP contact information ..........................399 Acronyms and abbreviations ...................... 400 Documentation feedback ......................404 Index ............................
Page 8: Introduction
Introduction Overview This guide is part of a two volume set. Volume I, the HP ProLiant Gen9 Troubleshooting Guide, Volume I: Troubleshooting provides procedures for resolving common problems. This 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 9: Hp Proliant Server Errors
Description: Number of times that write memory parity errors were detected during transfers to memory on the array accelerator board. Action: If many parity errors occurred, you may need to replace the array accelerator board. HP ProLiant server errors 9...
Page 10 Description: The number of cache lines experiencing excessive ECC errors has reached a preset limit. Therefore, the cache has been shut down. Action: Reseat the cache to the controller. If the problem persists, replace the cache. HP ProLiant server errors 10...
Page 11 Description: Array accelerator board has been permanently disabled. It will remain disabled until it is reinitialized using HP SSA. Action: Check the Disable Code field. Run HP SSA to reinitialize the array accelerator board. Accelerator Status: Possible Data Loss in Cache Description: Possible data loss was detected during power-up due to all batteries being below sufficient voltage level and no presence of the identification signatures on the array accelerator board.
Page 12: Array Accelerator Battery Pack X Not Fully Charged
Description: Cache has been disabled due to a large number of ECC errors detected while testing the cache during POST. This is probably caused by a loose pin on one of the RAM chips. Action: Try reseating the cache to the controller. If that does not work, replace the cache. HP ProLiant server errors 12...
Page 13: Configuration Signature Is Zero
Action: Look for messages indicating which drives have been moved. If no messages are displayed and drive swapping did not occur, run HP SSA to configure the controller and run the server setup utility to configure NVRAM. Do not run either utility if you believe drive swapping has occurred.
Page 14: Controller Restarted With A Signature Of Zero
Description: The issuing of the Accelerator Disable command has disabled posted-writes. This occurred because of an operating system device driver. Action: Restart the system. Run HP SSA to reinitialize the array accelerator board. Drive (Bay) X Firmware Needs Upgrading Description: Firmware on this physical drive is below the latest recommended version.
Page 15 Action: CAUTION: Do not run the server setup utility and try to reconfigure, or data will be lost. Power down the server. Replace the drive that was incorrectly replaced. Replace the original drive that failed. HP ProLiant server errors 15...
Page 16: Drive Monitoring Features Are Unobtainable
Error Occurred Reading RIS Copy from SCSI Port X Drive ID Description: An error occurred while ADU was trying to read the RIS from this drive. Action: HP stores the hard drive configuration information in the RIS. If multiple errors occur, the drive may need to be replaced.
Page 17: Identify Logical Drive Data Did Not Match With Nvram
Logical Drive X Failed Due to Cache Error Description: This logical drive failed due to a catastrophic cache error. Action: Replace the array accelerator board and reconfigure it using HP SSA. Logical Drive X Status = Failed Description: This status could be issued for several reasons: •...
Page 18 Description: A physical drive in this logical drive has failed and has now been replaced. The replaced drive is rebuilding from the mirror drive or the parity data. Action: No action is required. Normal operations can occur; however, performance will be less than optimal until after the rebuild process completes. HP ProLiant server errors 18...
Page 19: Mirror Data Miscompare
No Configuration for Array Accelerator Board Description: The array accelerator board has not been configured. Action: If the array accelerator board is present, run HP SSA to configure the board. One or More Drives is Unable to Support Redundant Controller Operation Description: At least one drive in use does not support redundant controller operation.
Page 20: Other Controller Indicates Different Hardware Model
Description: If a processor has an unsupported stepping, it is not started, and this message is displayed. Processor Not Supported (Unsupported Core Speed) Description: If a processor has a core speed that is incompatible with the other installed processors, the processor is not started, and this message is displayed. HP ProLiant server errors 20...
Page 21: Ris Copies Between Drives Do Not Match
If drives or arrays were moved, be sure the movement follows the guidelines listed in the documentation for the array controller. If the error persists after completing steps 1 through 4, contact an HP authorized service provider. SCSI Port X Drive ID Y Failed - REPLACE (failure message) Description: ADU detected a drive failure.
Page 22: Set Configuration Command Issued
Description: ADU has determined that the controller is running firmware that has been soft upgraded by the Upgrade Utility. However, the firmware running is not present on all drives. This could be caused by the addition of new drives in the system. Action: Update all drives to the latest firmware version. HP ProLiant server errors 22...
Page 23: Storage Enclosure On Scsi Bus X Indicated A Door Alert
Storage Enclosure on SCSI Bus X Indicated that the Fan is Degraded..SOLUTION: this condition usually occurs on enclosures with multiple fans and one of those fans has failed. Replace any fans not operating properly. HP ProLiant server errors 23...
Page 24: Storage Enclosure On Scsi Bus X Indicated That The Fan Module Is Unplugged
Description: One or more drive locations were changed while an expand operation was in progress. Action: Power down the server. Place the drives in their original locations. Restart the server, and then complete the expand operation. Move the drives to their new locations after the expand operation is completed. HP ProLiant server errors 24...
Page 25 Action: Identify the drives containing lost volumes, and then move them to another controller so the lost volumes can be recreated. CAUTION: Removing a drive that contains valid volume data causes all valid data to be lost. HP ProLiant server errors 25...
Page 26: System Board Is Unable To Identify Which Slots The Controllers Are In
...SOLUTION: Power down the system. Verify that the controller is fully seated. Then power the system on and look for helpful error messages displayed by the controller. If this doesn’t help, contact your HP service provider. HP ProLiant server errors 26...
Page 27: Unknown Disable Code
Restart the server. Resolve any error messages displayed by the controller. If this does not solve the problem, contact an HP authorized service provider. Unknown Disable Code Description: A code was returned from the array accelerator board that ADU does not recognize.
Page 28: Write Memory Error
ADU, and (2) the type of adapter last configured in EISA NVRAM. Action: Check the diagnosis screen for other error messages. Run the server setup utility to update the system configuration. HP ProLiant server errors 28...
Page 29: Adu Version 8.0 Through 8.28 Error Messages
Action: Adjust the memory installed in the array accelerators to matching sizes. Array Accelerator: The cache is disabled because the restore operation from flash memory failed. Action: Reseat the controller cache module. If the problem persists, contact HP support ("HP contact information" on page 399).
Page 30 399). Array Accelerator: This controller's firmware is not backward compatible with the cache module revision. Action: Upgrade the controller to the latest firmware. If the problem persists, contact HP support ("HP contact information" on page 399). Array status: The array has failed.
Page 31 If this doesn't solve the problem, power down the server and move the drives back to the original controller. • If this message is observed without any drive movement, check if the cache module has failed and replace it if required. If the problem persists, contact HP support ("HP contact information" on page 399).
Page 32 If this doesn't solve the problem, power down the server and move the drives back to the original controller. • If this message is observed without any drive movement, check if the cache module has failed and replace it if required. If the problem persists, contact HP support ("HP contact information" on page 399).
Page 33 Drive Offline due to Erase Operation: The physical drive is offline and the erase process has been failed..The drive may now be brought online through the re-enable erased drive command in HP SSA. Action: Re-enable the physical drive using HP SSA.
Page 34 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 HP SSA. Action: Re-enable the physical drive using HP SSA.
Page 35 ...as well as a high stripe size value such that a controller lock up could occur. It is recommended that the stripe size be migrated to a lower value. Action: Migrate the stripe size to a lower value using the HP SSA. NVRAM Error: Board ID could not be read...
Page 36 Also, check if the cache module is installed. Install the cache module if not present. If this doesn't solve the problem, power down the server and move the drives back to the original controller. HP ProLiant server errors 36...
Page 37 • If this message is observed without any drive movement, check if the cache module has failed and replace it if required. If the problem persists, contact HP support ("HP contact information" on page 399). Redundancy State: This controller has been setup to be part of a redundant pair of controllers..
Page 38 Storage Enclosure: Warning: The enclosure is reporting a high temperature status. Action: Be sure that all fans are connected and operating properly. Replace any defective fans. For better airflow, remove any dust buildup from fans or other areas. If the problem persists, contact HP support ("HP contact information"...
Page 39: Post Error Messages And Beep Codes
Possible Cause: This message indicates Mirrored Memory is enabled and indicates the amount of memory reserved for this feature. Action: None. Advanced Memory Protection mode: RAID memory with Advanced ECC ...Xxxx MB System memory and xxxx MB memory reserved for RAID. HP ProLiant server errors 39...
Page 40: Fatal Dma Error
Audible Beeps: None Possible Cause: A PCI Express port has experienced a fatal error that caused an NMI. Action: Run Insight Diagnostics and replace the failed PCI Express boards or reseat loose PCI Express boards. HP ProLiant server errors 40...
Page 41: Fatal Global Protocol Error
High Temperature Condition detected by Processor X Audible Beeps: None Possible Cause: Ambient temperature exceeds recommended levels, fan solution is insufficient, or fans have failed. Action: Adjust the ambient temperature, install fans, or replace the failed fans. HP ProLiant server errors 41...
Page 42: Ilo Generated Nmi
Action: Enter a valid password to access the system. Invalid Password - System Restricted! Audible Beeps: None Possible Cause: A valid password that does not have permissions to access the system has been entered. Action: Enter a valid password with the correct permissions. HP ProLiant server errors 42...
Page 43: Network Server Mode Active And No Keyboard Attached
Action: Install supported power supplies in a supported configuration. For supported power supply configurations, see the server documentation on the HP website (http://www.hp.com/support). Mixed processor speeds detected. Please make sure that all processors are the same speed.
Page 44: No Floppy Drive Present
Action: For plug-in PCI cards, remove the card. For embedded PCI devices, run Insight Diagnostics and replace any failed components as indicated. Power Fault Detected in Hot-Plug PCI Slot X Possible Cause: A PCI-X hot-plug expansion slot was not powered up properly. Action: Reboot the server. HP ProLiant server errors 44...
Page 45: Power Supply Solution Not Fully Redundant
CAUTION: Before removing or replacing any processors, be sure to follow the guidelines provided in "Performing processor procedures in the troubleshooting process" provided in the HP ProLiant Gen9 Troubleshooting Guide: Volume 1, Troubleshooting. Failure to follow the recommended guidelines can cause damage to the system board, requiring replacement of the system board.
Page 46: This Dimm Does Not Support Thermal Monitoring
Audible beeps: None Possible cause: Intel Trusted Execution Technology has indicated an error during the previous attempt at trusted boot. Action: Check the error code in the Intel documentation. For more information, see the Intel website (http://www.intel.com). HP ProLiant server errors 46...
Page 47: Unsupported Pci Card Detected Remove Pci Card From Slot
Possible Cause: The power supply in bay X is not supported by the server. Action: Install a supported power supply in bay X. For supported power supplies, see the server documentation on the HP website (http://www.hp.com/support). Unsupported Processor Detected System will ONLY boot ROMPAQ Utility. System Halted.
Page 48 Before removing or replacing any processors, be sure to follow the guidelines provided in "Performing processor procedures in the troubleshooting process." Failure to follow the recommended guidelines can cause damage to the system board, requiring replacement of the system board. Correct the processor configuration. HP ProLiant server errors 48...
Page 49: 100 Series
The system will run in Full Performance mode. Audible Beeps: None Possible Cause: The system is configured for HP Static Low mode and the current processor cannot support this mode. Action: For more information about the Power Regulator for ProLiant option, see the HP ROM-Based Setup Utility User Guide on the Documentation CD or the HP website (http://www.hp.com/support/smartstart/documentation).
Page 50: Asr Timer Failure
Possible Cause: 8237 DMA controllers, 8254 timers, and similar devices. CAUTION: Only authorized technicians trained by HP should attempt to remove the system board. If you believe the system board requires replacement, contact HP Technical Support ("HP contact information" on page 399) before proceeding.
Page 51: Series
CAUTION: Before removing or replacing any processors, be sure to follow the guidelines provided in "Performing processor procedures in the troubleshooting process" provided in the HP ProLiant Gen9 Troubleshooting Guide: Volume 1, Troubleshooting. Failure to follow the recommended guidelines can cause damage to the system board, requiring replacement of the system board.
Page 52 System Halted. Possible Cause: DIMMs are installed in pairs, but the server is in single channel memory mode. Action: Remove all other DIMMs or install memory in valid pairs and change the memory mode. HP ProLiant server errors 52...
Page 53: Invalid Lockstep Memory Configuration
209-RAID Memory Configuration - Memory Sizes on boards X and Y do not match Possible Cause: The overall size of two boards participating in a RAID does not match. Action: Install or reinstall DIMMs to support RAID mode. HP ProLiant server errors 53...
Page 54 ...System video output may have additional information regarding failure. The system is halted. 228- DIMM Configuration Error - Processor X, Channel Y - Memory channel not populated in correct order. See User Guide HP ProLiant server errors 54...
Page 55: 229-234 Dimm Configuration Error
Action: Remove server battery for at least 1 minute to allow the system to boot. 234- DIMM Initialization Error - Receive Enable error. Cannot train memory. Possible cause: The system receives a Receive Enable error during memory training. Action: Contact HP support. HP ProLiant server errors 55...
Page 56 234- DIMM Initialization Error – Memory cannot be initialized ...System halted. Action: Re-seat DIMMs. If issue persists, re-seat processors. If issue still persists, contact HP service. 235- DIMM Configuration Error - Processor X, Channel Y - Only 2 DIMMs can be installed on a channel with UDIMMs. - System Halted! Possible cause: A channel with UDIMMs has more than two DIMMs installed.
Page 57: Expansion Card
244– IMPORTANT: PCIe Slot X only supports 8 functions for a SR-IOV capable Expansion Card. Action: HP recommends moving this Expansion Card to another available slot to avoid possible SR-IOV limitations. Possible cause: The present PCIe slot only supports eight functions for a SR-IOV capable expansion card.
Page 58 Cycle power on the system • Reseat the processor • If the issue persists, contact HP Service. 246– IMPORTANT: The system has exceeded the amount of available Option ROM space..The Option ROM for one or more devices cannot be executed.
Page 59: The User
Action: Restore any desired configuration settings which differ from defaults. 268- iLO FW Not Responding – Unable to communicate with iLO FW ...Certain management functionality is not available. Action: Remove power. If issue persists, update iLO FW. If issue still persists, contact HP service. HP ProLiant server errors 59...
Page 60 270- iLO FW Communication Issue – Unable to communicate with iLO FW ...Certain management functionality is not available. Action: Remove power. If issue persists, update iLO FW. If issue still persists, contact HP service. 271- Processor X, DIMM Y could not be authenticated as genuine HP SmartMemory Enhanced and extended HP SmartMemory features will not be active.
Page 61 291- IMPORTANT: The Standard Boot Order (IPL) has been detected as corrupted and has been restored to default values Action: No action required. Configure the Standard Boot Order (IPL) in RBSU if changes are desired. HP ProLiant server errors 61...
Page 62: 292-299 Error
292- Invalid HP Software RAID Configuration ...HP B140i SW RAID Mode is NOT supported when the Boot Mode is configured for Legacy BIOS Mode. Action: Configure the Boot Mode to UEFI Mode if using HP SW RAID. 293- A critical error occurred resulting in a reboot of the system ...The source of the error could not be identified.
Page 63: 300 Series
300 Series 300- IMPORTANT: Unable to log an entry to the Integrated Management Log (IML) Action: Remove power. If issue persists, update iLO FW. If issue still persists, contact HP service. 301-Keyboard Error Audible Beeps: None Possible Cause: Keyboard failure occurred.
Page 64 306- Redundant ROM Error: iLO FW did not set the Primary System ROM ...The error has been corrected. iLO FW may have an issue. Action: Remove power. If issue persists, update iLO FW. If the issue persists, contact HP service. 307- Fan Failure Detected - Fan X Failed 308- Required Fan NOT Installed –...
Page 65: 400 Series
602-Diskette Boot Record Error Audible Beeps: None Possible Cause: The boot sector on the boot disk is corrupt. Action: Remove the diskette from the diskette drive. Replace the diskette in the drive. Reformat the diskette. HP ProLiant server errors 65...
Page 66: 1100 Series
Action: Restore the security override switch setting to the normal position. 1502: iLO 4 is disabled. Use the Security Override Switch and iLO 4 F8 ROM-Based Setup Utility to enable iLO functionality. Possible cause: The iLO functionality has been disabled. HP ProLiant server errors 66...
Page 67: 1600 Series
Only operate the server in a room where the temperature does not exceed the recommended temperature for the server. For more information about the optimum environment for the server, see the server user guide on the HP website (http://www.hp.com/support). 1611-CPU Zone Fan Assembly Failure Detected. Either...
Page 68 Possible Cause: Required fan is not installed or spinning. Action: Check the fans to be sure they are working. Be sure each fan cable is properly connected, if applicable, and each fan is properly seated. If the problem persists, replace the failed fans. HP ProLiant server errors 68...
Page 69 Possible Cause: Required fan is not spinning. Action: Replace the failed fan to provide redundancy, if applicable. 1611-Primary Fan Failure (Fan Zone System) Audible Beeps: None Possible Cause: A required fan is not spinning. Action: Replace the failed fan. HP ProLiant server errors 69...
Page 70 Audible Beeps: None Possible Cause: Power supply is improperly configured. Action: Run the server setup utility and correct the configuration. 1623- Power Supply Unplugged – Power Supply X is unplugged Action: Replace the power supply. HP ProLiant server errors 70...
Page 71: 1700 Series
...Upgrade to the latest firmware. If the problem persists, replace the Cache Module or Controller. Possible Cause: The cache module or controller has failed or is experiencing a fault. Action: • Upgrade to the latest firmware. HP ProLiant server errors 71...
Page 72 1708-Slot X Drive Array Controller - Bootstrap NVRAM restored from backup. System restart required Audible Beeps: None Possible Cause: The specified Smart Array controller Bootstrap NVRAM was restored in one of the following ways: • It was detected as corrupt, and the backup copy was restored. HP ProLiant server errors 72...
Page 73 Array Configuration Utility. Possible Cause: This configuration is not recommended because of controller memory requirements. Action: Perform RAID migration to smaller stripe size using HP SSA. 1713-Slot X Drive Array - Redundant ROM Reprogramming Failure..Replace the controller if this error persists after restarting system.
Page 74 (previous lock-up code = 0x####) Audible Beeps: None Possible Cause: A controller failure event occurred before the server powered up. Action: Install the latest version of controller firmware. If the condition persists, then replace the controller. HP ProLiant server errors 74...
Page 75 (or controller) with one having different cache memory size. This message may also appear following removal or installation of the cache battery back. Action: To change the default cache read/write allocation ratio, run HP SSA. 1727-Slot X Drive Array - New (or Previously Failed) Logical Drive(s) Attachment...
Page 76 ...Multiple paths to the same enclosure/drives are not supported by this Smart Array firmware version. Access to all drives has been disabled until redundant SAS cable(s) are detached, or firmware is updated to a version that supports dual-domain. HP ProLiant server errors 76...
Page 77 * Refer to product user guide Audible Beeps: None Possible Cause: Incorrect redundant cabling configuration Action: For information on how to cable the device in a supported manner for dual-domain redundant path support, see the product user guide. HP ProLiant server errors 77...
Page 78 To cancel the remove request and add these physical and logical drives back to the controller, press F2. • To re-enable the drives, use HP SSA. 1743-Slot X Drive Array - Logical Drive Erase Operation in Progress..Logical drives being erased are temporarily offline.
Page 79 Press the F1 key to continue disabling the drives until a new array configuration has been created. To avoid data loss, move the drives back to the original controller. • Press the F2 key to reset the configuration for the drives. HP ProLiant server errors 79...
Page 80 1762-Slot X Drive Array - Controller Firmware Upgrade Needed ...(Unsupported Cache Module Attached) ..Caching is disabled. Audible Beeps: None Possible Cause: The current controller firmware does not support the attached cache module type. Action: Upgrade the controller firmware, or replace the cache module. HP ProLiant server errors 80...
Page 81 * Expansion Progress Data Could Not Be Read From Cache Module. * Expansion Aborted due to Unrecoverable Drive Errors. * Expansion Aborted due to Cache Module Errors. Select "F1" to continue with logical drives disabled HP ProLiant server errors 81...
Page 82 1770-Slot X Drive Array - Disk Drive Firmware Update Recommended - ..Please upgrade firmware on the following drive model(s) using ROM Flash Components (download from www.hp.com/support/proliantstorage): Model XYZ (minimum version = ####) Audible Beeps: None Possible Cause: Drive firmware update needed.
Page 83 Action: No action is required. 1779-Slot X Drive Array - Replacement drive(s) detected OR previously failed drive(s) now appear to be operational:..Port X Box Y Bay(s) Z Restore data from backup if replacement drive(s) have been installed. HP ProLiant server errors 83...
Page 84: Slot X Drive Array Controller Failure
* [iLO communication mechanism self-test error] * [PROGRAM BUG! Insufficient padding bytes (cmd=##h)] * [Incorrect EEPROM type] * [Init failure (cmd=##h, err=##h)] * [Command failure (cmd=##h, err=##h)] * [Self-test failure (ErrCode=####h)] * [I2C NVRAM reconfiguration failure] HP ProLiant server errors 84...
Page 85 * Drive positions cannot be changed during Capacity Expansion. * Drive positions appear to have changed. Run Array Diagnostics Utility (ADU) if previous positions are unknown. Then turn system power OFF and move drives to their original positions. HP ProLiant server errors 85...
Page 86 * The following disk drive(s) are offline due to the erase process (additionally be one of the following if a spare drive is activated:) * On-Line Spare Drive is being Activated * On-Line Spare Drive Active * On-Line Spare Drive Failed HP ProLiant server errors 86...
Page 87: Slot X Drive Array Reports Incorrect Drive Replacement
A possible drive problem or loose cable exists. Action: Power down the system. Be sure all cables are properly connected. Be sure all drives are fully seated. Power cycle any external enclosures while the system is off. HP ProLiant server errors 87...
Page 88 Possible cause: The Cache Module Battery Pack is charging. Action: No action is required. 1794-Slot X Drive Array - Cache Module Battery Pack/Super-Cap Removed or Not Installed..Caching will be re-enabled when Battery Pack/Super-Cap is connected. HP ProLiant server errors 88...
Page 89 Possible Cause: Power was interrupted while data was in the write-back cache, or the data stored in the write-back cache does not correspond to this drive array. Action: Match the write-back cache to the correct drive array, or run HP SSA to clear the data in the write-back cache.
Page 90: 1800 Series
IMPORTANT: Unsupported Configuration: Controller performance and supported configurations are limited. Action: Install the Cache Module to remove these limitations. Audible Beeps: None Possible Cause: The Cache Module is not installed. Action: Install the Cache Module to remove the limitations. HP ProLiant server errors 90...
Page 91 ...Encrypted logical drives may be offline. System may not boot. Action: Correct the problem on the Key Manager GUI. 1811- Slot X Encryption Failure- Drive Keys not retrieved from the Remote Key Manager..Dependent encrypted logical drives are offline. System may not boot. HP ProLiant server errors 91...
Page 92 1817- Slot X Encryption Failure- Encryption is enabled for the controller but the Master Key name is not set... Action: Use HP SSA to set the Master Key name for the controller, and then reboot. For more information, see the server user guide.
Page 93 1825- Slot X Encryption Failure- Non-volatile storage corrupted: Critical Security Parameters erased per policy..Encrypted drives offline. Action: Use HP SSA to reestablish CSPs. For more information, see the server user guide. 1826- Slot X Encryption Failure- Encryption engine hardware failure..Encrypted logical drives offline.
Page 94: Event List Error Messages
ASR Lockup Detected: Cause Event Type: System lockup Action: Examine the IML to determine the cause of the lockup. For more information, refer to the HP ROM-Based Setup Utility User Guide on the server Documentation CD or the SmartStart Support and Documents website (http://www.hp.com/support/smartstart/documentation).
Page 95: Automatic Operating System Shutdown Initiated Due To Fan Failure
Event Type: Expansion bus error Action: Power down the server, and then replace the EISA board. PCI Bus Error (Slot X, Bus Y, Device Z, Function X) Event Type: Expansion bus error Action: Replace the PCI board. HP ProLiant server errors 95...
Page 96: Processor Correctable Error Threshold Passed (Slot X, Socket Y)
If the problem persists, remove some of the installed options. System AC Power Problem (Power Supply X) Event Type: AC voltage problem Action: Check for any power source problems. System Fan Failure (Fan X, Location) Event Type: Fan failure Action: Replace the fan. HP ProLiant server errors 96...
Page 97: System Fans Not Redundant
...Unrecoverable Host Bus Address Parity Error Event Type: Host bus error CAUTION: Only authorized technicians trained by HP should attempt to remove the system board. If you believe the system board requires replacement, contact HP Technical Support ("HP contact information" on page 399) before proceeding.
Page 98: Message Id: 4140
Before removing or replacing any processors, be sure to follow the guidelines provided in "Performing processor procedures in the troubleshooting process." Failure to follow the recommended guidelines can cause damage to the system board, requiring replacement of the system board. HP ProLiant server errors 98...
Page 99 Replace the processor. HP ProLiant server errors 99...
Page 100: Hp Proliant Gen9 Power Fault Leds
Riser board PCIe slots 5 flashes FlexibleLOM 6 flashes Removable HP Flexible Smart Array controller/Smart SAS HBA controller 7 flashes System board PCIe slots 8 flashes Power backplane or storage backplane 9 flashes Power supply HP ProLiant Gen9 power fault LEDs 100...
Page 101: Hp Smart Array Errors
Flashing = Both encrypted and plaintext volumes are present. Amber Debug On = Controller is in reset state. Off = Controller is in an idle or runtime state. Flashing 5 Hz = Controller and cache are performing a backup. HP Smart Array errors 101...
Page 102: P440 Controller Leds
When an error occurs, this LED is on. During power up, this LED is solid for up to 2 seconds. Green Crypto On = All attached volumes are encrypted. Off = All attached volumes are plaintext. Flashing = Both encrypted and plaintext volumes are present. HP Smart Array errors 102...
Page 103: P441 Controller Leds
When an error occurs, this LED is on. During power up, this LED is solid for up to 2 seconds. Green Crypto On = All attached volumes are encrypted. Off = All attached volumes are plaintext. Flashing = Both encrypted and plaintext volumes are present. HP Smart Array errors 103...
Page 104: P840 Controller Leds
When an error occurs, this LED is on. During power up, this LED is solid for up to 2 seconds. Green Crypto On = All attached volumes are encrypted. Off = All attached volumes are plaintext. Flashing = Both encrypted and plaintext volumes are present. HP Smart Array errors 104...
Page 105: Cache Module Leds
The cache module is idle, the battery is charged, and the cache contains data that has not yet been written to the drives. Flashing once A backup of the DDR content on the cache module is in per second progress. HP Smart Array errors 105...
Page 106: Smart Array Windows Event Log Messages
Message Id: 24580 Severity: Error Log Message: The HP Smart Array SAS/SATA Event Notification Service needs to be upgraded and cannot process events at this time. The service is being stopped and processing of HP 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.
Page 107 This drive can be found in box <box number> which is connected to port <port number> of the array controller <controller name / slot information>. The offline reason received from the HP Smart Array firmware is: <firmware error code>.
Page 108 • 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. HP Smart Array errors 108...
Page 109 OFFLINE_DRIVE_TYPE_MIX - Drive is offline because it is not the correct type for this array [SATA vs SAS]. • OFFLINE_ERASE_COMPLETE - Drive is offline because a Secure Erase operation has completed on it but it hasn’t been replaced yet. HP Smart Array errors 109...
Page 110 Message Id: 24592 Severity: Informational Log message: Redundant power supply number <power supply number> is no longer sensed as being in a failed state. Some possible reasons that would cause this state change to occur include: HP Smart Array errors 110...
Page 111 <bay number>. This drive can be found in box <box number> which is connected to port <port number> of the array controller <controller name / slot information>. The failure reason received from the HP Smart Array firmware is: <firmware error code>.
Page 112 WRONG_REPLACE - A hot-plug tape drive was plugged in as a replacement into a drive bay that a hard disk was removed from. • GDP_VPD_INQUIRY_FAILED - Could not read drive serial number after multiple retries. HP Smart Array errors 112...
Page 113 Log message: The <drive type> physical drive located in bay <bay number> is in a SMART predictive failure state. This drive can be found in box <box number> which is connected to port <port number> of the array controller <controller name / slot information>. Message Id: 24597 Severity: Warning HP Smart Array errors 113...
Page 114 “HARDWARE IS OVERHEATING” • “HARDWARE HAS OVERHEATED” • “EXPANDING” • “NOT YET AVAILABLE” • “QUEUED FOR EXPANSION” • “DISABLED DUE TO SCSI ID CONFLICT” • “EJECTED” • “ERASING” • “UNKNOWN” Message Id: 24599 Severity: Warning HP Smart Array errors 114...
Page 115: Message Identifiers 24600-24624
Log message: Logical drive <logical drive number> of array controller <controller name / slot information> has encountered a status change from: Status: <previous status> Status: <current status> <previous status> and <current status> values: • “OK” • “FAILED” • “NOT CONFIGURED” HP Smart Array errors 115...
Page 116 "OK". However, this status change will not occur until the logical drive is re-enabled. Please re-enable the logical drive either via the HP Array Configuration Utility or by rebooting the system.
Page 117 <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. HP Smart Array errors 117...
Page 118 <port number> and box <box number>. <firmware information>. Please check the cabling and ensure that a supported configuration is being used. <firmware information> values: • “The Smart Array firmware is reporting that no additional details are available” HP Smart Array errors 118...
Page 119 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 Severity: Informational HP Smart Array errors 119...
Page 120: Message Identifiers 24625-24649
This fan is located in box number <box number> which is connected to port <port number> of array controller <controller name / slot information>. Message Id: 24627 Severity: Informational HP Smart Array errors 120...
Page 121 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 HP Smart Array errors 121...
Page 122 Message Id: 24643 Severity: Warning Log message: The Smart Array controller <controller name / slot information> is not redundant because an inter-controller link could not be established with the partner controller. Message Id: 24644 Severity: Error HP Smart Array errors 122...
Page 123: Message Identifiers 24650-24674
“the external controller attached to” • "" Message Id: 24651 Severity: Error Log message: SnapShot ID <ID number> of logical drive <logical drive number> on <external specification> array controller <controller name / slot information> failed and has been deleted. HP Smart Array errors 123...
Page 124 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 HP Smart Array errors 124...
Page 125 <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 HP Smart Array errors 125...
Page 126 “the external controller attached to” • "" Message Id: 24672 Severity: Error Log message: Snapshot resource volume of logical drive <logical drive number> on <external specification> array controller <controller name / slot information> has reached its limit. HP Smart Array errors 126...
Page 127: Message Identifiers 24675-24699
<logical drive number>. This repair was conducted by overwriting the statistically incorrect stripe on the physical drive found in bay <bay number> of box <box number> connected to port <port number> of array controller <controller name / slot information>. Message Id: 24677 HP Smart Array errors 127...
Page 128 The logical drive rebuild is continuing so that the volume can regain fault tolerance. Capacity expansion operations must be avoided while the affected blocks are unreadable. Message Id: 24684 HP Smart Array errors 128...
Page 129 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 Severity: Warning HP Smart Array errors 129...
Page 130 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. HP Smart Array errors 130...
Page 131: Message Identifiers 24700-24724
<chassis label> is indicating that sensor number <sensor number> has reported that the internal temperature has exceeded the preset temperature limit. The external Smart Array controller may attempt to shut down power to and/or spin down the installed disk drive(s). HP Smart Array errors 131...
Page 132 <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 HP Smart Array firmware is: <firmware error code>. The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>.
Page 133 INIT_REQUEST_SENSE_FAILED - “Request Sense” command failed during device discovery/initialization. • INIT_START_UNIT_FAILED - “Start Unit” command failed during device discovery/initialization. • INQUIRY_FAILED - “Inquiry” command failed after multiple retries. • NON_DISK_DEVICE - Attached device is not a hard disk per its inquiry data. HP Smart Array errors 133...
Page 134 QUEUE_FULL_ON_ZERO - Drive indicates that its queue is full when we have no requests outstanding to the drive. • SMART_ERROR_REPORTED - Drive has reported a predictive-failure error when controller is configured to automatically fail [instead of reporting imminent failure of] drives that report this error. HP Smart Array errors 134...
Page 135 “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” • “EJECTED” HP Smart Array errors 135...
Page 136 Severity: Error Log message: The external Smart Array controller located in the MSA chassis labeled as <chassis label> has reported that logical drive <logical drive number> has encountered a status change from: Status: <current status> HP Smart Array errors 136...
Page 137 However, this status change will not occur until the logical drive is re-enabled. Please re-enable the logical drive either via the HP Array Configuration Utility or by power cycling the MSA chassis. The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>.
Page 138 <bus number> and ID <ID number>. The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>. Message Id: 24719 Severity: Warning HP Smart Array errors 138...
Page 139: Message Identifiers 24725-24749
BMIC device index <device index>. The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>. Message identifiers 24725-24749 Message Id: 24725 Severity: Informational HP Smart Array errors 139...
Page 140 <slot 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: 24730 Severity: Informational HP Smart Array errors 140...
Page 141 Smart Array controller <controller name / slot information>. Message Id: 24736 Severity: Error Log message: The external Smart Array controllers located in the MSA chassis labeled as <chassis label> are not redundant because an inter-controller link could not be established. HP Smart Array errors 141...
Page 142 Log message: The external Smart Array controllers located in the MSA chassis labeled as <chassis label> are no longer redundant because an expand operation is in progress. The controllers will become redundant once again once the expand operation has completed. HP Smart Array errors 142...
Page 143 (port <port number>) and <attached device><attached device index>. Please check this data path and the associated hardware. The external Smart Array controller reporting this event is attached to the host side Smart Array controller <controller name / slot information>. HP Smart Array errors 143...
Page 144: Message Identifiers 24750-24774
Log message: The external Smart Array controller located in the MSA chassis labeled as <chassis label> has reported that storage box number <box number> was added to port <port number>. This connection is through I/O module number <module number> on the storage box. HP Smart Array errors 144...
Page 145 <port number> of the external array controller. The external Smart Array controller reporting this event is attached to the host side Smart Array controller <controller name / slot information>. Message Id: 24758 HP Smart Array errors 145...
Page 146 External Smart Array controller number <controller number> located in the MSA chassis labeled as <chassis label> is reporting the following flash operation: "<firmware message>." The firmware was flashed from: Revision: <old revision number> Revision: <new revision number> HP Smart Array errors 146...
Page 147 <bay number> is in a SMART predictive failure state. The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>. Message Id: 24767 Severity: Informational HP Smart Array errors 147...
Page 148 <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>. Message Id: 24773 HP Smart Array errors 148...
Page 149: Message Identifiers 24775-24799
Log message: The external Smart Array controller located in the MSA chassis labeled as <chassis label> is reporting that the <drive type> physical hard drive located in bay <bay number> is offline. The offline reason received from the HP Smart Array firmware is: <firmware error code>.
Page 150 MISSING_IN_SAVE_RIS - Could not write to reserved configuration sectors after multiple retries. • WRONG_REPLACE - A hot-plug tape drive was plugged in as a replacement into a drive bay that a hard disk was removed from. HP Smart Array errors 150...
Page 151 <chassis label> is reporting that the <drive type> physical hard drive located in bay <bay number> is now online. The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>. HP Smart Array errors 151...
Page 152 The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>. <additional information> values: • “ The parity data does not match the data drives.” • “” Message Id: 24781 HP Smart Array errors 152...
Page 153 <chassis label> has reported that a storage enclosure processor (SEP) has failed. The external Smart Array controller is attached to the host side Smart Array controller <controller name / slot information>. Message Id: 24787 HP Smart Array errors 153...
Page 154 <temperature limit>°C. The current temperature is <current temperature>°C as reported by sensor number <sensor number>. The array controller may enact precautionary measures to prevent data loss should the temperature reach the operating limit. HP Smart Array errors 154...
Page 155 (wear out). This drive can be found in box <box number> which is connected to port <port number> of the array controller <controller name / slot information>. Message Id: 24798 Severity: Informational HP Smart Array errors 155...
Page 156: Message Identifiers 24800-24808
Log message: The <drive type> physical drive located in bay <bay number> could not be authenticated as a genuine HP 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 157: Smart Array Windows Driver Errors
%2 seconds. Message Id: 5002 Severity: Error Log message: The driver has taken the failed controller in slot %2 (bus %3, device %4, function %5) offline. Message Id: 5003 Severity: Error HP Smart Array errors 157...
Page 158 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. HP Smart Array errors 158...
Page 159: Hp Onboard Administrator Errors
18 Unable to perform the operation. Retry the operation or restart OA. (System Error 18) 19 The submitted bay is already assigned. 20 The submitted bay is not assigned. 22 The submitted value is already in use. 23 The first character in the submitted value is not valid. HP Onboard Administrator errors 159...
Page 160 53 Setting the Onboard Administrator's UID state failed. 54 Getting the Onboard Administrator's status failed. 55 Getting the Onboard Administrator's information failed. 56 Getting fan information for the submitted fan failed. 57 Rebooting the enclosure failed. 58 Shutting down the enclosure failed. HP Onboard Administrator errors 160...
Page 161 89 Could not read the configuration file. 90 Could not write to the configuration file. 92 The submitted url is not valid. 93 Could not update the firmware with the submitted image file. 94 Unable to acquire the rack topology. HP Onboard Administrator errors 161...
Page 162 133 HP SIM station name not found. 134 HP SIM SSO API received a bad parameter. 135 The maximum number of HP SIM XE stations already configured. 136 The maximum number of EBIPA interconnects DNS servers has been reached. 137 The session could not be created.
Page 163 175 There was an error attempting to clear the SSH keys. 176 The IP address is already listed. 177 There was an error getting the SSO trust mode. 178 The submitted SSO trust mode is invalid. HP Onboard Administrator errors 163...
Page 164 218 An error occurred while setting the enclosure part number. 219 An error occurred while setting the enclosure serial number. 220 Cannot set time when NTP is enabled. 221 Request is valid only for Itanium/BCS/IPF blades. HP Onboard Administrator errors 164...
Page 165 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 HP Onboard Administrator is initializing. Login disabled. 236 Cannot retrieve Onboard Administrator media device array. 237 The requested device is not ready.
Page 166 255 An undocumented error has occurred. Please update your firmware to the latest firmware version if necessary. Contact HP if the problem persists. 256 This certificate is already mapped to another user. 257 The user certificate could not be verified.
Page 167 318 Factory defaults cannot be restored because the enclosure is in VC mode. 319 The string entered is not a valid IPv6 address. 320 IPv6 static address already exists 321 IPv6 static address not found 322 Unable to add HP Onboard Administrator errors 167...
Page 168 359 URB reporting using SMTP and HTTP(S) cannot be enabled until HTTP(S) and SMTP settings have been configured. 360 Warning: Not all VC-Enet modules are on the same VLAN ID. 361 File doesn't exist. 362 This operation cannot be performed when AlertMail is enabled. 363 Setting SolutionsId failed HP Onboard Administrator errors 168...
Page 169 383 Failed to send Remote Support message. Please make sure DNS is enabled and verify Insight Remote Support host and port information. 384 Failed to resolve HP Insight Remote Support hosting server. Please verify DNS settings and Insight Remote Support host and port information.
Page 170 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 HP Remote Support receiver temporarily unavailable. Please retry later. HP Onboard Administrator errors 170...
Page 171 466 Data Package validation failed. Please retry your last step. If error persists and device is currently registered, unregister and re-register device. 467 HP Passport password must be changed or reset. Please attempt to register again after correcting the HP Passport account issue.
Page 172 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. 474 Failed to connect to HP Insight Remote Support direct connect web service. Please verify DNS settings, proxy settings and connectivity. 475 Dynamic DNS is not enabled.
Page 173 HP Passport profile and retry registration. 524 HP Passport Security Q and A is not compliant; the user must enter a new security Q and A upon login. Please update your HP Passport security Q and A and retry registration.
Page 174 UEFI boot mode. 561 Transmission from the HP Insight Remote Support receiver was unsuccessful. 562 Transmission from the HP Insight Remote Support receiver was unsuccessful. Please check connectivity between OA and the Insight Remote Support receiver. 563 The key strength for the provided key is invalid for this configuration.
Page 175: Syslog Messages
Alertmail: Failed to register with mgmt Alertmail: Failed to send AlertMail to [value] Alertmail: Failed to start reboot notifier thread Authentication and startup log messages Log type: LOG_WARNING, Failure type: SW sulogin: cannot open [value] sulogin: No password file HP Onboard Administrator errors 175...
Page 176: Cgi Log Messages
OA: ProLiant iLO firmware update attempted by user [value] Interconnect bay log messages Log type: LOG_WARNING, Failure type: Info OA: [value] was connected to interconnect bay #[value] OA: [value] was disconnected from interconnect bay #[value] HP Onboard Administrator errors 176...
Page 177: Dhcp Log Messages
OA: error executing [value] [value] [value]: [value] OA: mkdir([value]",0): [value]" OA: recvfrom: [value] OA: sendto: [value] OA: Timed out waiting for a valid DHCP server response. Will keep trying in the background OA: writePidFile: fopen: [value] HP Onboard Administrator errors 177...
Page 178: Enclosure-Link Log Messages
Enclosure-Link: Failed to register with enclosure [value:IpAddress] Enclosure-Link: Failed to retrieve enclosure addresses from lower elink chain Enclosure-Link: Failed to retrieve enclosure addresses from upper elink chain Enclosure-Link: Failed to send ICMP packet to host HP Onboard Administrator errors 178...
Page 179: Non-Volatile Configuration Log Messages
Error in default gateway envtools: Error in DNS1 address envtools: Error in DNS2 address envtools: Error in ipaddress envtools: Error in ipAllow1 address envtools: Error in ipAllow2 address envtools: Error in ipAllow3 address envtools: Error in ipAllow4 address HP Onboard Administrator errors 179...
Page 180 Updating NVRAM version to 24. envtools: Updating NVRAM version to 25. envtools: Updating NVRAM version to 26. envtools: Updating NVRAM version to 27. envtools: Updating NVRAM version to 28. envtools: Updating NVRAM version to 29. HP Onboard Administrator errors 180...
Page 181: Firmware Flash Log Messages
OA_Flash: Image verified successfully and applies to this system using the parameters supplied. Test Mode specified, skipping the actual flash process Firmware version [value:version] ExitCode=0 Flash certificate, configuration, and storage log messages Log type: LOG_ERR, Failure type: SW CERTS: .ssh has wrong directory permissions HP Onboard Administrator errors 181...
Page 182 CONFIG: Failed to write data to flash CONFIG: Tar file [value] is too big for flash [value] CONFIG: Wrong file permissions detected. Please reset to factory defaults CONFIG: Failed to create data CONFIG: Failed to locate data HP Onboard Administrator errors 182...
Page 183: Dns Network Configuration Log Messages
DDNS: Registered with Dynamic DNS netreg: DDNS: Update successful netreg: NETBIOS: Registered with WINS OA: WARNING: The [value:label] ‘[value:hostname]’ is not pingable OA: The [value:label] '[value:hostname]' is pingable again. OA: WARNING: There is no DNS record for [value:label] '[value:hostname]' HP Onboard Administrator errors 183...
Page 184: Lcd Log Messages
OA: KVM Socket connect error [value] ([value]) to ILO addr [value:Address]:[value:port] OA: KVM Socket creation error [value] ([value]) to ILO addr[value:Address] OA: Mutex SEMV post failed errno [value] OA: Mutex SEMV wait failed errno [value] HP Onboard Administrator errors 184...
Page 185: Operational Log Messages
OA: Active Onboard Administrator will not be flashed OA: Consider resetting the Standby and/or Active Onboard Administrators and retrying OA: Failed flashing Standby Onboard Administrator OA: Failed to copy firmware image to the Standby Onboard Administrator HP Onboard Administrator errors 185...
Page 186 OA: Enclosure Dynamic Power Cap set to: [value], derated circuit [value], rated circuit [value] by [value:username]. OA: Enclosure Dynamic Power Cap set to: OFF by [value:username]. OA: Enclosure part number changed from '[value]' to '[value]' by [value:username]. HP Onboard Administrator errors 186...
Page 187 OA: Enclosure PDU type changed from '[value]' to '[value]' by [value:username]. OA: Forced takeover requested by user [value:username]. OA: HP SSO certificate [value:subject-CN] added by user [value:username]. OA: HP SSO certificate [value] removed by user [value:username]. OA: LDAP Directory Server certificate(MD5=[value]) installed by user [value:username].
Page 188 OA: EBIPAv6 was [value] for bay [value:bayNumber] by user [value:username]. OA: EBIPAv6 Server domain for bay [value:bayNumber] set to [value] by user [value:username]. OA: EBIPAv6 Server first DNS IP for bay [value:bayNumber] set to [value] by user [value:username]. HP Onboard Administrator errors 188...
Page 189 OA: IPv6 address [value:address] added by user [value:username]. OA: IPv6 address [value:address] removed by user [value:username]. OA: IPv6 protocol was disabled by user [value:username]. OA: IPv6 protocol was enabled by user [value:username]. OA: IPv6 Router Advertisement was [enabled/disabled] by user [value:username]. HP Onboard Administrator errors 189...
Page 190 OA: Protocol SSH was [enabled/disabled] by user [value:username] OA: Protocol Telnet was [enabled/disabled] by user [value:username] OA: Protocol XML was [enabled/disabled] by user [value:username] OA: Rack Name was changed to [value] by user [value:username] OA: Remote syslog test message. HP Onboard Administrator errors 190...
Page 191 OA: User [value:username]'s contact was set removed by user [value:username]. OA: User [value:username]'s contact was set to [value] by user [value:username]. OA: User [value:username]'s full name was removed by user [value:username]. OA: User [value:username]'s full name was set to [value:fullname] by user [value:username]. HP Onboard Administrator errors 191...
Page 192 OA: Standby Onboard Administrator flashed successfully OA: Virtual power command enacted on interconnect [value:number] by user [value:username] OA: Warning: Not all VC-Enet modules are on the same VLAN ID Log type: LOG_ERR, Failure type: Info HP Onboard Administrator errors 192...
Page 193: Linux Log Messages
OA: LCD not functioning properly, pausing operation for 10 seconds. OA: LCD Status is: Failed OA: mgmt: GPIO initialization failed. OA: mgmt: i2c initialization failed. OA: Mismatching I/O was detected on Blade [value:bladeNumber], interconnect [value]. HP Onboard Administrator errors 193...
Page 194 OA: Blade [value:bladeNumber] FRU memory fault...state is DEGRADED. OA: Blade [value:bladeNumber] has integrated blade cross connection, Mezzanine card [value] is superfluous. OA: Blade [value:bladeNumber] Internal Temperature caution...state is CRITICAL. OA: Blade [value:bladeNumber] Internal Temperature caution...state is DEGRADED. HP Onboard Administrator errors 194...
Page 195 OA: Ekeying: Partner device of blade [value:bladeNumber] was removed, no more mezzanine card required on blade [value:bladeNumber]. OA: Fan Removed: Bay #[value:fanNumber] OA: Fan Status Changed: Bay #[value:fanNumber] From: [degraded/failed/ok] To: [degraded/failed/ok] OA: Fan Subsystem Status Changed: From: [degraded/failed/ok] To: [degraded/failed/ok] HP Onboard Administrator errors 195...
Page 196 OA: HP strongly recommends replacing power supply #[value] at the customer's earliest possible convenience pursuant to Customer Advisory c01519680. OA: Internal communication problem detected. OA: Internal communications restored. OA: Internal health status of interconnect in bay [value:slotNumber] changed to Degraded...
Page 197 Power Cap. The blade does not have the required iLO license. OA: Blade [value:bladeNumber] complies with location rules now. OA: Blade [value:bladeNumber] Disk Tray is Open state is OK. OA: Blade [value:bladeNumber] firmware management completed. HP Onboard Administrator errors 197...
Page 198 OA: PS Subsystem N + 1 Redundancy Power Limit - REPAIRED OA: PS Subsystem N + N Redundancy - REPAIRED OA: PS Subsystem N + N Redundancy Power Limit - REPAIRED OA: PS Subsystem Overloaded - REPAIRED OA: PS Subsystem Power Limit - REPAIRED HP Onboard Administrator errors 198...
Page 199 OA: Interconnect module in bay [value:slotNumber] was powered off OA: Interconnect module in bay [value:slotNumber] was powered on OA: LCD firmware upgrade initiated. OA: LCD firmware upgrade succeeded. OA: Server Blade in bay [value:bladeNumber] has been powered down HP Onboard Administrator errors 199...
Page 200: Oa Internal Log Messages
OA: Object read failed errno [value] OA: Object read failed size [value] OA: Object write failed errno [value] OA: Object write failed size [value] Log type: LOG_NOTICE, Failure type: SW OA: Internal communication problem detected. HP Onboard Administrator errors 200...
Page 201: Ldap Log Messages
Redundancy: Failed to read event from mgmt subsystem Redundancy: Onboard Administrator is switching to Active mode Redundancy: Onboard Administrator is switching to Standby mode. This OA will now reboot Log type: LOG_CRIT, Failure type: HW HP Onboard Administrator errors 201...
Page 202: Sso Log Messages
SSO log messages Log type: LOG_WARNING, Failure type: Info OA: HP SSO [value] logged into the Onboard Administrator OA: HP SSO [value] logged into the Onboard Administrator from [value:remoteAddress] Log type: LOG_NOTICE, Failure type: Info HP Onboard Administrator errors 202...
Page 203: Two-Factor Log Messages
OA: Authentication failure for user HP SSO [value] OA: Authentication failure for user HP SSO [value] from [value:remoteAddress] OA: HP SSO Trust Mode changed to [value] by user [value:username]. Two-factor log messages Log type: LOG_WARNING, Failure type:SW OA: Two Factor: Two-Factor authentication failed for user at [value]: local user certificate status check failed.
Page 204: Vlan Log Messages
Enclosure power supply is removed 22016 cpqRackPowerSupplyInserted Enclosure power supply is inserted 22017 cpqRackPowerSubsystemNotRedundant Enclosure power subsystem is not 22018 redundant cpqRackPowerSubsystemLineVoltageProble Enclosure power subsystem line voltage 22019 problem cpqRackPowerSubsystemOverloadCondition Enclosure power subsystem overload 22020 condition HP Onboard Administrator errors 204...
Page 205: Enclosure Event Notifications
When the SET DISPLAY EVENTS option is turned on, the terminal interface displays error, warning, and status messages, depending on the behavior of the enclosure and components. The syntax for these messages are: • <error>—Description of error • <warning>—Description of warning • <status>—Description of status HP Onboard Administrator errors 205...
Page 206 A power supply has been removed. Power Supply Removed The power supplies are either now redundant or Power Supply Redundancy are no longer redundant. Change The power supplies are being asked to draw Power Supply Overload HP Onboard Administrator errors 206...
Page 207 The privilege level of a user on the Onboard User Rights Administrator was changed. If you are logged in as this user, you are disconnected from the Onboard Administrator. You can log in again with your new privilege level. HP Onboard Administrator errors 207...
Page 208: Hp Virtual Connect Errors
(VC-Enet or VC-FC) and the role of the module in the VC domain. Virtual Connect supports SNMPv1, SNMPv2, and SNMPv3. The latest version of VC-specific MIBs can be downloaded from the HP Systems Insight Manager "MIB Kit" site on the HP website (http://h18006.www1.hp.com/products/servers/management/hpsim/mibkit.html).
Page 209: Snmp Traps
— VC QOS MIB (VC-QOS-MIB) * Not supported by the HP 8Gb 24-Port FC Module The VC Module MIB is a VC-specific MIB that describes the state of a specific VC module. In addition to unique VC module attributes, it defines traps for reporting alerts on port statistics, such as throughput, errors, and discards.
Page 210 VCM-MIB vcModPortProtectionConditionCleared ¹ Only supported by the HP VC 8Gb 24-Port FC module ² 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 211: Vc Module Mib Traps
The output error count on a port has exceeded its vcModOutputErrorsUp ifOutErrors high-water mark for longer than the threshold averaging period. port is the index of the affected port in ifTable. HP Virtual Connect errors 211...
Page 212 Indicates a component threshold has been reached or error condition is imminent warning Indicates an error condition exists that has little or no component impact minor Indicates an error condition exists that significantly impairs the component major HP Virtual Connect errors 212...
Page 213 Module in bay enc0:iobay3 has been removed The enclosure managed status ReasonCodes are provided in the following table. Enclosure reason code Description The enclosure is normal. vcEnclosureOk All Ethernet modules are abnormal, none are OK or degraded. vcEnclosureAllEnetModulesFailed HP Virtual Connect errors 213...
Page 214 The physical server managed status ReasonCodes are provided in the following table. Physical server reason code Description The server is functioning normally. vcPhysicalServerOk The server is unable to communicate with the enclosure/OA. vcPhysicalServerEnclosureDown The server is in a failed condition. vcPhysicalServerFailed HP Virtual Connect errors 214...
Page 215 3 TCServer profile connections for server in bay enc0:devbay3 are not mapped The following is an example of a profile RootCause string: The TelecomServer profile is assigned to an abnormal server in bay enc0:devbay1 The profile managed status ReasonCodes are provided in the following table. HP Virtual Connect errors 215...
Page 216: Virtual Connect Manager Syslog Events
The events generated in the Syslog cover the following areas that are managed by the Virtual Connect Manager: • Domain (1000–1999) • Enclosure (2000–2999) • Ethernet Interconnect modules (3000–3999) • FC Interconnect modules (4000–4999) • Servers (5000–5999) • Profiles (6000-6999) • Ethernet Network (7000–7999) • FC Fabric (8000–8999) HP Virtual Connect errors 216...
Page 217: Domain Events (1000-1999)
Verify OA and VC have been assigned IP addresses and that the IP addresses do not conflict with other assignments on the network. • Verify that management network is not being used for substantial data traffic. • Verify that management network topology is correct. • Verify end-to-end connectivity. HP Virtual Connect errors 217...
Page 218: Domain State Failed
• Export a support package from VC for HP analysis. • Capture the output of the OA show all command for HP analysis. 1022 - Domain state FAILED Severity: CRITICAL Description: The VC domain is suffering an outage that does not allow VC to talk to any enclosure or device.
Page 219: Enclosure Events (2000-2999)
• If all workarounds fail: Export a support package from VC for HP analysis. Capture the output of the OA show all command for HP analysis. Contact HP customer support with the previously gathered information. 2011 - Enclosure state NO_COMM Severity: CRITICAL Description: The VC management application is unable to communicate with an enclosure.
Page 220: Enclosure State Failed
If hardware replacement does not correct the issue: Export a support package from VC for HP analysis. Capture the output of the OA show all command for HP analysis. Contact HP customer support with the previously gathered information. 2016 - Enclosure Find failed...
Page 221: Ethernet Module Events (3000-3999)
• If all workarounds fail: Export a support package from VC for HP analysis. Capture the output of the OA show all command for HP analysis. Contact HP customer support with the previously gathered information. Ethernet Module events (3000-3999) 3009 - Enet Module OA CPU Fault Event...
Page 222: Enet Module State Missing
HP 1/10 Gb VC-Enet Module or an HP 1/10 Gb-F Ethernet Module can reside in an adjacent bay. • HP VC 8Gb 20-Port FC Modules can reside in any bay. However, only another HP VC 8Gb 20-Port FC Module can reside in an adjacent bay. •...
Page 223: Enet Module State No_Comm
Possible cause 1: More than one active uplink port or uplink Link Aggregation Group (LAG) from an uplink set has been assigned to the same network from the Virtual Connect domain to the external Ethernet switching environment, causing a network loop. HP Virtual Connect errors 223...
Page 224: Fc Module Events (4000-4999)
Action: Power cycle the module to clear any transient hardware failures. If the condition persists a support dump must be taken and analyzed to determine possible firmware failures. 4014 - FC Module State Incompatible Severity: MAJOR HP Virtual Connect errors 224...
Page 225: Server Events (5000-5999)
Description: The Virtual Connect Manager has received a Blade Fault event from the OA. Possible cause: The server hardware has failed. Actions: • Verify the communication between VC and the Onboard Administrator for the affected server is operational. • Verify the server is in a good state. HP Virtual Connect errors 225...
Page 226: Server State Failed
Power cycle the server to see if the server initialization completes successfully. • Remove and install the server blade. • Replace the multi-blade server. 5050 - The BIOS for the following devices is not compatible with Virtual Connect Severity: MAJOR HP Virtual Connect errors 226...
Page 227: Profile Events (6000-6999)
All physical functions after the first one with the duplicate network will be disabled, and no traffic will flow on the connection. Possible cause: A profile is applied to a server and the mapping results in duplicate Ethernet networks on the same Flex-10 physical port. HP Virtual Connect errors 227...
Page 228 Reboot the server and check to see if it is discovered. • Physically remove and replace the server. • Analyze the Onboard Administrator logs for possible details regarding the failure. 6030 - Profile could not be assigned to powered up server Severity: MAJOR HP Virtual Connect errors 228...
Page 229: Ethernet Network Events (7000-7999)
FC Fabric events (8000-8999) 8012 - FC Fabric state FAILED Severity: CRITICAL Description: The VC fabric lost all uplink connectivity because of lack of configured ports or all configured ports are in a bad state. Possible causes: HP Virtual Connect errors 229...
Page 230: Unknown Module Events (9000-9999)
Analyze the Onboard Administrator logs for possible details regarding the failure. 9019 - Unknown Module state NO_COMM Severity: MAJOR Description: VCM cannot properly communicate with the module. Possible cause 1: The module is powered off. Action: Power the module back on through the OA interface. HP Virtual Connect errors 230...
Page 231: Enet Uplinkset Events (17000-17999)
Possible cause: The speedtype of the ports in the uplink port set might be set to disabled. Action: Check the speedtype of the ports in the uplink port set and set it to auto-negotiation, or any appropriate value. HP Virtual Connect errors 231...
Page 232: Hprcu Errors
HPRCU errors HPRCU return codes Return code Possible messages displayed Success ERROR: This server is not supported. ERROR: Malformed or invalid XML file detected. ERROR: XML file error, feature_id is missing. ERROR: XML file error, settings for feature_id=[id] are missing. ERROR: The Toolkit I/O Driver(hpsstkio.sys) is missing or not installed.
Page 233: Conrep Errors
700 series servers. Some platforms require special settings that are contained in other XML files. These files are included in the Scripting Toolkit and are available from the HP website (http://www.hp.com) on the support page for each platform. You can use these files with the -x option to configure systems that are not supported by the default hardware configuration file.
Page 234: 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 235: Hp Ilo Errors
This section provides information about iLO error messages. For the latest information on iLO error messages, go to the HP website (http://www.hp.com/go/ilo) to download the latest iLO user guide. iLO POST LED indicators During the initial boot of iLO, the POST LED indicators flash to display the progress through the iLO boot process.
Page 236 Displays when a user resets the host server. Host server reset by: User Displays when a user powers off a host server. Host server powered OFF by: User Displays when a user powers on a host server. Host server powered ON by: User HP iLO errors 236...
Page 237 Displays when an authorized user removes a license. License removed by: User Displays when an error occurs activating the license. License activation error by: User Displays when an authorized user logs in to iLO RBSU. iLO RBSU user login: User HP iLO errors 237...
Page 238: Ribcl Messages
Login name is too long. 0x0003 Password is too short. 0x0004 Password is too long. 0x0005 User table is full. No room for new user. 0x0006 Cannot add user. The login/ user name already exists. 0x0007 HP iLO errors 238...
Page 239 User does NOT have correct privilege for action. CONFIG_RACK_PRIV 0x0028 required. User does NOT have correct privilege for action. VIRTUAL_MEDIA_PRIV 0x0029 required. Server is NOT a rack server; Rack commands do not apply. 0x002A Minimum password length value exceeded. 0x002B HP iLO errors 239...
Page 240 Power management is disabled. 0x004C Feature not supported. 0x004D Unable to import the HP SIM certificate from the specified source. 0x004E Insufficient room to add a HP SIM Server record. 0x004F Single Sign-On information is open for read-only access. Write access 0x0050 is required for this operation.
Page 241 - Missing required parameter for direct connect model setup. 0x0083 eRS - Missing required parameter for IRS connect model setup. 0x0084 eRS - No connect model specified. 0x0085 There are missing parameters in the xml script. 0x0086 HP iLO errors 241...
Page 242 0XAF This feature requires an advanced license key. 0XB0 There was an error on reading the data. 0XB1 There was an error on setting the data. 0XB2 Invalid port. 0XB3 Port assignments must be unique. 0XB4 HP iLO errors 242...
Page 243: Hardware And Software Link-Related Issues
The RBSU can also be used to correct login issues. Directory user premature logout Solution: To recover from a premature session timeout, log back in and continue using iLO. If the directory server is unavailable, then you must use a local account. HP iLO errors 243...
Page 244: Ilo Management Port Not Accessible By Name
128 bits and cannot be changed. The browser and iLO encryption levels must be the same. Unable to return to login page after an iLO flash or reset Solution: Clear your browser cache, and restart the browser. HP iLO errors 244...
Page 245: Unable To Access Virtual Media Or Graphical Remote Console
This name is unique to each iLO. Every time iLO resets, it generates a new certificate with the same name. HP iLO errors 245...
Page 246: Unable To Connect To The Ilo Ip Address
The name of the rack was changed. Rack Name Changed Unable to receive HP SIM alarms (SNMP Traps) from iLO Solution: A user with the Configure iLO Settings privilege must connect to iLO to configure SNMP trap parameters. When connected to iLO, be sure that the correct alert types and trap destinations are enabled in the SNMP/Insight Manager Settings screen of the iLO console application.
Page 247: Incorrect Authentication Code
In the unlikely event that it is necessary, setting the iLO Security Override switch also enables you to flash the iLO boot block. The boot block is exposed until iLO is reset. HP recommends that you disconnect iLO from the network until the reset is complete.
Page 248: Troubleshooting Remote Console Issues
If the mouse still fails to operate correctly, or if this situation occurs frequently, verify that your mouse settings match those recommended in the “Optimizing mouse performance for Java Integrated Remote Console or Integrated Remote Console” in the HP ProLiant Integrated Lights-Out 3 v 1.20 User Guide. Remote Console text window not updating properly When using the Remote Console to display text windows that scroll at a high rate of speed, the text window might not update properly.
Page 249: Monitor Problems In Irc Or Java Remote Console
When the JRC does not display the correct floppy and usb-key, perform the following steps to display them correctly. Solution: Ensure that RHEL 5 is installed on the local client system. Install the latest version of Java and configure it to connect with the default Firefox browser. HP iLO errors 249...
Page 250 Open a Java IRC session. Click Virtual Drives>Floppy/USB-key, and select Virtual Media. Verify the Linux box displays. Type or select the path of the USB-key/floppy (/dev/disk) which is inserted to the client. Click the OK button. HP iLO errors 250...
Page 251: Caps Lock Goes Out Of Synch Between Ilo And A Java Remote Console Session
Solution: As a session leader, when you play back capture video data, the IRC does not display the Deny or Accept warning message when another user attempts to access or share the IRC. Instead, the new IRC HP iLO errors 251...
Page 252: Keyboard Led Does Not Display Correctly
If the remote console Acquire function is enabled, use the Acquire button rather than requesting a shared remote console session. Troubleshooting SSH issues The following sections discuss troubleshooting SSH issues. HP iLO errors 252...
Page 253: Initial Putty Input Slow
Extended text configuration beyond the 80 x 25 configuration is not displayed correctly when using SSH. HP recommends configuring the text application in 80 x 25 mode or using the iLO Remote Console applet provided by the web interface.
Page 254: Troubleshooting Remote Text Console Issues
The iLO web server makes URL decisions based on each request received. For example, if a request does not have access rights, it is redirected to the login page, regardless of the original request. Web server based redirection, selecting File>New>Window or pressing the Ctrl+N keys, opens a duplicate instance of the original browser. HP iLO errors 254...
Page 255 You can force the browser to refresh and reveal your true identity by pressing the F5 key, selecting View>Refresh, or clicking the refresh button. Preventing cookie-related user issues To prevent cookie-based behavioral issues: HP iLO errors 255...
Page 256: Unable To Get Snmp Information From Hp Sim
Unable to get SNMP information from HP SIM Solution: The agents running on the managed server supply SNMP information to HP SIM. For agents to pass information through iLO, iLO device drivers must be installed. For installation instructions, see the “Installing iLO device drivers”...
Page 257: Ilo Network Failed Flash Recovery
226-File acceptable 226-Flashing 3% complete 226-Flashing 4% complete 226-Flashing 6% complete 226-Flashing 97% complete 226-Flashing 99% complete 226-Flashing 100% complete 226-Flashing completed 226 Closing file ftp: 8388608 bytes sent in 1.38Seconds 6100.81 Kbytes/sec. ftp> quote reset HP iLO errors 257...
Page 258: Issues Generating A Keytab Using Ktpass.exe
Verify Type is domain controller and click Next until a certificate is used. You can also use Microsoft LDP tool to verify SSL connections. For more information on the LDP tool, go to the Microsoft website at http://www.microsoft.com/support (http://www.microsoft.com/support). HP iLO errors 258...
Page 259: File Not Present After Copy Through Irc Virtual Drives To Usb Key
If a firmware upgrade is completed or a network setting is changed, iLO also resets. The HP Insight Management Agents 5.40 and later have the ability to reset iLO. To reset iLO, choose one of the following options: •...
Page 260: Server Name Still Present After Erase Utility Is Executed
Change the server name on the Administration>Access Settings>Access Options page on the iLO browser interface. Troubleshooting a remote host Troubleshooting a remote host server might require restarting the remote system. You can restart the remote host server by using the options listed in the Virtual Devices tab. HP iLO errors 260...
Page 261: Microsoft Windows Event Id And Snmp Traps
This section contains a listing of the Microsoft® Windows Server® 2003 Event Log messages associated with SNMP traps, which are generated by the HP Insight Management Agents for Servers for Windows®. Each event entry has the corresponding SNMP trap number used by the agents. Other information on the events in this section includes Event Severity, Event Message, Event Message Source, Event Symptom, and Supporting SNMP Trap Data.
Page 262: Foundation Agents
• 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: • sysName •...
Page 263 • cpqMeAlarmVariable • cpqMeAlarmSampleType • cpqMeAlarmValue • cpqMeAlarmRisingThreshold • cpqMeAlarmOwner • cpqMeAlarmSeverity • cpqMeAlarmExtendedDescription Supporting SNMP Trap Description: “[cpqMeAlarmOwner]: Variable [cpqMeAlarmVariable] has value [cpqMeAlarmValue] >= [cpqMeAlarmRisingThreshold].” NT Event ID: 1163 (Hex)0x8435048b (cpqhsmsg.dll) Log Severity: Warning (2) Log Message: Falling Threshold Passed. SNMP Trap: cpqMeFallingAlarmExtended - 10006 in CPQTHRSH.MIB Symptom: Falling Threshold passed.
Page 264 • cpqMeAlarmVariable • cpqMeAlarmSampleType • cpqMeAlarmValue • cpqMeAlarmRisingThreshold • cpqMeAlarmOwner • cpqMeAlarmSeverity • cpqMeAlarmExtendedDescription Supporting SNMP Trap Description: “[cpqMeAlarmOwner]: Variable [cpqMeAlarmVariable] has value [cpqMeAlarmValue] <= [cpqMeAlarmRisingThreshold].” NT Event ID: 1165 (Hex)0x8435048d (cpqhsmsg.dll) Log Severity: Warning (2) Log Message: Critical Falling Threshold Passed. SNMP Trap: cpqMeCriticalFallingAlarmExtended - 10008 in CPQTHRSH.MIB Symptom: Critical Falling Threshold passed.
Page 265 • cpqHoSwRunningTrapDesc Supporting SNMP Trap Description: “[cpqHoSwRunningTrapDesc]” NT Event ID: 1167 (Hex)0x8435048f (cpqhsmsg.dll) Log Severity: Warning (2) Log Message: The cluster resource %4 has become degraded. SNMP Trap: cpqClusterResourceDegraded - 15005 in CPQCLUS.MIB Symptom: This trap is sent any time the condition of a cluster resource becomes degraded. User Action: Make a note of the cluster resource name, and then check the resource for the cause of the degraded condition.
Page 266 • cpqClusterNetworkName Supporting SNMP Trap Description: ”Cluster network [cpqClusterNetworkName] has become degraded.” NT Event ID: 1170 (Hex)0xc4350492 (cpqhsmsg.dll) Log Severity: Error (3) Log Message: The cluster network %4 has failed. SNMP Trap: cpqClusterNetworkFailed - 15008 in CPQCLUS.MIB Symptom: This trap is sent any time the condition of a cluster network has failed. User Action: Make a note of the cluster network name, and then check the network for the cause of the failure.
Page 267 Supporting SNMP Trap Description: “Cluster service on [cpqClusterNodeName] has failed.” NT Event ID: 1173 (Hex)0x84350495 (cpqhsmsg.dll) Log Severity: Warning (2) Log Message: The Processor Performance Instance, '%4' is degraded with Processor Time of %5 percent. SNMP Trap: cpqOsCpuTimeDegraded - 19001 in CPQWINOS.MIB Symptom: The Processor Time performance property is set to degraded.
Page 268 • cpqOsCacheIndex • cpqOsCacheInstance • cpqOsCacheCopyReadHitsPercent Supporting SNMP Trap Description: “The Cache performance property is degraded with Copy Read Hits of [cpqOsCacheCopyReadHitsPercent] percent.” NT Event ID: 1176 (Hex)0xc4350498 (cpqhsmsg.dll) Log Severity: Error (3) Log Message: The Cache Performance Instance, '%4' is failed with Cache Copy Read Hits of %5 percent. SNMP Trap: cpqOsCacheCopyReadHitsFailed - 19004 in CPQWINOS.MIB Symptom: The Cache Copy Read Hits performance property is set to critical.
Page 269 Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqOsPagingFileIndex • cpqOsPagingFileInstance • cpqOsPageFileUsagePercent Supporting SNMP Trap Description: “The PagingFile performance instance, [cpqOsPagingFileInstance] is critical with PagingFile Usage of [cpqOsPageFileUsagePercent] percent.” NT Event ID: 1179 (Hex)0x8435049b (cpqhsmsg.dll) Log Severity: Warning (2) Log Message: The Logical Disk Performance Instance, '%4' is degraded with Disk Busy Time of %5 percent.
Page 270 Log Message: '%4' SNMP Trap: cpqHoCriticalSoftwareUpdateTrap - 11014 in CPQHOST.MIB Symptom: This trap is sent to notify the user of a Critical Software Update. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqHoCriticalSoftwareUpdateData Supporting SNMP Trap Description: “[cpqHoCriticalSoftwareUpdateData]” Event identifier: cpqhsmsg.dll - 1792 (Hex)0x84350700 (Service Event) Log Severity: Warning (2) Log Message: The agent is unable to generate traps due to an error during initialization.
Page 271: Event Identifiers 2048-2359
persists, reinstalling the Management Agents or the Remote Access Service may correct this error. For more information, see the Management Agents Asynchronous Management documentation. Event Identifiers 2048-2359 Event identifier: cpqhsmsg.dll - 2048 (Hex)0x84350800 (Service Event) Log Severity: Warning (2) Log Message: Unable to allocate memory. This indicates a low memory condition. Rebooting the system will correct this error.
Page 272 Log Severity: Warning (2) Log Message: Unable to acquire file system information for %1. This error can be caused by a low memory condition. Rebooting the server may correct this error. Event identifier: cpqhsmsg.dll - 2100 (Hex)0x84350834 (Service Event) Log Severity: Warning (2) Log Message: Unable to acquire the current process list.
Page 273 Event identifier: cpqhsmsg.dll - 2312 (Hex)0x84350908 (Service Event) Log Severity: Warning (2) Log Message: The Threshold Agent could not create its main thread of execution. The data contains the error code. Event identifier: cpqhsmsg.dll - 2313 (Hex)0x84350909 (Service Event) Log Severity: Warning (2) Log Message: The Threshold Agent main thread did not terminate properly.
Page 274: Event Identifiers 3072-3876
Log Severity: Warning (2) 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) Log Message: The Threshold Agent is not loaded.
Page 275 Log Severity: Warning (2) Log Message: Unable to load a required library. This error can be caused by a corrupt or missing file. Reinstalling the Management Agents or running the Emergency Repair procedure may correct this error. Event identifier: cpqhsmsg.dll - 3090 (Hex)0x84350c12 (Service Event) Log Severity: Warning (2) Log Message: Unable to allocate memory.
Page 276 Event identifier: cpqhsmsg.dll - 3857 (Hex)0x84350f11 (Service Event) Log Severity: Warning (2) Log Message: Could not get the cluster's status. The Cluster service may not be running. Try to restart the Cluster service. Event identifier: cpqhsmsg.dll - 3858 (Hex)0x84350f12 (Service Event) Log Severity: Warning (2) Log Message: Could not open the enumerated resource.
Page 277 Log Severity: Information (1) Log Message: Resource status is offline pending. The resource is being taken offline. Event identifier: cpqhsmsg.dll - 3868 (Hex)0x84350f1c (Service Event) Log Severity: Warning (2) Log Message: Cluster information is unavailable. The Cluster service may not be running. Try to restart the Cluster service.
Page 278: Event Identifiers 4352-4626
Event Identifiers 4352-4626 Event identifier: cpqhsmsg.dll - 4352 (Hex)0x84351100 (Service Event) Log Severity: Warning (2) Log Message: The External Status MIB Agent could not allocate memory. The data contains the error code. Event identifier: cpqhsmsg.dll - 4353 (Hex)0x84351101 (Service Event) Log Severity: Warning (2) Log Message: The External Status MIB Agent could not open the base of the registry.
Page 279 Log Message: The External Status MIB Agent main thread did not terminate properly. The data contains the error code. Event identifier: cpqhsmsg.dll - 4362 (Hex)0x8435110a (Service Event) Log Severity: Warning (2) Log Message: The External Status MIB Agent got an unexpected error code while waiting for an event. The data contains the error code.
Page 280 Log Message: The External Status MIB Agent is not loaded. Sets are not available. The data contains the error code. Event identifier: cpqhsmsg.dll - 4608 (Hex)0x84351200 (Service Event) Log Severity: Warning (2) Log Message: Unable to allocate memory. This indicates a low memory condition. Rebooting the system will correct this error.
Page 281: Storage Agents
Event identifier: cpqhsmsg.dll - 4626 (Hex)0x84351212 (Service Event) Log Severity: Warning (2) Log Message: The Agent failed to process the MOF file to get the data from WMI. Problem with WMI service or MOF file or wrong file paths used. Storage agents Event Identifiers 256-774 Event identifier: cpqstmsg.dll - 256 (Hex)0x84350100 (Service Event)
Page 282 Event identifier: cpqstmsg.dll - 264 (Hex)0x84350108 (Service Event) Log Severity: Warning (2) Log Message: The Storage Agents service could not load the module “%1”. The data contains the error code. Event identifier: cpqstmsg.dll - 265 (Hex)0x84350109 (Service Event) Log Severity: Warning (2) Log Message: The Storage Agents service could get the control function for module “%1”.
Page 283 Log Severity: Information (1) Log Message: The Storage Agents service version %1 has started. Event identifier: cpqstmsg.dll - 401 (Hex)0x44350191 (Service Event) Log Severity: Information (1) Log Message: %1 Event identifier: cpqstmsg.dll - 512 (Hex)0x84350200 (Service Event) Log Severity: Warning (2) Log Message: Unable to allocate memory.
Page 284: Event Identifiers 1061-1098
Log Severity: Warning (2) Log Message: The Drive Array Agent failed to get capacity on SCSI drive because SCSI pass through IOCTL failed. Event identifier: cpqstmsg.dll - 768 (Hex)0x84350300 (Service Event) Log Severity: Warning (2) Log Message: The Remote Alerter Agent detected an invalid data type within an alert definition. Event identifier: cpqstmsg.dll - 769 (Hex)0x84350301 (Service Event) Log Severity: Warning (2) Log Message: The Remote Alerter Agent detected an error while attempting to log an alert remotely.
Page 285 Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqDaPhyDrvCntlrIndex • cpqDaPhyDrvBusNumber • cpqDaPhyDrvBay • cpqDaPhyDrvModel • cpqDaPhyDrvFWRev • cpqDaPhyDrvSerialNum Supporting SNMP Trap Description: “Factory threshold passed for a physical drive.” NT Event ID: 1062 (Hex)0xc4350426 (cpqstmsg.dll) Log Severity: Error (3) Event Title: Drive Array Logical Drive Status Change.
Page 286 • cpqDaSpareBay Supporting SNMP Trap Description: “Spare Status is now [cpqDaSpareStatus].” NT Event ID: 1064 (Hex)0xc4350428 (cpqstmsg.dll) Log Severity: Error (3) Event Title: Drive Array Physical Drive Status Change. Log Message: The physical drive in slot %4, port %5, bay %6 with serial number “%7”, has a new status of SNMP Trap: cpqDa5PhyDrvStatusChange - 3029 in CPQIDA.MIB Symptom: Physical Drive Status Change.
Page 287 • cpqDaCntlrModel • cpqDaAccelSerialNumber • cpqDaAccelTotalMemory • cpqDaAccelStatus • cpqDaAccelErrCode Supporting SNMP Trap Description: “Status is now [cpqDaAccelStatus].” NT Event ID: 1066 (Hex)0xc435042a (cpqstmsg.dll) Log Severity: Error (3) Event Title: Drive Array Accelerator Bad Data. Log Message: The array accelerator board attached to the array controller in slot %4 is reporting that it contains bad cached data.
Page 288 • cpqDaCntlrModel • cpqDaAccelSerialNumber • cpqDaAccelTotalMemory Supporting SNMP Trap Description: “Battery status is failed.” NT Event ID: 1068 (Hex)0xc435042c (cpqstmsg.dll) Log Severity: Error (3) Event Title: SCSI Controller Status Change. Log Message: The SCSI controller in slot %4, SCSI bus %5 has a new status of %2. SNMP Trap: cpqScsi3CntlrStatusChange - 5005 in CPQSCSI.MIB Symptom: SCSI Controller Status Change.
Page 289 Log Message: The SCSI physical drive with SCSI target %6 connected to SCSI bus %5 of the controller in slot %4 has a new status of %2. SNMP Trap: cpqScsi5PhyDrvStatusChange - 5020 in CPQSCSI.MIB Symptom: Physical Drive Status Change. The Storage Agent has detected a change in the status of a SCSI physical drive.
Page 290 SNMP Trap: cpqSs3TempFailed - 8009 in CPQSTSYS.MIB Symptom: Storage System temperature failure. The agent has detected that a temperature status has been set to failed. The storage system is shut down. User Action: Shut down the storage system as soon as possible. Insure that the storage system environment is being cooled properly and that no components are overheated.
Page 291: Event Identifiers 1101-1199
• 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 292 NT Event ID: 1104 (Hex)0x84350450 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Storage System Fault Tolerant Power Supply Degraded. Log Message: The fault tolerant power supply in the %6 %7 storage system connected to SCSI bus %5 of the controller in slot %4 has a degraded status. Restore power or replace any failed power supply. SNMP Trap: cpqSs4PwrSupplyDegraded - 8015 in CPQSTSYS.MIB Symptom: A storage system power supply status has been set to degraded.
Page 293 Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqTapePhyDrvCondition Supporting SNMP Trap Description: “Status is now [cpqTapePhyDrvCondition].” NT Event ID: 1120 (Hex)0x84350460 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: SCSI Tape Drive Cleaning Tape Needs Replacing. Log Message: The tape drive with SCSI target %6 connected to SCSI bus %5 of the controller in slot %4 needs the cleaning tape replaced.
Page 294 SNMP Trap: cpqIdeDriveOk - 14002 in CPQIDE.MIB Symptom: An IDE drive status has been set to OK. User Action: None. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqIdeIdentIndex Supporting SNMP Trap Description: “IDE drive [cpqIdeIdentIndex] has returned to normal operating condition.”...
Page 295 Symptom: External Array Physical Drive Status Change. This trap indicates that the agent has detected a change in the status of a physical drive. The variable cpaFcaPhyDrvStatus indicates the current physical drive status. User Action: If the physical drive status is threshExceeded(4), predictiveFailure(5) or failed(6), replace the drive.
Page 296 Supporting SNMP Trap Description: “Spare Status is now [cpqFcaSpareStatus] on bus [cpqFcaSpareBusNumber].” NT Event ID: 1148 (Hex)0xc435047c (cpqstmsg.dll) Log Severity: Error (3) Event Title: External Array Accelerator Status Change. Log Message: The array accelerator board attached to the external controller in I/O slot %5 of array “%4” has a new status of %6.
Page 297 • cpqSsChassisName • cpqSsChassisTime • cpqFcaAccelBoxIoSlot • cpqFcaCntlrModel • cpqFcaAccelSerialNumber • cpqFcaAccelTotalMemory Supporting SNMP Trap Description: “Accelerator lost battery power. Data Loss possible.” NT Event ID: 1150 (Hex)0xc435047e (cpqstmsg.dll) Log Severity: Error (3) Event Title: External Array Accelerator Battery Failed. Log Message: The array accelerator board attached to the external controller in I/O slot %5 of array “%4”...
Page 298 • sysName • cpqHoTrapFlags • cpqSsChassisName • cpqSsChassisTime • cpqFcaCntlrBoxIoSlot • cpqFcaCntlrStatus • cpqFcaCntlrModel • cpqFcaCntlrSerialNumber • cpqFcaAccelTotalMemory Supporting SNMP Trap Description: “Status is now [cpqFcaCntlrStatus].” NT Event ID: 1152 (Hex)0x84350480 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Storage System Fan Module Status Change. Log Message: Storage system “%4”...
Page 299 Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqSsChassisName • cpqSsChassisTime • cpqSsPowerSupplyBay • cpqSsPowerSupplyStatus • cpqSsPowerSupplySerialNumber • cpqSsPowerSupplyBoardRevision • cpqSsPowerSupplyFirmwareRevision Supporting SNMP Trap Description: “Storage system power supply status changed to [cpqSsPowerSupplyStatus].” NT Event ID: 1154 (Hex)0x84350482 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Storage System Power Supply UPS Status Change.
Page 300 Symptom: Storage system temperature sensor status change. The agent has detected a change in the status of a storage system temperature sensor. The variable cpqSsTempSensorStatus indicates the current status. User Action: If the temperature status is degraded or failed, shut down the storage system as soon as possible.
Page 301 • cpqHoTrapFlags • cpqTapeLibrarySerialNumber Supporting SNMP Trap Description: “Tape Library [cpqTapeLibrarySerialNumber] Recovered.” NT Event ID: 1158 (Hex)0x84350486 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: SCSI Tape Library Degraded. Log Message: The SCSI tape library with SCSI target %6 connected to SCSI bus %5 of the controller in slot %4 is in a degraded condition.
Page 302 Symptom: Tape Library Door Closed. The Insight Agent has detected that the door on an autoloader has closed. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqTapeLibrarySerialNumber Supporting SNMP Trap Description: “Tape library [cpqTapeLibrarySerialNumber] door closed.” NT Event ID: 1161 (Hex)0xc4350489 (cpqstmsg.dll) Log Severity: Error (3) Event Title: SCSI CD Library Status Change.
Page 303 • cpqDaCntlrModel • cpqDaCntlrSerialNumber • cpqDaCntlrFWRev • cpqDaAccelTotalMemory Supporting SNMP Trap Description: “Status is now [cpqDaCntlrBoardStatus].” NT Event ID: 1165 (Hex)0x8435048d (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Drive Array Controller Active. Log Message: The Drive Array Controller in slot %4 has become the active controller. SNMP Trap: cpqDaCntlrActive - 3016 in CPQIDA.MIB Symptom: Controller Active.
Page 304 Supporting SNMP Trap Description: “Status is now [cpqFcTapeCntlrStatus] for tape controller [cpqFcTapeCntlrWWN].” NT Event ID: 1174 (Hex)0x84350496 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Fibre Channel Tape Library Status Change. Log Message: The Fibre Channel tape library on tape controller with world wide name “%4”, SCSI bus %5, SCSI target %6, has a new status of %7.
Page 305 • cpqFcTapeLibraryScsiTarget • cpqFcTapeLibraryScsiLun • cpqFcTapeLibraryDoorStatus Supporting SNMP Trap Description: “The door is [cpqFcTapeLibraryDoorStatus] for tape library.” NT Event ID: 1176 (Hex)0x84350498 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Fibre Channel Tape Drive Status Change. Log Message: The Fibre Channel tape drive on tape controller with world wide name “%4”, SCSI bus %5, SCSI target %6, has a new status of %7.
Page 306 • cpqFcTapeDriveScsiLun Supporting SNMP Trap Description: “Cleaning is needed for tape drive.” NT Event ID: 1178 (Hex)0x8435049a (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Fibre Channel Tape Drive Replace Cleaning Tape. Log Message: The cleaning tape in the Fibre Channel tape drive on tape controller with world wide name “%4”, SCSI bus %5, SCSI target %6, needs to be replaced.
Page 307 NT Event ID: 1180 (Hex)0x8435049c (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Drive Array Tape Library Status Change. Log Message: The tape library in slot %4, SCSI bus %5, SCSI target %6 has a new status of %7 SNMP Trap: cpqDa2TapeLibraryStatusChange - 3031 in CPQIDA.MIB Symptom: Tape Library Status Change.
Page 308 • cpqDaTapeLibraryScsiLun • cpqDaTapeLibraryDoorStatus Supporting SNMP Trap Description: “The door is [cpqDaTapeLibraryDoorStatus] for tape library.” NT Event ID: 1182 (Hex)0x8435049e (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Drive Array Tape Drive Status Change. Log Message: The tape drive in slot %4, SCSI bus %5, SCSI target %6 has a new status of %7. SNMP Trap: cpqDa2TapeDriveStatusChange - 3032 in CPQIDA.MIB Symptom: Tape Drive Status Change.
Page 309 • cpqDaTapeDrvScsiIdIndex • cpqDaTapeDrvLunIndex Supporting SNMP Trap Description: “Cleaning is needed for the tape drive.” NT Event ID: 1184 (Hex)0x843504a0 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Drive Array Tape Drive Replace Cleaning Tape. Log Message: The cleaning tape in the tape drive in slot %4, SCSI bus %5, SCSI target %6 needs to be replaced.
Page 310 NT Event ID: 1186 (Hex)0x843504a2 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: IDE ATA Disk Status Change. Log Message: The ATA disk drive with model %6 and serial number %7 has a new status of %2. SNMP Trap: cpqIdeAtaDiskStatusChange - 14004 in CPQIDE.MIB Symptom: ATA Disk Status Change.
Page 311 Supporting SNMP Trap Description: “Status is now [cpqIdeLogicalDriveStatus] for the IDE logical drive.” NT Event ID: 1188 (Hex)0x843504a4 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Storage System Fan Status Change. Log Message: An enclosure attached to port %5 of storage system “%4” has a new fan status of %7. The enclosure model is “%6”.
Page 312 • cpqSsBackplaneIndex • cpqSsBackplaneVendor • cpqSsBackplaneModel • cpqSsBackplaneSerialNumber • cpqSsBackplaneTempStatus Supporting SNMP Trap Description: “Storage system temperature status changed to [cpqSsBackplaneTempStatus].” NT Event ID: 1190 (Hex)0x843504a6 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Storage System Power Supply Status Change. Log Message: An enclosure attached to port %5 of storage system “%4” has a new power supply status of %7.
Page 313 • sysName • cpqHoTrapFlags • cpqTapeLibraryCntlrIndex • cpqTapeLibraryBusIndex • cpqTapeLibraryScsiIdIndex • cpqTapeLibraryLunIndex • cpqTapeLibraryName • cpqTapeLibraryFwRev • cpqTapeLibrarySerialNumber • cpqTapeLibraryState Supporting SNMP Trap Description: “Status is now [cpqTapeLibraryState].” NT Event ID: 1192 (Hex)0x843504a8 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: SCSI Tape Drive Status Change. Log Message: The tape drive with SCSI target %6 connected to SCSI bus %5 of the controller in slot %4 has a new status of %2.
Page 314 Symptom: External Tape Drive Status Change. This trap indicates that the agent has detected a change in the status of an External Tape Drive. The variable cpqFcTapeDriveStatus indicates the current tape status. User Action: If the tape is failed or is offline, check the tape and all connections. Supporting SNMP Trap Data: •...
Page 315 Log Severity: Warning (2) Event Title: External Tape Drive Replace Cleaning Tape. Log Message: The cleaning tape in the tape drive at location “%4” needs to be replaced. SNMP Trap: cpqExtTapeDriveCleanTapeReplace - 16025 in CPQFCA.MIB Symptom: External Tape Drive Cleaning Tape Needs Replacing. The agent has detected that an autoloader tape unit has a cleaning tape that has been fully used and therefore needs to be replaced with a new cleaning tape.
Page 316 Supporting SNMP Trap Description: “Storage system recovery server option status changed to [cpqSsChassisRsoStatus].” NT Event ID: 1197 (Hex)0x843504ad (cpqstmsg.dll) Log Severity: Warning (2) Event Title: External Tape Library Status Change. Log Message: The tape library at location “%4”, has a new status of %7. SNMP Trap: cpqExtTapeLibraryStatusChange - 16026 in CPQFCA.MIB Symptom: External Tape Library Status Change.
Page 317: Event Identifiers 1200-1294
• 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. Log Message: The Drive Array Controller in %7 has a new status of %5.
Page 318 Symptom: Logical Drive Status Change. This trap indicates that the agent has detected a change in the status of a drive array logical drive. The variable cpqDaLogDrvStatus indicates the current logical drive status. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags •...
Page 319 Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqDaCntlrHwLocation • cpqDaPhyDrvIndex • cpqDaPhyDrvBusNumber • cpqDaPhyDrvBay • cpqDaPhyDrvModel • cpqDaPhyDrvFWRev • cpqDaPhyDrvSerialNum • cpqDaPhyDrvFailureCode • cpqDaPhyDrvStatus Supporting SNMP Trap Description: “Physical Drive Status is now [cpqDaPhyDrvStatus].” NT Event ID: 1203 (Hex)0x843504b3 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Drive Array Physical Drive Threshold Exceeded.
Page 320 Event Title: Drive Array Accelerator Status Change. Log Message: The array accelerator board attached to the array controller in %4 has a new status of %2. SNMP Trap: cpqDa6AccelStatusChange - 3038 in CPQIDA.MIB Symptom: Accelerator Board Status Change. This trap indicates that the agent has detected a change in the status of an array accelerator cache board.
Page 321 Supporting SNMP Trap Description: “Accelerator lost battery power. Data Loss possible.” NT Event ID: 1206 (Hex)0x843504b6 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Drive Array Accelerator Battery Failed. Log Message: The array accelerator board attached to the array controller in %4 is reporting a battery failure.
Page 322 • cpqDaTapeLibraryScsiLun • cpqDaTapeLibraryModel • cpqDaTapeLibraryFWRev • cpqDaTapeLibrarySerialNumber • cpqDaTapeLibraryStatus Supporting SNMP Trap Description: “Status is now [cpqDaTapeLibraryStatus] for the tape library.” NT Event ID: 1208 (Hex)0x843504b8 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Drive Array Tape Library Door Status Change. Log Message: The tape library in %4, SCSI bus %5, SCSI target %6 has a new door status of %7.
Page 323 User Action: If the tape is failed, check the tape and all SCSI connections. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqDaCntlrHwLocation • cpqDaTapeDrvCntlrIndex • cpqDaTapeDrvBusIndex • cpqDaTapeDrvScsiIdIndex • cpqDaTapeDrvLunIndex • cpqDaTapeDrvName • cpqDaTapeDrvFwRev • cpqDaTapeDrvSerialNumber • cpqDaTapeDrvStatus Supporting SNMP Trap Description: “Status is now [cpqDaTapeDrvStatus] for a tape drive.”...
Page 324 Log Message: The cleaning tape in the tape drive in %4, SCSI bus %5, SCSI target %6 needs to be replaced. SNMP Trap: cpqDa6TapeDriveCleanTapeReplace - 3045 in CPQIDA.MIB Symptom: Tape Drive Cleaning Tape Needs Replacing. The agent has detected that an autoloader tape unit has a cleaning tape that has been fully used and therefore needs to be replaced with a new cleaning tape.
Page 325 NT Event ID: 1213 (Hex)0x843504bd (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Storage System Temperature Status Change. Log Message: The %6 %7 storage system connected to SCSI bus %5 of the controller in %4 has a new temperature status of %2. SNMP Trap: cpqSs5TempStatusChange - 8027 in CPQSTSYS.MIB Symptom: Storage System Temperature Status Change.
Page 326 • cpqSsBoxBusIndex • cpqSsBoxVendor • cpqSsBoxModel • cpqSsBoxSerialNumber • cpqSsBoxFltTolPwrSupplyStatus Supporting SNMP Trap Description: “Storage system power supply status changed to [cpqSsBoxFltTolPwrSupplyStatus].” NT Event ID: 1215 (Hex)0x843504bf (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Fibre Channel Controller Status Change. Log Message: The Fibre Channel Controller in %4 has a new status of %5. SNMP Trap: cpqFca3HostCntlrStatusChange - 16028 in CPQFCA.MIB Symptom: Fibre Channel Host Controller Status Change.
Page 327 • sysName • cpqHoTrapFlags • cpqDaCntlrHwLocation • cpqDaPhyDrvCntlrIndex • cpqDaPhyDrvIndex • cpqDaPhyDrvLocationString • cpqDaPhyDrvType • cpqDaPhyDrvModel • cpqDaPhyDrvFWRev • cpqDaPhyDrvSerialNum • cpqDaPhyDrvFailureCode • cpqDaPhyDrvStatus • cpqDaPhyDrvBusNumber Supporting SNMP Trap Description: “Physical Drive Status is now [cpqDaPhyDrvStatus].” NT Event ID: 1217 (Hex)0x843504c1 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Drive Array Spare Drive Status Change.
Page 328 SNMP Trap: cpqSs6FanStatusChange - 8029 in CPQSTSYS.MIB Symptom: Storage System Fan Status Change. The agent has detected a change in the fan status of a storage system. 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: •...
Page 329 • cpqSsBoxLocationString Supporting SNMP Trap Description: “Storage System temperature status changed to [cpqSsBoxTempStatus].” NT Event ID: 1220 (Hex)0x843504c4 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Storage System Fault Tolerant Power Supply Status Change. Log Message: The fault tolerant power supply in the %6 %7 storage system connected to %5 of the controller in%4 has a new status of %2.
Page 330 • cpqHoTrapFlags • cpqSasHbaHwLocation • cpqSasPhyDrvLocationString • cpqSasPhyDrvHbaIndex • cpqSasPhyDrvIndex • cpqSasPhyDrvStatus • cpqSasPhyDrvType • cpqSasPhyDrvModel • cpqSasPhyDrvFWRev • cpqSasPhyDrvSerialNumber • cpqSasPhyDrvSasAddress Supporting SNMP Trap Description: “Status is now [cpqSasPhyDrvStatus].” NT Event ID: 1222 (Hex)0x843504c6 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: SAS/SATA Logical Drive Status Change.
Page 331 Supporting SNMP Trap Data • sysName • cpqHoTrapFlags • cpqSasHbaHwLocation • cpqSasTapeDrvLocationString • cpqSasTapeDrvHbaIndex • cpqSasTapeDrvIndex • cpqSasTapeDrvName • cpqSasTapeDrvFWRev • cpqSasTapeDrvSerialNumber • cpqSasTapeDrvSasAddress • cpqSasTapeDrvStatus Supporting SNMP Trap Description: "Status is now %d." NT Event ID: 1224 (Hex)0x843504c8 (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Partner Controller Status Change.
Page 332 Log Severity: Warning (2) Event Title: Storage System Connection Status Change. Log Message: The %7 storage system connected to %5 of the controller in %4 has a new connection status of %6. (Connection status values: 1=other, 2=notSupported, 3=connected, 4=notConnected) SNMP Trap: cpqSsConnectionStatusChange - 8032 in CPQSTSYS.MIB Symptom: The agent has detected a change in the connection status of a storage system.
Page 333 • cpqSasPhyDrvLocationString • cpqSasPhyDrvHbaIndex • cpqSasPhyDrvIndex • cpqSasPhyDrvType • cpqSasPhyDrvModel • cpqSasPhyDrvFWRev • cpqSasPhyDrvSerialNumber • cpqSasPhyDrvSasAddress Supporting SNMP Trap Description: "Solid State Disk Wear Status is now %d." NT Event ID: 1227 (Hex)0x843504cb (cpqstmsg.dll) Log Severity: Warning (2) Event Title: Drive Array Physical Drive SSD Wear Status Change. Log Message: The physical drive in %4, %5 with serial number "%6", has a new solid state wear status of %7.
Page 334 Log Message: The ATA disk drive with model %6 and serial number %7 has a new solid state wear status of %2. (SSD wear status values: 1=other, 2=ok, 3=fiftySixDayThreshold, 4=fivePercentThreshold, 5=twoPercentThreshold, 6=ssdWearOut) SNMP Trap: cpqIdeAtaDiskSSDWearStatusChange - 14006 in CPQIDE.MIB Symptom: This trap signifies that the agent has detected a change in the SSD wear status of a SATA physical drive.
Page 335: Event Identifiers 1343-4613
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. Event identifier: cpqstmsg.dll - 1285 (Hex)0x84350505 (Service Event) Log Severity: Warning (2) Log Message: Could not write the registry subkey: “%1”.
Page 336 This can be caused by a failure in the Remote Access Service or by a missing or invalid configuration. Use the HP Insight Management Agents control panel to verify the Asynchronous Management configuration settings. Use the Network control panel to verify the Remote Access configuration. If this error persists, reinstalling the Storage Agents or the Remote Access Service may correct this error.
Page 337 Log Severity: Warning (2) Log Message: “%1”. The data contains the error code. Event identifier: cpqstmsg.dll - 3588 (Hex)0x84350e04 (Service Event) Log Severity: Warning (2) Log Message: The IDE Agent could not read the registry value “%1”. The data contains the error code. Event identifier: cpqstmsg.dll - 3589 (Hex)0x84350e05 (Service Event) Log Severity: Warning (2) Log Message: The IDE Agent found an incorrect type for registry value “%1”.
Page 338 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) Log Severity: Warning (2) Log Message: The IDE Agent did not respond to a request. The data contains the error code. Event identifier: cpqstmsg.dll - 3600 (Hex)0x84350e10 (Service Event) Log Severity: Warning (2) Log Message: The IDE Agent received an unknown action code from the service.
Page 339: Server Agents
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 - 4612 (Hex)0x84351204 (Service Event) Log Severity: Warning (2) Log Message: Could not read the registry subkey: “%1”.
Page 340 Log Severity: Warning (2) Log Message: The Server Agents service could not start any agents successfully. Event identifier: cpqsvmsg.dll - 263 (Hex)0x84350107 (Service Event) Log Severity: Warning (2) Log Message: The Server Agents service could not read the registry value “%1”. The data contains the error code.
Page 341 Log Message: The Server Agents service could not create the registry key “%1”. The data contains the error code. Event identifier: cpqsvmsg.dll - 273 (Hex)0x84350111 (Service Event) Log Severity: Warning (2) Log Message: The Server Agents service could not write the registry value “%1”. The data contains the error code.
Page 342: Event Identifiers 1025-1092
Log Message: The Remote Alerter Agent received an error on WaitForMultipleObjects call. The data contains the error code. Event identifier: cpqsvmsg.dll - 774 (Hex)0xc4350306 (Service Event) Log Severity: Error (3) Log Message: The Remote Alerter Agent received an error on ResetEvent call. The data contains the error code.
Page 343 User Action: Replace the faulty memory. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags Supporting SNMP Trap Description: “The Advanced Memory Protection subsystem has engaged the online spare memory.” NT Event ID: 1027 (Hex)0x84350403 (cpqsvmsg.dll) Log Severity: Warning (2) Log Message: The Advanced Memory Protection sub-system has detected a memory fault. Advanced ECC has been activated.
Page 344 Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqHeFltTolPowerSupplyChassis Supporting SNMP Trap Description: “The Power Supplies are now redundant on Chassis [cpqHeFltTolPowerSupplyChassis].” NT Event ID: 1030 (Hex) 0x44350406 (cpqsvmsg.dll) Log Severity: Information (1) 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.
Page 345 require a replacement of the memory module in slot [cpqHeResMem2BoardNum]], cpu [cpqHeResMem2CpuNum], riser [cpqHeResMem2RiserNum], socket [cpqHeResMem2ModuleNum]. NT Event ID: 1036 (Hex) 0x4435040CL (cpqsvmsg.dll) Log Severity: Informational (1) Log Message: A memory board or cartridge has been removed from the system. Please reinsert the memory board or cartridge.
Page 346 Log Severity: Error (3) Log Message: A memory board or cartridge bus error has been detected in the memory subsystem. SNMP Trap: cpqHe5ResMemBoardBusError- 6067 in CPQHLTH.MIB Symptom: Memory board, cartridge, or riser bus error detected. An Advanced Memory Protection sub-system board, cartridge, or riser bus error has been detected. Value 0 for CPU means memory is not processor-based.
Page 347 • cpqHeFltTolPowerSupplyChassis • cpqHeFltTolPowerSupplyBay • cpqHeFltTolPowerSupplyStatus • cpqHeFltTolPowerSupplyModel • cpqHeFltTolPowerSupplySerialNumber • cpqHeFltTolPowerSupplyAutoRev • cpqHeFltTolPowerSupplyFirmwareRev • cpqHeFltTolPowerSupplySparePartNum • cpqSiServerSystemId Supporting SNMP Trap Description: “The Power Supply AC power loss in [sysName], Bay [cpqHeFltTolPowerSupplyBay], Status [cpqHeFltTolPowerSupplyStatus], Model [cpqHeFltTolPowerSupplyModel], Serial Num [cpqHeFltTolPowerSupplySerialNumber], Firmware [cpqHeFltTolPowerSupplyFirmwareRev].”...
Page 348 Log Severity: Warning (2) Log Message: The Thermal Temperature Condition has been set to degraded. The system may be shut down due to this thermal condition depending on the state of the thermal degraded action value '%4'. SNMP Trap: cpqHe3ThermalTempDegraded - 6018 in CPQHLTH.MIB Symptom: The temperature status has been set to degraded.
Page 349 Log Message: A System Fan Condition has been set to degraded. If the system fan is part of a redundancy group, the system will not be shut down. If the system fan is not part of a redundancy group, the system may be shut down depending on the state of the thermal degraded action value '%4'.
Page 350 Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags Supporting SNMP Trap Description: “CPU fan is now OK.” 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.
Page 351: Event Identifiers 1103-1183
Event Identifiers 1103-1183 NT Event ID: 1103 (Hex)0x8435044f (cpqsvmsg.dll) Log Severity: Warning (2) Log Message: The Fault Tolerant Power Sub-system has been set to Degraded. Check power connections and replace the power supply as needed. SNMP Trap: cpqHe3FltTolPwrSupplyDegraded - 6028 in CPQHLTH.MIB Symptom: The fault tolerant power supply sub-system condition has been set to degraded.
Page 352 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. Supporting SNMP Trap Data: •...
Page 353 • sysName • cpqHoTrapFlags Supporting SNMP Trap Description: “Remote Insight keyboard cable disconnected.” NT Event ID: 1114 (Hex)0x8435045a (cpqsvmsg.dll) Log Severity: Warning (2) Log Message: A processor has crossed the threshold of allowable corrected errors. The processor should be replaced. SNMP Trap: cpqSeCpuThresholdPassed - 1005 in CPQSTDEQ.MIB Symptom: This trap is sent when an internal processor error threshold has been passed on a particular processor, causing it to become degraded.
Page 354 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. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags •...
Page 355 Symptom: Mouse Cable Disconnected. The Remote Insight mouse cable has been disconnected. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags Supporting SNMP Trap Description: “Remote Insight mouse cable disconnected.” NT Event ID: 1117 (Hex)0x8435045d (cpqsvmsg.dll) Log Severity: Warning (2) Log Message: The Remote Insight Board has detected that the external power cable is disconnected. SNMP Trap: cpqSm2ExternalPowerCableDisconnected - 9010 in CPQSM2.MIB Symptom: External Power Cable Disconnected.
Page 356 NT Event ID: 1123 (Hex)0x84350463 (cpqsvmsg.dll) Log Severity: Warning (2) Log Message: Post Errors were detected. One or more Power-On-Self-Test errors were detected during server startup. SNMP Trap: cpqHe3PostError - 6027 in CPQHLTH.MIB Symptom: One or more POST errors occurred. Power On Self-Test (POST) errors occur during the server restart process.
Page 357 SNMP Trap: cpqHe4FltTolPowerSupplyFailed - 6050 in CPQHLTH.MIB Symptom: The fault tolerant power supply condition has been set to failed for the specified chassis and bay location. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqHeFltTolPowerSupplyChassis • cpqHeFltTolPowerSupplyBay • cpqHeFltTolPowerSupplyStatus •...
Page 358 Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqHeFltTolPowerSupplyChassis • cpqHeFltTolPowerSupplyBay Supporting SNMP Trap Description: “The Power Supply Inserted on Chassis [cpqHeFltTolPowerSupplyChassis], Bay [cpqHeFltTolPowerSupplyBay].” NT Event ID: 1128 (Hex)0x84350468 (cpqsvmsg.dll) Log Severity: Warning (2) Log Message: Fault Tolerant Power Supply Removed. A hot-plug fault tolerant power supply has been removed from the system.
Page 359 Symptom: The Fault Tolerant Fan condition has been set to failed for the specified chassis and fan. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqHeFltTolFanChassis • cpqHeFltTolFanIndex Supporting SNMP Trap Description: “The Fan Failed on Chassis [cpqHeFltTolFanChassis], Fan [cpqHeFltTolFanIndex].”...
Page 360 Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqHeFltTolFanChassis • cpqHeFltTolFanIndex Supporting SNMP Trap Description: “The Fan Removed on Chassis [cpqHeFltTolFanChassis], Fan [cpqHeFltTolFanIndex].” NT Event ID: 1134 (Hex)0xc435046e (cpqsvmsg.dll) Log Severity: Error (3) Log Message: A Temperature Sensor Condition has been set to failed. The system will be shut down due to this overheat condition.
Page 361 NT Event ID: 1136 (Hex)0x44350470 (cpqsvmsg.dll) Log Severity: Information (1) Log Message: A Temperature Sensor Condition has been set to OK. The system's temperature has returned to the normal operating range. SNMP Trap: cpqHe3TemperatureOk - 6042 in CPQHLTH.MIB Symptom: The temperature status has been set to OK in the specified chassis and location. The server's temperature has returned to the normal operating range.
Page 362 • cpqHePwrConvChassis • cpqHePwrConvSlot • cpqHePwrConvSocket Supporting SNMP Trap Description: “The Power Converter Failed on Chassis [cpqHePwrConvChassis], Slot [cpqHePwrConvSlot], Socket [cpqHePwrConvSocket].” NT Event ID: 1139 (Hex)0x84350473 (cpqsvmsg.dll) Log Severity: Warning (2) Log Message: The DC-DC power converter is in a failed state. Replace System Information Agent: Health: The DC-DC Power Converter sub-system has lost redundancy.
Page 363 User Action: None. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags • cpqSiHotPlugSlotChassis • cpqSiHotPlugSlotIndex Supporting SNMP Trap Description: “Hot Plug Slot Board Inserted into Chassis [cpqSiHotPlugSlotChassis], Slot [cpqSiHotPlugSlotIndex].” NT Event ID: 1142 (Hex)0xc4350476 (cpqsvmsg.dll) Log Severity: Error (3) Log Message: Hot Plug PCI Board Failed. A hot plug PCI adapter has failed to power up. Insure the board and all cables are installed correctly.
Page 364 • cpqRackUid • cpqRackSerialNum • cpqRackTrapSequenceNum Supporting SNMP Trap Description: “The rack name has changed to [cpqRackName].” NT Event ID: 1144 (Hex)0x44350478 (cpqsvmsg.dll) Log Severity: Information (1) Log Message: Rack Enclosure Name Changed. SNMP Trap: cpqRackEnclosureNameChanged - 22002 in CPQRACK.MIB Symptom: The enclosure name has changed.
Page 365 • cpqRackUid • cpqRackCommonEnclosureName • cpqRackCommonEnclosureModel • cpqRackCommonEnclosureSerialNum • cpqRackCommonEnclosureSparePartNumber • cpqRackCommonEnclosureTrapSequenceNum Supporting SNMP Trap Description: “The enclosure [cpqRackCommonEnclosureName] has been removed from rack [cpqRackName].” NT Event ID: 1146 (Hex)0x4435047a (cpqsvmsg.dll) Log Severity: Information (1) Event Title: Enclosure Inserted Log Message: This trap indicates that an enclosure has been inserted into the rack. SNMP Trap: cpqRackEnclosureInserted - 22004 in CPQRACK.MIB Symptom: The enclosure has been inserted.
Page 366 User Action: Shut down the enclosure and possibly the rack as soon as possible. Be sure that all fans are working properly and that air flow in the rack has not been blocked. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags •...
Page 367 Log Severity: Information (1) Event Title: Rack Enclosure Temperature Normal Log Message: This trap indicates that an enclosure temperature sensor has returned to normal. SNMP Trap: cpqRackEnclosureTempOk - 22007 in CPQRACK.MIB Symptom: The enclosure temperature status has been set to OK. This trap indicates that an enclosure temperature sensor has returned to normal.
Page 368 • cpqRackCommonEnclosureFanSparePartNumber • cpqRackCommonEnclosureTrapSequenceNum Supporting SNMP Trap Description: “The enclosure [cpqRackCommonEnclosureName] fan in rack [cpqRackName] has been set to failed.” NT Event ID: 1151 (Hex)0x8435047f (cpqsvmsg.dll) Log Severity: Warning (2) Event Title: Rack Enclosure Fan Degraded Log Message: This trap indicates that an enclosure fan has failed but other fans in the redundant fan group are still operating.
Page 369 • cpqRackName • cpqRackUid • cpqRackCommonEnclosureName • cpqRackCommonEnclosureSerialNum • cpqRackCommonEnclosureFanLocation • cpqRackCommonEnclosureFanSparePartNumber • cpqRackCommonEnclosureTrapSequenceNum Supporting SNMP Trap Description: “The enclosure [cpqRackCommonEnclosureName] fan in rack [cpqRackName] has been set to ok.” NT Event ID: 1153 (Hex)0x84350481 (cpqsvmsg.dll) Log Severity: Warning (2) Event Title: Rack Enclosure Fan Removed Log Message: The enclosure fan has been removed.
Page 370 • sysName • cpqHoTrapFlags • cpqRackName • cpqRackUid • cpqRackCommonEnclosureName • cpqRackCommonEnclosureSerialNum • cpqRackCommonEnclosureFanLocation • cpqRackCommonEnclosureFanSparePartNumber • cpqRackCommonEnclosureTrapSequenceNum Supporting SNMP Trap Description: “The enclosure [cpqRackCommonEnclosureName] fan in rack [cpqRackName] has been inserted.” NT Event ID: 1155 (Hex)0xc4350483 (cpqsvmsg.dll) Log Severity: Error (3) Event Title: Rack Power Supply Failed Log Message: This trap indicates that a power supply has failed.
Page 371 SNMP Trap: cpqRackPowerSupplyDegraded - 22014 in CPQRACK.MIB Symptom: The power supply status has been set to degraded. This trap indicates that a power supply has degraded. User Action: Replace the power supply as soon as possible. Supporting SNMP Trap Data: •...
Page 372 • cpqRackCommonEnclosureSerialNum • cpqRackCommonEnclosureTrapSequenceNum Supporting SNMP Trap Description: “The power supply [cpqRackPowerSupplyPosition] in enclosure [cpqRackPowerSupplyEnclosureName] in rack [cpqRackName] has been set to ok.” NT Event ID: 1158 (Hex)0x84350486 (cpqsvmsg.dll) Log Severity: Warning (2) Event Title: Rack Power Supply Removed Log Message: The power supply has been removed. SNMP Trap: cpqRackPowerSupplyRemoved - 22016 in CPQRACK.MIB Symptom: The power supply has been removed.
Page 373 • cpqRackUid • cpqRackPowerSupplyEnclosureName • cpqRackPowerSupplySerialNum • cpqRackPowerSupplyPosition • cpqRackPowerSupplyFWRev • cpqRackPowerSupplySparePartNumber • cpqRackCommonEnclosureSerialNum • cpqRackCommonEnclosureTrapSequenceNum Supporting SNMP Trap Description: “The power supply [cpqRackPowerSupplyPosition] in enclosure [cpqRackPowerSupplyEnclosureName] in rack [cpqRackName] has been inserted.” NT Event ID: 1160 (Hex)0x84350488 (cpqsvmsg.dll) Log Severity: Warning (2) Event Title: Rack Power Subsystem Not Redundant Log Message: The rack power subsystem is no longer in a redundant state.
Page 374 • sysName • cpqHoTrapFlags • cpqRackName • cpqRackUid • cpqRackPowerSupplyEnclosureName • cpqRackPowerSupplyPosition • cpqRackPowerSupplyFWRev • cpqRackPowerSupplyInputLineStatus • cpqRackPowerSupplySparePartNumber • cpqRackCommonEnclosureSerialNum • cpqRackCommonEnclosureTrapSequenceNum Supporting SNMP Trap Description: “The rack power supply detected an input line voltage problem in power supply [cpqRackPowerSupplyPosition], enclosure [cpqRackPowerSupplyEnclosureName], rack [cpqRackName].”...
Page 375 SNMP Trap: cpqRackPowerShedAutoShutdown - 22021 in CPQRACK.MIB Symptom: Server shutdown due to power shedding. The server blade was shut down due to a lack of power. User Action: Check power connections or add power supplies. Supporting SNMP Trap Data: • sysName •...
Page 376 NT Event ID: 1165 (Hex)0xc435048d (cpqsvmsg.dll) Log Severity: Error (3) Event Title: Not Enough Power To Power On Log Message: Inadequate power to power on. SNMP Trap: cpqRackServerPowerOnFailedNotEnoughPower - 22023 in CPQRACK.MIB Symptom: Inadequate power to power on. There is not enough power to power on the server blade. User Action: Check power connections or add power supplies.
Page 377 • cpqRackCommonEnclosureSerialNum • cpqRackCommonEnclosureTrapSequenceNum Supporting SNMP Trap Description: “Inadequate power to power on blade [cpqRackServerBladePosition], in enclosure [cpqRackServerBladeEnclosureName], in rack [cpqRackName].” NT Event ID: 1167 (Hex)0xc435048f (cpqsvmsg.dll) Log Severity: Error (3) Event Title: Inadequate Power To Power On Log Message: There is not enough power to power on the server blade. The power enclosure micro-controller was not found.
Page 378 • cpqRackUid • cpqRackServerBladeEnclosureName • cpqRackServerBladePosition • cpqRackServerBladeSparePartNumber • cpqRackCommonEnclosureSerialNum • cpqRackCommonEnclosureTrapSequenceNum Supporting SNMP Trap Description: “Server power on via manual override on blade [cpqRackServerBladePosition], in enclosure [cpqRackServerBladeEnclosureName], in rack [cpqRackName].” NT Event ID: 1169 (Hex)0x84350491 (cpqsvmsg.dll) Log Severity: Warning (2) Event Title: Fuse or Breaker Tripped Log Message: The fuse has been tripped.
Page 379 • sysName • cpqHoTrapFlags • cpqRackName • cpqRackUid • cpqRackServerBladeEnclosureName • cpqRackServerBladeName • cpqRackServerBladePosition • cpqRackServerBladeSparePartNumber • cpqRackCommonEnclosureSerialNum • cpqRackCommonEnclosureTrapSequenceNum Supporting SNMP Trap Description: “Server blade [cpqRackServerBladeName] removed from position [cpqRackServerBladePosition], in enclosure [cpqRackServerBladeEnclosureName], in rack [cpqRackName].” NT Event ID: 1171 (Hex)0x44350493 (cpqsvmsg.dll) Log Severity: Information (1) Event Title: Server Blade Inserted Log Message: The server blade has been inserted from the enclosure.
Page 380 Event Title: Rack Power Subsystem Not Load Balanced Log Message: The power subsystem is out of balance for this power enclosure. SNMP Trap: cpqRackPowerChassisNotLoadBalanced - 22030 in CPQRACK.MIB Symptom: Power subsystem not load balanced. The power subsystem is out of balance for this power enclosure.
Page 381 Supporting SNMP Trap Description: “Power subsystem DC power problem in enclosure [cpqRackCommonEnclosureName], in rack [cpqRackName].” NT Event ID: 1174 (Hex)0x84350496 (cpqsvmsg.dll) Log Severity: Warning (2) Event Title: Power Subsystem Facility AC Power Problem Log Message: The AC facility input power has been exceeded for this power enclosure. SNMP Trap: cpqRackPowerChassisAcFacilityPowerExceeded - 22032 in CPQRACK.MIB Symptom: Power subsystem AC facility input power exceeded for this power enclosure.
Page 382 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. SNMP Trap: cpqRackPowerChassisLoadBalancingWireMissing - 22034 in CPQRACK.MIB Symptom: Power subsystem load balancing wire missing.
Page 383 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 Log Message: The power subsystem has been improperly configured. SNMP Trap: cpqRackPowerChassisConfigError - 22036 in CPQRACK.MIB Symptom: Power subsystem improperly configured.
Page 384 Symptom: The Management processor is ready. The management processor has successfully reset and is now available again. User action: None Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags Supporting SNMP Trap Description: “The Management processor is ready after a successfull reset” NT Event ID: 1181 (Hex) 0x8435049D (cpqsvmsg.dll) Log Severity: Warning (3) Log Message: The Management Processor has not reset successfully and is not operational.
Page 385: Event Identifiers 1539-3352
Symptom: The USB key has been removed from the server. User Action: None required. Supporting SNMP Trap Data: • 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)
Page 386 Log Message: The SNMP Agent is older than other components. The SNMP Agent is older than the other components of the Server Agents. Reinstall the entire Server Agents package to correct this error. Event identifier: cpqsvmsg.dll - 1796 (Hex)0x84350704 (Service Event) Log Severity: Warning (2) Log Message: The %1 Agent is older than other components.
Page 387: Event Identifiers 5632-5684
Log Severity: Warning (2) 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 - 3332 (Hex)0x84350d04 (Service Event) Log Severity: Warning (2) Log Message: Could not read the registry sub-key: “%1”.
Page 388 Log Severity: Warning (2) Log Message: “%1”. The data contains the error code. Event identifier: cpqsvmsg.dll - 5635 (Hex)0x84351603 (Service Event) Log Severity: Warning (2) Log Message: “%1”. The data contains the error code. Event identifier: cpqsvmsg.dll - 5636 (Hex)0x84351604 (Service Event) Log Severity: Warning (2) Log Message: The Rack And Enclosure MIB Agent could not read the registry value “%1”.
Page 389: Nic Agents
Log Severity: Warning (2) Log Message: The Rack And Enclosure MIB Agent received an unknown action code from the service. The data contains the action code. Event identifier: cpqsvmsg.dll - 5645 (Hex)0x8435160d (Service Event) Log Severity: Warning (2) Log Message: The Rack And Enclosure MIB Agent could not get the system type. The data contains the error code.
Page 390 Log Message: The NIC Management Agent could not set the service status with the Service Control Manager. The data contain the error code. Event identifier: cpqnimsg.dll - 260 (Hex)0x84350104 (Service Event) Log Severity: Warning (2) Log Message: The NIC Management Agent could not start the Service Control Dispatcher. The data contain the error code.
Page 391 Event identifier: cpqnimsg.dll - 269 (Hex)0xc435010d (Service Event) Log Severity: Error (3) Log Message: The NIC Management Agent encountered a fatal error. The service is terminating. The data contain the error code. Event identifier: cpqnimsg.dll - 270 (Hex)0x8435010e (Service Event) Log Severity: Warning (2) Log Message: Unable to create thread.
Page 392 Log Message: The NIC Management Agent could not set an event. The data contain the error code. Event identifier: cpqnimsg.dll - 280 (Hex)0x84350118 (Service Event) Log Severity: Warning (2) Log Message: The NIC Management Agent service could not start any agents successfully. Event identifier: cpqnimsg.dll - 281 (Hex)0x84350119 (Service Event) Log Severity: Warning (2) Log Message: The NIC Management Agent main thread did not terminate properly.
Page 393: Event Identifiers 300-1293
Event identifier: cpqnimsg.dll - 296 (Hex)0xc4350128 (Service Event) Log Severity: Error (3) Log Message: A driver for a NIC failed to open. This error can be caused by an improperly installed adapter. Removing and reinstalling all adapters may correct the problem. The NIC Agent service will not respond to any management requests.
Page 394 Log Message: The %1 Agent is older than other components. The %1 Agent is older than the other components of the Insight Agents. Reinstall the entire Insight Agents package to correct this error. Event identifier: cpqnimsg.dll - 1029 (Hex)0x84350405 (Service Event) Log Severity: Warning (2) Log Message: The NIC SNMP Management Agent has failed to refresh data associated with key %1.
Page 395 Event identifier: cpqnimsg.dll - 1038 (Hex)0x8435040e (Service Event) Log Severity: Warning (2) Log Message: The Management Agent service is not running. The SNMP Management Agent has determined that the Management Agent service is not running. Stop the SNMP service and restart the Management Agents service.
Page 396 SNMP Trap: cpqNicRedundancyReduced - 18004 in CPQNIC.MIB Symptom: This trap is sent any time a physical adapter in a logical adapter group changes to the Failed condition, but at least one physical adapter remains in the OK condition. This can be caused by loss of link due to a cable being removed from the adapter or the Hub or Switch.
Page 397 Log Severity: Error (3) Log Message: Connectivity has been lost for the NIC in slot %1, port %2. SNMP Trap: cpqNic3ConnectivityLost - 18012 in CPQNIC.MIB Symptom: This trap is sent any time the status of a logical adapter changes to the Failed condition. This occurs when the adapter in a single adapter configuration fails, or when the last adapter in a redundant configuration fails.
Page 398 • cpqNicIfPhysAdapterStatus • cpqSePciSlotBoardName • cpqNicIfPhysAdapterPartNumber • ipAdEntAddr • cpqNicIfLogMapIPV6Address • cpqNicIfLogMapAdapterOKCount Supporting SNMP Trap Description: “Redundancy increased by adapter in slot [cpqNicIfPhysAdapterSlot], port [cpqNicIfPhysAdapterPort].” NT Event ID: 1293 (Hex)0xc435050D (cpqnimsg.dll) Log Severity: Error (3) Log Message: Redundancy has been reduced by the NIC in slot %1, port %2. Number of functional NICs in the team: %3.
Page 399: Support And Other Resources
Active Health System log (HP ProLiant Gen8 or later products) Download and have available an Active Health System log for 7 days before the failure was detected. For more information, see the HP iLO 4 User Guide or HP Intelligent Provisioning User Guide on the HP website (http://www.hp.com/go/ilo/docs).
Page 400: Acronyms And Abbreviations
Acronyms and abbreviations Array Configuration Utility Advanced Data Guarding (also known as RAID 6) Array Diagnostics Utility Automatic Server Recovery certificate authority Common Gateway Interface command line protocol CONREP Configuration Replication utility DDNS Dynamic Domain Name System DHCP Dynamic Host Configuration Protocol direct memory access domain name system Acronyms and abbreviations 400...
Page 401 FBDIMM fully buffered DIMM FBWC flash-backed write cache heartbeat host bus adapter HP SIM HP Systems Insight Manager HP SSA HP Smart Storage Administrator HPRCU HP ROM Configuration Utility Integrated Lights-Out Integrated Management Log Integrated Remote Console...
Page 402 Lights-Out Management Microsoft Management Console nonmaskable interrupt network time protocol NVRAM nonvolatile memory PERL Practical Extraction and Report Language POST Power-On Self Test processor power module RBSU ROM-Based Setup Utility RIBCL Remote Insight Board Command Language RILOE Remote Insight Lights-Out Edition RILOE II Remote Insight Lights-Out Edition II reserve information sector...
Page 403 SATA serial ATA SLES SUSE Linux Enterprise Server SMART self-monitoring analysis and reporting technology solid-state drive Secure Shell Secure Sockets Layer single sign-on Selective Storage Presentation UEFI Unified Extensible Firmware Interface unit identification WINS Windows® Internet Naming Service Acronyms and abbreviations 403...
Page 404: Documentation Feedback
Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (mailto:docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Page 405: Index
Index 100 series, error messages 49 5009 - Server OA fault event 225 1003 - VCM-OA communication down 217 5012 - Server state FAILED 226 1022 - Domain state FAILED 218 5014 - Server state INCOMPATIBLE 226 1023 - Domain state PROFILE_FAILED 218 5019 - Server state is NO_COMM 226 1026 - Domain state NO_COMM 218 5022 - Missing information for one or more blades of a...
Page 406 controller failure 13, 74 controller LEDs 101, 102 accelerator error log 9 controller runtime LEDs 101, 102, 103, 104 accelerator status 10, 11, 12 controller state 33 ActiveX 247 controllers, array 13, 14, 20, 26, 80 adapters 12, 17 cookie behavior 255 ADG enabler dongle is broken or missing 12 cookie sharing, browser instances 254 ADU error messages 9, 29...
Page 407 8 error messages, POST 39 error messages, RIBCL 238 errors 16 HP Insight Diagnostics 94 Ethernet Module events, Virtual Connect 221 hub link error 41 Ethernet Network events, Virtual Connect 229 event identifiers 1025-1092, server agents 342...
Page 408 Onboard Administrator internal log messages 200 One Button Disaster Recovery 47 keyboard 43, 44 online spare memory 39 keyboard problems 43, 44, 63 operating system problems 95 keyboard, incorrect LED display 252 operational log messages 185 keytab, issues generating using ktpass.exe 258 overheating 97 LCD log messages 184 parity errors 9, 16, 44...
Page 409 339 unable to pass data through an SSH terminal 254 server events, Virtual Connect 225 unable to receive HP SIM alarms from iLO 246 server setup 12 unable to return to login page 244 shared ports 83...
Page 410 warning messages 27, 28 Windows driver errors, Smart Array 157 Windows event identifiers and SNMP traps 261 Windows Event Log 106, 261 Windows Event Log processor error codes 97 Index 410...

HP ProLiant Gen9 Troubleshooting Manual

Introduction

A

HP Proliant Gen9 Power Fault Leds

HP Smart Array Errors

HP Onboard Administrator Errors

HP Virtual Connect Errors

HPRCU Errors

CONREP Errors

HP Ilo Errors

Microsoft Windows Event ID and SNMP Traps

Quick Links

Troubleshooting Guide

Troubleshooting

Related Manuals for HP ProLiant Gen9

Summary of Contents for HP ProLiant Gen9