3par inform os 2.3.1 messages and operator's guide
Post on 09-Feb-2022
7 Views
Preview:
TRANSCRIPT
3PAR Confidential
3PAR InForm® OS 2.3.1Messages and Operator’s Guide
3PAR Inc.4209 Technology DriveFremont, CA 94538 USA
Part No. 320-200181 Rev B February 2010
Revision NoticeThis is the second release of this manual. A complete revision history is provided at the end of this manual.
ChangesThe 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.3PAR reserves the right to make changes in the product design without reservation and without notification to its users.
Updates to the Documentation at 3PAR CentralAny updates to this document, or other 3PAR technical documents, can be found by logging into 3PAR Central’s Document Control System from 3PAR’s Support page, at: http://support.3PAR.com.
3PAR Technical Support and ServicesContact your 3PAR Authorized Service Provider for technical support and services at: http://www.3PAR.com/services.html.
Sales and Ordering InformationFor sales and ordering information, contact3PAR Inc.4209 Technology DriveFremont, CA 94538 USATelephone: 510-413-5999Fax: 510-413-5699Email: salesinfo@3PAR.com
Reader Comments and SuggestionsPlease email your comments and suggestions about this document to: ReaderComments@3PAR.com
CopyrightPrinted MaterialCopyright © 2004-2010 3PAR Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of 3PAR Inc., 4209 Technology Drive, Fremont, CA 94538. By way of exception to the foregoing, the user may print one copy of electronic material for personal use only.
Trademarks3PAR, InServ, InForm, InSpire and Serving Information are registered trademarks of 3PAR Inc.Microsoft and Windows NT are registered trademarks of Microsoft Corporation in the U.S. and other countries, used under license.All other trademarks are owned by their respective owners.
Federal Communications Commission Radio Frequency Interference StatementWARNING: Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment.This device complies with Part 15 of FFC Rules. Operation is subjected to the following two conditions (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.
3PAR Confidential
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).
WARNING: This is a Class A product. In a domestic environment, this product may causeradio interference in which case the user may be required to take adequate measures.
3PAR Confidential
3PAR Confidential
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.5 Power Supply Numbering 2.15
3 Numbering System and Component Locations for T-Class Servers
3.1 Identifying Storage Server Components 3.2
3.2 Service Processor Placement 3.3
3.3 Understanding Component Numbering 3.4
3PAR ConfidentialvTable of Contents
vi
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.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.16
5 Numbering System and Component Locations for F-Class Servers
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.15
6 Understanding S-Class LED Status
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.4 3PAR Fibre Channel Port LEDs 6.23
Table of Contents
3PAR Confidential
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.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.1.10 Supermicro II Service Processor 7.19
7.2 Securing the Storage Server 7.20
8 Understanding E-Class LED Status
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.6 Power Distribution Unit Lamps 8.21
viiTable of Contents
3PAR Confidential
viii
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.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.2 Service Processor LEDs 9.21
9.2.1 Supermicro Service Processor 9.21
9.2.2 Supermicro II Service Processor 9.22
9.3 Securing the Storage Server 9.24
10 Power Off/On Procedures
10.1 Powering Off the Storage Server 10.1
10.2 Powering On the Storage Server 10.4
11 Troubleshooting
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
Table of Contents
3PAR Confidential
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 Agency Compliance Statements
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.16
IX Index
RH Revision History
ixTable of Contents
3PAR Confidential
x
Messages and Operator’s Guide InForm OS Version 2.3.1
Table of Contents
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
1Introduction
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.
Information provided in this document supports the S-Class, T-Class, E-Class, and F-Class models
of the InServ Storage Servers.
1.1Introduction
3PAR Confidential
1.2
Messages and Operator’s Guide InForm OS Version 2.3.1
1.1 AudienceThis 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.2 Related DocumentsAlong with this guide, the following documents compose the 3PAR InServ Storage Server
family documentation suite:
For information about… Read the…
Using the InForm Command Line Interface
(CLI) to configure and administer InServ
Storage Servers
3PAR InForm OS CLI Administrator’s
Manual and InForm OS Command Line
Interface Reference
Using the InForm Management Console
graphical user interface to configure and
administer InServ Storage Servers
3PAR InForm OS Management Console
Online Help
InServ Storage Server concepts and
terminology
3PAR InForm OS Concepts Guide
Using Remote Copy 3PAR Remote Copy User’s Guide
Storage server hardware configurations,
component numbering and layout, and
system cabling
3PAR InServ E-Class/F-Class Storage
Server and Third-Party Rack Physical
Planning Manual
3PAR InServ S-Class/T-Class Storage Server
Physical Planning Manual
Audience
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
1.3 OrganizationThis 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.
Chapter 2, Numbering System and Component Locations for S-Class Servers, identifies all
major components of the InServ S-Class Storage Servers and explains the numbering system
used within the storage server to identify components.
Chapter 3, Numbering System and Component Locations for T-Class Servers, identifies all
major components of the InServ T-Class Storage Servers and explains the numbering system
used within the storage server to identify components.
Chapter 4, Numbering System and Component Locations for E-Class Servers, identifies all
major components of the InServ E-Class Storage Servers and explains the numbering system
used within the storage server to identify components.
Chapter 5, Numbering System and Component Locations for F-Class Servers, identifies all major
components of the InServ F-Class Storage Servers and explains the numbering system used
within the storage server to identify components.
Chapter 6, Understanding S-Class LED Status, illustrates and explains all LEDs in the S-Class
Storage Servers and provides an understanding of when a hardware problem may exist and
what action to take.
Chapter 7, Understanding T-Class LED Status, illustrates and explains all LEDs in the T-Class
InServ Storage Servers and provides an understanding of when a hardware problem may exist
and what action to take.
Chapter 8, Understanding E-Class LED Status, illustrates and explains all LEDs in the E-Class
InServ Storage Servers and provides an understanding of when a hardware problem may exist
and what action to take.
Chapter 9, Understanding F-Class LED Status, illustrates and explains all LEDs in the F-Class
InServ Storage Servers and provides an understanding of when a hardware problem may exist
and what action to take.
Chapter 10, Power Off/On Procedures, provides operational procedures for powering on and
off the storage server.
1.3Organization
3PAR Confidential
1.4
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.
This guide also contains an index and revision history for your reference.
1.4 Typographical ConventionsThe following typographical conventions are used in this guide:
Typeface Meaning Example
ABCDabcd Used for dialog box elements such as
titles and button labels.
Enter your system name in the Value
box and click OK.
ABCDabcd Used for file names, paths, and
screen output, and for text you are
to enter.
Found < 12 > 73G disks.
Enter cli at the Windows command
prompt.
ABCDabcd Used to contrast your input with
system output.cli% removevv VV1
Removing vv VV1.
ABCDabcd
ABCDabcd
Used for variables in file names,
paths, and screen output, and
variables in user input.
[root@(systemID-nodeID)root]
To continue Enter your system
name ==> systemname
Blue Text Used to emphasize text in examples
and screen output.
The following virtual volumes were
created:
Test_VV1
Test_VV2
Typographical Conventions
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
1.5 AdvisoriesTo 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.
WARNING: Warnings alert you to actions that can cause injury to a person or
irreversible damage to data or the operating system.
1.5Advisories
3PAR Confidential
1.6
Messages and Operator’s Guide InForm OS Version 2.3.1
Advisories
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
2Numbering 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.1 Identifying Storage Server Components Figure 2-1 and Figure 2-2 identify the major components of an InServ S400 Storage Server in a
2M (40U) 3PAR cabinet.
NOTE: Figure 2-1 and Figure 2-2 show sample systems and may not match your
particular storage server configuration.
2.1Numbering System and Component Locations for S-Class Servers
3PAR Confidential
2.2
Messages and Operator’s Guide InForm OS Version 2.3.1
Figure 2-1. The Front of an InServ S400
Drive Magazines
Storage ServerBackplane withController Nodes
Main PowerCords
Leveling Foot
Drive Chasis
Front Fascia
Drive CageFC-AL
Modules
ServiceProcessor
Battery Tray
ControllerNodes
0001_L_R3
Bezel
Identifying Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
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. The location of a component is expressed by a string of
numbers that contains information about the exact positioning of the component in relation
to the cabinet and to other components.
2.2.1 Cabinet Numbering
The InServ S-Class Storage Server 2M (40U) storage server cabinet is an EIA-standard rack that
accepts storage server components. Numbers for chassis bays are assigned:
0212_L_R1
Hinge
Lock
Drive Cage Power Supplies
Rear Door
Controller Node Power Supplies
Battery Backup Units (BBUs)
Power DistributionUnits (PDUs)
2.3Understanding Component Numbering
3PAR Confidential
2.4
Messages and Operator’s Guide InForm OS Version 2.3.1
■ beginning with 0.
■ from top to bottom.
Figure 2-3 illustrates numbering of chassis bays in a 3PAR cabinet.
Figure 2-3. Numbering of Chassis Bays in the Cabinet
0213_L_R1
ChassisBays
0
1
2
3
4
5
6
7
8
9
Understanding Component Numbering
3PAR Confidential
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:
2.2.2 PDU Numbering
The four Power Distribution Units (PDUs) occupy the lowest chassis bay in the cabinet. Each
PDU has two power banks.
Numbers for PDUs are assigned:
■ beginning with 0.
■ from top to bottom.
Table 2-1. Cabinet Numbering for Multi-Cabinet Systems
Cabinet Number
Node cabinet C00
Additional node cabinets C10, C20, C30…
Drive cages connecting to the first node cabinet C01, C02, C03…C09
Drive chassis cabinets connecting to
the second node cabinetC11, C12, C13…C19
Drive chassis cabinets connecting to the third node
cabinetC21, C22, C23…C29
2.5Understanding Component Numbering
3PAR Confidential
2.6
Messages and Operator’s Guide InForm OS Version 2.3.1
Figure 2-4 illustrates PDU numbering for 3PAR cabinets.
Figure 2-4. Numbering of PDUs
In addition, each PDU has two power banks (Figure 2-5).
Figure 2-5. Power Banks in the PDU
2.2.3 Drive Cage Numbering
There are two models of drive cages available for the InServ S-Class Storage Servers, DC2 and
DC4. Depending on the specific configuration, a storage server may contain up 64 drive cages.
The DC2 and DC4 drive cages contain ten drive bays and each drive bay accommodates a single
drive magazine holding four disks. A single InServ S-Class Storage Server can contain both DC2
and DC4 drive cages.
NOTE: Figure 2-4 shows a sample system and may not match your particular
storage server configuration.
0216_L_R1
PDUs
0
1
2
3
0221_L_R1
Power Bank 2Power Bank 1
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
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.
NOTE: Figure 2-6 shows a sample system and may not match your particular
storage server configuration.
0003_L_R3
StorageServerBackplane
DriveChassis
5
4
3
2
1
0
NOTE: For systems that occupy multiple cabinets, drive cage numbers continue at
the bottom of the next cabinet and progress through the top of the cabinet.
2.7Understanding Component Numbering
3PAR Confidential
2.8
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...
FC-AL modules
Left side
Right sideA
A
left to right
Fibre Channel ports
Left side
Right sideA0,B0
A1,B1
top to bottom
top to bottom
Drive magazines 0,1,2,3,4,5,6,7,8,9 left to right*
* When facing the storage server.
Disks on the drive magazine 0,1,2,3 rear to front*
Understanding Component Numbering
3PAR Confidential
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.
Figure 2-7. Numbering of the Drive Magazines in the Drive Cage
Figure 2-8. Numbering of Disks on the Drive Magazines
0588_L_R2
Drive Magazines
B0
A0
Por
tsA
1B
1P
orts
0 1 2 3 4 5 6 7 8 9
0600_L_R2
3 2
2
1
1
0
0
RearFront
3
2.9Understanding Component Numbering
3PAR Confidential
2.10
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:
A controller node assumes the number of the bay that it occupies in the storage server
midplane, as shown in Figure 2-9.
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
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Figure 2-9. Numbering of Controller Nodes in an InServ S800 Midplane
0219_L_R1
1
3
5
7
0
2
4
6
NOTE: Figure 2-9 shows a sample system and may not match your particular
storage server configuration.
2.11Understanding Component Numbering
3PAR Confidential
2.12
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. 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.
Figure 2-10. Numbering for Dual-Port Fibre Channel Adapters in the Controller Node
In quad-port Fibre Channel adapters, the ports are numbered PORT 0, PORT 1, PORT 2, and PORT 3,
from top to bottom.
The controller node also has an Ethernet port and a maintenance port.
0220_L_R1
1
FibreChannel
Ports
PCI Slots
MaintenancePort (C1)
EthernetPort (E0)
2
0 1 2 3 4 5
Understanding Component Numbering
3PAR Confidential
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).
Figure 2-11. Control Cache and Data Cache DIMMs in a P4 Controller Node
Numbers for controller nodes and their components are assigned in the order indicated in
Table 2-4 on page 2.13.
Data CacheDIMMs
Riser Card
7
6
5
4
3
2
1
0
PCI Slots withPCI Adapters and
Load Cards
Processors
P4 ControlCache DIMMs
0
1
2
3
0
1
2
3
(J7100)
(J7300)
(J7200)
(J7400)
4
5
0223_L_R1
Table 2-4. Numbering System for Controller Nodes and their Components
The following
components... Are numbered... Running from...
Controller nodes 0,1,2,3,4,5,6,7 left to right* and
top to bottom
Fibre Channel adapters 0,1,2,3,4,5 left to right*
2.13Understanding Component Numbering
3PAR Confidential
2.14
Messages and Operator’s Guide InForm OS Version 2.3.1
Fibre Channel ports
dual-port adapters
quad-port adapters1,2
1,1,2,3
top to bottom
top to bottom
DIMMs
control cache
data cache 0,1,2,3
0,1,2,3,4,5,6,7
right to left*
bottom to top
* When facing the storage server.
Table 2-4. Numbering System for Controller Nodes and their Components
The following
components... Are numbered... Running from...
Understanding Component Numbering
3PAR Confidential
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.
When viewing the cabinet from the rear, the power supplies in each power domain are
numbered from 0 to 3, from left to right. Figure 2-12 shows an expansion cabinet.
Figure 2-12. Numbering of Power Supplies within the Power Domains
0227_L_R2
Power Supplies
0 1 2 3
UpperPower Domain
Lower Power Domain
2.15Understanding Component Numbering
3PAR Confidential
2.16
Messages and Operator’s Guide InForm OS Version 2.3.1
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
3Numbering 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.20
This chapter identifies the major components of 3PAR InServ T-Class Storage Servers and
explains how storage server components are numbered.
NOTE: Illustrations in this chapter show sample systems and might not match your
particular storage server configuration.
3.1Numbering System and Component Locations for T-Class Servers
3PAR Confidential
3.2
Messages and Operator’s Guide InForm OS Version 2.3.1
3.1 Identifying Storage Server ComponentsFigure 3-1 and Figure 3-2 identify the major components of an InServ T400 Storage Server in a
2M (40U) 3PAR cabinet.
Figure 3-1. The Front of an InServ T400 Storage Server
Drive Magazines
Storage ServerBackplane withController Nodes
Main PowerCords
Leveling Foot
Drive Chassis
Front Fascia
Drive CageFC-AL
Modules
ServiceProcessor
Battery Tray
ControllerNodes
0582_L_R1
Bezel
Identifying Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Figure 3-2. The Rear View of an InServ T400 Storage Server
3.2 Service Processor PlacementA 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. The service processor allows 3PAR to diagnose and even resolve potential
problems remotely.
The service processor is usually installed directly above the PDUs and below the battery tray
(Figure 3-3). The service processor is powered internally by the storage server and does not
require an external power connection.
0212_L_R1
Hinge
Lock
Drive Cage Power Supplies
Rear Door
Controller Node Power Supplies
Battery Backup Units (BBUs)
Power Distribution Units (PDUs)
3.3Service Processor Placement
3PAR Confidential
3.4
Messages and Operator’s Guide InForm OS Version 2.3.1
Figure 3-3. Placement of the Service Processor
When a cabinet does not include a service processor, a filler panel covers the area of the
cabinet that the service processor normally occupies.
3.3 Understanding Component NumberingBecause of the large number of potential storage server configurations, 3PAR has standardized
component placement and internal cabling to simplify installation and maintenance. For this
reason, system components are placed in the cabinet according to the principles outlined in
this section and numbered according to their order and location in the cabinet.
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.
0004_L_R3
Service Processor
Battery Tray
PDUs(Visible Only
from the Back)
NOTE: For information about standardized cabling, see the 3PAR InServ® T-Class
Storage Server Installation and Deinstallation Guide.
Understanding Component Numbering
3PAR Confidential
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.
Figure 3-4. Numbering of Chassis Bays in the Cabinet
A storage system can be housed in a single cabinet or multiple cabinets. When multiple
cabinets are required, the first cabinet (the controller node cabinet) holds the storage 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.
ChassisBays
0
1
2
3
4
5
6
7
0583_L_R1
8
9
3.5Understanding Component Numbering
3PAR Confidential
3.6
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:
Figure 3-5 shows the location of system components for InServ T400 and T800 Storage Server
controller node cabinets. Figure 3-6 shows the location of system components for drive chassis
cabinets.
Figure 3-5. Controller Node Cabinet Component Layout by Storage Server Model
Table 3-1. Cabinet Numbering
Cabinet Number
Controller node cabinet C00
Drive chassis cabinets connecting to the first node cabinet C01, C02, C03...C09
0616_L_R1
0
BayNumber
RackUnits (U)
4038363432302826242220181614121086420
1
2
3
4
5
6
7
8
9
Drive Chassis orFiller Panel
Drive Chassis orFiller Panel
Drive Chassis orFiller Panel
Drive Chassis
T800
Service Processor*Battery Tray 0
Nodes 2, 3
Nodes 4, 5
Nodes 6, 7
Battery Tray 1PDU 0 + PDU 2PDU 1 + PDU 3
Drive Chassis orFiller Panel
Drive Chassis orFiller Panel
Drive Chassis orFiller Panel
T400
PDU 2PDU 3
PDU 0PDU 1
Battery Tray 0Service Processor*
Nodes 0, 1
Nodes 2, 3
Nodes 0, 1 Drive Chassis
Drive Chassis orFiller Panel
Drive Chassis orFiller Panel
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Figure 3-6. Drive Chassis Cabinet Component Layout
3.3.2 PDU Numbering
For each cabinet, the four Power Distribution Units (PDUs) occupy the lowest chassis bay in the
cabinet.
Numbers for PDUs are assigned:
■ beginning with 0.
■ from top to bottom.
Figure Figure 3-7 illustrates the four PDUs at the bottom of a 3PAR cabinet.
0
BayNumber
1
2
3
4
5
6
7
8
9
0215_L_R1
RackUnits (U)
4038363432302826242220181614121086420
Drive Chassis orFiller Panel
Drive Chassis orFiller Panel
Drive Chassis orFiller Panel
PDU 2PDU 3
PDU 0PDU 1
Drive Chassis
Filler Panel
Drive Chassis orFiller Panel
Drive Chassis orFiller Panel
Drive Chassis orFiller Panel
Drive Chassis orFiller Panel
3.7Understanding Component Numbering
3PAR Confidential
3.8
Messages and Operator’s Guide InForm OS Version 2.3.1
Figure 3-7. Numbering of PDUs
Each PDU has two power banks, each with a separate circuit breaker, to be used exclusively for
storage server components (Figure 3-8).
Figure 3-8. Power Banks in the PDU
0216_L_R1
PDUs
0
1
2
3
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.
0221_L_R1
Power Bank 2Power Bank 1
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.
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s 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. One battery per controller node is
required for all storage server configurations.
There is always a battery tray located directly below the storage server backplane. When a
second battery tray is required, as is the case with storage servers that have six or eight
controller nodes, a second battery tray rests immediately above the storage server backplane.
Storage servers use Magnetek BBUs. Each battery unit contains two independently-switched
batteries, labeled BATTERY A and BATTERY B (Figure 3-9).
Figure 3-9. Battery Backup Unit
BBU placement and numbering schemes vary according to the type of components used in the
system.
A battery tray can hold a maximum of four BBUs. The number of BBUs and battery trays in a
system depends on the number of controller nodes installed (Table 3-2).
NOTE: For more information on PDUs and storage server configurations, see the
3PAR InServ® T-Class Storage Server Installation and Deinstallation Guide.
0260_L_R1
Battery AStatus LED
Battery BStatus LED
3.9Understanding Component Numbering
3PAR Confidential
3.10
Messages and Operator’s Guide InForm OS Version 2.3.1
3.3.3.1 Magnetek Battery Backup Units
Magnetek BBUs have batteries that sit vertically, with battery A above battery B. (Figure 3-10).
Figure 3-10. Magnetek Battery Backup Units Have Batteries Sit Vertically
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
T800 2 2 1 Below backplane
4 4 1 Below backplane
6 6 2 Below backplane (1)
Above backplane (1)
8 8 2 Below backplane (1)
Above backplane (1)
0217_L_R1
Battery Tray (Rear)
Magnetek BBUwith Two (2)
Batteries (A and B)
Battery Tray Holds Four (4) BBUs
A
B
Understanding Component Numbering
3PAR Confidential
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).
Figure 3-11. Magnetek BBU Numbering Scheme
3.3.4 Controller Node Numbering
InServ T-Class Storage Servers contain two, four, six, or eight controller nodes per system.
The T-Class Storage Servers only use T-Class controller nodes.
Controller nodes are loaded into the storage server backplane enclosure from bottom to top.
Therefore, for an InServ T800 storage system with only two controller nodes installed, those
controller nodes would occupy the lowest 4U of the backplane and would be numbered
node 6 and node 7. The other bays in the backplane enclosure would be protected with filler
panels that block insertion of other components.
0218_L_R1
Storage Server (Rear)
Storage Server Backplane
BBU 3Tray 0 BBU 2 BBU 1 BBU 0
BBU 3Tray 1 BBU 2 BBU 1 BBU 0
3.11Understanding Component Numbering
3PAR Confidential
3.12
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.
Figure 3-12. Numbering of Controller Nodes in an InServ T800 Backplane
0586_L_R1
1
3
5
7
0
2
4
6
Understanding Component Numbering
3PAR Confidential
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).
Figure 3-13. Numbering for Dual-Port Fibre Channel Adapters in the Controller Node PCI Slots
Each Fibre Channel adapter in a PCI slot has four ports. Each iSCSI adapter in a PCI slot has two
or four ports. PCI adapters assume the numbers of the PCI slots they occupy.
■ In dual-port adapters, ports are labeled PORT 1 and PORT 2, from top to bottom.
■ In quad-port Fibre Channel adapters, the ports are numbered PORT 1, PORT 2, PORT 3, and
PORT 4, from top to bottom.
FibreChannel
Ports
MaintenancePort (C0)
EthernetPort (E0)
0590_L_R2
PCI Slots
0 1 2 3 4 5 EthernetPort (E1)
1
2
3
4
3.13Understanding Component Numbering
3PAR Confidential
3.14
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).
Figure 3-14. Control Cache and Data Cache DIMMs in a T-Class Controller Node
Numbers for controller nodes and their components are assigned in the order indicated in
Table 3-3 on page 3.14.
0594_L_R2
Bank 2
Bank 0 Bank 1
DIMM 2.0 (J1300)DIMM 2.1 (J1200)
DIMM 1.0 (J0900)DIMM 1.1 (J0800)
DIMM 0.0 (J0901)DIMM 0.1 (J0801)
Data Cache 2-Slot Riser Card Data Cache 4-Slot Riser Card
Table 3-3. Numbering System for Controller Nodes and their Components
The Following Components... Are Numbered... Running from...
Controller nodes 0,1,2,3,4,5,6,7 left to right* and
top to bottom
PCI adapters 0,1,2,3,4,5 left to right*
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
3.3.5 Drive Chassis Numbering
Depending on the specific configuration, a storage server can include up to 64 drive chassis. A
drive chassis houses two drive cages where each contains five drive bays. Each drive bay can
accommodate a single drive magazine holding four disks for a total of 20 disks per drive cage
and 40 disks per drive chassis.
Numbers for drive chassis are assigned:
■ beginning with 0.
■ from bottom to top, beginning with the drive chassis directly above the storage server
backplane.
PCI ports
dual-port adapters
quad-port adapters
1,2
1,2,3,4top to bottom
top to bottom
Control Cache DIMMs
control cache
data cache
0,1
0,1,2,3,4,5,6,7
left to right*
Data Cache DIMMs
Bank 0
Bank 1
Bank 2
0,1
0,1
0,1
top to bottom
* When facing the storage server.
Table 3-3. Numbering System for Controller Nodes and their Components (continued)
The Following Components... Are Numbered... Running from...
3.15Understanding Component Numbering
3PAR Confidential
3.16
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.
Figure 3-15. Numbering of Drive Chassis
0003_L_R3
StorageServerBackplane
DriveChassis
5
4
3
2
1
0
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.
Understanding Component Numbering
3PAR Confidential
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.
Figure 3-16. Numbering of Drive Chassis Components
Figure 3-17. Numbering of Disks on a DC4 and DC4 Type-2 Drive Magazine
0588_L_R2
Drive Magazines
B0
A0
Por
tsA
1B
1P
orts
0 1 2 3 4 5 6 7 8 9
0600 L R4
3 2
2
1
1
0
0
Rear
Rear
Front
Front
3
3
3
2
2
1
1
0
0
DC4 Type-2
DC4
3.17Understanding Component Numbering
3PAR Confidential
3.18
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
Fibre Channel ports
FC-AL 0
FC-AL 1
A0,B0
A1,B1
top to bottom
Drive magazines 0,1,2,3,4,5,6,7,8,9 left to right
Disks on the drive magazine 0,1,2,3 rear to front
Understanding Component Numbering
3PAR Confidential
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.
Figure 3-18. Pattern for Loading Initial Drive Magazines into the Drive Chassis
NOTE: See the systems planning document or 3PAR Systems Assurance and Pre-
Site Planning Guide drive magazine allocation instructions specific to your system.
0595_L_R1
Drive Cage
DC4
11 23 1224
9 21 1022
7 19 820
5 17 618
3 15 416
1 13 21425 26
3.19Understanding Component Numbering
3PAR Confidential
3.20
Messages and Operator’s Guide InForm OS Version 2.3.1
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. Drive cages and controller nodes depend on
these power supplies, located at the rear of the system, to supply power from the PDUs at the
bottom of the cabinet.
When viewing the cabinet from the rear, the power supplies in each power domain are
numbered from 0 to 3, from left to right. Figure 3-19 shows an expansion cabinet.
NOTE: For further instructions on drive magazine allocation, see the 3PAR
InServ® T-Class Storage Server Installation and Deinstallation Guide.
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Figure 3-19. Numbering of Power Supplies within the Power Domains
0227_L_R2
Power Supplies
0 1 2 3
UpperPower Domain
Lower Power Domain
3.21Understanding Component Numbering
3PAR Confidential
3.22
Messages and Operator’s Guide InForm OS Version 2.3.1
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
4Numbering 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.16
This chapter identifies the major components of the InServ E-Class Storage Server and explains
how storage server components are numbered.
NOTE: Illustrations in this chapter show sample systems and might not match your
particular storage server configuration.
4.1Numbering System and Component Locations for E-Class Servers
3PAR Confidential
4.2
Messages and Operator’s Guide InForm OS Version 2.3.1
4.1 Identifying Storage Server ComponentsFigure 4-1 and Figure 4-2 identify the major components of an InServ E-Class Storage Server in
a 2M (40U) 3PAR cabinet.
Figure 4-1. The Front of an InServ E-Class (in a 2M Rack)
0396_L_R2
Power DistributionUnits (PDUs)
Bezel (ControllerNodes Located
Behind)
Drive Chassis
Service Processor
Identifying Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Figure 4-2. The Rear View of an InServ E-Class (in a 2M Rack)
(Rear View)0398_L_R2
Drive ChassisPower Supplies (4x)
Controller NodePower Supplies (2x)
Power Distribution Units (PDUs) (4x)
ControllerNodes (2x)
Service Processor
4.3Identifying Storage Server Components
3PAR Confidential
4.4
Messages and Operator’s Guide InForm OS Version 2.3.1
4.2 Service Processor PlacementA 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.
Because the service processor is capable of supporting multiple storage servers at the same
operating site, not all cabinets contain a service processor. However, when present, the service
processor is usually installed directly above the PDUs and below the drive cage (see Figure 4-1).
The service processor is powered internally by the storage server and does not require an
external power connection.
When a cabinet does not include a service processor, a filler panel covers the area of the
cabinet that the service processor normally occupies.
4.3 Understanding Component NumberingBecause of the almost unlimited number of potential storage server configurations, 3PAR has
standardized component placement and internal cabling to simplify installation and
maintenance. For this reason, system components are placed in the cabinet according to the
principles outlined in this section and numbered according to their order and location in the
cabinet.
4.3.1 Cabinet Numbering
The InServ F-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.
Service Processor Placement
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Figure 4-3 illustrates numbering of chassis bays in a 3PAR cabinet.
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. Any additional cabinets, or drive chassis cabinets, hold the additional drive
cages that do not fit into the controller node cabinet.
0397_L_R3
Bay #
0
1
2
3
4
5
6
7
8
91011121314
Rail #
32
29
26
23
19
16
10
654321
7
13
4.5Understanding Component Numbering
3PAR Confidential
4.6
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.
Figure 4-4. Controller Node 1M and 2M Cabinet Component Layout by Storage Server Model
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.
0413_L_R1
2M Cabinet
PDU 2PDU 3
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Drive Chassis 4
Drive Chassis 5
Drive Chassis 6
Drive Chassis 7
6U Empty
Node 1
Node 0
1U1U
= 40U
1U1U
1U
3U
3U
3U
3U
2U
2U
3U
3U
3U
3U
6U
1U
1M Cabinet
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Node 1
Node 0
= 20U
1U1U
1U
3U
3U
3U
3U
2U
2U
1U
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
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. Refer to Figure 4-3 for bay numbering.
Numbers for PDUs are assigned:
■ beginning with 0.
■ from top to bottom.
Figure Figure 4-6 illustrates the PDUs at the bottom of 1M and 2 M 3PAR cabinets.
0414_L_R1
1M Cabinet
PDU 0PDU 1
2U Empty
Drive Chassis 0
Drive Chassis 1
Drive Chassis 2
Drive Chassis 3
4U Empty
= 20U
1U2U
3U
3U
3U
3U
4U
1U
4.7Understanding Component Numbering
3PAR Confidential
4.8
Messages and Operator’s Guide InForm OS Version 2.3.1
Figure 4-6. Numbering of PDUs
Each PDU has two power banks, each with a separate circuit breaker, to be used exclusively for
storage server components (Figure 4-7).
Figure 4-7. Power Banks in the PDU
0415_L_R1
2M Cabinet
PDU 2PDU 3
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Drive Chassis 4
Drive Chassis 5
Drive Chassis 6
Drive Chassis 7
6U Empty
Node 1
Node 0
1M Cabinet
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Node 1
Node 0
0221_L_R1
Power Bank 2Power Bank 1
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
4.3.3 Controller Node Numbering
The InServ E-Class Storage Server contains two nodes per system.
For both 1M and 2M cabinets, controller nodes are numbered from top to bottom node 0 and
node 1.
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.9Understanding Component Numbering
3PAR Confidential
4.10
Messages and Operator’s Guide InForm OS Version 2.3.1
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. Slots 1 and 2 can accept PCI adapters such as dual-port Fibre
Channel, Gigabit Ethernet, and iSCSI adapters.
0416_L_R1
2M Cabinet
PDU 2PDU 3
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Drive Chassis 4
Drive Chassis 5
Drive Chassis 6
Drive Chassis 7
6U Empty
Node 1
Node 0
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
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.
■ In quad-port Fibre Channel adapters, the ports are numbered PORT 1, PORT 2, PORT 3, and
PORT 4, from top to bottom.
Inside the controller node are data cache DIMMs and control cache DIMMs.
■ Data cache DIMMs are located in data cache slots 0 through 3.
■ Control cache DIMMs are located on control cache slots 0 and 1 (Figure 4-10).
0399_L_R1
Controller Slot 0
Controller Slots 1 and 2 (PCI Slots)
Controller Slot 3
4.11Understanding Component Numbering
3PAR Confidential
4.12
Messages and Operator’s Guide InForm OS Version 2.3.1
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. A drive chassis houses sixteen drive magazines.
In a 2M cabinet, drive chassis are first placed sequentially below controller node 1 and then
sequentially above controller node 0. In a 1M cabinet, drive chassis are placed sequentially
under controller node 1. Drive chassis are numbered as shown in Figure 4-11.
Data Cache DIMMs: DIMM 0 (J4401) DIMM 1 (J4402) DIMM 2 (J4501) DIMM 3 (J4502)
0400_L_R1
Control Cache DIMMs:DIMM 0 (J7300)DIMM 1 (J7100)
Controller Slot 1
Controller Slot 2
Controller Slot 0
Controller Slot 3
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Figure 4-11. Numbering of Drive Chassis
0415_L_R1
2M Cabinet
PDU 2PDU 3
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Drive Chassis 4
Drive Chassis 5
Drive Chassis 6
Drive Chassis 7
6U Empty
Node 1
Node 0
1M Cabinet
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Node 1
Node 0
NOTE: For systems that occupy multiple cabinets, drive chassis numbers continue
at the bottom of the next cabinet and progress through the top of the cabinet.
4.13Understanding Component Numbering
3PAR Confidential
4.14
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.
Figure 4-12. Drive Chassis - Front View, Drive Magazine Bay Numbering
Figure 4-13. Drive Chassis - Rear View, Port Numbering
0148_L_R2
0406_L_R1
FCAL-B FCAL-A
B3B2B1B0
Drive ChassisPower Supply
Drive ChassisPower Supply
A0A1A2A3
Understanding Component Numbering
3PAR Confidential
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:
Figure 4-14. Drive Magazine Bay Numbering
Drive magazines are loaded in the following ordered pairs:
NOTE: See the systems planning document or 3PAR Systems Assurance and Pre-
Site Planning Guide drive magazine allocation instructions specific to your system.
0148_L_R2
Table 4-1. Drive Magazine Loading Pattern
Group Number
Drive Magazine Pair
Number Drive Magazine Bay
1 1 0, 4
2 11, 15
2 3 8, 12
4 3, 7
3 5 1, 5
6 10, 14
4.15Understanding Component Numbering
3PAR Confidential
4.16
Messages and Operator’s Guide InForm OS Version 2.3.1
4.3.5 Power Supply Numbering
InServ E-Class Storage Server cabinets share a single power domain that contains a drive cage
or controller node and two dedicated power supplies. Drive cages and controller nodes
depend on these two power supplies to supply power from the PDUs at the bottom of the
cabinet. When viewing the cabinet from the rear, the power supplies are numbered as follows
(Figure 4-15):
4 7 9, 13
8 2, 6
Table 4-1. Drive Magazine Loading Pattern (continued)
Group Number
Drive Magazine Pair
Number 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.
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Figure 4-15. Numbering of Power Supplies
0402_L_R2(Rear View)
Drive ChassisPower Supply
Numbering:
0
1
Controller NodePower Supply
Numbering:
1
0
4.17Understanding Component Numbering
3PAR Confidential
4.18
Messages and Operator’s Guide InForm OS Version 2.3.1
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
5Numbering 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.15
This chapter identifies the major components of the InServ F-Class Storage Server and explains
how storage server components are numbered.
NOTE: Illustrations in this chapter show sample systems and might not match your
particular storage server configuration.
5.1Numbering System and Component Locations for F-Class Servers
3PAR Confidential
5.2
Messages and Operator’s Guide InForm OS Version 2.3.1
5.1 Identifying Storage Server ComponentsFigure 5-1 and Figure 5-2 identify the major components of an InServ F-Class Storage Server.
Figure 5-1. The Front of an InServ F400
Power DistributionUnits (PDUs)
Bezel (ControllerNodes Located
Behind)
Drive Chassis
0699_L_R2
Service ProcessorEmpty 1U Space
Identifying Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Figure 5-2. The Rear View of an InServ F400
(Rear View)0698_L_R2
ControllerNodes (4x)
Service ProcessorEmpty 1U Space
Drive ChassisPower Supplies (4x)
Controller NodePower Supplies (4x)
Power Distribution Units (PDUs) (4x)
5.3Identifying Storage Server Components
3PAR Confidential
5.4
Messages and Operator’s Guide InForm OS Version 2.3.1
5.2 Service Processor PlacementA 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.
Because the service processor is capable of supporting multiple storage servers at the same
operating site, not all cabinets contain a service processor. However, when present, the service
processor is usually installed directly above the PDUs and below the drive cage (see Figure 5-1).
The service processor is powered internally by the storage server and does not require an
external power connection.
When a cabinet does not include a service processor, a filler panel covers the area of the
cabinet that the service processor normally occupies.
5.3 Understanding Component NumberingBecause of the almost unlimited number of potential storage server configurations, 3PAR has
standardized component placement and internal cabling to simplify installation and
maintenance. For this reason, system components are placed in the cabinet according to the
principles outlined in this section and numbered according to their order and location in the
cabinet.
5.3.1 Cabinet Numbering
The InServ F-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.
Service Processor Placement
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Figure 5-3 illustrates numbering of chassis bays in a 3PAR cabinet.
Figure 5-3. Numbering of Chassis Bays in the Cabinet
0700_L_R5
33
30
27
19
16
13
10
54321
36
7
32
29
26
23
19
16
13
10
54321
35
6
38
F200 Cabinet F400 Cabinet
76
BayNumber
11121314
10
1
2
3
4
6
7
8
9
0
BayNumber
2
3
4
5
6
1
0
7
8
9
10
12131415
11
RailNumber
RailNumber
5.5Understanding Component Numbering
3PAR Confidential
5.6
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.
Table 5-1 describes the pattern for cabinet numbering in multi-cabinet storage systems and for
operating sites with multiple systems:
Figure 5-4 shows the location of controller node and drive chassis components for InServ F200
and F400 Storage Server controller node cabinets.
Table 5-1. Cabinet Numbering
Cabinet Number
Controller node cabinet C00
Drive chassis cabinets connecting to the first node cabinet C01, C02, C03...C09
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Figure 5-4. Controller Node and Drive Chassis Component Layout by Storage Server Model
5.3.2 PDU Numbering
The four Power Distribution Units (PDUs) occupy the lowest chassis bay in the cabinet. Refer to
Figure 5-3 for bay numbering.
Numbers for PDUs are assigned:
■ beginning with 0.
■ from top to bottom.
0701_L_R3
F400 Cabinet
PDU 2PDU 3
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Drive Chassis 4
Drive Chassis 5
Drive Chassis 6
2U Empty
Node 3
Node 2
Node 0
Node 1
Drive Chassis 7
PDU 2PDU 3
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Drive Chassis 5
Drive Chassis 6
Drive Chassis 8
Node 1
Node 0
Drive Chassis 7
Drive Chassis 4
F200 Cabinet
Drive Chassis 9
1U1U
= 40U
1U1U1U
3U
3U
3U
3U
2U
2U
2U
3U
3U
3U
3U
1U
2U
2U
1U1U
= 40U
1U1U1U
3U
3U
3U
3U
2U
2U
3U
3U
3U
3U
1U
3U
3U
5.7Understanding Component Numbering
3PAR Confidential
5.8
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.
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).
Figure 5-6. Power Banks in the PDU
0216_L_R1
PDUs
0
1
2
3
0221_L_R1
Power Bank 2Power Bank 1
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.
Understanding Component Numbering
3PAR Confidential
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.
Figure 5-7. Numbering of Controller Nodes
0702_L_R2
F400 Cabinet
PDU 2PDU 3
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Drive Chassis 4
Drive Chassis 5
Drive Chassis 6
2U Empty
Node 3
Node 2
Node 0
Node 1
Drive Chassis 7
PDU 2PDU 3
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Drive Chassis 5
Drive Chassis 6
Drive Chassis 8
Node 1
Node 0
Drive Chassis 7
Drive Chassis 4
F200 Cabinet
Drive Chassis 9
5.9Understanding Component Numbering
3PAR Confidential
5.10
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.
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. Fibre Channel
adapters assume the numbers of the PCI slots they occupy.
■ In dual-port adapters, ports are labeled PORT 1 and PORT 2, from top to bottom.
■ In quad-port Fibre Channel adapters, the ports are numbered PORT 1, PORT 2, PORT 3, and
PORT 4, horizontally.
Inside the controller node are data cache DIMMs and control cache DIMMs.
■ Data cache DIMMs are located in data cache slots 0 through 2.
■ Control cache DIMMs are located on control cache slots 0 and 1 (Figure 5-9).
0681_L_R2
Slot 0FC / iSCSI
Slot 1FC / iSCSI
Slot 2FC
EthernetPort (E0)
EthernetPort (E1)
GigE GigE
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
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.
Drive chassis are first placed sequentially below controller node 1 (controller node 3 in an F400)
and then sequentially above controller node 0. Drive chassis are numbered as shown in
Figure 5-10.
Control Cache DIMMs:
Data Cache DIMMs:
DC DIMM 0 (J5801)DC DIMM 1 (J5901)DC DIMM 2 (J6001)
CC DIMM 0 (J4200)CC DIMM 1 (J4300)
0689_L_R2
5.11Understanding Component Numbering
3PAR Confidential
5.12
Messages and Operator’s Guide InForm OS Version 2.3.1
Figure 5-10. 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.
0702_L_R2
F400 Cabinet
PDU 2PDU 3
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Drive Chassis 4
Drive Chassis 5
Drive Chassis 6
2U Empty
Node 3
Node 2
Node 0
Node 1
Drive Chassis 7
PDU 2PDU 3
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Drive Chassis 5
Drive Chassis 6
Drive Chassis 8
Node 1
Node 0
Drive Chassis 7
Drive Chassis 4
F200 Cabinet
Drive Chassis 9
Understanding Component Numbering
3PAR Confidential
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.
Figure 5-11. Drive Chassis - Front View, Drive Magazine Bay Numbering
Figure 5-12. Drive Chassis - Rear View, Port Numbering
0148_L_R2
0406_L_R1
FCAL-B FCAL-A
B3B2B1B0
Drive ChassisPower Supply
Drive ChassisPower Supply
A0A1A2A3
5.13Understanding Component Numbering
3PAR Confidential
5.14
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:
Figure 5-13. Drive Magazine Bay Numbering
Drive magazines are loaded in the following ordered pairs:
NOTE: See the systems planning document or 3PAR Systems Assurance and Pre-
Site Planning Guide drive magazine allocation instructions specific to your system.
0148_L_R2
Table 5-2. Drive Magazine Loading Pattern
Group Number
Drive Magazine Pair
Number Drive Magazine Bay
1 1 0, 4
2 11, 15
2 3 8, 12
4 3, 7
3 5 1, 5
6 10, 14
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
5.3.5 Power Supply Numbering
InServ F-Class Storage Server cabinets share a single power domain that contains a drive cage
or controller node and two dedicated power supplies. Drive cages and controller nodes
depend on these two power supplies to supply power from the PDUs at the bottom of the
cabinet. When viewing the cabinet from the rear, the power supplies are numbered as follows
(Figure 5-14):
4 7 9, 13
8 2, 6
Table 5-2. Drive Magazine Loading Pattern (continued)
Group Number
Drive Magazine Pair
Number 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.15Understanding Component Numbering
3PAR Confidential
5.16
Messages and Operator’s Guide InForm OS Version 2.3.1
Figure 5-14. Numbering of Power Supplies
0702_L_R2
F400 Cabinet
PDU 2PDU 3
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Drive Chassis 4
Drive Chassis 5
Drive Chassis 6
2U Empty
Node 3
Node 2
Node 0
Node 1
Drive Chassis 7
PDU 2PDU 3
PDU 0PDU 1
Service Processor1U Empty
Drive Chassis 3
Drive Chassis 2
Drive Chassis 1
Drive Chassis 0
Drive Chassis 5
Drive Chassis 6
6U Empty
Node 1
Node 0
Drive Chassis 7
Drive Chassis 4
F200 Cabinet
Understanding Component Numbering
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
6Understanding 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.3 Securing the Storage Server 6.32
6.1Understanding S-Class LED Status
3PAR Confidential
6.2
Messages and Operator’s Guide InForm OS Version 2.3.1
6.1 Using the Component LEDsInServ 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.
If you detect any problems during inspection of the LEDs, contact your 3PAR Authorized
Service Provider.
6.1.1 Removing the Bezels and Unlocking the Door
■ To view the node, drive chassis or service processor LEDs, remove the bezels.
WARNING: Hazardous energy is located behind the rear access door of the
storage server cabinet. Use caution when working with the door open.
NOTE: Front locking fascias are optionally available. If the InServ Storage Server
has locking fascia, they must be removed prior to removing the bezels. See
Figure 6-1.
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
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.
0229_L_R1
FasciaLock (4x)
6.3Using the Component LEDs
3PAR Confidential
6.4
Messages and Operator’s Guide InForm OS Version 2.3.1
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.
Figure 6-2. DC2 Drive Cage
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.
0224_L_R1
Drive Magazines
B0
B1
A0
A1
Por
tsA
1A
0B
1B
0P
orts
0 1 2 3 4 0 1 2 3 4
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Figure 6-3. DC4 Drive Cage
0588_L_R1
Drive Magazines
B0
A0
Por
tsA
1B
1P
orts0 1 2 3 4 5 6 7 8 9
6.5Using the Component LEDs
3PAR Confidential
6.6
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.
Figure 6-4. Connections and LEDs on the DC2 Drive Cage FC-AL Modules
0250_L_R1
(Typical)
FC-AL Status LED
Port B RX LED
Port A RX LED
Hot-Plug LED
Port B TX LED
Port A TX LED
Port B
Port A
Split Mode LED
Using the Component LEDs
3PAR Confidential
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.
TX Steady green light Indicates the presence of SFP and
the laser is on and transmitting.
No light Indicates no SFP is present or the
SFP transmitter failed.
FC-AL status Steady green light Indicates the drive cage is
functioning properly, but is not
communicating with any nodes.
Flashing green light (1
blink per second)
Indicates the cage is connected and
communicating with the system
manager of a node in the cluster.
Steady amber light Normal, initial indication for two
seconds upon power up. Otherwise,
indicates FC-AL module error or
other cage error. If both FC-AL
modules have a steady light, the
temperature of a disk drive has
exceeded 62°C, or a power supply
has failed.
Flashing amber light (1
blink per second)
The drive cage has some type of
error, e.g. missing power supply,
but is communicating with a node.
6.7Using the Component LEDs
3PAR Confidential
6.8
Messages and Operator’s Guide InForm OS Version 2.3.1
Rapid toggle between
amber and green light
Indicates a cage firmware upgrade
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.
Split Mode Green light Indicates the drive cage is split into
two logical portions.
No light Indicates the drive cage is not split.
Table 6-1. DC2 Drive Cage FC-AL Module LED Displays (continued)
LED Appearance Meaning
Using the Component LEDs
3PAR Confidential
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.
Figure 6-5. Connections and LEDs on the DC4 Drive Cage FC-AL Modules
0250_L_R1
(Typical)
FC-AL Status LED
Port B RX LED
Port A RX LED
Hot-Plug LED
Port B TX LED
Port A TX LED
Port B
Port A
Split Mode LED
6.9Using the Component LEDs
3PAR Confidential
6.10
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.
TX Steady green light Indicates the presence of SFP
and the LED is on and
transmitting.
No light Indicates no SFP is present or
the SFP transmitter failed.
FC-AL status Steady green light Indicates the drive cage is
functioning properly, but is not
communicating with any nodes.
Flashing green light (1 blink
per second)
Indicates that the cage is
connected and communicating
with the system manager of a
node in the cluster.
Steady amber light Normal, initial indication for
two seconds upon power up.
Otherwise, indicates FC-AL
module error or other cage
error. If both FC-AL modules
have a steady light, the
temperature of a disk drive has
exceeded 55°C, or a power
supply has failed.
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Flashing amber light (1 blink
per second)
The drive cage has some type of
error, for example a failed or
missing power supply, but is
communicating with a node.
Rapid toggle between amber
and green light
Indicates a cage firmware
upgrade initiated by the
upgradecage CLI command is
in progress. 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.
Split Mode Steady green light Indicates the drive cage is split
into two logical portions.
No light Indicates the drive cage is not
split.
Table 6-2. DC4 Drive Cage FC-AL Module LED Displays (continued)
LED Appearance Meaning
6.11Using the Component LEDs
3PAR Confidential
6.12
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.
Figure 6-6. DC2 Drive Magazine Status LEDs
Table 6-3 describes the LED functions of the DC2 drive magazines.
0518_L_R1
Disk Status LEDs
Hot-Plug LED
Drive MagazineStatus LED
DC2
!0123
DC2 (SATA Drive)
Using the Component LEDs
3PAR Confidential
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
20%-on/80%-off
green light
Indicates disk is not spun up but is
functioning.
Steady green light Indicates disk is spun up and waiting for
a command.
Flashing green light Indicates the disk is executing
commands.
No light Indicates no disk is present.
Steady amber light Indicates a disk error, or the disk is
bypassed on both paths (loops).
DC2 Hot-plug Steady green or amber
light (depending on
hardware version).
When illuminated, the drive magazine is
prepared for replacement (hot plug).
No light Indicates magazine is not prepared for
hot plug.
NOTE: After powering on the storage server, allow approximately two minutes
for the disks on the drive magazine to spin up before checking the drive
magazine LEDs.
6.13Using the Component LEDs
3PAR Confidential
6.14
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.
Figure 6-7. DC4 Drive Magazine LEDs
Table 6-4 describes the LED functions of the DC4 drive magazines.
DC4 0587_L_R1
Disk Status LEDs
Hot-Plug LED
Drive MagazineStatus LED
!0123
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.
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Table 6-4. DC4 Drive Magazine LED Displays
LED Appearance Meaning
DC4 Drive
Magazine Status
Steady green light Indicates that the drive
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
percent-on and 80 percent-
off green light
Indicates disk is not spun up but
is functioning.
Steady green light Indicates that the disk is spun up
and waiting for a command.
Flashing green light Indicates that the disk is
executing commands.
No light Indicates no disk is present.
Steady amber light Indicates a disk error, or the disk
is bypassed on both paths
(loops).
DC4 Hot-plug Steady amber light
(depending on hardware
version).
When illuminated, the drive
magazine is prepared for
replacement (hot-plug).
No light Indicates magazine is not
prepared for hot-plug.
Flashing amber light Indicates drive magazine error.
Contact your local service
provider for technical support
and services.
6.15Using the Component LEDs
3PAR Confidential
6.16
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.
Figure 6-8. Controller Node LEDs
Consult Table 6-5 to verify proper functioning of controller nodes.
0252_L_R1
Ethernet10/100 MbpsLED
EthernetActivityLED
Hot-PlugLED
StatusLED
Using the Component LEDs
3PAR Confidential
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
per second)
Indicates node is fully functional and part of the
cluster.
Flashing amber light
(1 blink per second)
Indicates the node has a failed or 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.
Rapidly flashing green (3
blinks per second), in
conjunction with the Hot-
plug LED being solid amber.
Indicates the node is safe to remove.
Steady amber light Indicates an error within the node.
Solid amber and Hot-plug
LED amber
Fatal node failure.
Hot-plug Steady amber light In combination with the Status LED blinking
green 3 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.
Ethernet
activity
Steady or flashing green
light
Indicates ethernet activity.
No light Indicates no ethernet activity.
6.17Using the Component LEDs
3PAR Confidential
6.18
Messages and Operator’s Guide InForm OS Version 2.3.1
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).
Figure 6-9. QLogic Fibre Channel Port LEDs
Each QLogic port in the Fibre Channel adapter has an LED pair composed of one green LED
(left) and one amber LED (right). For dual port QLogic Fibre Channel adapters, the LED pair for
PORT 2 is below the LED pair for PORT 1.
Ethernet 10/
100 MB/sec
Light on 100 MB/sec mode.
No light 10 MB/sec mode (or disconnected).
Table 6-5. Controller Node LED Displays (continued)
LED Appearance Meaning
0516_L_R1
Port 1 LEDs
Port 1
Port 2
Port 2 LEDs
Green LEDs
Amber LEDs
Using the Component LEDs
3PAR Confidential
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.
Off Flashing Cable disconnected or loss of
synchronization.
Flashing Flashing Firmware error.
6.19Using the Component LEDs
3PAR Confidential
6.20
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).
Figure 6-10. LSI Logic 2-Port Fibre Channel Port LEDs
NOTE: For the dual-port Fibre Channel adapters pictured in Figure 6-10, there is a
provision for a third LED to the right of the LEDs for PORT 2; however, no LED
occupies this space.
Port 2
Port 1 LED
Port 2 LED
UnusedHole
0515_L_R1
Port 1
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
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.
Consult this table to verify proper functionality of the Fibre Channel ports.
Table 6-8 on page 6.22 lists all of the LED conditions for the 4-Port LSI Logic Fibre Channel card.
Consult this table to verify proper functionality of the Fibre Channel ports.
Note: LEDs are Numbered and Correspond with Ports3 21 0
1 23 4
0517_L_R1
LEDs
Port 1
Port 2
Port 3
Port 4
6.21Using the Component LEDs
3PAR Confidential
6.22
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 Port Status
Steady amber light Link down or cable disconnected
Off Link up
Flashing green light Indicates I/O activity
Table 6-8. Fibre Channel Port Status LED Indications (LSI Logic 4-Port Adapter)
LED Condition Port Status
Steady amber light Link down or cable disconnected
Steady green light Link up
Flashing green light Indicates I/O activity
Using the Component LEDs
3PAR Confidential
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).
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. Fibre Channel Port Status LED Indications (3PAR 4-Port Adapter)
Yellow LED Green LED Port Status
3PAR Internal Testing Only Off Wake-Up Failure (dead device)
3PAR Internal Testing Only On Normal - Link up at 1-4 GB/sec
3PAR Internal Testing Only Slow Blink Normal - Link Down
0256_L_R1
Port 4
NotUsed (4x)
Port 1
Green (4x)
6.23Using the Component LEDs
3PAR Confidential
6.24
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).
Figure 6-13. Gigabit Ethernet Adapter LEDs
Consult Table 6-10 to verify the proper functioning of Gigabit Ethernet adapter LEDs.
Table 6-10. Gigabit Ethernet Adapter Indicators
LED Appearance Meaning
ACT/LNK Steady green light Valid link partner
Flashing green light Data activity
No light ACT/LNK is off
Speed No light 10 MB/sec
0513_L_R1
ACT/LNK LED
ACTLNK
101001000
Speed LED
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
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.
Figure 6-14. iSCSI Adapter Port LED
Steady green light 100 MB/sec
Steady yellow light 1000 MB/sec
Table 6-10. Gigabit Ethernet Adapter Indicators (continued)
LED Appearance Meaning
0514_L_R1
Green LEDs
Port 2
Port 1
6.25Using the Component LEDs
3PAR Confidential
6.26
Messages and Operator’s Guide InForm OS Version 2.3.1
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):
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.
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Figure 6-15. Power Supply LEDs
Consult Table 6-12 on page 6.28 to verify proper operation of the power supplies.
0291_L_R1
Controller Node Power Supply Drive Chassis Power Supply
AC LED
Power SupplyStatus LED
AC LED
Power SupplyStatus LED
NOTE: The appearance of the power supplies may vary slightly according to
manufacturer and location (drive chassis or controller node).
6.27Using the Component LEDs
3PAR Confidential
6.28
Messages and Operator’s Guide InForm OS Version 2.3.1
6.1.8 Battery Backup Unit LEDs
Depending on the configuration, the InServ S-Class Storage Servers include one or more
battery trays that hold up to four Battery Backup Units (BBUs) apiece. BBUs supply enough
power to write the cache memory to the drive inside the node in the event of a power failure.
BBUs contain two batteries, labeled BATTERY A and BATTERY B. The BBUs also include the
following LEDs (Figure 6-16):
Figure 6-16. Battery Backup Unit LEDs (Magnetek)
Table 6-12. Power Supply LED Displays
LED Appearance Meaning
Power supply
status
Steady green light Indicates power is on.
Steady amber
light
Indicates power supply error.
No light Indicates a broken connection to the power source.
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).
0260_L_R1
Battery AStatus LED
Battery BStatus LED
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Consult Table 6-13 to verify proper functioning of the BBUs.
6.1.9 Power Distribution Unit Lamps
The InServ S-Class Storage Servers include four power distribution units (PDUs). PDUs contain
two power bank lamps (Figure 6-17):
Figure 6-17. Power Distribution Unit Lamps
A blue illuminated lamp denotes that power is being supplied to a power bank. When the blue
lamp is not illuminated, the power bank is not receiving AC input.
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.
Battery B status LED Steady green light Indicates battery B is charged.
Blinking green light Battery is undergoing a test.
Steady amber light Indicates battery error.
0221_L_R1
Power Bank 2Power Bank 1
6.29Using the Component LEDs
3PAR Confidential
6.30
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).
Figure 6-18. Wintec Service Processor LEDs
Consult Table 6-14 to verify proper functioning of the Wintec service processor displays.
Hard Disk Drive LED
0009_L_R2
NIC Port 2 LED
NIC Port 1 LED
Power LED
Reset Button
Power Button
NOTE: The Wintec Service Processor NIC Port LEDs in front and Ethernet Ports in
the rear are crisscrossed. NIC Port 2 corresponds with Eth 1 and NIC Port 1
corresponds with Eth 0.
Table 6-14. Wintec Service Processor LED Displays
LED Appearance Meaning
Hard Disk No light Indicates no activity on the hard drive.
Flashing blue light Indicates hard drive activity.
NIC Port 2 No light No network activity.
Flashing amber light Indicates network activity.
Service Processor LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
6.2.2 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 6-19).
Figure 6-19. Supermicro Service Processor LEDs
Consult Table 6-15 to verify proper functioning of service processor displays.
NIC Port 1 No light .No network activity.
Flashing amber light Indicates network activity.
Power No light The system is off.
Steady blue light Indicates that the system is powered on.
Table 6-14. Wintec Service Processor LED Displays (continued)
LED Appearance Meaning
Table 6-15. Supermicro Service Processor LED Displays
LED Appearance Meaning
Power No light Indicates the service processor is off.
Steady green light Indicates the service processor is on.
Hard Disk Drive LED
NIC Port 2 LEDNIC Port 1 LED
Power LED
Overheat LED
Power Button
0637_L_R1
Reset Button
6.31Service Processor LEDs
3PAR Confidential
6.32
Messages and Operator’s Guide InForm OS Version 2.3.1
6.3 Securing the Storage ServerAfter verifying that the storage server is functioning properly, secure the system by closing the
rear door and locking it with the keys provided with the storage server.
Hard Disk Drive No Light Indicates no hard drive activity.
Flashing amber light Indicates hard drive activity.
NIC Port 2 No light Indicates the port is not connected.
Steady green light Indicates the port is connected.
Flashing green light Indicates network activity.
NIC Port 1 No light Indicates the port is not connected.
Steady green light Indicates the port is connected.
Flashing green light Indicates network activity.
Overheat No light Indicates the service processor
temperature is normal.
Steady red light Indicates the service processor
temperature is overheating.
Table 6-15. Supermicro Service Processor LED Displays (continued)
LED Appearance Meaning
WARNING: Hazardous energy is located behind the rear access door of the
storage server cabinet. Use caution when working with the door open.
Securing the Storage Server
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
7Understanding 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.2 Securing the Storage Server 7.20
7.1Understanding T-Class LED Status
3PAR Confidential
7.2
Messages and Operator’s Guide InForm OS Version 2.3.1
7.1 Using the Component LEDsInServ 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.
If you detect any problems during inspection of the LEDs, contact your 3PAR Authorized
Service Provider.
7.1.1 Removing the Bezels and Unlocking the Door
■ To view the node, drive chassis or service processor LEDs, remove the bezels.
■ To view the power supply, battery or PDU LEDs, open the rear door by unlatching the three
latches of the door (S800 InServ Storage Servers contain PDUs in the front and rear of the
cabinet).
WARNING: Hazardous energy is located behind the rear access door of the
storage server cabinet. Use caution when working with the door open.
NOTE: If your 3PAR cabinet has locking fascias, you must first remove the fascias
to access the server bezel.
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.
Using the Component LEDs
3PAR Confidential
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.
Figure 7-1. DC4 Drive Cage
0588_L_R1
Drive Magazines
B0
A0
Por
tsA
1B
1P
orts
0 1 2 3 4 5 6 7 8 9
7.3Using the Component LEDs
3PAR Confidential
7.4
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):
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.
0655_L_R1
(Typical)
FC-AL Status LED
Port B RX LED
Port A RX LED
Hot-Plug LED
Port B TX LED
Port A TX LED
Port B
Port A
Split Mode LED 4 Gb/s
Using the Component LEDs
3PAR Confidential
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.
No light Indicates SFP is not present or
the SFP transmitter failed.
FC-AL status Steady green light Indicates the drive cage is
functioning properly, but is not
communicating with any nodes.
Flashing green light (1 blink
per second)
Indicates the cage is connected
and communicating with the
system manager of a node in
the cluster.
Steady amber light Normal, initial indication for
two seconds upon power up.
Otherwise, indicates FC-AL
module error or other cage
error. If both FC-AL modules
have a steady light, the
temperature of a disk drive has
exceeded 62°C, or a power
supply has failed.
7.5Using the Component LEDs
3PAR Confidential
7.6
Messages and Operator’s Guide InForm OS Version 2.3.1
Flashing amber light (1 blink
per second)
The drive cage has some type of
error, for example a failed or
missing power supply, but is
communicating with a node.
Rapid toggle between amber
and green light
Indicates a cage firmware
upgrade initiated by the
upgradecage CLI command is
in progress. 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.
Split Mode Steady green light Indicates the drive cage is split
into two logical portions.
No light Indicates the drive cage is not
split.
4 GB/s Steady green light Indicates the transfer rate is
operating at 4 Gb/s.
No light Indicates the transfer rate is
operating at 2 Gb/s.
Table 7-1. Drive Cage DC4 FC-AL Module LED Displays (continued)
LED Appearance Meaning
Using the Component LEDs
3PAR Confidential
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):
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
Magazine Status
Steady green light Indicates the drive magazine is
functioning properly.
Steady amber light Indicates a drive magazine error,
or one or more drives are
bypassed on at least one path.
DC4 0587_L_R1
Disk Status LEDs
Hot-Plug LED
Drive MagazineStatus LED
!0123
7.7Using the Component LEDs
3PAR Confidential
7.8
Messages and Operator’s Guide InForm OS Version 2.3.1
Disk status Quick flashing, or 20
percent-on and 80 percent-
off green light
Indicates disk is not spun up but
is functioning.
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.
Steady amber light Indicates a disk error, or the disk
is bypassed on both paths
(loops).
DC4 Hot-plug Steady amber light
(depending on hardware
version).
When illuminated, the drive
magazine is prepared for
replacement (hot-plug).
No light Indicates magazine is not
prepared for hot-plug.
Flashing amber light Indicates drive magazine error.
Contact your local service
provider for technical support
and services.
Table 7-2. Drive Magazine LED Displays (continued)
LED Appearance Meaning
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.
Using the Component LEDs
3PAR Confidential
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):
Figure 7-4. Controller Node LEDs
Consult Table 7-3 to verify proper functioning of controller nodes.
0571_L_R2
Node Hot-plug LED
Node Status LED
Ethernet10/100/1000 MbpsLED
Ethernet Activity LED
DiskHot-plug LED
Table 7-3. Controller Node LED Displays
LED Appearance Meaning
Disk Hot-plug Steady amber light Indicates the internal disk is
ready for hot-plug.
No light Indicates the internal disk is not
ready for hot-plug.
7.9Using the Component LEDs
3PAR Confidential
7.10
Messages and Operator’s Guide InForm OS Version 2.3.1
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.
Node Status Flashing green light (1 blink
per second)
Indicates node is fully functional
and part of the cluster.
Flashing amber light
(1 blink per second)
Indicates the node has a failed
or 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.
Rapidly flashing green (3
blinks per second), in
conjunction with the hot-plug
LED being solid amber.
Indicates the node is safe to
remove.
Steady amber light Indicates an error within the
node.
Solid amber and hot-plug LED
amber
Indicates a fatal node failure.
Table 7-3. Controller Node LED Displays (continued)
LED Appearance Meaning
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
7.1.4 3PAR Fibre Channel Port LEDs
The 3PAR Fibre Channel adapter contained in the controller node also contains Fibre Channel
port LEDs (Figure 7-5).
Figure 7-5. 3PAR 4-Port Fibre Channel LEDs
Ethernet activity Steady or flashing green light Indicates Ethernet activity.
No light Indicates no Ethernet activity.
Ethernet 10/100/
1000 MB/sec
Steady amber light 1000 MB/sec mode.
Steady green light 100 MB/sec mode.
No light 10 MB/sec mode.
Table 7-3. Controller Node LED Displays (continued)
LED Appearance Meaning
0256_L_R2
Port 4
Port 1
LED (4x)
7.11Using the Component LEDs
3PAR Confidential
7.12
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.
7.1.5 QLogic iSCSI Port LEDs
The QLogic iSCSI adapter contains two ports. There is one LED for each port as shown in
(Figure 7-6).
Figure 7-6. iSCSI Adapter LEDs
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.
0514_L_R2
LEDs (2x)
Port 2
Port 1
Using the Component LEDs
3PAR Confidential
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.
7.1.6 Power Supply LEDs
Power supply units are located at the rear of all drive cages and controller nodes. Power
supplies have the following LEDs (Figure 7-7):
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.13Using the Component LEDs
3PAR Confidential
7.14
Messages and Operator’s Guide InForm OS Version 2.3.1
Figure 7-7. Power Supply LEDs
0632_L_R1
Controller Node Power Supply
AC LED
Power SupplyStatus LED
AC LED
Power SupplyStatus LED
Drive Chassis Power Supply
NOTE: The appearance of the drive chassis and controller node power supplies
can vary slightly according to manufacturer and location.
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Consult Table 7-6 to verify proper operation of the power supplies.
7.1.7 Battery Backup Unit LEDs
Depending on the configuration, storage servers with 3PAR cabinets include one or more
battery trays that hold up to four Battery Backup Units (BBUs) apiece. BBUs supply enough
power to write the cache memory to the drive inside the node in the event of a power failure.
BBUs contain two batteries, labeled BATTERY A and BATTERY B. The BBUs also include the
following LEDs (Figure 7-8):
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.
No light Indicates no AC is entering from an
external source (for example, when
power is off or when using battery
power).
7.15Using the Component LEDs
3PAR Confidential
7.16
Messages and Operator’s Guide InForm OS Version 2.3.1
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.
No light BBUs or power supply is turned
off.
Battery B status LED Steady green light Indicates battery B is charged.
Blinking green light Indicates the battery is undergoing
a test.
Steady amber light Indicates a battery error.
No light BBUs or power supply is turned
off.
0260_L_R1
Battery AStatus LED
Battery BStatus LED
Using the Component LEDs
3PAR Confidential
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):
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.9 Service Processor LEDs
The Supermicro service processor LEDs are defined in the following section. The LEDs are
located at the top of the service processor (Figure 7-10).
Figure 7-10. Supermicro Service Processor LEDs
Consult Table 7-8 to verify proper functioning of the Supermicro service processor displays.
0261_L_R1
Power Bank 2
Power Bank Lamps
Power Bank 1
Hard Disk Drive LED
NIC Port 2 LEDNIC Port 1 LED
Power LED
Overheat LED
Power Button
0637_L_R1
Reset Button
7.17Using the Component LEDs
3PAR Confidential
7.18
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.
Hard Disk No light Indicates there is no hard drive activity.
Flashing amber light Indicates there is hard drive activity.
NIC Port 2 No light Indicates the port is not connected.
Flashing green light Indicates there is network activity.
Steady green light Indicates the port is connected and there is
network activity.
NIC Port 1 No light Indicates the port is not connected.
Flashing green light Indicates there is network activity.
Steady green light Indicates the port is connected and there is
network activity.
Overheat No light Indicates the service processor
temperature is normal.
Steady red light Indicates the service processor
temperature is overheating.
Using the Component LEDs
3PAR Confidential
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).
Figure 7-11. Supermicro II Service Processor LEDs
Consult Table 7-9 to verify proper functioning of the Supermicro II service processor displays.
Table 7-9. 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.
Hard Disk Drive No light Indicates no hard drive activity.
Flashing amber light Indicates hard drive activity.
NIC Port 2 No light Indicates the port is not connected.
Steady green light Indicates the port is connected and there is
network activity.
Flashing green light Indicates network activity.
Hard Disk Drive LED
NIC Port 2 LED
NIC Port 1 LED
Power LED
Overheat LED
0802_L_R1
Reset Button
Power Button
7.19Using the Component LEDs
3PAR Confidential
7.20
Messages and Operator’s Guide InForm OS Version 2.3.1
7.2 Securing the Storage ServerAfter verifying that the storage server is functioning properly, secure the system by closing the
rear door and locking it with the keys provided with the storage server.
NIC Port 1 No light Indicates the port is not connected.
Steady green light Indicates the port is connected and there is
network activity.
Flashing green light Indicates network activity.
Overheat No light Indicates the service processor
temperature is normal.
Steady red light Indicates the service processor is
overheating.
Flashing red light Indicates the service processor has a failed
fan.
Table 7-9. Supermicro II Service Processor Front-Panel Displays (continued)
LED Appearance Meaning
WARNING: Hazardous energy is located behind the rear access door of the
storage server cabinet. Use caution when working with the door open.
Securing the Storage Server
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
8Understanding 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.5 Controller Node Power Supply LEDs 8.20
8.1.6 Power Distribution Unit Lamps 8.21
8.2 Service Processor LEDs 8.22
8.2.1 Wintec Service Processor 8.22
8.1Understanding E-Class LED Status
3PAR Confidential
8.2
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 LEDsInServ 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.
If you detect any problems during inspection of the LEDs, contact your 3PAR Authorized
Service Provider.
8.1.1 Bezel LEDs
InServ E-Class Storage Server LEDs are provided at the front of the storage server on the bezel
for quick assessment of node health. LEDs are provided as follows:
Figure 8-1. Bezel LEDs
NODE 0 NODE 10 1
Fan 0 LED
Fan 1 LED
Node 0 LED
Node 1 LED0344_L_R1
Using the Component LEDs
3PAR Confidential
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
Fan 1
Solid green light Indicates fan is operating normally.
Solid amber light Indicates fan error.
Node 0
Node 1
Flashing green light (1 blink
per second)
Indicates node is fully functional and part of
the cluster.
Flashing amber light
(1 blink per second)
Indicates the node has a failed or 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.
Rapidly flashing green (3
blinks per second), in
conjunction with the Hot-
plug LED being solid amber
(see Controller Node LEDs on
page 8.13)
Indicates the node is safe to remove.
Steady amber light Indicates an error within the node.
Solid amber and Hot-plug
LED amber (see Controller
Node LEDs on page 8.13)
Fatal node failure.
8.3Using the Component LEDs
3PAR Confidential
8.4
Messages and Operator’s Guide InForm OS Version 2.3.1
8.1.2 Removing the Bezels and Unlocking the Door
■ 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.
8.1.3 Drive Chassis LEDs
The InServ E-Class Storage Server drive chassis LEDs are located at the rear of the chassis. The
drive chassis houses the following components, each with their own LEDs:
■ one OPs panel.
■ two Fibre Channel Arbitrated Loops (FCAL).
■ two Power supply/cooling modules.
Figure 8-2. Drive Chassis Components
WARNING: Hazardous energy is located behind the rear access door of the
storage server cabinet. Use caution when working with the door open.
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.
InterfaceCard
FCAL-B
OPs Panel
Power Supply/Cooling Modules
InterfaceCard
FCAL-A0345 L R1
Using the Component LEDs
3PAR Confidential
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:
Figure 8-3. Drive Chassis OPs Panel LEDs
Consult Table 8-2 for OPs panel LED meanings.
Invalid Address LED Power On LED
Power Supply/Cooling/Temperature Fault LED
2 Gb Link Speed LED
System Fault LED
OPs Panel LEDs0348_L_R1
8.5Using the Component LEDs
3PAR Confidential
8.6
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
green light
Used in conjunction with Power Supply/Cooling/Temperature
Fault LED, 2 Gb Link Speed LED, Invalid Address LED, and
System Fault LED as described below:
Power
Supply/
Cooling/
Temperature
Fault LED
Steady
amber light
Indicates the following:
■ Test state (5 seconds), if:
◆ Power On LED is steady green.
◆ System Fault LED is steady amber.
◆ Invalid Address LED is steady amber.
◆ 2 Gb Link Speed LED is steady green.
■ Power supply or fan fault, if:
◆ Power On LED is steady green.
◆ System Fault LED is off.
■ Over or under temperature, if:
◆ Power On LED is steady green.
◆ System Fault LED is flashing amber.
Flashing
amber light
Indicates the following:
■ Power supply is removed and system power redundancy check
option is set, if:
◆ Power On LED is steady green.
◆ System Fault LED is flashing amber.
■ OPs to ESI communications failed, if:
◆ Power On LED is steady green.
◆ System Fault LED is steady amber.
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
2 Gb Link
Speed LED
Steady
green light
Indicates the following:
■ 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.
No green
light
Indicates the that 5 V aux is present, overall power fail, if Power
On LED is green and all other LEDs are off.
Invalid
Address LED
Steady
amber light
Indicates 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.
■ 2 Gb Link Speed LED is steady amber.
Flashing
amber light
Indicates an invalid address mode setting if Power On LED is
steady green.
Table 8-2. Drive Chassis OPs Panel LED Meanings (continued)
LED Appearance Meaning
8.7Using the Component LEDs
3PAR Confidential
8.8
Messages and Operator’s Guide InForm OS Version 2.3.1
System Fault
LED
Steady
amber light
Indicates the following:
■ 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.
◆ Power Supply/Cooling/Temperature Fault LED is off.
■ Unknown FCAL module type installed, 12C Bus failure, or
backplane autostart watchdog failure, if:
◆ Power ON LED is steady green.
◆ Power Supply/Cooling/Temperature Fault LED is off.
■ Ops to ESI communication failure, if:
◆ Power ON LED is steady green.
◆ Power Supply/Cooling/Temperature Fault LED is flashing.
Flashing
amber light
Indicates the following:
■ Over or under temperature, if:
◆ Power On LED is steady green.
◆ Power Supply/Cooling/Temperature Fault LED is steady
amber.
■ Power supply is removed and system power redundancy check
option is set, if:
◆ Power On LED is steady green.
◆ Power Supply/Cooling/Temperature Fault LED is flashing.
■ No drives fitted, if:
◆ Power ON LED is steady green.
◆ Power Supply/Cooling/Temperature Fault LED is off.
Table 8-2. Drive Chassis OPs Panel LED Meanings (continued)
LED Appearance Meaning
Using the Component LEDs
3PAR Confidential
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:
Figure 8-4. FCAL Module LEDs
Consult Table 8-3 for FCAL module LED meanings.
Table 8-3. FCAL Module LED Meanings
LED Appearance Meaning
Host Port 0 Signal Good Steady green light Indicates that incoming Fibre
Channel signal is good.
Host Port 1 Signal Good Steady green light Indicates that incoming Fibre
Channel signal is good.
0350_L_R1
Host Port 0Signal Good LED
Host Port 1Signal Good LED
Module Fault LED
Host Port 2Signal Good LED
Host Port 3Signal Good LED
Loops Status LED
8.9Using the Component LEDs
3PAR Confidential
8.10
Messages and Operator’s Guide InForm OS Version 2.3.1
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.
Flashing green
light
Indicates that the drives are
bypassed by module.
Module Fault Steady amber light FCAL module is failed.
Table 8-3. FCAL Module LED Meanings (continued)
LED Appearance Meaning
Using the Component LEDs
3PAR Confidential
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:
Figure 8-5. Drive Chassis Power Supply/Cooling Module LEDs
Consult Table 8-4 for power supply/cooling module LED meanings.
Power Supply Good LED
AC Input Fail LED
Fan Fault LED
DC Output Fail LED
0349_L_R1
Table 8-4. Power Supply/Cooling Module LED Meanings
LED Appearance Meaning
Power Supply Good Steady green light Indicates the power supply is operating normally.
Steady amber light Indicates the power supply is not operating
correctly.
AC Input Fail Steady green light Indicates the AC input is normal.
Steady amber light Indicates AC input failure.
8.11Using the Component LEDs
3PAR Confidential
8.12
Messages and Operator’s Guide InForm OS Version 2.3.1
8.1.4 Drive Magazine LEDs
InServ E-Class Storage Server drive magazines LEDs can be viewed at the front of the storage
server. Drive magazines contain the following LEDs:
Figure 8-6. Drive Magazine LEDs
Consult Table 8-5 to verify proper functioning of disks and drive magazines.
Fan Fault Steady green light Indicates the fan is operating normally.
Steady amber light Indicates fan fault.
DC Output Fail Steady green light Indicates the DC output is normal.
Steady amber light Indicates DC output failure.
Table 8-4. Power Supply/Cooling Module LED Meanings (continued)
LED Appearance Meaning
Activity (Green) LED
0149_L_R3
Fault (Amber) LED
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
8.1.5 Controller Node LEDs
InServ E-Class Storage Server controller nodes contain the following LEDs:
Figure 8-7. Controller Node LEDs
Consult Table 8-6 to verify proper functioning of controller nodes.
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.
Fault Steady amber light Indicates drive fault.
No light Indicates the following:
■ No drive is present.
■ Drive power is on.
■ Drive activity.
Flashing amber
light
Indicates the drive is bypassed by the FCAL module.
0200_L_R1
Status LEDHot-Plug LED
Ethernet Activity LEDs
8.13Using the Component LEDs
3PAR Confidential
8.14
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
per second)
Indicates node is fully functional and
part of the cluster.
Flashing amber light
(1 blink per second)
Indicates the node has a failed or
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.
Rapidly flashing green (3 blinks
per second), in conjunction
with the Hot-plug LED being
solid amber.
Indicates the node is safe to remove.
Steady amber light Indicates an error within the node.
Solid amber and Hot-plug LED
amber
Fatal node failure.
Hot-plug Steady amber light In combination with the Status LED
blinking green 3 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.
Ethernet activity Steady or flashing green light Indicates Ethernet activity.
No light Indicates no Ethernet activity.
Using the Component LEDs
3PAR Confidential
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.
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.15 lists all of the LED conditions for the 2-Port LSI Logic Fibre Channel card.
Consult this table to verify proper functionality of the Fibre Channel ports.
=
Table 8-7. Fibre Channel Port Status LED Indications (LSI Logic 2-Port Adapter)
LED Condition Port Status
Steady amber light Link down or cable disconnected
Off Link up
Flashing green light Indicates I/O activity
0257_L_R1
Amber LEDGreen LED
8.15Using the Component LEDs
3PAR Confidential
8.16
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).
Figure 8-9. Emulex 2-Port Fibre Channel LEDs
Consult Table 8-8 to verify proper function of the Emulex Fibre Channel adapter LED.
Table 8-8. Emulex Fibre Channel Port Status LED Indications
Yellow LED Green LED Port Status
Off Off Wake-up failure (dead device)
On Off POST Failure (dead board)
Green 2xYellow 2x
0269_L_R2
(Port 1*)
(Port 2*)
*These ports correspond to the numbering as reported by the InForm OS.
Node Frame
Node Frame
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Slow Blink Off Wake-up failure monitor
Fast Blink Off POST failure
Flashing Off POST processing in progress
Off On Failure while functioning
On On Failure while functioning
1 Blink On 1Gb Link rate - Normal, link up
2 Blinks On 2Gb Link rate - Normal, link up
3 Blinks On 4Gb Link rate - Normal, link up
Off Slow Blink Normal - Link down or not started
Slow Blink Slow Blink Off-line for download
Fast Blink Slow Blink Restricted off-line mode (Waiting restart)
Flashing Slow Blink Restricted off-line mode (Test active)
Table 8-8. Emulex Fibre Channel Port Status LED Indications (continued)
Yellow LED Green LED Port Status
8.17Using the Component LEDs
3PAR Confidential
8.18
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).
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
LED Condition Port Status
Steady green Indicates that a link is established
Flashing green Indicates receiving or transmitting activity.
0351_L_R1
QLogic iSCSI Adapter
Green LEDs
Using the Component LEDs
3PAR Confidential
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).
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.
Flashing green light Data activity.
No light ACT/LNK is off.
Speed No light 10 MB/sec.
Steady green light 100 MB/se.
Steady orange light 1000 MB/sec.
0352_L_R1
Gigabit Ethernet Adapter
Speed LED ACT/LINK LED
8.19Using the Component LEDs
3PAR Confidential
8.20
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. The LEDs are located on the rear of the power supply units as follows (Figure 8-12):
Figure 8-12. Controller Node Power Supply LEDs
Consult Table 8-11 to verify proper operation of the power supplies.
0353_L_R1
AC LED
Power SupplyStatus LED
Battery StatusLED
Table 8-11. Power Supply LED Displays
LED Appearance Meaning
Power Supply Status Steady green light Indicates power is on.
Steady amber light Indicates power supply error.
No light Indicates a broken connection to the power
source.
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
8.1.6 Power Distribution Unit Lamps
InServ Storage Servers include four Power Distribution Units (PDUs). PDUs contain two power
bank lamps (Figure 8-13):
Figure 8-13. Power Distribution Unit Lamps
A blue illuminated lamp denotes that power is being supplied to a power bank. When the blue
lamp is not illuminated, the power bank is not receiving AC input.
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.
Table 8-11. Power Supply LED Displays (continued)
LED Appearance Meaning
0221_L_R1
Power Bank 2Power Bank 1
8.21Using the Component LEDs
3PAR Confidential
8.22
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).
Figure 8-14. Wintec Service Processor LEDs
Consult Table 8-12 to verify proper functioning of the Wintec service processor displays.
Hard Disk Drive LED
0009_L_R2
NIC Port 2 LED
NIC Port 1 LED
Power LED
Reset Button
Power Button
NOTE: The Wintec Service Processor NIC Port LEDs in front and Ethernet Ports in
the rear are crisscrossed. NIC Port 2 corresponds with Eth 1 and NIC Port 1
corresponds with Eth 0.
Table 8-12. Wintec Service Processor LED Displays
LED Appearance Meaning
Hard Disk No light Indicates no activity on the hard drive.
Flashing blue light Indicates hard drive activity.
NIC Port 2 No light No network activity.
Flashing amber light Indicates network activity.
Service Processor LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
8.2.2 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 8-15).
Figure 8-15. Supermicro Service Processor LEDs
Consult Table 8-13 to verify proper functioning of service processor displays.
NIC Port 1 No light No network activity.
Flashing amber light Indicates network activity.
Power No light The system is off.
Steady blue light Indicates that the system is powered
on.
Table 8-12. Wintec Service Processor LED Displays (continued)
LED Appearance Meaning
Hard Disk Drive LED
NIC Port 2 LEDNIC Port 1 LED
Power LED
Overheat LED
Power Button
0637_L_R1
Reset Button
8.23Service Processor LEDs
3PAR Confidential
8.24
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.
Hard Disk Drive No light Indicates there is no hard drive activity.
Flashing amber light Indicates there is hard drive activity.
NIC Port 2 No light Indicates the port is not connected.
Flashing green light Indicates there is network activity.
Steady green light Indicates the port is connected.
NIC Port 1 No light Indicates the port is not connected.
Flashing green light Indicates there is network activity.
Steady green light Indicates the port is connected.
Overheat No light Indicates the service processor
temperature is normal.
Steady red light Indicates the service processor
temperature is overheating.
Service Processor LEDs
3PAR Confidential
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.
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. 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.
Hard Disk Drive No light Indicates no hard drive activity.
Flashing amber light Indicates hard drive activity.
NIC Port 2 No light Indicates the port is not connected.
Steady green light Indicates the port is connected and there is
network activity.
Flashing green light Indicates network activity.
Hard Disk Drive LED
NIC Port 2 LED
NIC Port 1 LED
Power LED
Overheat LED
0802_L_R1
Reset Button
Power Button
8.25Service Processor LEDs
3PAR Confidential
8.26
Messages and Operator’s Guide InForm OS Version 2.3.1
8.3 Securing the Storage Server1 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.
NIC Port 1 No light Indicates the port is not connected.
Steady green light Indicates the port is connected and there is
network activity.
Flashing green light Indicates network activity.
Overheat No light Indicates the service processor
temperature is normal.
Steady red light Indicates the service processor is
overheating.
Flashing red light Indicates the service processor has a failed
fan.
Table 8-14. Supermicro II Service Processor Front-Panel Displays (continued)
LED Appearance Meaning
WARNING: Hazardous energy is located behind the rear access door of the
storage server cabinet. Use caution when working with the door open.
Securing the Storage Server
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
9Understanding F-Class LED Status
In this chapter9.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.2 Service Processor LEDs 9.21
9.3 Securing the Storage Server 9.24
9.1Understanding F-Class LED Status
3PAR Confidential
9.2
Messages and Operator’s Guide InForm OS Version 2.3.1
9.1 Using the Component LEDsInServ 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.
If you detect any problems during inspection of the LEDs, contact your 3PAR Authorized
Service Provider.
9.1.1 Bezel LEDs
LEDs are provided at the front of the F-Class Storage Server on the bezel for quick assessment
of node health. LEDs are provided as follows:
Figure 9-1. Bezel LEDs
0722_L_R2
NODE 0 NODE 10 1
NODE 2 NODE 32 3
Fan 2 Status LED
Fan 3 Status LED
Node 2 Status LED
Node 3 Status LED
Fan 0 Status LED
Fan 1 Status LED
Node 0 Status LED
Node 1 Status LED
Using the Component LEDs
3PAR Confidential
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
Fan 1
Fan 2
Fan 3
Solid green light Indicates fan is operating normally.
Solid amber light Indicates fan error.
Node 0
Node 1
Node 2
Node 3
Flashing green light (1 blink per
second)
Indicates node is fully functional and part
of the cluster.
Flashing amber light
(1 blink per second)
Indicates the node has a failed or missing
power supply, fan or battery, but the node
is still operational.
Steady green light Indicates node is in the process of joining
the cluster.
Rapidly flashing green (3 blinks
per second), in conjunction
with the nodes hot-plug LED
being solid amber (see
Controller Node LEDs on
page 9.14)
Indicates the node is safe to remove.
Steady amber light Indicates an error within the node.
Steady amber and hot-plug LED
amber (see Controller Node
LEDs on page 9.14)
Fatal node failure.
9.3Using the Component LEDs
3PAR Confidential
9.4
Messages and Operator’s Guide InForm OS Version 2.3.1
9.1.2 Removing the Bezels and Unlocking the Door
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.
9.1.3 Drive Chassis LEDs
The F-Class Storage Server drive chassis LEDs are located at the front and rear of the chassis.
The drive chassis houses the following components, each with their own LEDs:
■ One OPs panel.
■ Two interface cards.
■ Two Power supply/cooling modules.
Figure 9-2. Drive Chassis Components
WARNING: Hazardous energy is located behind the rear access door of the
storage server cabinet. Use caution when working with the door open.
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.
InterfaceCard
FCAL-B
OPs Panel
Power Supply/Cooling Modules
InterfaceCard
FCAL-A0345_L_R2
PS1 PS0
Using the Component LEDs
3PAR Confidential
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:
Figure 9-3. Drive Chassis OPs Panel LEDs
Invalid Address LED Power On LED
Power Supply/Cooling/Temperature Fault LED
2 Gb Link Speed LED
System Fault LED
OPs Panel LEDs0348_L_R1
9.5Using the Component LEDs
3PAR Confidential
9.6
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
green light
Used in conjunction with Power Supply/Cooling/Temperature
Fault LED, 2 Gb Link Speed LED, Invalid Address LED, and
System Fault LED as described below.
Power
Supply/
Cooling/
Temperature
Fault LED
Steady
amber light
Indicates the following:
■ Test state (5 seconds), if:
◆ Power On LED is steady green.
◆ System Fault LED is steady amber.
◆ Invalid Address LED is steady amber.
◆ 2 Gb Link Speed LED is steady green.
■ Power supply or fan fault, if:
◆ Power On LED is steady green.
◆ System Fault LED is off.
■ Over or under temperature, if:
◆ Power On LED is steady green.
◆ System Fault LED is flashing amber.
Flashing
amber light
Indicates the following:
■ One power supply is removed if:
◆ Power On LED is steady green.
◆ System Fault LED is flashing amber.
■ OPs to ESI communications failed, if:
◆ Power On LED is steady green.
◆ System Fault LED is steady amber.
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
2 Gb Link
Speed LED
Steady
green light
Indicates the following:
■ 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.
Flashing
green light
One or more drives are bypassed on at least one loop.
No green
light
Indicates the 5 V aux is present, overall power fail, if Power On
LED is green and all other LEDs are off.
Invalid
Address LED
Steady
amber light
Indicates 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.
■ 2 Gb Link Speed LED is steady amber.
Flashing
amber light
Indicates an invalid address mode ID switch setting if Power On
LED is steady green.
Table 9-2. Drive Chassis OPs Panel LED Meanings (continued)
LED Appearance Meaning
9.7Using the Component LEDs
3PAR Confidential
9.8
Messages and Operator’s Guide InForm OS Version 2.3.1
System Fault
LED
Steady
amber light
Indicates the following:
■ 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.
◆ Power Supply/Cooling/Temperature Fault LED is off.
■ Unknown FCAL module type installed, I2C Bus failure, or
backplane autostart watchdog failure, if:
◆ Power ON LED is steady green.
◆ Power Supply/Cooling/Temperature Fault LED is off.
■ Ops to ESI communication failure, if:
◆ Power ON LED is steady green.
◆ Power Supply/Cooling/Temperature Fault LED is flashing.
Flashing
amber light
Indicates the following:
■ Over or under temperature, if:
◆ Power On LED is steady green.
◆ Power Supply/Cooling/Temperature Fault LED is steady
amber.
■ Power supply is removed if:
◆ Power On LED is steady green.
◆ Power Supply/Cooling/Temperature Fault LED is flashing.
■ No drives fitted, if
◆ Power ON LED is steady green.
◆ Power Supply/Cooling/Temperature Fault LED is off.
Table 9-2. Drive Chassis OPs Panel LED Meanings (continued)
LED Appearance Meaning
Using the Component LEDs
3PAR Confidential
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:
Figure 9-4. Interface Card LEDs
Consult Table 9-3 for interface card LED meanings.
Table 9-3. Interface Card LED Meanings
LED Appearance Meaning
Host Port 0 Signal Good Steady green light Indicates the incoming Fibre
Channel signal is good.
Host Port 1 Signal Good Steady green light Indicates the incoming Fibre
Channel signal is good.
0350_L_R1
Host Port 0Signal Good LED
Host Port 1Signal Good LED
Module Fault LED
Host Port 2Signal Good LED
Host Port 3Signal Good LED
Loops Status LED
9.9Using the Component LEDs
3PAR Confidential
9.10
Messages and Operator’s Guide InForm OS Version 2.3.1
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.
Flashing green light Indicates the drives are bypassed
by module.
Module Fault Steady amber light FCAL module is failed.
Table 9-3. Interface Card LED Meanings (continued)
LED Appearance Meaning
Using the Component LEDs
3PAR Confidential
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:
Figure 9-5. Drive Chassis Power Supply/Cooling Module LEDs
Consult Table 9-4 for power supply/cooling module LED meanings.
Table 9-4. Drive Chassis Power Supply/Cooling Module LED Meanings
LED Appearance Meaning
Power Supply Good Steady green light Indicates the power supply is
operating normally.
Steady amber light Indicates the power supply is
not operating correctly.
Power Supply Good LED
AC Input Fail LED
Fan Fault LED
DC Output Fail LED
0349_L_R1
9.11Using the Component LEDs
3PAR Confidential
9.12
Messages and Operator’s Guide InForm OS Version 2.3.1
9.1.4 Drive Magazine LEDs
The F-Class Storage Server drive magazine LEDs can be viewed at the front of the storage
server. Drive magazines contain the following LEDs:
Figure 9-6. Drive Magazine LEDs
AC Input Fail Steady green light Indicates the AC input is normal.
Steady amber light Indicates AC input failure.
Fan Fault Steady green light Indicates the fan is operating
normally.
Steady amber light Indicates fan fault.
DC Output Fail Steady green light Indicates the DC output is
normal.
Steady amber light Indicates DC output failure.
Table 9-4. Drive Chassis Power Supply/Cooling Module LED Meanings (continued)
LED Appearance Meaning
Activity (Green) LED
0149_L_R3
Fault (Amber) LED
Using the Component LEDs
3PAR Confidential
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
light (once every 3
seconds)
Indicates the drive has spun down.
No light Indicates a drive is not present.
Fault Steady amber light Indicates drive fault.
No light Indicates the following:
■ No drive is present.
■ Drive power is on.
■ Drive activity.
Slowly blinking amber
light
Indicates the drive is bypassed by the
FCAL module or ready for removal.
9.13Using the Component LEDs
3PAR Confidential
9.14
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):
Figure 9-7. Controller Node LEDs
Consult Table 9-6 to verify proper functioning of controller nodes.
Table 9-6. Controller Node LED Displays
LED Appearance Meaning
Disk Hot-plug Steady amber light Indicates the node disk is prepared
for hot-plug.
No light Indicates the node disk is not
prepared for hot-plug.
0684_L_R1
Node Hot-plug LED
Node Status LED
Disk Hot-plug LED
Ethernet LED Activity
Ethernet 10/100/1000 Mbps LED
Using the Component LEDs
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
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.
Node status Flashing green light
(1 blink per second)
Indicates the node is fully functional
and part of the cluster.
Flashing amber light
(1 blink per second)
Indicates the node has a failed or
missing power supply, fan, battery
backup unit, or TOD battery but the
node is still operational.
Steady green light Indicates the node is in the process of
joining the cluster.
Rapidly flashing green
(3 blinks per second),
in conjunction with
the hot-plug LED
being solid amber
Indicates the node is safe to remove.
Steady amber light Indicates an error within the node.
Solid amber and
hot-plug LED amber
Indicates a fatal node failure.
Table 9-6. Controller Node LED Displays (continued)
LED Appearance Meaning
9.15Using the Component LEDs
3PAR Confidential
9.16
Messages and Operator’s Guide InForm OS Version 2.3.1
9.1.6 3PAR Fibre Channel Port LEDs
The 3PAR Fibre Channel adapter contained in the controller node also contains Fibre Channel
port LEDs
Figure 9-8. 3PAR 4-Port Fibre Channel LEDs
Consult to verify the proper function of the 3PAR Fibre Channel adapter LED.
Ethernet activity Steady green light Indicates an Ethernet link.
Flashing green light Indicates no Ethernet activity.
No light Indicates no Ethernet connection.
Ethernet
10/100/1000 MB/sec
Steady amber light 1000 Mb/sec mode.
Steady green light 100 Mb/sec mode.
No light 10 Mb/sec mode (or disconnected).
Table 9-6. Controller Node LED Displays (continued)
LED Appearance Meaning
Table 9-7. 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.
0720_L_R1
Port 4
Port 1
LED (4x)
Using the Component LEDs
3PAR Confidential
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.
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.
No Light Indicates no connection or active link.
0721_L_R1
Port 2
Port 1
LEDs (2x)
9.17Using the Component LEDs
3PAR Confidential
9.18
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).
Figure 9-10. Emulex 2-Port Fibre Channel LEDs
Consult Table 9-9 for Emulex Fibre Channel adapter LED meanings.
Table 9-9. Fibre Channel Port Status LED Indications (Emulex 2-Port Adapter)
Yellow LED Green LED Port Status
3PAR Internal Test Only Off Wake-Up Failure (dead device)
3PAR Internal Test Only On Normal - Link up at 1-4 GB/sec
3PAR Internal Test Only Slow Blink Normal - Link Down
Green 2xYellow 2x
0269_L_R2
(Port 1*)
(Port 2*)
*These ports correspond to the numbering as reported by the InForm OS.
Node Frame
Node Frame
Using the Component LEDs
3PAR Confidential
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:
Figure 9-11. Controller Node Power Supply LEDs
Consult Table 9-10 for node power supply LED meanings.
Table 9-10. Power Supply LED Displays
LED Appearance Meaning
Power Supply Status Steady green light Indicates power is on.
Steady amber light Indicates power supply error.
No light Indicates a broken connection to
the power source.
0353_L_R1
AC LED
Power SupplyStatus LED
Battery StatusLED
9.19Using the Component LEDs
3PAR Confidential
9.20
Messages and Operator’s Guide InForm OS Version 2.3.1
9.1.10 Power Distribution Unit Lamps
InServ Storage Servers include four Power Distribution Units (PDUs). PDUs contain two power
bank lamps (Figure 9-12):
Figure 9-12. Power Distribution Unit Lamps
A blue illuminated lamp denotes that power is being supplied to a power bank. When the blue
lamp is not illuminated, the power bank is not receiving AC input.
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
Table 9-10. Power Supply LED Displays (continued)
LED Appearance Meaning
0261_L_R1
Power Bank 2
Power Bank Lamps
Power Bank 1
Using the Component LEDs
3PAR Confidential
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).
Figure 9-13. Supermicro Service Processor LEDs
Consult Table 9-11 to verify proper functioning of service processor displays.
Table 9-11. 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.
Hard Disk No light Indicates there is no hard drive activity.
Flashing amber light Indicates there is hard drive activity.
NIC Port 2 No light Indicates the port is not connected.
Steady green light Indicates the port is connected.
Flashing green light Indicates there is network activity.
Hard Disk Drive LED
NIC Port 2 LEDNIC Port 1 LED
Power LED
Overheat LED
Power Button
0637_L_R1
Reset Button
9.21Service Processor LEDs
3PAR Confidential
9.22
Messages and Operator’s Guide InForm OS Version 2.3.1
9.2.2 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 9-14).
Figure 9-14. Supermicro II Service Processor LEDs
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.
Overheat No light Indicates the service processor temperature
is normal.
Steady red light Indicates the service processor temperature
is overheating.
Table 9-11. Supermicro Service Processor Front-Panel Displays (continued)
LED Appearance Meaning
NIC Port 2 LED
NIC Port 1 LED
Overheat LED
0802_L_R1
Reset Button
Power Button
Service Processor LEDs
3PAR Confidential
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.
Hard Disk Drive No light Indicates there is no hard drive activity.
Flashing amber light Indicates there is hard drive activity.
NIC Port 2 No light Indicates the port is not connected.
Flashing green light Indicates there is network activity.
Steady green light Indicates the port is connected.
NIC Port 1 No light Indicates the port is not connected.
Flashing green light Indicates there is network activity.
Steady green light Indicates the port is connected.
Overheat No light Indicates the service processor
temperature is normal.
Flashing red light Indicates the service processor has a
failed fan.
Steady red light Indicates the service processor
temperature is overheating.
9.23Service Processor LEDs
3PAR Confidential
9.24
Messages and Operator’s Guide InForm OS Version 2.3.1
9.3 Securing the Storage Server1 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.
Securing the Storage Server
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
10Power 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 ServerThe following procedure describes how to safely remove power from the InServ Storage Server
and Service Processor.
1 SSH to the Service Processor or physically connect a maintenance PC to the serial
connection.
2 Log in to the service processor by entering your login name and password.
3 If necessary, enter spmaint to get to the spmaint main menu.
4 Select option 4, InServ Product Maintenance.
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. locatesys will blink all node and drive cage LEDs. Note this
information now, as it is needed for step 12 on page 10.4.
10.1Power Off/On Procedures
3PAR Confidential
10.2
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.
9 Wait until the system has completed shutdown by observing that all controller nodes in the
system have the Hot-Plug LED solid amber and the Node Status LED blinking fast-green (a
rate of three blinks per second). See Figure 10-1 for the InServ T-Class Storage Server,
Figure 10-2 for the S-Class Storage Server, Figure 10-3 for the InServ F-Class Storage Server,
and Figure 10-4 for the InServ E-Class Storage Servers.
Figure 10-1. InServ T-Class Server Hot-Plug LED and Node Status LED
CAUTION: Failure to wait until all controller nodes are in a halted state as
defined in step 9 could cause the system to view the shutdown as uncontrolled
and place the system in a checkld state upon power up. This can seriously impact
host access to data.
0601_L_R3
NodeHot-plug LED
Node Status LED
Disk Hot-plug LED
Powering Off the Storage Server
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Figure 10-2. InServ S-Class Storage Server Hot-Plug LED and Node Status LED
Figure 10-3. InServ F-Class Storage Server Hot-Plug LED and Node Status LED
0294_L_R1
Hot-Plug LED
NodeStatus
LED
0683_L_R1
Node Hot-plug LED
Node Status LED
Disk Hot-plug LED
10.3Powering Off the Storage Server
3PAR Confidential
10.4
Messages and Operator’s Guide InForm OS Version 2.3.1
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).
Figure 10-5. PDU Circuit Breakers
10.2 Powering On the Storage Server
1 Turn on AC power to the cabinet(s) by turning on all the PDU circuit breakers (Figure 10-5)
of ALL four PDUs.
0361_L_R1
Status LEDHot-Plug LED
0295_L_R2
Circuit Breaker CB-1 Circuit Breaker CB-2
NOTE: The system takes approximately five minutes to become fully operational
providing it was gracefully shut down. If the system was powered off abruptly,
powering on could take considerably longer.
Powering On the Storage Server
3PAR Confidential
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.
3 Verify that all drive chassis LEDs (Figure 10-6 and Figure 10-7 for InServ T-Class or S-Class
Storage Servers and Figure 10-8 for the InServ F-Class or E-Class Storage Server) are solid
green and all controller node status LEDs (Figure 10-1 for the InServ T-Class Storage Server,
Figure 10-2 for the S-Class Storage Server, Figure 10-3 for the InServ F-Class Storage Server,
and Figure 10-4 for the InServ E-Class Storage Server) are blinking green once per second.
Figure 10-6. DC4 LEDs on the In T-Class Storage Server Drive Cage
DC4 0587_L_R1
Disk Status LEDs
Hot-Plug LED
Drive MagazineStatus LED
!0123
10.5Powering On the Storage Server
3PAR Confidential
10.6
Messages and Operator’s Guide InForm OS Version 2.3.1
Figure 10-7. DC2 LEDs on the InServ S-Class Storage Server Drive Cage
Figure 10-8. DC3 LEDs on the InServ E-Class and F-Class Storage Server Drive Cage
0518_L_R1
Disk Status LEDs
Hot-Plug LED
Drive MagazineStatus LED
DC2
!0123
DC2 (SATA Drive)
Activity (Green) LED
0149_L_R3
Fault (Amber) LED
Powering On the Storage Server
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
11Troubleshooting
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.1 OverviewThe InForm OS CLI checkhealth command checks and then displays the status of InServ
Storage Server hardware and software components. For example, the checkhealth
command can check for unresolved system alerts, display issues with hardware components, or
display information about virtual volumes that are not optimal. By default, the checkhealth
command checks most InServ system components but you can also check the status of specific
components. For a complete list of system components analyzed by the checkhealth
command, see Troubleshooting InServ Storage Server Components on page 11.4.
11.1Troubleshooting
3PAR Confidential
11.2
Messages and Operator’s Guide InForm OS Version 2.3.1
11.2 The checkhealth CommandCOMMAND
checkhealth
DESCRIPTION
The checkhealth command checks and then displays the status of system hardware and
software components.
SYNTAX
checkhealth [<options> | <component>...]
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.
SPECIFIERS
<component>
Indicates the component to check. Use -list option to get the list of components.
11.3 Using the checkhealth CommandUse the checkhealth command without any specifiers to check the health of all the
components analyzed by the checkhealth command. The following example displays both
summary and detailed information about the InServ Storage Server hardware and software
components:
The checkhealth Command
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
CLI% checkhealth -detailChecking alertChecking cageChecking dateChecking ldChecking licenseChecking networkChecking nodeChecking pdChecking portChecking rcChecking snmpChecking taskChecking vlunChecking vvComponent -----------Description----------- QtyAlert New alerts 4Date Date is not the same on all nodes 1LD LDs not mapped to a volume 2License Golden License. 1vlun Hosts not connected to a port 5
The following information is included when you use the -detail option:Component ----Identifier---- -----------Description-------Alert sw_port:1:3:1 Port 1:3:1 Degraded (Target Mode Port Went Offline) Alert sw_port:0:3:1 Port 0:3:1 Degraded (Target Mode Port Went Offline) Alert _sw_sysmgr ______Total available FC raw space has reached threshold of 800G (2G remaining out of 544G total)Alert sw_sysmgr _______Total FC raw space usage at 307G (above 50% of total 544G) Date -- _____________Date is not the same on all nodes LD ld:name.usr.0 __LD is not mapped to a volume LD ld:name.usr.1 __LD is not mapped to a volume vlun ___host:group01 Host wwn:2000000087041F72 is not connected to a port vlun ___host:group02 Host wwn:2000000087041F71 is not connected to a port vlun ___host:group03 _ Host iscsi_name:2000000087041F71 is not connected to a port vlun ___host:group04 ___Host wwn:210100E08B24C750 is not connected to a port vlun ___host:Host_name Host wwn:210000E08B000000 is not connected to a port
If there are no faults or exception conditions, the checkhealth command indicates that the
system is healthy.
cli% checkhealthChecking alertChecking cage…Checking vlunChecking vvSystem is healthy
With the checkhealth <component> specifier you can check the status of one or more
specific InServ Storage Server components. For example:
CLI% checkhealth node pd
11.3Using the checkhealth Command
3PAR Confidential
11.4
Messages and Operator’s Guide InForm OS Version 2.3.1
Checking nodeChecking pdThe following components are healthy: node, pd
11.4 Troubleshooting InServ Storage Server ComponentsUse 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. Component Functions
Component Function
Alert Displays any unresolved alerts.
Cage Displays drive cage conditions that are not optimal.
Date Displays if nodes have different dates.
LD Displays LDs that are not optimal.
License Displays license violations.
Network Displays Ethernet issues.
Node Displays node conditions that are not optimal.
PD Displays PDs with states or conditions that are not
optimal.
Port Displays port connection issues.
RC Displays Remote Copy issues.
SNMP Displays issues with SNMP.
Troubleshooting InServ Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
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.1 Format of Possible Alert Exception MessagesAlert <component> <alert_text >
11.4.1.2 Alert Example Component -Identifier- --------Description--------------------Alert hw_cage:1 Cage 1 Degraded (Loop Offline)Alert sw_cli 11 authentication failures in 120 secs
11.4.1.3 Alert Suggested Action
View the full Alert output using the IMC (GUI) or the showalert -d CLI command. Consult
the 3PAR Messages and Operator's Guide for more information about the alert.
11.4.2 Cage
Displays drive cage conditions that are not optimal.
Reports exceptions if any of the following do not have normal states:
■ ports
■ drive magazine states (DC1, DC2, & DC4)
■ Small Form-factor Pluggable (SFP) voltages (DC2 and DC4)
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.
Table 11-1. Component Functions
Component Function
11.5Troubleshooting InServ Storage Server Components
3PAR Confidential
11.6
Messages and Operator’s Guide InForm OS Version 2.3.1
■ SFP signal levels (RX power low and TX failure)
■ power supplies
■ cage firmware (is not current)
Reports if a servicecage operation has been started and has not ended.
11.4.2.1 Format of Possible Cage Exception MessagesCage cage:<cageid> "Missing A loop" (or "Missing B loop")Cage cage:<cageid> "Interface Card <STATE>"Cage cage:<cageid>,mag:<magpos> "Magazine is <MAGSTATE>"Cage cage:<cageid> "Power supply <X> fan is <FANSTATE>"Cage cage:<cageid> "Power supply <X> is <PSSTATE>" (Degraded, Failed, Not_Present)Cage cage:<cageid> "Power supply <X> AC state is <PSSTATE>"Cage cage:<cageid> "Cage has a hotplug enabled interface card" Cage cage:<cageid> "Firmware is not current"
11.4.2.2 Cage Example 1Component -------------Description-------------- QtyCage Cages missing A loop 1Cage SFPs with low receiver power 1
Component -Identifier- --------Description------------------------Cage cage:4 Missing A loop Cage cage:4 Interface Card 0, SFP 0: Receiver Power Low: Check FC Cable
11.4.2.3 Cage Suggested Action 1
Check the connection/path to the SFP in the cage and the level of signal the SFP is receiving. An
RX Power reading below 100 uW will signal the RX Power Low condition; typical readings are
between 300 and 400 uW. Helpful CLI commands are showcage -d and showcage -sfp ddm.
At least two connections are expected for drive cages and this exception will be flagged if that
is not the case.
cli% showcage -d cage4Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 4 cage4 --- 0 3:2:1 0 8 28-36 2.37 2.37 DC4 n/a
-----------Cage detail info for cage4 ---------
Fibre Channel Info PortA0 PortB0 PortA1 PortB1 Link_Speed 0Gbps -- -- 4Gbps
Troubleshooting InServ Storage Server Components
3PAR Confidential
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.1 No No No Yes
Interface Board Info FCAL0 FCAL1 Link A RXLEDs Off Off Link A TXLEDs Green Off Link B RXLEDs Off Green Link B TXLEDs Off Green LED(Loop_Split) Off OffLEDS(system,hotplug) Green,Off Green,Off
-----------Midplane Info----------- Firmware_status Current Product_Rev 2.37 State Normal Op Loop_Split 0VendorId,ProductId 3PARdata,DC4 Unique_ID 1062030000098E00
...
-------------Drive Info------------- ----LoopA----- ----LoopB-----Drive NodeWWN LED Temp(C) ALPA LoopState ALPA LoopState 0:0 2000001d38c0c613 Green 33 0xe1 Loop fail 0xe1 OK 0:1 2000001862953510 Green 35 0xe0 Loop fail 0xe0 OK 0:2 2000001862953303 Green 35 0xdc Loop fail 0xdc OK 0:3 2000001862953888 Green 31 0xda Loop fail 0xda OK
cli% showcage -sfp cage4Cage FCAL SFP -State- --Manufacturer-- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM 4 0 0 OK FINISAR CORP. 4.1 No No Yes Yes 4 1 1 OK FINISAR CORP. 4.1 No No No Yes
cli% showcage -sfp -ddm cage4---------Cage 4 Fcal 0 SFP 0 DDM---------- -Warning- --Alarm----Type-- Units Reading Low High Low HighTemp C 33 -20 90 -25 95 Voltage mV 3147 2900 3700 2700 3900TX Bias mA 7 2 14 1 17 TX Power uW 394 79 631 67 631
11.7Troubleshooting InServ Storage Server Components
3PAR Confidential
11.8
Messages and Operator’s Guide InForm OS Version 2.3.1
RX Power uW 0 15 794 10* 1259 ---------Cage 4 Fcal 1 SFP 1 DDM---------- -Warning- --Alarm----Type-- Units Reading Low High Low HighTemp C 31 -20 90 -25 95 Voltage mV 3140 2900 3700 2700 3900TX 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.4 Cage Example 2Component -------------Description-------------- QtyCage Degraded or failed cage power supplies 2Cage Degraded or failed cage AC power 1
Component -Identifier- ------------Description------------Cage cage:1 Power supply 0 is Failed Cage cage:1 Power supply 0's AC state is FailedCage cage:1 Power supply 2 is Off
11.4.2.5 Cage Suggested Action 2
A cage power supply or power supply fan is failed, is missing input AC power, or the switch is
turned OFF. The showcage -d cageX and showalert commands should provide more
detail.
cli% showcage -d cage1Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 1 cage1 0:0:2 0 1:0:2 0 24 27-39 2.37 2.37 DC2 n/a
-----------Cage detail info for cage1 ---------
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 OffLEDS(system,hotplug) Amber,Off Amber,Off
-----------Midplane Info----------- Firmware_status Current Product_Rev 2.37 State Normal Op Loop_Split 0
Troubleshooting InServ Storage Server Components
3PAR Confidential
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 <AC input is missing ps1 OK OK OK POI ps2 Off OK OK POI <PS switch is turned off ps3 OK OK OK POI
11.4.2.6 Cage Example 3Component -Identifier- --------------Description----------------Cage cage:1 Cage has a hotplug enabled interface card
11.4.2.7 Cage Suggested Action 3
When a servicecage operation is started, it puts the targeted cage into servicing mode and
illuminates the Hot Plug LED on the FCAL-Module (DC1, DC2, DC4), and causes I/O to be routed
through the other path. When the service action is finished, the servicecage endfc
command should be issued to return the cage to normal status. This checkhealth exception
will be reported if the FCAL-Module's Hot Plug LED is illuminated or if the cage is in servicing
mode. If a maintenance activity is currently occurring on the drive cage, this condition may be
ignored.
cli% showcage -d cage1Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 1 cage1 0:0:2 0 1:0:2 0 24 28-40 2.37 2.37 DC2 n/a
-----------Cage detail info for cage1 ---------
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 OffLEDS(system,hotplug) Green,Off Green,Amber
-----------Midplane Info----------- Firmware_status Current
NOTE: The primary path can be seen by an asterisk (*) in showpd's Ports
columns.
11.9Troubleshooting InServ Storage Server Components
3PAR Confidential
11.10
Messages and Operator’s Guide InForm OS Version 2.3.1
Product_Rev 2.37 State Normal Op Loop_Split 0VendorId,ProductId 3PARdata,DC2 Unique_ID 10320300000AD000
cli% showpd -s Id CagePos Type -State-- -----Detailed_State------ 20 1:0:0 FC degraded disabled_B_port,servicing 21 1:0:1 FC degraded disabled_B_port,servicing 22 1:0:2 FC degraded disabled_B_port,servicing 23 1:0:3 FC degraded disabled_B_port,servicing
cli% showpd -p -cg 1 ---Size(MB)---- ----Ports----Id CagePos Type Speed(K) State Total Free A B 20 1:0:0 FC 10 degraded 139520 119808 0:0:2* 1:0:2-21 1:0:1 FC 10 degraded 139520 122112 0:0:2* 1:0:2-22 1:0:2 FC 10 degraded 139520 119552 0:0:2* 1:0:2-23 1:0:3 FC 10 degraded 139520 122368 0:0:2* 1:0:2-
11.4.2.8 Cage Example 4SComponent ---------Description--------- QtyCage Cages not on current firmware 1
Component -Identifier- ------Description------Cage cage:3 Firmware is not current
11.4.2.9 Cage Suggested Action 4
Check the drive cage firmware revision using the command showcage and showcage -d cageX. The showfirwaredb command indicates what the current firmware level should be
for the specific drive cage type.
cli% showcageId Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 2 cage2 2:0:3 0 3:0:3 0 24 29-43 2.37 2.37 DC2 n/a 3 cage3 2:0:4 0 3:0:4 0 32 29-41 2.36 2.36 DC2 n/a
NOTE: DC1 and DC3 cages have firmware in the FCAL-Modules; DC2 and DC4
cages have firmware on the cage midplane. The upgradecage command may be
used to upgrade the firmware.
Troubleshooting InServ Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
cli% showcage -d cage3Id 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 0VendorId,ProductId 3PARdata,DC2 Unique_ID 10320300000AD100
cli% showfirmwaredb Vendor Prod_rev Dev_Id Fw_status Cage_type Firmware_File...3PARDATA [2.37] DC2 Current DC2 /opt...dc2/lbod_fw.bin-2.37
11.4.2.10 Cage Example 5Component -Identifier- ------------Description------------Cage cage:4 Interface Card 0, SFP 0 is unqualified
11.4.2.11 Cage Suggested Action 5
In this example, a 2Gb/sec SFP was installed in a 4Gb/sec drive cage (DC4), and the 2Gb SFP is
not qualified for use in this drive cage. For cage problems, the following CLI commands are
helpful: showcage -d, showcage -sfp, showcage -sfp -ddm, showcage -sfp -d, and
showpd -state.
cli% showcage -d cage4Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 4 cage4 2:2:1 0 3:2:1 0 8 30-37 2.37 2.37 DC4 n/a
-----------Cage detail info for cage4 ---------
Fibre Channel Info PortA0 PortB0 PortA1 PortB1 Link_Speed 2Gbps -- -- 4Gbps
----------------------------------SFP Info-----------------------------------FCAL SFP -State- --Manufacturer-- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM 0 0 OK SIGMA-LINKS 2.1 No No No Yes 1 1 OK FINISAR CORP. 4.1 No No No Yes
11.11Troubleshooting InServ Storage Server Components
3PAR Confidential
11.12
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 OffLEDS(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.1 Qualified : No <<< Unqualified SFPTX Disable : No TX Fault : No RX Loss : No RX Power Low : No DDM Support : Yes
--------Cage 4 FCAL 1 SFP 1--------Cage ID : 4 Fcal ID : 1 SFP ID : 1 State : OK Manufacturer : FINISAR CORP. Part Number : FTLF8524P2BNV Serial Number : PF52GRF Revision : A MaxSpeed(Gbps) : 4.1 Qualified : Yes TX Disable : No TX Fault : No RX Loss : No RX Power Low : No DDM Support : Yes
Troubleshooting InServ Storage Server Components
3PAR Confidential
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.
This condition is not currently detected by checkhealth.
cli% showcage -d cage1Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 1 cage1 0:0:2 0 1:0:2 0 15 31-38 08 08 DC3 n/a
-----------Cage detail info for cage1 ---------
Position: --------------Midplane Info------------ VendorId,ProductId 3PARdata,DC3 Serial_Num OPS69907C013287 Node_WWN 20000050CC013287 TempSensor_State OK TempSensor_Value 36 OpsPanel_State OKAudible_Alarm_State Muted ID_Switch 1 Cage_State Degraded
Interface Board Info LoopA LoopB Firmware_status Current Current Product_Rev 08 08 IFC_State OK OK ESH_State OK OK Master_CPU Yes No Loop_Map valid valid Link_Speed 2Gbps 2Gbps Port0_State OK OK Port1_State No_SFP Bypass,Rx_Loss Port2_State No_SFP No_SFP Port3_State No_SFP No_SFP
11.4.3 Date
Checks the date and time on all nodes and reports an error if they are not the same.
11.13Troubleshooting InServ Storage Server Components
3PAR Confidential
11.14
Messages and Operator’s Guide InForm OS Version 2.3.1
11.4.3.1 Format of Possible Date Exception MessagesDate -- "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.
cli% showdateNode Date0 2009-09-08 10:56:41 PDT (America/Los_Angeles)1 2009-09-08 10:56:39 PDT (America/Los_Angeles)
cli% shownetIP Address Netmask/PrefixLen Nodes Active Speed 192.168.56.209 255.255.255.0 0123 0 100 Duplex AutoNeg Status Full Yes Active
Default route: 192.168.56.1NTP server: 192.168.56.109
11.4.4 LD
Displays Logical Disks (LDs) that are not optimal.
■ Checks for preserved LDs
■ Checks that current and created availability are the same
■ Checks for owner and backup
■ Checks that preserved data space (pdsld's) is same as total data cache
■ Checks size and number of logging LDs
■ Checks that Logging LDs are the correct quantity and size
11.4.4.1 Format of Possible LD Exception MessagesLD ld:<ldname> "LD is not mapped to a volume" LD ld:<ldname> "LD is in write-through mode" LD ld:<ldname> "LD has <X> preserved RAID sets and <Y> preserved chunklets"
Troubleshooting InServ Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
LD ld:<ldname> "LD has reduced availability. Current: <cavail>, Configured: <avail>" LD ld:<ldname> "LD does not have a backup" LD ld:<ldname> "LD does not have owner and backup" LD ld:<ldname> "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.2 LD Example 1Component -------Description-------- QtyLD LDs not mapped to a volume 10
Component -Identifier-- --------Description---------LD ld:Ten.usr.0 LD is not mapped to a volume
11.4.4.3 LD Suggested Action 1
Examine the identified LD(s) using CLI commands such as showld, showld –d, showldmap,
showvvmap, etc.
LDs are normally mapped to (used by) VVs but they can be disassociated with a VV if a VV is
deleted without the underlying LDs being deleted, or by an aborted tune operation. Normally,
you would remove the unmapped LD to return its chunklets to the free pool. cli% showld Ten.usr.0Id Name RAID -Detailed_State- Own SizeMB UsedMB Use Lgct LgId WThru MapV88 Ten.usr.0 0 normal 0/1/2/3 8704 0 V 0 --- N N
cli% showldmap Ten.usr.0Ld space not used by any vv
11.4.4.4 LD Example 2Component -------Description-------- QtyLD LDs in write through mode 3
Component -Identifier-- --------Description---------LD ld:Ten.usr.12 LD is in write-through mode
11.4.4.5 LD Suggested Action 2
Examine the identified LD(s) using CLI commands such as showld, showld –d, showldch,
and showpd for any failed/missing disks.
Write-through mode (WThru) indicates that host I/O operations must be written through to
the disk before the host I/O command will be acknowledged. This is usually due to a node-
11.15Troubleshooting InServ Storage Server Components
3PAR Confidential
11.16
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 MapV91 Ten.usr.3 0 normal 1/0/3/2 13824 0 V 0 --- N N92 Ten.usr.12 0 normal 2/3/0/1 28672 0 V 0 --- Y N
cli% showldch Ten.usr.12Ldch Row Set PdPos Pdid Pdch State Usage Media Sp From To 0 0 0 3:3:0 108 6 normal ld valid N --- --- 11 0 11 --- 104 74 normal ld valid N --- ---
cli% showpd 104 -Size(MB)-- ----Ports---- Id CagePos Type Speed(K) State Total Free A B 104 4:9:0? FC 15 failed 428800 0 ----- -----
11.4.4.6 LD Example 3Component ---------Description--------- QtyLD LDs with reduced availability 1
Component --Identifier-- ------------Description---------------LD ld:R1.usr.0 LD has reduced availability. Current: ch, Configured: cage
11.4.4.7 LD Suggested Action 3
LDs are created with certain high-availability characteristics, such as ha-cage. If chunklets in
an LD get moved to locations where the Current Availability (CAvail) is not at least as good as
the desired level of Availability (Avail), this condition will be reported. Chunklets may have
been manually moved with movech or by specifying it during a tune operation or during
failure conditions such as node, path, or cage failures. The HA levels from highest to lowest are
port, cage, mag, and ch (disk).
Examine the identified LD(s) using CLI commands such as showld, showld –d, showldch,
and showpd for any failed or missing disks. In the example below, the LD should have cage-
level availability but it currently has chunklet (disk) level availability (i.e., the chunklets are on
the same disk).cli% showld -d R1.usr.0Id Name CPG RAID Own SizeMB RSizeMB RowSz StepKB SetSz Refcnt Avail CAvail32 R1.usr.0 --- 1 0/1/3/2 256 512 1 256 2 0 cage ch
cli% showldch R1.usr.0Ldch Row Set PdPos Pdid Pdch State Usage Media Sp From To 0 0 0 0:1:0 4 0 normal ld valid N --- --- 1 0 0 0:1:0 4 55 normal ld valid N --- ---
11.4.4.8 LD Example 4Component -Identifier-- -----Description-------------
Troubleshooting InServ Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
LD -- 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). This message will appear if a node is
offline because the comparison of LD size to data cache size does not match; this message can
be ignored unless all nodes are online. If all nodes are online and the error condition persists,
determine the cause of the failure. Use the admithw command to correct the condition.
cli% shownode Control Data CacheNode --Name--- -State- Master InCluster ---LED--- Mem(MB) Mem(MB) Available(%) 0 1001335-0 OK Yes Yes GreenBlnk 2048 4096 100 1 1001335-1 OK No Yes GreenBlnk 2048 4096 100
cli% showld pdsld*Id Name RAID -Detailed_State- Own SizeMB UsedMB Use Lgct LgId WThru MapV19 pdsld0.0 1 normal 0/1 256 0 P,F 0 --- Y N20 pdsld0.1 1 normal 0/1 7680 0 P 0 --- Y N21 pdsld0.2 1 normal 0/1 256 0 P 0 --- Y N---------------------------------------------------------------------------- 3 8192 0
11.4.5 License
Displays license violations.
Returns information if a license is temporary, and if it has expired.
11.4.5.1 Format of Possible License Exception MessagesLicense <feature_name> "License is enabled on a trial basis" License <feature_name> "License has expired"
11.4.5.2 License Example Component -Identifier- --------Description-------------License -- System Tuner License has expired
11.4.5.3 License Suggested Action
If desired, request a new/updated license from their 3PAR Sales Engineer.
11.17Troubleshooting InServ Storage Server Components
3PAR Confidential
11.18
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 MessagesNetwork -- "IP address change has not been completed" Network "Node<node>:<type>" "Errors detected on network"
11.4.6.2 Network Example 1Network -- "IP address change has not been completed"
11.4.6.3 Network Suggested Action 1
The setnet command was issued to change some network parameter, such as the IP address,
but the action has not been completed. Use setnet finish to complete the change, or
setnet abort to cancel. Use shownet to examine the current condition.
cli% shownetIP Address Netmask/PrefixLen Nodes Active Speed Duplex AutoNeg Status 192.168.56.209 255.255.255.0 0123 0 100 Full Yes Changing 192.168.56.233 255.255.255.0 0123 0 100 Full Yes Unverified
11.4.6.4 Network Example 2Component ---Identifier---- -----Description----------Network Node0:Admin Errors detected on network
11.4.6.5 Network Suggested Action 2
Network errors have been detected on the specified node and network interface. Commands
such as shownet and shownet -d are useful for troubleshooting network problems.
shownet -d IP Address: 192.168.56.209 Netmask 255.255.255.0 Assigned to nodes: 0123Connected through node 0Status: Active
Admin interface on node 0
NOTE: These error counters cannot be cleared except by rebooting a controller
node.
Troubleshooting InServ Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MAC Address: 00:02:AC:25:04:03RX Packets: 1225109 TX Packets: 550205RX Bytes: 1089073679 TX Bytes: 568149943RX Errors: 0 TX Errors: 0RX Dropped: 0 TX Dropped: 0RX FIFO Errors: 0 TX FIFO Errors: 0RX Frame Errors: 60 TX Collisions: 0RX Multicast: 0 TX Carrier Errors: 0RX Compressed: 0 TX Compressed: 0
11.4.7 Node
Displays node conditions that are not optimal.
■ Checks if node batteries have been tested in the last 30 days.
■ Checks for offline nodes.
■ Checks for power supply and battery problems.
11.4.7.1 Format of Possible Node Exception MessagesNode node:<nodeID> "Node is not online" Node node:<nodeID> "Power supply <psID> detailed state is <status>Node node:<nodeID> "Power supply <psID> AC state is <acStatus>" Node node:<nodeID> "Power supply <psID> DC state is <dcStatus> Node node:<nodeID> "Power supply <psID> battery is <batStatus>" Node node:<priNodeID> "<bat> has not been tested within the last 30 days"
11.4.7.2 Suggested Node Action, General
For node error conditions, examine the node and node-component states with commands such
as shownode, shownode -s, shownode -d, showbattery, and showsys -d.
11.4.7.3 Node Example 1Component -Identifier- ---------------Description----------------Node node:0 Power supply 1 detailed state is DC FailedNode node:0 Power supply 1 DC state is Failed Node node:1 Power supply 0 detailed state is AC FailedNode node:1 Power supply 0 AC state is Failed Node node:1 Power supply 0 DC state is Failed
NOTE: For an E- or F-Class system, the failure of a system fan is not detected
except in the Alert section. These fans cool the nodes in E- and F-Class systems.
11.19Troubleshooting InServ Storage Server Components
3PAR Confidential
11.20
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.
cli% shownode Control Data CacheNode --Name--- -State-- Master InCluster ---LED--- Mem(MB) Mem(MB) Available(%) 0 1001356-0 Degraded Yes Yes AmberBlnk 2048 8192 100 1 1001356-1 Degraded No Yes AmberBlnk 2048 8192 100
cli% shownode -sNode -State-- -Detailed_State- 0 Degraded PS 1 Failed 1 Degraded PS 0 Failed
cli% shownode -psNode PS -Serial- -PSState- FanState ACState DCState -BatState- ChrgLvl(%) 0 0 FFFFFFFF OK OK OK OK OK 100 0 1 FFFFFFFF Failed -- OK Failed Degraded 100 1 0 FFFFFFFF Failed -- Failed Failed Degraded 100 1 1 FFFFFFFF OK OK OK OK OK 100
11.4.7.5 Node Example 2Component -Identifier- ---------Description------------Node node:3 Power supply 1 battery is Failed
11.4.7.6 Node Suggested Action 2
Examine the state of the battery and power supplies with commands such as shownode,
shownode -s, shownode -ps, showbattery (and showbattery with -d, -s, -log), etc.
Turn on, fix, or replace the battery backup unit.
cli% shownode Control Data Cache
NOTE: In the example below, the battery state is considered Degraded because
the power supply is Failed; this is normal.
NOTE: The condition of the Degraded Power Supply (PS) is due to the battery
failing.
Troubleshooting InServ Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Node --Name--- -State-- Master InCluster ---LED--- Mem(MB) Mem(MB) Available(%) 2 1001356-2 OK No Yes GreenBlnk 2048 8192 100 3 1001356-3 Degraded No Yes AmberBlnk 2048 8192 100
cli% shownode -sNode -State-- -Detailed_State- 2 OK OK 3 Degraded PS 1 Degraded
cli% shownode -psNode PS -Serial- -PSState- FanState ACState DCState -BatState- ChrgLvl(%) 2 0 FFFFFFFF OK OK OK OK OK 100 2 1 FFFFFFFF OK OK OK OK OK 100 3 0 FFFFFFFF OK OK OK OK OK 100 3 1 FFFFFFFF Degraded OK OK OK Failed 0
cli% showbatteryNode PS Bat Serial -State-- ChrgLvl(%) -ExpDate-- Expired Testing 3 0 0 100A300B OK 100 07/01/2011 No No 3 1 0 12345310 Failed 0 04/07/2011 No No
11.4.7.7 Node Example 3Component -Identifier- --------------Description----------------Node node:3 Node:3, Power Supply:1, Battery:0 has not been tested within the last 30 days
11.4.7.8 Node Suggested Action 3
The indicated battery has not been tested in the past 30 days. A node backup battery will be
tested every 14 days under normal conditions, but if a battery is missing, expired, or failed, it
will not be tested. In addition, the other battery connected to the same node will not be tested
because testing it would cause loss of battery backup to the node, and the system will not
allow that. An untested battery will have an Unknown status in the showbattery -s output.
Use commands such as showbattery, showbattery -s, showbattery -d, and
showbattery -log.
showbattery -sNode PS Bat -State-- -Detailed_State- 0 0 0 OK normal 0 1 0 Degraded Unknown
11.21Troubleshooting InServ Storage Server Components
3PAR Confidential
11.22
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.
showbattery -logNode PS Bat Test Result Dur(mins) ---------Time---------- 0 0 0 0 Passed 1 2009-10-14 14:34:50 PDT 0 0 0 1 Passed 1 2009-10-28 14:36:57 PDT 0 1 0 0 Passed 1 2009-08-27 06:17:44 PDT 0 1 0 1 Passed 1 2009-09-10 06:19:34 PDT
showbattery Node PS Bat Serial -State-- ChrgLvl(%) -ExpDate-- Expired Testing 0 0 0 83205243 OK 100 04/07/2011 No No 0 1 0 83202356 Degraded 100 04/07/2011 No No
11.4.8 PD
Displays Physical Disks (PDs) with states or conditions that are not optimal.
■ Checks for failed and degraded PDs
■ Checks for an imbalance of PD ports, for example, if Port-A is used on more disks than Port-
B.
■ Checks for an "Unknown" Sparing Algorithm. For example, when it hasn't been set
■ Checks for disks experiencing a high number of IOPS
■ Reports if a servicemag operation is outstanding (servicemag status)
11.4.8.1 Format of Possible PD Exception MessagesPD disk:<pdid> "Detailed State: <showpd -s -degraded -failed">PD -- "There is an imbalance of active PD ports" PD -- "Sparing algorithm is not set"PD disk:<pdid> "Disk is experiencing a high level of I/O per second: <iops>" PD -- There is at least one active servicemag operation in progress
11.4.8.2 PD Example 1Component -------------------Description------------------- QtyPD PDs that are degraded or failed 40
Component -Identifier- ---------------Description-----------------PD disk:48 Detailed State: missing_B_port,loop_failure PD disk:49 Detailed State: missing_B_port,loop_failure ...
Troubleshooting InServ Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
PD 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.
cli% showpd -degraded -failed ----Size(MB)---- ----Ports---- Id CagePos Type Speed(K) State Total Free A B 48 3:0:0 FC 10 degraded 139520 115200 2:0:4* ----- 49 3:0:1 FC 10 degraded 139520 121344 2:0:4* -----…107 4:9:3 FC 15 failed 428800 0 ----- 3:2:1*
cli% showpd -s -degraded -failed Id CagePos Type -State-- -----------------Detailed_State-------------- 48 3:0:0 FC degraded missing_B_port,loop_failure 49 3:0:1 FC degraded missing_B_port,loop_failure …107 4:9:3 FC failed prolonged_not_ready,missing_A_port,relocating
cli% showcage -d cage3Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 3 cage3 2:0:4 0 --- 0 32 28-39 2.37 2.37 DC2 n/a
-----------Cage detail info for cage3 ---------
Fibre Channel Info PortA0 PortB0 PortA1 PortB1 Link_Speed 2Gbps -- -- 0Gbps
----------------------------------SFP Info-----------------------------------FCAL SFP -State- --Manufacturer-- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM 0 0 OK SIGMA-LINKS 2.1 No No No Yes 1 1 OK SIGMA-LINKS 2.1 No No Yes Yes
Interface Board Info FCAL0 FCAL1 Link A RXLEDs Green Off Link A TXLEDs Green Off Link B RXLEDs Off Off Link B TXLEDs Off Green LED(Loop_Split) Off OffLEDS(system,hotplug) Green,Off Green,Off
11.23Troubleshooting InServ Storage Server Components
3PAR Confidential
11.24
Messages and Operator’s Guide InForm OS Version 2.3.1
-------------Drive Info------------- ----LoopA----- ----LoopB-----Drive NodeWWN LED Temp(C) ALPA LoopState ALPA LoopState 0:0 20000014c3b3eab9 Green 34 0xe1 OK 0xe1 Loop fail 0:1 20000014c3b3e708 Green 36 0xe0 OK 0xe0 Loop fail
11.4.8.4 PD Example 2Component --Identifier-- --------------Description--------------- PD -- There is an imbalance of active pd ports
11.4.8.5 PD Suggested Action 2
The primary and secondary I/O paths for disks (PD's) are balanced between nodes. The primary
path is indicated in the showpd -path output and by an asterisk in the showpd output. An
imbalance of active ports is usually caused by a nonfunctioning path/loop to a cage, or because
an odd number of drives is installed or detected. To diagnose further, use CLI commands such
as showpd, showpd path, showcage, and showcage -d.
cli% showpd ----Size(MB)----- ----Ports---- Id CagePos Type Speed(K) State Total Free A B 0 0:0:0 FC 10 normal 139520 119040 0:0:1* 1:0:1 1 0:0:1 FC 10 normal 139520 121600 0:0:1 1:0:1* 2 0:0:2 FC 10 normal 139520 119040 0:0:1* 1:0:1 3 0:0:3 FC 10 normal 139520 119552 0:0:1 1:0:1*... 46 2:9:2 FC 10 normal 139520 112384 2:0:3* 3:0:3 47 2:9:3 FC 10 normal 139520 118528 2:0:3 3:0:3* 48 3:0:0 FC 10 degraded 139520 115200 2:0:4* ----- 49 3:0:1 FC 10 degraded 139520 121344 2:0:4* ----- 50 3:0:2 FC 10 degraded 139520 115200 2:0:4* ----- 51 3:0:3 FC 10 degraded 139520 121344 2:0:4* -----
cli% showpd -path -----------Paths----------- Id CagePos Type -State-- A B Order 0 0:0:0 FC normal 0:0:1 1:0:1 0/1 1 0:0:1 FC normal 0:0:1 1:0:1 1/0 2 0:0:2 FC normal 0:0:1 1:0:1 0/1 3 0:0:3 FC normal 0:0:1 1:0:1 1/0 ... 46 2:9:2 FC normal 2:0:3 3:0:3 2/3 47 2:9:3 FC normal 2:0:3 3:0:3 3/2 48 3:0:0 FC degraded 2:0:4 3:0:4\missing 2/- 49 3:0:1 FC degraded 2:0:4 3:0:4\missing 2/-
Troubleshooting InServ Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
50 3:0:2 FC degraded 2:0:4 3:0:4\missing 2/- 51 3:0:3 FC degraded 2:0:4 3:0:4\missing 2/-
cli% showcage -d cage3Id 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.37 DC2 n/a
-----------Cage detail info for cage3 ---------
Fibre Channel Info PortA0 PortB0 PortA1 PortB1 Link_Speed 2Gbps -- -- 0Gbps
----------------------------------SFP Info-----------------------------------FCAL SFP -State- --Manufacturer-- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM 0 0 OK SIGMA-LINKS 2.1 No No No Yes 1 1 OK SIGMA-LINKS 2.1 No No Yes Yes
Interface Board Info FCAL0 FCAL1 Link A RXLEDs Green Off Link A TXLEDs Green Off Link B RXLEDs Off Off Link B TXLEDs Off Green LED(Loop_Split) Off OffLEDS(system,hotplug) Green,Off Green,Off...-------------Drive Info------------- ----LoopA----- ----LoopB-----Drive NodeWWN LED Temp(C) ALPA LoopState ALPA LoopState 0:0 20000014c3b3eab9 Green 35 0xe1 OK 0xe1 Loop fail 0:1 20000014c3b3e708 Green 38 0xe0 OK 0xe0 Loop fail 0:2 20000014c3b3ed17 Green 35 0xdc OK 0xdc Loop fail 0:3 20000014c3b3dabd Green 30 0xda OK 0xda Loop fail
11.4.8.6 PD Example 3Component -------------------Description------------------- QtyPD Disks experiencing a high level of I/O per second 93
Component --Identifier-- ---------Description---------- PD disk:100 Disk is experiencing a high level of I/O per second: 789.0
11.4.8.7 PD Suggested Action 3
This check samples the I/O per second (IOPS) information in statpd to see if any disks are
being overworked, and then it samples again after 5 seconds. This does not necessarily indicate
11.25Troubleshooting InServ Storage Server Components
3PAR Confidential
11.26
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. If the IOPS rate is very
high and/or a large number of disks are experiencing very heavy I/O, examine the system
further using statistical monitoring commands/utilities such as statpd, the InForm OS IMC
(GUI) and System Reporter. The following example will report disks whose total I/O is 150/sec or
more.
cli% statpd -filt curs,t,iops,15014:51:49 11/03/09 r/w I/O per second KBytes per sec ... Idle % ID Port Cur Avg Max Cur Avg Max ... Cur Avg 100 3:2:1 t 658 664 666 172563 174007 174618 ... 6 6
11.4.8.8 PD Example 4Component --Identifier-- -------Description----------PD disk:3 Detailed State: old_firmware
11.4.8.9 PD Suggested Action 4
The identified disk does not have firmware that the InServ Storage Server considers current.
When a disk is replaced, the servicemag operation should upgrade the disk's firmware.
When disks are installed or added to a system, the admithw command can perform the
firmware upgrade. Check the state of the disk using CLI commands such as showpd -s,
showpd -i, and showfirmwaredb.
cli% showpd -s 3Id CagePos Type -State-- -Detailed_State- 3 0:4:0 FC degraded old_firmware
cli% showpd -i 3Id CagePos State ----Node_WWN---- --MFR-- ---Model--- -Serial- -FW_Rev- 3 0:4:0 degraded 200000186242DB35 SEAGATE ST3146356FC 3QN0290H XRHJ
cli% showfirmwaredb Vendor Prod_rev Dev_Id Fw_status Cage_type ...SEAGATE [XRHK] ST3146356FC Current DC2.DC3.DC4
Troubleshooting InServ Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
11.4.8.10 PD Example 5Component --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. After setting the parameter, use the admithw command to programmatically create
and distribute the spare chunklets.
% showsys -paramSystem parameters from configured settings
----Parameter----- --Value--RawSpaceAlertFC : 0RawSpaceAlertNL : 0RemoteSyslog : 0RemoteSyslogHost : 0.0.0.0SparingAlgorithm : Unknown
11.4.9 Port
Displays port connection issues.
■ Checks for ports in unacceptable states
■ Checks for mismatches in type and mode, such as hosts connected to initiator ports, or host
and Remote Copy over Fibre Channel (RCFC) ports configured on the same FC adapter
■ Checks for Cyclic Redundancy Check (CRC) errors on a port
■ Checks for degraded SFPs and those with low power; perform this check only if this FC
Adapter type uses SFPs
11.4.9.1 Format of Possible Port Exception MessagesPort port:<nsp> "Port mode is in <mode> state" Port port:<nsp> "is offline" Port port:<nsp> "Mismatched mode and type" Port port:<nsp> "Port is <state>" Port port:<nsp> "SFP is missing" Port port:<nsp> "SFP is disabled" Port port:<nsp> "Receiver Power Low: Check FC Cable" Port port:<nsp> "Transmit Power Low" Port port:<nsp> "SFP has TX fault"
11.27Troubleshooting InServ Storage Server Components
3PAR Confidential
11.28
Messages and Operator’s Guide InForm OS Version 2.3.1
Port port:<nsp> "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.2 Port Suggested Actions, General
Some specific examples are displayed below, but in general, use the following CLI commands
to check for these conditions:
■ For port SFP errors, use commands such as showport, showport -sfp, showport -sfp-ddm, showcage, showcage -sfp, and showcage -sfp -ddm.
■ For port CRC and Link Error Status Block (LESB) errors, use commands such as
showportlesb single, showportlesb hist, or
showportlesb hist -start|-t <time>.
11.4.9.3 Port Example 1Component ------Description------ QtyPort Degraded or failed SFPs 1
Component -Identifier- --Description--Port port:0:0:2 SFP is Degraded
11.4.9.4 Port Suggested Action 1
An SFP in a Node-Port is reporting a degraded condition. This is most often caused by the SFP
receiver circuit detecting a low signal level (RX Power Low), and that is usually caused by a
poor or contaminated FC connection, such as a cable. An alert should identify the condition,
such as the following:
Port 0:0:2, SFP Degraded (Receiver Power Low: Check FC Cable)
Check SFP statistics using CLI commands such as showport -sfp, showport -sfp -ddm,
showcage, etc.
cli% showport -sfpN:S:P -State-- -Manufacturer- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM0:0:1 OK FINISAR_CORP. 2.1 No No No Yes0:0:2 Degraded FINISAR_CORP. 2.1 No No No Yes
In the following example an RX power level of 361 microwatts (uW) for Port 0:0:1 DDM is a
good reading; and 98 uW for Port 0:0:2’s is a weak reading ( < 100 uW). Normal RX power level
readings are 200-400 uW.
cli% showport -sfp -ddm
Troubleshooting InServ Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
--------------Port 0:0:1 DDM-------------- -Warning- --Alarm----Type-- Units Reading Low High Low HighTemp C 41 -20 90 -25 95 Voltage mV 3217 2900 3700 2700 3900TX Bias mA 7 2 14 1 17 TX Power uW 330 79 631 67 631 RX Power uW 361 15 794 10 1259 --------------Port 0:0:2 DDM-------------- -Warning- --Alarm----Type-- Units Reading Low High Low HighTemp C 40 -20 90 -25 95 Voltage mV 3216 2900 3700 2700 3900TX Bias mA 7 2 14 1 17 TX Power uW 335 79 631 67 631 RX Power uW 98 15 794 10 1259
cli% showcageId Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 0 cage0 0:0:1 0 1:0:1 0 15 33-38 08 08 DC3 n/a 1 cage1 --- 0 1:0:2 0 15 30-38 08 08 DC3 n/a
cli% showpd -s Id CagePos Type -State-- -Detailed_State- 1 0:2:0 FC normal normal ... 13 1:1:0 NL degraded missing_A_port 14 1:2:0 FC degraded missing_A_port
cli% showpd -path ---------Paths--------- Id CagePos Type -State-- A B Order 1 0:2:0 FC normal 0:0:1 1:0:1 0/1 ... 13 1:1:0 NL degraded 0:0:2\missing 1:0:2 1/- 14 1:2:0 FC degraded 0:0:2\missing 1:0:2 1/-
11.4.9.5 Port Example 2Component -Description- QtyPort Missing SFPs 1
Component -Identifier- -Description--Port port:0:3:1 SFP is missing
11.29Troubleshooting InServ Storage Server Components
3PAR Confidential
11.30
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 -sfpN:S:P -State- -Manufacturer- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM0:0:1 OK FINISAR_CORP. 2.1 No No No Yes0:0:2 OK FINISAR_CORP. 2.1 No No No Yes0:3:1 - - - - - - - 0:3:2 OK FINISAR_CORP. 2.1 No No No Yes
11.4.9.7 Port Example 3Component -Description- QtyPort Disabled SFPs 1
Component -Identifier- --Description--Port port:3:5:1 SFP is disabled
11.4.9.8 Port Suggested Action 3
A node-port SFP will be disabled if the port has been placed offline using the controlport offline command. Also see Example 4.
cli% showport -sfpN:S:P -State- -Manufacturer- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM3:5:1 OK FINISAR_CORP. 4.1 Yes No No Yes3:5:2 OK FINISAR_CORP. 4.1 No No No Yes
11.4.9.9 Port Example 4Component -Description- QtyPort Offline ports 1
Component -Identifier- --Description--Port port:3:5:1 is offline
11.4.9.10 Port Suggested Action 4
Check the state of the port with showport. If a port is offline, it was deliberately put in that
state using the controlport offline command. Offline ports may be restored using
controlport rst.
cli% showportN:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type3:5:1 target offline 2FF70002AC00054C 23510002AC00054C free
Troubleshooting InServ Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
11.4.9.11 Port Example 5Component -----------Description------------------------- QtyPort 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. Devices with high InvCRC values are receiving bad packets
from an upstream device (disk, HBA, SFP, or cable).
cli% showportlesb single 3:2:1 ID ALPA ----Port_WWN---- LinkFail LossSync LossSig InvWord InvCRC<3:2:1> 0x1 23210002AC00054C 20697 2655432 20700 37943749 1756pd107 0xa3 2200001D38C28AA3 0 157 0 1129 0pd106 0xa5 2200001D38C0D01E 0 279 0 1551 0
11.4.9.13 Port Example 6Component -----------Description------------------------- QtyPort Ports with increasing CRC error counts 2
Component -Identifier- ------Description-----------Port port:2:2:1 CRC errors have been increasing by more than one per day ______________________ over the past week
11.4.9.14 Port Suggested Action 6
Check the fibre channel error counters for the port using the CLI commands showportlesb single and showportlesb hist.
The message "CRC errors have been increasing … over the past week" comes from a check of
the daily port-LESB history as seen in showportlesb hist. If the error condition has been
corrected, checkhealth port may continue to report the error until the next daily update
has been stored. It should stop being reported within 24 hours after the CRC counter stops
incrementing.
cli% showportlesb single 3:2:1 ID ALPA ----Port_WWN---- LinkFail LossSync LossSig InvWord InvCRC<3:2:1> 0x1 23210002AC00054C 20697 2655432 20700 37943749 1756pd107 0xa3 2200001D38C28AA3 0 157 0 1129 0pd106 0xa5 2200001D38C0D01E 0 279 0 1551 0
11.31Troubleshooting InServ Storage Server Components
3PAR Confidential
11.32
Messages and Operator’s Guide InForm OS Version 2.3.1
11.4.9.15 Port Example 7Component ------------Description------------ QtyPort 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. Useful CLI commands are showport,
showport -c, showport -par, showport -rcfc, showcage, etc.
cli% showportN:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type2:0:1 initiator ready 2FF70002AC000591 22010002AC000591 disk2:0:2 initiator ready 2FF70002AC000591 22020002AC000591 disk2:0:3 target ready 2FF70002AC000591 22030002AC000591 disk2:0:4 target loss_sync 2FF70002AC000591 22040002AC000591 free
Component -Identifier- ------Description-------Port port:0:1:1 Mismatched mode and type
cli% showportN:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type0:1:1 initiator ready 2FF70002AC000190 20110002AC000190 rcfc0:1:2 initiator loss_sync 2FF70002AC000190 20120002AC000190 free0:1:3 initiator loss_sync 2FF70002AC000190 20130002AC000190 free0:1:4 initiator loss_sync 2FF70002AC000190 20140002AC000190 free
11.4.10 RC
Displays Remote Copy issues.
■ Checks Remote Copy targets
■ Checks Remote Copy links
■ Checks Remote Copy Groups and VVs
NOTE: A known problem exists when Remote Copy is configured on a fibre
channel adapter port. These ports will be flagged in error and these errors can be
ignored. This will be fixed in a future release.
Troubleshooting InServ Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
11.4.10.1 Format of Possible RC Exception MessagesRC rc:<name> "All links for target <name> are down but target not yet marked failed." RC rc:<name> "Target <name> has failed." RC rc:<name> "Link <name> of target <target> is down." RC rc:<name> "Group <name> is not started to target <target>." RC rc:<vvname> "VV <vvname> of group <name> is stale on target <target>." RC rc:<vvname> "VV <vvname> of group <name> is not synced on target <target>."
11.4.10.2 RC ExampleComponent -Description- QtyRC Stale volumes 1
Component --Identifier--- ---------Description---------------RC rc:yush_tpvv.rc VV yush_tpvv.rc of group yush_group.r1127 is stale on target S400_Async_Primary.
11.4.10.3 RC Suggested Action
Perform remote copy troubleshooting such as checking the physical links between InServ
Storage Servers, and using CLI commands such as showrcopy, showrcopy -d, showport -rcip, showport -rcfc, shownet -d, controlport rcip ping, etc.
11.4.11 SNMP
Displays issues with SNMP.
Attempts the showsnmpmgr command and reports errors if the CLI returns an error.
11.4.11.1 Format of Possible SNMP Exception MessagesSNMP -- <err>
11.4.11.2 SNMP ExampleComponent -Identifier- ----------Description---------------SNMP -- Could not obtain snmp agent handle. Could be _______________________misconfigured.
11.4.11.3 SNMP Suggested Action
Any error message that can be produced by showsnmpmgr may be displayed.
11.4.12 Task
Displays failed tasks.
Checks for any tasks that have failed within the past 24 hours. This is the default time frame
for the showtask -failed command.
11.33Troubleshooting InServ Storage Server Components
3PAR Confidential
11.34
Messages and Operator’s Guide InForm OS Version 2.3.1
11.4.12.1 Format of Possible Task Exception MessagesTask Task:<Taskid> 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). Please see task status for details.
11.4.12.3 Task Suggested Action
The CLI command showtask -d Task_id will display detailed information about the task.
To clean up the Alerts and the Alert-reporting of checkhealth, you can delete the failed-task
alerts if they are of no further use. They will not be auto-resolved and they will remain until
they are manually removed with the 3PAR IMC (GUI) or CLI with removealert or setalert ack. To display system-initiated tasks, use showtask -all.
cli% showtask -d 6313 Id Type Name Status Phase Step 6313 background_command upgradecage -a -f failed --- ---
Detailed status is as follows:
2009-10-22 10:35:36 PDT Created task.2009-10-22 10:35:36 PDT Updated Executing "upgradecage -a -f" as 0:121092009-10-22 10:35:36 PDT Errored upgradecage: Invalid option: -f
11.4.13 VLUN
Displays inactive Virtual LUNs (VLUNs) and those which have not been reported by the host
agent.
Reports VLUNs that have been configured but are not currently being exported to hosts or
host-ports.
11.4.13.1 Format of Possible VLUN Exception Messagesvlun host:<hostname> "Host <ident>(<type>):<connection> is not connected to a port"
11.4.13.2 VLUN Example Component ---------Description--------- Qtyvlun Hosts not connected to a port 1
Component -----Identifier----- ---------Description--------
Troubleshooting InServ Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
vlun 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. For example:
cli% showvlun -host cs-wintec-test1Active VLUNsLun VVName HostName -Host_WWN/iSCSI_Name- Port Type 2 BigVV cs-wintec-test1 10000000C964121C 2:5:1 host----------------------------------------------------------- 1 total
VLUN TemplatesLun VVName HostName -Host_WWN/iSCSI_Name- Port Type 2 BigVV cs-wintec-test1 ---------------- --- host
cli% showhost cs-wintec-test1Id Name Persona -WWN/iSCSI_Name- Port 0 cs-wintec-test1 Generic 10000000C964121D --- 10000000C964121C 2:5:1
cli% servicehost listList of inactive hosts:
Lun VVName HostName -Host_WWN/iSCSI_Name- Port Type 2 BigVV cs-wintec-test1 10000000C964121D 3:5:1 unknown
11.4.14 VV
Displays Virtual Volumes (VV) that are not optimal.
Checks for VVs and Common Provisioning Groups (CPG) whose state is not normal.
11.4.14.1 Format of Possible VV Exception MessagesVV vv:<vvname> "IO to this volume will fail due to no_stale_ss policy"VV vv:<vvname> "Volume has reached snapshot space allocation limit"VV vv:<vvname> "Volume has reached user space allocation limit"VV vv:<vvname> "VV has expired"cpg cpg:<cpg> "CPG is unable to grow SA (or SD) space"
11.35Troubleshooting InServ Storage Server Components
3PAR Confidential
11.36
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.
Troubleshooting InServ Storage Server Components
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
12Alerts
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. For complete
information on the events log’s display options, see the InForm OS Command Line Interface
Reference.
0x10001 12.7
0x30001 12.8
0x300de 12.9
0x300fa 12.10
0x40003 12.11
0x400fa 12.12
NOTE: Message codes ending in de indicate a degraded state alert. Message
codes ending in fa indicate a failed state alert.
12.1Alerts
3PAR Confidential
12.2
Messages and Operator’s Guide 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.51
3PAR Confidential
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.33PAR Confidential
12.4
Messages and Operator’s Guide 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.131
0x27000f 12.132
3PAR Confidential
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.53PAR Confidential
12.6
Messages and Operator’s Guide InForm OS Version 2.3.1
0x460001 12.165
3PAR Confidential
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. If there is a hardware failure in the main link connecting nodes x and y at the same
time there is a serial link failure, there is a 50% chance of losing the healthy node.
MESSAGE 2
Serial link from node x to node y failed. Rate of loss 100%.
SUGGESTED ACTION
The serial link hardware between node x and node y has detected an error. Node y should be
replaced and diagnosed. If there is a hardware failure in the main link connecting nodes x and
y at the same time there is a serial link failure, there is a 50% chance of losing the healthy
node.
MESSAGE 3
Serial link from node x to node y failed. Rate of loss <percent_of_loss>.
SUGGESTED ACTION
There might be an error in the low-level software controlling the serial port in either node x or
node y; or the hardware might be unstable. If there is a hardware failure in the main link
connecting nodes x and y at the same time there is a serial link failure, there is a 50% chance of
losing the healthy node. If there are many nodes that report the same condition to a specific
node, replace and diagnose that node.
12.73PAR Confidential
12.8
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x30001
TYPE
Firmware coredump event
MESSAGE
Firmware COREDUMP: recovered file <file_name>
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.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x300de
TYPE
Component state change
MESSAGE
Port <port_id> Node <node_id> Slot <slot_id> Degraded (<list of states>)
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.
STATE 2
Target Mode Port Went Offline
SUGGESTED ACTION
May be caused by a pulled cable or the HBA being reset due to an internal error. If there is an
HBA core dump file present in /var/core/hba on the master node, send the information to
your local service provider for analysis.
STATE 3
Firmware Coredump
SUGGESTED ACTION
Contact your local service provider for technical support and services.
STATE 4
Target Qlength Above Threshold
SUGGESTED ACTION
The fibre channel target port is getting very high traffic and may start sending back QFULL
conditions back to the host. Consider spreading the load between the different target ports on
the InServ array or turning on flow control on the hosts to reduce the load on this target port.
Contact your local service provider for technical support and services.
12.93PAR Confidential
12.10
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x300fa
TYPE
Component state change
MESSAGE
Port <port_id> Node <node_id> Slot <slot_id> Failed (<list of states>)
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. Contact your local service provider
for technical support and services.
STATE 3
Shutdown due to too many firmware cores
SUGGESTED ACTION
The HBA port is getting multiple fatal errors in succession. Send the firmware cores and the
event log to your local service prover for analysis.
STATE 4
Shutdown due to too many internal errors
SUGGESTED ACTION
The HBA port is getting multiple internal errors. Use CLI command controlport rst -l to
hard reset the HBA port. Replace the HBA if the problem persists.
3PAR Confidential
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.113PAR Confidential
12.12
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x400fa
TYPE
Component state change
MESSAGE
VV <vv_id>(<vvname>) Failed (<list of states>)
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 <vvname> to confirm that the
VV is still in this state.
Use the CLI command showld -vv <vvname> to see which LDs are not in the 'normal' state.
Most of the time, LDs are not in the normal state because some nodes, drive cages, or PDs are
off-line.
Contact your local service provider for technical support and services.
STATE 2
Needs Checking
SUGGESTED ACTION
The VV specified in the alert has not been started by the system because it needs a consistency
check to be run on it. Use the CLI command showvv <vvname> to confirm that the VV is still
in this state.
To run the consistency check, use the CLI command checkvv. After a successful check, the VV
will transition to the 'normal’ state.
NOTE: Prior to running a consistency check:
1 Run the CLI command showvv to confirm the VV is still in this state.
2 Run the CLI command showld -vv <vvname> to confirm that all the underlying
LDs are in the ‘normal state.
3PAR Confidential
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. Use the CLI command showvv <vvname> to confirm that the VV is still in
this state. Use the CLI commands showld -vv <vvname> and showpd to obtain additional
data on the underlying errors. Once these errors are fixed, the VV will transition automatically
to the 'normal' state.
Contact your local service provider for technical support and services.
STATE 5
Stale
SUGGESTED ACTION
The snapshot VV specified in the alert is stale. Use the CLI command showvv <vvname> to
confirm that the VV is still in this state.
The snapshot VV is stale because at some point in the past, there were I/O errors on the
underlying LDs, or because the snapshot volume ran out of space. At this point, the only action
that can be taken on this VV is to delete it.
Contact your local service provider for technical support and services.
STATE 6
Copy Failed
12.133PAR Confidential
12.14
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.
3PAR Confidential
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.
4 Use the admithw command to create a new Log Ld.
If this does not resolve the issue, contact 3PAR engineering for support.
12.153PAR Confidential
12.16
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.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x60003
TYPE
Invalid PD configuration
MESSAGE
Disk <disk_id> (wwn <disk_wwwn>) is showing up with two wwns on port <port_id> - <wwn1> and <wwn2>
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.173PAR Confidential
12.18
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x60007
TYPE
Disk overtemp alert
MESSAGE 1
PD <pd_id> (wwn <wwn>) is overtemp (<temp> 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.
MESSAGE 2
PD <pd_id> (wwn <wwn>) is overtemp (<temp> C) but could not be 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.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x60008
TYPE
Disk overtemp warning
MESSAGE
At least one drive <pd_id> 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.193PAR Confidential
12.20
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x60009
TYPE
Disk overtemp alert
MESSAGE
At least one drive <pd_id> 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. Contact your local service provider for technical support and services.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x600de
TYPE
Component State Change
MESSAGE
PD <pd_id> Degraded (<list of states>)
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 <pd_id> to confirm the disk is still in this state. If both ports
are reporting errors, then another alert is posted specifying No Valid Ports on that disk.
STATE 2
Errors on B 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 <pd_id> to confirm the disk is still in this state. If both ports
are reporting errors, then another alert is posted specifying No Valid Ports on that disk.
STATE 3
Disabled A Port
SUGGESTED ACTION
The PD specified in the alert has one of its ports marked as disabled.
If this is not because of a service action, please contact your local service provider for further
information.
STATE 4
Disabled B Port
SUGGESTED ACTION
The PD specified in the alert has one of its ports marked as disabled.
12.213PAR Confidential
12.22
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 <pd_id> to confirm the disk is still in this state.
This state might be temporary and might fix itself on retries. If the error persists, contact your
local service provider for technical support and services.
STATE 6
Missing
SUGGESTED ACTION
The PD specified in the alert has been missing on both ports. Use the CLI command showpd <pd_id> to confirm the disk is still in this state.
This state might be temporary and might fix itself on retries. If the error persists, contact your
local service provider for technical support and services.
STATE 7
Missing A Port
SUGGESTED ACTION
The PD specified in the alert has its A port missing. Use the CLI showpd <pd_id> to confirm it
is still in this state.
If the disk has disappeared from the A loop, it reports its A 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 8
Missing B Port
SUGGESTED ACTION
The PD specified in the alert has its B port missing. Use the CLI showpd <pd_id> to confirm it
is still in this state.
3PAR Confidential
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.
The relocations could be because of an active service operation or because of intermittent
disturbances. No further action is required.
STATE 10
Servicing
SUGGESTED ACTION
This is a disk activity flag indicating the disk is being serviced. This flag will be set if a
servicemag or a servicecage operation is active on the disk.
STATE 11
Prolonged Missing A Port
SUGGESTED ACTION
Port A is missing for over 20 minutes. Check if the PD port is missing by issuing CLI command
showpd and showcage -d. If only one port is missing, the PD may need to be replaced.
Contact your local service provider for technical support and services.
STATE 12
Prolonged Missing B Port
SUGGESTED ACTION
Port B is missing for over 20 minutes. Check if the PD port is missing by issuing CLI command
showpd and showcage -d. If only one port is missing, the PD may need to be replaced.
Contact your local service provider for technical support and services.
STATE 13
Cage State Missing
12.233PAR Confidential
12.24
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.
STATE 17
Fail To Spinup
SUGGESTED ACTION
The PD is experiencing problems spinning up. If this continues, a new failure alert will be
issued with further actions to be taken.
STATE 18
Loop Failure
SUGGESTED ACTION
The PD loop connection may have failed. No action required.
STATE 19
Drive Error Bit Set
3PAR Confidential
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.
STATE 23
Sysmgr Spundown
SUGGESTED ACTION
The Sysmgr has issued a command for a PD to be spundown. No action required.
STATE 24
Critical Over Temp
SUGGESTED ACTION
Temperature of the PD has reached the threshold maximum. Check for fan failure and
ventilation obstructions.
STATE 25
Spundown Requested Drive Ready
12.253PAR Confidential
12.26
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.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x600fa
TYPE
Component state change
MESSAGE
PD <pd_id> Failed (<list of states>)
STATE 1
Invalid
SUGGESTED ACTION
The PD specified in the alert has been marked failed. Use the CLI command showpd <pd_id>
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.
If there is no reason code associated with this, contact your local service provider for technical
support and services.
STATE 2
Inquiry Failed
SUGGESTED ACTION
The PD specified in the alert has been marked failed because a SCSI inquiry to it failed. Use the
CLI command showpd <pd_id> to confirm the disk is still in this state.
A disk is marked failed because a SCSI inquiry to it failed to gather information about its serial
number, device ID, vendor ID, etc. Generally this alert is auto-fixed when the SCSI inquiry is
retried.
Wait for a few minutes to see if the alert is auto-fixed. If that does not happen, contact your
local service provider for a possible disk replacement.
STATE 3
Unit Ready Failed
12.273PAR Confidential
12.28
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 <pd_id> 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.
STATE 4
Read Capacity Failed
SUGGESTED ACTION
The PD specified in the alert has been marked failed because a command sent to read its
capacity has failed. Use the CLI command showpd <pd_id> to confirm the disk is still in this
state.
A disk is marked failed if a SCSI inquiry to check its capacity fails. This error is also intermittent
and might get fixed if the SCSI inquiry succeeds on a retry. As above, the suggested action is to
wait for a few minutes for the retry to fix it. If not, contact your local service provider for a
possible disk replacement.
STATE 5
Write Label Failed
SUGGESTED ACTION
The PD specified in the alert has been marked failed because the disk label could not be
written to the disk. Use the CLI command showpd <pd_id> to confirm the disk is still in this
state.
If the error is persistent, contact your local service provider for possible disk replacement.
STATE 6
Mod Page Update Failed
SUGGESTED ACTION
The PD specified in the alert has been marked failed because its mod pages could not be
updated. Use the CLI command showpd <pd_id> to confirm the disk is still in this state.
If the error is persistent, contact your local service provider for possible disk replacement.
3PAR Confidential
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 <pd_id> to confirm the disk is still in this state.
If the error is persistent, contact your local service provider for possible disk replacement.
STATE 8
Invalid Label
SUGGESTED ACTION
The PD specified in the alert has been marked failed because the disk label read from the disk
cannot be validated. Use the CLI command showpd <pd_id> to confirm the disk is still in this
state.
If the error is persistent, contact your local service provider for possible disk replacement.
STATE 9
Invalid Capacity
SUGGESTED ACTION
The PD specified in the alert has been marked failed because the capacity of
the disk read by a SCSI inquiry is different from the matching entry in a list of supported values.
Use the CLI command showpd <pd_id> to confirm the disk is still in this state.
Contact your local service provider for possible disk replacement.
STATE 10
Invalid Type
SUGGESTED ACTION
The PD specified in the alert has been marked failed because the vendor of the disk is not
included in the list of supported vendors. Use the CLI command showpd <pd_id> to confirm
the disk is still in this state.
Contact your local service provider for possible disk replacement.
STATE 11
Invalid Firmware
12.293PAR Confidential
12.30
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 <pd_id> 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. Use the CLI command showpd <pd_id> to confirm the disk is still in this state.
Contact your local service provider for possible disk replacement.
STATE 13
Invalid Cage
SUGGESTED ACTION
The PD specified in the alert has been marked temporarily failed because it does not have a
known cage position. Use the CLI command showpd <pd_id> to confirm the disk is still in this
state.
If the error persists, contact your local service provider for possible disk replacement.
STATE 14
Prolonged Not Ready
SUGGESTED ACTION
The PD specified in the alert has been marked failed because it has been marked not ready for
more than 20 minutes. Use the CLI command showpd <pd_id> to confirm the disk is still in
this state.
Contact your local service provider for possible disk replacement.
STATE 15
Prolonged Missing
3PAR Confidential
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 <pd_id> 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. Use the CLI command showpd <pd_id> to confirm the disk is still in this state.
A disk might be marked failed because the media on certain sectors is marked bad. Other
reason codes below might help in further analysis of why the disk has its media marked invalid.
STATE 17
Failed Hardware
SUGGESTED ACTION
A disk might be marked media-failed because the hardware reports media failures. Contact
your local service provider to replace the disk.
STATE 18
Smart Threshold Exceeded
SUGGESTED ACTION
A disk might be marked media-failed if it has been reporting disk aborts with error code 21 to
specify that the threshold for SMART errors has been exceeded.
Contact your local service provider to replace the disk.
STATE 19
Multiple Chunklets Media Bad
SUGGESTED ACTION
A disk might be marked media-failed because more than six chunklets on that disk have
reported media-errors.
Contact your local service provider to replace the disk.
12.313PAR Confidential
12.32
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.
STATE 22
No Valid Ports
SUGGESTED ACTION
The PD specified in the alert has been failed because it has no valid ports. Use the CLI
command showpd <pd_id> to confirm the disk is still in this state.
Contact your local service provider for technical support and services.
3PAR Confidential
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 <disk_id> <chunklet_position>
SUGGESTED ACTION
The system has a limit on the number of free chunklets that are used for automatic relocation.
This limit is one disk worth of chunklets per system node. If you see this alert, there must have
been numerous disk errors on the system recently, or perhaps an entire cage is missing, or the
system has used up all it's free space. Fixing that error condition will automatically repair the
problem.
Contact your local service provider for technical support and services.
12.333PAR Confidential
12.34
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 <disk_id> <chunklet_position>
SUGGESTED ACTION
The system has a limit on the number of free chunklets that are used for automatic relocation.
This limit is one disk worth of chunklets per system node. If you see this alert, there must have
been numerous disk errors on the system recently, or perhaps an entire cage is missing, or the
system has used up all it's free space. Fixing that error condition will automatically repair the
problem.
Contact your local service provider for technical support and services.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x90001
TYPE
Host configuration error
MESSAGE
Host <host_id> persona <persona_id> is incompatible with port <port_id> persona <persona_id>
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.353PAR Confidential
12.36
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x900fa
TYPE
Host Persona Incompatible with Port Persona
MESSAGE
Host <host_id> persona <persona_id> incompatible with port <port_id> persona <persona_id> Failed (<list of states>)
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.
3PAR Confidential
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 <volume_name>, id <volume_ID>(kernel ID <interal_volume_ID>) low on space, l2bmap <percentage>% 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.373PAR Confidential
12.38
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 <volume_name>, id <volume_ID>(kernel ID <internal_volume_ID>) low on space, l2bmap <percentage>% 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.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0xc0002
TYPE
Process cannot be started
MESSAGE
Process <process_name> could not be started up after repeated attempts on node <node_id>
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.393PAR Confidential
12.40
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 <node_id>, not the admin volume. Previously recorded alerts will not be visible until the PR transitions to the admin volume.
SUGGESTED ACTION
Try to determine why the admin volume is not functional. Most likely, this is because some
nodes or cages are not currently available.
Contact your local service provider for technical support and services.
3PAR Confidential
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.413PAR Confidential
12.42
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.
MESSAGE 2
TOC quorum found for TOC <TOC_generation_number>, but waiting for nodes <node_ids> to boot up. If the nodes are offline, use “setsysmgr tocgen <TOC_generation_number>”.
SUGGESTED ACTION
Some nodes have not joined the cluster. Try to rejoin the nodes to the cluster. If this fails, run
setsysmgr tocgen <TOC_generation_number>, where <TOC_generation_number> is shown in the alert.
MESSAGE 3
TPD system is waiting for manual startup. Use “setsysmgr” to set system manager startup date.
SUGGESTED ACTION
The file /manualstartup has been created on one or more nodes. Remove it from all nodes
and run setsysmgr to proceed. Normally, running setsysmgr tocgen starts the system.
NOTE: The Table of Contents (TOC) generation number is an identifying
number that distinguishes each modified version of the TOC from its predecessor.
Normally, the largest numbered generation is the one that is valid.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE 4
Cannot reach TOC quorum for TOC <TOC_generation_number>. 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 <TOC_generation_number>.
MESSAGE 5
TOC quorum found for TOC <TOC_generation_number>, but waiting for nodes <node_ids> to boot up because we need to recover from a previous powerfail. You can use “setsysmgr force_iderecovery” to force recovery with possible data loss.
SUGGESTED ACTION
Attempt to get all the nodes online in order to attempt a successful powerfail recovery.
If only one node is still down, the system waits about 10 minutes and attempts to do a
powerfail recovery with the remaining nodes.
If more than one node is still down, contact your local service provider for technical support
and services.
12.433PAR Confidential
12.44
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.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0xe0005
TYPE
License key usage
MESSAGE 1
This system contains <current_nodes> nodes, but is only licensed for <max_nodes> nodes. Please contact your 3PAR representative as soon as possible.
SUGGESTED ACTION
The system is not licensed for the number of nodes currently installed; shut down the excess
nodes, or contact your local service provider regarding purchasing licenses for the additional
nodes.
MESSAGE 2
License feature <feature_name> has expired. You are in violation of your 3PAR License Agreement. Please contact your 3PAR representative as soon as possible.
SUGGESTED ACTION
The trial period for the stated feature has expired. Contact your local service provider to either
purchase the full license for this feature, or to have a new license key installed with this
feature disabled.
MESSAGE 3
The maximum size allowed for <feature_name> <maximum_licensed_size> has been exceeded. You are in violation of your 3PAR License Agreement. Please contact your 3PAR representative as soon as possible.
SUGGESTED ACTION
The maximum thin provisioning size has been exceeded. Contact your local service provider if
you want to purchase a license for a larger size.
12.453PAR Confidential
12.46
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 <volume_name> with id <volume_ID_number>.
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.
3PAR Confidential
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 <node_id> had <number_of_panics> 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.473PAR Confidential
12.48
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0xe0008
TYPE
Power fail saved version mismatch
MESSAGE
Powefail saved version <num> on node <nodeid> does not match expected version <num>. 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.
3PAR Confidential
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 <number of tasks> 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. To resolve the problems
with the admin volume, contact your local service provider.
12.493PAR Confidential
12.50
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0xe000a
TYPE
Task failed
MESSAGE
Task <task_id> <task_type> <task_name> has failed <failure_reason> with a failure code of <failure_code>. Please see task status for details.
SUGGESTED ACTION
The task specified in the message has failed. Run the CLI showtask -d <taskid> command
for detailed status on the failure.
3PAR Confidential
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 <n> with missing node <m>.
SUGGESTED ACTION
Contact your local service provider for technical support and services.
12.513PAR Confidential
12.52
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 <node_mask_id> reason <reason_id>
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.
3PAR Confidential
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 <node_id> for replicant <replicant_id>.
SUGGESTED ACTION
Contact your local service provider for technical support and services.
12.533PAR Confidential
12.54
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 <missing_node_id>. Current online: <current_nodes_online_mask>, original online: <original_nodes_online_mask>.
SUGGESTED ACTION
Contact your local service provider for technical support and services.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x110001
TYPE
Errors accessing the internal drive
MESSAGE
Filesystem <file_system_mount_point> on node <node_id> 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. Look for a subsequent alert
with message code 1114114 listing the action taken in response to this issue.
12.553PAR Confidential
12.56
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x110002
TYPE
Internal drive error handling
MESSAGE 1
Node <node_id> is being shutdown by the system because it had internal drive errors.
MESSAGE 2
Node <node_id> is not being shutdown by the system though of internal drive errors because it is the last node left alive.
MESSAGE 3
Node <node_id> is not being shutdown by the system though of internal drive errors because some LDs cannot be served by the remaining nodes.
SUGGESTED ACTION FOR MESSAGE 1-3
This alert indicates what action was taken as a result of an earlier alert with message code
0x110001.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x110004
TYPE
Version mismatch event
MESSAGE 1
My node <node_id> version x1.x2.x3.x4 could not join the cluster with node <node_id> 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.573PAR Confidential
12.58
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 <number of deleted alerts> 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.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x140001
TYPE
Notification
MESSAGE 1
Media error fix on PD <pdid>: <chunklet_id> failed-<reason_string>
SUGGESTED ACTION
For media error corrective action alerts, inform your local service provider with the alert
information.
MESSAGE 2
Notification SCSI hardware error <error_code> detected on PD <pdid> --This drive should be replaced
SUGGESTED ACTION
For a hardware error alert, inform your local service provider with the alert information.
MESSAGE 3
Node <node_id> is not integraged.
SUGGESTED ACTION
This alert is issued after five attempts or approximately 25 minutes after the node first
attempted integration into the cluster. If the node is able to integrate after five attempts a
fixed alert message is issued.
Contact your local service provider for technical support and services.
12.593PAR Confidential
12.60
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 <max> exceeded, no process created for connection from client address<IP address>:<port>
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.
Contact your local service provider for technical support and services.
MESSAGE 2
Could not fork CLI server process for connection from client address <IP>:<port>
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.
Contact your local service provider for technical support and services.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x150006
TYPE
Authentication failure
MESSAGE
<number of fails> authentication failures in <n> 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.613PAR Confidential
12.62
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x15000c
TYPE
CPG free space limit
MESSAGE
Free space allows CPG <cpgname> to grow to <n>MB, limit: <limit>MB, warn:<warning>MB
NOTES
This alert is generated when there is not enough storage in the system to allow the CPG to
grow to either the growth warning or limit size, i.e. the warning/alert settings are meaningless
because the system will run out of storage before these can be reached.
The alert is generated every 24 hours when the condition exists.
The alert is auto-fixed on this same 24 hour cycle if the condition is corrected, i.e. the warning/
limit has been lowered, removed or more space has been made available to the CPG.
SUGGESTED ACTION
There are several possible suggested actions to correct the condition:
1 Adjust the CPG growth warning/limit down to a level below the actual storage available to
the system, as follows:
setcpg -sdgl <new limit> cpgname
setcpg -sdgw <new limit> cpgname
Note the showspace command can be useful in determining how much space is available
to the CPG. Note also that the CPG growth arguments can be obtained from the showcpg -sdg command (see example below).
2 Remove the warning/limit by setting the value to zero (see step1 example).
3 Contact your local service provider to add more storage.
4 Adjust the CPG growth parameters to make more storage available to the CPG. For
example, if a PD pattern was used to restrict the CPG to a specific set of disks, this pattern
could be expanded to provide more space to the CPG.
For example, the following shows a CPG with only 30720MB available for growth:
◆ Create a CPG with specific growth arguments:
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
cli% createcpg -ha mag -p -dk 0-7 mycpg
◆ Determine the space available for future growth:
cli% showspace -ha mag -p -dk 0-7
--Estimated(MB)---
RawFree UsableFree
61440 30720
◆ Display the current CPG growth arguments:
cli% showcpg -sdg mycpg
Id NameWarnMBLimitMB GrowMB Args
0 mycpg - - 32768 -ha mag -p -dk 0-7
◆ Verify additional space is available with a different disk pattern:
cli% showspace -ha mag -p -dk 0-15
--Estimated(MB)---
RawFree UsableFree
197632 98816
◆ Update the CPG growth parameters with this new pattern:
cli% setcpg -ha mag -p -dk 0-15 mycpg
12.633PAR Confidential
12.64
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x170001
TYPE
TOC update
MESSAGE
TOC update done to <number_of_good_TOC_copies> disks out of <total_number_of_TOC_copies>.
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.
3PAR Confidential
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.653PAR Confidential
12.66
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x1a0002
TYPE
Node is down
MESSAGE
Node <node_id> 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.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x1a0005
TYPE
HW: CPU Memory Correctable ECC
MESSAGE
Node <node_id> DIMM <DIMM_id> (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.673PAR Confidential
12.68
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x1a0006
TYPE
CPU Configuration
MESSAGE
Node <node_id> Expected <number_of_CPUs> CPUs Found <number_of_CPUs> CPUs
SUGGESTED ACTION
A CPU is either bad or missing. Replace the node motherboard. Contact your local service
provider for technical support and services.
3PAR Confidential
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 <filename>
SUGGESTED ACTION
Node firmware (BIOS) previously detected a hardware failure which required normal operation
to abruptly terminate. A log of the event and BIOS output leading up to the event has been
recorded and is available at the specified path. This log needs to be examined for a detailed
failure cause. Contact your local service provider for technical support and services.
12.693PAR Confidential
12.70
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x1a0008
TYPE
Node environmental
MESSAGE
Node#: <Error Code>: <status> <Expected>: <Reading>, hi_limit: <Hi Limit>, lo_limit: <Lo Limit>
Where:
<Error Code> is:
<Status> 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,
Table 12-2.
OVER LIMIT <Hi Limit>
UNDER LIMIT <Lo Limit>
Within Tolerance = 0x38,
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
<Expected>, <Reading>, <Hi Limit>, <Lo Limit> are:Table 12-3.
Measurement Reading Lo Limit Hi Limit Status CPU0 1.32V: 1.32 V 1.28 V 1.36 V Within Tolerance CPU1 1.32V: 1.32 V 1.28 V 1.36 V Within Tolerance 82563 1.20V: 1.21 V 1.13 V 1.26 V Within Tolerance 31154 1.30V: 1.29 V 1.22 V 1.37 V Within Tolerance 82563 1.90V: 1.88 V 1.79 V 2.00 V Within Tolerance 3.30V: 3.36 V 3.11 V 3.47 V Within Tolerance PLX 3.30V: 3.30 V 3.12 V 3.47 V Within Tolerance VCC 5.00V: 5.15 V 4.74 V 5.76 V Within Tolerance V_PTT 1.20V: 1.20 V 1.13 V 1.26 V Within Tolerance MCH 1.50V: 1.50 V 1.41 V 1.58 V Within Tolerance ESB 1.50V: 1.50 V 1.41 V 1.58 V Within Tolerance FBD 1.50V: 1.44 V 1.41 V 1.58 V Within Tolerance FBD 1.80V: 1.79 V 1.69 V 1.89 V Within Tolerance VTT_FBD 0.90V: 0.91 V 0.84 V 0.95 V Within Tolerance ESB 1.20V: 1.21 V 1.13 V 1.26 V Within Tolerance PLX 1.00V: 1.00 V 0.94 V 1.05 V Within Tolerance Osprey DDR 1.25V: 1.25 V 1.17 V 1.32 V Within Tolerance Osprey DDR 2.50V: 2.50 V 2.36 V 2.63 V Within Tolerance Osprey Lnk 1.87V: 1.86 V 1.76 V 1.97 V Within Tolerance FPGA 2.50V: 2.50 V 2.36 V 2.63 V Within Tolerance 12.00V: 12.00 V 11.37 V 12.62 V Within Tolerance MCH Temp: 41 C 0 C 85 C Within Tolerance Board Temp: 27 C 0 C 70 C Within Tolerance LM94 Temp: 23 C 0 C 65 C Within Tolerance LM87 Temp: 25 C 0 C 65 C Within Tolerance LM87 Ext Temp: 23 C -10 C 65 C Within Tolerance CPU0 Temp: 25 C 0 C 85 C Within Tolerance CPU1 Temp: 28 C 0 C 85 C Within Tolerance CPU0 VRM Temp: n/a n/a n/a Within Tolerance CPU1 VRM Temp: n/a n/a n/a Within Tolerance CPU DIMM0 Temp: 38 C 0 C 105 C Within Tolerance CPU DIMM1 Temp: 36 C 0 C 105 C Within Tolerance
NOTE: These tables are examples of environmental readings from nodes. The
specific output for your node may vary.
12.713PAR Confidential
12.72
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.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x1a00de
TYPE
Component State Change
MESSAGE
Node <node_id> Degraded (<list of states>)
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.
STATE 3
CPU Overheating
SUGGESTED ACTION
Use the shownodeenv command to view current system temperatures and voltages. If a
temperature limit has been exceeded, verify the system has adequate ventilation and ambient
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 4
CPU VRM Overheating
SUGGESTED ACTION
Use the shownodeenv command to view current system temperatures and voltages. If a
temperature limit has been exceeded, verify the system has adequate ventilation and ambient
12.733PAR Confidential
12.74
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. If a
temperature limit has been exceeded, verify the system has adequate ventilation and ambient
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.
1)
STATE 6
Node Offline Due to Failure
SUGGESTED ACTION
If the node doesn't come back up within 1 hour, contact 3PAR technical support.
STATE 7
Node Shutdown Manually
SUGGESTED ACTION
If the node doesn't come back up after maintenance has been completed, contact 3PAR
technical support.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x1a00fa
TYPE
Component State Change
MESSAGE
Node <node_id> Failed (<list of states>)
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.
STATE2
Uncorrectable Memory Error
SUGGESTED ACTION
The reported DIMM should be replaced. Contact your local service provider for technical
support and services.
STATE 3
Multiple Uncorrectable Memory Error
SUGGESTED ACTION
The reported DIMM should be replaced. Contact your local service provider for technical
support and services.
STATE 4
Internal System Error
SUGGESTED ACTION
Contact your local service provider for technical support and services.
STATE 5
Hardware Watchdog Error
12.753PAR Confidential
12.76
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.
STATE 8
Node Offline Due to Failure
SUGGESTED ACTION
The node identified in the alert is currently off-line due to a failure. If it is a recoverable failure,
then the node will rejoin the system soon. Use the CLI command shownode to view the current
state of the node. The node identified may need replacement. Contact your local service
provider for technical support and services.
STATE 9
Node Shutdown Manually
SUGGESTED ACTION
The node identified in the alert was shutdown by an administrator or service personnel. Use
the CLI command shownode to view the current state of the node. If shutting down the node
was unexpected, contact your local service provider for technical support and services.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
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.
Suggested Action: Replace the faulty power supply. If the condition persists after replacing
the power supply, replace the battery and/or the battery cable. Replace the node if the
condition persists.
■ <e2> (PS1 - ACFAIL) ■ <f2> (PS0 - ACFAIL)
■ <e4> (PS1 - CHROVLD) ■ <f4> (PS0 - CHROVLD)
■ <e5> (PS1 - BATFAIL) ■ <f5> (PS0 - BATFAIL)
12.773PAR Confidential
12.78
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x1b00de
TYPE
Component State Change.
MESSAGE
Node <node_id> Power Supply <power_supply_id> Degraded (<list of states>)
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.
STATE 2
Oscillating Presence
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 3
Oscillating DC Failure
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 4
Oscillating AC Failure
3PAR Confidential
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. If problem persists, replace power supply. Contact your local service
provider for technical support and services.
STATE 6
Oscillating Charger Overload
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 7
Oscillating Battery Failure
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.
12.793PAR Confidential
12.80
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x1b00fa
TYPE
Component State Change.
MESSAGE
Node <node_id> Power Supply <power_supply_id> Failed (<list of states>)
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.
Make sure the power supply is fully seated and the on/off switch is ON. If there is not an AC
failure, the power switch is on, and the power supply is fully inserted, replace the power
supply.
STATE 3
AC Failure
SUGGESTED ACTION
Check the AC cables and ensure the AC connection is good. If the AC connection is good but
the power supply still reports an AC failure, replace the power supply.
STATE 4
Fan Failure
3PAR Confidential
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.813PAR Confidential
12.82
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x1e0001
TYPE
Cage log alerts
MESSAGE 1
Midplane FPGA_<fpga> ESI<port> <failure type> failure: <code>.
SUGGESTED ACTION
Internal midplane hardware error. One or more communication channels has been disabled.
Replace midplane.
MESSAGE 2
Midplane FPGA_<fpga> IRQ rate too high: <code>.
SUGGESTED ACTION
Internal midplane hardware error. Two or more communication channels have been disabled.
Hard reset cage using InForm UI. If error persists, replace midplane.
MESSAGE 3
Midplane FPGA_<fpga> FPGA Downrev: <rev>.
SUGGESTED ACTION
An older version of FPGA firmware was detected. Replace midplane.
MESSAGE 4
Miplane FPGAs FPGA Revision Mismatch: <code>.
SUGGESTED ACTION
Internal midplane hardware error. All communication channels have been disabled. Replace
midplane.
MESSAGE 5
Midplane FPGA_<fpga> Revision unknown: <rev>.
SUGGESTED ACTION
Internal midplane hardware error. Two or more communication channels have been disabled.
Replace midplane.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE 6
Midplane FPGA_<fpga> POST Fail: <code>.
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 <count> (<code>).
SUGGESTED ACTION
Internal midplane hardware error. If you receive this alert, then cage completed self recovery.
If error persists, replace midplane.
MESSAGE 8
Firmware panic due to disk presence assertion. Panic count is <count> (<code>).
SUGGESTED ACTION
Internal midplane hardware or software error. If you receive this alert, then cage completed
self recovery. Upgrade cage firmware. If error persists, replace midplane.
MESSAGE 9
Firmware panic due to watchdog timeout. Panic count is <count> (<code>).
SUGGESTED ACTION
Internal midplane hardware or software error. If you receive this alert, then cage completed
self recovery. Upgrade cage firmware. If error persists, replace midplane.
MESSAGE 10
Firmware panic due to CPU exception. Panic count is <count> (<code>).
SUGGESTED ACTION
Internal midplane hardware or software error. If you receive this alert, then cage completed
self recovery. Upgrade cage firmware. If error persists, replace midplane.
12.833PAR Confidential
12.84
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE 11
Firmware panic due to PMC read failure. Panic count is <count> (<code>).
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 <count> (<code>).
SUGGESTED ACTION
Internal midplane hardware error. If you receive this alert, then cage completed self recovery.
If error persists, replace midplane.
MESSAGE 13
Firmware panic due to generic POST failure. Panic count is <count> (<code>).
SUGGESTED ACTION
Internal midplane hardware error. If you receive this alert, then cage completed self recovery.
If error persists, replace midplane.
MESSAGE 14
Firmware panic due to SRAM test failure. Panic count is <count> (<code>).
SUGGESTED ACTION
Internal midplane hardware error. If you receive this alert, then cage completed self recovery.
If error persists, replace midplane.
MESSAGE 15
Midplane PMC <ID> Revision <rev> not supported.
SUGGESTED ACTION
Internal midplane hardware error. Replace midplane.
MESSAGE 16
POST IRQ Init <error> <code>.
3PAR Confidential
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 <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. Interrupts could not be initialized. Replace FCAL1 or replace
midplane.
MESSAGE 18
POST Ticker Init <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. Timer could not be initialized. Replace midplane.
MESSAGE 19
POST Flash Init <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. Flash initialization failed. Replace midplane.
MESSAGE 20
POST Event Log Init <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. Event log initialization failed. Replace midplane.
MESSAGE 21
POST I2C Init <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. I2C initialization failed. Replace midplane.
MESSAGE 22
POST Env Init <error> <code>.
12.853PAR Confidential
12.86
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 <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. Error 10, 11, or 20: I2C failed to PROM device. Replace
midplane.
MESSAGE 24
POST FPGA Init <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. Communication with FPGA failed. Replace midplane.
MESSAGE 25
POST Watchdog Init <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. CPU watchdog initialization failed. Replace midplane.
MESSAGE 26
POST IRQ Enable <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. CPU interrupts could not be enabled. Replace midplane.
MESSAGE 27
POST IRQ Test <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. CPU interrupt test failed. Replace midplane.
MESSAGE 28
POST SRAM Test <error> <code>.
3PAR Confidential
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 <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. I2C failed to onboard device. Replace midplane.
MESSAGE 30
POST FPGA Test <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. FPGA stress test failed. Replace midplane.
MESSAGE 31
POST ADC Init <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. CPU voltage sampler initialization failed. Replace midplane.
MESSAGE 32
POST Poweron Hours Init <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. Midplane power on time could not be read. Replace
midplane.
MESSAGE 33
POST Midplane Init <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. Midplane type could not be determined.
Replace midplane.
MESSAGE 34
POST Midplane EEPROM Test <error> <code>.
12.873PAR Confidential
12.88
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 <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. Midplane LM87 temperature sensor failed. Replace
midplane.
MESSAGE 36
POST Flash Test <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. Code 0: midplane CPU flash failed testing. Replace
midplane.
MESSAGE 37
POST Flash Test <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. Code 1: midplane flash failed testing. Replace midplane.
MESSAGE 38
POST FCAL Init <error> <code>.
SUGGESTED ACTION
FCAL failed to initialize. Replace FCAL.
MESSAGE 39
POST FCAL EEPROM Test <error> <code>.
SUGGESTED ACTION
FCAL EEPROM failed during functional test. Replace FCAL.
MESSAGE 40
POST Power Supply Init <error> <code>.
3PAR Confidential
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 <error> <code>.
SUGGESTED ACTION
Power supply failed during functional test. Replace Power Supply.
MESSAGE 42
POST Power Supply EEPROM Test <error> <code>.
SUGGESTED ACTION
Power supply EEPROM failed during functional test. Replace Power Supply.
MESSAGE 43
POST Power Supply Test <error> <code>.
SUGGESTED ACTION
Power supply failed during functional test. Replace Power Supply.
MESSAGE 44
POST ESI Test <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. ESI channel failed to initialize. Replace midplane.
MESSAGE 45
POST ESI Init <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. ESI channel failed to initialize. Replace midplane.
MESSAGE 46
POST PMC Alive Test <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. ESI channel failed to initialize. Replace midplane.
12.893PAR Confidential
12.90
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE 47
POST PMC Loopback Test <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. PMC switch chip failed POST internal loopback. Replace
midplane.
MESSAGE 48
POST PMC Interchip Test <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. PMC switch chip failed interchip test. Replace midplane (or
possibly FCAL).
MESSAGE 49
POST SFP Test <error> <code>.
SUGGESTED ACTION
FCAL SFP failed functional test. Code 0x01: replace FCAL0. Code 0x02: replace FCAL1. Code
0x12: replace FCAL1 SFP0. Code 0x22: replace FCAL1 SFP1.
MESSAGE 50
POST Disk Loopback Test <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. PMC switch chip failed disk loopback functional test.
Replace midplane (try reseating loopback magazines first).
MESSAGE 51
POST Scheduler Init <error> <code>.
SUGGESTED ACTION
Internal midplane hardware error. Scheduler initialization failed. Reload cage firmware. If
error persists, replace midplane.
MESSAGE 52
Midplane LM87 read failure
3PAR Confidential
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 (<code>)
SUGGESTED ACTION
Midplane voltage sensor reports low voltage. Replace power supplies. If error persists, replace
midplane.
MESSAGE 54
Midplane LM87 voltage/temperature over limit (<code>)
SUGGESTED ACTION
Midplane voltage sensor reports high voltage. Replace power supplies. If error persists, replace
midplane.
MESSAGE 55
Midplane LM87 start failure
SUGGESTED ACTION
Internal midplane hardware error. Power cycle cage. If error persists, replace midplane.
MESSAGE 56
Firmware panic due to <reason>.Panic count is <count> (<code>)
SUGGESTED ACTION
Midplane hardware or software error. If you receive this message, then the cage completed
self-recovery. If error persists, replace midplane. If a cage firmware core dump is available, a
separate message code 0x1e0005 will also be present. A cage firmware core dump can be
analyzed by your service provider.
12.913PAR Confidential
12.92
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x1e0002
TYPE
Invalid cage configuration
MESSAGE 1
Cage <cage_id> (WWN <cage_wwn>) is not directly attached to node on either loop.
MESSAGE 2
Cage <cage_id> (WWN <cage_wwn>) is paired with different partners. SideA with <cage_name> and sideB with <cage_name>.
MESSAGE 3
Can’t tell cage order on port <node:port:slot>.
MESSAGE 4
More than 2 cages reported port <node:port:slot>.
MESSAGE 5
<cage_id> reported twice on port <node:port:slot>. This means that both loops of this cage are daisy chained together.
MESSAGE 6
<port_number> of <cage_id> on both ports <node:port:slot> and <node:port:slot>.
MESSAGE 7
DC2 <cage_name> in daisy chain config with <cage_name> on port <node:port:slot>.
MESSAGE 8
<cage_name> in daisy chain config with <cage_name> on port <node:port:slot>. Mixed cage
types are not allowed in daisy chain configuration.
SUGGESTED ACTION FOR MESSAGE 1-8
Check all fibre channel cable connections. Contact your local service provider to reconfigure
the drive cages.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x1e0004
TYPE
Critical ESI port count in cage
MESSAGE 1
<cage_name> is connected but is down to one valid ESI port.
MESSAGE 2
<cage_name> is connected but has only one valid ESI port.
MESSAGE 3
Lost communication to cage <cage_name> on all ESI ports.
SUGGESTED ACTION FOR MESSAGE 1-3
Inspect the current cage hardware configuration and insert more ESI-capable magazines.
NOTE: Messages 1 and 3 are logged when the system is coming up as well as
when losing valid ESI ports. As more ESI ports are validated, Message 2 is
displayed and an AUTOFIX message, Message 4, is logged when two or more ESI
ports are available.
12.933PAR Confidential
12.94
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x1e0005
TYPE
Cage firmware coredump event
MESSAGE
Cage COREDUMP: recovered file <file_name>
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.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x1e00de
TYPE
Component State Change
MESSAGE
Cage <ID> Degraded (<list of states>)
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.
STATE 8
Single Loop
SUGGESTED ACTION
One of the FCAL modules is off line. Use the CLI command showcage <cage_name> to
confirm the loop is unavailable. Contact your local service provider for technical support and
services.
12.953PAR Confidential
12.96
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 <cage_name> 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. Contact
your local service provider for technical support and services.
Validate the alert by running CLI command showpd -degraded and showpd -failed. If ESI
PDs are intentionally off line, reconnect them. Replace PDs if they are failing.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x1e00fa
TYPE
Component State Change
MESSAGE
Cage <ID> Failed (<list of states>)
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.
STATE 7
Double Loops Down
SUGGESTED ACTION
Both of the FCAL modules are off line. Check if the cables are properly seated. Use CLI
command showcage <cage_name> to confirm the loop is unavailable. Contact your local
service provider for additional analysis on the cage ports.
STATE 8
No ESI Port
12.973PAR Confidential
12.98
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 <cage_name> 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.
STATE 10
Node Offline Due to Failure
SUGGESTED ACTION
If the node doesn't come back up within 1 hour, contact 3PAR technical support.
STATE 11
Node Shutdown Manually
SUGGESTED ACTION
If the node doesn't come back up after maintenance has been completed, contact 3PAR
technical support.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x1f0001
TYPE
Disk overtemp
MESSAGE
Disk <disk_id> (wwn <wwn_number>) is overtemp (<degrees_celcius> 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.993PAR Confidential
12.10
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x1f000de
TYPE
Component state change
MESSAGE
Disk <wwn_id> Degraded (<list of states>)
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 <pd_id> to confirm the disk is still in this state. If both ports
are reporting errors, then another alert is posted specifying No Valid Ports on that disk.
STATE 2
Errors on B 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 <pd_id> to confirm the disk is still in this state. If both ports
are reporting errors, then another alert is posted specifying No Valid Ports on that disk.
STATE 3
Disabled A Port
SUGGESTED ACTION
The PD specified in the alert has one of its ports marked as disabled.
If this is not because of a service action, please contact your local service provider for further
information.
STATE 4
Disabled B Port
SUGGESTED ACTION
The PD specified in the alert has one of its ports marked as disabled.
3PAR Confidential
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 <pd_id> to confirm the disk is still in this state.
This state might be temporary and might fix itself on retries. If the error persists, contact your
local service provider for technical support and services.
STATE 6
Missing
SUGGESTED ACTION
The PD specified in the alert has been missing on both ports. Use the CLI command showpd <pd_id> to confirm the disk is still in this state.
This state might be temporary and might fix itself on retries. If the error persists, contact your
local service provider for technical support and services.
STATE 7
Missing A Port
SUGGESTED ACTION
The PD specified in the alert has its A port missing. Use the CLI showpd <pd_id> to confirm it
is still in this state.
If the disk has disappeared from the A loop, it reports its A 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 8
Missing B Port
SUGGESTED ACTION
The PD specified in the alert has its B port missing. Use the CLI showpd <pd_id> to confirm it
is still in this state.
12.103PAR Confidential
12.10
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.
The relocations could be because of an active service operation or because of intermittent
disturbances. No further action is required.
STATE 10
Servicing
SUGGESTED ACTION
This is a disk activity flag indicating the disk is being serviced. This flag will be set if a
servicemag or a servicecage operation is active on the disk.
STATE 11
Prolonged Missing A Port
SUGGESTED ACTION
Port A is missing for over 20 minutes. Check if the PD port is missing by issuing CLI command
showpd and showcage -d. If only one port is missing, the PD may need to be replaced.
Contact your local service provider for technical support and services.
STATE 12
Prolonged Missing B Port
SUGGESTED ACTION
Port B is missing for over 20 minutes. Check if the PD port is missing by issuing CLI command
showpd and showcage -d. If only one port is missing, the PD may need to be replaced.
Contact your local service provider for technical support and services.
STATE 13
Cage State Missing
3PAR Confidential
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.
STATE 17
Fail To Spinup
SUGGESTED ACTION
The PD is experiencing problems spinning up. If this continues, a new failure alert will be
issued with further actions to be taken.
STATE 18
Loop Failure
SUGGESTED ACTION
The PD loop connection may have failed. No action required.
STATE 19
Drive Error Bit Set
12.103PAR Confidential
12.10
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.
STATE 23
Sysmgr Spundown
SUGGESTED ACTION
The Sysmgr has issued a command for a PD to be spundown. No action required.
STATE 24
Critical Over Temp
SUGGESTED ACTION
Temperature of the PD has reached the threshold maximum. Check for fan failure and
ventilation obstructions.
STATE 25
Spundown Requested Drive Ready
3PAR Confidential
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.103PAR Confidential
12.10
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x1f000fa
TYPE
Component state change
MESSAGE
Disk <wwn_id> Failed (<list of states>)
STATE 1
Invalid
SUGGESTED ACTION
The PD specified in the alert has been marked failed. Use the CLI command showpd <pd_id>
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.
If there is no reason code associated with this, contact your local service provider for technical
support and services.
STATE 2
Inquiry Failed
SUGGESTED ACTION
The PD specified in the alert has been marked failed because a SCSI inquiry to it failed. Use the
CLI command showpd <pd_id> to confirm the disk is still in this state.
A disk is marked failed because a SCSI inquiry to it failed to gather information about its serial
number, device ID, vendor ID, etc. Generally this alert is auto-fixed when the SCSI inquiry is
retried.
Wait for a few minutes to see if the alert is auto-fixed. If that does not happen, contact your
local service provider for a possible disk replacement.
STATE 3
Unit Ready Failed
3PAR Confidential
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 <pd_id> 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.
STATE 4
Read Capacity Failed
SUGGESTED ACTION
The PD specified in the alert has been marked failed because a command sent to read its
capacity has failed. Use the CLI command showpd <pd_id> to confirm the disk is still in this
state.
A disk is marked failed if a SCSI inquiry to check its capacity fails. This error is also intermittent
and might get fixed if the SCSI inquiry succeeds on a retry. As above, the suggested action is to
wait for a few minutes for the retry to fix it. If not, contact your local service provider for a
possible disk replacement.
STATE 5
Write Label Failed
SUGGESTED ACTION
The PD specified in the alert has been marked failed because the disk label could not be
written to the disk. Use the CLI command showpd <pd_id> to confirm the disk is still in this
state.
If the error is persistent, contact your local service provider for possible disk replacement.
STATE 6
Mod Page Update Failed
SUGGESTED ACTION
The PD specified in the alert has been marked failed because its mod pages could not be
updated. Use the CLI command showpd <pd_id> to confirm the disk is still in this state.
If the error is persistent, contact your local service provider for possible disk replacement.
12.103PAR Confidential
12.10
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 <pd_id> to confirm the disk is still in this state.
If the error is persistent, contact your local service provider for possible disk replacement.
STATE 8
Invalid Label
SUGGESTED ACTION
The PD specified in the alert has been marked failed because the disk label read from the disk
cannot be validated. Use the CLI command showpd <pd_id> to confirm the disk is still in this
state.
If the error is persistent, contact your local service provider for possible disk replacement.
STATE 9
Invalid Capacity
SUGGESTED ACTION
The PD specified in the alert has been marked failed because the capacity of
the disk read by a SCSI inquiry is different from the matching entry in a list of supported values.
Use the CLI command showpd <pd_id> to confirm the disk is still in this state.
Contact your local service provider for possible disk replacement.
STATE 10
Invalid Type
SUGGESTED ACTION
The PD specified in the alert has been marked failed because the vendor of the disk is not
included in the list of supported vendors. Use the CLI command showpd <pd_id> to confirm
the disk is still in this state.
Contact your local service provider for possible disk replacement.
STATE 11
Invalid Firmware
3PAR Confidential
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 <pd_id> 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. Use the CLI command showpd <pd_id> to confirm the disk is still in this state.
Contact your local service provider for possible disk replacement.
STATE 13
Invalid Cage
SUGGESTED ACTION
The PD specified in the alert has been marked temporarily failed because it does not have a
known cage position. Use the CLI command showpd <pd_id> to confirm the disk is still in this
state.
If the error persists, contact your local service provider for possible disk replacement.
STATE 14
Prolonged Not Ready
SUGGESTED ACTION
The PD specified in the alert has been marked failed because it has been marked not ready for
more than 20 minutes. Use the CLI command showpd <pd_id> to confirm the disk is still in
this state.
Contact your local service provider for possible disk replacement.
STATE 15
Prolonged Missing
12.103PAR Confidential
12.11
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 <pd_id> 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. Use the CLI command showpd <pd_id> to confirm the disk is still in this state.
A disk might be marked failed because the media on certain sectors is marked bad. Other
reason codes below might help in further analysis of why the disk has its media marked invalid.
STATE 17
Failed Hardware
SUGGESTED ACTION
A disk might be marked media-failed because the hardware reports media failures. Contact
your local service provider to replace the disk.
STATE 18
Smart Threshold Exceeded
SUGGESTED ACTION
A disk might be marked media-failed if it has been reporting disk aborts with error code 21 to
specify that the threshold for SMART errors has been exceeded.
Contact your local service provider to replace the disk.
STATE 19
Multiple Chunklets Media Bad
SUGGESTED ACTION
A disk might be marked media-failed because more than six chunklets on that disk have
reported media-errors.
Contact your local service provider to replace the disk.
3PAR Confidential
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.
STATE 22
No Valid Ports
SUGGESTED ACTION
The PD specified in the alert has been failed because it has no valid ports. Use the CLI
command showpd <pd_id> to confirm the disk is still in this state.
Contact your local service provider for technical support and services.
12.113PAR Confidential
12.11
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 <IPaddr> port <port>
SUGGESTED ACTION
Contact your local service provider for technical support and services.
3PAR Confidential
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.113PAR Confidential
12.11
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x220001
TYPE
Battery expiration
MESSAGE 1
Node <node_id> PS <power_supply_id> Battery <battery_id> will expire in 30 days [Replace Battery soon]
SUGGESTED ACTION
1 Check the system time.
2 Check the battery expiration date.
3 Contact your local service provider to schedule the battery replacement.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x2200de
TYPE
Component state change
MESSAGE
Node <node_id> Power Supply <power_supply_id> Battery <battery_id> Degraded (<list of states>)
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.113PAR Confidential
12.11
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x2200fa
TYPE
Component state change
MESSAGE
Node <node_id> Power Supply <power_supply_id> Battery <battery_id> Failed (<list of states>)
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.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x230003
TYPE
Port shutdown on fatal error
MESSAGE
Port <port_id> shut down: <time_shutdown>
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
2 Ensure the device connected on the port is functioning correctly. Perhaps by power-cycling
the device and issuing controlport rst n:s:p to reset the port and see if the new port
now functions correctly.
3 Verify that the problem is not port-specific by swapping the cable with a known working
port.
4 If the problem persists, contact your local service provider.
NOTE: This will reset the port. If the port continues to generate firmware cores, it
will shut down again and the alert reposted.
12.113PAR Confidential
12.11
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x230004
TYPE
Host port is down
MESSAGE
Host port (<node>:<slot>:<port>) is down (<reason>)
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.
3PAR Confidential
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.113PAR Confidential
12.12
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x240001
TYPE
Internodal serial port error
MESSAGE
Node <node_id> Serial Port <serial_port_id> Error: <error_number> <error_description>
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.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x250002
TYPE
Remote Copy link status
MESSAGE
The Remote Copy link <remote_copy_link_process_name> 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. In the latter case, the customer should attempt to determine what caused the
network failure and attempt to correct the situation.
12.123PAR Confidential
12.12
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x270001
TYPE
TP VV allocation size warning
MESSAGE
Thin provisioned VV <name> 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. Check the configured ‘Allocation Limit’ for the named
TPVV, and determine if it needs to be set at a higher percentage of its exported virtual size.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x270002
TYPE
TP VV allocation size limit
MESSAGE
Thin provisioned VV <name> 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.123PAR Confidential
12.12
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 <name> 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. Check the configured ‘Allocation Limit’ for the
Snapshot space for the named VV, and determine if it needs to be set at a higher value.
3PAR Confidential
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 <name> 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.
To allow the Snapshot space for the named VV to continue to auto-grow, reset its ‘Allocation
Limit’ to a greater value.
12.123PAR Confidential
12.12
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x270005
TYPE
CPG growth warning
MESSAGE 1
CPG <cpg name> <SA/SD> space has reached allocation warning of <number>G.
SUGGESTED ACTION
The logical capacity reserved and in use by the named Common Provisioning Group (CPG) is
above the configured allocation warning. If the named CPG reaches its allocation limit and all
of its reserved space is in use, new writes on TPVVs and/or Snapshot Volumes mapped to this
CPG will result in write failures. Check the configured ‘Allocation Limit’ for the named CPG,
and determine if it needs to be set at a higher limit.
MESSAGE 2
CPG <cpg name> SA space past allocation warning of <number>G.
SUGGESTED ACTION
The logical capacity reserved and in use by the named Common Provisioning Group (CPG) is
above the configured allocation warning. If the named CPG reaches its allocation limit and all
of its reserved space is in use, new writes on TPVVs and/or Snapshot Volumes mapped to this
CPG will result in write failures. Check the configured ‘Allocation Limit’ for the named CPG,
and determine if it needs to be set at a higher limit.
NOTE: There are times when a single allocation results in both the warning and
the limit being hit at the same time. In this case, only the most severe alert is
posted, the limit. For example, if you create a single VV that takes you from <50%
used, to >95% used, only the 95% used alert is generated.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x270006
TYPE
CPG growth limit
MESSAGE 1
CPG <cpg name> 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. Also, check that sufficient capacity is available to accommodate CPG auto-LD creation. This can be verified by executing the showspace command with the -cpg <cpg name> option, which will take into account the specific LD characteristics associated with the CPG when determining the available capacity. If effective available capacity is running low, contact your service provider to purchase and install additional capacity.
MESSAGE 2
CPG <cpg name> SA space past 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. Also, check that sufficient capacity is available to
accommodate CPG auto-LD creation. This can be verified by executing the showspace command with the -cpg <cpg name> option, which will take into account the specific LD
characteristics associated with the CPG when determining the available capacity. If effective
available capacity is running low, contact your service provider to purchase and install
additional capacity.
NOTE: There are times when a single allocation results in both the warning and
the limit being hit at the same time. In this case, only the most severe alert is
posted, the limit. For example, if you create a single VV that takes you from <50%
used, to >95% used, only the 95% used alert is generated.
12.123PAR Confidential
12.12
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x270007
TYPE
TP VV allocation failure
MESSAGE 1
Thin provisioned VV <name> unable to allocate SA space from CPG <cpg name>
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.
MESSAGE 2
Thin provisioned VV <name> unable to allocate SD space from CPG <cpg name>
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.
3PAR Confidential
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 <VV name> unable to allocate SA space from CPG <cpg name>
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.
MESSAGE 2
Snapshot space for VV <VV name> unable to allocate SD space from CPG <cpg name>
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.
12.123PAR Confidential
12.13
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x270009
TYPE
CPG growth failure
MESSAGE 1
CPG <cpg name> SA grow command: createald -args-paramsFailed with: <error string>
SUGGESTED ACTION
The specific LD creation command and failure text must be examined to determine the
corrective action. This might include replacing failed hardware or adding additional storage.
Contact your local service provider for technical support and services for further assistance.
MESSAGE 2
CPG <cpg name> SD grow command: createald -args-paramsFailed with: <error string>
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.
NOTE: There are times when a single allocation results in both the warning and
the limit being hit at the same time. In this case, only the most severe alert is
posted, the limit. For example, if you create a single VV that takes you from <50%
used, to >95% used, only the 95% used alert is generated.
3PAR Confidential
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. Contact your local service provider for technical
support and services to order capacity upgrade.
NOTE: Raw space usage indicated by this alert may not apply to available physical
space required for CPG auto-LD creation for CPGs with customized LD
characteristics. Available space for such CPGs may be limited to a subset of total
available space in the system, and may become fully used even while available
capacity exists which may not adhere to the LD characteristics for the CPG.
NOTE: There are times when a single allocation results in both the warning and
the limit being hit at the same time. In this case, only the most severe alert is
posted, the limit. For example, if you create a single VV that takes you from <50%
used, to >95% used, only the 95% used alert is generated.
12.133PAR Confidential
12.13
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. If, available space runs out, new
writes on all virtual volumes will result in write failures. Contact your local service provider for
technical support and services to order capacity upgrade.
NOTE: Raw space usage indicated by this alert may not apply to available physical
space required for CPG auto-LD creation for CPGs with customized LD
characteristics. Available space for such CPGs may be limited to a subset of total
available space in the system, and may become fully used even while available
capacity exists. This may not adhere to the LD characteristics for the CPG.
NOTE: There are times when a single allocation results in both the warning and
the limit being hit at the same time. In this case, only the most severe alert is
posted, the limit. For example, if you create a single VV that takes you from <50%
used, to >95% used, only the 95% used alert is generated.
3PAR Confidential
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. If there is no remaining available physical space,
new writes on all virtual volumes will result in write failures. Contact your local service provider
for technical support and services to order capacity upgrade and schedule installation.
NOTE: Raw space usage indicated by this alert may not apply to available physical
space required for CPG auto-LD creation for CPGs with customized LD
characteristics. Available space for such CPGs may be limited to a subset of total
available space in the system, and may become fully used even while available
capacity exists. This may not adhere to the LD characteristics for the CPG.
NOTE: There are times when a single allocation results in both the warning and
the limit being hit at the same time. In this case, only the most severe alert is
posted, the limit. For example, if you create a single VV that takes you from <50%
used, to >95% used, only the 95% used alert is generated.
12.133PAR Confidential
12.13
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.
NOTE: Raw space usage indicated by this alert may not apply to available physical
space required for CPG auto-LD creation for CPGs with customized LD
characteristics. Available space for such CPGs may be limited to a subset of total
available space in the system, and may become fully used even while available
capacity exists which may not adhere to the LD characteristics for the CPG.
NOTE: There are times when a single allocation results in both the warning and
the limit being hit at the same time. In this case, only the most severe alert is
posted, the limit. For example, if you create a single VV that takes you from <50%
used, to >95% used, only the 95% used alert is generated.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x270012
TYPE
CPG space used status
MESSAGE
CPG <cpg_name> <SA/SD> space over <percentage_number>% used (<amount of space used>G used out of <total_amount_of_space_available> 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.
■ Examine the VVs in the CPG to see if any of the applications using those VVs are consuming
more storage than expected.
12.133PAR Confidential
12.13
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 <new value>.
3PAR Confidential
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. Contact your local service provider for technical
support and services to order capacity upgrade.
NOTE: Raw space usage indicated by this alert may not apply to available physical
space required for CPG auto-LD creation for CPGs with customized LD
characteristics. Available space for such CPGs may be limited to a subset of total
available space in the system, and may become fully used even while available
capacity exists which may not adhere to the LD characteristics for the CPG.
NOTE: There are times when a single allocation results in both the warning and
the limit being hit at the same time. In this case, only the most severe alert is
posted, the limit. For example, if you create a single VV that takes you from <50%
used, to >95% used, only the 95% used alert is generated.
12.133PAR Confidential
12.13
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. If, available space runs out, new
writes on all virtual volumes will result in write failures. Contact your local service provider for
technical support and services to order capacity upgrade.
NOTE: Raw space usage indicated by this alert may not apply to available physical
space required for CPG auto-LD creation for CPGs with customized LD
characteristics. Available space for such CPGs may be limited to a subset of total
available space in the system, and may become fully used even while available
capacity exists. This may not adhere to the LD characteristics for the CPG.
NOTE: There are times when a single allocation results in both the warning and
the limit being hit at the same time. In this case, only the most severe alert is
posted, the limit. For example, if you create a single VV that takes you from <50%
used, to >95% used, only the 95% used alert is generated.
3PAR Confidential
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. If there is no remaining available physical space,
new writes on all virtual volumes will result in write failures. Contact your local service provider
for technical support and services to order capacity upgrade and schedule installation.
NOTE: Raw space usage indicated by this alert may not apply to available physical
space required for CPG auto-LD creation for CPGs with customized LD
characteristics. Available space for such CPGs may be limited to a subset of total
available space in the system, and may become fully used even while available
capacity exists. This may not adhere to the LD characteristics for the CPG.
NOTE: There are times when a single allocation results in both the warning and
the limit being hit at the same time. In this case, only the most severe alert is
posted, the limit. For example, if you create a single VV that takes you from <50%
used, to >95% used, only the 95% used alert is generated.
12.133PAR Confidential
12.14
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.
NOTE: Raw space usage indicated by this alert may not apply to available physical
space required for CPG auto-LD creation for CPGs with customized LD
characteristics. Available space for such CPGs may be limited to a subset of total
available space in the system, and may become fully used even while available
capacity exists which may not adhere to the LD characteristics for the CPG.
NOTE: There are times when a single allocation results in both the warning and
the limit being hit at the same time. In this case, only the most severe alert is
posted, the limit. For example, if you create a single VV that takes you from <50%
used, to >95% used, only the 95% used alert is generated.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x270050
TYPE
CPG space used status
MESSAGE
CPG <cpgname> <SA or SD> space has reached allocation <limit or warning> of <allocated_space>
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.143PAR Confidential
12.14
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. Contact your local
service provider for technical support and services.
3PAR Confidential
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. If all the LDs are
in the started state, contact your local service provider for technical support and services.
12.143PAR Confidential
12.14
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x2900de
TYPE
Component State Change
MESSAGE
Cage <cage_name> Interface Card <ifc_id> SFP <sfp_id> Degraded (<list of states>)
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. Check the Fibre Channel cables and SFP to ensure they are
properly inserted. Contact your local service provider for technical support and services.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x2b00de
TYPE
Component State Change
MESSAGE
Cage <cage_name> Power Supply <power_supply_id> Degraded (<list of states>)
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.143PAR Confidential
12.14
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x2b00fa
TYPE
Component State Change
MESSAGE
Cage <cage_name> Power Supply <power_supply_id> Failed (<list of states>)
STATE 1
Power Supply Failed
SUGGESTED ACTION
The cage power supply identified may need replacement. Contact your local service provider
for technical support and services.
STATE 2
Power Supply Warning
SUGGESTED ACTION
The cage power supply identified may need replacement. Contact your local service provider
for technical support and services.
STATE 3
Power Supply Comm_Err
SUGGESTED ACTION
The cage power supply identified may need replacement. Contact your local service provider
for technical support and services.
STATE 4
Power Supply Not_Present
SUGGESTED ACTION
Check if the power supply is properly inserted. If the condition persists, replace the power
supply. Contact your local service provider for technical support and services.
3PAR Confidential
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.
STATE 7
Fan Warning
SUGGESTED ACTION
The cage power supply identified may need replacement. Contact your local service provider
for technical support and services.
STATE 8
Fan Comm_Err
SUGGESTED ACTION
The cage power supply identified may need replacement. Contact your local service provider
for technical support and services.
STATE 9
Fan Not_Present
SUGGESTED ACTION
The cage power supply identified may need replacement. Contact your local service provider
for technical support and services.
STATE 10
Fan Not_Available
12.143PAR Confidential
12.14
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. If there is multiple power supply
failure, check PDU. Contact your local service provider for technical support and services.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x2d00de
TYPE
Component state change
MESSAGE
Cage <cage_name> FCAL Module <FCAL_id> Degraded (<list of states>)
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. Use CLI command admithw or upgradecage
to upgrade cage firmware.
STATE 3
Firmware for CPU B 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. Use CLI command admithw or upgradecage
to upgrade cage firmware.
STATE 4
FCAL Module Not Responding
SUGGESTED ACTION
The condition should be temporary and should resolve itself. Use CLI command showcage and
showpd to confirm a degraded FCAL.
12.143PAR Confidential
12.15
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.
STATE 7
Firmware for CPU B Unknown
SUGGESTED ACTION
Use CLI command showcage and showpd to confirm condition. Contact your local service
provider for technical support and services.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x2d00fa
TYPE
Component state change
MESSAGE
Cage <cage_name> Interface Card <interface_card_id> Failed (<list of states>)
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.153PAR Confidential
12.15
Messages and Operator’s Guide InForm OS Version 2.3.1
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.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x3500de
TYPE
Component state change
MESSAGE
Cage <cage_name> Magazine <mag_id> Degraded (<list of states>)
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.153PAR Confidential
12.15
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x3500fa
TYPE
Component State Change
MESSAGE
Cage <cage_name> Magazine <mag_id> Failed (<list of states>)
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.
Use CLI command showpd -degraded and showpd -failed to verify disk failure.
STATE 3
Serial Console Issued Bypass
SUGGESTED ACTION
A bypass was issued from the cage serial console. Undo the bypass of the drive magazine using
the controlmag command.
STATE 4
Midplane I2C Transaction Failure
SUGGESTED ACTION
Communication between I2C to cage magazine is down. Check and confirm problem and
replace the drive magazine.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x3700de
TYPE
Component state change
MESSAGE
Remote Copy Volume <remote_copy_volume_id> <volume_name> Degraded (<list of states>)
STATE 1
Resync Snapshot Became Stale - Full Sync Required
SUGGESTED ACTION
Indicates that a remote copy snapshot went stale and was deleted and the next
synchronization will have to be a full synchronization. Determine what caused the snapshot to
go stale and possibly grow snapshot space for the base volume.
STATE 2
Volume Group Unsync; Did Not Take Snapshots While Stopping Group
SUGGESTED ACTION
Check to ensure that all volumes in the group can have snapshots taken, i.e. they have used
snapshot space and are not experiencing some other error that would prevent snapshots.
STATE 3
Volume Unsync; Secondary Volume Was Not Marked as In-Sync
SUGGESTED ACTION
Something stopped the group on the secondary system. This could have been the result of
stopcopygroup being run there (if configuration mirroring is off), stopcopy being
executed, the system shutting down, etc. Determine what caused the secondary to stop. Once
that is resolved restart the group on the primary.
STATE 4
Volume Unsync; Volume Was Unavailable When Group Was Stopped
12.153PAR Confidential
12.15
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.
STATE 6
Volume Unsync; Promote of Snapshot Failed
SUGGESTED ACTION
Indicates that some volumes are no longer in sync because promote of snapshot failed.
Determine why this is and resolve the situation, then perform a resynchronization.
STATE 7
Volume Unsync; Could Not Take Snapshot During Sysmgr Startup
SUGGESTED ACTION
Indicates that some volumes are no longer in sync because could not take snapshot during
sysmgr startup. Determine why this is and resolve the situation, then perform a
resynchronization.
STATE 8
Volume Requires a Full Resync Since LDCK is in Progress
SUGGESTED ACTION
Indicates that some volumes are no longer in sync because ldck is in progress.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x3700fa
TYPE
Component state change
MESSAGE
Remote Copy Volume <remote_copy_volume_id> <volume_name> Failed (<list of states>)
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.
STATE 2
Sync Failed
SUGGESTED ACTION
Indicates an attempt to synchronize a remote copy volume has failed. Try and determine why
this occurred, i.e. volume group was stopped by a CLI command, there was a network failure, a
write error on the secondary volume, etc., and correct the problem. Once the problem is
resolved, the volume can be synchronized using syncrcopy.
12.153PAR Confidential
12.15
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x3800de
TYPE
Component state change
MESSAGE
Remote Copy Volume Group <remote_copy_group_id> <group_name> Degraded (<list of states>)
STATE 1
Sync Failed: Could Not Take Local Snapshots
SUGGESTED ACTION
Check to ensure that all volumes in the group can have local snapshots taken, i.e. they have
used snapshot space and are not experiencing some other error that would prevent snapshots.
STATE 2
Sync Failed; Could Not Take Remote Snapshots
SUGGESTED ACTION
Check to ensure all volumes in the group can have remote snapshots taken, i.e. they have used
snapshot space and are not experiencing some other error that would prevent snapshots.
STATE 3
Sync Failed; Could Not Communicate With Target
SUGGESTED ACTION
Check to ensure that the target is up and running, then retry the command.
STATE 4
Sync Failed; Synchronization Snapshot Has Been Deleted
SUGGESTED ACTION
Check to see whether the synchronization snapshot has been deleted.
STATE 5
Resync Failed; Resynchronization Snapshot Has Been Deleted
3PAR Confidential
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. If it is a link problem, try to fix the link problem, otherwise the resync period may need to
be reset.
STATE 8
Sync Failed In-Sync
SUGGESTED ACTION
Contact your local service provider for technical support and services.
12.153PAR Confidential
12.16
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x3900fa
TYPE
Component state change
MESSAGE
Remote Copy Target <target_id> <target_name> Degraded (<list of states>)
STATE 1
Target At Incompatible Revision
SUGGESTED ACTION
The primary and secondary systems do not have the same software versions. They should be
updated to the same level or compatible levels.
STATE 2
All Links To Target Are Down
SUGGESTED ACTION
Determine the reason the connectivity was lost and correct the problem.
STATE 3
All Links To Target Are Down
SUGGESTED ACTION
Determine the reason the connectivity was lost and correct the problem.
STATE 4
All Links To Target Are Down
SUGGESTED ACTION
Determine the reason the connectivity was lost and correct the problem.
STATE 5
All Links To Target Are Down
SUGGESTED ACTION
Determine the reason the connectivity was lost and correct the problem.
3PAR Confidential
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. Check the system
and remove one target and the groups in the target.
12.163PAR Confidential
12.16
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x3a00de
TYPE
Component state change
MESSAGE
Remote Copy Link <remote_copy_link:link_id> <sysmgr_name> Degraded (<list of states>)
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.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x3a00fa
TYPE
Component state change
MESSAGE
Remote Copy Link <remote_copy_link:link_id> <sysmgr_name> Failed (<list of states>)
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. In the latter case, the customer should attempt to determine what caused the
network failure and attempt to correct the situation.
STATE 2
Multiple link down errors within 24 hours
SUGGESTED ACTION
Check your physical link connection. Issue a CLI command showrcopy -links to verify the
link is down. Contact your local service provider for technical support and services.
STATE 3
Link has been down for more than 4 hours
SUGGESTED ACTION
Check your physical link connection. Issue a CLI command showrcopy -links to verify the
link is down. Contact your local service provider for technical support and services.
12.163PAR Confidential
12.16
Messages and Operator’s Guide InForm OS Version 2.3.1
MESSAGE CODE
0x450001
TYPE
Data Cache DIMM CECC Monitoring
MESSAGE
Node <Node_ID> Data Cache <DIMM_ID>: Correctable ECC limit exceeded
STATE 1
New
SUGGESTED ACTION
Contact your local service provider to have the DIMM replaced as soon as possible.
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
MESSAGE CODE
0x460001
TYPE
Control Cache DIMM CECC Monitoring
MESSAGE
Node <Node_ID> <DIMM_ID>: Correctable ECC limit exceeded
STATE 1
New
SUGGESTED ACTION
Contact your local service provider to have the DIMM replaced as soon as possible.
12.163PAR Confidential
12.16
Messages and Operator’s Guide InForm OS Version 2.3.1
3PAR Confidential
InForm OS Version 2.3.1 ____________Messages and Operator’s Guide
AAgency 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.16
This appendix contains safety precautions and agency compliance notices for InServ Storage
Servers and their components. Read this section before beginning any of the procedures
described in this guide.
A.1Agency Compliance Statements
3PAR Confidential
A.2
Messages and Operator’s Guide InForm OS Version 2.3.1
A.1 Safety PrecautionsFor 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.
In addition, please take the following precautions:
■ Install and maintain storage servers and their components in a restricted access location,
limiting access to storage server equipment, software, and documentation.
■ Follow all instructions, warnings, and cautions printed on individual storage server
components. Those instructions take precedence over statements made in this guide.
■ Before installing a storage server, verify that the voltage and frequency of the power
sources at the operating sites matches the voltage and frequency indicated on the system’s
electrical rating label.
A.2 Safety Agency Compliance NoticesInServ Storage Servers comply with UL® 1950 and IEC 60950 safety standards for ITE
equipment. requirements. For your safety, observe the notices that follow.
A.2.1 System Placement and Security
Install and maintain storage servers and their components in a restricted access location,
limiting access to storage server equipment, software, and documentation.
WARNING: Install the unit in a restricted access location.
ACHTUNG: Diese Einheit darf nicht frei zugänglich installiert werden.
Safety Precautions
3PAR Confidential
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.
A.3Safety Agency Compliance Notices
3PAR Confidential
A.4
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.
WAARSCHUWING: Achter de toegangsdeur van de opslagserverkast aan de
achterzijde ontstaat gevaarlijke energie.
ADVERTENCIA: Energía peligrosa esta localizada detrás de la puerta de acceso
trasera del gabinete del servidor de almacenamiento.
Safety Agency Compliance Notices
3PAR Confidential
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.
ACHTUNG: Bei unsachgemäßem Austausch der Lithium-Knopfbatterie im
Steuerknoten besteht Explosionsgefahr. Die Knopfbatterie darf nur durch eine
gleiche bzw. vom Hersteller empfohlene gleichwertige Batterie ersetzt werden.
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. Vervang de muntbatterij
alleen door een type dat equivalent is aan het type dat door de fabrikant wordt
aanbevolen.
A.5Safety Agency Compliance Notices
3PAR Confidential
A.6
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.
Safety Agency Compliance Notices
3PAR Confidential
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.
A.7Safety Agency Compliance Notices
3PAR Confidential
A.8
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.
ADVERTENCIA: Está unidad deberá ser instalada en una área de acceso
restringido.
Safety Agency Compliance Notices
3PAR Confidential
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.
A.9Safety Agency Compliance Notices
3PAR Confidential
A.10
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. vom Hersteller empfohlene gleichwertige Batterie ersetzt werden.
Safety Agency Compliance Notices
3PAR Confidential
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. Vervang de muntbatterij
alleen 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 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.
A.11Safety Agency Compliance Notices
3PAR Confidential
A.12
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.
Safety Agency Compliance Notices
3PAR Confidential
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.
ADVERTENCIA: Está unidad deberá ser instalada en una área de acceso
restringido.
A.13Safety Agency Compliance Notices
3PAR Confidential
A.14
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. Remplacez la batterie seulement avec le même type ou équivalent
recommandé par le fabricant.
Safety Agency Compliance Notices
3PAR Confidential
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.
A.15Safety Agency Compliance Notices
3PAR Confidential
A.16
Messages and Operator’s Guide InForm OS Version 2.3.1
A.3 3PAR Power CablesEnglish Compliance Statement
All power cables provided by 3PAR are for exclusive use for 3PAR products.
Japanese Compliance Statement
A.4 Energy Consumption EfficiencyEnergy consumption efficiency*= 0.089
* Japan Green Law statement of compliance: The energy consumption efficiency value has
been calculated per requirements for Category-G Magnetic Disk Drive Units by dividing the
power consumption, measured according to the definition in the Law Concerning the Rational
Use of Energy, by the storage capacity defined in the Energy Conservation Law. The efficiency
value is based on a host-maximized T800 configuration using 750GB drives.
3PAR Power Cables
3PAR Confidential
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
Aadapter 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
Bbatteries
explosion warning for A.5
lithium, replacement and disposal of A.5
battery backup units (BBUs)
cache memory and power failure 3.9, 6.28, 7.15
LEDs 3.9, 6.28, 7.15
status and error display 6.29, 7.16
Ccabinets
drive chassis
non-3PAR cabinets, warning for A.16
non-3PAR, controller node warnings A.8
numbering in
drive chassis 2.9, 3.15 to 3.17, 4.12, 5.11
PDUs 2.5 to 2.6, 3.7 to 3.8, 4.7 to 4.8, 5.7 to 5.8
cabinets
numbering in
drive chassis 2.9
cache memory. See control cache memory and
data cache memory
cautions, about 1.6
components, server
identifying 2.1 to 2.3, 3.2 to 3.3, 4.2 to 4.3, 5.2 to 5.3
numbering of 2.3 to 2.15, 3.4 to 3.21, 4.4, 5.4
drive chassis, system for 3.18
control cache memory
location on controller node 2.13, 3.14
numbering system for 2.14, 3.15
controller node chassis
IX.1Index
3PAR Confidential
IX.2
Messages and Operator’s Guide InForm OS Version 2.3.1
amber status light 6.17, 7.10, 8.3, 8.14, 9.3, 9.15
controller node power supplies
LEDs 8.20, 9.19
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
Fibre Channel adapters
numbering of 2.12, 3.13, 4.11, 5.10
LEDs 6.16, 6.19
location of 6.16, 7.9, 8.13, 9.14
status and error display 6.17, 7.9, 8.14, 9.14
loading order for 2.12, 3.11
non-3PAR cabinets, warnings for A.8
numbering of 2.10 to 2.14, 4.9, 5.9
system for 2.13, 3.14
PCI slots 2.12, 3.13
controller nodes
LEDs 7.9
numbering of 3.11
conventions 1.6
icon 1.6
typographical 1.5
Ddata cache memory
location on controller node 2.13, 3.14
numbering system for 2.14, 3.15
data protection, maximizing 3.19, 4.15, 5.14
DIMMs
See also control cache memory and data cache
memory
location on controller node 2.13, 3.14, 4.12, 5.11
numbering system for 2.14, 3.15
disk hot-plug status LED
controller nodes 7.9
disks
numbering system for 2.8, 3.18
documents, related 1.2
Drive 2.9
drive cages
FC-AL modules
LEDs, status and error displays 6.7, 6.10, 7.5
numbering system for 3.18
drive chassis
cabinets, non-3PAR cabinets, warning for A.13
LEDs 6.13, 8.4, 9.4
non-3PAR cabinets, warning for A.16
numbering of 2.9, 3.15 to 3.17, 4.12, 5.11
system for 2.8, 3.18
drive magazines
LEDs
location of 6.12, 6.14, 7.7, 8.12, 9.12
loading pattern 3.19
maximizing availability and data
protection 3.19, 4.15, 5.14
numbering system for 2.8, 3.18
FFC-AL modules
LEDs
location of
DC1 6.6, 6.9, 7.4
status and error displays 6.7, 6.10, 7.5
numbering system for 2.8, 3.18
Fibre Channel
adapter ports 2.12, 3.13, 4.11, 5.10
numbering system for 2.8, 3.18
LEDs
Index
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
port status error display 6.19, 6.22, 8.15
ports, location of 6.18, 6.20, 6.21, 8.15
Fibre Channel adapters
location on controller node 2.13, 3.14
numbering example 2.12, 3.13, 4.11, 5.10
numbering system, chart for 2.13, 3.14
quad-port, numbering for 2.12, 3.13, 4.11, 5.10
Hhot-plug status LEDs 6.8, 6.11, 7.6
controller nodes 6.17, 8.14, 9.15
Iicon conventions 1.6
LLEDs
2-Port LSI Fibre Channel ports
status and error display 6.22, 8.15
3PAR Fibre Channel ports
location of 6.23
Status and error display 7.12
4-Port LSI Fibre Channel ports
status and error display 6.22
battery backup units (BBUs) 3.9, 6.28, 7.15
status and error display 6.29, 7.16
controller nodes 6.16 to 6.19, 7.9
location of 6.16, 7.9, 8.13, 9.14
status and error display 6.17, 7.9, 8.14, 9.14
disks, status and error display 6.13, 6.15, 7.8
drive chassis 6.4 to 6.13, 7.3, 8.4
drive cage, FC-AL modules 6.6, 6.9, 7.4, 8.5
drive cage, FCAL modules 9.5
drive magazines
location of 6.12, 6.14, 7.7, 8.12, 9.12
Emulex Fibre Channel ports
Location of 7.11
location of 8.16
gigabit Ethernet adapter 8.19
gigabit ethernet adapter 6.24
LSI 2-Port Fibre Channel ports
location of 6.20, 8.15
LSI 4-Port Fibre Channel ports
location of 6.21
power supplies 6.26, 7.13, 8.20, 9.19
location of 6.27, 7.14, 8.20, 9.19
QLogic Fibre Channel ports
location of 6.18
status and error display 6.19
server diagnostics 6.2, 7.2, 8.2, 9.2
Nnode hot-plug status LEDs
controller nodes 7.10
node status LEDs, status and error display 7.10
notes, about 1.6
numbering
controller nodes 2.10 to 2.13, 3.11 to 3.14, 4.9, 5.9
drive chassis 2.6 to 2.9, 3.15 to 3.17, 4.12, 5.11
components, system for 3.18
PDUs 2.5, 3.7, 4.7
power supplies 2.15, 3.20, 4.16, 5.15
Ooverview of this guide 1.4
PPCI slots, controller nodes 2.12, 3.13
ports, Fibre Channel adapters 2.12, 3.13, 4.10, 4.11,
5.10
numbering system for 2.8, 2.14, 3.15, 3.18
power banks
indicator lamps 6.29, 7.17, 8.21, 9.20
IX.3Index
3PAR Confidential
IX.4
Messages and Operator’s Guide InForm OS Version 2.3.1
power distribution units (PDUs)
indicator lamps 6.29, 7.17, 8.21, 9.20
numbering for 2.5, 3.7, 4.7, 5.7
power status LEDs, status and error display 6.17,
8.14, 9.15
power supplies
LEDs 6.26, 7.13
location of 6.27, 7.14
numbering of 2.15, 3.20
powering on storage servers 10.4
Rrelated documents 1.2
revision history RH.1
riser card, location on controller node 2.13, 3.14
SS400 server
front view 2.2, 3.2
numbering controller nodes 2.10
rear view 2.3, 3.3
S800 server
numbering controller nodes 2.10
safety agency compliance notices A.2
safety precautions A.2
securing the storage server 6.32, 7.20, 8.26, 9.24
security, of servers A.2
servers
safety precautions A.2
service processor
LEDs 6.24, 8.19
storage server
powering on 10.4
storage servers
components
identifying 2.1 to 2.3, 3.2 to 3.3, 4.2 to 4.3, 5.2 to
5.3
numbering of 2.3 to 2.15, 3.4 to 3.21, 4.4, 5.4
LEDs, for diagnostics 6.2, 7.2, 8.2, 9.2
lithium battery replacement A.5
placement and security A.2
securing 6.32, 7.20, 8.26, 9.24
security of A.2
TTUV compliance A.2
typographical conventions 1.5
UUL® compliance A.2
Vvoltage and frequency verification A.2
Wwarnings, about 1.6
Wintec LEDs 6.30, 6.31, 7.17, 8.22, 8.23, 9.21
Index
3PAR Confidential
InForm OS Version 2.3.1 Messages and Operator’s Guide
Revision History
Release Level Revision Summary
320-200181 Rev A
October 2009
First release of this manual with updated part number to support the
release of 3PAR InForm OS 2.3.1. Chapter 12, Alerts has been
updated.
320-200181 Rev B
February 2010
Second release of this manual to support the Supermicro II service
processor and Solid State Drives (SSD).
Added Chapter 11, Troubleshooting.
RH.1Revision History
3PAR Confidential
RH.2
Messages and Operator’s Guide InForm OS Version 2.3.1
3PAR Confidential
top related