HP 3PAR OS 3.1.1 Messages and Operators Guide Abstract This guide is for system administrators and experienced users who are familiar with the storage systems, understand the operating system(s) they are using, and have a working knowledge of RAID. This guide provides information on the T-Class, F-Class and StoreServ 10000 Storage system LEDs, alerts, components, and procedures for powering the system on and off.
© Copyright 2008, 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Introduction..................................................................................................7 Related Documentation..............................................................................................................7 1 Component Numbering for T-Class Storage System.........................................8 Identifying Storage System Components.....................................................................................35 Service Processor Placement..............
Securing the Storage System....................................................................................................71 5 Understanding F-Class Storage System LED Status.........................................58 Using the F-Class Component LEDs............................................................................................58 Bezel LEDs........................................................................................................................
Alert Example.............................................................................................................293 Alert Suggested Action................................................................................................293 Cage.............................................................................................................................293 Format of Possible Cage Exception Messages.................................................................294 Cage Example 1......
PD Suggested Action 3................................................................................................309 PD Example 4.............................................................................................................309 PD Suggested Action 4................................................................................................309 PD Example 5.............................................................................................................
Introduction This guide provides the information you need to familiarize yourself with the HP 3PAR Storage System alerts, components, LEDs, and procedures for powering on and powering off the storage system. Information provided in this document supports the HP 3PAR T-Class, F-Class, and StoreServ 10000 Storage Systems. NOTE: The InServ Storage Server has been rebranded as HP 3PAR Storage System.
1 Component Numbering for T-Class Storage System NOTE: Illustrations in this chapter show sample systems and might not match your configuration. Identifying Storage System Components Figure 1 (page 8) and Figure 2 (page 9) identify the major components of the T400 Storage System in a 2M (40U) HP 3PAR cabinet.
Figure 2 T400 Rear View Service Processor Placement The Service Processor (SP) is located at the bottom of the cabinet and is designed to support all actions required for maintenance of the storage system, providing real-time, automated monitoring. The SP also supports remote access to diagnose and resolve potential problems. The SP is usually installed directly above the PDUs and below the battery tray (Figure 3 (page 10)) and is powered internally by the storage system.
Figure 3 Placement of the Service Processor NOTE: In the T800, the SP is located above the backplane, below the lowest drive chassis but above the upper battery tray. Figure 5 (page 12) illustrates SP placement for the T800. When a cabinet does not include a SP, a filler panel covers the area of the cabinet that the SP normally occupies.
Figure 4 Numbering of Chassis Bays in the Cabinet A storage system can be housed in a single cabinet or multiple cabinets. When multiple cabinets are required, the first cabinet (the controller node cabinet ) holds the storage system backplane populated with controller nodes. Any additional cabinets, or drive chassis cabinets , hold the additional drive chassis that do not fit into the controller node cabinet.
Figure 5 Controller Node Cabinet Component Layout 12 Component Numbering for T-Class Storage System
Figure 6 Drive Chassis Cabinet Component Layout PDU Numbering For each cabinet, the four Power Distribution Units (PDUs) occupy the lowest chassis bay in the cabinet. Numbers for PDUs are assigned: • beginning with 0. • from top to bottom. Figure 7 (page 13) illustrates the four PDUs at the bottom of a T-Class cabinet.
NOTE: In the T800, PDUs are positioned back-to-back so that they only take up 2U of space at the bottom of the cabinet rather than the standard 4U of space. PDUs are accessible from both the front and the rear of the storage system. “Controller Node Cabinet Component Layout” (page 12) illustrates PDU placement for the T800. Each PDU has two power banks, each with a separate circuit breaker, to be used exclusively for storage system components (Figure 8 (page 39)).
A battery tray can hold a maximum of four BBUs. The number of BBUs and battery trays in a system depends on the number of controller nodes installed (Table 3 (page 15)).
Figure 11 Magnetek BBU Numbering Scheme Controller Node Numbering The T-Class Storage System contain two, four, six, or eight controller nodes per system and only use T-Class controller nodes. Controller nodes are loaded into the backplane enclosure from bottom to top. Therefore, for the T800 with only two controller nodes installed, those controller nodes would occupy the lowest 4U of the backplane and would be numbered, node 6 and node 7.
Figure 12 Numbering of Controller Nodes As shown in Figure 13 (page 18), a controller node contains six PCI slots. These slots accept PCI adapters such as dual-port Fibre Channel adapters, iSCSI adapters, and Ethernet adapters. The controller node also has a management Ethernet port (E0) and a maintenance port (C1).
Figure 13 Numbering for Dual-Port Fibre Channel Adapters in the Controller Node PCI Slots Each Fibre Channel adapter in a PCI slot has four ports. Each iSCSI adapter in a PCI slot has two or four ports. PCI adapters assume the numbers of the PCI slots they occupy. • In dual-port adapters, ports are labeled port 1 and 2, from top to bottom. • In quad-port Fibre Channel adapters, the ports are numbered port 1–4, from top to bottom. Inside the controller node are control cache DIMMs and data cache DIMMs.
Figure 14 Control Cache and Data Cache DIMMs in a T-Class Controller Node Numbers for controller nodes and their components are assigned in the order indicated in Table 4 (page 19). Table 4 Numbering System for Controller Nodes and their Components The Following Components... Are Numbered... Running from...
Drive chassis are always placed above the storage system backplane enclosure and numbered according to their position in relation to the backplane, as shown in Figure 15 (page 20). Figure 15 Numbering of Drive Chassis NOTE: For systems occupying multiple cabinets, drive chassis numbers continue at the bottom of the next cabinet and progress through the top of the cabinet. Figure 16 (page 21) and Figure 17 (page 21) illustrate individual drive chassis components and how they are numbered.
Figure 16 Numbering of Drive Chassis Components Figure 17 Numbering of Disks on a DC4 and DC4 Type-2 Drive Magazine Numbers for drive chassis components are assigned: • from bottom to top. • from rear to front (in the case of disks). • in the order indicated by Table 5 (page 21). Table 5 Numbering System for Drive Chassis Components The Following Components... Are Numbered... Running from... Drive cages 0,1,...
Table 5 Numbering System for Drive Chassis Components (continued) The Following Components... Are Numbered... Running from... Fibre Channel ports FC-AL 0 FC-AL 1 A0,B0 A1,B1 top to bottom Drive magazines 0,1,2,3,4,5,6,7,8,9 left to right Disks on the drive magazine 0,1,2,3 rear to front Drive Magazine Allocation For highest availability and data protection, drive magazines are placed on different loops and internal power domains by loading them in the order illustrated by Figure 18 (page 22).
NOTE: For further instructions on drive magazine allocation, see the HP 3PAR T-Class Storage System Installation and Deinstallation Guide . Power Supply Numbering Cabinets are divided into upper and lower power domains that contain drive cages or controller nodes and dedicated power supplies. Drive cages and controller nodes depend on these power supplies, located at the rear of the system, to supply power from the PDUs at the bottom of the cabinet.
2 Component Numbering for F-Class Storage System NOTE: Illustrations in this chapter show sample systems and might not match your configuration. Identifying Storage System Components Figure 20 (page 24) and Figure 21 (page 25) identify the major components of an F-Class Storage System.
Figure 21 F400 Rear View Service Processor Placement The Service Processor (SP) is located at the bottom of the cabinet and is designed to support all actions required for maintenance of the storage system, providing real-time automated monitoring. The SP also supports remote access to diagnose and resolve potential problems. Because the SP is capable of supporting multiple storage systems at the same operating site, not all cabinets contain a SP.
Understanding Component Numbering Because of the almost unlimited number of potential configurations, there is standardized component placement and internal cabling to simplify installation and maintenance. For this reason, system components are placed in the cabinet according to the principles outlined in this section and numbered according to their order and location in the cabinet. Cabinet Numbering The F-Class Storage System 2M (40U) cabinet is an EIA-standard rack that holds storage system components.
Table 6 (page 27) describes the pattern for cabinet numbering in multi-cabinet storage systems and for operating sites with multiple systems: Table 6 Cabinet Numbering Cabinet Number Controller node cabinet C00 Drive chassis cabinets connecting to the first node cabinet C01, C02, C03...C09 Figure 23 (page 27) shows the location of controller node and drive chassis components for the storage system cabinet in the F200 and F400.
Figure 24 Numbering of PDUs Each PDU has two power banks, each with a separate circuit breaker, to be used exclusively for storage system components (Figure 25 (page 28)). Figure 25 PDU Power Banks WARNING! To avoid possible injury, damage to storage system equipment, and potential loss of data, do not use the surplus power outlets in the storage system PDUs.
Figure 26 Numbering of Controller Nodes A controller node contains two controller slots and two on-board Ethernet ports. See Figure 27 (page 30) for specific port type assignments.
Figure 27 Numbering for Dual-Port Fibre Channel Adapters in the Controller Node PCI Slots Each Fibre Channel adapter in a PCI slot has two or four Fibre Channel ports. Fibre Channel adapters assume the numbers of the PCI slots they occupy. • In dual-port adapters, ports are labeled port 1 and port 2, from top to bottom. • In quad-port Fibre Channel adapters, the ports are numbered port 1, port 2, port 3, and port 4, horizontally. Inside the controller node are data cache DIMMs and control cache DIMMs.
Drive Chassis Numbering Depending on configuration, an F-Class Storage System can include up to 10 drive chassis. A drive chassis houses 16 drive magazines. Drive chassis are first placed sequentially below controller node 1 (controller node 3 in an F400) and then sequentially above controller node 0. Drive chassis are numbered as shown in Figure 29 (page 31).
Figure 30 Drive Chassis - Front View, Drive Magazine Bay Numbering Figure 31 Drive Chassis - Rear View, Port Numbering Drive Magazine Allocation For highest availability and data protection, drive magazines are placed on different loops and internal power domains by loading them in the order described in by Table 7 (page 33).
Table 7 Drive Magazine Loading Pattern Group Number Drive Magazine Pair Number Drive Magazine Bay 1 1 0, 4 2 11, 15 3 8, 12 4 3, 7 5 1, 5 6 10, 14 7 9, 13 8 2, 6 2 3 4 NOTE: The loading sequence displayed in the table above indicates the loading order is in vertical columns. All drives in a vertical column must be of the same type and speed. Mixing drive types and speeds in the same column may cause unpredictable results.
Figure 33 Numbering of Power Supplies 34 Component Numbering for F-Class Storage System
3 Component Numbering for HP 3PAR StoreServ 10000 Storage NOTE: Illustrations in this chapter show sample systems and might not match your configuration. Identifying Storage System Components Figure 34 (page 35) and Figure 35 (page 36) identifies the major components the 10400 and 10800 in an HP 3PAR cabinet.
Figure 35 10400 and 10800 Rear View Service Processor Placement The Service Processor (SP) is supports all actions required for maintenance of the storage system, providing real-time, automated monitoring. The SP also supports remote access to diagnose and resolve potential problems. The SP resides in the lower section of the controller node cabinet and is typically installed directly below the node chassis power supply tray and directly above the DC4 drive chassis (Figure 36 (page 36)).
Understanding Component Numbering Because of the large number of potential configurations, we have standardized component placement and internal cabling to simplify installation and maintenance. System components are placed in the cabinet according to the principles outlined in this section and numbered according to their order and location in the cabinet. NOTE: For information about standardized cabling, see the HP 3PAR StoreServ 10000 Storage Installation and Deinstallation Guide.
Figure 37 PDU Numbering Each PDU is equipped with two power banks and separate circuit breakers, used exclusively for storage system components (Figure 8 (page 39)).
Figure 38 Power Banks in the PDU NOTE: For more information on PDUs and storage system configurations, see the HP 3PAR StoreServ 10000 Storage Installation and Deinstallation Guide. Battery Module Numbering The HP 3PAR StoreServ 10000 Storage system include one or two battery compartments that hold up to four battery modules each. The battery compartment is part of the node chassis and adjacent to the node fan compartment.
Figure 39 Battery Module Numbering Controller Node Numbering The HP 3PAR StoreServ 10000 Storage system may contain two, four, six, or eight controller nodes per system configuration. The controller node chassis slots are located at the rear of the cabinet. From the rear of the cabinet, component numbering starts with zero (0) at the bottom-left corner and advances right and upward, refer to Figure 40 (page 41).
Figure 40 Controller Nodes Numbering in the 10400 and 10800 As shown in Figure 41 (page 42), a controller node contains nine PCI slots. These slots contain PCI adapters, such as quad-port Fibre Channel and iSCSI adapters. Each controller node has an administrative Ethernet port (E0), a dedicated Remote Copy over IP port (RCIP) (E1), and a console maintenance port (S0).
Figure 41 Controller Node PCI Slots and Port Numbering Each Fibre Channel adapter in a PCI slot has four ports. Each iSCSI adapter in a PCI slot has two ports. PCI adapters assume the numbers of the PCI slots they occupy. • In dual-port adapters, ports are labeled port 1 and port 2 in ascending order away from the adapter handle. • In quad-port Fibre Channel adapters, the ports are numbered port 1, port 2, port 3, and port 4 in ascending order away from the adapter handle.
Figure 42 Control Cache and Data Cache DIMMs in a Controller Node Numbers for controller nodes and their components are assigned in the order indicated in Table 10 (page 43). Table 10 Controller Nodes and Components Numbering Components Numbered PCI adapters PCI ports dual-port adapters quad-port adapters 0, 1, 2, 3, 4, 5, 6, 7, 8 1, 2 1, 2, 3, 4 Control Cache DIMMs 0, 1, 2, 3 Data Cache DIMMs CH1- 0.1.0 0.1.1 CH0- 0.0.0, 0.0.1 CH1- 1.1.0, 1.1.1 CH0- 1.0.0, 1.0.
Figure 43 Drive Chassis Numbering NOTE: For systems with multiple cabinets, drive chassis numbering may vary based on InForm OS configuration. Figure 44 (page 44) and Figure 45 (page 45) illustrate individual drive chassis components and their numbering scheme. Fibre Channel ports in the FC-AL adapters at the sides of the drive chassis enable connection to the controller nodes.
Figure 45 Numbering of Disks on a NL and FC Drive Magazine Numbers for drive chassis components are assigned from bottom to top, from rear to front (in the case of disks). Table 11 Drive Chassis Component Numbering Components Numbered Running from Drive cages 0, 1, ...
Figure 46 Power Supplies Numbering within Power Domains 46 Component Numbering for HP 3PAR StoreServ 10000 Storage
4 Understanding T-Class Storage System LED Status Using the T-Class Component LEDs The T-Class Storage System components have LEDs to indicate whether or not the hardware is functioning properly and to help identify errors. These LEDs help diagnose basic hardware problems. You can quickly identify hardware problems by examining the LEDs on all the components and using the following tables and illustrations in this chapter.
Figure 48 Connections and LEDs on the DC4 Drive Cage FC-AL Modules Table 12 Drive Cage DC4 FC-AL Module LED Displays LED Appearance Indicates RX Steady green light The presence of a small form-factor pluggable optical transceiver (SFP) and a valid signal from the node. No light No connection to the node or no SFP is installed. Steady green light The presence of an SFP and the LED is on and transmitting. No light No SFP is present or the SFP transmitter failed.
Table 12 Drive Cage DC4 FC-AL Module LED Displays (continued) LED Appearance Indicates high-level threshold, or a power supply has failed. Hot plug Split mode 4GB/s Flashing amber light (1 blink per second) The drive cage has some type of error, such as a failed or missing power supply, but is communicating with a node. Rapid toggle between amber and green light A cage firmware upgrade initiated by the upgradecage CLI command is in progress.
Figure 49 DC4 Drive Magazine LEDs Table 13 Drive Magazine LED Displays LED Appearance Indicates Drive magazine status Steady green light The drive magazine is functioning properly. Steady amber light A drive magazine error, or one or more drives are bypassed on at least one path. Disk status Hot plug 50 Quick flashing, or 20 percent on, 80 The disk is not spun up but has power. percent off green light Steady green light The disk is spun up and waiting for a command.
Controller Node LEDs Depending on configuration, a storage systsem contains between two and eight controller nodes, all located in the chassis. Controller nodes contain the following LEDs (Figure 50 (page 51)): Figure 50 Controller Node LEDs Table 14 Controller Node LED Displays LED Appearance Indicates Disk hot plug Steady amber light Disk is prepared for hot plug. No light Disk is not prepared for hot plug.
Table 14 Controller Node LED Displays (continued) LED Ethernet status Appearance Indicates Flashing green light No Ethernet activity. No light No Ethernet connection. Steady amber light 1000 MB/s mode Steady green light 100 MB/s mode No light 10 MB/s mode (or disconnected) Fibre Channel Port LEDs The Fibre Channel adapter in the controller node also contains Fibre Channel port LEDs (Figure 51 (page 52)).
Figure 52 iSCSI Adapter Ports and LEDs Table 16 iSCSI Adapter Port LED Displays LED Appearance Indicates Port 1, 2 No light No connection or active link. Steady green light Link is established. Flashing green light Receiving or transmitting activity.
Figure 53 Power Supply LEDs NOTE: The appearance of the drive chassis and controller node power supplies can vary slightly according to manufacturer and location. Table 17 Power Supply LED Displays LED Appearance Indicates Power supply status Steady green light Power is on. Steady amber light Power supply error. No light Broken connection. Steady green light AC is entering from an external source.
Battery Backup Unit LEDs Depending on the configuration, storage systems with HP 3PAR cabinets include one or more battery trays that hold up to four BBUs each. BBUs supply power to write the cache memory to the drive inside the node in the event of a power failure.
Supermicro Service Processor LEDs Supermicro Service Processor LEDs are located at the top of the service processor (Figure 56 (page 56)). Figure 56 Supermicro Service Processor LEDs Table 19 Supermicro Service Processor LED Displays LED Appearance Indicates Power No light Service processor is off. Steady green light Service processor is on. No light No hard drive activity. Flashing amber light Hard drive activity. No light Port is not connected. Steady green light Port is connected.
Figure 57 Supermicro II Service Processor LEDs Table 20 Supermicro II Service Processor LED Displays LED Appearance Indicates Power No light Service processor is off. Steady green light Service processor is on. No light No hard drive activity. Flashing amber light Hard drive activity. No light Port is not connected. Steady green light Port is connected. Flashing green light Network activity. No light Service processor temperature is normal.
5 Understanding F-Class Storage System LED Status Using the F-Class Component LEDs The F-Class Storage System components have LEDs to indicate whether or not the hardware is functioning properly and to help identify errors. These LEDs help diagnose basic hardware problems. You can quickly identify hardware problems by examining the LEDs on all the components and using the following tables and illustrations in this chapter.
Table 21 Bezel LED Displays (continued) LED Appearance Indicates Steady amber light Error within the node. Steady amber and hot-plug LED amber Fatal node failure. (see Controller Node LEDs on page 5.13) Removing the Bezels and Unlocking the Door If your HP 3PAR cabinet has locking fascias, you must first remove the fascias to access the system bezel. WARNING! Hazardous energy is located behind the rear access door of the storage system cabinet. Use caution when working with the door open.
Figure 60 Drive Chassis OPs Panel LEDs 60 Understanding F-Class Storage System LED Status
Table 22 Drive Chassis OPs Panel LED Displays LED Appearance Indicates Power On Steady green light Used in conjunction with Power Supply/Cooling/Temperature Fault LED, 2GB Link Speed LED, Invalid Address LED, and System Fault LED as described below. Power Steady amber light Supply/Cooling/Temperature Fault LED • Test state (5 seconds), if: ◦ Power On LED is steady green. ◦ System Fault LED is steady amber. ◦ Invalid Address LED is steady amber. ◦ 2GB Link Speed LED is steady green.
Table 22 Drive Chassis OPs Panel LED Displays (continued) LED Appearance Indicates Invalid Address LED Steady amber light • Indicates test state (5 seconds), if: System Fault LED ◦ Power On LED is steady green. ◦ Power Supply/Cooling/Temperature Fault LED is steady amber. ◦ System Fault LED is steady amber. ◦ 2GB Link Speed LED is steady amber. Flashing amber light Invalid address mode ID switch setting if Power On LED is steady green.
Interface Card LEDs The drive chassis contains two interface cards, FC-AL-A and FC-AL-B, with the following LEDs: Figure 61 Interface Card LEDs Table 23 Interface Card LED Displays LED Appearance Indicates Host Port 0, 1, 2, 3 Steady green light The incoming Fibre Channel signal is good. Steady green light All device ports are good at 2GB. No light All device ports are good at 1GB. Flashing green light Drives are bypassed by module. Steady amber light FC-AL module is failed.
Figure 62 Drive Chassis Power Supply/Cooling Module LEDs Table 24 Power Supply/Cooling Module LED Displays LED Appearance Indicates Power Supply Good Steady green light The power supply is operating normally. Steady amber light The power supply is not operating correctly. Steady green light Indicates the AC input is normal. Steady amber light Indicates AC input failure. Steady green light Indicates the fan is operating normally. Steady amber light There is a fan fault.
Figure 63 Drive Magazine LEDs Table 25 Drive Magazine LED Displays LED Appearance Indicates Activity Steady green light Drive power is present. Blinking green light There is drive activity. Slowly blinking green light (once every 3 seconds) The drive has spun down. No light A drive is not present. Steady amber light There is a drive fault. No light No drive is present. Drive power is on. Drive activity.
Figure 64 Controller Node LEDs Table 26 Controller Node LED Displays LED Appearance Indicates Disk hot plug Steady amber light Disk is prepared for hot plug. No light Disk is not prepared for hot plug. Steady amber light In combination with the status LED blinking green three times per second, indicates the node is prepared for removal. In combination with the status LED being solid, indicates a fatal failure. No light The node is not prepared for removal.
Table 26 Controller Node LED Displays (continued) LED Appearance Indicates Steady green light 100 MB/s mode No light 10 MB/s mode (or disconnected) Fibre Channel Port LEDs The Fibre Channel adapter in the controller node also contains Fibre Channel port LEDs: Figure 65 4-Port Fibre Channel LEDs Table 27 Fibre Channel Adapter LED Displays LED Appearance Indicates No light Wake up failure (dead device) Steady green light Normal - link up at 2-4GBs/s Flashing green light Link down or not connect
Table 28 iSCSI Adapter Port LED Displays LED Appearance Indicates No light No connection or active link. Steady green light Link is established. Flashing green light Receiving or transmitting activity. Emulex Fibre Channel Port LEDs The Emulex Fibre Channel adapter in the controller node also contain Fibre Channel port LEDs. Two port Emulex Fibre Channel adapters are only used in an F-Class Storage System (Figure 67 (page 68)).
Controller Node Power Supply LEDs F-Class Storage System controller node power supply units are located on both sides of the controller nodes. The battery is integral to the controller node power supply. The LEDs are located on the rear of the power supply units: Figure 68 Controller Node Power Supply LEDs Table 30 Power Supply LED Displays LED Appearance Indicates Power supply status Steady green light Power is on. Steady amber light Power supply error.
A blue illuminated lamp denotes that power is being supplied to a power bank. When the blue lamp is not illuminated, the power bank is not receiving AC input. Service Processor LEDs The following describes the LEDs for the Supermicro and the Supermicro II Service Processor LEDs. Supermicro Service Processor The Supermicro Service Processor LEDs are located at the top of the service processor (Figure 70 (page 70)).
Figure 71 Supermicro II Service Processor LEDs Table 32 Supermicro II Service Processor LED Displays LED Appearance Indicates Power No light Service processor is off. Steady green light Service processor is on. No light No hard drive activity. Flashing amber light Hard drive activity. No light Port is not connected. Steady green light Port is connected. Flashing green light Network activity. No light Service processor temperature is normal.
6 Understanding HP 3PAR StoreServ 10000 Storage LED Status The storage system components have LEDs to indicate whether or not the hardware is functioning properly and to help identify errors. The LEDs help diagnose basic hardware problems. You can quickly identify hardware problems by examining the LEDs on all of the components and using the tables and illustrations in this chapter. If you detect any problems during inspection of the LEDs, contact your Authorized Service Provider.
DC4 Drive Cage FC-AL Module LEDs The DC4 drive cage FC-AL modules have the following LEDs: Figure 73 FC-AL LED and Port Locations Table 33 Drive Cage DC4 FC-AL Module LEDs LED Appearance Indicates RX Steady green light A presence of a small form-factor pluggable optical transceiver (SFP) and a valid signal from the node. No light No connection to the node or no SFP is installed. Steady green light A presence of an SFP and that the LED is on and transmitting.
Table 33 Drive Cage DC4 FC-AL Module LEDs (continued) LED Appearance Indicates FC-AL module error or other cage error. If both FC-AL modules have a steady light, the temperature of a disk drive in the drive-cage has exceeded its high-level threshold, or a power supply has failed. Hot plug 4GB/s 74 Flashing amber light (1 blink per second) The drive cage has some type of error, such as a failed or missing power supply, but is communicating with a node.
Drive Magazine LEDs NOTE: After powering on, allow approximately two minutes for the disks on the drive magazine to spin up before checking the drive magazine LEDs. Drive magazines have the following LEDs: Figure 74 Drive Magazine LEDs Table 34 Drive Magazine LEDs LED Appearance Indicates Drive magazine status Steady green light The drive magazine is functioning properly. Steady amber light A drive magazine error, or one or more drives are bypassed on at least one path.
Controller Node LEDs Depending on configuration, storage systems contain between two and eight controller nodes, all located in the chassis. Controller nodes have the following LEDs: NOTE: You can issue the locatenode command to flash all service LEDs associated to a controller node blue. This includes the power supplies, battery modules, and fan module LEDs. Table 35 Controller Node LEDs LED Appearance Indicates Node Disk No light Normal operation.
Table 35 Controller Node LEDs (continued) LED HBA Service Appearance Indicates Rapidly flashing green light (three times per second) The node is booting, or, in combination with a blue service LED, the node is safe to remove. Flashing amber light The node has joined the cluster but there is a degraded component associated with the node. A slow flashing light means the node is part of the cluster. Steady amber light An error within the node.
Fan Module LEDs The 10400 controller node chassis can hold up to eight fan modules that each hold two fans, and the 10800 can hold up to 16. Fan modules have the following LEDs: Table 36 Fan Module LEDs LED Appearance Indicates Status Green Normal operation, no faults. Amber Fan speed is too low, failed, off or not working properly. With a blue service LED, the fan module failed and was not able to recover in 60 seconds. Replace the fan module. Solid Blue The servicenode start fan has been issued.
Fibre Channel Adapter Port LEDs The Fibre Channel adapter in the controller node also contains Fibre Channel port LEDs: Figure 76 Fibre Channel LEDs Table 37 Fibre Channel Adapter LEDs LED Appearance Indicates Port 1-4 No light Wake up failure (dead device) or power is not applied. (Port speed) Amber light off Not connected. Amber (3 fast blinks) Connected at 4GB/sec. Amber (4 fast blinks) Connected at 8GB/sec. Steady green light Normal/Connected - link up.
CNA Port LEDs The Converged Network Adapter (CNA) includes two ports with corresponding LEDs: Figure 77 CNA Port LEDs Table 38 CNA Port LEDs LED Appearance Indicates Link No light Link down Steady green light Link up No light No activity.
Ethernet LEDs The controller node has two built-in Ethernet ports and each port contains two LEDs: Figure 78 Ethernet LEDs Table 39 Ethernet LEDs LED Appearance Indicates ACT/LNK (top E0, E1) Steady green light Valid link partner Flashing green light Data activity No light ACT/LNK is off Steady yellow light 1000Mb/sec mode Steady green light 100Mb/sec mode No light 10Mb/sec mode Speed (bottom E0, E1) Ethernet LEDs 81
Power Supply LEDs Power supplies are located at the rear of the storage system. The drive chassis and controller node power supplies have the following LEDs: Drive Chassis Power Supply LEDs Drive chassis power supplies are located at the rear of the drive chassis. Figure 79 Drive Chassis Power Supply LEDs Table 40 Drive Chassis Power Supply LEDs LED Appearance Indicates Power Supply Status Steady green light Power is on. Steady amber light Power supply error. No light Broken connection.
Controller Node Power Supply LEDs The controller node power supplies are located behind the cable management tray in the node chassis. Figure 80 Controller Node Power Supply LEDs The power supply service LED is located on the dividers between the power supplies. Figure 81 Controller Node Power Supply Service LED Table 41 Controller Node Power Supply LEDs LED Appearance Indicates Power Status Steady green light Power is on. Steady amber light Power supply error. No light Broken connection.
Battery Module LEDs Depending on configuration, storage systems include one or two battery compartments that hold up to four battery modules each. Each node has one battery module. Each battery module has three LEDs: Figure 82 Battery Module LEDs Table 42 Battery Module LEDs LED Appearance Indicates Charging Green Battery modules is being charged. Amber Battery module is at fault. Off Battery module is not in node or connected. Green Battery module output is on and supplying power to the node.
Power Distribution Unit Lamps Each storage system includes four PDUs that contain two power bank lamps: Figure 83 PDU Lamps Table 43 PDU Lamps LED Appearance Indicates Lamp Steady green light Power is being supplied to a power bank and the circuit breaker is turned ON. Off Power bank is not receiving AC input or the circuit breaker is turned OFF.
Service Processor LEDs The LEDs are located at the top of the SP: Figure 84 Service Processor LEDs Table 44 SP LEDs LED Appearance Indicates Power No light Service processor is off. Steady green light Service processor is on. No light No hard drive activity. Flashing amber light Hard drive activity. No light Port is not connected. Steady green light Port is connected. Flashing green light Network activity. No light Service processor temperature is normal.
7 Power Off/On Procedures Powering Off the Storage System When it is necessary to power off the storage system, use the following steps to safely remove power from the storage system and the service processor (SP). NOTE: PDUs in any expansion cabinets connected to the storage system may need to be shut off. Use the locatesys command to identify all connected cabinets. locatesys will blink all node and drive cage LEDs. Note this information now, as it is needed for the last step in this procedure.
2. 3. Verify that the blue LED on the front of the SP is illuminated. Verify that all drive chassis LEDs are solid green and all controller node status LEDs are blinking green once per second. Connecting to the Service Processor Once you are connected to the SP, there are two SP user interfaces, SPOCC and SPMAINT, that you can use to perform various administrative and diagnostic tasks to support of both the storage system and the SP.
1. Unlock and open the rear door of the storage system cabinet. If necessary, insert a red crossover Category 5 Ethernet cable (RJ45 to RJ45) into the proper Ethernet port of the SP (ETH1), refer to the following figures.
Figure 88 Local Area Connection Properties Dialog Box 4. Double-click Internet Protocol (TCP/IP). The Internet Protocol (TCP/IP) Properties dialog box appears (“Internet Protocol (TCP/IP) Properties Box” (page 90)). Figure 89 Internet Protocol (TCP/IP) Properties Box 5. In the Internet Protocol (TCP/IP) Properties dialog box, click the Use the following IP address button, then type the following IP addresses: Table 45 IP Addresses 90 IP address 10.255.155.49 Subnet mask 255.255.255.
6. 7. 8. Click OK. Click OK in the Advanced TCP/IP Settings dialog box to finish configuring the LAN connection. Initiate a SSH using PuTTy. Refer to “Using PuTTY” (page 91). Using PuTTY After you have configured LAN settings and established an Ethernet connection, use PuTTY to initiate a SSH between the maintenance PC and the SP. 1. Go to the permanent location where you extracted putty.zip and double-click the putty.exe file. 2.
Logging into the SP Onsite Customer Care Interface (SPOCC) After the Ethernet connection is configured, log in to the SPOCC interface using a supported Web browser. To log in to SPOCC using a Web browser: 1. Type the IP address of the SP in the Web browser and press ENTER. NOTE: If you are using the crossover cable to the SP ETH1 (Int) port, use IP address 10.255.155.54. 2. 3. On the Service Processor Login screen, click the Login button. The Enter Network Password dialog box appears.
8 Alerts Alerts are triggered by events that require intervention by the system administrator. This chapter provides a list of alerts identified by message code, the message(s), and what action should be taken for each alert. To learn more about alerts, see the HP 3PAR StoreServ Storage Concepts Guide. To view the alerts, use the showalert command.
MESSAGE CODE 0x0010001 TYPE Serial link event MESSAGE 1 Serial link from node x to node y failed. FIFO is full. SUGGESTED ACTION The serial link hardware between node x and y has detected an error. If the problem is persistent, or if other node-related errors are present, Node x should be diagnosed and replaced. If there is a hardware failure in the main link connecting nodes x and y at the same time there is a serial link failure, there is a 50% chance of losing the healthy node.
MESSAGE CODE 0x0030001 TYPE Firmware coredump event MESSAGE Firmware COREDUMP: recovered file from node SUGGESTED ACTION There was a firmware coredump on one of the Fibre Channel adapter cards that has been saved in the specified location. Contact your local service provider for technical support and services.
MESSAGE CODE 0x0030002 TYPE Too many WWNs on an RCFC port MESSAGE More than one WWN () seen on an RCFC port SUGGESTED ACTION Configure the array or the network such that this RCFC port can only see other RCFC ports. Please refer to the Remote Copy User's Guide for instructions and configuration details. Configure the array or the network such that this RCFC port can only see a single WWN. The Remote Copy configuration needs to be verified.
MESSAGE CODE 0x0030003 TYPE Host [[sw_port]] experienced over 50 CRC errors () in 24 hours MESSAGE Host Port experienced over 50 CRC errors () in 24 hours SUGGESTED ACTION A host port link is reporting an excessive number of CRC errors. Verify that the fiber channel cables are connected properly and that the cables/SFP's/HBAs are functioning properly. Please contact the HP Support for additional assistance if required. The specified port has detected an unusual number of errors.
MESSAGE CODE 0x0030007 TYPE RCFC port sees non-3PAR WWNs MESSAGE RCFC port sees non-RCFC WWNs SUGGESTED ACTION Configure the array or the network such that this RCFC port can only see other RCFC ports. Please refer to the Remote Copy User's Guide for instructions and configuration details. Configure the array or the network such that this RCFC port can only see other RCFC ports. The Remote Copy configuration needs to be verified.
MESSAGE CODE 0x0030009 TYPE Excessive retransmits on RCFC port. MESSAGE Excessive RCFC retransmits at .% on node STATE This alert gets generated when a node detects that the RCFC retransmit rate has exceeded 2% but will clear once the rate drops below 0.5%. SUGGESTED ACTION An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
MESSAGE CODE 0x00300de TYPE Component state change MESSAGE Port Node Slot Degraded () STATE Firmware Core Dumped SUGGESTED ACTION An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
MESSAGE CODE 0x00300fa TYPE Component state change MESSAGE Port Node Slot Failed () STATE 1 Down Due To Reset Failure SUGGESTED ACTION The HBA failed to reset. This may be caused by a hardware failure on the HBA. Replace the HBA. STATE 2 Down Due To Missing Firmware File SUGGESTED ACTION Points to improper software installation of the HP 3PAR OS. Contact your local service provider for technical support and services.
MESSAGE CODE 0x0040001 TYPE Need to manually run checkvv on VV MESSAGE VV VV name () Need to run command: checkvv -y SUGGESTED ACTION An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
MESSAGE CODE 0x0040003 TYPE Admin Volume I/O timeout MESSAGE I/O operations to the admin volume are taking too long to complete. The PR may transition to the internal drive. SUGGESTED ACTION Contact your local service provider for technical support and services.
MESSAGE CODE 0x0040004 TYPE VV availability MESSAGE VV () is unavailable because of preserved data. SUGGESTED ACTION An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
MESSAGE CODE 0x0040006 TYPE Aborted DCOWs MESSAGE VV () tree has aborted DCOWs on Node SUGGESTED ACTION An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
MESSAGE CODE 0x00400de TYPE Component state change MESSAGE VV () Failed () STATE 1 Maintenance Check Required SUGGESTED ACTION An event has occurred on your system which requires attention. The specified volume (vvname) requires a checkvv in order to validate internal structures. Contact your authorized support provider for assistance if required.
MESSAGE CODE 0x00400fa TYPE Component state change MESSAGE VV () Failed () STATE 1 LDs Not Started SUGGESTED ACTION The VV specified in the alert has not been started by the system due to some of the underlying LDs are not in the 'normal' state. Use the CLI command showvv to confirm that the VV is still in this state. Use the CLI command showld -vv to see which LDs are not in the 'normal' state.
SUGGESTED ACTION The snapshot VV specified in the alert is stale. Use the CLI command showvv to confirm that the VV is still in this state. The snapshot VV is stale because at some point in the past, there were I/O errors on the underlying LDs, or because the snapshot volume ran out of space. At this point, the only action that can be taken on this VV is to delete it. Contact your local service provider for technical support and services.
MESSAGE CODE 0x0050005 TYPE Log LD raid set failure. MESSAGE Log LD 0 (log0.0) has a failed raid set: 0. Reason pd 2 ch 544 is stale (media valid, disk missing, pderr 1) pd 21 ch 500 is stale (media valid, disk missing, pderr 1) SUGGESTED ACTION 1. 2. 3. 4. Ensure there are no logging chunklets or failed/degraded disks. If the RAID set is still stale, fix the issue that caused the to go stale. Remove the Log ld using the removeld -rmsys command. Use the admithw command to create a new Log Ld.
MESSAGE CODE 0x006000a TYPE Chunklet relocation failure MESSAGE PD : repeated failures relocating chunklets: SUGGESTED ACTION The relocation of a chunklet from a failed disk did not succeed. The failed device should be replaced. Please contact the HP Support for assistance. An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
MESSAGE CODE 0x0060002 TYPE Disk monitor stopped MESSAGE pd wwn has failed for too long. Disk monitoring has stopped on this disk. SUGGESTED ACTION Contact your local service provider for technical support and services.
MESSAGE CODE 0x0060007 TYPE Disk overtemp MESSAGE 1 pd (wwn ) is overtemp ( C, limit C) and has been spundown. SUGGESTED ACTION There are drives in the system that has reached critical temperature. Run CLI commands showpd -s, showpd -e, showcage -d to confirm. Check the data center room to verify it is at an optimal temperature. Contact your local service provider for technical support and services.
MESSAGE CODE 0x0060008 TYPE Disk overtemp warning MESSAGE At least one drive in the system has an above normal temperature. SUGGESTED ACTION There are drives in the system that have an above normal temperature. Run CLI commands showpd -s, showpd -e, showcage -d to confirm. Check the data center room to verify it is at an optimal temperature. Contact your local service provider for technical support and services.
MESSAGE CODE 0x0060009 TYPE Disk overtemp alert MESSAGE At least one drive in the system has reached a CRITICAL temperature and it will be spun-down if it continues to rise. SUGGESTED ACTION There are drives in the system that has above normal temperature. Run CLI commands showpd -s, showpd -e, showcage -d to confirm. Check the data center room to verify it is at an optimal temperature. Contact your local service provider for technical support and services.
MESSAGE CODE 0x00600de TYPE Component State Change; degraded disk MESSAGE PD Degraded () STATE 1 Notready SUGGESTED ACTION The PD specified in the alert has reported it being not ready. Use the CLI command showpd pd_id to confirm the disk is still in this state. This state might be temporary and might fix itself on retries. If the error persists, contact your local service provider for technical support and services. This state might be temporary and might fix itself on retries.
A physical disk drive has failed and requires replacement. STATE 5 Write Label Failed SUGGESTED ACTION The PD specified in the alert has been marked failed because the disk label could not be written to the disk. Use the CLI command showpd to confirm the disk is still in this state. A physical disk drive has failed and requires replacement. STATE 6 Read Label Failed SUGGESTED ACTION The PD specified in the alert has been marked failed because the disk label could not be read from the disk.
SUGGESTED ACTION A disk might be marked media-failed if it has been reporting disk aborts with error code 21 to specify that the threshold for SMART errors has been exceeded. Contact your local service provider to replace the disk. A physical disk drive has failed and requires replacement. STATE 10 Multiple Chunklets Media Bad SUGGESTED ACTION A disk might be marked media-failed because more than six chunklets on that disk have reported media-errors.
SUGGESTED ACTION The drive was issued a command by the Sysmgr to bring a PD onloop. No action required. STATE 16 Spinup SUGGESTED ACTION A PD is in the process of spinning up. No action required. STATE 17 Fail To Spinup SUGGESTED ACTION The PD is experiencing problems spinning up. If this continues, a new failure alert will be issued with further actions to be taken. STATE 18 Loop Failure SUGGESTED ACTION The PD loop connection may have failed. No action required.
STATE 23 Sysmgr Spundown SUGGESTED ACTION The Sysmgr has issued a command for a PD to be spundown. No action required. STATE 24 Critical Over Temp SUGGESTED ACTION Temperature of the PD has reached the threshold maximum. Check for fan failure and ventilation obstructions. STATE 25 Spundown Requested Drive Ready SUGGESTED ACTION The PD has been sent a request by the Sysmgr to be spundown. The PD will remain in a ready state. No action required.
SUGGESTED ACTION An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance. STATE 30 Temperature Over Alert SUGGESTED ACTION An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance. STATE 31 Temperature Over Warning SUGGESTED ACTION An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
MESSAGE CODE 0x00600fa TYPE Component state change; disk failed MESSAGE PD Failed () STATE 1 Invalid SUGGESTED ACTION The PD specified in the alert has been marked failed. Use the CLI command showpd to confirm that the disk is still in this state. The PD can be marked Invalid because of a number of reasons. A reason code along with Invalid will give more information about why the PD was marked Invalid.
A disk is marked failed if a SCSI inquiry to check its capacity fails. This error is also intermittent and might get fixed if the SCSI inquiry succeeds on a retry. As above, the suggested action is to wait for a few minutes for the retry to fix it. If not, contact your local service provider for a possible disk replacement. STATE 5 Write Label Failed SUGGESTED ACTION The PD specified in the alert has been marked failed because the disk label could not be written to the disk.
Contact your local service provider for possible disk replacement. STATE 10 Invalid Type SUGGESTED ACTION The PD specified in the alert has been marked failed because the vendor of the disk is not included in the list of supported vendors. Use the CLI command showpd to confirm the disk is still in this state. A physical disk drive has failed and requires replacement. Contact your local service provider for possible disk replacement.
STATE 15 Prolonged Missing SUGGESTED ACTION The PD specified in the alert has been marked failed because it has been marked missing for more than 20 minutes. Use the CLI command showpd to confirm the disk is still in this state. Contact your local service provider for possible disk replacement. STATE 16 Invalid Media SUGGESTED ACTION The PD specified in the alert has been marked media-failed. Use the CLI command showpd to confirm the disk is still in this state.
STATE 21 Increased Error Count SUGGESTED ACTION A disk will be marked media-failed if there has been an increase of more than 20 in the error counts of the disk in the last 24 hours. Contact your local service provider for possible disk replacement. STATE 22 No Valid Ports SUGGESTED ACTION The PD specified in the alert has been failed because it has no valid ports. Use the CLI command showpd to confirm the disk is still in this state.
MESSAGE CODE 0x0070001 TYPE No free chunklet found for relocation MESSAGE Could not find a suitable free chunklet for : SUGGESTED ACTION The system has a limit on the number of free chunklets that are used for automatic relocation. This limit is one disk worth of chunklets per system node. If you see this alert, there must have been numerous disk errors on the system recently, or perhaps an entire cage is missing, or the system has used up all its free space.
MESSAGE CODE 0x0070002 TYPE No spare chunklet found for relocation MESSAGE Could not find a suitable spare chunklet for : SUGGESTED ACTION The system has a limit on the number of free chunklets that are used for automatic relocation. This limit is one disk worth of chunklets per system node. If you see this alert, there must have been numerous disk errors on the system recently, or perhaps an entire cage is missing, or the system has used up all its free space.
MESSAGE CODE 0x0080001 TYPE Could not process SCSI DB MESSAGE Host path status change for : Path to status SUGGESTED ACTION Contact your local service provider for technical support and services.
MESSAGE CODE 0x0090001 TYPE Host Path Status Change MESSAGE Host path status change for : Path to SUGGESTED ACTION The host mentioned should not be connected to the port specified. Disconnect the host and check the host and port configuration settings. Contact your local service provider for technical support and services.
MESSAGE CODE 0x00900fa TYPE Host Persona Incompatible with Port Persona MESSAGE Host persona incompatible with port persona Failed () SUGGESTED ACTION The host mentioned should not be connected to the mentioned port. Disconnect the host. Check the host and port configuration settings. Contact your local service provider for technical support and services.
MESSAGE CODE 0x00900de STATE ONTAP host shares port with non-ONTAP host(s) TYPE Component state change SUGGESTED ACTION An event has occurred on your system which requires attention. The specified port has detected a mix of ONTAP and non-ONTAP configured hosts. Configure all hosts on this port to be ONTAP, or move all non-ONTAP hosts to another port. Contact your authorized support provider for assistance if required.
MESSAGE CODE 0x00a0001 TYPE Snap Admin Volume low on space MESSAGE Snap Admin volume '', id low on space, % zone allocated SUGGESTED ACTION An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
MESSAGE CODE 0x00a0002 TYPE Snap Data Volume low on space MESSAGE Snap Data volume '', id low on space, % zone allocated SUGGESTED ACTION An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
MESSAGE CODE 0x00a0004 TYPE Snap Data Volume 2 low on space MESSAGE Snap Data volume '', id low on space, % zone allocated SUGGESTED ACTION An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
MESSAGE CODE 0x00c0002 TYPE Process cannot be started MESSAGE Process could not be started up after repeated attempts on node SUGGESTED ACTION The process identified in the message cannot be started. This affects some system operations, depending on the process that cannot be restarted. Contact your local service provider for technical support and services.
MESSAGE CODE 0x00d0002 TYPE PR transition MESSAGE The PR is currently getting data from the internal drive on node , not the admin volume. Previously recorded alerts will not be visible until the PR transitions to the admin volume SUGGESTED ACTION Try to determine why the admin volume is not functional. Most likely, this is because some nodes or cages are not currently available. Contact your local service provider for technical support and services.
MESSAGE CODE 0x00e0001 TYPE Double node failure MESSAGE System is not able to recover from double node failure SUGGESTED ACTION More than one node has died and system operations cannot recover. Contact your local service provider for technical support and services.
MESSAGE CODE 0x00e0002 TYPE System manager cannot startup MESSAGE 1 Cannot reach TOC quorum. Use 'setsysmgr' to set system manager startup state. SUGGESTED ACTION Attempt to get as many of the physical disks online as possible before proceeding. If the system software has not been recently upgraded, run showsysmgr to gather more information about the problem and a list of valid TOCs.
powerfail. You can use “setsysmgr force_iderecovery” to force recovery with possible data loss. SUGGESTED ACTION Attempt to get all the nodes online in order to attempt a successful powerfail recovery. If only one node is still down, the system waits about 10 minutes and attempts to do a powerfail recovery with the remaining nodes. Contact your local service provider for technical support and services.
MESSAGE CODE 0x00e0003 TYPE Node recovery powerfail event MESSAGE Node recovery requires a powerfail to continue SUGGESTED ACTION When recovering from previous node failures due to software panics, it is sometimes necessary for the system manager to restart the entire system. This alert indicates that the system manager has restarted the system. Contact your local service provider for technical support and services.
MESSAGE CODE 0x00e0005 TYPE License key usage MESSAGE 1 This system contains nodes, but is only licensed for nodes. Please contact your 3PAR representative as soon as possible. SUGGESTED ACTION The system is not licensed for the number of nodes currently installed; shut down the excess nodes, or contact your local service provider regarding purchasing licenses for the additional nodes. MESSAGE 2 License feature "" has expired.
MESSAGE CODE 0x00e0006 TYPE System recovery notification about bad volume MESSAGE Powerfail recovery could not be performed for Volume with id .This might have caused loss of data for that volume. Use checkvv to check and fix the volume metadata consistency. SUGGESTED ACTION Use the CLI command setsysmgr force_iderecovery to cause powerfail recovery to resume. WARNING! 142 Alerts This can cause data loss for the volumes indicated by the ID in the message.
MESSAGE CODE 0x00e0007 TYPE Pfail partition needs to be wiped MESSAGE Use the “setsysmgr force_idewipe” CLI command to wipe pfail partition and restart the system. This will cause some data to be lost. Node had panics. SUGGESTED ACTION Use the CLI command setsysmgr force_idewipe to cause the system to resume. WARNING! This can cause data loss, and cause all LDs and VVs to be checked for consistency.
MESSAGE CODE 0x00e0008 TYPE Power fail saved version mismatch MESSAGE Powefail saved version on node does not match expected version . User needs to either revert to matching tpd software version or wipe the pfail save partition using “setsysmgr force_idewipe” cli command. SUGGESTED ACTION Contact your local service provider. It will need to be determined what software version is needed to make the pfail recovery happen.
MESSAGE CODE 0x00e0009 TYPE Failed to save task data MESSAGE The PR is not available on the admin volume. The system was unable to save status data for tasks. SUGGESTED ACTION The system normally stores away task data for completed tasks in the admin volume. Due to some problems with the admin volume, some of this data could not be stored. If necessary, this data can be retrieved from system logs by your local service provider.
MESSAGE CODE 0x00e000a TYPE Task failed MESSAGE Task (type '', name '') has failed (). Please see task status for details. SUGGESTED ACTION The task specified in the message has failed. Run the CLI showtask -d command for detailed status on the failure.
MESSAGE CODE 0x00e000b TYPE Pfail recovery stalled due to failed previous NM1 recovery. MESSAGE Previous NM1 recovery found on node with missing node . SUGGESTED ACTION Contact your local service provider for technical support and services.
MESSAGE CODE 0x00e000c TYPE Cluster shutdown after powerfail recovery completion MESSAGE Cluster shutdown initiated after system recovery for node mask reason SUGGESTED ACTION Check the system to see if this alert auto-resolves itself. If not, the system is having trouble recovering from powerfail. Contact your local service provider for technical support and services.
MESSAGE CODE 0x00e000d TYPE System recovery stalled due to unknown replicant state MESSAGE System recovery stalled due to unknown replicant state on node for replicant . Reported state . SUGGESTED ACTION Contact your local service provider for technical support and services.
MESSAGE CODE 0x00e000e TYPE System recovery stalled due to sole owner of LD missing MESSAGE System recovery stalled because node is down, and is the sole owner of some lds. current online nodes: 0x, original online nodes: 0x. SUGGESTED ACTION Contact your local service provider for technical support and services.
MESSAGE CODE 0x00e000f TYPE Servicemag information MESSAGE servicemag unmark : SUGGESTED ACTION No action required.
MESSAGE CODE 0x0110001 TYPE Errors accessing the IDE disk MESSAGE Internal drive in node has experienced errors. SUGGESTED ACTION The internal IDE drive for the specified node has encountered errors. Monitor for further issues and have the drive replaced if necessary.The internal IDE drive for the specified node has encountered errors. Monitor for further issues and have the drive replaced if necessary. An event has occurred on your system which requires attention.
MESSAGE CODE 0x0110002 TYPE IDE disk error handling MESSAGE 1 Node is being shutdown by the system because it had internal drive errors. MESSAGE 2 Node is not being shutdown by the system even though there are internal drive errors because it is the last node left alive. MESSAGE 3 Node is not being shutdown by the system even though there are internal drive errors because some LDs cannot be served by the remaining nodes.
MESSAGE CODE 0x0110004 TYPE Version mismatch event MESSAGE 1 My node version x1.x2.x3.x4 could not join the cluster with node version y1.y2.y3.y4 SUGGESTED ACTION There is a software version mismatch of the node trying to join the cluster. Install the new node with the correct software version. Contact your local service provider for technical support and services.
MESSAGE CODE 0x0130001 TYPE Too many alerts in the system MESSAGE There are too many alerts in the system. Deleted alerts. SUGGESTED ACTION There are too many alerts in the system. This affects the system's ability to process newer alerts quickly. The system has automatically deleted some of the oldest alerts. Please cleanup older alerts from the system using the CLI command removealert.
MESSAGE CODE 0x0140001 TYPE Notification MESSAGE 1 Cage , Interface Card , SFP (Unqualified). SUGGESTED ACTION An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance. MESSAGE 2 chcmd_state: ld ldch is pd ch , not pd ch SUGGESTED ACTION Contact HP Support. MESSAGE 3 RAID 0 ld is failed due to stale chunklet.
SUGGESTED ACTION An interface card reset was successful. No further action is required. An event has occurred on your system which does not require further attention MESSAGE 7 DC3 I2C Lockup Reset Failed on cage , side SUGGESTED ACTION An interface card reset failed. Please contact the HP Support for assistance. An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
MESSAGE 12 OS version for node does not match but compatible with cluster master (node ): Node : .. Master: .. SUGGESTED ACTION The OS version installed on the specified node does not match the cluster master's version, but is compatible with it. The node will be admitted to the cluster. An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
MESSAGE CODE 0x0150002 TYPE CLI server process event MESSAGE 1 Max allowable CLI server processes of exceeded, no process created for connection from client address: SUGGESTED ACTION The CLI server creates processes to service CLI client requests. This alert is generated when the CLI server is unable to create a process and is likely due to an unexpected system error or because too many processes already exist.
MESSAGE CODE 0x0150006 TYPE Authentication failure MESSAGE authentication failures in secs SUGGESTED ACTION The CLI client unsuccessfully attempted multiple log ins within a short period of time. This alert is likely due to an application trying to access the storage system with incorrect login credentials.
MESSAGE CODE 0x015000c TYPE CPG free space limit MESSAGE Free space allows CPG to grow to MB, limit: MB, warn:MB Notes This alert is generated when there is not enough storage in the system to allow the CPG to grow to either the growth warning or limit size, i.e. the warning/alert settings are meaningless because the system will run out of storage before these can be reached. The alert is generated every 24 hours when the condition exists.
• Verify additional space is available with a different disk pattern: cli% showspace -ha mag -p -dk 0-15 --Estimated(MB)--RawFree UsableFree 197632 98816 • Update the CPG growth parameters with this new pattern: cli% setcpg -ha mag -p -dk 0-15 mycpg 162 Alerts
MESSAGE CODE 0x0170001 TYPE TOC update MESSAGE TOC update done to disks out of . SUGGESTED ACTION The system was unable to save configuration information to a substantial number of disks. Most likely the system has lost access to some drive magazines. Work on getting more disks back online as soon as possible to prevent a loss of TOC quorum.
MESSAGE CODE 0x0170002 TYPE TOC update failure MESSAGE System is entering powerfail mode because it failed to find a quorum of disks to write the TOC to SUGGESTED ACTION The system was unable to save configuration information to a quorum of disks. It will now go into powerfail mode. An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
MESSAGE CODE 0x0190001 TYPE ea msg timeout MESSAGE Failed to recv reply for from node: User Data SUGGESTED ACTION An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
MESSAGE CODE 0x01a0006 TYPE CPU Configuration MESSAGE Node Expected CPU(s) Found CPU(s) SUGGESTED ACTION Contact your local service provider for technical support and services.
MESSAGE CODE 0x01a0007 TYPE BIOS IDE log entry MESSAGE BIOS log entry stored in /pr_mnt SUGGESTED ACTION Node firmware (BIOS) previously detected a hardware failure which required normal operation to abruptly terminate. A log of the event and BIOS output leading up to the event has been recorded and is available at the specified path. This log needs to be examined for a detailed failure cause. Contact your local service provider for technical support and services.
MESSAGE CODE 0x01a0008 TYPE Node environmental MESSAGE ERROR: node-: : Where: is: Table 46 Error Code I2C_OK = 0x00 TE_PASS (0) I2C_BUS_ERR = 0x37, I2C_DEV_ERR = 0x38, I2C_HOST_BUSY = 0x39, I2C_BUSY_IN_BIOS = 0x3A, TEMP_VCC_FAIL = 0x3B, I2C_ERR = 0x3C, is: Table 47 Status OVER LIMIT UNDER LIMIT Within Tolerance = 0x38, , , , are: Measurement CPU0 1.32V: CPU1 1.32V: 82563 1.
LM94 LM87 LM87 Ext CPU0 CPU1 CPU0 VRM CPU1 VRM CPU DIMM0 CPU DIMM1 Temp: Temp: Temp: Temp: Temp: Temp: Temp: Temp: Temp: 23 C 25 C 23 C 25 C 28 C n/a n/a 38 C 36 C 0 C 0 C -10 C 0 C 0 C n/a n/a 0 C 0 C 65 C 65 C 65 C 85 C 85 C n/a n/a 105 C 105 C Within Within Within Within Within Within Within Within Within Tolerance Tolerance Tolerance Tolerance Tolerance Tolerance Tolerance Tolerance Tolerance NOTE: These tables are examples of environmental readings from nodes.
MESSAGE CODE 0x01a0014 TYPE Too many TCP segment errors MESSAGE 1 Excessive TCP segment errors at .% on node MESSAGE 2 Excessive TCP retransmits at .% on node SUGGESTED ACTION The specified node is experiencing excessive TCP segment errors. Validate the network setup. Validate the network cabling and configuration. Contact your authorized support provider for assistance if required.
MESSAGE CODE 0x01a0015 TYPE Node PCIe Correctable Error Status MESSAGE Node :status SUGGESTED ACTION The specified device is experiencing many errors. Please contact support. An event has occurred on your system which requires attention. The specified node is experiencing excessive TCP segment errors. Validate the network cabling and configuration. Contact your authorized support provider for assistance if required.
MESSAGE CODE 0x01a0016 TYPE Node PCIe Link Status MESSAGE Node :status SUGGESTED ACTION The node is experiencing link failures. Please contact support. An event has occurred on your system which requires attention. The link is experiencing errors. Contact your authorized support provider for assistance if required.
MESSAGE CODE 0x01a001e TYPE Node Thermal Status STATE 1 Alert Level STATE 2 Node Shutdown Level STATE 3 WARNING Level SUGGESTED ACTION Check room temperature or fan status, replace the fan if failed. If fan failed, call HP Support.
MESSAGE CODE 0x01a001d TYPE Node-Failure-Analysis File Received From Remote/Local MCU MESSAGE Node-Failure-Analysis file received from Node %d SUGGESTED ACTION There was a Node Failure Analysis file on the NEMOE that has been saved. Contact your local service provider for technical support and services. An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance.
the temperature continues to exceed the limit, contact your local service provider for technical support and services. • If a voltage limit has been exceeded, contact your local service provider for technical support and services. If the temperature continues to exceed the limit, replace the node. STATE 6 Node Offline Due to Failure SUGGESTED ACTION If the node doesn't come back up within 1 hour, contact technical support.
MESSAGE CODE 0x01a00fa TYPE Component State Change MESSAGE Node Failed () STATE 1 Link Error SUGGESTED ACTION Could not establish communication between node ‘x’ and node ‘y’. If node ‘y’ is turned off, there is no suggested action required. If node ‘y’ is turned on, make sure node ‘y’ is properly inserted into the slot. Contact your local service provider for technical support and services.
SUGGESTED ACTION Recover the core files and contact your local service provider for technical support and services. STATE 7 Driver Software Error SUGGESTED ACTION Contact your local service provider for technical support and services. STATE 8 Node Offline Due to Failure SUGGESTED ACTION The node identified in the alert is currently off-line due to a failure. If it is a recoverable failure, then the node will rejoin the system soon. Use the CLI command shownode to view the current state of the node.
STATE 13 CPU BTI Overheating SUGGESTED ACTION Informational, don't have to do anything. Watch for other CPU errors, if too many then replace the node. Monitor the systems, if too many other CPU errors that are not resolved by the system, then contact HP Support. STATE 14 CPU Dead SUGGESTED ACTION The CPU appears to not be alive. If the alert is not transient, a node replacement might be indicated and the HP Support should be contacted. If the alert is not resolved by the system, call HP Support.
STATE 19 CPU VRM Disabled SUGGESTED ACTION The voltage regulator module has been disabled. If the alert is not transient, call HP Support STATE 20 CPU VRM Missing SUGGESTED ACTION The voltage regulator module is not present. If the alert is not transient, contact HP Support. STATE 21 CPU VRM Power Fault SUGGESTED ACTION The voltage regulator module encountered a fault during power on. If the alert is not transient, contact HP Support.
Call HP Support. STATE 26 Node Fan Module 0 Under Limit SUGGESTED ACTION The specified node fan module's RPM is under limit. Replacement of the fan may be indicated, if the alert is not transient. Call HP Support. STATE 27 Node Fan Module 1 Failed SUGGESTED ACTION The specified node fan module has failed. If the issue isn't transient, call HP Support STATE 28 Node Fan Module 1 Power Fault SUGGESTED ACTION The specified node fan module has experienced a power fault.
Contact the HP Support.
MESSAGE CODE 0x01b00de TYPE Component State Change. MESSAGE Node Power Supply Degraded () STATE 1 Not Present SUGGESTED ACTION Contact your local service provider for technical support and services. STATE 2 Oscillating Presence SUGGESTED ACTION Contact your local service provider for technical support and services. STATE 3 Oscillating DC Failure SUGGESTED ACTION Contact your local service provider for technical support and services.
SUGGESTED ACTION Contact your local service provider for technical support and services. STATE 8 Disabled SUGGESTED ACTION Check the power supply switch. Pull the power supply out and put in to see if it enable again. NEMOE can't talk to the power supply using i2c interface. Call HP Support. STATE 9 I2C Failed SUGGESTED ACTION NEMOE can't talk to the power supply using i2c interface. Call HP Support. STATE 10 Switched Off SUGGESTED ACTION Check the power supply switch.
MESSAGE CODE 0x01b00fa TYPE Component State Change. MESSAGE Node Power Supply Failed () STATE 1 Invalid Battery Count SUGGESTED ACTION Replace power supply and battery. STATE 2 DC Failed SUGGESTED ACTION An event has occurred on your system which requires attention. Please contact your authorized support provider for assistance. STATE 3 AC Failed SUGGESTED ACTION An event has occurred on your system which requires attention.
STATE 7 Alert Asserted SUGGESTED ACTION No action needed STATE 8 Over Current SUGGESTED ACTION Check the power supply, if the warning does not go away, call HP Support. STATE 9 Over Temperature SUGGESTED ACTION Check the power supply, if the warning does not go away, call HP Support. STATE 10 Over Voltage SUGGESTED ACTION Check ps, if the warning does not go away, call HP Support. STATE 11 Under Voltage SUGGESTED ACTION Check the power supply, if the warning does not go away, call HP Support.
MESSAGE CODE 0x01e0001 TYPE Cage log event MESSAGE 1 cage, port , cage time . Internal parameters: . SUGGESTED ACTION An internal midplane hardware error has occurred. One or more communication channels have been disabled. Replace the midplane. Contact your authorized support provider for assistance if required. MESSAGE 2 Midplane FPGA_ IRQ rate too high: .
MESSAGE 6 Midplane FPGA_ POST Fail: . SUGGESTED ACTION An internal midplane hardware error has been detected. Two or more communication channels have been disabled. Replace the midplane. Contact your authorized support provider for assistance if required. MESSAGE 7 Firmware panic due to unknown CPU interrupt. Panic count is (). SUGGESTED ACTION Internal midplane hardware error. If you receive this alert, then cage completed self recovery.
Contact your authorized support provider for assistance if required. MESSAGE 12 Firmware panic due to PMC write failure. Panic count is (). SUGGESTED ACTION Internal midplane hardware error. If you receive this alert, then cage completed self recovery. Upgrade cage firmware. Contact your authorized support provider for assistance if required. MESSAGE 13 Firmware panic due to generic POST failure. Panic count is (). SUGGESTED ACTION Internal midplane hardware error.
MESSAGE 18 POST Ticker Init . SUGGESTED ACTION Internal midplane hardware error. Timer could not be initialized. Replace the midplane. Contact your authorized support provider for assistance if required. MESSAGE 19 POST Flash Init . SUGGESTED ACTION Internal midplane hardware error. Flash initialization failed. Replace the midplane. Contact your authorized support provider for assistance if required. MESSAGE 20 POST Event Log Init .
SUGGESTED ACTION Internal midplane hardware error. Communication with FPGA failed. Replace the midplane. Contact your authorized support provider for assistance if required. MESSAGE 25 POST Watchdog Init . SUGGESTED ACTION Internal midplane hardware error. CPU watchdog initialization failed. Replace the midplane. Contact your authorized support provider for assistance if required. MESSAGE 26 POST IRQ Enable . SUGGESTED ACTION Internal midplane hardware error.
MESSAGE 31 POST ADC Init . SUGGESTED ACTION Internal midplane hardware error. CPU voltage sampler initialization failed. Replace midplane. Contact your authorized support provider for assistance if required. MESSAGE 32 POST Poweron Hours Init . SUGGESTED ACTION Internal midplane hardware error. Midplane power on time could not be read. Replace midplane. Contact your authorized support provider for assistance if required. MESSAGE 33 POST Midplane Init .
SUGGESTED ACTION FCAL failed to initialize. Replace FCAL. Contact your authorized support provider for assistance if required. MESSAGE 38 POST FCAL EEPROM Test . SUGGESTED ACTION FCAL EEPROM failed during functional test. Replace FCAL. Contact your authorized support provider for assistance if required. MESSAGE 39 POST Power Supply Init . SUGGESTED ACTION The power supply failed to initialize during the power on self test. Replace the power supply.
MESSAGE 44 POST ESI Init . SUGGESTED ACTION Internal midplane hardware error. ESI channel failed to initialize. Replace midplane. Contact your authorized support provider for assistance if required. MESSAGE 45 POST PMC Alive Test . SUGGESTED ACTION Internal midplane hardware error. ESI channel failed to initialize. Replace midplane. Contact your authorized support provider for assistance if required. MESSAGE 46 POST PMC Loopback Test .
MESSAGE 50 POST Scheduler Init . SUGGESTED ACTION Internal midplane hardware error. Scheduler initialization failed. Reload cage firmware. If error persists, replace midplane. Contact your authorized support provider for assistance if required. MESSAGE 51 Midplane LM87 read failure SUGGESTED ACTION An internal midplane hardware error has occurred. Power cycle the cage. If the error persists, replace the midplane. Contact your authorized support provider for assistance if required.
is available, a separate message code (0x1e0005) will also be present. A cage firmware core dump can be analyzed by your service provider. Contact your authorized support provider for assistance if required. MESSAGE 56 Midplane FPGA_ ESI RX FIFO Fill failure: . SUGGESTED ACTION An internal midplane hardware error has occurred. Two or more communication channels have been disabled due to FIFO buffer issues. Hard reset the cage using the OS UI. If the error persists, replace the midplane.
MESSAGE 61 Midplane FPGA_ ESI TX FIFO Fill failure: . SUGGESTED ACTION An internal midplane hardware error has occurred. Two or more communication channels have been disabled due to FIFO buffer issues. Hard reset the cage using the OS UI. If the error persists, replace the midplane. Contact your authorized support provider for assistance if required. MESSAGE 62 Midplane FPGA_ ESI TX FIFO Loopback failure: .
MESSAGE CODE 0x01e0002 TYPE Invalid cage configuration MESSAGE 1 Cage (wwn 0x) is not directly attached to node on either loop MESSAGE 2 Cage (WWN ) is paired with different partners. SideA with and sideB with MESSAGE 3 Can’t tell cage order on port MESSAGE 4 More than 2 cages reported port MESSAGE 5 reported twice on port .
SUGGESTED ACTION FOR MESSAGE 1-10 Check all fibre channel cable connections. Contact your local service provider to reconfigure the drive cages.
MESSAGE CODE 0x01e0004 TYPE Critical ESI port count in cage MESSAGE 1 is connected but is down to one valid ESI port MESSAGE 2 is connected but has only one valid ESI port. MESSAGE 3 Lost communication to cage on all ESI ports. SUGGESTED ACTION FOR MESSAGE 1–3 Inspect the current cage hardware configuration and insert more ESI-capable magazines. NOTE: Messages 1 and 3 are logged when the system is coming up as well as when losing valid ESI ports.
MESSAGE CODE 0x01e0005 TYPE Firmware coredump event MESSAGE 1 Cage COREDUMP: retrieve failed: SUGGESTED ACTION An attempt to capture a cage firmware coredump failed. Review the associated error_message to determine why. Please contact your authorized support provider for assistance. MESSAGE 2 Cage COREDUMP: retrieve failed: - SUGGESTED ACTION An attempt to capture a cage firmware coredump failed.
MESSAGE CODE 0x01e0006 TYPE servicemag failed to dismiss PD: cage , mag , taskid , pd : error - MESSAGE servicemag failed to dismiss PD: cage , mag , taskid , pd : error - SUGGESTED ACTION Try to manually dismiss the PD. Please contact your authorized support provider for assistance.
MESSAGE CODE 0x01e00de TYPE Component State Change MESSAGE Cage Degraded STATE 1 Unsupported Cage Description Cage has an unrecognized model and firmware STATE 2 Unsupported Link Speed Description Cage is connected at an unsupported link speed. A cage loop is offline. STATE 3 Loop Offline Description A cage loop is offline.
STATE 7 Loops moved Description Not currently used. SUGGESTED ACTION FOR STATE 1–7 Contact your local service provider for technical support and services.
MESSAGE CODE 0x01e00fa TYPE Component State Change MESSAGE Cage Failed () STATE 1 Inaccessible Description Both ports of a loops to a cage are down. STATE 2 Firmware CPU Unknown Description The revision of firmware on the cage CPU is a revision unknown by the system. STATE 3 No ESI Port Description Communication with the cage has failed. STATE 4 Loop Map Fail STATE 5 Side 0 Inaccessible Description Side 0 of a split cage has both loops down.
Description The link speed of the FC loops connected to the cage has changed, this could be from 2G to 4G or vice versa. SUGGESTED ACTION FOR STATE 1-7 Loss of power to the cage or loss of access to all ESI disks will cause this. Contact your local service provider for technical support and services.
MESSAGE CODE 0x01f00de TYPE Component state change MESSAGE Disk Degraded () STATE 1 Errors on A Port SUGGESTED ACTION One of the possible errors leading to a disk being marked failed is a disk port reporting errors. Use the CLI command showpd to confirm the disk is still in this state. If both ports are reporting errors, then another alert is posted specifying No Valid Ports on that disk.
STATE 6 Missing SUGGESTED ACTION The PD specified in the alert has been missing on both ports. Use the CLI command showpd to confirm the disk is still in this state. This state might be temporary and might fix itself on retries. Contact your local service provider for technical support and services. STATE 7 Missing A Port SUGGESTED ACTION The PD specified in the alert has its A port missing. Use the CLI showpd to confirm it is still in this state.
SUGGESTED ACTION Port A is missing for over 20 minutes. Check if the PD port is missing by issuing CLI command showpd and showcage -d. If only one port is missing, the PD may need to be replaced. Contact your local service provider for technical support and services. STATE 12 Prolonged Missing B Port SUGGESTED ACTION Port B is missing for over 20 minutes. Check if the PD port is missing by issuing CLI command showpd and showcage -d. If only one port is missing, the PD may need to be replaced.
SUGGESTED ACTION The PD loop connection may have failed. No action required. STATE 19 Drive Error Bit Set SUGGESTED ACTION PD is experiencing errors. Further alerts will be issued as to the specific error the PD is experiencing. STATE 20 Sysmgr Bypassed SUGGESTED ACTION The Sysmgr has issued a command to bypass a PD. No action required. STATE 21 Port Bypassed SUGGESTED ACTION Indicates the PD is in service, check service command run to verify bypass.
STATE 26 Inquiry Failed SUGGESTED ACTION The PD specified in the alert has been marked failed because a SCSI inquiry to it failed. Use the CLI command showpd to confirm the disk is still in this state. A disk is marked failed because a SCSI inquiry to it failed to gather information about its serial number, device ID, vendor ID, etc. Generally this alert is auto-fixed when the SCSI inquiry is retried. Wait for a few minutes to see if the alert is auto-fixed.
STATE 31 Smart Threshold Exceeded SUGGESTED ACTION A disk might be marked media-failed if it has been reporting disk aborts with error code 21 to specify that the threshold for SMART errors has been exceeded. Contact your local service provider to replace the disk. A physical disk drive has failed and requires replacement. STATE 32 Multiple Chunklets Media Bad SUGGESTED ACTION A disk might be marked media-failed because more than six chunklets on that disk have reported media-errors.
STATE 36 Invalid connections SUGGESTED ACTION The drive is connected to the wrong node. Re-connect the cable to the owner node Please contact your authorized support provider for assistance. STATE 37 Miscompare SUGGESTED ACTION A physical disk drive has failed and requires replacement. STATE 38 Not Available For Allocations SUGGESTED ACTION Use setpd ldalloc on command Please contact your authorized support provider for assistance.
SUGGESTED ACTION The PD specified in the alert has been marked failed because it has been marked not ready for more than 20 minutes. Use the CLI command showpd to confirm the disk is still in this state. A physical disk drive has failed and requires replacement. STATE 43 Invalid Media SUGGESTED ACTION The PD specified in the alert has been marked media. Use the CLI command showpd to confirm the disk is still in this state.
MESSAGE CODE 0x01f00fa TYPE Component state change MESSAGE Disk Failed () STATE 1 Invalid SUGGESTED ACTION The PD specified in the alert has been marked failed. Use the CLI command showpd to confirm that the disk is still in this state. The PD can be marked Invalid because of a number of reasons. A reason code along with Invalid will give more information about why the PD was marked Invalid. Contact your local service provider for technical support and services.
A disk is marked failed if a SCSI inquiry to check its capacity fails. This error is also intermittent and might get fixed if the SCSI inquiry succeeds on a retry. As above, the suggested action is to wait for a few minutes for the retry to fix it. Contact your local service provider for technical support and services. STATE 5 Write Label Failed SUGGESTED ACTION The PD specified in the alert has been marked failed because the disk label could not be written to the disk.
STATE 10 Invalid Type SUGGESTED ACTION The PD specified in the alert has been marked failed because the vendor of the disk is not included in the list of supported vendors. Use the CLI command showpd to confirm the disk is still in this state. Contact your local service provider for technical support and services. STATE 11 Invalid Firmware SUGGESTED ACTION The PD specified in the alert has been marked failed because it has unsupported drive firmware installed.
SUGGESTED ACTION The PD specified in the alert has been marked failed because it has been marked missing for more than 20 minutes. Use the CLI command showpd to confirm the disk is still in this state. Contact your local service provider for technical support and services. STATE 16 Invalid Media SUGGESTED ACTION The PD specified in the alert has been marked media-failed. Use the CLI command showpd to confirm the disk is still in this state.
SUGGESTED ACTION A disk will be marked media-failed if there has been an increase of more than 20 in the error counts of the disk. Contact your local service provider for technical support and services. STATE 22 No Valid Ports SUGGESTED ACTION The PD specified in the alert has been failed because it has no valid ports. Use the CLI command showpd to confirm the disk is still in this state.
MESSAGE CODE 0x0200009 TYPE Internal error in authentication library MESSAGE Authentication internal error. Client address port SUGGESTED ACTION Contact your local service provider for technical support and services.
MESSAGE CODE 0x0210001 TYPE InForm GUI has lost connection to the event filter MESSAGE Binary data SUGGESTED ACTION Wait for the connection to be restored. If the connection is not restored, ensure that the network is functioning. If the network is functioning, Contact your local service provider with this information.
MESSAGE CODE 0x0220001 TYPE Battery expiration MESSAGE 1 Node PS Battery will expire in [Replace Battery soon] SUGGESTED ACTION 1. 2. 3. Check the system time. Check the battery expiration date. Contact your local service provider to schedule the battery replacement. MESSAGE 2 BBU expired: Replace SUGGESTED ACTION Call HP Support.
MESSAGE CODE 0x02200de TYPE Component state change MESSAGE 1 Degraded (list of states) SUGGESTED ACTION The battery in the specified power supply is showing a state of "not tested in 3 weeks" or the power supply is showing AC/DC fail. Inspect the battery, power supply, power source, AC power cord, power switch and PDU for issues. Replace if necessary.
SUGGESTED ACTION Issue the CLI command, showbattery, if failure state, replace the battery. STATE 6 Charging Fadiled SUGGESTED ACTION Issue the CLI command, showbattery, if failure state, replace the battery. STATE 7 DC Failed SUGGESTED ACTION Issue the CLI command,showbattery, if failure state, replace the battery. STATE 8 Fan Failed SUGGESTED ACTION Issue the CLI command shownodeenv to confirm status. Call HP Support. STATE 9 I2C Corrupt SUGGESTED ACTION Unable to monitor anything.
STATE 12 Initialization Failed SUGGESTED ACTION Will get failure status when the CLI command, showbatterystatus is issued. Unable to talk to power supply or battery. Call HP Support. Most likely need to replace either or both. STATE 13 Internal Error SUGGESTED ACTION Will get failure status when the CLI command, showbatterystatus is issued. Unable to talk to power supply or battery. Call HP Support. Most likely need to replace either or both.
STATE 18 Not Engaged SUGGESTED ACTION Issue the CLI command, showbatterystatus to monitor charging information. Call HP Support if it does not increase. STATE 19 Charger Failed SUGGESTED ACTION Call HP Customer support STATE 20 Not Present SUGGESTED ACTION Issue the CLI command, showbatterystatus. Check if BBU is present. If there, remove and reinsert BBU to see if that will fix it. If not there, call HP HP Support.
SUGGESTED ACTION Warning, charge too much. Battery state might become bad. Take a look to see if it needs replaced. Issue the CLI command, showbatterystatus to monitor battery state. If the problem persist, call HP Support. STATE 26 Over Voltage SUGGESTED ACTION Warning, charge too much. Battery state might become bad. Take a look to see if it needs replaced. Issue the CLI command, showbatterystatus to monitor battery state. If the problem persist, call HP Support.
MESSAGE CODE 0x02200fa TYPE Component state change MESSAGE Node Power Supply Battery Failed () STATE 1 Failed Test SUGGESTED ACTION BBU permanently failed. Call Customer Service. Replace BBU. STATE 2 Not Present SUGGESTED ACTION The specified Cage Power supply Fan is not available. Check the given power supply and determine the state of the fan. Contact your authorized support provider for assistance if required.
MESSAGE CODE 0x02e00de TYPE Component state change STATE 1 Not Available SUGGESTED ACTION The specified Cage Power supply Fan is not available. Check the given power supply and determine the state of the fan. Contact your authorized support provider for assistance if required. The specified Cage Power supply Fan is not available. Check the given power supply and determine the state of the fan. Replace if required. STATE 2 Not Present SUGGESTED ACTION Replace the battery.
MESSAGE CODE 0x02e00fa TYPE Component state change STATE 1 Failed SUGGESTED ACTION The specified Cage Power supply Fan has failed. Check the given power supply and determine the state of the fan. Contact your authorized support provider for assistance if required. STATE 2 Warning SUGGESTED ACTION The specified Cage Power supply Fan is indicating a warning. Check the given power supply and determine the state of the fan. Contact your authorized support provider for assistance if required.
MESSAGE CODE 0x02f00fa TYPE Component state change STATE 1 Over Failure Threshold STATE 2 Over Warning Threshold STATE 3 Under Failure Threshold STATE 4 Under Warning Threshold SUGGESTED ACTION FOR STATUE 1–4 The Temperature of the specified Cage has reached the high temperature threshold. Check for fan failure and ventilation obstructions. Ensure that all drive blanks are in place. Check environmental conditions. Contact your authorized support provider for assistance if required.
MESSAGE CODE 0x0230003 TYPE Port shutdown on fatal error MESSAGE Port shut down: SUGGESTED ACTION Ensure the port settings are correct for the type of connection. For example, if the port is connected to a fabric switch or hub, the port persona should be one of the fabric connection types (7,8,9):controlport persona 7 n:s:p NOTE: This will reset the port. If the port continues to generate firmware cores, it will shut down again and the alert reposted. 1. 2. 3.
MESSAGE CODE 0x0230004 TYPE Host port is down MESSAGE Host port (::) is down () SUGGESTED ACTION The host port identified in the message is down. It is possible that the host went off-line, or that a cable has been unplugged. If required, contact your local service provider for further assistance.
MESSAGE CODE 0x0230005 TYPE All ports in the same FC card must be configured for RCFC MESSAGE Port () is used for disk or host SUGGESTED ACTION Configure all the ports in the same FC card for RCFC or leave them free.
MESSAGE CODE 0x0240001 TYPE Internodal Serial Port Error MESSAGE Node Serial Port Error: (<0xerror_number>) SUGGESTED ACTION If a node's internal serial port is not working, then the node is running with a system failure. The node will continue to run properly, but should be replaced before a second failure occurs. Contact your local service provider for technical support and services.
MESSAGE CODE 0x0250002 TYPE Remote Copy link status MESSAGE The Remote Copy link has changed its status to SUGGESTED ACTION The remote copy link has been disconnected. This could be the result of a CLI command (any command that stops a link), or it could be the result of an actual network failure or loss of the remote system. In the latter case, the customer should attempt to determine what caused the network failure and attempt to correct the situation.
MESSAGE CODE 0x0260001 TYPE Ethernet Monitor Event MESSAGE Node eth Ethernet device error detected State There is some problem with the IP network as specified by the type of error. SUGGESTED ACTION Check your network switches and cables for any problem. Contact your local service provider for technical support and services.
MESSAGE CODE 0x0270001 TYPE TP VV allocation size warning MESSAGE Thin provisioned VV has reached allocation of G(% of G) SUGGESTED ACTION The logical capacity in use by the named Thin Provisioned Virtual Volume (TPVV) is above the configured allocation warning. In the event the allocation limit is reached, new writes on the named TPVV will result in write failures.
MESSAGE CODE 0x0270002 TYPE TP VV allocation size limit MESSAGE Thin provisioned VV has reached allocation of G(% of G) SUGGESTED ACTION The logical capacity in use by the named TPVV is above the configured allocation limit. New writes on the named TPVV will result in write failures. To allow the named TPVV to continue to grow, reset its ‘Allocation Limit’ to a higher percentage of its exported virtual size.
MESSAGE CODE 0x0270003 TYPE Snapshot space allocation size warning MESSAGE Snapshot space for VV has reached allocation of G(% of G) SUGGESTED ACTION The logical capacity in use by the Snapshot space for named VV is above the configured allocation warning limit. Once the allocation limit is reached, any subsequent operation to create new snapshots of the named VV will fail.
MESSAGE CODE 0x0270004 TYPE Snapshot space allocation size limit MESSAGE Snapshot space for VV has reached allocation of G(% of G) SUGGESTED ACTION The logical capacity in use by the Snapshot space for a named VV is above the configured allocation limit. Any subsequent operation to create new snapshots of the named VV will fail. To allow the Snapshot space for the named VV to continue to auto-grow, reset its ‘Allocation Limit’ to a greater value.
MESSAGE CODE 0x0270005 TYPE CPG growth warning MESSAGE 1 CPG space has reached allocation of G. SUGGESTED ACTION The logical capacity reserved and in use by the named Common Provisioning Group (CPG) is above the configured allocation warning. If the named CPG reaches its allocation limit and all of its reserved space is in use, new writes on TPVVs and/or Snapshot Volumes mapped to this CPG will result in write failures.
MESSAGE CODE 0x0270006 TYPE CPG growth limit MESSAGE 1 CPG has reached allocation of G. SUGGESTED ACTION The logical capacity reserved and in use by the named CPG is above the configured allocation limit. New writes on TPVVs and/or Snapshot Volumes mapped to this CPG will result in write failures. To allow the named CPG to continue to auto-grow the logical capacity, reset its ‘Allocation Limit’ to a higher number.
MESSAGE CODE 0x0270007 TYPE TP VV allocation failure MESSAGE 1 Thin provisioned VV unable to allocate SA space from CPG SUGGESTED ACTION There is no more available LD space (either SA or SD as specified in the alert text) in the CPG. For further information on TPGs and CPGs see the OS Concepts Guide.
MESSAGE CODE 0x0270008 TYPE Snapshot space allocation failure MESSAGE 1 Snapshot space for VV unable to allocate SA space from CPG SUGGESTED ACTION There is no more available LD space (either SA or SD as specified in the alert text) in the CPG. For further information on TPGs and CPGs see the OS Concepts Guide.
MESSAGE CODE 0x0270009 TYPE CPG growth failure MESSAGE 1 CPG space grow command: createald -args-params Failed with: SUGGESTED ACTION The specific LD creation command and failure text must be examined to determine the corrective action. This might include replacing failed hardware or adding additional storage. Contact your local service provider for technical support and services for further assistance.
MESSAGE CODE 0x027000e TYPE FC raw space allocation 50% alert MESSAGE Total FC raw space usage at XX G (above 50% of total XXXG) SUGGESTED ACTION The system has used over 50% of the raw, physical space. Available physical space required for auto-growth of logical capacity by CPGs with default LD characteristics may be at risk. Recommend addition of physical capacity. Contact your local service provider for technical support and services to order capacity upgrade.
MESSAGE CODE 0x027000f TYPE FC raw space allocation 75% alert MESSAGE Total FC raw space usage at YY G (above 75% of total XXXG) SUGGESTED ACTION The system has used over 75% of the raw, physical space. It is likely that available physical space required for auto-growth of logical capacity of CPGs with default LD characteristics may be at risk. It is strongly recommended to add physical capacity. If, available space runs out, new writes on all virtual volumes will result in write failures.
MESSAGE CODE 0x0270010 TYPE FC raw space allocation 85% alert MESSAGE Total FC raw space usage at ZZ G (above 85% of total XXXG) SUGGESTED ACTION The system has used over 85% of the raw, physical space. Available physical space required for auto-growth of logical capacity by CPGs with default LD characteristics may be at risk. It is critical that physical capacity be added ASAP. If there is no remaining available physical space, new writes on all virtual volumes will result in write failures.
MESSAGE CODE 0x0270011 TYPE FC raw space allocation 95% alert MESSAGE Total raw space usage at G(above <95>% of totalG) SUGGESTED ACTION The system has used 95% of the raw, physical space. New writes on all virtual volumes will result in write failures. Contact your local service provider for technical support and services. NOTE: Raw space usage indicated by this alert may not apply to available physical space required for CPG auto-LD creation for CPGs with customized LD characteristics.
MESSAGE CODE 0x0270012 TYPE CPG space allocation warning percentage status MESSAGE 1 CPG % used (G used out of G total) SUGGESTED ACTION The CPG specified in the message has reached its warning percentage threshold for space in use. This limit threshold was previously specified by the user, using the (deprecated) options createc[g -aw or setcpg -aw.
MESSAGE CODE 0x0270013 TYPE Raw space allocation user configured alert MESSAGE Total available raw space has reached threshold of (remaining out of) total) SUGGESTED ACTION Raise the threshold using setsys rawspacealert .
MESSAGE CODE 0x0270014 TYPE NL raw space allocation 50% alert MESSAGE Total NL raw space usage at XX G (above 50% of total XXXG) SUGGESTED ACTION The system has used over 50% of the raw, physical space. Available physical space required for auto-growth of logical capacity by CPGs with default LD characteristics may be at risk. Recommend addition of physical capacity. Contact your local service provider for technical support and services to order capacity upgrade.
MESSAGE CODE 0x0270015 TYPE NL raw space allocation 75% alert MESSAGE Total NL raw space usage at YY G (above 75% of total XXXG) SUGGESTED ACTION The system has used over 75% of the raw, physical space. It is likely that available physical space required for auto-growth of logical capacity of CPGs with default LD characteristics may be at risk. It is strongly recommended to add physical capacity. If, available space runs out, new writes on all virtual volumes will result in write failures.
MESSAGE CODE 0x0270016 TYPE NL raw space allocation 85% alert MESSAGE Total NL raw space usage at ZZ G (above 85% of total XXXG) SUGGESTED ACTION The system has used over 85% of the raw, physical space. Available physical space required for auto-growth of logical capacity by CPGs with default LD characteristics may be at risk. It is critical that physical capacity be added ASAP. If there is no remaining available physical space, new writes on all virtual volumes will result in write failures.
MESSAGE CODE 0x0270017 TYPE NL raw space allocation 95% alert MESSAGE Total raw space usage at G (above <95>% of total G) SUGGESTED ACTION The system has used 95% of the raw, physical space. New writes on all virtual volumes will result in write failures. Contact your local service provider for technical support and services. NOTE: Raw space usage indicated by this alert may not apply to available physical space required for CPG auto-LD creation for CPGs with customized LD characteristics.
MESSAGE CODE 0x0270018 TYPE CPG was grown with degraded parameters MESSAGE CPG () could not grow with its normal grow parameters. The following parameters were used: SUGGESTED ACTION The CPG cannot be grown using its grow parameters, therefore, new space is allocated using degraded grow parameters. For example, if availability is set to "cage" and enough space is not available to grow using cage availability, then the system will try to grow using "mag" availability.
MESSAGE CODE 0x0270050 TYPE CPG space used status MESSAGE CPG space has reached allocation of SUGGESTED ACTION The CPG identified in the message has reached its allocation limit or warning level. This threshold was previously specified by the user. Contact your local service provider for technical support and services.
MESSAGE CODE 0x0280001 TYPE Preserved data LDs configuration MESSAGE 1 Preserved data LDs have not been configured. SUGGESTED ACTION No LDs have been configured on this system to handle preserved data. Contact your local service provider for technical support and services. MESSAGE 2 Preserved data LDs have not been started up. SUGGESTED ACTION The preserved data LDs on this system have not been initialized correctly. Contact your local service provider for technical support and services.
MESSAGE CODE 0x0280002 TYPE Preserved data LDs status MESSAGE Preserved data storage is currently unavailable. SUGGESTED ACTION The preserved data LDs on this system are not currently available. Most likely, this is caused by some missing PDs or because some nodes are not a part of the cluster at this time. Check for this using showld to see if all the preserved data LDs are in the started state. Contact your local service provider for technical support and services.
MESSAGE CODE 0x02900de TYPE Component State Change MESSAGE Cage Interface Card SFP Degraded () STATE 1 Unqualified SUGGESTED ACTION Confirm by using the CLI command showcage -sfp. The SFP being used may not be certified. Contact your local service provider for technical support and services. STATE 2 Receiver Power Low: Check FC Cable SUGGESTED ACTION The FCAL is receiving a low signal.
MESSAGE CODE 0x02a00de TYPE Component state change (degraded) MESSAGE Node System Fan (x) Degraded STATE 1 I2C Failed SUGGESTED ACTION Replace the failed node fan module. STATE 2 DC Failed SUGGESTED ACTION Replace the failed node fan module.
MESSAGE CODE 0x02a00fa TYPE Component state change (failed) MESSAGE Node System Fan (x) Failed STATE 1 I2C Failed SUGGESTED ACTION Replace the failed node fan module. STATE 2 DC Failed SUGGESTED ACTION Replace the failed node fan module.
MESSAGE CODE 0x02b00de TYPE Component State Change MESSAGE Cage Power Supply Degraded () STATE Power Supply Off SUGGESTED ACTION Switch the power supply on. If the power supply is switched off due to a failure, determine the problem by running showcage -d. Replace the power supply if the problem persists.
MESSAGE CODE 0x02b00fa TYPE Component State Change MESSAGE Cage Power Supply Failed () STATE 1 Power Supply Failed SUGGESTED ACTION The cage power supply identified may need replacement. Contact your local service provider for technical support and services. STATE 2 Power Supply Warning SUGGESTED ACTION The cage power supply identified may need replacement. Contact your local service provider for technical support and services.
SUGGESTED ACTION Check the fan and clear any obstruction. The cage power supply identified may need replacement. Contact your local service provider for technical support and services. STATE 7 Power Supply Fan Warning SUGGESTED ACTION The cage power supply identified may need replacement. Contact your local service provider for technical support and services. STATE 8 Power Supply Fan Not Present SUGGESTED ACTION The cage power supply identified may need replacement.
MESSAGE CODE 0x02d00de TYPE Component state change MESSAGE Cage FCAL Module Degraded () STATE 1 Interface Card Loop Down Recovery SUGGESTED ACTION Contact your local service provider for technical support and services. STATE 2 CPU Firmware A Not Current SUGGESTED ACTION The cage firmware is not the latest version that we support. Use CLI command showcage -d to confirm the firmware version is not current.
SUGGESTED ACTION Use CLI command showcage and showpd to confirm condition. Contact your local service provider for technical support and services. STATE 7 CPU Firmware B Unknown SUGGESTED ACTION Use CLI command showcage and showpd to confirm condition. Contact your local service provider for technical support and services.
MESSAGE CODE 0x02d00fa TYPE Component state change MESSAGE Cage Interface Card Failed () STATE 1 Interface Card Failed STATE 2 Interface Card Warning STATE 3 Interface Card Unrecoverable STATE 4 Interface Card Not Present STATE 5 Interface Card-- STATE 6 Interface Card Not Available STATE 7 ESH Failed STATE 8 ESH Warning STATE 9 ESH Unrecoverable STATE 10 ESH Not_Present STATE 11 ESH Unknown STATE 12 ESH Not Available 268 Alerts
STATE 13 ESH ASIC Clock Delta Beyond Thresholds STATE 14 ESH ASIC Failed POST STATE 15 ESH ASIC Not Functioning STATE 16 ESH ASIC Port Failed POST STATE 17 ESH Microcontroller Encountered FATAL Error SUGGESTED ACTION FOR STATE 1–17 Contact your local service provider for technical support and services.
MESSAGE CODE 0x03100de/fa TYPE Component state change STATE 1 Failed STATE 2 Not_Available STATE 3 Not_Present STATE 4 Unrecoverable STATE 5 Warning SUGGESTED ACTION FOR STATE 1–7 The specified Cage's LCD display has failed, unavailable, does not appear to be present, or encountered an unrecoverable condition or warning condition. Contact your authorized support provider for assistance.
MESSAGE CODE 0x03400fa TYPE Component state change STATE 1 ASIC Clock Delta Beyond Thresholds Contact your authorized support provider for assistance. STATE 2 ASIC Failed POST STATE 3 ASIC Not Functioning STATE 4 ASIC Port Failed POST STATE 5 Microcontroller Encountered FATAL Error STATE 6 Microcontroller Failed POST STATE 7 Not Available SUGGESTED ACTION FOR STATE 1–5 The specified node has encountered a hardware failure.
MESSAGE CODE 0x03500de TYPE Component state change MESSAGE Cage Magazine Degraded () STATE 1 Missing, No Admitted Disks SUGGESTED ACTION A drive mag exists in the system without any disks. Use CLI command showcage -d to verify absent disks. Add disks to the magazine. STATE 2 I2C Transaction Failure SUGGESTED ACTION Contact your local service provider for technical support and services.
MESSAGE CODE 0x03500fa TYPE Component State Change MESSAGE Cage Magazine Failed () STATE 1 Missing SUGGESTED ACTION A drive mag is missing from the cage. Check if the drive mag is properly inserted into the cage. STATE 2 Offloop, Loop Failure SUGGESTED ACTION Use CLI commandshowcage -d to confirm the drive mag loop is failing. Check if the drive mag is properly inserted into the cage. Use CLI command showpd -degraded and showpd -failed to verify disk failure.
MESSAGE CODE 0x0360002 TYPE Write Cache Availability MESSAGE System write cache availability is degraded. SUGGESTED ACTION 1. 2. 3. 274 Alerts Ensure all nodes are functioning correctly. Use CLI commands such as shownode, shownode -s, and checkhealth to check status. Ensure all nodes have battery modules installed and they function. Use CLI commands, such as showbattery, showbattery -s, showbattery -d, and showbattery -log to check status. Contact HP Support.
MESSAGE CODE 0x03700de TYPE Component state change MESSAGE Remote Copy Volume Degraded () STATE 1 Resync Snapshot Became Stale - full sync required SUGGESTED ACTION Indicates that a remote copy snapshot went stale and was deleted and the next synchronization will have to be a full synchronization. Determine what caused the snapshot to go stale and possibly grow snapshot space for the base volume.
STATE 6 Volume Unsynced - promote of snapshot failed SUGGESTED ACTION Indicates that some volumes are no longer in sync because promote of snapshot failed. Determine why this is and resolve the situation, then perform a resynchronization. STATE 7 Volume Unsynced - could not take snapshot during sysmgr startup SUGGESTED ACTION Indicates that some volumes are no longer in sync because could not take snapshot during sysmgr startup.
MESSAGE CODE 0x03700fa TYPE Component state change MESSAGE Remote Copy Volume Failed () STATE 1 Write To Secondary Volume Failed SUGGESTED ACTION This message means that there was an error attempting to write to a secondary volume, and thus the primary side volume group was stopped. Determine what caused the write error was and attempt to repair the problem and restart the group.
MESSAGE CODE 0x03800de TYPE Component state change MESSAGE Remote Copy Volume Group Degraded () STATE 1 Sync Failed - could not take local snapshots SUGGESTED ACTION Check to ensure that all volumes in the group can have local snapshots taken, i.e. they have used snapshot space and are not experiencing some other error that would prevent snapshots.
STATE 7 Sync Failed - could not take remote snapshots SUGGESTED ACTION Check to ensure that all volumes in the group can have remote snapshots taken, i.e. they have used snapshot space and are not experiencing some other error that would prevent snapshots. STATE 8 Sync Failed - could not communicate with target SUGGESTED ACTION Check to ensure that the target is up and running, then retry the command.
MESSAGE CODE 0x03900fa TYPE Component state change MESSAGE Remote Copy Target Degraded () STATE 1 Target At Incompatible Revision SUGGESTED ACTION The primary and secondary systems do not have the same software versions. They should be updated to the same level or compatible levels. STATE 2 All Links To Target Are Down SUGGESTED ACTION Determine the reason the connectivity was lost and correct the problem.
STATE 7 Multiple targets defined for one remote system, the target get disabled. Please remove the target. SUGGESTED ACTION The user has created an extra target which is not supported. Please remove the target. STATE 8 Multiple targets with groups created that point to the same remote system is not a supported configuration.Please check the system and remove one target. SUGGESTED ACTION The user has created an extra target which is not supported. Please remove the target.
MESSAGE CODE 0x03a00de TYPE Component state change MESSAGE Remote Copy Link Degraded () STATE Not All Connections Are Up SUGGESTED ACTION This may be caused by the inability of RCFC to open the required number of socket connections. The remedial step is to reset the link on both the endpoints, which may or may not fix the problem.
MESSAGE CODE 0x03a00fa TYPE Component state change MESSAGE Remote Copy Link Failed () STATE 1 Down Due To Send Error Or Missing Heartbeat SUGGESTED ACTION The remote copy link has been disconnected. This could be the result of a CLI command (any command that stops a link) or it could be the result of an actual network failure or loss of the remote system.
SUGGESTED ACTION Replace internal drive as soon as possible. A controller node in your system has reported a problem and may require replacement. MESSAGE 4 execute Test failed: disk test failed: SUGGESTED ACTION Replace internal drive as soon as possible. A controller node in your system has reported a problem and may require replacement. MESSAGE 5 failed self-check: disk failed SMART self-check SUGGESTED ACTION Replace internal drive as soon as possible.
MESSAGE 11 SMART Failure: disk SMART Failure: SUGGESTED ACTION Replace internal drive as soon as possible. A controller node in your system has reported a problem and may require replacement. MESSAGE 12 uncorrectable sectors: disk has uncorrectable sectors SUGGESTED ACTION Replace internal drive as soon as possible. A controller node in your system has reported a problem and may require replacement.
MESSAGE CODE 0x03b0002 TYPE Free node disk space MESSAGE 1 Node free disk space: root MB altroot <MB> common <MB> MESSAGE 2 Node free disk space: root MB altroot <MB> common MESSAGE 3 Node free disk space: root MB altroot common <MB> MESSAGE 4 Node free disk space: root MB altroot common SUGGESTED
MESSAGE CODE 0x0450001 TYPE Data Cache DIMM CECC Monitoring MESSAGE Node Data Cache : Correctable ECC limit exceeded STATE 1 New SUGGESTED ACTION Contact your local service provider to have the DIMM replaced as soon as possible.
MESSAGE CODE 0x0450002 TYPE Patrol Data Cache DIMM UERR MESSAGE Node Data Cache : Uncorrectable error SUGGESTED ACTION Replace the DIMM specified in the alert.
MESSAGE CODE 0x0460001 TYPE Control Cache DIMM Temperature MESSAGE Node : ( C) SUGGESTED ACTION Temperature of the DIMM has reached the threshold maximum. Check for fan/PCM ventilation obstructions. Contact your authorized support provider for assistance if required.
MESSAGE CODE 0x04c00fa TYPE Component state change STATE 1 Failed SUGGESTED ACTION The AC power in the specified Cage Power Supply is showing a failed state. Inspect the power supply, power source, AC power cord, power switch and PDU for issues. Replace if necessary. Contact your authorized support provider for assistance. STATE 2 Not Current SUGGESTED ACTION The specified drive cage is reporting old firmware. Upgrade the cage firmware using the supported procedure.
9 Troubleshooting The OS CLI checkhealth command checks and displays the status of storage system hardware and software components. For example, the checkhealth command can check for unresolved system alerts, display issues with hardware components or display information about virtual volumes that are not optimal. By default the checkhealth command checks most storage system components, but you can also check the status of specific components.
Checking snmp Checking task Checking vlun Checking vv Component -----------Description----------- Qty Alert New alerts 4 Date Date is not the same on all nodes 1 LD LDs not mapped to a volume 2 License Golden License.
Table 48 Component Functions Component Function Alert Displays any unresolved alerts. Cage Displays drive cage conditions that are not optimal. Date Displays if nodes have different dates. LD Displays LDs that are not optimal. License Displays license violations. Network Displays Ethernet issues. Node Displays node conditions that are not optimal. PD Displays PDs with states or conditions that are not optimal. Port Displays port connection issues. RC Displays Remote Copy issues.
• power supplies • cage firmware (is not current) Reports if a servicecage operation has been started and has not ended.
Firmware_status Current Product_Rev 2.37 State Normal Op Loop_Split 0 VendorId,ProductId 3PARdata,DC4 Unique_ID 1062030000098E00 ...
Link A RXLEDs Green Off Link A TXLEDs Green Off Link B RXLEDs Off Green Link B TXLEDs Off Green LED(Loop_Split) Off Off LEDS(system,hotplug) Amber,Off Amber,Off -----------Midplane Info----------Firmware_status Current Product_Rev 2.
20 21 22 23 1:0:0 1:0:1 1:0:2 1:0:3 FC FC FC FC degraded degraded degraded degraded disabled_B_port,servicing disabled_B_port,servicing disabled_B_port,servicing disabled_B_port,servicing cli% showpd -p -cg 1 Id 20 21 22 23 CagePos 1:0:0 1:0:1 1:0:2 1:0:3 Type Speed(K) State FC 10 degraded FC 10 degraded FC 10 degraded FC 10 degraded ---Size(MB)---Total Free 139520 119808 139520 122112 139520 119552 139520 122368 ----Ports---A B 0:0:2* 1:0:20:0:2* 1:0:20:0:2* 1:0:20:0:2* 1:0:2- Cage Example 4 SCom
Cage Suggested Action 5 In this example, a 2Gb/sec SFP was installed in a 4Gb/sec drive cage (DC4), and the 2Gb SFP is not qualified for use in this drive cage. For cage problems, the following CLI commands are helpful: showcage -d, showcage -sfp, showcage -sfp -ddm, showcage -sfp -d, and showpd -state. cli% showcage -d cage4 Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 4 cage4 2:2:1 0 3:2:1 0 8 30-37 2.37 2.
DDM Support : Yes Note for DC3 Cages If an SFP is installed in a DC3 FCAL-Module but it is not connected, the port will have a state of Bypass, Rx_Loss (or loss_sync) and showcage-d output indicates the Cage_State as being Degraded. The IMC (GUI) also indicates a degraded condition for the drive cage and interface card. This is not truly an error condition as long as the cage has two good paths to two different nodes. This condition is not currently detected by checkhealth.
Date Suggested Action The time on the nodes should stay synchronized whether there is an NTP server or not. Use showdate to see if a node is out of sync, and shownet and shownet -d to see the network and NTP information. cli% Node 0 1 showdate Date 2010-09-08 10:56:41 PDT (America/Los_Angeles) 2010-09-08 10:56:39 PDT (America/Los_Angeles) cli% shownet IP Address Netmask/PrefixLen 192.168.56.209 255.255.255.0 Duplex AutoNeg Status Full Yes Active Nodes 0123 Active Speed 0 100 Default route: 192.168.56.
LDs are normally mapped to (used by) VVs but they can be disassociated with a VV if a VV is deleted without the underlying LDs being deleted, or by an aborted tune operation. Normally, you would remove the unmapped LD to return its chunklets to the free pool. cli% showld Ten.usr.0 Id Name RAID -Detailed_State- Own MapV 88 Ten.usr.0 N 0 normal 0/1/2/3 SizeMB UsedMB Use Lgct LgId WThru 8704 0 V 0 --- N cli% showldmap Ten.usr.
Component --Identifier-- ------------Description--------------LD ld:R1.usr.0 LD has reduced availability. Current: ch, Configured: cage LD Suggested Action 3 LDs are created with certain high-availability characteristics, such as ha-cage. If chunklets in an LD get moved to locations where the Current Availability (CAvail) is not at least as good as the desired level of Availability (Avail), this condition will be reported.
License Displays license violations. Returns information if a license is temporary, and if it has expired. Format of Possible License Exception Messages License "License is enabled on a trial basis" License "License has expired" License Example Component -Identifier- --------Description------------License -System Tuner License has expired License Suggested Action If desired, request a new/updated license from your Sales Engineer.
NOTE: These error counters cannot be cleared except by rebooting a controller node. shownet -d IP Address: 192.168.56.209 Assigned to nodes: 0123 Connected through node 0 Status: Active Netmask 255.255.255.
Node Suggested Action 1 Examine the states of the power supplies with commands such as shownode, shownode -s, shownode -ps, etc. Turn on or replace the failed power supply. NOTE: In the example below, the battery state is considered Degraded because the power supply is Failed; this is normal.
3 3 0 1 0 100A300B OK 0 12345310 Failed 100 07/01/2011 No 0 04/07/2011 No No No Node Example 3 Component -Identifier- --------------Description---------------Node node:3 Node:3, Power Supply:1, Battery:0 has not been tested within the last 30 days Node Suggested Action 3 The indicated battery has not been tested in the past 30 days. A node backup battery will be tested every 14 days under normal conditions, but if a battery is missing, expired, or failed, it will not be tested.
PD disk: "Disk is experiencing a high level of I/O per second: " PD -- There is at least one active servicemag operation in progress PD Example 1 Component -------------------Description------------------- Qty PD PDs that are degraded or failed 40 Component PD PD ...
0:0 20000014c3b3eab9 Green 0:1 20000014c3b3e708 Green 34 0xe1 36 0xe0 OK 0xe1 Loop fail OK 0xe0 Loop fail PD Example 2 Component --Identifier-- --------------Description--------------PD -There is an imbalance of active pd ports PD Suggested Action 2 The primary and secondary I/O paths for disks (PD's) are balanced between nodes. The primary path is indicated in the showpd -path output and by an asterisk in the showpd output.
Interface Board Info FCAL0 FCAL1 Link A RXLEDs Green Off Link A TXLEDs Green Off Link B RXLEDs Off Off Link B TXLEDs Off Green LED(Loop_Split) Off Off LEDS(system,hotplug) Green,Off Green,Off ...
the state of the disk using CLI commands such as showpd -s, showpd -i, and showfirmwaredb. cli% showpd -s 3 Id CagePos Type -State-- -Detailed_State3 0:4:0 FC degraded old_firmware cli% showpd -i 3 Id CagePos State ----Node_WWN---- --MFR-- ---Model--- -Serial- -FW_Rev3 0:4:0 degraded 200000186242DB35 SEAGATE ST3146356FC 3QN0290H XRHJ cli% showfirmwaredb Vendor Prod_rev ... SEAGATE [XRHK] Dev_Id Fw_status Cage_type ST3146356FC Current DC2.DC3.
Port Port Port Port port: port: port: port: "SFP is disabled" "Receiver Power Low: Check FC Cable" "Transmit Power Low" "SFP has TX fault" Port Suggested Actions, General Some specific examples are displayed below, but in general, use the following CLI commands to check for these conditions: • For port SFP errors, use commands such as showport, showport -sfp,showport -sfp -ddm, showcage, showcage -sfp, and showcage -sfp -ddm.
Voltage TX Bias TX Power RX Power mV mA uW uW 3216 7 335 98 2900 2 79 15 3700 14 631 794 2700 1 67 10 3900 17 631 1259 cli% showcage Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 0 cage0 0:0:1 0 1:0:1 0 15 33-38 08 08 DC3 n/a 1 cage1 --0 1:0:2 0 15 30-38 08 08 DC3 n/a cli% showpd Id CagePos 1 0:2:0 ... 13 1:1:0 14 1:2:0 -s Type -State-- -Detailed_StateFC normal normal NL FC degraded missing_A_port degraded missing_A_port cli% showpd -path Id 1 ...
Port Suggested Action 3 A node-port SFP will be disabled if the port has been placed offline using the controlport offline command. Also see Example 4. cli% showport N:S:P -State3:5:1 OK 3:5:2 OK -sfp -Manufacturer- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM FINISAR_CORP. 4.1 Yes No No Yes FINISAR_CORP. 4.
cli% showport N:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type 0:1:1 initiator ready 2FF70002AC000190 20110002AC000190 rcfc 0:1:2 initiator loss_sync 2FF70002AC000190 20120002AC000190 free 0:1:3 initiator loss_sync 2FF70002AC000190 20130002AC000190 free 0:1:4 initiator loss_sync 2FF70002AC000190 20140002AC000190 free RC Displays Remote Copy issues.
SNMP Suggested Action Any error message that can be produced by showsnmpmgr may be displayed. SP Checks the status of the Ethernet connection between the Service Processor (SP) and nodes. This can only be run from the SP because it performs a short Ethernet transfer check between the SP and the storage system.
manually removed with the IMC (GUI) or CLI with removealert or setalert ack. To display system-initiated tasks, use showtask -all. cli% showtask -d 6313 Id Type Name Status Phase Step 6313 background_command upgradecage -a -f failed --- --- Detailed status is as follows: 2010-10-22 10:35:36 PDT Created 2010-10-22 10:35:36 PDT Updated 2010-10-22 10:35:36 PDT Errored task.
VV Displays Virtual Volumes (VV) that are not optimal. Checks for VVs and Common Provisioning Groups (CPG) whose state is not normal.
10 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 (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
