HP ProLiant Gen8 Troubleshooting Guide Volume II: Error Messages 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.
© Copyright 2012, 2013 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. Microsoft®, Windows®, and Windows Vista® are U.S.
Contents Introduction .................................................................................................................................. 8 Overview ................................................................................................................................................. 8 Troubleshooting resources................................................................................................................. 8 HP ProLiant server errors ................................
Message ID: 4140 ........................................................................................................................ 99 Message ID: 4141 ........................................................................................................................ 99 Message ID: 4169 ........................................................................................................................ 99 Message ID: 4190 ........................................................................
Command line event notifications ............................................................................................................ 203 HP Virtual Connect errors........................................................................................................... 205 SNMP overview .................................................................................................................................... 205 SNMP traps ..................................................................
Monitor problems in IRC or Java Remote Console ............................................................................ 243 Mouse/keyboard not working in IRC or Java Remote Console ........................................................... 243 IRC sends characters continuously after switching windows ............................................................... 243 Java Remote Console does not display the correct floppy and USB-key device .....................................
NIC agents ........................................................................................................................................... 383 Event Identifiers 256-299 ............................................................................................................. 383 Event Identifiers 300-1293 ........................................................................................................... 387 Support and other resources .................................................
Introduction Overview This guide is part of a two volume set. Volume I, the HP ProLiant Gen8 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. Use these messages to troubleshoot and optimize the operation of your HP equipment.
HP ProLiant server errors ADU error messages Introduction to ADU error messages This section contains a complete alphabetical list of all ADU error messages for ADU version 7.85.16.0 and earlier. IMPORTANT: This guide provides information for multiple servers. Some information may not apply to the server you are troubleshooting. Refer to the server documentation for information on procedures, hardware options, software tools, and operating systems supported by the server.
Accelerator Status: Cache was Automatically Configured During Last Controller Reset Description: Cache board was replaced with one of a different size. Action: No action is required. Accelerator Status: Data in the Cache was Lost... ...due to some reason other than the battery being discharged. Description: Data in cache was lost, but not because of the battery being discharged. Action: Be sure the array accelerator is properly seated. If the error persists, you may need to replace the array accelerator.
Accelerator Status: Obsolete Data Detected Description: During reset initialization, obsolete data was found in the cache due to the drives being moved and written to by another controller. Action: No action is required. The controller either writes the data to the drives or discards the data completely. Accelerator Status: Obsolete Data was Discarded Description: During reset initialization, obsolete data was found in the cache, and was discarded (not written to the drives). Action: No action is required.
Accelerator Status: Warranty Alert Description: Catastrophic problem exists with array accelerator board. Refer to other messages on Diagnostics screen for exact meaning of this message. Action: Replace the array accelerator board. Adapter/NVRAM ID Mismatch Description: EISA NVRAM has an ID for a different controller from the one physically present in the slot. Action: Run the server setup utility. Array Accelerator Battery Pack X not Fully Charged Description: Battery is not fully charged.
Configuration Signature is Zero Description: ADU detected that NVRAM contains a configuration signature of zero. Old versions of the server setup utility could cause this. Action: Run the latest version of server setup utility to configure the controller and NVRAM. Configuration Signature Mismatch Description: The array accelerator board is configured for a different array controller board.
Controller Reported POST Error. Error Code: X Description: The controller returned an error from its internal POST. Action: Replace the controller. Controller Restarted with a Signature of Zero Description: ADU did not find a valid configuration signature to use to get the data. NVRAM may not be present (unconfigured) or the signature present in NVRAM may not match the signature on the controller. Action: Run the server setup utility to configure the controller and NVRAM.
Drive (Bay) X is a Replacement Drive Description: This drive has been replaced. This message is displayed if a drive is replaced in a fault-tolerant logical volume. Action: If the replacement was intentional, allow the drive to rebuild.
Drive Monitoring Features Are Unobtainable Description: ADU is unable to get monitor and performance data due to a fatal command problem (such as drive time-out), or is unable to get data due to these features not being supported on the controller. Action: Check for other errors such as time-outs. If no other errors occur, upgrade the firmware to a version that supports monitor and performance, if desired.
Identify Logical Drive Data did not Match with NVRAM Description: The identify unit data from the array controller does not match with the information stored in NVRAM. This can occur if new, previously configured drives have been placed in a system that has also been previously configured. Action: Run the server setup utility to configure the controller and NVRAM.
Otherwise, follow the procedures for correcting problems when an incorrect drive is replaced or a loose cable is detected. Logical Drive X Status = Interim Recovery (Volume Functional, but not Fault Tolerant) Description: A physical drive in this logical drive has failed. The logical drive is operational, but the loss of an additional drive may cause permanent data loss. Action: Replace the failed drive as soon as possible. Logical Drive X Status = Loose Cable Detected... ...
Logical Drive X Status = Wrong Drive Replaced Description: A physical drive in this logical drive has failed. The incorrect drive was replaced. Action: 1. Power down the server. 2. Replace the drive that was incorrectly replaced. 3. Replace the original drive that failed with a new drive. CAUTION: Do not run the server setup utility and try to reconfigure, or data will be lost.
Other Controller Indicates Different Hardware Model Description: The other controller in the redundant controller configuration is a different hardware model. Action: Be sure both controllers are using the same hardware model. If they are, make sure the controllers are fully seated in their slots. Other Controller Indicates Different Firmware Version Description: The other controller in the redundant controller configuration is using a different firmware version.
RIS Copies Between Drives Do Not Match Description: The drives on this controller contain copies of the RIS that do not match. The hard drives in the array do not have matching configuration information. Action: 1. Resolve all other errors encountered. 2. Obtain the latest version of ADU, and then rerun ADU. 3. If unconfigured drives were added, configure these drives using ACU. 4.
3. Restart the system. 4. If the problem persists, replace the cables and connectors as needed. SCSI Port X, Drive ID Y RIS Copies Within This Drive Do Not Match Description: The copies of RIS on the drive do not match. Action: Check for other errors. The drive may need to be replaced. SCSI Port X, Drive ID Y...S.M.A.R.T. Predictive Failure Errors Have Been Detected in the Factory Monitor and Performance Data... ...SOLUTION: Please replace this drive when conditions permit.
Storage Enclosure on SCSI Bus X has a Cabling Error (Bus Disabled)... ...SOLUTION: The SCSI controller has an internal and external cable attached to the same bus. Please disconnect the internal or external cable from the controller. If this controller supports multiple buses, the cable disconnected can be reattached to an available bus. Description: The current cabling configuration is not supported. Action: Refer to the server documentation for cabling guidelines, and reconfigure as indicated.
Description: One or more fans in the external storage unit have failed. Action: Replace the failed fans. Storage Enclosure on SCSI Bus X Indicated that the Fan Module is Unplugged... ...SOLUTION: Make sure the fan module is properly connected. Description: A fan in the external storage unit is not connected properly. Action: Check and reseat all fan connections securely. Storage Enclosure on SCSI Bus X - Wide SCSI Transfer Failed... ...SOLUTION: This may indicate a bad SCSI cable on bus X.
Swapped Cables or Configuration Error Detected. An Unsupported Drive Arrangement Was Attempted... ...SOLUTION: Power down system then move drives back to their original location. Description: One or more physical drives were moved, causing a configuration that is not supported. Action: Move all drives to their original locations, and then refer to the server documentation for supported configurations. Swapped cables or configuration error detected. The cables appear to be interchanged... ...
System Board is Unable to Identify which Slots the Controllers are in Description: The slot indicator on the system board is not working correctly. Firmware recognizes both controllers as being installed in the same slot. Action: 1. Be sure both controllers are fully seated in their slots. If the problem persists, this might indicate a controller problem or a system board problem. CAUTION: Only authorized technicians trained by HP should attempt to remove the system board.
Description: ADU requested the identify controller data from the controller, but was unable to obtain it. This usually indicates that the controller is not seated properly or has failed. Action: 1. Power down the server. 2. Be sure the controller is fully seated. 3. Restart the server. 4. Resolve any error messages displayed by the controller. If this does not solve the problem, contact an HP authorized service provider.
WARNING - Resetting Corrupted CMOS Description: This informational message displays when the ROM detects that CMOS is corrupted. The default values are restored. This message does not display if a user has intentionally invalidated the configuration through RBSU by erasing NVRAM. WARNING - Resetting Corrupted NVRAM Description: This informational message displays when the ROM detects that NVRAM is corrupted. The default values are restored.
ADU version 8.0 through 8.28 error messages This section contains a complete alphabetical list of all ADU error messages. ADU is being replaced by the ACU diagnostics feature. If the following versions are installed on the server, see the messages in this section: • ADU version 8.0 through ADU version 8.25 • ACU diagnostics 8.28 and later Array Accelerator: The batteries were hot-removed. Action: Replace the batteries.
Array Accelerator: The cache is disabled because a capacitor has failed to charge to an acceptable level. Action: Replace the capacitor. Array Accelerator: The cache is disabled because the backup operation to flash memory failed. Action: Reseat the controller cache module. If the problem persists, contact HP support ("HP contact information" on page 393). Array Accelerator: The cache is disabled because there are no capacitors attached to the cache module. Action: Install a capacitor.
Action: Upgrade the controller to the latest firmware. If the problem persists, move the configured arrays back to the original controller. Controller State: The array controller contains more logical drives than are supported in the current configuration… …Any configuration command (e.g. logical drive creation, array expansion, etc.) or modification to the controller will result in the loss of all existing data on the disabled volume(s). Action: Identify the drives that contain the lost logical volumes.
Controller State: The array controller is operating without a memory board and has a bad volume position… …Any configuration command (e.g. logical drive creation, array expansion, etc.) or modification to the controller will result in the loss of all existing data on the disabled volume(s). Action: Install a cache memory module.
module if not present. 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 393). Controller State: The controller cannot be configured. CACHE STATUS PROBLEM DETECTED:... …The cache on this controller has a problem.
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 ACU. Action: Re-enable the physical drive using the Array Configuration Utility. Drive Offline due to Erase Operation: The physical drive is offline from having an erase in progress. Action: No action is required.
Logical drive state: The logical drive is offline from being ejected. Action: Reinstall the removed physical drives. Logical drive state: The logical drive is queued for erase. Action: No action is required. Logical drive migrate and extend operations are not possible while the erase operation is in progress. Logical drive state: The logical drive is queued for expansion. Action: No action is required. Logical drive state: The logical drive is queued for rebuilding. Action: No action is required.
3. Restore all data to the new drive. If this drive is part of a fault-tolerant configuration, do not replace this drive unless all other drives in the array are online. Physical Drive State: This drive is not supported for configuration... ...and should be disconnected from this controller. Action: Replace the physical drive with a drive supported by the controller. Physical Drive State: SATA drives are not supported for configuration and should be disconnected from this 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 393). Redundancy State: This controller has been setup to be part of a redundant pair of controllers.... ...but redundancy is temporarily disabled. Redundancy is temporarily disabled because capacity expansion, extension, or migration is in progress. Redundancy will be enabled when this process is complete.
Smart SSD State: SSD has less than 5% of usage remaining before wearout… …It has less than an estimated 56 days before it reaches the maximum usage limit and should be replaced as soon as possible. Action: Replace the SSD as soon as possible. Smart SSD State: SSD has less than an estimated 56 days before it reaches the maximum usage limit for writes (wearout)... ...and should be replaced as soon as possible. Action: Replace the SSD as soon as possible.
POST error messages and beep codes Introduction to POST error messages The error messages and codes in this section include all messages generated by ProLiant servers. Some messages are informational only and do not indicate any error. A server generates only the codes that are applicable to its configuration and options. HP ProLiant p-Class server blades do not have speakers and thus do not support audio output. Disregard the audible beeps information if the server falls into this category.
Audible Beeps: None Possible Cause: This message indicates RAID Memory is enabled and indicates the amount of memory reserved for this feature. Action: None. An Unexpected Shutdown occurred prior to this power-up Audible Beeps: None Possible Cause: The server shut down because of an unexpected event on the previous boot. Action: Check the System Management Log or OS Event Log for details on the failure.
Fatal Front Side Bus Error Audible Beeps: None Possible Cause: The processor front-side bus experienced a fatal error. Action: 1. Run Insight Diagnostics. CAUTION: Before replacing or reseating 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. 2.
Illegal Opcode - System Halted Audible Beeps: None Possible Cause: The server has entered the Illegal Operator Handler because of an unexpected event. This error is often software-related and does not necessarily indicate a hardware issue. Action: Run Insight Diagnostics and replace any failed components as indicated. Be sure that all software is installed properly. iLO Generated NMI Audible Beeps: None Possible Cause: The iLO controller generated an NMI.
Memory found on unpopulated Node. — Processor is required to be installed for memory to be used. Description: The system detects DIMMs, but is unable to use the DIMMs because a processor is not installed in the corresponding socket. Action: CAUTION: Before installing any processors, be sure to follow the guidelines provided in "Performing processor procedures in the troubleshooting process.
NMI - Undetermined Source Audible Beeps: None Possible Cause: An NMI event has occurred. Action: Reboot the server. Node Interleaving disabled - Invalid memory configuration Description: Each node must have the same memory configuration to enable interleaving. Action: Populate each node with the same memory configuration and enable interleaving in RBSU. No Floppy Drive Present Audible Beeps: None Possible Cause: No diskette drive is installed or a diskette drive failure has occurred. Action: 1.
Power Fault Detected in Hot-Plug PCI Slot X Audible Beeps: 2 short Possible Cause: A PCI-X hot-plug expansion slot was not powered up properly. Action: Reboot the server. Power Supply Solution Not Fully Redundant Audible beeps: None Possible cause: The minimum power supply requirement is installed, but a redundant power supply is missing or failed. Action: Do one of the following: • Install a power supply. • Replace failed power supplies to complete redundancy. Processor X Unsupported Wattage.
Audible Beeps: None Possible Cause: ROM bootblock is corrupt. Action: Contact an authorized service provider. REDUNDANT ROM ERROR: Primary ROM invalid. Booting Backup ROM. -... ...run ROMPAQ to correct error condition Audible Beeps: None Possible Cause: The primary system ROM is corrupt. The system is booting from the redundant ROM. Action: Run ROMPaq Utility to restore the system ROM to the correct version.
Correct the processor configuration. Trusted Execution Error found: 0X 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). Unsupported DIMM(s) found in system. - DIMM(s) may not be used Description: Unsupported memory types found in system.
1. Enable OBDR 2. Exit Audible Beeps: None Possible Cause: A USB tape device that supports One Button Disaster Recovery (OBDR) is installed in the system. Action: 1. Press 1 or 2. o Pressing 2 exits the configuration. o Pressing 1 starts the configuration. The following message appears Attempting to enable OBDR for the attached USB tape drive... 2. Observe the configuration progress. The following error may appear: Error - USB tape drive not in Disaster Recovery mode. 3.
Possible cause: One or more 800-MHz front side bus speed processors have been initialized at 667-MHz. Action: CAUTION: 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.
102-System Board Failure Audible Beeps: None 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 393) before proceeding. Action: Replace the system board. Run the server setup utility. 102-System Board Failure, CMOS Test Failed.
Action: Run Insight Diagnostics and replace failed components as indicated. 162-System Options Not Set Audible Beeps: 2 long Possible Cause: Configuration is incorrect. The system configuration has changed since the last boot (addition of a hard drive, for example) or a loss of power to the real-time clock has occurred. The real-time clock loses power if the onboard battery is not functioning correctly. Action: Press the F1 key to record the new configuration.
207 - Invalid Memory Configuration Detected. DIMMs installed when no corresponding processor is detected. Description: Processor is required to be installed for memory to be used. Action: CAUTION: Before installing 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.
207-Invalid Memory Configuration - Mismatched DIMMs within DIMM Bank Audible Beeps: 1 long, 1 short Possible Cause: Installed DIMMs in the same bank are of different sizes. Action: Install correctly matched DIMMs. 207-Invalid Memory Configuration - Mismatched DIMMs within DIMM Bank... ...Memory in Bank X Not Utilized. Audible Beeps: 1 long, 1 short Possible Cause: Installed DIMMs in the same bank are of different sizes. Action: Install correctly matched DIMMs.
Audible Beeps: 1 long, 1 short, or none Possible Cause: Installed DIMMs have a primary width of x8. Action: Install DIMMs that have a primary width of x4 if Advanced ECC memory support is required. 208-Memory Board Error - This error could be the result of a bad or improperly installed memory board or a system board issue Audible Beeps: 1 long, 1 short Possible Cause: The memory board is bad or improperly installed, or there is a system board issue. Action: Reseat the memory board.
210-Memory Board Power Fault on board X Audible Beeps: 1 long, 1 short Possible Cause: A problem exists with a memory board powering up properly. Action: Exchange DIMMs and retest. Replace the memory board if problem persists. 210-Memory Board Failure on board X Audible Beeps: 1 long, 1 short Possible Cause: A problem exists with a memory board powering up properly. Action: Exchange DIMMs and retest. Replace the memory board if problem persists.
230 - DIMM Configuration Error - Processor X, Channel Y - Only 2 DIMMs can be installed on a channel containing Quad-Rank DIMM(s). - System Halted! Audible beeps: Repeating long beep Possible cause: There are too many DIMMs installed on a channel containing Quad Rank DIMMs. Action: Ensure there are only two DIMMs installed on the channel. 231 - DIMM Configuration Error - No memory is available. If DIMMs are installed, verify that the corresponding processor is installed.
Possible cause: Ultra-Low Voltage (1.25V) DIMMs are not supported. Action: Install correct DIMMs. 237 - DIMM Configuration Error - Processor X, Channel Y - Only 2 DIMMs can be installed on a channel containing Quad-Rank DIMM(s). - System Halted! Audible beeps: Repeating long beep Possible cause: An incorrect number of DIMMs was detected on a channel containing Quad Rank DIMMs. Action: Ensure the correct number of DIMMs are installed.
242 - Unsupported Processor Configuration Detected – System does not support booting with three processors installed. Action: Install or remove one processor so the system has a supported number. - System Halted! Audible beeps: Constant long beep Possible cause: The system does not support booting with three processors. Action: Install an additional processor or remove one of the processors. 242 - Unsupported Processor Configuration Detected – Processors are installed in the incorrect order.
• Contact HP Service if the issue persists 246– IMPORTANT: The system has exceeded the amount of available Option ROM space. ...The Option ROM for one or more devices cannot be executed. Action: Disable unneeded Option ROMs (such as PXE). Audible beeps: 2 short Possible cause: The amount of available Option ROM space was exceeded. Action: Disable any unneeded Option ROMs. 247 – Memory Initialization Error .– Ultra-Low Voltage (1.25V) and Standard Voltage (1.5V) DIMMs are mixed in the same system.
300 Series 301-Keyboard Error Audible Beeps: None Possible Cause: Keyboard failure occurred. Action: 1. Power down the server, and then reconnect the keyboard. 2. Be sure no keys are depressed or stuck. 3. If the failure reoccurs, replace the keyboard. 301-Keyboard Error or Test Fixture Installed Audible Beeps: None Possible Cause: Keyboard failure occurred. Action: 1. Power down the server, and then reconnect the keyboard. 2. Be sure no keys are depressed or stuck. 3.
400 Series 40X-Parallel Port X Address Assignment Conflict Audible Beeps: 2 short Possible Cause: Both external and internal ports are assigned to parallel port X. Action: Run the server setup utility and correct the configuration. 404-Parallel Port Address Conflict Detected... ...A hardware conflict in your system is keeping some system components from working correctly. If you have recently added new hardware remove it to see if it is the cause of the conflict.
605-Diskette Drive Type Error. Audible Beeps: 2 short Possible Cause: Mismatch in drive type occurred. Action: Run the server setup utility to set the diskette drive type correctly. 611-Primary Floppy Port Address Assignment Conflict Audible Beeps: 2 short Possible Cause: A hardware conflict in the system is preventing the diskette drive from operating properly. Action: 1. Run the server setup utility to configure the diskette drive port address and manually resolve the conflict. 2.
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. Action: Set the Security Override Switch, and then use the iLO RBSU to enable and reset iLO. 1503: iLO 4 ROM-based Setup Utility is disabled. Possible cause: The RBSU or iLO is disabled and the Security Override Switch is set to OFF.
1611-CPU Zone Fan Assembly Failure Detected. Either... ...the Assembly is not installed or multiple fans have failed in the CPU zone. Audible Beeps: None Possible Cause: Required fans are missing or not spinning. Action: 1. Check the fans to be sure they are installed and working. 2. Be sure the assembly is properly connected and each fan is properly seated. 3. If the problem persists, replace the failed fans. 4. If a known working replacement fan is not spinning, replace the assembly.
3. If the problem persists, replace the failed fans. 1611-Fan x Not Present (Fan Zone CPU) Audible Beeps: 2 short Possible Cause: Required fan is not installed or spinning. Action: 1. Check the fans to be sure they are working. 2. Be sure each fan cable is properly connected, if applicable, and each fan is properly seated. 3. If the problem persists, replace the failed fans. 1611-Fan x Not Present (Fan Zone I/O) Audible Beeps: 2 short Possible Cause: Required fan is not installed or spinning.
1611-Redundant Fan Failure (Fan Zone System) Audible Beeps: None Possible Cause: A redundant fan is not spinning. Action: Replace the failed fan. 1612-Primary Power Supply Failure Audible Beeps: 2 short Possible Cause: Primary power supply has failed. Action: Replace power supply. 1615-Power Supply Configuration Error Audible Beeps: None Possible Cause: The server configuration requires an additional power supply.
1700 Series 1700-Slot X Drive Array - Please replace Cache Module Battery Pack... ...Caching will be enabled once the Battery Pack has been replaced and charged. Audible Beeps: None Possible Cause: The battery needs to be replaced and charged. Action: Replace and charge the battery pack. 1700-Slot X Drive Array - Please replace Array Accelerator Battery... ...The Array Accelerator Cache will be enabled once the battery has been replaced and charged.
Audible Beeps: None Possible Cause: The cache module has failed or is experiencing a fault. Action: Replace the cache module. 1704-Unsupported Virtual Mode Disk Operation - System Halted Audible Beeps: None Possible Cause: The operating system currently running does not support virtual DMA service. Action: Load or update the device driver appropriate for the operating system. 1705-Slot X Drive Array - Please replace Cache Module Super-Cap... ...
(no suitable backup found) Audible Beeps: None Possible Cause: The Bootstrap NVRAM on the specified Smart Array controller is corrupt or invalid. Action: 1. Update the controller with the latest firmware version. 2. If the problem still exists, replace the controller. 1708-Slot X Drive Array Controller - Bootstrap NVRAM restored from backup.
Audible Beeps: None Possible Cause: This configuration is not recommended because of controller memory requirements. Action: Perform RAID migration to smaller stripe size using the Array Configuration Utility. 1713-Slot X Drive Array - Redundant ROM Reprogramming Failure... ...Replace the controller if this error persists after restarting system. Audible Beeps: None Possible Cause: Flash ROM is failing. The controller detects a checksum failure, but is unable to reprogram the backup ROM. Action: 1.
1717-Slot X Drive Array - Disk Drive(s) Reporting OVERHEATED Condition: Port X Box Y Bay(s) Z Audible Beeps: None Possible Cause: The drives listed in this message are currently in an overheated state. Action: Check the fans and be sure the air flows over the drive. Install the access panel, if removed. 1718-Slot X Drive Array - Device discovery found more devices attached to this controller than firmware currently supports... ...Some devices are ignored.
Audible Beeps: None Possible Cause: The logical drive configuration has been updated automatically following physical drive position changes. Action: No action is required. 1726-Slot X Drive Array - Cache Memory Size or Battery Presence Has Changed ...Cache Module configuration has automatically been updated. Audible Beeps: None Possible Cause: The cache module configuration has been updated automatically due to replacement of the cache module (or controller) with one having different cache memory size.
1728-Slot X Drive Array - Abnormal Shut-Down Detected With Write Cache Enabled Audible Beeps: None Possible Cause: No array accelerator battery backup exists on the array controller, but caching was enabled. Any data that may have been in array accelerator memory has been lost due to the controller power loss. Action: Restore data from backup. 1729-Slot X Drive Array - Disk Performance Optimization Scan in Progress... ...RAID 5/6 performance may be higher after completion.
• If the condition persists, then replace the enclosure components. For more information, see the HP BladeSystem c-Class Enclosure Troubleshooting Guide on the HP website (http://www.hp.com/support/BladeSystem_Enclosure_TSG_en). 1735-Slot X Drive Array - Unsupported Redundant Cabling Configuration Detected... ...Multiple paths to the same enclosure/drives are not supported by this Smart Array firmware version.
* * * * I/O modules are not cabled for good fault tolerance Redundant I/O paths exist due to direct loopback of controller ports Redundant I/O module supported and unsupported storage boxes are cabled together. 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.
Audible Beeps: None Possible Cause: A drive erase operation was previously initiated by the user and is in progress or is scheduled for all drives in the list. Action: None required 1745-Slot X Drive Array - Drive Erase Operation Completed... ...
• The drives were moved to a controller that does not have a cache module attached. Action: Attach a cache module to this controller, or move the drives back to the original controller. If Capacity Expansion operations are pending, be sure that the original cache module is attached. If all logical drives have been disabled, upgrade the controller or move the drives back to the original controller to avoid data loss. Then, run ACU to discard the current array and create a new configuration.
1748-Slot X Drive Array - Unsupported Cache Module Battery Attached... ...Please install Battery Pack(s) with the correct part number. Audible Beeps: None Possible Cause: The current battery pack is not supported on this cache module. Action: Install only supported battery packs with the correct part number. 1748-Slot X Drive Array - Unsupported Array Accelerator Battery Attached... ...Please install battery pack(s) with the correct part number.
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. 1762-Slot X Drive Array - Controller Firmware Upgrade Needed ...
1764-Slot X Drive Array - Capacity Expansion Process is Temporarily Disabled... (followed by one of the following:) ...Expansion will resume when Array Accelerator has been reattached. * Expansion will resume when Array Accelerator has been replaced. * Expansion will resume when Array Accelerator RAM allocation is successful. * Expansion will resume when Array Accelerator battery/capacitor reaches full charge. * Expansion will resume when Automatic Data Recovery has been Completed.
* Expansion Progress Data Could Not Be Read From Array Accelerator. * Expansion Aborted due to Unrecoverable Drive Errors. * Expansion Aborted due to Array Accelerator Errors. Select "F1" to continue with logical drives disabled Select "F2" to accept data loss and to re-enable logical drives Audible Beeps: None Possible Cause: Data was lost while the array was expanded; therefore, the drives have been temporarily disabled.
1775-Slot X Drive Array - Storage Enclosure Cabling Problem Detected: SAS Port Y: OUT port of this box is attached to OUT port of previous box... ...Turn system and storage box power OFF and check cables. Drives in this box and connections beyond it will not be available until the cables are attached correctly. Audible Beeps: None Action: For cabling configuration information, see the storage enclosure documentation.
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. Audible Beeps: None Possible Cause: More drives failed (or were replaced) than the fault-tolerance level allows. The array cannot be rebuilt. If drives have not been replaced, this message indicates an intermittent drive failure.
* [PDPI not found] * [PDPI disabled; check System ROM version] * [Board ID not programmed] Audible Beeps: None Possible Cause: The controller failed. Action: 1. Reseat the array accelerator module. 2. Reseat the controller in the PCI slot. 3. Update the controller to the latest firmware version. 4. If the problem persists, replace the controller. 1784-Slot X Drive Array - Logical Drive Failure Audible Beeps: None Possible Cause: Defective drive or cables detected. Action: 1.
* Configuration information indicates drives were configured on a controller with a newer firmware version. To avoid data loss, reattach drives to original controller or upgrade controller firmware. Audible Beeps: None Possible Cause: Drive array configuration not detected. Action: • Run ACU. • Power down the system and swap the SAS port connectors to prevent data loss. • Run ADU if previous positions are unknown. Then, power down the system and move the drives to their original positions.
Audible Beeps: None Possible Cause: Hard drive X failed or cable is loose or defective. Following a system restart, this message notes that drive X is defective and fault tolerance is being used. Action: 1. Be sure all cables are connected properly and securely. 2. Test and replace defective cables. 3. Replace drive X. (depending on the fault-tolerance level, all data may be lost if another drive fails). 1788-Slot X Drive Array Reports Incorrect Drive Replacement... ...
5. Power up the server to see if the problem still exists. 6. If configured for fault-tolerant operation and the RAID level can sustain failure of all indicated drives: a. Press the F2 key to fail the drives that are not responding b. Replace the failed drives. 7. Press the F1 key to start the system with all logical drives on the controller disabled. Be sure the system is always powered up and down correctly.
* Array Accelerator Battery Disconnected * Array Accelerator Data Backup Failed * Array Accelerator Backup Data Restore Failed Audible Beeps: None Possible Cause: Power was interrupted while data was in the array accelerator memory, or the array accelerator batteries failed. Data in array accelerator has been lost. Action: 1. Verify the integrity of the data stored on the drive. Power was not restored within enough time to save the data. 2.
Audible Beeps: None 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 ACU to clear the data in the write-back cache. 1795-Slot X Drive Array - Array Accelerator Configuration Error... ...Data does not correspond to this drive array. Array Accelerator is temporarily disabled.
1797-Slot X Drive Array - Write-Back Cache Restore Previously Failed... ...Caching is disabled. Audible beeps: None Possible causes: • An issue occurred with reading from the Write-Back Cache. • A failure occurred with writing to the DDR memory. • A failure occurred with reading or writing to the meta data stored in the Write-Back Cache. Action: Replace the DIMM. 1797-Slot X Drive Array - Write-Back Cache Read Error Occurred... ...Data in Cache has been lost. Caching is disabled.
1798-Slot X Drive Array - Cache Module Self-Test Error Occurred... ...Caching is disabled. Audible Beeps: None Possible Cause: Cache Module failed self-test. Depending on the array controller model, the cache may be disabled or the controller might not be usable until this problem is corrected. Action: Replace the Cache Module. 1798-Slot X Drive Array - Array Accelerator Self-Test Error Occurred... ...Array Accelerator is disabled. Audible Beeps: None Possible Cause: Array accelerator failed self-test.
Audible Beeps: None Possible Cause: The Cache Module Super-Cap is charging. Action: No action is required. 1800-Slot X Drive Array - Array Accelerator Super-Cap is charging... ...The Array Accelerator Cache will be enabled once Super-Cap has been charged. No action is required. Audible Beeps: None Possible Cause: The Array Accelerator Super-Cap is charging. Action: No action is required. 1801-Slot X Drive Array - Please install Cache Module Super-Cap... ...
Audible Beeps: None Possible Cause: The Cache Module has a critical error. Action: Replace the Cache Module. 1805-Slot X Drive Array - Cache Module Super-Cap is not installed... IMPORTANT: Unsupported Configuration: Cache Module functionality is limited. Action: Install the Super-Cap to remove these limitations. Audible Beeps: None Possible Cause: The Cache Module Super-Cap is not installed. Action: Install the Super-Cap. 1806-Slot X Drive Array - Cache Module flash memory is not installed;...
**001 of 010** ---caution--03/19/2002 12:54 PM FAN INSERTED Main System Location: System Board Fan ID: 03 **END OF EVENT** WARNING: To avoid potential problems, ALWAYS read the warnings and cautionary information in the server documentation before removing, replacing, reseating, or modifying system components. IMPORTANT: This guide provides information for multiple servers. Some information may not apply to the server you are troubleshooting.
Blue Screen Trap: Cause [NT]... ...Kernel Panic: Cause [UNIX] Abnormal Program Termination: Cause [NetWare] Event Type: System lockup Action: Refer to the operating system documentation. Corrected Memory Error Threshold Passed (Slot X, Memory Module Y)... ...
CAUTION: 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. Replace the processor. Real-Time Clock Battery Failing Event Type: System configuration battery low Action: Replace the system configuration battery.
System Power Supply Failure (Power Supply X) Event Type: Power supply failure Action: Replace the power supply. Unrecoverable Host Bus Data Parity Error... ...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 393) before proceeding.
switches 7 and 8 on the System Maintenance Switch determine which code is shown on the status LEDs. Check the platform system specification if these switches do not work. Both switches set to OFF results in the major code being displayed, while switch 8 set to ON and switch 7 set to OFF results in the minor code being displayed. If you use this method, you must record the major and minor codes, because both codes are needed to identify the last successful area of POST.
Message ID: 4140 Severity: Warning Description: The system is operating with a heterogeneous processor environment. Action: None Message ID: 4141 Severity: Warning Description: Only X out of the X installed processors have been started by the operating system. The system will continue to operate. Action: Confirm that the license agreement in use supports all of the installed processors.
HP ProLiant Gen8 Intel server blade health status LED bar error codes Health status LED bar errors The health status LED bar is on the front panel of each HP ProLiant Gen8 server blade. For more information, see the server blade user guide on the HP website (http://www.hp.com/go/bladesystem/documentation). On HP ProLiant Gen8 Intel server blades, the health status LED bar flashes red in a repeating pattern when certain errors occur.
HP Smart Array errors Controller board runtime LEDs Immediately after you power up the server, the controller runtime LEDs illuminate briefly in a predetermined pattern as part of the POST sequence. At all other times during server operation, the illumination pattern of the runtime LEDs indicates the status of the controller. To determine the controller status, see the appropriate controller-specific section.
P420 LEDs Item Color Name Interpretation 1 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. 2 Red Fault When an error occurs, this LED is on. During power up, this LED is solid for up to 2 seconds. 3 Green Heartbeat When the controller is in good health, this LED flashes at 1 Hz. During power up, this LED is solid for up to 2 seconds.
Item Color Name Interpretation 2 Red Fault When an error occurs, this LED is on. During power up, this LED is solid for up to 2 seconds. 3 Amber Debug On = Controller is in reset. Off = Controller is in an idle or runtime state. Flashing 5 Hz = Controller and cache are performing a backup. During power up, this LED is solid for up to 2 seconds. FBWC module LEDs (P222, P420, P421) The FBWC module has three single-color LEDs (one amber and two green).
1 - Amber 2 - Green 3 - Green Interpretation Flashing 2 Hz Flashing 2 Hz On The capacitor has been charging for 10 minutes, but has not reached sufficient charge to perform a full backup. On On Off The current backup is complete, but power fluctuations occurred during the backup. On On On The cache module microcontroller has failed. FBWC module LEDs (P410, P411, P711m, P812) The FBWC module has two single-color LEDs (green and amber).
Message Id: 24579 Severity: Informational Log message: An event queue overflow has occurred for the array controller . At least one event has been lost. This controller will only queue up to 100 events. 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.
Log message: The physical drive located in bay is offline but operational. This drive can be found in box which is connected to port of the array controller . The offline reason received from the HP Smart Array firmware is: . values: • TOO_SMALL_IN_LOAD_CONFIG - Replacement drive is too small for configured volume(s).
• 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. • READ_CAPACITY_FAILED - “Read Capacity” command failed after multiple retries. • INVALID_BLOCK_SIZE - Drive indicates it is not formatted for 512 bytes per sector. • HOT_PLUG_REQUEST_SENSE_FAILED - “Request Sense” command failed after drive hot-added.
• 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. • PHY_RESET_FAILED - Phy reset request failed. • FR_CHKBLK_FAILED_WRITE - Drive failed write command while checking for media errors.
Message Id: 24590 Severity: Informational Log message: Sensor number has reported that a previously existing temperature condition has been corrected. This sensor is located in box which is connected to port of array controller . All of the temperature sensors in the attached box are now reporting acceptable temperature levels.
• ERROR_ERASING_RIS - Could not write to reserved configuration sectors after multiple retries. • ERROR_SAVING_RIS - Could not write to reserved configuration sectors after multiple retries. • FAIL_DRIVE_COMMAND - “Fail Drive” command received from host. • MARK_BAD_FAILED - Unable to create media defect after multiple retries. • MARK_BAD_FAILED_IN_FINISH_REMAP - Unable to create media defect after multiple retries. • TIMEOUT - Too many SCSI command timeouts.
• INVALID_BLOCK_SIZE - Drive indicates it is not formatted for 512 bytes per sector. • HOT_PLUG_REQUEST_SENSE_FAILED - “Request Sense” command failed after drive hot-added. • HOT_PLUG_START_UNIT_FAILED - “Start Unit” command failed after drive hot-added) • WRITE_ERROR_AFTER_REMAP - After reassigning a media error reported during a write command, the write command failed with another media error.
• FR_CHKBLK_FAILED_WRITE - Drive failed write command while checking for media errors. • FR_ATI_TEST_FAILED_WRITE - Drive failed write command while checking for errors. • OFFLINE_ERASE - Drive is offline due to a Secure Erase operation. • OFFLINE_TOO_SMALL - Drive is offline because it’s a replacement drive that is too small. • OFFLINE_DRIVE_TYPE_MIX - Drive is offline because it is not the correct type for this array [SATA vs SAS].
• “INTERIM RECOVERY MODE” • “READY FOR RECOVERY” • “RECOVERING” • “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” • “ERASING” • “UNKNOWN” Message Id: 24599 Severity: Warning Log message: Logical drive of array controller has encount
• “EJECTED” • “ERASING” • “UNKNOWN” Message identifiers 24600-24624 Message Id: 24600 Severity: Error Log message: Logical drive of array controller has encountered a status change from: Status: to Status: and values: • “OK” • “FAILED” • “NOT CONFIGURED” • “INTERIM RECOVERY MODE” • “READY FOR RECOVERY” • “RECOVERING” • “WRONG PHYSICAL DRIVE REPLACED” • “PHYS
Message Id: 24602 Severity: Warning Log message: The recovery of logical drive configured on array controller was aborted while rebuilding due to an unrecoverable read error. Physical drive number was the replacement drive being rebuilt before the read error occurred, while physical drive number is the error drive which reported the read error.
Array controller is also reporting that the last physical drive to report a fatal error condition (associated with this logical request), is located on bus and ID . Message Id: 24607 Severity: Warning Log message: The event information received from array controller was of an unknown or unrecognized class. An excerpt of the controller message is as follows: .
Severity: Informational Log message: Array controller has reported that the external array controller attached to port has been disconnected or powered down. Message Id: 24615 Severity: Informational Log message: Array controller has reported that an external array controller was attached to port or was previously attached and was powered on.
• “The Smart Array firmware is reporting that the redundant I/O modules of this box have multiple paths to the controller” Message Id: 24618 Severity: Warning Log message: Array controller is reporting that an unsupported configuration has occurred with the redundant cabling that is attached to port . Please check the cabling and ensure that a supported configuration is being used.
Message identifiers 24625-24649 Message Id: 24625 Severity: Informational Log message: Fan number is reporting that it is now operational. This fan is located in box number which is connected to port of array controller . Message Id: 24626 Severity: Informational Log message: Fan number located on fan module is reporting that it is now operational.
Log message: Array controller has reported that its cache has been disabled. Message Id: 24633 Severity: Informational Log message: Array controller has reported that its cache has been enabled. Message Id: 24634 Severity: Informational Log message: Array controller has reported that its cache batteries are missing.
Severity: Warning Log message: The Smart Array controller is reporting that no redundant array controller is installed. Message Id: 24642 Severity: Error Log message: The Smart Array controller is not redundant because it is a different model than its' partner controller.
Message identifiers 24650-24674 Message Id: 24650 Severity: Informational Log message: SnapShot ID of logical drive on array controller has been created.
values: • • “the external controller attached to” "" Message Id: 24655 Severity: Error Log message: Restore operation of SnapShot ID of logical drive on array controller failed due to possible data corruption.
Message Id: 24660 Severity: Informational Log message: Smart Array controller has reported that its' partner controller has been the SAS fabric. Message Id: 24661 Severity: Informational Log message: Surface analysis parity/consistency initialization forced complete for logical drive on Smart Array controller .
Severity: Informational Log message: Snapshot resource volume of logical drive on array controller has been deleted. values: • • “the external controller attached to” "" Message Id: 24672 Severity: Error Log message: Snapshot resource volume of logical drive on array controller has reached its limit.
be found in bay of box connected to port of array controller . values: • • “The party data does not match the data drives.“ “” Message Id: 24676 Severity: Informational Log message: Surface analysis has repaired an inconsistent stripe on logical drive .
Severity: Informational Log message: An error log update has occurred for the physical drive with BMIC device index of array controller . Message Id: 24683 Severity: Warning Log message: Array controller has reported an uncorrectable read error during rebuild operations for logical drive .
Severity: Warning Log message: A SAS link PHY error has been detected. The PHY error threshold has been exceeded for PHY number located on expander number . This expander can be found in box which is attached to port of array controller .
Log message: A SAS link error has been detected between I/O module of box and I/O module of box . These boxes are connected to port of array controller . Please check this data path and the associated hardware.
The external Smart Array controller is attached to the host side Smart Array controller . Message Id: 24703 Severity: Informational Log message: The external Smart Array controller located in the MSA chassis labeled as has reported that fan number is now operational. The external Smart Array controller is attached to the host side Smart Array controller .
Log message: The external Smart Array controller located in the MSA chassis labeled as has reported that redundant 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: 1. The previously failed power supply has returned to an operational state. 2. The previously failed power supply was removed from the chassis.
• SPIN_UP_FAILURE_IN_RECOVER - “Start Unit” command failed during error recovery • REBUILD_WRITE_ERROR - Drive failed write command after multiple retries during rebuild. • TOO_SMALL_IN_HOT_PLUG - Replacement drive is too small for configured volume(s). • BUS_RESET_RECOVERY_ABORTED - Unable to communicate with drive after multiple bus resets and retries; may be due to this drive or another drive that is corrupting the parallel SCSI bus. • REMOVED_IN_HOT_PLUG - Drive has been hot-removed.
• DRIVE_TYPE_MIX_IN_LOAD_CFG - attempt to use a SATA drive as a replacement in a SAS-only volume, or vice versa. • PROTOCOL_ADAPTER_FAILED - Protocol layer reports that the protocol hardware has failed; may be a controller failure. • FAULTY_ID_BAY_EMPTY - Drive responds to SCSI ID, but the corresponding bay is empty. • FAULTY_ID_BAY_OCCUPIED - Bay is occupied by a drive that does not respond to the corresponding SCSI ID.
• “FAILED” • “NOT CONFIGURED” • “INTERIM RECOVERY MODE” • “READY FOR RECOVERY” • “RECOVERING” • “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” • “ERASING” • “UNKNOWN” Message Id: 24711 Severity: Warning Log message: The external Smart Array controller located in the MSA chassis labeled
• “HARDWARE HAS OVERHEATED” • “EXPANDING” • “NOT YET AVAILABLE” • “QUEUED FOR EXPANSION” • “DISABLED DUE TO SCSI ID CONFLICT” • “EJECTED” • “ERASING” • “UNKNOWN” Message Id: 24712 Severity: Error Log message: The external Smart Array controller located in the MSA chassis labeled as has reported that logical drive has encountered a status change from: Status: to Status: The external Smart Array controller is attached to
Message Id: 24713 Severity: Informational Log message: The external Smart Array controller located in the MSA chassis labeled as has reported that logical drive is in a failed state but has had one or more drive replacements and is now ready to change to a status of "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 power cycling the MSA chassis.
of the MSA chassis. The physical drive that reported the write error is located in bay of the MSA chassis. The external Smart Array controller is attached to the host side Smart Array controller .
Severity: Warning Log message: The external Smart Array controller located in the MSA chassis labeled as has reported that its cache batteries have failed. The external Smart Array controller is attached to the host side Smart Array controller .
Severity: Informational Log message: The external Smart Array controller located in the MSA chassis labeled as has reported that a firmware update is needed for the physical drive with product ID . The recommended minimum firmware revision should be . The external Smart Array controller is attached to the host side Smart Array controller .
Log message: The external Smart Array controller located in the MSA chassis labeled as is reporting that no redundant array controller is installed. The external Smart Array controller reporting this event is attached to the host side Smart Array controller . Message Id: 24735 Severity: Error Log message: The external Smart Array controllers located in the MSA chassis labeled as are not redundant because they are different models.
The external Smart Array controller reporting this event is attached to the host side Smart Array controller . Message Id: 24741 Severity: Error Log message: The external Smart Array controllers located in the MSA chassis labeled as are no longer redundant because one or more drives has been determined not to be able to support redundant controller operations.
Log message: The external Smart Array controller located in the MSA chassis labeled as has reported that a SAS link error has been detected between its' onboard expander and an externally connected storage box. This error has been detected between port of the external controller and I/O module number located in box number . Please check this data path and the associated hardware.
Severity: Warning Log message: The external Smart Array controller located in the MSA chassis labeled as has reported that a SAS link error has been detected between a switch expander and I/O module of box . This hardware is connected to port of the external array controller. Please check this data path and the associated hardware.
Log message: The external Smart Array controller located in the MSA chassis labeled as has reported that box connected to port is now marked as repaired (re-added after a previous failure). The external Smart Array controller reporting this event is attached to the host side Smart Array controller .
The external Smart Array controller reporting this event is attached to the host side Smart Array controller . Message Id: 24762 Severity: Informational Log message: External Smart Array controller number located in the MSA chassis labeled as is reporting the following flash operation: ".
Log message: The MSA chassis labeled as has reported that battery pack number located on controller number has been . The external Smart Array controller reporting this operation is attached to the host side Smart Array controller .
Severity: Informational Log message: The external Smart Array controller located in the MSA chassis labeled as has reported that fan number located on fan module is reporting a degraded condition. The external Smart Array controller is attached to the host side Smart Array controller .
• ERROR_SAVING_RIS - Could not write to reserved configuration sectors after multiple retries. • FAIL_DRIVE_COMMAND - “Fail Drive” command received from host. • MARK_BAD_FAILED - Unable to create media defect after multiple retries. • MARK_BAD_FAILED_IN_FINISH_REMAP - Unable to create media defect after multiple retries. • TIMEOUT - Too many SCSI command timeouts. • AUTOSENSE_FAILED - Drive is failing commands but is not returning SCSI sense data after multiple retries.
• HOT_PLUG_REQUEST_SENSE_FAILED - “Request Sense” command failed after drive hot-added. • HOT_PLUG_START_UNIT_FAILED - “Start Unit” command failed after drive hot-added) • WRITE_ERROR_AFTER_REMAP - After reassigning a media error reported during a write command, the write command failed with another media error.
• FR_ATI_TEST_FAILED_WRITE - Drive failed write command while checking for errors. • OFFLINE_ERASE - Drive is offline due to a Secure Erase operation. • OFFLINE_TOO_SMALL - Drive is offline because it’s a replacement drive that is too small. • 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.
The external Smart Array controller is attached to the host side Smart Array controller . Message Id: 24780 Severity: Warning Log message: The external Smart Array controller located in the MSA chassis labeled as is reporting inconsistent data that was previously consistent.The inconsistent data may be caused by a power loss during write activity or by a drive returning corrupt data.
The external Smart Array controller is attached to the host side Smart Array controller . Message Id=24785 Severity: Informational Log message: The external Smart Array controller located in the MSA chassis labeled as has reported that a previously failed storage enclosure processor (SEP) is now responding and operational. The external Smart Array controller is attached to the host side Smart Array controller .
is approaching the maximum usage limit for writes (wear out). The drive should be replaced as soon as possible. The external Smart Array controller is attached to the host side Smart Array controller . Message Id=24791 Severity: Error Log message: Array controller has reported that its internal temperature has exceeded the preset limit of °C.
Log message: The external Smart Array controller located in the MSA chassis labeled as is indicating that a previously existing temperature condition on the controller from sensor has been corrected. All of the temperature sensors are now reporting acceptable temperature levels. The external Smart Array controller is attached to the host side Smart Array controller .
Message Id 24802 Severity: Informational Log message: The external Smart Array controller located in the MSA chassis labeled as is reporting that its cache is missing. This is an unsupported configuration. The external Smart Array controller is attached to the host side Smart Array controller .
Smart Array Windows driver errors Message Id: 5001 Severity: Error Log message: The controller in slot %3 (bus %4, device %5, function %6) heartbeat has not changed in %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 Log message: The controller (bus %2, device %3, function %4) has failed. driver configuration buffer.
HP Onboard Administrator errors Onboard Administrator error messages • Soap Response Errors—These are the general errors reported by the gSoap service for validation errors, device failures, and so on. These errors are organized into two categories: o User Request errors o Onboard Administrator errors • Soap interface errors—These errors signal internal issues with the gSoap service. • CGI application errors—These errors are reported by individual CGI processes.
24 The submitted value contains an invalid character. 25 The submitted value is too short. 26 The submitted value is too long. 27 The submitted trap receiver already exists. 28 The maximum number of trap receivers already exists. 29 The maximum number of IP managers already exists. 30 The IP Manager already exists. 31 The submitted bay number is out of range. 32 The submitted IP address is not valid. 33 The submitted value is null. 34 An error occurred while generating an event.
59 Getting the enclosure information failed. 60 Getting the enclosure names failed. 61 Getting the enclosure status failed. 62 Setting the enclosure name failed. 63 Setting the enclosure asset tag failed. 64 Setting the enclosure time zone failed. 65 Setting the enclosure UID failed. 66 Setting the UID for the submitted interconnect failed. 67 Resetting the submitted interconnect failed. 68 Getting interconnect information for the submitted interconnect failed.
95 Invalid domain. 97 Connecting to the blade's iLO failed. 98 Sending the RIBCL command to the requested blade failed. 99 Could not find the requested element in the RIBCL response. 100 Could not find the requested attribute in the RIBCL response. 101 Could not find the starting boundary in the RIBCL response. 102 Could not find the ending boundary in the RIBCL response. 103 Could not determine the IP address of the management processor for the requested blade. 104 Could not locate a Primary NTP server.
142 The maximum number of LDAP certificates already exist. 143 Could not remove LDAP certificate. 144 You must configure the directory server and at least one search context before enabling LDAP. 145 Could not set the LDAP group description. 146 An error occurred while communicating with the other Onboard Administrator. 147 Unable to perform the operation. Retry the operation or restart OA. (System Error 147) 148 The other Onboard Administrator is not present. 149 No redundant Onboard Administrator found.
179 The certificate cannot be removed because it does not exist. 180 The interconnect tray is not present. 181 The blade is not present. 182 Users cannot remove or disable themselves.
222 The Active and Standby Onboard Administrator are not the same hardware build. 223 The firmware installed on an Onboard Administrator module is incompatible with FirmwareSync. 224 Failed to create firmware image 225 The Active and Standby Onboard Administrator have the same firmware version installed. 226 Upgrade an Onboard Administrator to firmware 2.10 or later to enable this feature. 227 The requested user cannot be removed from iLO because it is the only remaining administrator account.
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. 258 This operation is not permitted when two-factor authentication is enabled. 260 This operation cannot be performed when AlertMail is disabled. 261 This operation cannot be performed when the AlertMail settings are not configured.
290 Request to enable DHCP addressing on the active Onboard Administrator is denied because Enclosure IP Mode is enabled. 291 The value provided is not proper base64. 292 The firmware image provided is an older version than the current firmware. Onboard Administrator settings cannot be preserved. 293 The file provided is not a valid Onboard Administrator firmware image. 294 There are no USB keys connected to the enclosure.
323 Invalid SMTP server 324 Invalid SNMP Trap receiver 325 Invalid NTP server 326 Invalid EBIPA configuration. Multiple subnets were detected. 327 Specified VLAN ID does not exist. 328 Cannot delete the default VLAN ID 329 Maximum VLAN entries reached 330 Duplicated VLAN ID 331 Specified VLAN ID is invalid. 332 Operation partially successful 333 Duplicated VLAN name 334 A pending command already exists. 337 The remote syslog server address cannot be cleared while remote logging is enabled.
364 SolutionsId must be an 8-byte hex string, between 0000000000000000 and FFFFFFFFFFFFFFFF. 365 Failed Remote Support registration 366 Failed Remote Support un-registration 367 Failed Remote Support restore registration 368 Failed to send Remote Support message (Hint: Check the Remote Support proxy and endpoint URL. Use SET REMOTE_SUPPORT PROXY to configure and re-try.) 369 Failed to set Remote Support interval.
403 The operation cannot be performed while Enclosure Firmware Management is running. 404 Unable to mount ISO or validate version information. Check URL and validate ISO is available from URL entered. 405 Unable to open firmware log. 406 The blade's firmware has not been discovered. 407 An error occurred while reading the firmware log. 408 Enclosure Firmware Management is not supported by this device type 409 Firmware ISO image is in use, changing url is not allowed.
446 Unregistration request was not processed successfully by the HP Remote Support receiver. Remote Support has been disabled locally. No service events or data collections will be sent until this device has been re-registered. 447 Authentication error. Please unregister and re-register device. 448 Missing device identifiers. Please unregister and re-register device. 449 Corrupt device identifiers. Please unregister and re-register device. 450 Insufficient device identifier information.
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. 476 Invalid SNMP Engine ID. The Engine ID must start with '0x' followed by an even number of up to 64 hexadecimal digits. 477 Invalid Authentication Protocol.
516 HP Passport system failure occurred. A problem has been detected in the HP Passport system. Please retry later. 517 The session token is invalid due to any of the following reasons: failed decoding, token is null or empty, userId is empty or session start value is not a number. Please retry registration. 518 Password is required. Please retry registration. 519 HP Passport user ID is invalid. Please retry registration with a valid user ID.
Insight Display screen shot errors 1 Missing credentials. 2 The getLCDImage CGI process has caught the SIGSEGV signal. 3 Could not acquire access to the image in a reasonable amount of time. 4 Cannot open semaphores. 5 Produce SEMV does not work. 6 Consume SEMV does not work. 7 Cannot lock the image file. 8 Cannot open the image file. 9 Cannot seek in the image file. 10 Unable to resume session. 11 Insufficient privileges.
Alertmail: Failed to read rack topology information Alertmail: Failed to read status of fan [value] Alertmail: Failed to read status of Interconnect [value] Alertmail: Failed to read status of powersupply [value] Alertmail: Failed to read topology after event 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] sulog
CLI log messages Log type: LOG_WARNING, Failure type: Info OA: [value] logged out of the Onboard Administrator Log type: LOG_INFO, Failure type: Info OA: ProLiant iLO firmware update attempted by user [value] Interconnect bay log messages Log type: LOG_WARNING, Failure type: Info OA: [value] was connected to interconnect bay #[value] OA: [value] was disconnected from interconnect bay #[value] DHCP log messages Log type: LOG_WARNING, Failure type: SW OA: dhcpStart: retrying MAC address request (returned [v
OA: dhcpStart: ioctl SIOCGIFHWADDR: [value] OA: dhcpStart: ioctl SIOCSIFFLAGS: [value] OA: dhcpStart: setsockopt: [value] OA: dhcpStart: socket: [value] OA: dhcpStop: ioctl SIOCSIFFLAGS: [value] OA: error executing [value] [value] [value]: [value] 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] DHCP Monitor: Could not start DHCPD for IPv4.
Enclosure-Link: Failed to enable lower chain Enclosure-Link: Failed to enable upper chain Enclosure-Link: Failed to generate EVENT for initial topology detection Enclosure-Link: Failed to generate EVENT for topology change Enclosure-Link: Failed to get local address.
Non-volatile configuration log messages Log type: LOG_WARNING, Failure type: SW CLI: Error accessing User Configuration Files Log type: LOG_ERR, Failure type: SW envtools: Block [value] failed encoding envtools: Error in default gateway envtools: Error in DNS1 address envtools: Error in DNS2 address envtools: Error in ipaddress envtools: Error in ipAllow1 address envtools: Error in ipAllow2 address envtools: Error in ipAllow3 address envtools: Error in ipAllow4 address envtools: Error in ipAllow5 address en
envtools: NVRAM downgraded to version [value] envtools: Updating NVRAM version to 19. envtools: Updating NVRAM version to 20. envtools: Updating NVRAM version to 21. envtools: Updating NVRAM version to 22. envtools: Updating NVRAM version to 23. envtools: 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.
OA_Flash: The firmware image provided is older than the current firmware and OA settings cannot be preserved. The force downgrade option must be used. Please re-try with the force option to flash and go back to factory defaults. Log type: LOG_NOTICE, Failure type: Info FWSync: New firmware image flashed.
CONFIG: [value] has wrong permissions. Please reset to factory defaults CONFIG: Failed to compute MD5 CONFIG: Failed to open flash CONFIG: Failed to open input file CONFIG: Fail to open the file to be flashed CONFIG: Failed to open output file CONFIG: Failed to read data from flash CONFIG: Failed to read system files CONFIG: Failed to update system with new data CONFIG: Failed to write data to flash CONFIG: Tar file [value] is too big for flash [value] CONFIG: Wrong file permissions detected.
netreg: DDNS: Server failure netreg: DDNS: Unable to create socket netreg: DDNS: Update refused by DNS server netreg: Error starting DDNS thread netreg: Error starting NetBIOS thread netreg: NETBIOS: Refreshed WINS registration Log type: LOG_NOTICE, Failure type: Info netreg: DDNS: Registered with Dynamic DNS netreg: DDNS: Update successful 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: KVM Bay [value:bladeNumber] - Could not connect. Error([value]). OA: KVM Bay [value:bladeNumber] - Could not connect. If error persists reboot the OA. OA: KVM Bay [value:bladeNumber] - Could not create thread. OA: KVM Bay [value:bladeNumber] - Disconnected from blade. Bad getmore OA: KVM Bay [value:bladeNumber] - Disconnected from blade. Bad next state detected. OA: KVM Bay [value:bladeNumber] - Disconnected from blade. Bad state transition detected.
Operational log messages Log type: LOG_EMERG, Failure type: SW OA: Internal System Firmware Error. Rebooting.
OA: CA certificate (issuer = [value:issuer-CN]) installed by user [value:username]. OA: CA certificate (issuer = [value:issuer-CN]) removed by user [value:username]. OA: Certificate for user [value:username] installed by user [value:username]. OA: Certificate for user [value:username] removed by user [value:username]. All web sessions (if any) were ended. OA: Certificate owner field set to ([SAN/SUBJECT]) on Onboard Administrator by user [value:username].
OA: [value:protocol] was [enabled/disabled] by user [value:username] OA: Alertmail domain changed to [value:mailDomain] by user [value:username] OA: Alertmail recipient changed to [value] by user [value:username] OA: Alertmail server changed to [value:mailServer] by user [value:username] OA: Default VLAN ID for enclosure changed to [value] OA: DHCPv6 was [enabled/disabled] by user [value:username].
OA: EBIPA Server netmask for bay [value:bladeNumber] set to [value] by user [value:username] OA: EBIPA Server NTP [value:bladeNumber] [value] [value] by user [value:username] OA: EBIPA Server second DNS IP for bay [value:bladeNumber] set to [value] by user [value:username] OA: EBIPA Server third DNS IP for bay [value:bladeNumber] set to [value] by user [value:username] OA: EBIPA was [disabled/enabled] for device bay #[value:bladeNumber] by user [value:username] OA: EBIPA was [disabled/enabled] for interconn
OA: Firmware management policy set to manual OA: Firmware management scheduled update disabled OA: Firmware management scheduled update time set to [value:date] [value:time] OA: Firmware management server bays to include have been changed OA: Firmware management was [enabled/disabled] by user [value:username]. OA: Could not factory reset firmware management log: [value:error] (Code: [value:number]) OA: Group [value:groupname] was added. OA: Group [value:groupname] was deleted.
OA: Network Interface link forced to [value:speed]Mbps - Half Duplex by user [value:username]. OA: Network Interface link set to Auto negotiation by user [value:username]. OA: New SSH key installed by user [value:username] OA: Nothing needs to be reverted as VLAN setting has not changed OA: Polling Interval of NTP set to [value] seconds by user [value:username]. OA: PowerDelay has been initiated for the selected devices. OA: PowerDelay has completed for the selected devices.
OA: Undoing VLAN IPCONFIG changes. IP mode is set to STATIC for OA #[value:number] OA: USB enable changed to [value]. Rebooting... OA: User [value:username] privilege level was changed from [value:Administrator/Operator/User/Anonymous] to [value:Administrator/Operator/User/Anonymous] by user [value:username]. All web and CLI sessions (if any) were ended. OA: User [value:username] was added by user [value:username]. OA: User [value:username] was assigned to group [value:groupname].
OA: Momentary Press virtual command enacted on blade [value:bladeNumber] by user [value:username]. OA: Onboard Administrator in bay [value:bayNumber] was restarted by user [value:username]. OA: Power limit was set to [value] by user [value:username] OA: Power savings mode was set to [ON/OFF] by user [value:username] OA: Power subsystem redundancy mode was set to [value] by user [value:username] OA: Press and Hold virtual command enacted on blade [value:bladeNumber] by user [value:username].
OA Tray firmware upgrade failed. OA: Blade in bay [value:bladeNumber] contains an unsupported #[value] mezz card. OA: Enclosure Status changed from [N/A/Unknown/OK/Degraded/Failed] to [N/A/Unknown/OK/Degraded/Failed]. OA: Failed to initialize key components. Please call support immediately. OA: Fan [value] firmware upgrade failed. OA: Interconnect [value:slotNumber] firmware upgrade failed. OA: Interconnect [value] firmware upgrade failed. OA: LCD fails to respond to keystrokes.
OA: Blade [value:bladeNumber] Ambient Temperature Cable fault...state is DEGRADED. OA: Blade [value:bladeNumber] Ambient Temperature caution...state is CRITICAL. OA: Blade [value:bladeNumber] Ambient Temperature caution...state is DEGRADED. OA: Blade [value:bladeNumber] Ambient Temperature Sensor fault...state is CRITICAL. OA: Blade [value:bladeNumber] Ambient Temperature Sensor fault...state is DEGRADED. OA: Blade [value:bladeNumber] cannot partner with its neighbor.
OA: Blade [value:bladeNumber] Storage Condition fault...state is CRITICAL. OA: Blade [value:bladeNumber] Storage Condition fault...state is DEGRADED. OA: Blade [value:bladeNumber] thermal state is CRITICAL. OA: Blade [value:bladeNumber] thermal state is DEGRADED.
OA: PS Subsystem N + N Redundancy - FAILED. OA: PS Subsystem Overload - FAILED. OA: PS Subsystem Overload – REPAIRED. OA: PS Subsystem Power Limit - FAILED. OA: PS Subsystem Power Limit – REPAIRED. OA: Redundant Onboard Administrator was removed OA: Required fan is missing from fan bay [value] OA: The fan in bay #[value:fanNumber] is not supported in this enclosure. Please replace this fan with the proper part number.
OA: Server Power Reduction - Deactivated OA: Tray Update: Can't get TRAY PS microcode version OA: Warning: integrated device on bus 0x[value] at address 0x[value] has not responded Log type: LOG_NOTICE, Failure type: Info OA: AC Subsystem Overloaded - REPAIRED OA: Blade [value:bladeNumber] Ambient Temperature Cable state is OK. OA: Blade [value:bladeNumber] Ambient Temperature Sensor state is OK. OA: Blade [value:bladeNumber] Ambient Temperature state is OK.
OA: Internal health status of interconnect in bay [value:slotNumber] changed to OK OA: IO module in slot [value:slotNumber] temperature is normal OA: Management Process on Blade [value:bladeNumber] appears responsive again. OA: Midplane replacement detected. Serial number changed from [value] to [value].
OA: VC module in interconnect bay [value:slotNumber] has firmware revision [value:version] but minimum firmware revision [value:version] is required Log type: LOG_INFO, Failure type: Info OA Tray firmware upgrade initiated. OA Tray firmware upgrade succeeded. OA: Blade [value:bladeNumber] management processor firmware upgrade initiated. OA: Blade [value:bladeNumber] management processor firmware upgrade succeeded. OA: Fan [value] firmware upgrade initiated. OA: Fan [value] firmware upgrade succeeded.
OA: File [value] could not set permissions [value] OA: File [value] could not set user [value] group [value] OA: File [value] failed to open. OA: File [value] failed to read. OA: File [value] failed to write OA: File [value] failed to write into archive. OA: flar [x|c]); OA: Flash Archiver could not obtain root privileges (errno [value]) OA: Invalid file descriptor [value]. OA: malloc failure ([value] bytes) OA: Management process failure. OA: NULL object passed.
LDAP: error manipulating password Log type: LOG_ERR, Failure type: SW LDAP: bad username [value:username] LDAP: couldn't obtain coversation function [value] Log type: LOG_NOTICE, Failure type: SW LDAP: authentication failure; [value] for [value] service, not a member of any configured group LDAP: could not recover authentication token Redundancy log messages Log type: LOG_WARNING, Failure type: SW Redundancy: Active Onboard Administrator has lost link connectivity on the external NIC for [value] seconds.
Redundancy: WARNING: The other OA ([Standby/Active]) is running a different firmware. OA Redundancy will be degraded Log type: LOG_NOTICE, Failure type: SW Redundancy: Assuming active Onboard Administrator network settings. Redundancy: Enclosure IP mode was [disabled/enabled] Log type: LOG_INFO, Failure type: SW Redundancy: Enclosure IP mode configurations have been reset.
Two Factor: Error downloading CRL from [value:URL] Two Factor: Error mapping CRL files. Two Factor: Error starting CRL service. Two Factor: Insufficient privileges. Two Factor: Internal error. Two Factor: Invalid/corrupt CRL file at [value:URL] Two Factor: Messaging system error. FIPS log messages Log type: LOG_INFO, Failure type: SW FIPS: Onboard Administrator is operating in FIPS Mode Debug. FIPS: Onboard Administrator is operating in FIPS Mode On.
Trap ID Trap name Description 22001 cpqRackNameChanged Rack Name has changed 22002 cpqRackEnclosureNameChanged Enclosure Name has changed 22003 cpqRackEnclosureRemoved Linked Enclosure removal detected 22004 cpqRackEnclosureInserted Linked Enclosure insertion detected 22008 cpqRackEnclosureFanFailed Enclosure fan has failed 22009 cpqRackEnclosureFanDegraded Enclosure fan is degraded 22010 cpqRackEnclosureFanOk Enclosure fan is OK 22011 cpqRackEnclosureFanRemoved Enclosure fan is re
Event messages include the device affected, the device name, and the date and time of the event. Some examples of event messages are: • The enclosure is in a degraded state. • Blade X has experienced a failure. • The temperature on Blade X has exceeded the failed threshold. • Fan X has experienced a failure. • The power supplies are no longer redundant. • Power supply X is in a degraded state. • The enclosure temperature has exceeded the degraded threshold.
Event Cause LDAP Group Removed A LDAP group was removed from the Onboard Administrator. If you are logged into the Onboard Administrator under this LDAP group, you are disconnected. OA System Log Cleared The Onboard Administrator system log was cleared. OA Name Changed The Onboard Administrator DNS name was changed. OA Inserted A redundant Onboard Administrator was inserted into the enclosure. OA Removed The redundant Onboard Administrator was removed from the enclosure.
HP Virtual Connect errors SNMP overview SNMP is used by network management systems to monitor network-attached devices for conditions that require administrative attention. SNMP consists of a set of standards for network management, including an Application Layer protocol, a database schema, and a set of data objects. The SNMP configuration is controlled by VCM and applies to all modules in the VC domain.
MIB VC-Enet VC-FC RFC 2863 IF-MIB X — RFC 4188 Bridge-MIB X — RFC 3418 SNMP v2 MIB X X Compaq System Info MIB X X Compaq Host MIB X X Compaq Rack MIB — X* RFC 1213 Network Mgmt X — RFC 4293 IP-MIB X — Fibre Alliance MIB (FC Mgmt Integ) — X RFC 2837 Fabric Element MIB — X VC Module MIB (VCM-MIB) X — VC Domain MIB (VCD-MIB) X — IEEE LLDP MIB (LLDP-MIB) X — IEEE LLDPv2 MIB (LLDPv2-MIB) X — IEEE8023 LAG MIB (LAG-MIB) X — VC QOS MIB (VC-QOS-MIB) X — * Not suppor
Trap Category connUnitSensorStatusChange VC-FC Other CRITICAL FA-MIB connUnitPortStatusChange VC-FC Port Status See table below FA-MIB authenticationFailure¹ VC-FC Other CRITICAL SNMPv2-MIB coldStart VC-FC Other CRITICAL SNMPv2-MIB cpqHoSWRunningStatusChange VC-FC Other INFO CPQHOST-MIB authenticationFailure VC-Enet Other CRITICAL SNMPv2-MIB Domain status change (deprecated) — — — vcDomainManagedStateChanged VCM Domain Status StackingLinkRedundant status change VCM Domain St
Trap Category Severity MIB vcModPortProtectionConditionDetected VC-Enet Port Status CRITICAL VCM-MIB vcModPortProtectionConditionCleared VC-Enet Port Status INFO VCM-MIB ¹ 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.
Trap name Trap data Description vcModInputErrorsUp port identification ifInErrors vcModInputErrorsDown port identification ifInErrors The input error count on a port has exceeded its high-water mark for longer than the error averaging period. port is the index of the affected port in ifTable.
Managed status Description disabled Indicates the component is disabled and non-functioning info Indicates a non-service affecting condition exists such as initializing components and system login/logout • The Cause string indicates why an object transitioned to the current managed state from the specific objects perspective. A network failure is an example Cause string. • The RootCause string indicates the root causes for an object transitioning managed states.
Enclosure reason code Description vcEnclosureSomeModulesOrServersInco The enclosure contains incompatible modules, or configured modules are missing. mpatible One or more FC modules are abnormal. vcEnclosureSomeFcModulesAbnormal vcEnclosureSomeServersAbnormal At least one server is in a known state and no servers are OK, or at least one server is degraded. vcEnclosureUnknown The condition of the enclosure cannot be determined, or the state of servers or modules is unknown.
Physical server reason code Description vcPhysicalServerUnknown The condition of the server is unknown. vcFcFabricManagedStatusChanged The following is an example of a FC fabric Cause string: 1 of 2 uplink ports are abnormal on BackupSAN fabric The following is an example of a FC fabric RootCause string: 1 of 2 uplink ports are abnormal on BackupSAN fabric The FC fabric managed status ReasonCodes are provided in the following table.
Profile reason code Description vcProfileServerAbnormal The server the profile is assigned to is abnormal. vcProfileAllConnectionsFailed All connections in the profile have failed. vcProfileSomeConnectionsUnmapped One or more connections in the profile are not mapped to a physical port. vcProfileAllConnectionsAbnormal All connections in profile are abnormal. vcProfileSomeConnectionsAbnormal Some connections in the profile are abnormal.
The events are categorized by severity which reflects the functional state of the component. The severity will guide you on the kind of attention you should give to taking an action in the occurrence of the event. The following is a list of the categories: • SEVERITY_INFO An info event is a low-level condition for out-of-service equipment, system login/logout and other non-service affecting information. The standard event display color is black.
• 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. While this outage does not affect current network traffic, no domain configuration or monitoring can occur.
Enclosure events (2000-2999) 2003 - Enclosure import failed Severity: CRITICAL Description: An import or recovery of an enclosure failed. Imports are triggered by a user request to add an enclosure to the domain. Recoveries may be triggered by a VCM reset, VCM failover, Configuration restore, firmware upgrade, user re-authentication request, or the reconnection of an enclosure that was previously in a NO-COMM state. Possible causes: • The primary OA IP, username, or password is not valid.
2013 - Enclosure state failed Severity: CRITICAL Description: The enclosure is non-functional due to total Ethernet module or total server hardware failures. VC cannot configure or monitor this enclosure. Possible causes: • All Ethernet modules are not OK or DEGRADED. All Ethernet modules are suffering from some kind of hardware failure that prevents them from accepting configuration and passing network traffic. • All servers are not OK or DEGRADED.
• • • Verify end-to-end connectivity (for example, the ping command). Make sure OA has appropriate firmware version and update if necessary. If all workarounds fail: a. Export a support package from VC for HP analysis. b. Capture the output of the OA show all command for HP analysis. c. Contact HP customer support with the previously gathered information.
Action: Insert a module that is compatible with the adjacent module. Supported Adjacent Module Configurations: • HP 1/10Gb VC-Enet Module, HP 1/10Gb VC-Enet Module • HP 1/10Gb VC-Enet Module, HP 1/10Gb-F VC-Enet Module • HP VC Flex-10 Enet Module, HP VC Flex-10 Enet Module • HP VC FlexFabric 10Gb/24-Port Module, HP VC FlexFabric 10Gb/24-Port Module Possible cause 2: A newly inserted module is not the same type as the previously configured module that was in the interconnect bay.
• The primary VC-Enet module is unable to exchange network packets with the indicated module. This inability can occur if the Onboard Administrator has configured the internal switch that connects the I/O modules inappropriately. Action: • Verify that the network configuration (IP address, topology, etc.) is correct. If the module is in a remote enclosure (not located in the same enclosure as the primary VC-Enet module), reset or reboot the Active Onboard Administrator in the remote enclosure.
Possible cause: The OA reported the module status as failed. This is due to a hardware failure or a firmware failure. The firmware failure could be a kernel panic, memory exhausted, CPU overload, or boot failure. 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.
Action: Verify that communication between VC and Onboard Administrator for the affected server is operational. Verify that the server is in a good state (not failed or faulted). 5014 - Server state INCOMPATIBLE Severity: MAJOR Description: The VC management application has determined that the server BIOS version does not support the minimum capabilities required for Virtual Connect. Possible cause: The server has a down-rev BIOS version. Action: Update the BIOS on the server to latest version.
6021 - Profile has PXE enabled on a non-primary Flex-10 NIC Severity: MAJOR Description: PXE is enabled on an Ethernet connection in a profile that is mapped to a non-primary physical function on a Flex-10 NIC. The current Flex-10 implementation does not allow PXE booting on any but the first physical function on a Flex-10 NIC port. Possible cause: PXE is enabled on an Ethernet connection that is mapped to the second, third, or fourth physical function on a Flex-10 NIC.
Description: A network has been administratively disabled. Possible cause: A user disabled a network through the UI. Action: Enable the network through the UI. 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: • The VC fabric has no configured ports. The user removed all the uplink ports from the fabric.
• Remove either the unknown module, or the module adjacent to it. • Remove the unknown module from the interconnect bay. • Try re-seating or rebooting the module to see if it can recover. • Physically remove and replace the module. • 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.
HPRCU errors HPRCU return codes Return code Possible messages displayed 0 Success 1 ERROR: This server is not supported. 2 3 4 5 6 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. ERROR: The configuration can't be changed because the RBSU password has been set on the system.
CONREP errors Using CONREP The CONREP utility generates a system configuration XML file used to duplicate the hardware configuration of one ProLiant server onto another. The CONREP utility uses the hardware configuration XML file to identify and configure the system, which defaults to conrep.xml. You can change the default using the -x option. The actual system configuration file is captured as an XML data file. The default name is conrep.dat.
Value Meaning 0 The command was completed successfully. 2 The system configuration data file (conrep.dat) is corrupt or not found. 1 The hardware definition data file (conrep.xml) is corrupt or not found. 3 The Health Driver is required for this operation but is not loaded. 4 The system administrator password is set. The settings cannot be changed unless this password is cleared. 5 The XML hardware definition file (conrep.xml) is corrupt or not appropriate for the current platform.
HP iLO errors iLO overview 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. After the boot process is complete, the HB LED flashes in one second intervals.
Event log display Event log explanation Server power restored Displays when the server power is restored. Browser logout: IP address Displays the IP address for the browser that logged out. Server reset Displays when the server is reset. Failed Browser login ? IP Address: IP address Displays when a browser login fails. iLO Self Test Error: # Displays when iLO has failed an internal test. The probable cause is that a critical component has failed.
Event log display Event log explanation Virtual Floppy in use by: User Displays when a user begins using a Virtual Floppy. Remote Console login: User Displays when a user logs on a Remote Console session. Remote Console Closed Displays when a Remote Console session is closed. Failed Console login - IP Address: IP address Displays a failed console login and IP address. Added User: User Displays when a local user is added. User Deleted by: User Displays when a local user is deleted.
Event log display Event log explanation Power on request received by: Type A power request was received as one of the following types: Power Button Wake On LAN Automatic Power On Virtual NMI selected by: User Displays when an authorized user selects the Virtual NMI button. Virtual Serial Port session started by: User Displays when a Virtual Serial Port session is started. Virtual Serial Port session stopped by: User Displays when a Virtual Serial Port session is ended.
Status number Error message 0x0008 Cannot modify user. The login/ user name already exists. 0x0009 0x000A 0x000B 0x000C 0x000D 0x000E 0x000F 0x0010 0x0011 0x0012 0x0013 0x0014 0x0015 0x0016 0x0017 0x0018 0x0019 0x001A 0x001B 0x001C 0x001D 0x001E 0x001F 0x0020 0x0021 0x0022 0x0023 0x0024 0x0025 0x0026 0x0027 0x0028 0x0029 0x002A 0x002B Cannot delete user information for currently logged user. User login name was not found. User information is open for read-only access.
Status number Error message 0x002C Unable to allocate memory for parser. 0x002D 0x002E 0x002F 0x0030 0x0031 0x0032 0x0033 0x0034 0x0035 0x0036 0x0037 0x0038 0x0039 0x003A 0x003B 0x003C 0x003D 0x003E 0x003F 0x0040 0x0041 0x0042 0x0043 0x0044 0x0045 0x0046 0x0047 0x0048 0x0049 0x004A 0x004B 0x004C 0x004D 0x004E 0x004F 0x0050 0x0051 0x0052 0x0053 Unable to allocate memory from memory pool. License key error. License is already active. Login is currently being delayed.
Status number Error message 0x0054 Command without TOGGLE="Yes" attribute is ignored when host power is off. 0x0055 Duplicate record exists. 0x0056 Premature operation refused. 0x0057 0x0058 0x0059 0x005A 0x005B 0x005C 0x005D 0x005E 0x005F 0x0060 0x0061 0x0062 0x0063 0x0064 0x0065 0x0066 0x0067 0x0068 0x0069 0x006A 0x006B 0x006C 0x006D 0x006E 0x006F 0x0070 0x0071 0x0072 0x0073 0x0074 0x0082 0x0083 0x0084 0x0085 0x0086 SSH key was not found.
Status number Error message 0x0087 Either SNMP Pass-through OR Embedded Health must be enabled. One of these tags, AGENTLESS_MANAGEMENT_ENABLE, or SNMP_PASSTHROUGH_STATUS must be set to “yes” and the other tag set to “no.” The iLO subsystem is currently generating a Certificate Signing Request(CSR), run script after 10 minutes or more to receive the CSR. Power capping information is not available at this time, try again later. Failed to import the certificate.
Hardware and software link-related issues iLO uses standard Ethernet cabling, which includes CAT5 UTP with RJ-45 connectors. Straight-through cabling is necessary for a hardware link to a standard Ethernet hub. Use a crossover cable for a direct PC connection. The iLO Management Port must be connected to a network that is connected to a DHCP server, and iLO must be on the network before power is applied. DHCP sends a request soon after power is applied.
Network errors can cause iLO to conclude that a directory connection is no longer valid. If iLO cannot detect the directory, then iLO terminates the directory connection. Any additional attempts to continue using the terminated connection redirects the browser to the Login page. Redirection to the Login page can appear to be a premature session timeout. A premature session timeout can occur during an active session if: • The network connection is severed. • The directory server is shut down.
Unable to access virtual media or graphical remote console Solution: Virtual media and graphical Remote Console are only enabled by licensing the optional iLO Advanced Pack. A message appears to inform the user that the features are not available without a license. Although up to 20 users can log in to iLO, only one user can access the remote console. A warning message appears indicating that the Remote Console is already in use.
Unable to connect to the iLO IP address Solution: If the Web browser software is configured to use a proxy server, it will not connect to the iLO IP address. To resolve this issue, configure the browser not to use the proxy server for the IP address of iLO. For example, in Internet Explorer, select Tools>Internet Options>Connections>LAN Settings>Advanced, and then enter the iLO IP address or DNS name in the Exceptions field.
A warning message appears on the iLO webpages, indicating that the iLO Security Override switch is currently in use. An iLO log entry is added recording the use of the iLO Security Override switch. An SNMP alert might also be sent upon setting or clearing the iLO Security Override switch. 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.
permissions. This periodic query keeps the Directory connection active, preventing a timeout and logging the user. Troubleshooting Remote Console issues The following sections discuss troubleshooting Remote Console issues. In general: • Pop-up blockers prevent Remote Console from starting. • Pop-up blocking applications, which are set to prevent the automatic opening of new windows, prevent Remote Console from running. Disable any pop-up blocking programs before starting Remote Console.
Monitor problems in IRC or Java Remote Console Some displays (monitor/graphic card) do not support DirectDraw. For instance, some known USB VGA device drivers might disable DirectDraw in all monitors for Windows Vista and Windows 7 clients. The .NET Integrated Remote Console requires DirectDraw support. Solution for Java Integrated Remote console: 1. Shut down and exit your browser. 2. Open the Java Plugin Control Panel (on a Windows machine, select Start>Settings>Control Panel>Java Plug-in. 3.
3. Log in to iLO using Firefox. 4. Insert a USB key or Floppy on the local client system. Ensure you can access them. 5. Open a Java IRC session. 6. Click Virtual Drives>Floppy/USB-key, and select Virtual Media. Verify the Linux box displays. 7. Type or select the path of the USB-key/floppy (/dev/disk) which is inserted to the client. 8. Click the OK button.
The image shows how to mount the USB key by-label. Caps Lock goes out of synch between iLO and a Java Remote Console session After logging on to a JRC, the Caps Lock might go out of synch between iLO and the JRC. Solution: 1. Click the Keyboard menu item on the JRC screen. 2. Click Caps Lock to synchronize the iLO Caps Lock and the JRC Caps Lock.
session waits and eventually times out. If you require access to the IRC, attempt to access the IRC and time-out, then use the Acquire feature to take control of the IRC. Keyboard LED does not display correctly Solution: The client keyboard LED does not reflect the true state of the various keyboard lock keys. However, the Caps Lock, Num Lock and Scroll Lock keys are fully functional when using the Key Up/Down keyboard option in IRC.
Initial PuTTY input slow During initial connection using a PuTTY client, input is accepted slowly for approximately 5 seconds. This can be addressed by changing the configuration options in the client under the Low-level TCP connection options, uncheck the Disable Nagle's algorithm option.
Troubleshooting Remote Text Console issues The following sections discuss items to be aware of when attempting to resolve Remote Text Console issues. Unable to view the Linux installer in the text console When installing Linux using the text console, the initial install screen might not display because the screen is in graphics mode. Solution: To correct this and proceed with the installation, do one the following: • For most versions of Linux, enter linux text nofb.
Cookie order behavior During login, the login page builds a browser session cookie that links the window to the appropriate session in the firmware. The firmware tracks browser logins as separate sessions listed in the Active Sessions section of the iLO Status page. For example, when User1 logs in, the Web server builds the initial frames view, with current user: User1 in the top pane, menu items in the left pane, and page data in the lower-right pane.
• Start a new browser for each login by double-clicking the browser icon or shortcut. • Click the Log Out link to close the iLO session before closing the browser window. 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” topic in the HP ProLiant Integrated Lights-Out 3 v 1.
iLO network failed flash recovery Normally firmware upgrades proceed successfully. In the unlikely event of server power loss during an iLO firmware upgrade, iLO might still be recoverable when power is restored. When booting, the kernel performs image validation on the main image. If the image is corrupt or incomplete, the kernel enters Failed Flash Recovery. Failed Flash Recovery activates an FTP server within iLO. This FTP server enables you to send an image to iLO for programming.
221 Goodbye (reset). Connection closed by remote host. ftp> quit Issues generating a keytab using ktpass.exe If you use ktpass.exe to generate a keytab, you have to specify a principal name using the -princ argument. Principal names must be entered as follows: HTTP/ilo.somedomain.com@SOMEDOMAIN.COM This is case-sensitive. The command must be entered as follows: • The first part of the command is uppercase (HTTP) • The middle part is lowercase (ilo.somedomain.
An old certificate can cause issues with SSL can on the domain controller when it points to a previously trusted CA with the same name, which is rare but might happen if a certificate service is added and removed and then added again on the domain controller. To remove old certificates and issue a new one, follow the instructions in Step 2.
• On the Diagnostic page of the iLO browser interface, click Reset. Server name still present after ERASE utility is executed The Server Name field is communicated to iLO through the Insight Manager Agents. To remove the Server Name field after a redeployment of a server, do one of the following: • Load the Insight Manager Agents to update the Server Name field with the new server name. • Use the Reset to Factory Defaults feature of the iLO RBSU utility to clear the Server Name field.
Microsoft Windows Event ID and SNMP traps Event log messages associated with 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.
• 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 • cpqHoTrapFlags • cpqHoGenericData Supporting SNMP Trap Description: “[cpqHoGenericData]” NT Event ID: 1106 (Hex)0x44350452 (cpqhsmsg.
• 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.
• 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.
• 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.
• 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.
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.
• 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.
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.
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.
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. Event identifier: cpqhsmsg.
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. This error can be caused by a low memory condition. Rebooting the server may correct this error. Event identifier: cpqhsmsg.
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. The data contains the error code. Event identifier: cpqhsmsg.
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. Sets are not available. The data contains the error code. Event Identifiers 3072-3876 Event identifier: cpqhsmsg.
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. This indicates a low memory condition. Rebooting the system will correct this error. Event identifier: cpqhsmsg.
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. The Cluster service may not be running. Try to restart the Cluster service. Event identifier: cpqhsmsg.
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. Event identifier: cpqhsmsg.dll - 3869 (Hex)0x84350f1d (Service Event) Log Severity: Warning (2) Log Message: The Cluster service is not running.
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. The data contains the error code. Event identifier: cpqhsmsg.
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. Event identifier: cpqhsmsg.
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. Event identifier: cpqhsmsg.dll - 4609 (Hex)0x84351201 (Service Event) Log Severity: Warning (2) Log Message: Could not read from the registry sub-key.
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) Log Severity: Warning (2) Log Message: The Storage Agents service detected an error. The insertion string is: %1. The data contains the error code.
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”. The data contains the error code. Event identifier: cpqstmsg.
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. This indicates a low memory condition. Rebooting the system will correct this error. Event identifier: cpqstmsg.
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.
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. Log Message: Logical drive number %5 on the array controller in slot %4 has a new status of %2.
• 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 %2. SNMP Trap: cpqDa5PhyDrvStatusChange - 3029 in CPQIDA.MIB Symptom: Physical Drive Status Change.
• 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. SNMP Trap: cpqDa5AccelBadDataTrap - 3026 in CPQIDA.
• 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.
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. The current physical drive status is indicated in the cpqScsiPhyDrvStatus variable.
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.
• 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. Event Identifiers 1101-1199 NT Event ID: 1101 (Hex)0x8435044d (cpqstmsg.
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.
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. SNMP Trap: cpqTape3PhyDrvCleanTapeReplace - 5009 in CPQSCSI.
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.” NT Event ID: 1145 (Hex)0xc4350479 (cpqstmsg.dll) Log Severity: Error (3) Event Title: External Array Logical Drive Status Change. Log Message: Logical drive number %5 on array “%4” has a new status of %6.
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.
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. SNMP Trap: cpqFca2AccelStatusChange - 16017 in CPQFCA.MIB Symptom: External Array Accelerator Board Status Change.
• 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” is reporting a battery failure.
• 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” fan module at location %5 has a new status of %6.
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.
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. Be sure that the storage system environment is being cooled properly and that no components are overheated.
• 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. SNMP Trap: cpqTape3LibraryDegraded - 5012 in CPQSCSI.MIB Symptom: Tape Library Degraded.
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.
• 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.
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. SNMP Trap: cpqFcTapeLibraryStatusChange - 16009 in CPQFCA.MIB Symptom: Fibre Channel Tape Library Status Change.
• 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. SNMP Trap: cpqFcTapeDriveStatusChange - 16011 in CPQFCA.
• 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. SNMP Trap: cpqFcTapeDriveCleanTapeReplace - 16013 in CPQFCA.
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. This trap indicates that the agent has detected a change in the status of a tape library. The variable cpqDaTapeLibraryStatus indicates the current tape library status.
• 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.
• 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. SNMP Trap: cpqDaTapeDriveCleanTapeReplace - 3024 in CPQIDA.MIB Symptom: Tape Drive Cleaning Tape Needs Replacing.
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. This trap indicates that the agent has detected a change in the status of an ATA disk drive. The variable cpqIdeAtaDiskStatus indicates the current disk drive status.
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”. SNMP Trap: cpqSsExBackplaneFanStatusChange - 8022 in CPQSTSYS.MIB Symptom: Storage System Fan Status Change.
• 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. The enclosure model is “%6”.
• 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.
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.
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.
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.
• 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.
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 • cpqDaCntlrHwLocation • cpqDaLogDrvCntlrIndex • cpqDaLogDrvIndex • cpqDaLogDrvStatus Supporting SNMP Trap Description: “Status is now [cpqDaLogDrvStatus].” NT Event ID: 1201 (Hex)0x843504b1 (cpqstmsg.
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.
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. The current status is represented by the variable cpqDaAccelStatus.
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. SNMP Trap: cpqDa6AccelBatteryFailed - 3040 in CPQIDA.MIB Symptom: Accelerator Board Battery Failed.
• 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.
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.” NT Event ID: 1210 (Hex)0x843504ba (cpqstmsg.
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.
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. The agent has detected a change in the temperature status of a storage system.
• 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.
• 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.
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.
• 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. SNMP Trap: cpqSs6PwrSupplyStatusChange - 8031 in CPQSTSYS.
• 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.
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.
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. The variable cpqSSboxConnectionStatus indicates the current connection status.
• 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 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. The variable cpqIdeAtaDiskSSDWearStatus indicates the current SSD wear status.
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”. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqstmsg.
Log Severity: Warning (2) Log Message: Unable to read security configuration information. SNMP sets have been disabled. Cause: This can be cause by an invalid or missing configuration or by a corrupt registry. Reinstalling the Storage Agents may correct this problem. Event identifier: cpqstmsg.dll - 1803 (Hex)0xc435070b (Service Event) Log Severity: Error (3) Log Message: Unable to load a required library. This error can be caused by a corrupt or missing file.
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”. The data contains the type found. Event identifier: cpqstmsg.
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.
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”. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqstmsg.
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. Event identifier: cpqsvmsg.dll - 264 (Hex)0x84350108 (Service Event) Log Severity: Warning (2) Log Message: The Server Agents service could not load the module “%1”.
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. Event identifier: cpqsvmsg.dll - 399 (Hex)0xc435018f (Service Event) Log Severity: Error (3) Log Message: The Server Agents service encountered a fatal error. The service is terminating.
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. NT Event ID: 1024 (Hex)0xc4350400 (cpqsvmsg.dll) Log Severity: Error (3) Log Message: A cache accelerator parity error indicates a cache module needs to be replaced.
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. Schedule server down time to replace the memory.
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.
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. SNMP Trap: cpqHe5ResMemBoardRemoved - 6065 in CPQHLTH.MIB Symptom: Memory board or cartridge or riser removed.
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. User Action: Replace the indicated board or cartridge or Riser.
• 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 [cpqHeFlt
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. The server's temperature is outside of the normal operating range. The server is shut down if the cpqHeThermalDegradedAction variable is set to shutdown (3).
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'. SNMP Trap: cpqHe3ThermalSystemFanDegraded - 6021 in CPQHLTH.MIB Symptom: The system fan status has been set to degraded. An optional system fan is not operating normally.
Supporting SNMP Trap Data: • 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. SNMP Trap: cpqHe3AsrConfirmation - 6025 in CPQHLTH.MIB Symptom: The server is operational again.
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.
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: • sysName • cpqHoTrapFlags • cpqSm2CntlrSelfTestErrors Supporting SNMP Trap Description: “Remote Insight/Integrated Lights-Out self test error [cpqSm2CntlrSelfTestErrors].
• 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.
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.
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.
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. Supporting SNMP Trap Data: • sysName • cpqHoTrapFlags Supporting SNMP Trap Description: “Errors occurred during server restart.
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 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.
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].” NT Event ID: 1131 (Hex)0x8435046b (cpqsvmsg.dll) Log Severity: Warning (2) Log Message: The Fan Sub-system has lost redundancy. Replace any failed or missing fans.
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. SNMP Trap: cpqHe3TemperatureFailed - 6040 in CPQHLTH.
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.
• 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. Replace any failed or degraded power converters.
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.
• 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. This trap indicates that an agent or utility has changed the name of an enclosure within the rack.
• 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.
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.
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. User Action: None.
• 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. This may result in overheating of the enclosure.
• 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.
• 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.
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.
• 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.
• 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.
• 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 [cpqRackN
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.
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.
• 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.
• 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.
• 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].
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. User Action: Check the power enclosure and power supplies. Replace any failed or degraded power supplies. Add additional power supplies if needed.
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.
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. The power subsystem load balancing wire is missing. User Action: Connect the load balancing wire.
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. The power subsystem has been improperly configured.
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. The data contains the error code.
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) Log Severity: Error (3) Log Message: Unable to write to the registry.
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. The %1 Agent is older than the other components of the Server Agents. Reinstall the entire Server Agents package to correct this error.
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”. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqsvmsg.
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”. The data contains the error code. Event identifier: cpqsvmsg.
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. Event identifier: cpqsvmsg.
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. Event identifier: cpqnimsg.dll - 261 (Hex)0x84350105 (Service Event) Log Severity: Warning (2) Log Message: Unable to read from the registry.
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. This error can be caused by a low memory condition. Rebooting the server may correct this error. Event identifier: cpqnimsg.
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. The data contain the error code. Event identifier: cpqnimsg.
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. Event identifier: cpqnimsg.dll - 297 (Hex)0x84350129 (Service Event) Log Severity: Warning (2) Log Message: An attempt to log an event to the IML failed. The IML log may be full.
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. Check to make sure management service is up and running.
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. If the error persists, reinstalling the Management Agents may correct this error. Event identifier: cpqnimsg.
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. Internal adapter, Hub, or Switch failures can also cause this condition. User Action: Check the cables to the adapter and the Hub or Switch.
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. This can be caused by loss of link due to a cable being removed from the adapter or the Hub or Switch.
• 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.
Support and other resources Before you contact HP Be sure to have the following information available before you call HP: • Active Health System log (HP ProLiant Gen8 or later products) Download and have available an Active Health System log for 3 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).
Acronyms and abbreviations ACU Array Configuration Utility ADG Advanced Data Guarding (also known as RAID 6) ADU Array Diagnostics Utility ASR Automatic Server Recovery CA certificate authority CGI Common Gateway Interface CLP command line protocol CONREP Configuration Replication utility DDNS Dynamic Domain Name System DHCP Dynamic Host Configuration Protocol DMA direct memory access DNS domain name system Acronyms and abbreviations 394
EBIPA Enclosure Bay IP Addressing EEPROM electrical erasable programmable read only memory FBDIMM fully buffered DIMM FBWC flash-backed write cache HB heartbeat HBA host bus adapter HP SIM HP Systems Insight Manager HPRCU HP ROM Configuration Utility iLO Integrated Lights-Out IML Integrated Management Log IRC Integrated Remote Console JRC Java Remote Console LDAP Lightweight Directory Access Protocol LOM Lights-Out Management Acronyms and abbreviations 395
MMC Microsoft Management Console NMI nonmaskable interrupt NTP network time protocol NVRAM nonvolatile memory PERL Practical Extraction and Report Language POST Power-On Self Test PPM 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 RIS reserve information sector SAS serial attached SCSI SATA serial ATA Acronyms and abbreviations 396
SLES SUSE Linux Enterprise Server SMART self-monitoring analysis and reporting technology SSD solid-state drive SSH Secure Shell SSL Secure Sockets Layer SSO single sign-on SSP Selective Storage Presentation UID unit identification WINS Windows® Internet Naming Service Acronyms and abbreviations 397
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.
Index 1 1003 1022 1023 1026 4 - VCM-OA communication down 214 Domain state FAILED 215 Domain state PROFILE_FAILED 215 Domain state NO_COMM 215 4009 4012 4014 4019 - FC FC FC FC Module Module Module Module OA CPU Fault Event 220 State Failed 220 State Incompatible 221 State is NO_COMM 221 2 5 2003 - Enclosure import failed 216 2011 - Enclosure state NO_COMM 216 2013 - Enclosure state failed 217 2016 - Enclosure Fined failed 217 228 - DIMM Configuration Error - Processor X, Channel Y 55 229 - DIMM Co
ADU error messages 9, 29 Advanced ECC support 39 Advanced Memory Protection (AMP) 39 agent descriptions 255 alert and trap problems 240 alertmail log messages 172 AMP (Advanced Memory Protection) 39 array accelerator 29 array accelerator board 9, 10, 12, 16, 17, 19, 27, 28, 72 array accelerator memory size change detected 72 array controllers 22, 78 array status 30 ASR (Automatic Server Recovery) 94 ASR timer failure 50 authentication and startup log messages 173 authentication code incorrect 241 B battery
Ethernet Module events, Virtual Connect 218 Ethernet Network events, Virtual Connect 223 event identifiers 1025-1092, server agents 336 event identifiers 1061-1098, storage agents 278 event identifiers 1101-1199, storage agents 285 event identifiers 1103-1183, server agents 345 event identifiers 1105-1808, foundation agents 256 event identifiers 1200-1294, storage agents 311 event identifiers 1343-4613, storage agents 329 event identifiers 1539-3352, server agents 379 event identifiers 2048-2359, foundation
message identifiers 24725-24749, Smart Array message identifiers 24750-24774, Smart Array message identifiers 24775-24799, Smart Array message identifiers 24800-24824, Smart Array mirror data miscompare 19 mirrored memory 39 J Java Remote Java Remote Java Remote Java Remote working Console, Caps Lock issue 245 Console, display problem 243 Console, monitor problem 243 Console, mouse/keyboard not 243 N K network settings, unable to connect to iLO 239 NIC agent errors 383 NMI event 40, 41, 42, 43, 44 Node
power fault 45 power module 94 power regulator 49 power regulator, troubleshooting 49 power supplies 43, 45, 47, 65, 66, 96, 97 powering down 40 powering on problems 40 PPM (processor power module) 42 predicive failure errors detected 22 premature logout, directory user 237 processor correctable error threshold passed 95 processor error codes 98 processor problems 42, 43, 55, 98, 99 processor stepping 48 processor uncorrectable internal error 95 processors 42, 43, 45, 46, 47, 49, 98, 99 profile events, Virt
unable to connect to iLO IP address 240 unable to connect to iLO processor through NIC 239 unable to log in to iLO 239 unable to login with emergency access 240 unable to pass data through an SSH terminal 248 unable to receive HP SIM alarms from iLO 240 unable to return to login page 238 uncorrectable memory error 97 unknown disable code 27 unknown module events, Virtual Connect 224 unrecoverable host bus data parity error 97 unrecoverable read error 27 unsupported array accelerator battery attached 78 unsu
