3PAR InForm® OS 2.3.1 Messages and Operator's Guide (320-200181 Rev B, February 2010)

ManualsBrandsHP ManualsStorageHP 3PAR F200 Field Starter Kit

3PAR InForm

OS 2.3.1

Messages and Operator’s Guide

3PAR Inc.

4209 Technology Drive

Fremont, CA 94538 USA

Part No. 320-200181 Rev B

February 2010

Summary of content (420 pages)

PAGE 1
3PAR InForm® OS 2.3.1 Messages and Operator’s Guide 3PAR Inc. 4209 Technology Drive Fremont, CA 94538 USA Part No.
PAGE 2
Revision Notice This is the second release of this manual. A complete revision history is provided at the end of this manual. Changes The material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, 3PAR Inc. assumes no liability resulting from errors or omissions in this document or from the use of the information contained herein.
PAGE 3
Japanese Compliance Statement This is a Class A product based on the standard of the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may arise. When such trouble occurs, the user may be required to take corrective actions. European Compliance Statement: This product complies with CENELEC EN55022 Class A and EN55024:1998/A1:2001 specifications for Information Technology Equipment (ITE).
PAGE 4
PAGE 5
InForm OS Version 2.3.1 Messages and Operator’s Guide Table of Contents 1 Introduction 1.1 Audience 1.2 1.2 Related Documents 1.2 1.3 Organization 1.3 1.4 Typographical Conventions 1.4 1.5 Advisories 1.5 2 Numbering System and Component Locations for S-Class Servers 2.1 Identifying Storage Server Components 2.1 2.2 Understanding Component Numbering 2.3 2.2.1 Cabinet Numbering 2.3 2.2.2 PDU Numbering 2.5 2.2.3 Drive Cage Numbering 2.6 2.2.4 Controller Node Numbering 2.10 2.2.
PAGE 6
Messages and Operator’s Guide InForm OS Version 2.3.1 3.3.1 Cabinet Numbering 3.5 3.3.2 PDU Numbering 3.7 3.3.3 Battery Backup Unit Numbering 3.9 3.3.4 Controller Node Numbering 3.11 3.3.5 Drive Chassis Numbering 3.15 3.3.6 Power Supply Numbering 3.20 4 Numbering System and Component Locations for E-Class Servers 4.1 Identifying Storage Server Components 4.2 4.2 Service Processor Placement 4.4 4.3 Understanding Component Numbering 4.4 4.3.1 Cabinet Numbering 4.4 4.3.
PAGE 7
InForm OS Version 2.3.1 Messages and Operator’s Guide 6.1.5 Gigabit Ethernet Adapter LEDs 6.24 6.1.6 QLogic iSCSI Port LEDs 6.25 6.1.7 Power Supply LEDs 6.26 6.1.8 Battery Backup Unit LEDs 6.28 6.1.9 Power Distribution Unit Lamps 6.29 6.2 Service Processor LEDs 6.30 6.2.1 Wintec Service Processor 6.30 6.2.2 Supermicro Service Processor 6.31 6.3 Securing the Storage Server 6.32 7 Understanding T-Class LED Status 7.1 Using the Component LEDs 7.2 7.1.
PAGE 8
Messages and Operator’s Guide InForm OS Version 2.3.1 8.2 Service Processor LEDs 8.22 8.2.1 Wintec Service Processor 8.22 8.2.2 Supermicro Service Processor 8.23 8.2.3 Supermicro II Service Processor 8.25 8.3 Securing the Storage Server 8.26 9 Understanding F-Class LED Status 9.1 Using the Component LEDs 9.2 9.1.1 Bezel LEDs 9.2 9.1.2 Removing the Bezels and Unlocking the Door 9.4 9.1.3 Drive Chassis LEDs 9.4 9.1.4 Drive Magazine LEDs 9.12 9.1.5 Controller Node LEDs 9.14 9.1.
PAGE 9
InForm OS Version 2.3.1 Messages and Operator’s Guide 11.4.1 Alert 11.5 11.4.2 Cage 11.5 11.4.3 Date 11.13 11.4.4 LD 11.14 11.4.5 License 11.17 11.4.6 Network 11.18 11.4.7 Node 11.19 11.4.8 PD 11.22 11.4.9 Port 11.27 11.4.10 RC 11.32 11.4.11 SNMP 11.33 11.4.12 Task 11.33 11.4.13 VLUN 11.34 11.4.14 VV 11.35 12 Alerts A IX RH Agency Compliance Statements A.1 Safety Precautions A.2 A.2 Safety Agency Compliance Notices A.2 A.2.
PAGE 10
Messages and Operator’s Guide x Table of Contents InForm OS Version 2.3.
PAGE 11
InForm OS Version 2.3.1 Messages and Operator’s Guide 1 Introduction In this chapter 1.1 Audience 1.2 1.2 Related Documents 1.2 1.3 Organization 1.3 1.4 Typographical Conventions 1.4 1.5 Advisories 1.5 This guide provides the information you need to familiarize yourself with 3PAR® InServ® Storage Server alerts, components, LEDs and procedures for powering on and powering off the storage server.
PAGE 12
Messages and Operator’s Guide InForm OS Version 2.3.1 1.1 Audience This guide is for system administrators and experienced users who are familiar with storage servers, understand the operating system(s) they are using, and have a working knowledge of RAID. 1.
PAGE 13
InForm OS Version 2.3.1 Messages and Operator’s Guide 1.3 Organization This guide is organized as follows: This chapter provides an overview of this guide, including intended audience, user interfaces, supported operating systems, related documents, typographical conventions, and advisories.
PAGE 14
Messages and Operator’s Guide InForm OS Version 2.3.1 Chapter 11, Troubleshooting, provides information about troubleshooting InServ Storage Server hardware and software components. Chapter 12, Alerts, provides alerts displayed on the Management Console and the Command Line Interface (CLI) and explains what actions to take when an alert is displayed. Appendix A, Agency Compliance Statements, provides safety precautions and agency compliance notices for InServ Storage Servers and their components.
PAGE 15
InForm OS Version 2.3.1 Messages and Operator’s Guide 1.5 Advisories To avoid injury to people or damage to data and equipment, be sure to observe the cautions and warnings in this guide. Always be careful when handling any electrical equipment. NOTE: Notes are reminders, tips, or suggestions that supplement the procedures included in this guide. CAUTION: Cautions alert you to actions that can cause damage to equipment, software, or data.
PAGE 16
Messages and Operator’s Guide 1.6 Advisories InForm OS Version 2.3.
PAGE 17
InForm OS Version 2.3.1 Messages and Operator’s Guide 2 Numbering System and Component Locations for S-Class Servers In this chapter 2.1 Identifying Storage Server Components 2.1 2.2 Understanding Component Numbering 2.3 2.2.1 Cabinet Numbering 2.3 2.2.2 PDU Numbering 2.5 2.2.3 Drive Cage Numbering 2.6 2.2.4 Controller Node Numbering 2.10 2.2.5 Power Supply Numbering 2.15 2.
PAGE 18
Messages and Operator’s Guide InForm OS Version 2.3.1 Front Fascia Drive Magazines Bezel Drive Cage FC-AL Modules Drive Chasis Controller Nodes Storage Server Backplane with Controller Nodes Main Power Cords Battery Tray Service Processor Leveling Foot 0001_L_R3 Figure 2-1. The Front of an InServ S400 2.
PAGE 19
InForm OS Version 2.3.1 Messages and Operator’s Guide Rear Door Drive Cage Power Supplies Lock Controller Node Power Supplies Battery Backup Units (BBUs) Hinge Power Distribution Units (PDUs) 0212_L_R1 Figure 2-2. Rear View of an InServ S400 2.2 Understanding Component Numbering System components in the InServ S-Class Storage Servers are numbered according to their order and location in the cabinet.
PAGE 20
Messages and Operator’s Guide ■ beginning with 0. ■ from top to bottom. InForm OS Version 2.3.1 Figure 2-3 illustrates numbering of chassis bays in a 3PAR cabinet. Chassis Bays 0 1 2 3 4 5 6 7 8 9 0213_L_R1 Figure 2-3. Numbering of Chassis Bays in the Cabinet 2.
PAGE 21
InForm OS Version 2.3.1 Messages and Operator’s Guide For multi-cabinet configurations, the storage server midplane to which the controller nodes are connected is housed in the node cabinet. Additional cabinets connected to the node cabinet are referred to as drive chassis cabinets. Table 2-1 describes the pattern for cabinet numbering in multi-cabinet storage systems: Table 2-1.
PAGE 22
Messages and Operator’s Guide InForm OS Version 2.3.1 Figure 2-4 illustrates PDU numbering for 3PAR cabinets. NOTE: Figure 2-4 shows a sample system and may not match your particular storage server configuration. PDUs 0 1 2 3 0216_L_R1 Figure 2-4. Numbering of PDUs In addition, each PDU has two power banks (Figure 2-5). Power Bank 1 Power Bank 2 0221_L_R1 Figure 2-5. Power Banks in the PDU 2.2.
PAGE 23
InForm OS Version 2.3.1 Messages and Operator’s Guide NOTE: Figure 2-6 shows a sample system and may not match your particular storage server configuration. 5 4 Drive Chassis 3 2 1 0 Storage Server Backplane 0003_L_R3 Figure 2-6. Numbering of Drive Cages Numbers for drive cages are assigned: ■ beginning with 0. ■ from bottom to top, beginning with the drive cage directly above the top two nodes.
PAGE 24
Messages and Operator’s Guide InForm OS Version 2.3.1 Numbers for drive cage components are assigned: ■ from top to bottom. ■ from left to right. ■ from rear to front for disks in the magazines. ■ in the order indicated by Table 2-2. Table 2-2. Numbering System for DC2 and DC4 Drive Cage Components The following components... Are numbered... Running from...
PAGE 25
InForm OS Version 2.3.1 Messages and Operator’s Guide Figure 2-7 and Figure 2-8 illustrate how the numbering system applies to individual drive cages and drive components. Drive Magazines 1 2 3 4 5 6 7 8 9 Ports A1 B1 Ports B0 A0 0 0588_L_R2 Figure 2-7. Numbering of the Drive Magazines in the Drive Cage Front 3 2 1 0 3 2 1 0 Rear 0600_L_R2 Figure 2-8. Numbering of Disks on the Drive Magazines Understanding Component Numbering 2.
PAGE 26
Messages and Operator’s Guide InForm OS Version 2.3.1 2.2.4 Controller Node Numbering The S-Class Storage Servers use P4 controller nodes. S-Class Storage Servers contain the following numbers of controller nodes: Table 2-3. Number of Controller Nodes by Storage Server Midplane Model Number Storage server midplane Number of nodes InServ S400 2 or 4 InServ S800 2, 4, 6, or 8 A controller node assumes the number of the bay that it occupies in the storage server midplane, as shown in Figure 2-9. 2.
PAGE 27
InForm OS Version 2.3.1 Messages and Operator’s Guide 0 1 2 3 4 5 6 7 0219_L_R1 Figure 2-9. Numbering of Controller Nodes in an InServ S800 Midplane NOTE: Figure 2-9 shows a sample system and may not match your particular storage server configuration. Understanding Component Numbering 2.
PAGE 28
Messages and Operator’s Guide InForm OS Version 2.3.1 Controller nodes are loaded into the storage server midplane from bottom to top. Therefore, for an InServ S800 storage system with only two controller nodes installed, those controller nodes would occupy the lowest 4U of the midplane and would be numbered node 6 and node 7. As shown in Figure 2-10, a controller node contains six PCI slots numbered 0 through 5, from left to right.
PAGE 29
InForm OS Version 2.3.1 Messages and Operator’s Guide Controller nodes contain both control cache DIMMs and data cache DIMMs (Figure 2-11). Data Cache DIMMs P4 Control Cache DIMMs Riser Card 7 0 (J7100) 6 1 (J7300) 5 2 (J7200) 4 3 (J7400) 3 2 1 0 Processors 0 1 2 3 4 5 PCI Slots with PCI Adapters and Load Cards 0223_L_R1 Figure 2-11.
PAGE 30
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 2-4. Numbering System for Controller Nodes and their Components The following components... Are numbered... Running from... dual-port adapters 1,2 top to bottom quad-port adapters 1,1,2,3 top to bottom control cache 0,1,2,3 right to left* data cache 0,1,2,3,4,5,6,7 bottom to top Fibre Channel ports DIMMs * When facing the storage server. 2.
PAGE 31
InForm OS Version 2.3.1 Messages and Operator’s Guide 2.2.5 Power Supply Numbering InServ T-Class and S-Class Storage Server cabinets are divided into power domains that each contain drive cages or controller nodes and four dedicated power supplies. These power supplies, located at the rear of the system, receive AC power input from the PDUs, at the bottom of the cabinet, and deliver DC power to the drive cages and controller nodes.
PAGE 32
Messages and Operator’s Guide 2.16 Understanding Component Numbering InForm OS Version 2.3.
PAGE 33
InForm OS Version 2.3.1 Messages and Operator’s Guide 3 Numbering System and Component Locations for T-Class Servers In this chapter 3.1 Identifying Storage Server Components 3.2 3.2 Service Processor Placement 3.3 3.3 Understanding Component Numbering 3.4 3.3.1 Cabinet Numbering 3.5 3.3.2 PDU Numbering 3.7 3.3.3 Battery Backup Unit Numbering 3.9 3.3.4 Controller Node Numbering 3.11 3.3.5 Drive Chassis Numbering 3.15 3.3.6 Power Supply Numbering 3.
PAGE 34
Messages and Operator’s Guide InForm OS Version 2.3.1 3.1 Identifying Storage Server Components Figure 3-1 and Figure 3-2 identify the major components of an InServ T400 Storage Server in a 2M (40U) 3PAR cabinet. Drive Magazines Front Fascia Drive Chassis Bezel Drive Cage FC-AL Modules Controller Nodes Storage Server Backplane with Controller Nodes Battery Tray Main Power Cords Service Processor Leveling Foot 0582_L_R1 Figure 3-1. The Front of an InServ T400 Storage Server 3.
PAGE 35
InForm OS Version 2.3.1 Messages and Operator’s Guide Rear Door Drive Cage Power Supplies Lock Controller Node Power Supplies Battery Backup Units (BBUs) Hinge Power Distribution Units (PDUs) 0212_L_R1 Figure 3-2. The Rear View of an InServ T400 Storage Server 3.2 Service Processor Placement A service processor designed to support all actions required for the maintenance of the storage server also resides at the bottom of the cabinet. It also provides real-time, automated monitoring.
PAGE 36
Messages and Operator’s Guide InForm OS Version 2.3.1 Battery Tray Service Processor PDUs (Visible Only from the Back) 0004_L_R3 Figure 3-3. Placement of the Service Processor NOTE: For T800 Storage Servers, the service processor is located above the storage server backplane, below the lowest drive chassis but above the upper battery tray. Figure 3-5 illustrates service processor placement for an T800 storage server.
PAGE 37
InForm OS Version 2.3.1 Messages and Operator’s Guide 3.3.1 Cabinet Numbering The InServ T-Class Storage Server 2M (40U) storage server cabinet is an EIA-standard rack that accepts storage server components. Numbers for chassis bays are assigned: ■ beginning with 0. ■ from top to bottom. Figure 3-4 illustrates numbering of chassis bays in a 3PAR cabinet. Chassis Bays 0 1 2 3 4 5 6 7 8 9 0583_L_R1 Figure 3-4.
PAGE 38
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 3-1 describes the pattern for cabinet numbering in multi-cabinet storage systems and for operating sites with multiple systems: Table 3-1. Cabinet Numbering Cabinet Number Controller node cabinet C00 Drive chassis cabinets connecting to the first node cabinet C01, C02, C03...C09 Figure 3-5 shows the location of system components for InServ T400 and T800 Storage Server controller node cabinets.
PAGE 39
InForm OS Version 2.3.1 Messages and Operator’s Guide Rack Units (U) 40 Bay Number 0 Drive Chassis or Filler Panel 1 Drive Chassis or Filler Panel 2 Drive Chassis or Filler Panel 3 Drive Chassis or Filler Panel 4 Drive Chassis or Filler Panel 5 Drive Chassis or Filler Panel 6 Drive Chassis or Filler Panel 7 Drive Chassis 38 36 34 32 30 28 26 24 22 20 18 16 14 12 10 8 8 Filler Panel 6 PDU 0 PDU 1 PDU 2 PDU 3 4 9 2 0 0215_L_R1 Figure 3-6. Drive Chassis Cabinet Component Layout 3.3.
PAGE 40
Messages and Operator’s Guide InForm OS Version 2.3.1 PDUs 0 1 2 3 0216_L_R1 Figure 3-7. Numbering of PDUs NOTE: For T800 Storage Servers, 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 of the storage server and the rear. Figure 3-5 illustrates PDU placement for an T800 storage server.
PAGE 41
InForm OS Version 2.3.1 Messages and Operator’s Guide NOTE: For more information on PDUs and storage server configurations, see the 3PAR InServ® T-Class Storage Server Installation and Deinstallation Guide. 3.3.3 Battery Backup Unit Numbering The storage server controller node cabinet includes one or two battery trays that hold the Battery Backup Units (BBU). The BBUs supply enough power to write the cache memory to the IDE drive inside the nodes in the event of a power failure.
PAGE 42
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 3-2. Number of BBUs and Battery Tray Placement by Storage Server Backplane and Number of Controller Nodes Backplane Nodes BBU Battery Trays Tray Placement T400 2 2 1 Below backplane 4 4 1 Below backplane 2 2 1 Below backplane 4 4 1 Below backplane 6 6 2 T800 Below backplane (1) Above backplane (1) 8 8 2 Below backplane (1) Above backplane (1) 3.3.3.
PAGE 43
InForm OS Version 2.3.1 Messages and Operator’s Guide When facing the rear of the storage server, Magnetek BBUs are numbered from right to left, 0 through 3. When two battery trays are present, the upper tray is numbered 0 and the lower tray is numbered 1 (Figure 3-11). Storage Server (Rear) Tray 0 BBU 3 BBU 2 BBU 1 BBU 0 Storage Server Backplane Tray 1 BBU 3 BBU 2 BBU 1 BBU 0 0218_L_R1 Figure 3-11. Magnetek BBU Numbering Scheme 3.3.
PAGE 44
Messages and Operator’s Guide InForm OS Version 2.3.1 A controller node takes on the number of the bay that it occupies in the storage server backplane, as shown in Figure 3-12. 0 1 2 3 4 5 6 7 0586_L_R1 Figure 3-12. Numbering of Controller Nodes in an InServ T800 Backplane 3.
PAGE 45
InForm OS Version 2.3.1 Messages and Operator’s Guide As shown in Figure 3-13, 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). Fibre Channel Ports 1 2 3 4 Maintenance Port (C0) 0 1 2 3 PCI Slots 4 5 Ethernet Port (E0) Ethernet Port (E1) 0590_L_R2 Figure 3-13.
PAGE 46
Messages and Operator’s Guide InForm OS Version 2.3.1 Inside the controller node are control cache DIMMs and data cache DIMMs. ■ Control cache DIMMs are located in control cache slots 0 and 1 (Figure 3-14). ■ Data cache DIMMs are located on data cache riser cards (Figure 3-14). DIMM 0.0 (J0901) DIMM 0.1 (J0801) Bank 0 Bank 2 DIMM 2.0 (J1300) DIMM 2.1 (J1200) Bank 1 DIMM 1.0 (J0900) DIMM 1.1 (J0800) Data Cache 2-Slot Riser Card Data Cache 4-Slot Riser Card 0594_L_R2 Figure 3-14.
PAGE 47
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 3-3. Numbering System for Controller Nodes and their Components (continued) The Following Components... Are Numbered... Running from... dual-port adapters 1,2 top to bottom quad-port adapters 1,2,3,4 top to bottom control cache 0,1 left to right* data cache 0,1,2,3,4,5,6,7 PCI ports Control Cache DIMMs Data Cache DIMMs Bank 0 0,1 Bank 1 0,1 Bank 2 0,1 top to bottom * When facing the storage server. 3.3.
PAGE 48
Messages and Operator’s Guide InForm OS Version 2.3.1 Drive chassis are always placed above the storage server backplane enclosure and numbered according to their position in relation to the backplane, as shown in Figure 3-15. 5 4 Drive Chassis 3 2 1 0 Storage Server Backplane 0003_L_R3 Figure 3-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. 3.
PAGE 49
InForm OS Version 2.3.1 Messages and Operator’s Guide Figure 3-16 and Figure 3-17 illustrate individual drive chassis components and how they are numbered. Fibre Channel ports in the FC-AL adapters at the sides of the drive chassis enable connection to the controller nodes. Drive Magazines 1 2 3 4 5 6 7 8 9 Ports A1 B1 Ports B0 A0 0 0588_L_R2 Figure 3-16.
PAGE 50
Messages and Operator’s Guide InForm OS Version 2.3.1 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 3-4. Table 3-4. Numbering System for Drive Chassis Components The Following Components... Are Numbered... Running from... Drive cages 0,1,... bottom to top FC-AL modules 0,1 left to right FC-AL 0 A0,B0 top to bottom FC-AL 1 A1,B1 Fibre Channel ports 3.
PAGE 51
InForm OS Version 2.3.1 Messages and Operator’s Guide 3.3.5.1 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 3-18. NOTE: See the systems planning document or 3PAR Systems Assurance and PreSite Planning Guide drive magazine allocation instructions specific to your system.
PAGE 52
Messages and Operator’s Guide InForm OS Version 2.3.1 NOTE: For further instructions on drive magazine allocation, see the 3PAR InServ® T-Class Storage Server Installation and Deinstallation Guide. 3.3.6 Power Supply Numbering Cabinets are divided into upper and lower power domains that contain drive cages or controller nodes and dedicated power supplies.
PAGE 53
InForm OS Version 2.3.1 Messages and Operator’s Guide Power Supplies 0 1 2 3 Upper Power Domain Lower Power Domain 0227_L_R2 Figure 3-19. Numbering of Power Supplies within the Power Domains Understanding Component Numbering 3.
PAGE 54
Messages and Operator’s Guide 3.22 Understanding Component Numbering InForm OS Version 2.3.
PAGE 55
InForm OS Version 2.3.1 Messages and Operator’s Guide 4 Numbering System and Component Locations for E-Class Servers In this chapter 4.1 Identifying Storage Server Components 4.2 4.2 Service Processor Placement 4.4 4.3 Understanding Component Numbering 4.4 4.3.1 Cabinet Numbering 4.4 4.3.2 PDU Numbering 4.7 4.3.3 Controller Node Numbering 4.9 4.3.4 Drive Chassis Numbering 4.12 4.3.5 Power Supply Numbering 4.
PAGE 56
Messages and Operator’s Guide InForm OS Version 2.3.1 4.1 Identifying Storage Server Components Figure 4-1 and Figure 4-2 identify the major components of an InServ E-Class Storage Server in a 2M (40U) 3PAR cabinet. Drive Chassis Bezel (Controller Nodes Located Behind) Service Processor Power Distribution Units (PDUs) 0396_L_R2 Figure 4-1. The Front of an InServ E-Class (in a 2M Rack) 4.
PAGE 57
InForm OS Version 2.3.1 Messages and Operator’s Guide Drive Chassis Power Supplies (4x) Controller Node Power Supplies (2x) Controller Nodes (2x) Service Processor Power Distribution Units (PDUs) (4x) (Rear View) 0398_L_R2 Figure 4-2. The Rear View of an InServ E-Class (in a 2M Rack) Identifying Storage Server Components 4.
PAGE 58
Messages and Operator’s Guide InForm OS Version 2.3.1 4.2 Service Processor Placement A service processor designed to support all actions required for the maintenance of the storage server also resides at the bottom of the cabinet to provide real-time automated monitoring. The service processor allows 3PAR to identify, research, diagnose, and even resolve potential problems remotely.
PAGE 59
InForm OS Version 2.3.1 Messages and Operator’s Guide Figure 4-3 illustrates numbering of chassis bays in a 3PAR cabinet. Bay # Rail # 0 32 1 29 2 26 3 23 4 19 5 16 6 13 7 10 8 9 10 11 12 13 14 7 6 5 4 3 2 1 0397_L_R3 Figure 4-3. Numbering of Chassis Bays in the Cabinet A storage system can be housed in a single cabinet (2M) or multiple cabinets (1M). When multiple cabinets are required, the first cabinet, the controller node cabinet, holds the controller nodes.
PAGE 60
Messages and Operator’s Guide InForm OS Version 2.3.1 Figure 4-4 shows the location of system components for InServ E-Class 1M and 2M controller node cabinets. Figure 4-5 shows the location of system components for 1M drive chassis expansion cabinets. NOTE: When a cabinet does not include a service processor, a filler panel covers the area of the cabinet that the service processor would normally occupy.
PAGE 61
InForm OS Version 2.3.1 Messages and Operator’s Guide 4U Empty 4U Drive Chassis 3 3U Drive Chassis 2 3U Drive Chassis 1 3U Drive Chassis 0 3U 2U Empty PDU 0 PDU 1 1M Cabinet 2U 1U 1U = 20U 0414_L_R1 Figure 4-5. Drive Chassis 1M Expansion Cabinet Component Layout 4.3.2 PDU Numbering For each InServ E-Class Storage Server 2M cabinet, four Power Distribution Units (PDUs) occupy the lowest chassis bay in the cabinet. For each 1M cabinet, two PDUs occupy the lowest chassis bay.
PAGE 62
Messages and Operator’s Guide InForm OS Version 2.3.1 6U Empty Drive Chassis 7 Drive Chassis 6 Drive Chassis 5 Drive Chassis 4 Node 0 Node 0 Node 1 Node 1 Drive Chassis 0 Drive Chassis 0 Drive Chassis 1 Drive Chassis 1 Drive Chassis 2 Drive Chassis 2 Drive Chassis 3 Drive Chassis 3 Service Processor 1U Empty PDU 0 PDU 1 1M Cabinet Service Processor 1U Empty PDU 0 PDU 1 PDU 2 PDU 3 2M Cabinet 0415_L_R1 Figure 4-6.
PAGE 63
InForm OS Version 2.3.1 Messages and Operator’s Guide WARNING: To avoid possible injury, damage to storage server equipment, and potential loss of data, do not use the surplus power outlets in the storage server PDUs. Never use outlets in the PDUs to power components that do not belong to the storage server or to power storage server components that reside in other cabinets. 4.3.3 Controller Node Numbering The InServ E-Class Storage Server contains two nodes per system.
PAGE 64
Messages and Operator’s Guide InForm OS Version 2.3.1 6U Empty Drive Chassis 7 Drive Chassis 6 Drive Chassis 5 Drive Chassis 4 Node 0 Node 1 Drive Chassis 0 Drive Chassis 1 Drive Chassis 2 Drive Chassis 3 Service Processor 1U Empty PDU 0 PDU 1 PDU 2 PDU 3 2M Cabinet 0416_L_R1 Figure 4-8. Numbering of Controller Nodes in a 2M Cabinet As shown in Figure 4-9, a controller node contains four controller slots. Slots 0 and 3 accept SFPs for Fibre Channel connection.
PAGE 65
InForm OS Version 2.3.1 Messages and Operator’s Guide Controller Slots 1 and 2 (PCI Slots) Controller Slot 0 Controller Slot 3 0399_L_R1 Figure 4-9. 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.
PAGE 66
Messages and Operator’s Guide InForm OS Version 2.3.1 Data Cache DIMMs: DIMM 0 (J4401) DIMM 1 (J4402) DIMM 2 (J4501) DIMM 3 (J4502) Controller Slot 0 Controller Slot 1 Controller Slot 2 Controller Slot 3 Control Cache DIMMs: DIMM 0 (J7300) DIMM 1 (J7100) 0400_L_R1 Figure 4-10. Control Cache and Data Cache DIMMs in the Controller Node 4.3.4 Drive Chassis Numbering Depending on the specific configuration, an InServ E-Class Storage Server can include up to six drive chassis.
PAGE 67
InForm OS Version 2.3.1 Messages and Operator’s Guide 6U Empty Drive Chassis 7 Drive Chassis 6 Drive Chassis 5 Drive Chassis 4 Node 0 Node 0 Node 1 Node 1 Drive Chassis 0 Drive Chassis 0 Drive Chassis 1 Drive Chassis 1 Drive Chassis 2 Drive Chassis 2 Drive Chassis 3 Drive Chassis 3 Service Processor 1U Empty PDU 0 PDU 1 1M Cabinet Service Processor 1U Empty PDU 0 PDU 1 PDU 2 PDU 3 2M Cabinet 0415_L_R1 Figure 4-11.
PAGE 68
Messages and Operator’s Guide InForm OS Version 2.3.1 Figure 4-12 and Figure 4-13 illustrate individual drive chassis components and how they are numbered. Fibre Channel ports in the Fibre Channel Arbitrated Loop (FCAL) at the sides of the drive chassis enable connection to the controller nodes. 0148_L_R2 Figure 4-12. Drive Chassis - Front View, Drive Magazine Bay Numbering Drive Chassis Power Supply B3 A0 B2 A1 B1 A2 B0 A3 FCAL-B FCAL-A Drive Chassis Power Supply 0406_L_R1 Figure 4-13.
PAGE 69
InForm OS Version 2.3.1 Messages and Operator’s Guide 4.3.4.1 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 4-1 on page 4.15. The following figure shows the drive magazine numbering: NOTE: See the systems planning document or 3PAR Systems Assurance and PreSite Planning Guide drive magazine allocation instructions specific to your system.
PAGE 70
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 4-1. Drive Magazine Loading Pattern (continued) Drive Magazine Pair Group Number Number 4 7 9, 13 8 2, 6 Drive Magazine Bay NOTE: The loading sequence displayed in the table above indicates that 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. 4.3.
PAGE 71
InForm OS Version 2.3.1 Messages and Operator’s Guide Drive Chassis Power Supply Numbering: 0 1 Controller Node Power Supply Numbering: 1 0 (Rear View) 0402_L_R2 Figure 4-15. Numbering of Power Supplies Understanding Component Numbering 4.
PAGE 72
Messages and Operator’s Guide 4.18 Understanding Component Numbering InForm OS Version 2.3.
PAGE 73
InForm OS Version 2.3.1 Messages and Operator’s Guide 5 Numbering System and Component Locations for F-Class Servers In this chapter 5.1 Identifying Storage Server Components 5.2 5.2 Service Processor Placement 5.4 5.3 Understanding Component Numbering 5.4 5.3.1 Cabinet Numbering 5.4 5.3.2 PDU Numbering 5.7 5.3.3 Controller Node Numbering 5.9 5.3.4 Drive Chassis Numbering 5.11 5.3.5 Power Supply Numbering 5.
PAGE 74
Messages and Operator’s Guide InForm OS Version 2.3.1 5.1 Identifying Storage Server Components Figure 5-1 and Figure 5-2 identify the major components of an InServ F-Class Storage Server. Drive Chassis Bezel (Controller Nodes Located Behind) Service Processor Empty 1U Space Power Distribution Units (PDUs) 0699_L_R2 Figure 5-1. The Front of an InServ F400 5.
PAGE 75
InForm OS Version 2.3.1 Messages and Operator’s Guide Drive Chassis Power Supplies (4x) Controller Node Power Supplies (4x) Controller Nodes (4x) Service Processor Empty 1U Space Power Distribution Units (PDUs) (4x) (Rear View) 0698_L_R2 Figure 5-2. The Rear View of an InServ F400 Identifying Storage Server Components 5.
PAGE 76
Messages and Operator’s Guide InForm OS Version 2.3.1 5.2 Service Processor Placement A service processor designed to support all actions required for the maintenance of the storage server also resides at the bottom of the cabinet to provide real-time automated monitoring. The service processor allows 3PAR to identify, research, diagnose, and even resolve potential problems remotely.
PAGE 77
InForm OS Version 2.3.1 Messages and Operator’s Guide Figure 5-3 illustrates numbering of chassis bays in a 3PAR cabinet. Bay Number Rail Number Bay Number 0 Rail Number 1 36 2 33 3 30 4 27 38 0 35 1 32 2 29 3 26 5 23 4 6 19 19 7 16 6 16 7 8 13 13 8 9 10 10 9 10 7 6 5 4 3 2 1 11 12 13 14 15 F200 Cabinet 7 6 5 4 3 2 1 10 11 12 13 14 F400 Cabinet 0700_L_R5 Figure 5-3. Numbering of Chassis Bays in the Cabinet Understanding Component Numbering 5.
PAGE 78
Messages and Operator’s Guide InForm OS Version 2.3.1 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 server 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.
PAGE 79
InForm OS Version 2.3.
PAGE 80
Messages and Operator’s Guide InForm OS Version 2.3.1 Figure 5-5 illustrates the four PDUs at the bottom of a 3PAR cabinet. PDUs 0 1 2 3 0216_L_R1 Figure 5-5. Numbering of PDUs Each PDU has two power banks, each with a separate circuit breaker, to be used exclusively for storage server components (Figure 5-6). Power Bank 1 Power Bank 2 0221_L_R1 Figure 5-6.
PAGE 81
InForm OS Version 2.3.1 Messages and Operator’s Guide 5.3.3 Controller Node Numbering The InServ F-Class Storage Server contains two or four nodes per system. Controller nodes are numbered from top to bottom node 0 and node 1 for a two node system, and node 0, node 1, node 2, node 3 for a four node system.
PAGE 82
Messages and Operator’s Guide InForm OS Version 2.3.1 A controller node contains two controller slots and two on-board Ethernet ports. See Figure 5-8 for specific port type assignments. Slot 0 Slot 1 Slot 2 FC / iSCSI FC / iSCSI FC Ethernet Port (E0) GigE Ethernet Port (E1) GigE 0681_L_R2 Figure 5-8. 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.
PAGE 83
InForm OS Version 2.3.1 Messages and Operator’s Guide Data Cache DIMMs: DC DIMM 2 (J6001) DC DIMM 1 (J5901) DC DIMM 0 (J5801) Control Cache DIMMs: CC DIMM 0 (J4200) CC DIMM 1 (J4300) 0689_L_R2 Figure 5-9. Control Cache and Data Cache DIMMs in the Controller Node 5.3.4 Drive Chassis Numbering Depending on the specific configuration, an InServ F-Class Storage Server can include up to 10 drive chassis. A drive chassis houses 16 drive magazines.
PAGE 84
Messages and Operator’s Guide InForm OS Version 2.3.
PAGE 85
InForm OS Version 2.3.1 Messages and Operator’s Guide Figure 5-11 and Figure 5-12 illustrate individual drive chassis components and how they are numbered. Fibre Channel ports in the Fibre Channel Arbitrated Loop (FCAL) at the sides of the drive chassis enable connection to the controller nodes. 0148_L_R2 Figure 5-11. Drive Chassis - Front View, Drive Magazine Bay Numbering Drive Chassis Power Supply B3 A0 B2 A1 B1 A2 B0 A3 FCAL-B Drive Chassis Power Supply FCAL-A 0406_L_R1 Figure 5-12.
PAGE 86
Messages and Operator’s Guide InForm OS Version 2.3.1 5.3.4.1 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 5-2 on page 5.14. The following figure shows the drive magazine numbering: NOTE: See the systems planning document or 3PAR Systems Assurance and PreSite Planning Guide drive magazine allocation instructions specific to your system.
PAGE 87
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 5-2. Drive Magazine Loading Pattern (continued) Drive Magazine Pair Group Number Number 4 7 9, 13 8 2, 6 Drive Magazine Bay 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. 5.3.
PAGE 88
Messages and Operator’s Guide InForm OS Version 2.3.
PAGE 89
InForm OS Version 2.3.1 Messages and Operator’s Guide 6 Understanding S-Class LED Status In this chapter 6.1 Using the Component LEDs 6.2 6.1.1 Removing the Bezels and Unlocking the Door 6.2 6.1.2 Drive Cage LEDs 6.4 6.1.3 Controller Node LEDs 6.16 6.1.7 Power Supply LEDs 6.26 6.1.8 Battery Backup Unit LEDs 6.28 6.1.9 Power Distribution Unit Lamps 6.29 6.2 Service Processor LEDs 6.30 6.2.1 Wintec Service Processor 6.30 6.2.2 Supermicro Service Processor 6.31 6.
PAGE 90
Messages and Operator’s Guide InForm OS Version 2.3.1 6.1 Using the Component LEDs InServ S-Class Storage Server components have LEDs to indicate that the hardware is functioning properly and to help identify errors. These LEDs serve as tools for diagnosing basic hardware problems. You can quickly identify hardware problems by simply examining the LEDs on all the components. Use the tables and diagrams in the following sections to verify the hardware is functioning properly.
PAGE 91
InForm OS Version 2.3.1 Messages and Operator’s Guide Fascia Lock (4x) 0229_L_R1 Figure 6-1. Optional Locking Fascia ■ To view the power supply, battery or PDU LEDs, open the rear door by unlatching the three latches located at the top, center, and bottom of the door. Using the Component LEDs 6.
PAGE 92
Messages and Operator’s Guide InForm OS Version 2.3.1 NOTE: Many LEDs are visible without removing the bezels. To view the power supply, battery or PDU LEDs, open the rear door of the cabinet. 6.1.2 Drive Cage LEDs The S-Class InServ Storage Server can use DC2 and DC4 drive cages. The drive cages house two FC-AL modules and a maximum of ten drive magazines. See Figure 6-2 and Figure 6-3. Drive Magazines 1 2 3 4 0 1 2 3 4 B0 B0 B1 B1 Ports Ports A0 A0 A1 A1 0 0224_L_R1 Figure 6-2.
PAGE 93
InForm OS Version 2.3.1 Messages and Operator’s Guide Drive Magazines 1 2 3 4 5 6 7 8 9 Ports A1 B1 Ports B0 A0 0 0588_L_R1 Figure 6-3. DC4 Drive Cage Using the Component LEDs 6.
PAGE 94
Messages and Operator’s Guide InForm OS Version 2.3.1 6.1.2.1 DC2 and DC4 Drive Cage FC-AL Module LEDs The DC2 drive cage FC-AL modules have the following LEDs, see Figure 6-4. Port A Port A RX LED Port A TX LED Port B Port B RX LED Port B TX LED Hot-Plug LED FC-AL Status LED Split Mode LED (Typical) 0250_L_R1 Figure 6-4. Connections and LEDs on the DC2 Drive Cage FC-AL Modules 6.
PAGE 95
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 6-1 describes the LED functions of the DC2 drive cage FC-AL modules. Table 6-1. DC2 Drive Cage FC-AL Module LED Displays LED Appearance Meaning RX Steady green light Indicates the presence of small form-factor pluggable optical transceiver (SFP) and a valid signal from the node. No light Indicates there is no connection to the node or no SFP installed.
PAGE 96
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 6-1. DC2 Drive Cage FC-AL Module LED Displays (continued) LED Appearance Meaning Rapid toggle between Indicates a cage firmware upgrade amber and green light initiated by the upgradecage CLI command. A firmware upgrade normally takes less than two minutes to complete. Hot-plug Steady amber light Indicates FC-AL module is prepared for replacement (hot plug). No light Indicates FC-AL module is not prepared for hot plug.
PAGE 97
InForm OS Version 2.3.1 Messages and Operator’s Guide The DC4 drive cage FC-AL modules contain the following LEDs, see Figure 6-4. Port A Port A RX LED Port A TX LED Port B Port B RX LED Port B TX LED Hot-Plug LED FC-AL Status LED Split Mode LED (Typical) 0250_L_R1 Figure 6-5. Connections and LEDs on the DC4 Drive Cage FC-AL Modules Using the Component LEDs 6.
PAGE 98
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 6-2 describes the LED functions of the DC4 drive cage FC-AL modules. Table 6-2. DC4 Drive Cage FC-AL Module LED Displays LED Appearance Meaning RX Steady green light Indicates the presence of small form-factor pluggable optical transceiver (SFP) and a valid signal from the node. No light Indicates there is no connection to the node or no SFP installed.
PAGE 99
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 6-2. DC4 Drive Cage FC-AL Module LED Displays (continued) LED Appearance Meaning Flashing amber light (1 blink The drive cage has some type of per second) error, for example a failed or missing power supply, but is communicating with a node. Rapid toggle between amber Indicates a cage firmware and green light upgrade initiated by the upgradecage CLI command is in progress.
PAGE 100
Messages and Operator’s Guide InForm OS Version 2.3.1 6.1.2.2 DC2 Drive Magazine LEDs DC2 drive magazines contain the following LEDs, see Figure 6-6. Disk Status LEDs Hot-Plug LED 3 2 1 0 ! DC2 (SATA Drive) Drive Magazine Status LED DC2 0518_L_R1 Figure 6-6. DC2 Drive Magazine Status LEDs Table 6-3 describes the LED functions of the DC2 drive magazines. 6.
PAGE 101
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 6-3. DC2 Drive Magazine LED Displays LED Appearance Meaning DC2 Drive Magazine Status Steady amber light Indicates a drive magazine error, or one or more drives are bypassed on at least one path. Disk status Quick flashing, or Indicates disk is not spun up but is 20%-on/80%-off functioning. green light Steady green light Indicates disk is spun up and waiting for a command.
PAGE 102
Messages and Operator’s Guide InForm OS Version 2.3.1 6.1.2.3 DC4 Drive Magazine LEDs DC4 Drive magazines contain the following LEDs, see Figure 6-6. Disk Status LEDs Hot-Plug LED 3 2 1 0 ! Drive Magazine Status LED DC4 0587_L_R1 Figure 6-7. DC4 Drive Magazine LEDs Table 6-4 describes the LED functions of the DC4 drive magazines. NOTE: After powering on, allow approximately two minutes for the disks on the DC4 drive magazine to spin up before checking the drive magazine LEDs. 6.
PAGE 103
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 6-4. DC4 Drive Magazine LED Displays LED Appearance Meaning DC4 Drive Steady green light Indicates that the drive Magazine Status magazine is functioning properly. Steady amber light Indicates a drive magazine error, or one or more drives are bypassed on at least one path. Disk status Quick flashing, or 20 Indicates disk is not spun up but percent-on and 80 percent- is functioning.
PAGE 104
Messages and Operator’s Guide InForm OS Version 2.3.1 6.1.3 Controller Node LEDs Depending upon the configuration, the InServ S-Class Storage Servers contain between two and eight controller nodes, all located in the storage server midplane. Controller nodes contain the following LEDs, see Figure 6-8. Hot-Plug LED Ethernet 10/100 Mbps LED Status LED Ethernet Activity LED 0252_L_R1 Figure 6-8. Controller Node LEDs Consult Table 6-5 to verify proper functioning of controller nodes. 6.
PAGE 105
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 6-5. Controller Node LED Displays LED Appearance Meaning Status Flashing green light (1 blink Indicates node is fully functional and part of the per second) cluster. Flashing amber light Indicates the node has a failed or missing power (1 blink per second) supply, fan, backup battery, or TOD battery, but the node is still operational. Steady green light Indicates node is in the process of joining the cluster.
PAGE 106
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 6-5. Controller Node LED Displays (continued) LED Appearance Meaning Ethernet 10/ Light on 100 MB/sec mode. No light 10 MB/sec mode (or disconnected). 100 MB/sec 6.1.3.1 QLogic Fibre Channel Port LEDs The QLogic Fibre Channel adapters in the InServ S-Class Storage Server controller nodes also contain Fibre Channel port LEDs (Figure 6-9). Port 1 Port 2 Green LEDs Port 1 LEDs Port 2 LEDs Amber LEDs 0516_L_R1 Figure 6-9.
PAGE 107
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 6-6 on page 6.19 contains descriptions of all LED combinations for the QLogic Fibre Channel port LED pairs. Consult this table to verify proper functioning of Fibre Channel ports for QLogic HBAs. Table 6-6. Fibre Channel Port Status LED Indications (QLogic 2-Port) Green LED (left) Amber LED (right) Port status On On Port has power. On Off Port is connected and online. Off On Port is receiving signal.
PAGE 108
Messages and Operator’s Guide InForm OS Version 2.3.1 6.1.3.2 LSI Logic Fibre Channel Port LEDs The LSI Logic Fibre Channel adapters in the InServ S-Class Storage Server controller nodes also contain Fibre Channel port LEDs. The LSI Logic adapters are available in either two-port or four-port models (Figure 6-10) and (Figure 6-11).
PAGE 109
InForm OS Version 2.3.1 Messages and Operator’s Guide Port 1 Port 2 Port 3 Port 4 LEDs Note: LEDs are Numbered 3 2 1 2 and Correspond with Ports 1 0 3 4 0517_L_R1 Figure 6-11. LSI Logic 4-Port Fibre Channel Port LEDs Each LSI Logic port in the Fibre Channel adapter has one LED which is either off, green or amber, depending on its condition. Table 6-7 on page 6.22 lists all of the LED conditions for the 2-Port LSI Logic Fibre Channel card.
PAGE 110
Messages and Operator’s Guide InForm OS Version 2.3.1 = Table 6-7. Fibre Channel Port Status LED Indications (LSI Logic 2-Port Adapter) LED Condition Steady amber light Off Flashing green light Port Status Link down or cable disconnected Link up Indicates I/O activity Table 6-8. Fibre Channel Port Status LED Indications (LSI Logic 4-Port Adapter) LED Condition Steady amber light Link down or cable disconnected Steady green light Link up Flashing green light 6.
PAGE 111
InForm OS Version 2.3.1 Messages and Operator’s Guide 6.1.4 3PAR Fibre Channel Port LEDs The 3PAR Fibre Channel adapters contained in the controller node also contain Fibre Channel port LEDs. Four port 3PAR Fibre Channel adapters are only used in a P4 InServ S-Class Storage Server (Figure 6-12). Port 1 Not Used (4x) Port 4 Green (4x) 0256_L_R1 Figure 6-12. 3PAR 4-Port Fibre Channel LEDs Consult Table 6-9 to verify proper function of the 3PAR Fibre Channel adapter LEDs. Table 6-9.
PAGE 112
Messages and Operator’s Guide InForm OS Version 2.3.1 6.1.5 Gigabit Ethernet Adapter LEDs When present, the controller node Gigabit Ethernet adapter in the InServ S-Class Storage Server has two LEDs (Figure 6-13). ACT/LNK LED ACT LNK Speed LED 10 100 1000 0513_L_R1 Figure 6-13. Gigabit Ethernet Adapter LEDs Consult Table 6-10 to verify the proper functioning of Gigabit Ethernet adapter LEDs. Table 6-10.
PAGE 113
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 6-10. Gigabit Ethernet Adapter Indicators (continued) LED Appearance Meaning Steady green light 100 MB/sec Steady yellow light 1000 MB/sec 6.1.6 QLogic iSCSI Port LEDs The QLogic iSCSI adapter is provided with two ports. There is one LED for each port as shown in Figure 6-14. Port 1 Green LEDs Port 2 0514_L_R1 Figure 6-14. iSCSI Adapter Port LED Using the Component LEDs 6.
PAGE 114
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 6-11. iSCSI Adapter Port LED Meanings LED Condition Port Status Steady Green Indicates that a link is established. Flashing Green Indicates receiving or transmitting activity. Off Indicates no connection or active link. 6.1.7 Power Supply LEDs Power supply units in the InServ S-Class Storage Servers are located at the rear of all drive cages and controller nodes. Power supplies have the following LEDs (Figure 6-15): 6.
PAGE 115
InForm OS Version 2.3.1 Messages and Operator’s Guide AC LED AC LED Power Supply Status LED Power Supply Status LED Controller Node Power Supply Drive Chassis Power Supply 0291_L_R1 Figure 6-15. Power Supply LEDs NOTE: The appearance of the power supplies may vary slightly according to manufacturer and location (drive chassis or controller node). Consult Table 6-12 on page 6.28 to verify proper operation of the power supplies. Using the Component LEDs 6.
PAGE 116
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 6-12. Power Supply LED Displays LED Appearance Meaning Power supply Steady green light Indicates power is on. Steady amber Indicates power supply error. status light AC No light Indicates a broken connection to the power source. Steady green light Indicates AC is entering from an external source. No light Indicates no AC is entering from an external source (for example, when power is off or when using battery power). 6.1.
PAGE 117
InForm OS Version 2.3.1 Messages and Operator’s Guide Consult Table 6-13 to verify proper functioning of the BBUs. Table 6-13. Battery Backup Unit LED Displays LED Appearance Meaning Battery A status LED Steady green light Indicates battery A is charged. Blinking green light Battery is undergoing a test. Steady amber light Indicates battery error. Steady green light Indicates battery B is charged. Blinking green light Battery is undergoing a test.
PAGE 118
Messages and Operator’s Guide InForm OS Version 2.3.1 6.2 Service Processor LEDs 6.2.1 Wintec Service Processor The Wintec service processor LEDs are defined in this section. The LEDs are located at the top of the service processor (Figure 6-18). Power Button Reset Button Power LED NIC Port 1 LED NIC Port 2 LED Hard Disk Drive LED 0009_L_R2 Figure 6-18. Wintec Service Processor LEDs Consult Table 6-14 to verify proper functioning of the Wintec service processor displays.
PAGE 119
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 6-14. Wintec Service Processor LED Displays (continued) LED Appearance Meaning NIC Port 1 No light .No network activity. Flashing amber light Indicates network activity. No light The system is off. Steady blue light Indicates that the system is powered on. Power 6.2.2 Supermicro Service Processor The Supermicro service processor LEDs are defined in the following section.
PAGE 120
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 6-15. Supermicro Service Processor LED Displays (continued) LED Appearance Meaning Hard Disk Drive No Light Indicates no hard drive activity. Flashing amber light Indicates hard drive activity. No light Indicates the port is not connected. Steady green light Indicates the port is connected. Flashing green light Indicates network activity. No light Indicates the port is not connected.
PAGE 121
InForm OS Version 2.3.1 Messages and Operator’s Guide 7 Understanding T-Class LED Status In this chapter 7.1 Using the Component LEDs 7.2 7.1.1 Removing the Bezels and Unlocking the Door 7.2 7.1.2 Drive Cage LEDs 7.3 7.1.3 Controller Node LEDs 7.9 7.1.4 3PAR Fibre Channel Port LEDs 7.11 7.1.5 QLogic iSCSI Port LEDs 7.12 7.1.6 Power Supply LEDs 7.13 7.1.7 Battery Backup Unit LEDs 7.15 7.1.8 Power Distribution Unit Lamps 7.17 7.1.9 Service Processor LEDs 7.17 7.
PAGE 122
Messages and Operator’s Guide InForm OS Version 2.3.1 7.1 Using the Component LEDs InServ T-Class Storage Server components have LEDs to indicate that the hardware is functioning properly and to help identify errors. These LEDs help diagnose basic hardware problems. You can quickly identify hardware problems by simply examining the LEDs on all the components. Use the tables and diagrams in the following sections to verify that the hardware is functioning properly.
PAGE 123
InForm OS Version 2.3.1 Messages and Operator’s Guide 7.1.2 Drive Cage LEDs The T-Class InServ Storage Server uses a DC4 drive chassis that holds one DC4 drive cage housing two drive cage FC-AL modules and a maximum of 10 drive magazines. See Figure 7-1. Drive Magazines 1 2 3 4 5 6 7 8 9 Ports A1 B1 Ports B0 A0 0 0588_L_R1 Figure 7-1. DC4 Drive Cage Using the Component LEDs 7.
PAGE 124
Messages and Operator’s Guide InForm OS Version 2.3.1 7.1.2.1 DC4 Drive Cage FC-AL Module LEDs The DC4 drive cage FC-AL modules have the following LEDs (Figure 7-2): Port A Port A RX LED Port A TX LED Port B Port B TX LED Port B RX LED Hot-Plug LED FC-AL Status LED 4 Gb/s Split Mode LED (Typical) 0655_L_R1 Figure 7-2. Connections and LEDs on the DC4 Drive Cage FC-AL Modules Consult Table 7-1 to verify proper functioning of the DC4 drive cage FC-AL modules. 7.
PAGE 125
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 7-1. Drive Cage DC4 FC-AL Module LED Displays LED Appearance Meaning RX Steady green light Indicates the presence of small form-factor pluggable optical transceiver (SFP) and a valid signal from the node. No light Indicates there is not a connection to the node or SFP is not installed. TX Steady green light Indicates the presence of SFP and the LED is on and transmitting.
PAGE 126
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 7-1. Drive Cage DC4 FC-AL Module LED Displays (continued) LED Appearance Meaning Flashing amber light (1 blink The drive cage has some type of per second) error, for example a failed or missing power supply, but is communicating with a node. Rapid toggle between amber Indicates a cage firmware and green light upgrade initiated by the upgradecage CLI command is in progress.
PAGE 127
InForm OS Version 2.3.1 Messages and Operator’s Guide 7.1.2.2 Drive Magazine LEDs Drive magazines contain the following LEDs (Figure 7-3): Disk Status LEDs Hot-Plug LED 3 2 1 0 DC4 ! Drive Magazine Status LED 0587_L_R1 Figure 7-3. DC4 Drive Magazine LEDs Consult Table 7-2 to verify proper functioning of disks and drive magazines. Table 7-2. Drive Magazine LED Displays LED Appearance Meaning DC4 Drive Steady green light Indicates the drive magazine is Magazine Status functioning properly.
PAGE 128
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 7-2. Drive Magazine LED Displays (continued) LED Appearance Meaning Disk status Quick flashing, or 20 Indicates disk is not spun up but percent-on and 80 percent- is functioning. off green light Steady green light Indicates the disk is spun up and waiting for a command. Flashing green light Indicates the disk is executing commands. No light Indicates disk is not present.
PAGE 129
InForm OS Version 2.3.1 Messages and Operator’s Guide 7.1.3 Controller Node LEDs Depending upon the configuration, storage servers contain between two and eight controller nodes, all located in the storage server chassis. Controller nodes contain the following LEDs (Figure 7-4): Ethernet 10/100/1000 Mbps LED Disk Hot-plug LED Node Hot-plug LED Node Status LED Ethernet Activity LED 0571_L_R2 Figure 7-4. Controller Node LEDs Consult Table 7-3 to verify proper functioning of controller nodes. Table 7-3.
PAGE 130
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 7-3. Controller Node LED Displays (continued) LED Appearance Meaning Node Hot-plug Steady amber light In combination with the Status LED blinking green three times per second, indicates the controller node is prepared for removal. In combination with the Status LED being solid, indicates a fatal node failure. No light Indicates node is not prepared for removal.
PAGE 131
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 7-3. Controller Node LED Displays (continued) LED Appearance Meaning Ethernet activity Steady or flashing green light Indicates Ethernet activity. No light Indicates no Ethernet activity. Steady amber light 1000 MB/sec mode. Steady green light 100 MB/sec mode. No light 10 MB/sec mode. Ethernet 10/100/ 1000 MB/sec 7.1.
PAGE 132
Messages and Operator’s Guide InForm OS Version 2.3.1 Consult Table 7-4 to verify proper function of the 3PAR Fibre Channel adapter LED. Table 7-4. 3PAR Fibre Channel Port Status LED Indications (3PAR 4-Port Adapter) LED Appearance Meaning No light Wake-up Failure (dead device). Steady green light Normal -- Link up at 2-4 GB/sec. Flashing green light Link down or not connected. 7.1.5 QLogic iSCSI Port LEDs The QLogic iSCSI adapter contains two ports.
PAGE 133
InForm OS Version 2.3.1 Messages and Operator’s Guide Consult Table 7-5 to verify the proper functioning of QLogic iSCSI adapter LEDs. Table 7-5. iSCSI Adapter Port LED Indications LED Appearance Meaning Steady green Indicates a link is established. Flashing green Indicates receiving or transmitting activity. Off Indicates no connection or active link. 7.1.6 Power Supply LEDs Power supply units are located at the rear of all drive cages and controller nodes.
PAGE 134
Messages and Operator’s Guide InForm OS Version 2.3.1 AC LED AC LED Power Supply Status LED Power Supply Status LED Drive Chassis Power Supply Controller Node Power Supply 0632_L_R1 Figure 7-7. Power Supply LEDs NOTE: The appearance of the drive chassis and controller node power supplies can vary slightly according to manufacturer and location. 7.
PAGE 135
InForm OS Version 2.3.1 Messages and Operator’s Guide Consult Table 7-6 to verify proper operation of the power supplies. Table 7-6. Power Supply LED Displays LED Appearance Meaning Power Supply status Steady green light Indicates the power is on. Steady amber light Indicates a power supply error. No light Indicates a broken connection to the AC power source. AC Steady green light Indicates the AC is from an external source.
PAGE 136
Messages and Operator’s Guide InForm OS Version 2.3.1 Battery A Status LED Battery B Status LED 0260_L_R1 Figure 7-8. Battery Backup Unit LEDs (Magnetek) Consult Table 7-7 to verify proper functioning of the BBUs. Table 7-7. Battery Backup Unit LED Displays LED Appearance Meaning Battery A status LED Steady green light Indicates battery A is charged. Flashing green light Indicates the battery is undergoing a test. Steady amber light Indicates a battery error.
PAGE 137
InForm OS Version 2.3.1 Messages and Operator’s Guide 7.1.8 Power Distribution Unit Lamps InServ Storage Servers include four Power Distribution Units (PDUs). PDUs contain two power bank lamps (Figure 7-9): Power Bank Lamps Power Bank 1 Power Bank 2 0261_L_R1 Figure 7-9. Power Distribution Unit Lamps A blue illuminated lamp indicates that power is being supplied to a power bank. When the blue lamp is not illuminated, the power bank is not receiving AC input. 7.1.
PAGE 138
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 7-8. Supermicro Service Processor Front-Panel Displays LED Appearance Meaning Power No light Indicates the service processor is off. Steady green light Indicates the service processor is on. No light Indicates there is no hard drive activity. Flashing amber light Indicates there is hard drive activity. No light Indicates the port is not connected. Flashing green light Indicates there is network activity.
PAGE 139
InForm OS Version 2.3.1 Messages and Operator’s Guide 7.1.10 Supermicro II Service Processor The Supermicro II service processor LEDs are defined in the following section. The LEDs are located at the top of the service processor (Figure 7-11). Power LED Hard Disk Drive LED NIC Port 1 LED NIC Port 2 LED Overheat LED Reset Button Power Button 0802_L_R1 Figure 7-11. Supermicro II Service Processor LEDs Consult Table 7-9 to verify proper functioning of the Supermicro II service processor displays.
PAGE 140
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 7-9. Supermicro II Service Processor Front-Panel Displays (continued) LED Appearance Meaning NIC Port 1 No light Indicates the port is not connected. Steady green light Indicates the port is connected and there is network activity. Overheat Flashing green light Indicates network activity. No light Indicates the service processor temperature is normal. Steady red light Indicates the service processor is overheating.
PAGE 141
InForm OS Version 2.3.1 Messages and Operator’s Guide 8 Understanding E-Class LED Status In this chapter 8.1 Using the Component LEDs 8.2 8.1.1 Bezel LEDs 8.2 8.1.2 Removing the Bezels and Unlocking the Door 8.4 8.1.3 Drive Chassis LEDs 8.4 8.1.4 Drive Magazine LEDs 8.12 8.1.5 Controller Node LEDs 8.13 8.1.5.1 LSI Logic Fibre Channel Port LEDs 8.15 8.1.5.2 Emulex Fibre Channel Port LEDs 8.16 8.1.5.3 QLogic iSCSI Port LEDs 8.18 8.1.5.4 Gigabit Ethernet Adapter LEDs 8.19 8.1.5.
PAGE 142
Messages and Operator’s Guide InForm OS Version 2.3.1 8.2.2 Supermicro Service Processor 8.23 8.3 Securing the Storage Server 8.26 8.1 Using the Component LEDs InServ Storage Server components have LEDs to indicate that the hardware is functioning properly and to help identify errors. These LEDs serve as tools for diagnosing basic hardware problems. You can quickly identify hardware problems by simply examining the LEDs on all the components.
PAGE 143
InForm OS Version 2.3.1 Messages and Operator’s Guide Consult Table 8-1 for bezel LED meanings. Table 8-1. Bezel LED Meanings LED Appearance Meaning Fan 0 Solid green light Indicates fan is operating normally. Fan 1 Solid amber light Indicates fan error. Node 0 Flashing green light (1 blink Indicates node is fully functional and part of per second) the cluster.
PAGE 144
Messages and Operator’s Guide InForm OS Version 2.3.1 8.1.2 Removing the Bezels and Unlocking the Door WARNING: Hazardous energy is located behind the rear access door of the storage server cabinet. Use caution when working with the door open. ■ To view the drive magazine or service processor LEDs, remove the bezels. ■ To view the power supply or PDU LEDs, open the rear door by unlatching the three latches located at the top, center, and bottom of the door.
PAGE 145
InForm OS Version 2.3.1 Messages and Operator’s Guide 8.1.3.1 OPs Panel LEDs The InServ E-Class Storage Server drive chassis OPs panel has the following LEDs: Invalid Address LED Power On LED Power Supply/Cooling/ Temperature Fault LED System Fault LED 2 Gb Link Speed LED OPs Panel LEDs 0348_L_R1 Figure 8-3. Drive Chassis OPs Panel LEDs Consult Table 8-2 for OPs panel LED meanings. Using the Component LEDs 8.
PAGE 146
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 8-2. Drive Chassis OPs Panel LED Meanings LED Appearance Meaning Power On Steady Used in conjunction with Power Supply/Cooling/Temperature green light Fault LED, 2 Gb Link Speed LED, Invalid Address LED, and System Fault LED as described below: Power Steady Indicates the following: Supply/ amber light ■ Test state (5 seconds), if: Cooling/ ◆ Power On LED is steady green. Temperature ◆ System Fault LED is steady amber.
PAGE 147
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 8-2. Drive Chassis OPs Panel LED Meanings (continued) LED Appearance Meaning 2 Gb Link Steady Indicates the following: Speed LED green light ■ Test state (5 seconds), if: ◆ Power On LED is steady green. ◆ Power Supply/Cooling/Temperature Fault LED is steady amber. ■ ◆ System Fault LED is steady amber. ◆ Invalid Address LED is steady amber. 2 Gb/s drive loop is selected, if Power On LED is steady green.
PAGE 148
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 8-2. Drive Chassis OPs Panel LED Meanings (continued) LED Appearance Meaning System Fault Steady Indicates the following: LED amber light ■ Test state (5 seconds), if: ◆ Power On LED is steady green. ◆ Power Supply/Cooling/Temperature Fault LED is steady amber. ■ ■ ◆ Invalid Address LED is steady amber. ◆ 2 Gb Link Speed LED is steady amber. Processor module in FCAL failure, if: ◆ Power ON LED is steady green.
PAGE 149
InForm OS Version 2.3.1 Messages and Operator’s Guide 8.1.3.2 FCAL Module LEDs The InServ E-Class Storage Server drive chassis contains two FCAL modules. FCAL module LEDs are as follows: Host Port 0 Signal Good LED Host Port 1 Signal Good LED Module Fault LED Host Port 2 Signal Good LED Host Port 3 Signal Good LED Loops Status LED 0350_L_R1 Figure 8-4. FCAL Module LEDs Consult Table 8-3 for FCAL module LED meanings. Table 8-3.
PAGE 150
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 8-3. FCAL Module LED Meanings (continued) LED Appearance Meaning Host Port 2 Signal Good Steady green light Indicates that incoming Fibre Channel signal is good. Host Port 3 Signal Good Steady green light Indicates that incoming Fibre Channel signal is good. Loop Status Steady green light Indicates that all device ports are good at 2 Gb/s. No light Indicates that all device ports are good at 1 Gb/s. Module Fault 8.
PAGE 151
InForm OS Version 2.3.1 Messages and Operator’s Guide 8.1.3.3 Power Supply/Cooling Module LEDs The drive chassis power supplies/cooling modules have the following LEDs: DC Output Fail LED Fan Fault LED AC Input Fail LED Power Supply Good LED 0349_L_R1 Figure 8-5. Drive Chassis Power Supply/Cooling Module LEDs Consult Table 8-4 for power supply/cooling module LED meanings. Table 8-4.
PAGE 152
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 8-4. Power Supply/Cooling Module LED Meanings (continued) LED Appearance Meaning Fan Fault Steady green light Indicates the fan is operating normally. Steady amber light Indicates fan fault. Steady green light Indicates the DC output is normal. Steady amber light Indicates DC output failure. DC Output Fail 8.1.4 Drive Magazine LEDs InServ E-Class Storage Server drive magazines LEDs can be viewed at the front of the storage server.
PAGE 153
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 8-5. Drive Magazine LED Displays LED Appearance Meaning Activity Steady green light Indicates that drive power is present. Blinking green light Indicates drive activity. No light Indicates no drive is present. Steady amber light Indicates drive fault. No light Indicates the following: Fault Flashing amber ■ No drive is present. ■ Drive power is on. ■ Drive activity. Indicates the drive is bypassed by the FCAL module.
PAGE 154
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 8-6. Controller Node LED Displays LED Appearance Meaning Status Flashing green light (1 blink Indicates node is fully functional and per second) part of the cluster. Flashing amber light Indicates the node has a failed or (1 blink per second) missing power supply, fan, backup battery, or TOD battery, but the node is still operational. Steady green light Indicates node is in the process of joining the cluster.
PAGE 155
InForm OS Version 2.3.1 Messages and Operator’s Guide 8.1.5.1 LSI Logic Fibre Channel Port LEDs When present, the LSI Logic Fibre Channel adapters in the InServ E-Class Storage Server controller nodes contain Fibre Channel port LEDs. The LSI Logic adapters have two-ports. Green LED Amber LED 0257_L_R1 Figure 8-8. LSI Logic 2-Port Fibre Channel Port LEDs Each LSI Logic port in the Fibre Channel adapter have LEDs that are either off, green, or amber, depending on condition. Table 8-7 on page 8.
PAGE 156
Messages and Operator’s Guide InForm OS Version 2.3.1 8.1.5.2 Emulex Fibre Channel Port LEDs The Emulex Fibre Channel adapter contained in the controller node also contain Fibre Channel port LEDs. The two-port Emulex Fibre Channel adapters are only used in InServ E-Class Storage Servers (Figure 8-9). Node Frame Yellow 2x Green 2x (Port 1*) (Port 2*) Node Frame *These ports correspond to the numbering as reported by the InForm OS. 0269_L_R2 Figure 8-9.
PAGE 157
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 8-8.
PAGE 158
Messages and Operator’s Guide InForm OS Version 2.3.1 8.1.5.3 QLogic iSCSI Port LEDs When present, the QLogic iSCSI adapter is provided with two ports. There is one LED for each port (Figure 8-10). Green LEDs QLogic iSCSI Adapter 0351_L_R1 Figure 8-10. iSCSI Adapter Port LEDs Consult Table 8-9 table to verify the proper functioning of Gigabit Ethernet adapter LEDs. Table 8-9. iSCSI Adapter Port LED Meanings 8.
PAGE 159
InForm OS Version 2.3.1 Messages and Operator’s Guide 8.1.5.4 Gigabit Ethernet Adapter LEDs When present, the controller node Gigabit Ethernet adapter has two LEDs (Figure 8-11). Speed LED ACT/LINK LED Gigabit Ethernet Adapter 0352_L_R1 Figure 8-11. Gigabit Ethernet Adapter LEDs Consult Table 8-10 to verify the proper functioning of Gigabit Ethernet adapter LEDs. Table 8-10. Gigabit Ethernet Adapter Indicators LED Appearance Meaning ACT/LNK Steady green light Valid link partner.
PAGE 160
Messages and Operator’s Guide InForm OS Version 2.3.1 8.1.5.5 Controller Node Power Supply LEDs InServ E-Class Storage Server controller node power supply units are located on both sides of the controller nodes. Each controller node has a corresponding power supply (e.g. node 0, power supply 0; node 1, power supply 1). The battery is integral to the controller node power supply.
PAGE 161
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 8-11. Power Supply LED Displays (continued) LED Appearance Meaning AC Steady green light Indicates AC is entering from an external source. No light Indicates no AC is entering from an external source (for example, when power is off or when using battery power). Battery Status Steady green light Indicates battery A is charged. Blinking green light Battery is undergoing a test. Steady amber light Indicates battery error. 8.1.
PAGE 162
Messages and Operator’s Guide InForm OS Version 2.3.1 8.2 Service Processor LEDs 8.2.1 Wintec Service Processor The Wintec service processor LEDs are defined in this section. The LEDs are located at the top of the service processor (Figure 8-14). Power Button Reset Button Power LED NIC Port 1 LED NIC Port 2 LED Hard Disk Drive LED 0009_L_R2 Figure 8-14. Wintec Service Processor LEDs Consult Table 8-12 to verify proper functioning of the Wintec service processor displays.
PAGE 163
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 8-12. Wintec Service Processor LED Displays (continued) LED Appearance Meaning NIC Port 1 No light No network activity. Flashing amber light Indicates network activity. No light The system is off. Steady blue light Indicates that the system is powered Power on. 8.2.2 Supermicro Service Processor The Supermicro service processor LEDs are defined in the following section.
PAGE 164
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 8-13. Supermicro Service Processor Front-Panel Displays LED Appearance Meaning Power No light Indicates the service processor is off. Steady green light Indicates the service processor is on. No light Indicates there is no hard drive activity. Flashing amber light Indicates there is hard drive activity. No light Indicates the port is not connected. Flashing green light Indicates there is network activity.
PAGE 165
InForm OS Version 2.3.1 Messages and Operator’s Guide 8.2.3 Supermicro II Service Processor The Supermicro II service processor LEDs are defined in the following section. The LEDs are located at the top of the service processor. Power LED Hard Disk Drive LED NIC Port 1 LED NIC Port 2 LED Overheat LED Reset Button Power Button 0802_L_R1 Figure 8-16. Supermicro II Service Processor LEDs Consult Table 8-14 to verify proper functioning of the Supermicro II service processor displays. Table 8-14.
PAGE 166
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 8-14. Supermicro II Service Processor Front-Panel Displays (continued) LED Appearance Meaning NIC Port 1 No light Indicates the port is not connected. Steady green light Indicates the port is connected and there is network activity. Overheat Flashing green light Indicates network activity. No light Indicates the service processor temperature is normal. Steady red light Indicates the service processor is overheating.
PAGE 167
InForm OS Version 2.3.1 Messages and Operator’s Guide 9 Understanding F-Class LED Status In this chapter 9.1 Using the Component LEDs 9.2 9.1.2 Removing the Bezels and Unlocking the Door 9.4 9.1.3 Drive Chassis LEDs 9.4 9.1.4 Drive Magazine LEDs 9.12 9.1.5 Controller Node LEDs 9.14 9.1.6 3PAR Fibre Channel Port LEDs 9.16 9.1.7 QLogic iSCSI Port LEDs 9.17 9.1.8 Emulex Fibre Channel Port LEDs 9.18 9.1.9 Controller Node Power Supply LEDs 9.19 9.1.10 Power Distribution Unit Lamps 9.20 9.
PAGE 168
Messages and Operator’s Guide InForm OS Version 2.3.1 9.1 Using the Component LEDs InServ Storage Server components have LEDs to indicate that the hardware is functioning properly and to help identify errors. These LEDs serve as tools for diagnosing basic hardware problems. You can quickly identify hardware problems by simply examining the LEDs on all the components. Use the tables and diagrams in the following sections to verify the hardware is functioning properly.
PAGE 169
InForm OS Version 2.3.1 Messages and Operator’s Guide Consult Table 9-1 for bezel LED meanings. Table 9-1. Bezel LED Meanings LED Appearance Meaning Fan 0 Solid green light Indicates fan is operating normally. Solid amber light Indicates fan error. Node 0 Flashing green light (1 blink per Indicates node is fully functional and part Node 1 second) of the cluster.
PAGE 170
Messages and Operator’s Guide InForm OS Version 2.3.1 9.1.2 Removing the Bezels and Unlocking the Door WARNING: Hazardous energy is located behind the rear access door of the storage server cabinet. Use caution when working with the door open. To view the power supply or PDU LEDs, open the rear door by unlatching the three latches located at the top, center, and bottom of the door. NOTE: Many LEDs are visible without removing the bezels.
PAGE 171
InForm OS Version 2.3.1 Messages and Operator’s Guide 9.1.3.1 OPs Panel LEDs The drive chassis OPs panel has the following LEDs: Invalid Address LED Power On LED Power Supply/Cooling/ Temperature Fault LED System Fault LED 2 Gb Link Speed LED OPs Panel LEDs 0348_L_R1 Figure 9-3. Drive Chassis OPs Panel LEDs Using the Component LEDs 9.
PAGE 172
Messages and Operator’s Guide InForm OS Version 2.3.1 Consult Table 9-2 for OPs panel LED meanings. Table 9-2. Drive Chassis OPs Panel LED Meanings LED Appearance Meaning Power On Steady Used in conjunction with Power Supply/Cooling/Temperature green light Fault LED, 2 Gb Link Speed LED, Invalid Address LED, and System Fault LED as described below. Power Steady Indicates the following: Supply/ amber light ■ ◆ Power On LED is steady green. Temperature ◆ System Fault LED is steady amber.
PAGE 173
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 9-2. Drive Chassis OPs Panel LED Meanings (continued) LED Appearance Meaning 2 Gb Link Steady Indicates the following: Speed LED green light ■ Test state (5 seconds), if: ◆ Power On LED is steady green. ◆ Power Supply/Cooling/Temperature Fault LED is steady amber. ■ Flashing ◆ System Fault LED is steady amber. ◆ Invalid Address LED is steady amber. 2 Gb/s drive loop is selected, if Power On LED is steady green.
PAGE 174
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 9-2. Drive Chassis OPs Panel LED Meanings (continued) LED Appearance Meaning System Fault Steady Indicates the following: LED amber light ■ Test state (5 seconds), if: ◆ Power On LED is steady green. ◆ Power Supply/Cooling/Temperature Fault LED is steady amber. ■ ■ ◆ Invalid Address LED is steady amber. ◆ 2 Gb Link Speed LED is steady amber. Processor module in FCAL failure, if: ◆ Power ON LED is steady green.
PAGE 175
InForm OS Version 2.3.1 Messages and Operator’s Guide 9.1.3.2 Interface Card LEDs The drive chassis contains two interface cards, FCAL-A and FCAL-B. Interface card LEDs are as follows: Host Port 0 Signal Good LED Host Port 1 Signal Good LED Module Fault LED Host Port 2 Signal Good LED Host Port 3 Signal Good LED Loops Status LED 0350_L_R1 Figure 9-4. Interface Card LEDs Consult Table 9-3 for interface card LED meanings. Table 9-3.
PAGE 176
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 9-3. Interface Card LED Meanings (continued) LED Appearance Meaning Host Port 2 Signal Good Steady green light Indicates the incoming Fibre Channel signal is good. Host Port 3 Signal Good Steady green light Indicates the incoming Fibre Channel signal is good. Loop Status Steady green light Indicates all device ports are good at 2 Gb/s. No light Indicates all device ports are good at 1 Gb/s.
PAGE 177
InForm OS Version 2.3.1 Messages and Operator’s Guide 9.1.3.3 Power Supply/Cooling Module LEDs The F-Class Storage Server drive chassis power supplies/cooling modules have the following LEDs: DC Output Fail LED Fan Fault LED AC Input Fail LED Power Supply Good LED 0349_L_R1 Figure 9-5. Drive Chassis Power Supply/Cooling Module LEDs Consult Table 9-4 for power supply/cooling module LED meanings. Table 9-4.
PAGE 178
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 9-4. Drive Chassis Power Supply/Cooling Module LED Meanings (continued) LED Appearance Meaning AC Input Fail Steady green light Indicates the AC input is normal. Steady amber light Indicates AC input failure. Steady green light Indicates the fan is operating Fan Fault normally. DC Output Fail Steady amber light Indicates fan fault. Steady green light Indicates the DC output is normal.
PAGE 179
InForm OS Version 2.3.1 Messages and Operator’s Guide Consult Table 9-5 for drive magazine LED meanings. Table 9-5. Drive Magazine LED Displays LED Appearance Meaning Activity Steady green light Indicates the drive power is present. Blinking green light Indicates drive activity. Slowly blinking green Indicates the drive has spun down. light (once every 3 seconds) Fault No light Indicates a drive is not present. Steady amber light Indicates drive fault.
PAGE 180
Messages and Operator’s Guide InForm OS Version 2.3.1 9.1.5 Controller Node LEDs Depending upon the configuration, storage servers contain two or four controller nodes, all located in the storage server chassis. Controller nodes contain the following LEDs (Figure 9-7): Ethernet 10/100/1000 Mbps LED Disk Hot-plug LED Node Hot-plug LED Ethernet LED Activity Node Status LED 0684_L_R1 Figure 9-7. Controller Node LEDs Consult Table 9-6 to verify proper functioning of controller nodes. Table 9-6.
PAGE 181
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 9-6. Controller Node LED Displays (continued) LED Appearance Meaning Node Hot-plug Steady amber light In combination with the Status LED blinking green three times per second, indicates the controller node is prepared for removal. In combination with the Status LED being solid, indicates a fatal node failure. No light Indicates the node is not prepared for removal.
PAGE 182
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 9-6. Controller Node LED Displays (continued) LED Appearance Meaning Ethernet activity Steady green light Indicates an Ethernet link. Flashing green light Indicates no Ethernet activity. No light Indicates no Ethernet connection. Steady amber light 1000 Mb/sec mode. Steady green light 100 Mb/sec mode. No light 10 Mb/sec mode (or disconnected). Ethernet 10/100/1000 MB/sec 9.1.
PAGE 183
InForm OS Version 2.3.1 Messages and Operator’s Guide 9.1.7 QLogic iSCSI Port LEDs The QLogic iSCSI adapter contains two ports. There is one LED for each port as shown Figure 9-9. LEDs (2x) Port 1 Port 2 0721_L_R1 Figure 9-9. iSCSI Adapter Port LEDs Consult Table 9-8 for iSCSI adapter port LED meanings. Table 9-8. iSCSI Adapter Port LED Meanings LED Condition Port Status Steady green Indicates a link is established. Flashing green Indicates receiving or transmitting activity.
PAGE 184
Messages and Operator’s Guide InForm OS Version 2.3.1 9.1.8 Emulex Fibre Channel Port LEDs The Emulex Fibre Channel adapter contained in the controller node also contain Fibre Channel port LEDs. Two port Emulex Fibre Channel adapters are only used in an InServ F-Class Storage Server (Figure 9-10). Node Frame Yellow 2x Green 2x (Port 1*) (Port 2*) Node Frame *These ports correspond to the numbering as reported by the InForm OS. 0269_L_R2 Figure 9-10.
PAGE 185
InForm OS Version 2.3.1 Messages and Operator’s Guide 9.1.9 Controller Node Power Supply LEDs F-Class Storage Server 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 as follows: AC LED Power Supply Status LED Battery Status LED 0353_L_R1 Figure 9-11. Controller Node Power Supply LEDs Consult Table 9-10 for node power supply LED meanings.
PAGE 186
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 9-10. Power Supply LED Displays (continued) LED Appearance Meaning AC Steady green light Indicates AC is entering from an external source. No light Indicates no AC is entering from an external source (for example, when power is off or when using battery power). Battery Status Steady green light Indicates the battery is charged. Blinking green light Battery is undergoing a test. Steady amber light Indicates battery error 9.1.
PAGE 187
InForm OS Version 2.3.1 Messages and Operator’s Guide 9.2 Service Processor LEDs 9.2.1 Supermicro Service Processor The Supermicro service processor LEDs are defined in the following section. The LEDs are located at the top of the service processor (Figure 9-13). Power Button Reset Button Power LED Hard Disk Drive LED NIC Port 1 LED NIC Port 2 LED Overheat LED 0637_L_R1 Figure 9-13. Supermicro Service Processor LEDs Consult Table 9-11 to verify proper functioning of service processor displays.
PAGE 188
Messages and Operator’s Guide InForm OS Version 2.3.1 Table 9-11. Supermicro Service Processor Front-Panel Displays (continued) LED Appearance Meaning NIC Port 1 No light Indicates the port is not connected. Steady green light Indicates the port is connected. Flashing green light Indicates there is network activity. No light Indicates the service processor temperature Overheat is normal. Steady red light Indicates the service processor temperature is overheating. 9.2.
PAGE 189
InForm OS Version 2.3.1 Messages and Operator’s Guide Consult Figure 9-14 to verify proper functioning of service processor displays. Table 9-12. Supermicro II Service Processor Front-Panel Displays LED Appearance Meaning Power No light Indicates the service processor is off. Steady green light Indicates the service processor is on. No light Indicates there is no hard drive activity. Flashing amber light Indicates there is hard drive activity. No light Indicates the port is not connected.
PAGE 190
Messages and Operator’s Guide InForm OS Version 2.3.1 9.3 Securing the Storage Server 1 After verifying that the storage server is functioning properly, secure the system. 2 Close the rear door and lock it with the keys provided with the storage server. WARNING: Hazardous energy is located behind the rear access door of the storage server cabinet. Use caution when working with the door open. 9.
PAGE 191
InForm OS Version 2.3.1 Messages and Operator’s Guide 10 Power Off/On Procedures In this chapter 10.1 Powering Off the Storage Server 10.1 10.2 Powering On the Storage Server 10.4 10.1 Powering Off the Storage Server The following procedure describes how to safely remove power from the InServ Storage Server and Service Processor. NOTE: PDUs in any expansion cabinets connected to the InServ Storage Server may need to be shut off. Use the locatesys command to identify all connected cabinets.
PAGE 192
Messages and Operator’s Guide InForm OS Version 2.3.1 5 Select option 6, Halt an InServ cluster/node. 6 Select the desired InServ Storage Server. 7 Select option a, all and respond to the confirmation prompts. 8 Press X to return to the 3PAR Service Processor Menu. The InServ Storage Server will now shutdown and halt. This may take several minutes.
PAGE 193
InForm OS Version 2.3.1 Messages and Operator’s Guide Hot-Plug LED Node Status LED 0294_L_R1 Figure 10-2. InServ S-Class Storage Server Hot-Plug LED and Node Status LED Disk Hot-plug LED 0683_L_R1 Node Hot-plug LED Node Status LED Figure 10-3. InServ F-Class Storage Server Hot-Plug LED and Node Status LED Powering Off the Storage Server 10.
PAGE 194
Messages and Operator’s Guide InForm OS Version 2.3.1 Hot-Plug LED Status LED 0361_L_R1 Figure 10-4. InServ E-Class Hot-Plug LED and Node Status LED 10 From the spmaint main menu: a Select option 1, SP Control/Status. b Select option 3, Halt SP and confirm all prompts to halt the SP. 11 Verify that the power LED on the front of the service processor is no longer illuminated. 12 Remove AC to the storage server by turning off the PDU circuit breakers of ALL four PDUs in the cabinet (Figure 10-5).
PAGE 195
InForm OS Version 2.3.1 Messages and Operator’s Guide 2 Verify that the blue LED on the front of the service processor is illuminated.
PAGE 196
Messages and Operator’s Guide InForm OS Version 2.3.1 Disk Status LEDs Hot-Plug LED 3 2 1 0 ! DC2 (SATA Drive) Drive Magazine Status LED DC2 0518_L_R1 Figure 10-7. DC2 LEDs on the InServ S-Class Storage Server Drive Cage Activity (Green) LED Fault (Amber) LED 0149_L_R3 Figure 10-8. DC3 LEDs on the InServ E-Class and F-Class Storage Server Drive Cage 10.
PAGE 197
InForm OS Version 2.3.1 Messages and Operator’s Guide 11 Troubleshooting In this chapter 11.1 Overview 11.1 11.2 The checkhealth Command 11.2 11.3 Using the checkhealth Command 11.2 11.4 Troubleshooting InServ Storage Server Components 11.4 This chapter provides information about troubleshooting an InServ Storage Server with the checkhealth InForm CLI command. 11.
PAGE 198
Messages and Operator’s Guide InForm OS Version 2.3.1 11.2 The checkhealth Command COMMAND checkhealth DESCRIPTION The checkhealth command checks and then displays the status of system hardware and software components. SYNTAX checkhealth [ | ...] AUTHORITY Super, Service OPTIONS -list Lists all components that checkhealth can analyze. -quiet Does not display which component is currently being checked. -detail Displays detailed information regarding the status of the system.
PAGE 199
InForm OS Version 2.3.1 Messages and Operator’s Guide CLI% checkhealth -detail Checking alert Checking cage Checking date Checking ld Checking license Checking network Checking node Checking pd Checking port Checking rc 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.
PAGE 200
Messages and Operator’s Guide InForm OS Version 2.3.1 Checking node Checking pd The following components are healthy: node, pd 11.4 Troubleshooting InServ Storage Server Components Use the checkhealth -list command to list all the components that can be analyzed by the checkhealth command. For detailed troubleshooting information about specific components, examples, and suggested actions for correcting issues with components, click on the component name in Table 11-1. Table 11-1.
PAGE 201
InForm OS Version 2.3.1 Messages and Operator’s Guide Table 11-1. Component Functions Component Function Task Displays failed tasks. VLUN Displays inactive VLUNs and those which have not been reported by the host agent. VV Displays VVs that are not optimal. The following sections provide details about troubleshooting specific components. 11.4.1 Alert Displays any unresolved alerts. Shows any alerts that would be seen by showalert -n. 11.4.1.
PAGE 202
Messages and Operator’s Guide ■ SFP signal levels (RX power low and TX failure) ■ power supplies ■ cage firmware (is not current) InForm OS Version 2.3.1 Reports if a servicecage operation has been started and has not ended. 11.4.2.
PAGE 203
InForm OS Version 2.3.1 Messages and Operator’s Guide ----------------------------------SFP Info----------------------------------FCAL SFP -State- --Manufacturer-- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM 0 0 OK FINISAR CORP. 4.1 No No Yes Yes 1 1 OK FINISAR CORP. 4.
PAGE 204
Messages and Operator’s Guide RX Power uW InForm OS Version 2.3.1 0 15 794 10* 1259 ---------Cage 4 Fcal 1 SFP 1 DDM----------Warning- --Alarm---Type-- Units Reading Low High Low High Temp C 31 -20 90 -25 95 Voltage mV 3140 2900 3700 2700 3900 TX Bias mA 8 2 14 1 17 TX Power uW 404 79 631 67 631 RX Power uW 402 15 794 10 1259 11.4.2.
PAGE 205
InForm OS Version 2.3.1 Messages and Operator’s Guide VendorId,ProductId 3PARdata,DC2 Unique_ID 10320300000AD000 Power Supply Info State Fan State AC Model ps0 Failed OK Failed POI
PAGE 206
Messages and Operator’s Guide InForm OS Version 2.3.1 Product_Rev 2.
PAGE 207
InForm OS Version 2.3.1 Messages and Operator’s Guide cli% showcage -d cage3 Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 3 cage3 2:0:4 0 3:0:4 0 32 29-41 2.36 2.36 DC2 n/a -----------Cage detail info for cage3 --------. . . -----------Midplane Info----------Firmware_status Old Product_Rev 2.36 State Normal Op Loop_Split 0 VendorId,ProductId 3PARdata,DC2 Unique_ID 10320300000AD100 cli% showfirmwaredb Vendor Prod_rev Dev_Id ... 3PARDATA [2.
PAGE 208
Messages and Operator’s Guide InForm OS Version 2.3.1 Interface Board Info FCAL0 FCAL1 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 Green,Off ... cli% showcage -sfp -d cage4 --------Cage 4 FCAL 0 SFP 0-------Cage ID : 4 Fcal ID : 0 SFP ID : 0 State : OK Manufacturer : SIGMA-LINKS Part Number : SL5114A-2208 Serial Number : U260651461 Revision : 1.4 MaxSpeed(Gbps) : 2.
PAGE 209
InForm OS Version 2.3.1 Messages and Operator’s Guide 11.4.2.12 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 3PAR 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.
PAGE 210
Messages and Operator’s Guide InForm OS Version 2.3.1 11.4.3.1 Format of Possible Date Exception Messages Date -- "Date is not the same on all nodes" 11.4.3.2 Date Example Component -Identifier- -----------Description----------Date -Date is not the same on all nodes 11.4.3.3 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.
PAGE 211
InForm OS Version 2.3.1 Messages and Operator’s Guide LD ld: "LD has reduced availability. Current: , Configured: " LD ld: "LD does not have a backup" LD ld: "LD does not have owner and backup" LD ld: "A logging LD is not 20G in size" LD -- "Number of logging LD's does not match number of nodes in the cluster" LD -- "Preserved data storage space does not equal total node's Data memory" 11.4.4.
PAGE 212
Messages and Operator’s Guide InForm OS Version 2.3.1 down condition, when node batteries are not working, or where disk redundancy is not optimal. cli% showld Ten* Id Name RAID -Detailed_State- Own SizeMB UsedMB Use Lgct LgId WThru MapV 91 Ten.usr.3 0 normal 1/0/3/2 13824 0 V 0 --N N 92 Ten.usr.12 0 normal 2/3/0/1 28672 0 V 0 --Y N cli% showldch Ten.usr.
PAGE 213
InForm OS Version 2.3.1 LD Messages and Operator’s Guide -- Preserved data storage space does not equal total node's Data memory 11.4.4.9 LD Suggested Action 4 Preserved data LDs (pdsld's) are created during system initialization (OOTB) and after some hardware upgrades (via admithw). The total size of the pdsld's should match the total size of all data-cache in the InServ Storage Server (see below).
PAGE 214
Messages and Operator’s Guide InForm OS Version 2.3.1 11.4.6 Network Displays Ethernet issues for the Administrative and Remote Copy over IP (RCIP) networks. ■ Check if the number of collisions is > 5% of total packets. ■ Check for Ethernet errors and transmit (TX) or receive (RX) errors. 11.4.6.1 Format of Possible Network Exception Messages Network -- "IP address change has not been completed" Network "Node:" "Errors detected on network" 11.4.6.
PAGE 215
InForm OS Version 2.3.1 Messages and Operator’s Guide MAC Address: 00:02:AC:25:04:03 RX Packets: 1225109 RX Bytes: 1089073679 RX Errors: 0 RX Dropped: 0 RX FIFO Errors: 0 RX Frame Errors: 60 RX Multicast: 0 RX Compressed: 0 TX TX TX TX TX TX TX TX Packets: Bytes: Errors: Dropped: FIFO Errors: Collisions: Carrier Errors: Compressed: 550205 568149943 0 0 0 0 0 0 11.4.7 Node Displays node conditions that are not optimal. ■ Checks if node batteries have been tested in the last 30 days.
PAGE 216
Messages and Operator’s Guide InForm OS Version 2.3.1 11.4.7.4 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.
PAGE 217
InForm OS Version 2.3.
PAGE 218
Messages and Operator’s Guide InForm OS Version 2.3.1 Examine the date of the last successful test of that battery. Assuming the comment date was 2009-10-14, the last battery test on Node 0, PS 1, Bat 0 was 2009-09-10, which is more than 30 days in the past.
PAGE 219
InForm OS Version 2.3.1 PD Messages and Operator’s Guide disk:107 Detailed State: failed,notready,missing_A_port 11.4.8.3 PD Suggested Action 1 Both degraded and failed disks show up in this report. When a FC path to a drive cage is not working, all disks in the cage will have a state of Degraded due to the nonredundant condition. Use commands such as showpd, showpd -s, showcage, showcage -d, showport -sfp, etc., to diagnose further.
PAGE 220
Messages and Operator’s Guide InForm OS Version 2.3.1 -------------Drive Info------------Drive NodeWWN LED Temp(C) 0:0 20000014c3b3eab9 Green 34 0:1 20000014c3b3e708 Green 36 ----LoopA----ALPA LoopState 0xe1 OK 0xe0 OK ----LoopB----ALPA LoopState 0xe1 Loop fail 0xe0 Loop fail 11.4.8.4 PD Example 2 Component --Identifier-- --------------Description--------------PD -There is an imbalance of active pd ports 11.4.8.
PAGE 221
InForm OS Version 2.3.1 50 3:0:2 51 3:0:3 Messages and Operator’s Guide FC FC degraded 2:0:4 degraded 2:0:4 3:0:4\missing 2/3:0:4\missing 2/- cli% showcage -d cage3 Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 3 cage3 2:0:4 0 --0 32 29-41 2.37 2.
PAGE 222
Messages and Operator’s Guide InForm OS Version 2.3.1 a problem, but it could negatively affect system performance. The IOPS thresholds currently set for this condition are as follows: ■ NL disks > 75 ■ FC 10K RPM disks > 150 ■ FC 15K RPM disks > 200 ■ SSD > 1500 Operations such as servicemag and tunevv can cause this condition.
PAGE 223
InForm OS Version 2.3.1 Messages and Operator’s Guide 11.4.8.10 PD Example 5 Component --Identifier-- -------Description---------- PD -- Sparing Algorithm is not set 11.4.8.11 PD Suggested Action 5 Check the system’s Sparing Algorithm value using the CLI command showsys -param. The value is normally set during the initial installation (OOTB). If it must be set later, use the command setsys SparingAlgorithm; valid values are Default, Minimal, Maximal, and Custom.
PAGE 224
Messages and Operator’s Guide InForm OS Version 2.3.1 Port port: "There is less than one week of LESB history for this port" Port port: "Port or devices attached to port have experienced CRC errors within ____________the last day" Port port: "CRC errors have been increasing by more than one per day over the ____________past week" 11.4.9.
PAGE 225
InForm OS Version 2.3.
PAGE 226
Messages and Operator’s Guide InForm OS Version 2.3.1 11.4.9.6 Port Suggested Action 2 FC node-ports that normally contain SFPs will report an error if the SFP has been removed. The condition can be checked using the showport -sfp command. In this example, the SFP in 0:3:1 has been removed from the adapter: cli% showport N:S:P -State0:0:1 OK 0:0:2 OK 0:3:1 0:3:2 OK -sfp -Manufacturer- MaxSpeed(Gbps) TXDisable FINISAR_CORP. 2.1 No FINISAR_CORP. 2.1 No - FINISAR_CORP. 2.
PAGE 227
InForm OS Version 2.3.1 Messages and Operator’s Guide 11.4.9.11 Port Example 5 Component -----------Description------------------------- Qty Port Ports with increasing CRC error counts 2 Component -Identifier- ------Description----------Port port:3:2:1 Port or devices attached to port have experienced CRC _______________________errors within the last day 11.4.9.12 Port Suggested Action 5 Check the fibre channel error counters for the port using the CLI commands showportlesb single and showportlesb hist.
PAGE 228
Messages and Operator’s Guide InForm OS Version 2.3.1 11.4.9.15 Port Example 7 Component ------------Description------------ Qty Port Ports with mismatched mode and type 1 Component -Identifier- ------Description------Port port:2:0:3 Mismatched mode and type 11.4.9.16 Port Suggested Action 7 This output indicates that the port's mode, such as an initiator or target, is not correct for the connection type, such as disk, host, iscsi or rcfc.
PAGE 229
InForm OS Version 2.3.1 Messages and Operator’s Guide 11.4.10.1 Format of Possible RC Exception Messages RC RC RC RC RC RC rc: "All links for target are down but target not yet marked failed." rc: "Target has failed." rc: "Link of target is down." rc: "Group is not started to target ." rc: "VV of group is stale on target ." rc: "VV of group is not synced on target ." 11.4.
PAGE 230
Messages and Operator’s Guide InForm OS Version 2.3.1 11.4.12.1 Format of Possible Task Exception Messages Task Task: Task failure description 11.4.12.2 Task Example Component --Identifier--- -------Description-------Task Task:6313 Failed Task For this example, checkhealth also showed an Alert; this task failed because the command was entered with a syntax error: Alert sw_task:6313 Task 6313 (type 'background_command', name 'upgradecage -a -f') has failed (Task Failed).
PAGE 231
InForm OS Version 2.3.1 vlun Messages and Operator’s Guide host:cs-wintec-test1 Host wwn:10000000C964121D is not connected to a port 11.4.13.3 VLUN Suggested Action Check the export status and port status for the VLUN and HOST with CLI commands such as showvlun, showvlun -pathsum, showhost, showhost pathsum, showport, servicehost list, etc.
PAGE 232
Messages and Operator’s Guide InForm OS Version 2.3.1 11.4.14.2 VV Suggested Action Check status with CLI commands such as showvv, showvv -d, showvv -cpg. 11.
PAGE 233
InForm OS Version 2.3.1 Messages and Operator’s Guide 12 Alerts In this chapter 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 3PAR InForm OS Concepts Guide. To view the alerts in the events log, use the showeventlog command.
PAGE 234
Messages and Operator’s Guide 12.2 InForm OS Version 2.3.1 0x60002 12.16 0x60003 12.17 0x60007 12.18 0x60008 12.19 0x60009 12.20 0x600de 12.21 0x600fa 12.27 0x70001 12.33 0x70002 12.34 0x90001 12.35 0x900fa 12.36 0xa0001 12.37 0xa0002 12.38 0xc0002 12.39 0xd0002 12.40 0xe0001 12.41 0xe0002 12.42 0xe0003 12.44 0xe0005 12.45 0xe0006 12.46 0xe0007 12.47 0xe0008 12.48 0xe0009 12.49 0xe000a 12.50 0xe000b 12.
PAGE 235
InForm OS Version 2.3.1 Messages and Operator’s Guide 0xe000c 12.52 0xe000d 12.53 0xe000e 12.54 0x110001 12.55 0x110002 12.56 0x110004 12.57 0x130001 12.58 0x140001 12.59 0x150002 12.60 0x150006 12.61 0x15000c 12.62 0x170001 12.64 0x170002 12.65 0x1a0002 12.66 0x1a0005 12.67 0x1a0006 12.68 0x1a0007 12.69 0x1a0008 12.70 0x1a00de 12.73 0x1a00fa 12.75 0x1b00de 12.78 0x1b00fa 12.80 0x1e0001 12.82 0x1e0002 12.92 0x1e0004 12.93 0x1e0005 12.94 12.
PAGE 236
Messages and Operator’s Guide 12.4 InForm OS Version 2.3.1 0x1e00de 12.95 0x1e00fa 12.97 0x1f0001 12.99 0x1f000de 12.100 0x1f000fa 12.106 0x200009 12.112 0x210001 12.113 0x220001 12.114 0x2200de 12.115 0x2200fa 12.116 0x230003 12.117 0x230004 12.118 0x230005 12.119 0x240001 12.120 0x250002 12.121 0x270001 12.122 0x270002 12.123 0x270003 12.124 0x270004 12.125 0x270005 12.126 0x270006 12.127 0x270007 12.128 0x270008 12.129 0x270009 12.130 0x27000e 12.
PAGE 237
InForm OS Version 2.3.1 Messages and Operator’s Guide 0x270010 12.133 0x270011 12.134 0x270012 12.135 0x270013 12.136 0x270014 12.137 0x270015 12.138 0x270016 12.139 0x270017 12.140 0x270050 12.141 0x280001 12.142 0x280002 12.143 0x2900de 12.144 0x2b00de 12.145 0x2b00fa 12.146 0x2d00de 12.149 0x2d00fa 12.151 0x3500de 12.153 0x3500fa 12.154 0x3700de 12.155 0x3700fa 12.157 0x3800de 12.158 0x3900fa 12.160 0x3a00de 12.162 0x3a00fa 12.163 0x450001 12.164 12.
PAGE 238
Messages and Operator’s Guide 0x460001 12.6 InForm OS Version 2.3.1 12.
PAGE 239
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x10001 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.
PAGE 240
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x30001 TYPE Firmware coredump event MESSAGE Firmware COREDUMP: recovered file 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. 12.
PAGE 241
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x300de TYPE Component state change MESSAGE Port Node Slot Degraded () STATE 1 Intermittent CRC Errors Detected SUGGESTED ACTION Replace the fibre channel cable. If the problem persists after cable replacement, contact your local service provider for technical support and services.
PAGE 242
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x300fa 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 InForm OS.
PAGE 243
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x40003 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. 12.
PAGE 244
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x400fa 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.
PAGE 245
InForm OS Version 2.3.1 Messages and Operator’s Guide Contact your local service provider for technical support and services. STATE 3 Snapdata Invalid SUGGESTED ACTION The VV specified in the alert has snapshots that cannot be started up because the snapshot data is invalid. Contact your local service provider for technical support and services. STATE 4 Preserved SUGGESTED ACTION The VV specified in the alert is in a cache-preserved mode because there are some I/O errors on the underlying LDs.
PAGE 246
Messages and Operator’s Guide InForm OS Version 2.3.1 SUGGESTED ACTION The VV specified in the alert was specified as the target of a physical copy, and the copy process failed. The task data for the physical copy should have more information on why the failure occurred. Use the CLI command showtask to look at task data. Contact your local service provider for technical support and services. 12.
PAGE 247
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x50005 TYPE Ldsk has failed set 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 Ensure there are no logging chunklets or failed/degraded disks. 2 If the RAID set is still stale, fix the issue that caused the to go stale. 3 Remove the Log Ld using the removeld -rmsys command.
PAGE 248
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x60002 TYPE Disk monitor stopped MESSAGE Pd WWN (disk_WWN) has failed for too long. Disk monitoring has stopped on this disk SUGGESTED ACTION Replace this disk. Contact your local service provider for technical support and services. 12.
PAGE 249
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x60003 TYPE Invalid PD configuration MESSAGE Disk (wwn ) is showing up with two wwns on port - and SUGGESTED ACTION The disk identified in the message is presenting itself to the system in an unexpected way. Contact your local service provider for technical support and services. 12.
PAGE 250
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x60007 TYPE Disk overtemp alert MESSAGE 1 PD (wwn ) is overtemp ( 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, and 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.
PAGE 251
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x60008 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 has above normal temperature. Run CLI commands showpd -s, showpd -e, and 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. 12.
PAGE 252
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x60009 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, and showcage -d to confirm. Check the data center room to verify it is at an optimal temperature.
PAGE 253
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x600de TYPE Component State Change MESSAGE PD 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.
PAGE 254
Messages and Operator’s Guide InForm OS Version 2.3.1 If this is not because of a service action, please contact your local service provider for further information. STATE 5 Not Ready SUGGESTED ACTION The PD specified in the alert has reported it being not ready. 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. If the error persists, contact your local service provider for technical support and services.
PAGE 255
InForm OS Version 2.3.1 Messages and Operator’s Guide If the disk has disappeared from the B loop,it reports its B loop as missing. This could also occur because of a servicemag operation or a controlmag offloop operation. Contact your local service provider for technical support and services. STATE 9 Relocating SUGGESTED ACTION This is only an activity flag which refers to the fact that chunklets from the disk are relocating.
PAGE 256
Messages and Operator’s Guide InForm OS Version 2.3.1 SUGGESTED ACTION Cage Report is missing a PD. No action required. STATE 14 New Offloop SUGGESTED ACTION The drive was issued a command by the Sysmgr to take a PD offloop. No action required. STATE 15 New Onloop 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.
PAGE 257
InForm OS Version 2.3.1 Messages and Operator’s Guide 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 22 Drive Not Ready SUGGESTED ACTION The PD is not ready at this time. No action required.
PAGE 258
Messages and Operator’s Guide InForm OS Version 2.3.1 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. 12.
PAGE 259
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x600fa TYPE Component state change 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.
PAGE 260
Messages and Operator’s Guide InForm OS Version 2.3.1 SUGGESTED ACTION The PD specified in the alert has been marked failed because a command sent to check if disk is ready has failed. Use the CLI command showpd to confirm the disk is still in this state. The failure could be intermittent and a retry might fix it. As above, the suggested action is to wait for a few minutes to see if the alert is auto-fixed. If not, contact your local service provider for possible disk replacement.
PAGE 261
InForm OS Version 2.3.1 Messages and Operator’s Guide STATE 7 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. Use the CLI command showpd to confirm the disk is still in this state. If the error is persistent, contact your local service provider for possible disk replacement.
PAGE 262
Messages and Operator’s Guide InForm OS Version 2.3.1 SUGGESTED ACTION The PD specified in the alert has been marked failed because it has unsupported drive firmware on it. Use the CLI command showpd to confirm the disk is still in this state. Contact your local service provider to reload the correct firmware on the disk. STATE 12 Invalid Block Size SUGGESTED ACTION The PD specified in the alert has been marked failed because it is reporting an unsupported block size.
PAGE 263
InForm OS Version 2.3.1 Messages and Operator’s Guide 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. Please 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.
PAGE 264
Messages and Operator’s Guide InForm OS Version 2.3.1 STATE 20 Media Failed SUGGESTED ACTION A disk will be marked media-failed if a hardware error or a device is bad error is reported by the disk. Contact your local service provider to replace the disk. 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 to replace the disk.
PAGE 265
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x70001 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.
PAGE 266
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x70002 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.
PAGE 267
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x90001 TYPE Host configuration error MESSAGE Host persona is incompatible with port persona 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. 12.
PAGE 268
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x900fa 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. 12.
PAGE 269
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0xa0001 TYPE Snap Admin Volume low on space MESSAGE Snap Admin volume , id (kernel ID ) low on space, l2bmap % allocated SUGGESTED ACTION If VV is TPVV or CPVV then sysmgr will auto-grow SA/SD accordingly. No user action is required. If VV is regular VV, the user needs to grow SA/SD accordingly by using the CLI command growaldvv so the snapshot won’t become stale. 12.
PAGE 270
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0xa0002 TYPE Snap Data Volume low on space MESSAGE Snap Data volume , id (kernel ID ) low on space, l2bmap % allocated SUGGESTED ACTION If VV is regular VV, the user needs to grow SA/SD accordingly by using the CLI command growaldvv so the snapshot won’t become stale. 12.
PAGE 271
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0xc0002 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. 12.
PAGE 272
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0xd0002 TYPE PR transition MESSAGE The PR is currently getting data from the local disk 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.
PAGE 273
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0xe0001 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. 12.
PAGE 274
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0xe0002 TYPE System manager cannot start up 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.
PAGE 275
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE 4 Cannot reach TOC quorum for TOC . Use setsysmgr to set system manager startup state. SUGGESTED ACTION The specified TOC generation number cannot be found on 60% of the physical disks. If that many physical disks are up and in a valid state, you can force the system to use a specific TOC generation number using setsysmgr tocgen .
PAGE 276
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0xe0003 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. 12.
PAGE 277
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0xe0005 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.
PAGE 278
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0xe0006 TYPE System recovery notification about bad volume MESSAGE Use the “setsysmgr force_iderecovery” CLI command to start pfailrecovery. This will cause loss of data for volume with id . SUGGESTED ACTION Use the CLI command setsysmgr force_iderecovery to cause powerfail recovery to resume. WARNING: This can cause data loss for the volumes indicated by the ID in the Message. 12.
PAGE 279
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0xe0007 TYPE Pfail partition needs to be wiped MESSAGE Use the “setsysmgr force_idewipe” CLI command to wipe pfail partition and restart the system. This can 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. 12.
PAGE 280
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0xe0008 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. 12.
PAGE 281
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0xe0009 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.
PAGE 282
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0xe000a TYPE Task failed MESSAGE Task has failed with a failure code of . 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. 12.
PAGE 283
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0xe000b 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. 12.
PAGE 284
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0xe000c 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. 12.
PAGE 285
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0xe000d TYPE System recovery stalled due to unknown replicant state MESSAGE System recovery stalled due to unknown replicant state on node for replicant . SUGGESTED ACTION Contact your local service provider for technical support and services. 12.
PAGE 286
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0xe000e TYPE System recovery stalled due to sole owner of LD missing MESSAGE System recovery stalled due to sole owner of LDs . Current online: , original online: . SUGGESTED ACTION Contact your local service provider for technical support and services. 12.
PAGE 287
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x110001 TYPE Errors accessing the internal drive MESSAGE Filesystem on node has transitioned to read-only. SUGGESTED ACTION The file system identified on the node has transitioned to read-only mode in response to errors from that node’s internal drive. The node is now a candidate for automatic shutdown by the system unless shutting it down leads to a loss of system availability.
PAGE 288
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x110002 TYPE Internal drive 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 though of internal drive errors because it is the last node left alive. MESSAGE 3 Node is not being shutdown by the system though of internal drive errors because some LDs cannot be served by the remaining nodes.
PAGE 289
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x110004 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. 12.
PAGE 290
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x130001 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. 12.
PAGE 291
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x140001 TYPE Notification MESSAGE 1 Media error fix on PD : failed- SUGGESTED ACTION For media error corrective action alerts, inform your local service provider with the alert information.
PAGE 292
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x150002 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.
PAGE 293
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x150006 TYPE Authentication failure MESSAGE authentication failures in secs SUGGESTED ACTION The CLI server cannot communicate with the system manager, which will lead to the failure of most CLI commands. This alert is likely due to an unexpected system failure. Contact your local service provider for technical support and services. 12.
PAGE 294
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x15000c 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.
PAGE 295
InForm OS Version 2.3.
PAGE 296
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x170001 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. 12.
PAGE 297
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x170002 TYPE TOC update failure MESSAGE System is entering powerfail mode because it failed to find a quorum of disks to write the TOC. SUGGESTED ACTION The system was unable to save configuration information to a quorum of disks. It will now go into powerfail mode. 12.
PAGE 298
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x1a0002 TYPE Node is down MESSAGE Node is offline SUGGESTED ACTION The node shown in the message has left the cluster. It should rejoin automatically. If the node leaving was unexpected, contact your local service provider for technical support and services. 12.
PAGE 299
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x1a0005 TYPE HW: CPU Memory Correctable ECC MESSAGE Node DIMM (DIMM_socket) Correctable ECC error rate too high. Replace DIMM. SUGGESTED ACTION Replace the DIMM. Contact your local service provider for technical support and services. 12.
PAGE 300
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x1a0006 TYPE CPU Configuration MESSAGE Node Expected CPUs Found CPUs SUGGESTED ACTION A CPU is either bad or missing. Replace the node motherboard. Contact your local service provider for technical support and services. 12.
PAGE 301
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x1a0007 TYPE BIOS internal drive log entry MESSAGE BIOS internal drive log entry stored at 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.
PAGE 302
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x1a0008 TYPE Node environmental MESSAGE Node#: : : , hi_limit: , lo_limit: Where: is: Table 12-1. 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 12-2. 12.
PAGE 303
InForm OS Version 2.3.1 Messages and Operator’s Guide , , , are: Table 12-3. Measurement CPU0 1.32V: CPU1 1.32V: 82563 1.20V: 31154 1.30V: 82563 1.90V: 3.30V: PLX 3.30V: VCC 5.00V: V_PTT 1.20V: MCH 1.50V: ESB 1.50V: FBD 1.50V: FBD 1.80V: VTT_FBD 0.90V: ESB 1.20V: PLX 1.00V: Osprey DDR 1.25V: Osprey DDR 2.50V: Osprey Lnk 1.87V: FPGA 2.50V: 12.
PAGE 304
Messages and Operator’s Guide InForm OS Version 2.3.1 SUGGESTED ACTION Use the shownodeenv command to get current readings of system temperatures and voltages. If a temperature limit has been exceeded, verify the system has adequate ventilation and ambient temperature. If a voltage limit has been exceeded, contact your local service provider for technical support and services. 12.
PAGE 305
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x1a00de TYPE Component State Change MESSAGE Node Degraded () STATE 1 Time-Of-Day Battery Failure SUGGESTED ACTION Replace the time-of-day battery. STATE 2 Invalid Battery Configuration SUGGESTED ACTION Check the power supply and battery cables for proper connection. If connected properly, replace the cables.
PAGE 306
Messages and Operator’s Guide InForm OS Version 2.3.1 temperature. If 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. STATE 5 Control Cache DIMM Overheating SUGGESTED ACTION Use the shownodeenv command to view current system temperatures and voltages.
PAGE 307
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x1a00fa 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.
PAGE 308
Messages and Operator’s Guide InForm OS Version 2.3.1 SUGGESTED ACTION Recover the core files and contact your local service provider for technical support and services. STATE 6 PCI Error 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.
PAGE 309
InForm OS Version 2.3.1 ■ (PS1 - ACFAIL) Messages and Operator’s Guide ■ (PS0 - ACFAIL) Suggested Action: Replace the faulty power supply and AC power cable. If the power supply AC LED does not illuminate solid green after replacing the power supply, check the AC source for any problems. Replace the node if the condition persists. ■ (PS1 - CHROVLD) ■ (PS0 - CHROVLD) ■ (PS1 - BATFAIL) ■ (PS0 - BATFAIL) Suggested Action: Replace the faulty power supply.
PAGE 310
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x1b00de TYPE Component State Change. MESSAGE Node Power Supply Degraded () STATE 1 Not Present SUGGESTED ACTION Make sure the power supply is fully seated. If the power supply is fully seated, disconnect and reconnect the cables. If problem persists, replace power supply. Contact your local service provider for technical support and services.
PAGE 311
InForm OS Version 2.3.1 Messages and Operator’s Guide SUGGESTED ACTION Make sure the power supply is fully seated. If the power supply is fully seated, disconnect and reconnect the cables. If problem persists, replace power supply. Contact your local service provider for technical support and services. STATE 5 Oscillating Fan Failure SUGGESTED ACTION Make sure the power supply is fully seated. If the power supply is fully seated, disconnect and reconnect the cables.
PAGE 312
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x1b00fa TYPE Component State Change. MESSAGE Node Power Supply Failed () STATE 1 Invalid Battery Count SUGGESTED ACTION Replace power supply and battery. STATE 2 DC Failure SUGGESTED ACTION If an AC failure accompanies this DC failure, ignore the DC failure until the AC failure is resolved. DC failure may indicate that the power supply has been switched off by software or manually.
PAGE 313
InForm OS Version 2.3.1 Messages and Operator’s Guide SUGGESTED ACTION Verify there is no obstruction preventing the fan's operation. If there is no obstruction or if the obstruction cannot be easily removed, replace the power supply. STATE 5 Charger Overload SUGGESTED ACTION Contact your local service provider for technical support and services. STATE 6 Invalid Firmware SUGGESTED ACTION Replace power supply. Contact your local service provider for technical support and services. 12.
PAGE 314
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x1e0001 TYPE Cage log alerts MESSAGE 1 Midplane FPGA_ ESI failure: . SUGGESTED ACTION Internal midplane hardware error. One or more communication channels has been disabled. Replace midplane. MESSAGE 2 Midplane FPGA_ IRQ rate too high: . SUGGESTED ACTION Internal midplane hardware error. Two or more communication channels have been disabled. Hard reset cage using InForm UI.
PAGE 315
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE 6 Midplane FPGA_ POST Fail: . SUGGESTED ACTION Internal midplane hardware error. Two or more communication channels have been disabled. Replace midplane. 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. If error persists, replace midplane.
PAGE 316
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE 11 Firmware panic due to PMC read failure. Panic count is (). SUGGESTED ACTION Internal midplane hardware error. If you receive this alert, then cage completed self recovery. If error persists, replace midplane. 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.
PAGE 317
InForm OS Version 2.3.1 Messages and Operator’s Guide SUGGESTED ACTION Internal midplane hardware error. Interrupts could not be initialized. Replace midplane. MESSAGE 17 POST UART SIO Init . SUGGESTED ACTION Internal midplane hardware error. Interrupts could not be initialized. Replace FCAL1 or replace midplane. MESSAGE 18 POST Ticker Init . SUGGESTED ACTION Internal midplane hardware error. Timer could not be initialized. Replace midplane.
PAGE 318
Messages and Operator’s Guide InForm OS Version 2.3.1 SUGGESTED ACTION Internal midplane hardware error. Error 1 or 17: runtime variables could not be read. Replace midplane. MESSAGE 23 POST Env Init . SUGGESTED ACTION Internal midplane hardware error. Error 10, 11, or 20: I2C failed to PROM device. Replace midplane. MESSAGE 24 POST FPGA Init . SUGGESTED ACTION Internal midplane hardware error. Communication with FPGA failed. Replace midplane.
PAGE 319
InForm OS Version 2.3.1 Messages and Operator’s Guide SUGGESTED ACTION Internal midplane hardware error. CPU SRAM test failed. Replace midplane. MESSAGE 29 POST I2C Test . SUGGESTED ACTION Internal midplane hardware error. I2C failed to onboard device. Replace midplane. MESSAGE 30 POST FPGA Test . SUGGESTED ACTION Internal midplane hardware error. FPGA stress test failed. Replace midplane. MESSAGE 31 POST ADC Init .
PAGE 320
Messages and Operator’s Guide InForm OS Version 2.3.1 SUGGESTED ACTION Internal midplane hardware error. Midplane EEPROM test failed. Replace midplane. MESSAGE 35 POST Midplane LM87 Test . SUGGESTED ACTION Internal midplane hardware error. Midplane LM87 temperature sensor failed. Replace midplane. MESSAGE 36 POST Flash Test . SUGGESTED ACTION Internal midplane hardware error. Code 0: midplane CPU flash failed testing. Replace midplane.
PAGE 321
InForm OS Version 2.3.1 Messages and Operator’s Guide SUGGESTED ACTION Power supply failed to initialize. Replace Power Supply. MESSAGE 41 POST Power Supply Probe . SUGGESTED ACTION Power supply failed during functional test. Replace Power Supply. MESSAGE 42 POST Power Supply EEPROM Test . SUGGESTED ACTION Power supply EEPROM failed during functional test. Replace Power Supply. MESSAGE 43 POST Power Supply Test .
PAGE 322
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE 47 POST PMC Loopback Test . SUGGESTED ACTION Internal midplane hardware error. PMC switch chip failed POST internal loopback. Replace midplane. MESSAGE 48 POST PMC Interchip Test . SUGGESTED ACTION Internal midplane hardware error. PMC switch chip failed interchip test. Replace midplane (or possibly FCAL). MESSAGE 49 POST SFP Test . SUGGESTED ACTION FCAL SFP failed functional test.
PAGE 323
InForm OS Version 2.3.1 Messages and Operator’s Guide SUGGESTED ACTION Internal midplane hardware error. Power cycle cage. If error persists, replace midplane. MESSAGE 53 Midplane LM87 voltage/temperature under limit () SUGGESTED ACTION Midplane voltage sensor reports low voltage. Replace power supplies. If error persists, replace midplane. MESSAGE 54 Midplane LM87 voltage/temperature over limit () SUGGESTED ACTION Midplane voltage sensor reports high voltage. Replace power supplies.
PAGE 324
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x1e0002 TYPE Invalid cage configuration MESSAGE 1 Cage (WWN ) 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 .
PAGE 325
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x1e0004 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.
PAGE 326
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x1e0005 TYPE Cage firmware coredump event MESSAGE Cage COREDUMP: recovered file SUGGESTED ACTION There was a firmware coredump on one of the drive cages that has been saved in the specified location. Contact your local service provider for technical support and services. 12.
PAGE 327
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x1e00de TYPE Component State Change MESSAGE Cage Degraded () STATE 1 Operators Panel Failed STATE 2 Operators Panel Warning STATE 3 Operators Panel Unrecoverable STATE 4 Operators Panel Not_Present STATE 5 Operators Panel Not_Available STATE 6 Audible Alarm Sensor Muted STATE 7 Audible Alarm Sensor Unrecoverable SUGGESTED ACTION FOR STATE 1-7 Contact your local service provider for technical support and services.
PAGE 328
Messages and Operator’s Guide InForm OS Version 2.3.1 Check if the cables are properly seated. Confirm the loop is off line by running CLI command showpd -degraded and showpd -failed. STATE 9 Single ESI Port SUGGESTED ACTION The cage has only one ESI PD online. A disk in the ESI position may be off line. Use the CLI command showpd -p -cg to verify if any disks are off line. If a PD is off-line due to a Servicemag operation or other service operation, the alert will auto resolve.
PAGE 329
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x1e00fa TYPE Component State Change MESSAGE Cage Failed () STATE 1 Unsupported Cage STATE 2 Unsupported Link Speed STATE 3 Temperature Under_Warning_Threshold STATE 4 Temperature Under_Failure_Threshold STATE 5 Temperature Over_Warning_Threshold STATE 6 Temperature Over_Failure_Threshold SUGGESTED ACTION FOR STATE 1-6 Contact your local service provider for technical support and services.
PAGE 330
Messages and Operator’s Guide InForm OS Version 2.3.1 SUGGESTED ACTION The cage has no ESI PD online. A disk in the ESI position may be off line. Use CLI command showpd -p -cg to determine if disks are off-line. Contact your local service provider for technical support and services. STATE 9 Loop Map Fail SUGGESTED ACTION Contact your local service provider for technical support and services. Use CLI commands showcage -d, showpd, showport, and showportdev to confirm.
PAGE 331
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x1f0001 TYPE Disk overtemp MESSAGE Disk (wwn ) is overtemp ( C) and has been spundown. Or, Disk %d (wwn %016LX) is overtemp (%u C) but could not be spundown. SUGGESTED ACTION Contact your local service provider for technical support and services. 12.
PAGE 332
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x1f000de 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.
PAGE 333
InForm OS Version 2.3.1 Messages and Operator’s Guide If this is not because of a service action, please contact your local service provider for further information. STATE 5 Not Ready SUGGESTED ACTION The PD specified in the alert has reported it being not ready. 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. If the error persists, contact your local service provider for technical support and services.
PAGE 334
Messages and Operator’s Guide InForm OS Version 2.3.1 If the disk has disappeared from the B loop,it reports its B loop as missing. This could also occur because of a servicemag operation or a controlmag offloop operation. Contact your local service provider for technical support and services. STATE 9 Relocating SUGGESTED ACTION This is only an activity flag which refers to the fact that chunklets from the disk are relocating.
PAGE 335
InForm OS Version 2.3.1 Messages and Operator’s Guide SUGGESTED ACTION Cage Report is missing a PD. No action required. STATE 14 New Offloop SUGGESTED ACTION The drive was issued a command by the Sysmgr to take a PD offloop. No action required. STATE 15 New Onloop 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.
PAGE 336
Messages and Operator’s Guide InForm OS Version 2.3.1 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 22 Drive Not Ready SUGGESTED ACTION The PD is not ready at this time. No action required.
PAGE 337
InForm OS Version 2.3.1 Messages and Operator’s Guide 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. 12.
PAGE 338
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x1f000fa 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.
PAGE 339
InForm OS Version 2.3.1 Messages and Operator’s Guide SUGGESTED ACTION The PD specified in the alert has been marked failed because a command sent to check if disk is ready has failed. Use the CLI command showpd to confirm the disk is still in this state. The failure could be intermittent and a retry might fix it. As above, the suggested action is to wait for a few minutes to see if the alert is auto-fixed. If not, contact your local service provider for possible disk replacement.
PAGE 340
Messages and Operator’s Guide InForm OS Version 2.3.1 STATE 7 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. Use the CLI command showpd to confirm the disk is still in this state. If the error is persistent, contact your local service provider for possible disk replacement.
PAGE 341
InForm OS Version 2.3.1 Messages and Operator’s Guide SUGGESTED ACTION The PD specified in the alert has been marked failed because it has unsupported drive firmware installed. Use the CLI command showpd to confirm the disk is still in this state. Contact your local service provider to reload the correct firmware on the disk. STATE 12 Invalid Block Size SUGGESTED ACTION The PD specified in the alert has been marked failed because it is reporting an unsupported block size.
PAGE 342
Messages and Operator’s Guide InForm OS Version 2.3.1 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. Please 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.
PAGE 343
InForm OS Version 2.3.1 Messages and Operator’s Guide STATE 20 Media Failed SUGGESTED ACTION A disk will be marked media-failed if a hardware error or a device is bad error is reported by the disk. Contact your local service provider to replace the disk. 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. Contact your local service provider to replace the disk.
PAGE 344
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x200009 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. 12.
PAGE 345
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x210001 TYPE InForm Management Console has lost connection to the event filter MESSAGE Events/Alerts unavailable for one or more systems. 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. 12.
PAGE 346
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x220001 TYPE Battery expiration MESSAGE 1 Node PS Battery will expire in 30 days [Replace Battery soon] SUGGESTED ACTION 12.11 1 Check the system time. 2 Check the battery expiration date. 3 Contact your local service provider to schedule the battery replacement.
PAGE 347
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x2200de TYPE Component state change MESSAGE Node Power Supply Battery Degraded () STATE Battery Expired SUGGESTED ACTION Verify the battery’s expiration date on its label. If the expiration date is incorrect, use the setbattery command to correct the problem. If the battery is expired, replace the battery. 12.
PAGE 348
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x2200fa TYPE Component state change MESSAGE Node Power Supply Battery Failed () STATE 1 Battery Failed SUGGESTED ACTION Replace the battery. If the problem persists, replace the power supply. STATE 2 Invalid Firmware SUGGESTED ACTION Replace the battery. 12.
PAGE 349
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x230003 TYPE Port shutdown on fatal error MESSAGE Port shut down: SUGGESTED ACTION 1 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.
PAGE 350
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x230004 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. 12.
PAGE 351
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x230005 TYPE All ports in the same FC card must be configured for RCFC MESSAGE Port (0:5:1) is used for disk or host SUGGESTED ACTION Configure all the ports in the same FC card for RCFC or leave them free. 12.
PAGE 352
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x240001 TYPE Internodal serial port error MESSAGE Node Serial Port Error: 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. 12.
PAGE 353
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x250002 TYPE Remote Copy link status MESSAGE The Remote Copy link has changed its status to DOWN. 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.
PAGE 354
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x270001 TYPE TP VV allocation size warning MESSAGE Thin provisioned VV has reached allocation warning of XX G (yy% of ZZ 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.
PAGE 355
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x270002 TYPE TP VV allocation size limit MESSAGE Thin provisioned VV has reached allocation limit of XX G (yy% of ZZ 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. 12.
PAGE 356
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x270003 TYPE Snapshot space allocation size warning MESSAGE Snapshot space for VV has reached allocation warning of XX G (yy% of ZZ 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.
PAGE 357
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x270004 TYPE Snapshot space allocation size limit MESSAGE Snapshot space for VV has reached allocation limit of XX G (yy% of ZZ 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.
PAGE 358
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x270005 TYPE CPG growth warning MESSAGE 1 CPG space has reached allocation warning of G. SUGGESTED ACTION The logical capacity reserved and in use by the named Common Provisioning Group (CPG) is above the configured allocation warning.
PAGE 359
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x270006 TYPE CPG growth limit MESSAGE 1 CPG SD space has reached allocation limit of XXG. 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.
PAGE 360
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x270007 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 3PAR InForm OS Concepts Guide.
PAGE 361
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x270008 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 3PAR InForm OS Concepts Guide.
PAGE 362
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x270009 TYPE CPG growth failure MESSAGE 1 CPG SA 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.
PAGE 363
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x27000e 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.
PAGE 364
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x27000f 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.
PAGE 365
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x270010 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.
PAGE 366
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x270011 TYPE FC raw space allocation 95% alert MESSAGE Total FC raw space usage at ZZ G (at 95% of total XXXG) 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.
PAGE 367
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x270012 TYPE CPG space used status MESSAGE CPG space over % used (G used out of total)G SUGGESTED ACTION The CPG specified in the message has reached its warning threshold for percentage of space in use. This warning level was previously specified by the user. ■ Add more SA or SD space to the CPG. ■ Raise the alert warning point.
PAGE 368
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x270013 TYPE Raw space allocation user configured alert. MESSAGE Total available raw space has reached threshold of XX G (YY G remaining out of ZZ G total) SUGGESTED ACTION Raise the threshold using setsys rawspacealert . 12.
PAGE 369
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x270014 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.
PAGE 370
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x270015 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.
PAGE 371
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x270016 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.
PAGE 372
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x270017 TYPE NL raw space allocation 95% alert MESSAGE Total NL raw space usage at ZZ G (at 95% of total XXXG) 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.
PAGE 373
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x270050 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. 12.
PAGE 374
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x280001 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.
PAGE 375
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x280002 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.
PAGE 376
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x2900de 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 by 3PAR. Contact your local service provider for technical support and services. STATE 2 Receiver Power Low SUGGESTED ACTION The FCAL is receiving a low signal.
PAGE 377
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x2b00de TYPE Component State Change MESSAGE Cage Power Supply Degraded () STATE Power Supply Switched 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. 12.
PAGE 378
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x2b00fa 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.
PAGE 379
InForm OS Version 2.3.1 Messages and Operator’s Guide STATE 5 Power Supply Not_Available SUGGESTED ACTION The cage power supply identified may need replacement. Contact your local service provider for technical support and services. STATE 6 Fan Failed 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.
PAGE 380
Messages and Operator’s Guide InForm OS Version 2.3.1 SUGGESTED ACTION The cage power supply identified may need replacement. Contact your local service provider for technical support and services. STATE 11 Power Supply Failed SUGGESTED ACTION The cage power supply identified may need replacement. Contact your local service provider for technical support and services. STATE 12 AC Failed SUGGESTED ACTION Verify AC power source. Check the power PDU power switch.
PAGE 381
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x2d00de TYPE Component state change MESSAGE Cage FCAL Module Degraded () STATE 1 CPU Firmware Loop Down Recovery SUGGESTED ACTION Contact your local service provider for technical support and services. STATE 2 Firmware for CPU A Not_Current SUGGESTED ACTION The cage firmware is not the latest version that 3PAR supports. Use CLI command showcage - d to confirm the firmware version is not current.
PAGE 382
Messages and Operator’s Guide InForm OS Version 2.3.1 STATE 5 FCAL Module Failed SUGGESTED ACTION Check the cable connection and reseat the FCAL module. Replace the FCAL module if the problem persists. Contact your local service provider for technical support and services. STATE 6 Firmware for CPU A Unknown SUGGESTED ACTION Use CLI command showcage and showpd to confirm condition. Contact your local service provider for technical support and services.
PAGE 383
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x2d00fa 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 Unknown STATE 6 Interface Card Not_Available STATE 7 ESH Failed STATE 8 ESH Warning STATE 9 ESH Unrecoverable STATE 10 ESH Not_Present 12.
PAGE 384
Messages and Operator’s Guide STATE 11 ESH Unknown STATE 12 ESH Not_Available SUGGESTED ACTION FOR STATE 1-12 Contact your local service provider for technical support and services. 12.15 InForm OS Version 2.3.
PAGE 385
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x3500de 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. 12.
PAGE 386
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x3500fa TYPE Component State Change MESSAGE Cage Magazine Failed () STATE 1 Not Present SUGGESTED ACTION A drive mag is missing from the cage. Check if the drive mag is properly inserted into the cage. STATE 2 Cage Magazine Loop Failure SUGGESTED ACTION Use CLI command showcage -d to confirm the drive mag loop is failing. Check if the drive mag is properly inserted into the cage.
PAGE 387
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x3700de 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.
PAGE 388
Messages and Operator’s Guide InForm OS Version 2.3.1 SUGGESTED ACTION Indicates that some volumes are no longer in sync because the volume was unavailable. Determine why this is and resolve the situation, then perform a resynchronization. STATE 5 Volume Unsync; Node or Sysmgr Failure SUGGESTED ACTION Indicates that some volumes are no longer in sync because node or sysmgr failed. Determine why this is and resolve the situation, then perform a resynchronization.
PAGE 389
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x3700fa 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.
PAGE 390
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x3800de 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.
PAGE 391
InForm OS Version 2.3.1 Messages and Operator’s Guide SUGGESTED ACTION Check to see whether all the volumes in the group are in sync. STATE 6 Not All Volumes In Group Are In Sync SUGGESTED ACTION Check to see whether all the volumes in the group are in sync. STATE 7 Periodic Sync Took More Than Sync Period SUGGESTED ACTION Check to see whether all the links are up and running and check the value of the period user set.
PAGE 392
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x3900fa 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.
PAGE 393
InForm OS Version 2.3.1 Messages and Operator’s Guide STATE 6 RMM_ST_TARGET_BADLINKS SUGGESTED ACTION Target's links connect to multiple InServs, dismiss and admit correct links. STATE 7 RMM_ST_MULT_TARGETS SUGGESTED ACTION Multiple targets defined for one remote system, one of the targets without groups defined gets disabled. Please remove the disabled target. STATE 8 RMM_ST_MULT_TARGETS_WITH_GROUPS SUGGESTED ACTION Multiple targets with groups defined that point to the same remote system.
PAGE 394
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x3a00de 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. 12.
PAGE 395
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x3a00fa TYPE Component state change MESSAGE Remote Copy Link Failed () STATE 1 Down Due To Send Error Or Missing Heart Beat 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.
PAGE 396
Messages and Operator’s Guide InForm OS Version 2.3.1 MESSAGE CODE 0x450001 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. 12.
PAGE 397
InForm OS Version 2.3.1 Messages and Operator’s Guide MESSAGE CODE 0x460001 TYPE Control Cache DIMM CECC Monitoring MESSAGE Node : Correctable ECC limit exceeded STATE 1 New SUGGESTED ACTION Contact your local service provider to have the DIMM replaced as soon as possible. 12.
PAGE 398
Messages and Operator’s Guide 12.16 InForm OS Version 2.3.
PAGE 399
InForm OS Version 2.3.1 ____________Messages and Operator’s Guide A Agency Compliance Statements In this appendix A.1 Safety Precautions A.2 A.2 Safety Agency Compliance Notices A.2 A.2.1 System Placement and Security A.2 A.2.2 Battery Replacement and Disposal A.5 A.2.3 Controller Nodes A.8 A.2.4 Drive Chassis A.13 A.3 3PAR Power Cables A.16 A.4 Energy Consumption Efficiency A.
PAGE 400
Messages and Operator’s Guide InForm OS Version 2.3.1 A.1 Safety Precautions For your safety, for the safety of others, and to protect system data and equipment, always follow the instructions in this manual while installing, maintaining, troubleshooting, and upgrading InServ Storage Servers and their components.
PAGE 401
InForm OS Version 2.3.1 Messages and Operator’s Guide AVERTISSEMENT: Installer cette unité dans un endroit restreint d'accès. WAARSCHUWING: Deze eenheid dient te worden geïnstalleerd op een beperkt toegankelijke locatie. ADVERTENCIA: Está unidad deberá ser instalada en una área de acceso restringido. Safety Agency Compliance Notices A.
PAGE 402
Messages and Operator’s Guide InForm OS Version 2.3.1 For storage servers with 3PAR cabinets, secure the system by locking the rear doors on all cabinets. WARNING: Hazardous energy is located behind the rear access door of the storage server cabinet. ACHTUNG: Hinter der rückwärtigen Zugangstür des Storage-Server-Schranks liegen gefährliche Spannungen an. AVERTISSEMENT: Énergie dangereuse située derrière la porte d'accès arrière du coffret de serveur de stockage.
PAGE 403
InForm OS Version 2.3.1 Messages and Operator’s Guide A.2.2 Battery Replacement and Disposal Storage server controller nodes contain 3-V lithium coin batteries. These batteries require periodic replacement. WARNING: There is danger of an explosion if the lithium coin battery inside the controller node is incorrectly replaced. Replace the coin battery only with the same or equivalent type recommended by the manufacturer.
PAGE 404
Messages and Operator’s Guide InForm OS Version 2.3.1 ADVERTENCIA: Existe el peligro de explosión si la batería de litio dentro del controlador del nodo es reemplazada incorrectamente. Reemplacela solamente con una batería del mismo tipo o con una de tipo equivalente recomendado por el fabricante. CAUTION: Dispose of used batteries according to the manufacturer’s instructions. A.
PAGE 405
InForm OS Version 2.3.1 Messages and Operator’s Guide VORSICHT: Gebrauchte Batterien nur gemäß Herstelleranweisung entsorgen. ATTENTION: Débarrassez-vous des batteries use selon les instructions de fabricant. WAARSCHUWING: Verwijder gebruikte batterijen volgens de instructies van de fabrikant. PRECAUCION: Deseche baterías usadas de acuerdo a las instrucciones del fabricante. Safety Agency Compliance Notices A.
PAGE 406
Messages and Operator’s Guide InForm OS Version 2.3.1 A.2.3 Controller Nodes For controller nodes installed in cabinets not provided by 3PAR, observe the following precautions: WARNING: Install the unit in a restricted access location. ACHTUNG: Diese Einheit darf nicht frei zugänglich installiert werden. AVERTISSEMENT: Installer cette unité dans un endroit restreint d'accès. WAARSCHUWING: Deze eenheid dient te worden geïnstalleerd op een beperkt toegankelijke locatie.
PAGE 407
InForm OS Version 2.3.1 Messages and Operator’s Guide WARNING: Hazardous energy located on rear connectors. ACHTUNG: An den rückwärtigen Anschlüssen liegen gefährliche Spannungen an. AVERTISSEMENT: Énergie dangereuse située sur les connecteurs arrière. WAARSCHUWING: Gevaarlijke energievelden achter de aansluitingen aan de achterzijde. Safety Agency Compliance Notices A.
PAGE 408
Messages and Operator’s Guide InForm OS Version 2.3.1 ADVERTENCIA: Energía peligrosa localizada en los conectores traseros. WARNING: There is danger of an explosion if the lithium coin battery inside the controller node is incorrectly replaced. Replace the coin battery only with the same or equivalent type recommended by the manufacturer. ACHTUNG: Bei unsachgemäßem Austausch der Lithium-Knopfbatterie im Steuerknoten besteht Explosionsgefahr. Die Knopfbatterie darf nur durch eine gleiche bzw.
PAGE 409
InForm OS Version 2.3.1 Messages and Operator’s Guide AVERTISSEMENT: Il y a un danger d'explosion si la batterie de lithium à l'intérieur du contrôleur est incorrectement positionnée. Remplacez la batterie seulement avec le même type ou équivalent recommandé par le fabricant. WAARSCHUWING: Er bestaat kans op explosies als de lithium muntbatterij in de controller node niet op de juiste wijze wordt vervangen.
PAGE 410
Messages and Operator’s Guide InForm OS Version 2.3.1 CAUTION: Dispose of used batteries according to the manufacturer’s instructions. VORSICHT: Gebrauchte Batterien nur gemäß Herstelleranweisung entsorgen. ATTENTION: Débarrassez-vous des batteries use selon les instructions de fabricant. WAARSCHUWING: Verwijder gebruikte batterijen volgens de instructies van de fabrikant. PRECAUCION: Deseche baterías usadas de acuerdo a las instrucciones del fabricante. A.
PAGE 411
InForm OS Version 2.3.1 Messages and Operator’s Guide A.2.4 Drive Chassis For drive chassis installed in cabinets not provided by 3PAR, observe the following precautions: WARNING: Install the unit in a restricted access location. ACHTUNG: Diese Einheit darf nicht frei zugänglich installiert werden. AVERTISSEMENT: Installer cette unité dans un endroit restreint d'accès. WAARSCHUWING: Deze eenheid dient te worden geïnstalleerd op een beperkt toegankelijke locatie.
PAGE 412
Messages and Operator’s Guide InForm OS Version 2.3.1 WARNING: There is danger of an explosion if the battery is incorrectly replaced. Replace only with the same or equivalent type recommended by the manufacturer. ACHTUNG: Bei unsachgemäßem Austausch der Batterie besteht Explosionsgefahr. Sie darf nur durch eine gleiche bzw. vom Hersteller empfohlene gleichwertige Batterie ersetzt werden. AVERTISSEMENT: Il y a un danger d'explosion si la batterie est incorrectement positionnée.
PAGE 413
InForm OS Version 2.3.1 Messages and Operator’s Guide WAARSCHUWING: Er bestaat kans op een explosie als de batterij niet op de juiste wijze wordt vervangen. Alleen te vervangen door een type dat equivalent is aan het type dat door de fabrikant wordt aanbevolen. ADVERTENCIA: Existe el peligro de explosión si la batería es reemplazada incorrectamente. Reemplácela solamente con una batería del mismo tipo o un tipo equivalente recomendado por el fabricante. Safety Agency Compliance Notices A.
PAGE 414
Messages and Operator’s Guide InForm OS Version 2.3.1 A.3 3PAR Power Cables English Compliance Statement All power cables provided by 3PAR are for exclusive use for 3PAR products. Japanese Compliance Statement A.4 Energy Consumption Efficiency Energy consumption efficiency*= 0.
PAGE 415
InForm OS Version 2.3.1 Messages and Operator’s Guide Index 2M (40U) 3PAR cabinet numbering, drive chassis 2.6 to 2.9, 3.15 to 3.17, 4.12, 5.11 C cabinets drive chassis non-3PAR cabinets, warning for A.16 A non-3PAR, controller node warnings A.8 adapter ports, Fibre Channel 2.12, 3.13, 4.11, 5.10 numbering system for 2.8, 3.18 adapters, Fibre Channel numbering of 2.12, 3.13, 4.11, 5.10 alerts about 1.6 audience for this manual 1.2 B numbering in drive chassis 2.9, 3.15 to 3.17, 4.12, 5.11 PDUs 2.
PAGE 416
Messages and Operator’s Guide amber status light 6.17, 7.10, 8.3, 8.14, 9.3, 9.15 InForm OS Version 2.3.1 disk hot-plug status LED controller nodes 7.9 controller node power supplies LEDs 8.20, 9.19 disks numbering system for 2.8, 3.18 location of 8.20, 9.19 controller nodes component locations on 2.13, 3.14, 4.12, 5.11 control cache memory location of 2.13, 3.14 documents, related 1.2 Drive 2.9 drive cages FC-AL modules Fibre Channel adapters LEDs, status and error displays 6.7, 6.10, 7.
PAGE 417
InForm OS Version 2.3.1 Messages and Operator’s Guide port status error display 6.19, 6.22, 8.15 gigabit Ethernet adapter 8.19 ports, location of 6.18, 6.20, 6.21, 8.15 gigabit ethernet adapter 6.24 LSI 2-Port Fibre Channel ports Fibre Channel adapters location of 6.20, 8.15 location on controller node 2.13, 3.14 LSI 4-Port Fibre Channel ports numbering example 2.12, 3.13, 4.11, 5.10 location of 6.21 numbering system, chart for 2.13, 3.14 power supplies 6.26, 7.13, 8.20, 9.
PAGE 418
Messages and Operator’s Guide power distribution units (PDUs) InForm OS Version 2.3.1 servers safety precautions A.2 indicator lamps 6.29, 7.17, 8.21, 9.20 numbering for 2.5, 3.7, 4.7, 5.7 service processor LEDs 6.24, 8.19 power status LEDs, status and error display 6.17, 8.14, 9.15 storage server powering on 10.4 power supplies LEDs 6.26, 7.13 location of 6.27, 7.14 storage servers components numbering of 2.15, 3.20 identifying 2.1 to 2.3, 3.2 to 3.3, 4.2 to 4.3, 5.
PAGE 419
InForm OS Version 2.3.1 Messages and Operator’s Guide Revision History Release Level Revision Summary 320-200181 Rev A First release of this manual with updated part number to support the October 2009 release of 3PAR InForm OS 2.3.1. Chapter 12, Alerts has been updated. 320-200181 Rev B Second release of this manual to support the Supermicro II service February 2010 processor and Solid State Drives (SSD). Added Chapter 11, Troubleshooting. Revision History RH.
PAGE 420
Messages and Operator’s Guide RH.2 InForm OS Version 2.3.