HPE 3PAR StoreServ 8000 Storage - Apache Welcome Pageh20628. · HPE 3PAR StoreServ 8000 Storage Service and Upgrade Guide Customer Edition Part Number: QL226-99284 Published: March

HPE 3PAR StoreServ 8000 StorageService and Upgrade GuideCustomer Edition

Part Number: QL226-99284Published: March 2017

AbstractThis Hewlett Packard Enterprise (HPE) guide provides information about servicing andupgrading hardware components for the HPE 3PAR StoreServ 8000 Storage systems.

© 2015, 2017 Hewlett Packard Enterprise Development LP

NoticesThe information contained herein is subject to change without notice. The only warranties for HewlettPackard Enterprise products and services are set forth in the express warranty statements accompanyingsuch products and services. Nothing herein should be construed as constituting an additional warranty.Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions containedherein.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession,use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, ComputerSoftware Documentation, and Technical Data for Commercial Items are licensed to the U.S. Governmentunder vendor's standard commercial license.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett PackardEnterprise has no control over and is not responsible for information outside the Hewlett PackardEnterprise website.

AcknowledgmentsIntel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation inthe United States and other countries.

Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in theUnited States and/or other countries.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java® and Oracle® are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

Contents

Preparation.............................................................................................. 7Safety and regulatory compliance.................................................................................................7Power safety................................................................................................................................. 7Preventing electrostatic discharge................................................................................................ 8Service and upgrade video........................................................................................................... 8

Component identification.......................................................................9Enclosures front view....................................................................................................................9

Drive bays........................................................................................................................ 12Drives............................................................................................................................... 12

Controller node enclosure rear view........................................................................................... 14Controller node.................................................................................................................15Ports on the controller node............................................................................................. 17

Ethernet port on the controller node......................................................................18FC ports on the controller node.............................................................................19SAS ports on the controller node.......................................................................... 20Cluster interconnect link ports on the controller node........................................... 21Console port on the controller node...................................................................... 22

PCIe host adapters (optional).......................................................................................... 234-port 16 Gb/s FC/10 GbE NIC combo PCIe host adapter................................... 244-port 10 Gb/s iSCSI/10 GbE NIC combo PCIe host adapter............................... 254-port 16 Gb/s FC PCIe host adapter....................................................................262-port 10 Gb/s iSCSI/FCoE CNA PCIe host adapter............................................ 274-port 1 GbE NIC PCIe host adapter.....................................................................282-port 10 GbE NIC PCIe host adapter...................................................................29

Power cooling modules for the controller node enclosure............................................... 30Expansion drive enclosure rear view.......................................................................................... 31

I/O Module........................................................................................................................33SAS ports on the I/O module........................................................................................... 34Power cooling modules for the expansion drive enclosure.............................................. 36

Physical Service Processor.........................................................................................................37Power distribution units...............................................................................................................39

HPE 3PAR Service Processor.............................................................. 40Connection methods for the SP.................................................................................................. 40

Connecting to the SP from a web browser.......................................................................41Connecting to the SP through an SSH.............................................................................41Connecting to the physical SP from a laptop................................................................... 41

Interfaces for the HPE 3PAR SP.................................................................................................42Accessing the SP 5.x SC interface.................................................................................. 43Accessing the SP 5.x TUI.................................................................................................43Accessing the SP 4.x SPOCC interface...........................................................................43Accessing the SP 4.x SPMaint interface directly............................................................. 43Accessing the CLI session from the SP 5.x SC interface................................................ 43Accessing the interactive CLI interface from the SP 5.x TUI........................................... 44Accessing the CLI session from the SP 4.x SPOCC interface.........................................44Accessing the interactive CLI interface from the SP 4.x SPMaint interface.....................44

Check health action from the SP................................................................................................ 44

Contents 3

Checking health from the SP 5.x SC interface.................................................................45Checking health from the SP 4.x SPOCC interface......................................................... 45Checking health from the SP 4.x SPMaint interface........................................................ 45

Maintenance mode action from the SP.......................................................................................47Setting maintenance mode from the SP 5.x SC interface................................................47Setting maintenance mode from the SP 4.x interactive CLI interface..............................47Setting or modifying maintenance mode from the SP 4.x SPMaint interface...................47

Locate action from the SP...........................................................................................................48Running the locate action from the SP 5.0 SC interface..................................................48Running the locate action from the SP 4.x SPOCC interface.......................................... 48

Alert notifications from the SP.....................................................................................................49Browser warnings........................................................................................................................49

Clear Internet Explorer browser warning..........................................................................50Clear Google Chrome browser warning...........................................................................50Clear Mozilla Firefox browser warning............................................................................. 51

HPE 3PAR StoreServ Management Console for the storagesystem....................................................................................................53

Connection method for the SSMC.............................................................................................. 53Connecting to the SSMC from a web browser................................................................. 53

Interfaces for the storage system from the SSMC...................................................................... 54Accessing the SSMC Main Console interface..................................................................54Accessing the SSMC Administrator Console interface.................................................... 54

Checking health from the SSMC.................................................................................................54Alert notifications from the SSMC............................................................................................... 54

Accounts and credentials for service and upgrade...........................56HPE 3PAR Service Processor accounts for service and upgrade.............................................. 56

Setting time-based or encrypted-based password option from the SP 5.x SC................ 58Generating the encrypted-based ciphertext from the SP 5.x SC..................................... 59Setting time-based or encrypted-based password option from the SP 5.x TUI............... 59Generating the encrypted-based ciphertext from the SP 5.x TUI.................................... 60

Storage system accounts for service and upgrade.....................................................................61Setting time-based or encrypted-based password option for a storage systemaccount.............................................................................................................................62Generating the encrypted-based ciphertext for a storage system account......................62Regenerating the encrypted-based ciphertext for a storage system account.................. 63

Time-based password (strong password)................................................................................... 63Encryption-based password (strong password)..........................................................................63

Hardware service of customer self-repair components.................... 64General precautions for hardware servicing............................................................................... 65Spare part number...................................................................................................................... 65Controller node shutdown........................................................................................................... 65

Shutting down a controller node from the SC interface....................................................66Shutting down a controller node from the SPMaint utility.................................................66

Controller node replacement only for 2-node storage systems—Optional CSR component...... 66Replacing a controller node only for a 2-node storage system........................................ 67

Drive replacement—mandatory CSR component.......................................................................69Replacing a drive............................................................................................................. 70

Power cooling module (alternating current) replacement—optional CSR component................73Replacing an AC power cooling module in a controller-node enclosure..........................73Replacing an AC PCM in a drive enclosure..................................................................... 77

4 Contents

Replace a battery in the AC PCM of the controller node enclosure.................................79Small form-factor pluggable transceiver replacement—mandatory CSR component.................83

Replacing a small form-factor pluggable transceiver....................................................... 83

Hardware upgrade of customer self-upgrade components.............. 86Drive upgrade—mandatory CSU component............................................................................. 86

Guidelines for allocating and loading drives.....................................................................87Guidelines specific to installing additional drives............................................................. 90Installing additional drives................................................................................................ 90

Installing system software manually...................................................93Serial cable connections............................................................................................................. 93Connect a laptop to the storage system..................................................................................... 94Connect a laptop to the physical SP........................................................................................... 95Adding a storage system to the SP 5.0 SC.................................................................................95Exporting test LUNs.................................................................................................................... 95Creating virtual volumes............................................................................................................. 96Exporting virtual volumes to a host............................................................................................. 96

Rescuing a controller node—Automatic Node-to-Node Rescue...... 97

Hardware service for the DC storage system.....................................98Power cooling module for the DC storage system......................................................................98Power cooling module (-48V direct-current) replacement—Optional CSR............................... 100

Replacing the -48V DC PCM in a controller node enclosure......................................... 101Replacing a -48V DC PCM in an expansion drive enclosure.........................................104Replacing a battery in the -48V DC PCM of a controller-node enclosure...................... 107

Troubleshooting.................................................................................. 111Troubleshooting issues with the storage system.......................................................................111

Alerts issued by the storage system............................................................................... 111Collecting log files...........................................................................................................111

Collecting HPE 3PAR SmartStart log files........................................................... 111Collecting SP log files from the SC interface....................................................... 111Collecting SP log files from the SPOCC interface............................................... 112

Troubleshooting issues with the components........................................................................... 112Components functions....................................................................................................112

alert .................................................................................................................113ao ....................................................................................................................... 113cabling .............................................................................................................114cage ................................................................................................................... 116cert ...................................................................................................................121dar ..................................................................................................................... 121date ...................................................................................................................122file ...................................................................................................................123fs ....................................................................................................................... 125host ...................................................................................................................126ld ....................................................................................................................... 128license ............................................................................................................ 131network ............................................................................................................ 131

Contents 5

pd ....................................................................................................................... 133pdch ...................................................................................................................138port ...................................................................................................................140qos ..................................................................................................................... 143rc ....................................................................................................................... 143snmp ...................................................................................................................144sp ....................................................................................................................... 145task ...................................................................................................................145vlun ...................................................................................................................146vv ....................................................................................................................... 147

Controlled thermal shutdown......................................................................................... 148

Parts catalog........................................................................................149Bezel (ear cap) parts list........................................................................................................... 149Cable parts list.......................................................................................................................... 149Controller node parts list........................................................................................................... 150Drive parts list........................................................................................................................... 152Drive enclosure parts list...........................................................................................................154I/O module parts list.................................................................................................................. 154PCIe host adapter parts list.......................................................................................................155Power cooling modules parts list.............................................................................................. 155Rail kit parts list.........................................................................................................................156Service processor parts list.......................................................................................................156

Websites.............................................................................................. 158

Support and other resources.............................................................159Accessing Hewlett Packard Enterprise Support....................................................................... 159Accessing updates....................................................................................................................159Customer self repair..................................................................................................................159Remote support........................................................................................................................ 160Warranty information.................................................................................................................160Regulatory information..............................................................................................................160Documentation feedback.......................................................................................................... 161

Acronyms.............................................................................................162

6 Contents

PreparationProcedure

1. Review Safety and regulatory compliance on page 7.2. Review Power safety on page 7.3. Review Preventing electrostatic discharge on page 8.4. Watch the Service and upgrade video on page 8.

Safety and regulatory complianceFor safety, environmental, and regulatory information, see Safety and Compliance Information for Server,Storage, Power, Networking, and Rack Products available at the Hewlett Packard Enterprise Safety andCompliance website.

Related referenceWebsites on page 158

Power safetyFollow these safety precautions when connecting multiple hardware components to power sources:

WARNING:

To reduce the risk of fire, electric shock and damage to power sources.

• Connect only to a circuit providing branch circuit overcurrent protection of appropriate currentrating.

• Connect the input power cord into a grounded (earthed) electrical outlet that is located near theequipment and is easily accessible.

• Be sure that all circuit breakers are in the off position before connecting input power.• Be sure that the load products connected to the power distribution unit (PDU) are adjusted for, or

otherwise capable of operation from the same line voltage supplying the PDU. Failure to verifythat the voltage can lead to severe equipment damage.

• Do not overload the PDU. The total input current rating of all equipment connected to eachoutput cannot exceed the total output rating marked on the PDU.

CAUTION:

To reduce the risk of personal injury from high-leakage current, verify earth connection beforeconnecting the power supply.

The summation of input power for multiple pieces of information technology equipment through theuse of power products can result in high-leakage currents.

If the total storage system leakage current for a storage system of components exceeds 3.5 mA:

• The use of a detachable input power cord is prohibited.• The input power cord must be securely attached and be connected to the AC mains by

hardwiring or through the use of a nonresidential, industrial-styled plug that maintains positiveearth connection.

• If the total storage system leakage current through the ground conductor exceeds 5% of theinput current per line under normal operating conditions, divide the storage system loads amongmultiple power connections.

Preparation 7

Preventing electrostatic dischargeElectrostatic discharge (ESD) can damage electrostatic-sensitive devices and micro circuitry.

CAUTION:

• Keep static-sensitive parts in their containers until they arrive at static-free workstations.• Transport products in electrostatic-safe containers, such as conductive tubes, bags, or boxes.• Avoid contact between electronic components and clothing, which can carry an electrostatic

charge.• Cover workstations with approved static-dissipating material. Prepare an ESD work surface by

placing an anti-static mat on the floor or on a table near the storage system. Attach the groundlead of the mat to an unpainted surface of the rack.

• Ensure that you are always properly grounded (earthed) when touching a static-sensitivecomponent or assembly. Always use the ESD grounding strap and attach the grounding strapclip directly to an unpainted metal surface.

• Keep the work area free of nonconductive materials, such as ordinary plastic assembly aids andfoam packing.

• Use conductive field service tools.• Avoid touching pins, leads, and circuitry.• Always place drives with the printed circuit board assembly-side down.

Procedure

• Use proper packaging and grounding techniques to prevent damage.

Service and upgrade videoCustomer self repair video:

With HPE 3PAR OS 3.3.1, the customer self repair (CSR) video is available at the hpe.com website:

www.hpe.com/support/3PAR8000CSRVideo

With HPE 3PAR OS 3.2.2, the customer self repair (CSR) videos are available at the CSR ServicesMedia Library website:

www.hpe.com/support/sml-csr

1. From the Product category list, select Storage.2. From the Product family list, select 3PAR StoreServ Storage.3. From the Product series list, select the product.4. Select Remove/Replace videos.

Customer self upgrade video:

With HPE 3PAR OS 3.3.1, the customer self upgrade (CSU) video is available at the hpe.com website:

www.hpe.com/support/3PAR8000CSUVideo

8 Preventing electrostatic discharge

http://www.hpe.com/support/3PAR8000CSRVideo

http://www.hpe.com/support/sml-csr

http://www.hpe.com/support/3PAR8000CSUVideo

Component identification• The illustrations of components in this guide are examples only and might not accurately represent the

configuration of your HPE 3PAR StoreServ 8000 Storage.• Due to the large number of prospective configurations, component placement and internal cabling is

standardized to simplify installation and maintenance. The components are placed in the rackaccording to the principles outlined in these topics, and are numbered according to their order andlocation in the rack.

• The components for the storage system have LEDs to indicate status of the hardware and whether it isfunctioning properly. These indicators help diagnose basic hardware problems. You can quicklyidentify hardware problems by examining the LEDs on all components.

• The components and ports for the storage system are assigned a number based on their locationwithin the storage system.

Enclosures front viewThe fronts of the controller node enclosure and expansion drive enclosure contain the bays for installingthe drives for the storage system.

There is one type of controller node enclosure:

• HPE 3PAR StoreServ 8000 Storage 2-node SFF 6.4 cm (2.5 in), 2U, controller node enclosure:Provides 24 SFF drive bays arranged in a single row

Figure 1: Front view of the 2-node SFF 2U controller node enclosure

There are two types of expansion drive enclosures:

• HPE 3PAR StoreServ 8000 Storage SFF 6.4 cm (2.5 in), 2U, SAS expansion drive enclosure:Provides 24 SFF drive bays arranged in a single row

Figure 2: Front view of the SFF 2U SAS expansion drive enclosure• HPE 3PAR StoreServ 8000 Storage LFF 8.9 cm (3.5 in), 4U, SAS expansion drive enclosure: Provides

24 LFF drive bays, arranged in four columns of six slots each

Component identification 9

Figure 3: Front view of the LFF 4U SAS expansion drive enclosure

Figure 4: Front view details of both SFF and LFF enclosures

Front view details of both SFF and LFF enclosures

Item Description

1 Left Ear Cap(bezel)

Location of the system LEDs and a lower-panel latch that opens to gain access to acaptive screw for securing the enclosure to a rack

2 SFF Drive SFF 6.4 cm (2.5 in) drives

3 LFF Drive LFF 8.9 cm (3.5 in) drives

4 Right Ear Cap(bezel)

Lower-panel latch that opens to gain access to a captive screw for securing theenclosure to a rack and the model information for the storage system

10 Component identification

Figure 5: LEDs on the left ear cap (bezel) on the front of the SFF enclosures

Figure 6: LEDs on the left ear cap (bezel) on the front of the LFF enclosures

LEDs on the left ear cap (bezel) on the front of the enclosures

LED Icon Function Status Indicates

1 System Power Green Solid Power

Off No power

System Standby Amber Solid Enclosure powered by the battery

2 Module Fault Amber Solid Fault

Off No fault

Table Continued


LEDs on the left ear cap (bezel) on the front of the enclosures

LED Icon Function Status Indicates

3 Drive Status Amber Solid Fault—An issue exists with one or more drives withinthe enclosure. To determine the affected drives,inspect the LEDs on each drive.

This LED applies only to drives.

Off No fault

Drive baysDrives mount in bays in the enclosure front and each bay is assigned a number for locating drives in thestorage system.

Figure 7: Numbers for the SFF drive bays

Figure 8: Numbers for the LFF drive bays

DrivesDrives are installed in the drive bays at the front of either the controller node enclosures or expansiondrive enclosures. Drives come in two physical sizes installed in carriers (magazines).

Drive types:

• Fast class (FC) drive• Near line (NL) drive• Solid state drive (SSD)

SFF drives are available in all three types: FC, NL, and SSD.

LFF drives are available only in types: NL or SSD.

For the HPE 3PAR StoreServ 8450 Storage, all flash array (AFA) model, only SSDs are supported.

12 Drive bays

Drive sizes:

• SFF 6.4 cm (2.5 in) drives• LFF 8.9 cm (3.5 in) drives

Maximum drives supported:

• 24 SFF drives per enclosure• 24 LFF drives per enclosure

LEDs on the drives:

Figure 9: LEDs on the SFF drives


Figure 10: LEDs on the LFF drives

LEDs on the drives

LED Function Status Indicates

1 Fault Amber solid Drive failed and ready for replacement

Flashing Locate active

2 Status Green solid Normal operation

Flashing Activity

Controller node enclosure rear view

Figure 11: Rear view of the controller node enclosure

14 Controller node enclosure rear view

Rear view of the controller node enclosure

Item Description

1 Power connection 0 This power connection requires a power cable to be attached between thepower supply and an independent electrical source. This electrical sourcemust support the entire power load of the enclosure and have its owncircuit breaker.

2 Power cooling module 0 The power cooling module (PCM) is an integrated power supply andcooling fan and also contains a replaceable battery. The PCM battery isshipped fully charged, but the batteries might lose some charge and showa degraded status immediately when power is applied. One PCM cansupply enough power for the controller node enclosure. Connect eachPCM to draw power from different mains to allow for continued operation ifone main fails.

3 Controller node 0 The controller node caches and manages data from the storage systemand provides hosts with a coherent, virtualized view of the storage system.

4 Controller node 1 The controller node caches and manages data from the storage systemand provides hosts with a coherent, virtualized view of the storage system.

5 Power cooling module 1 The power cooling module (PCM) is an integrated power supply andcooling fan and also contains a replaceable battery. The PCM battery isshipped fully charged, but the batteries might lose some charge and showa degraded status immediately when power is applied. One PCM cansupply enough power for the controller node enclosure. Connect eachPCM to draw power from different mains to allow for continued operation ifone main fails.

6 Power connection 1 This power connection requires a power cable to be attached between thepower supply and an independent electrical source. This electrical sourcemust support the entire power load of the enclosure and have its owncircuit breaker.

7 Serial number The 10-character serial number for the storage system is required for thesoftware setup. The serial number is on the controller node enclosure nextto the rightmost power cooling module (PCM 1) power switch.

Controller node

IMPORTANT:

The controller nodes in the controller node enclosure are inverted 180° from each other, as well asthe ports.

Controller node 15

Figure 12: LEDs on the controller node

LEDs on the controller node

LEDIcon

Function Status Indicates

Status Green Solid Not a cluster member

Green Rapid Flashing • Booting• Shutdown (halted)

Green Slow Flashing Cluster member and flashes slowly insynchronization with the other controller nodesin the cluster

UID/Service Blue Solid Shutdown (halted); not a cluster member; canbe removed

Blue Flashing Locate active; do not remove component

Off Locate not active

Fault Amber Solid Fault

Amber Flashing In the cluster, one of the other controller nodesis shutdown (halted).

Off No fault

Figure 13: Numbers for the controller nodes in a 2-node storage system


Figure 14: Numbers for the controller nodes in a 4-node storage system

Ports on the controller node

IMPORTANT:

The controller nodes in the controller node enclosure are inverted 180° from each other, as well asthe ports.

Figure 15: Ports on the controller node


Port type Description

1 PCIe host adapter slot PCIe slot used for optional host adapters (FC/CNA/NIC).

2 Fibre Channel ports Two onboard 16 Gb FC ports (FC-1, FC-2) used for the host server connection.

3 Ethernet port (MGMT) MGMT: Onboard 1 Gb Ethernet port used to connect to the network.

4 Ethernet port (RC-1) RC-1: Onboard 1 Gb Ethernet port used for an HPE 3PAR Remote Copy or HPE3PAR File Persona connection.

Table Continued

Ports on the controller node 17


Port type Description

5 SAS ports Two onboard 12 Gb SAS ports (DP-1, DP-2) used for the expansion driveenclosure connection.

6 Cluster InterconnectLink

Cluster Interconnect Link ports (Intr0, Intr1) used only with 4-node storagesystems for the controller nodes 0 and 1 to controller nodes 2 and 3 connection.

7 Console port Console port (MFG) is a serial connection for service procedures.

Ethernet port on the controller nodeThe controller node has two built-in Ethernet ports:

• MGMT—Onboard port for the network connection• RC-1—Onboard port for an HPE 3PAR Remote Copy or HPE 3PAR File Persona connection

Figure 16: Ethernet ports on the controller nodes of the controller node enclosure

Figure 17: LEDs for the Ethernet port

LEDs for the Ethernet port


1 Link Up Speed Green Solid 1 Gb Link

Amber Solid 100 Mb Link

Off No link established or 10 Mb Link

Table Continued

18 Ethernet port on the controller node

LEDs for the Ethernet port


2 Activity Green Solid No link activity

Green Flashing Link activity

Off No link established

FC ports on the controller nodeThe controller node has two onboard FC ports and each port includes two LEDs. The arrow head-shapedLEDs point to the port they are associated with.

NOTE:

Incorrectly configured cables result in illuminated amber LEDs.

Figure 18: Onboard FC ports on the controller node

Figure 19: LEDs for the onboard FC ports

LEDs for the onboard FC ports


All ports Off Wake up failure (dead device) or power not applied

1 Port Speed Off Not connected

3 Fast Amber Flashes Connected at 8 Gb/s

Table Continued

FC ports on the controller node 19

LEDs for the onboard FC ports


4 Fast Amber Flashes Connected at 16 Gb/s

2 Link Status On Normal/Connected—link up

Green Flashing Link down or not connected

Numbers for the onboard FC ports

Port Node:Slot:Port (N:S:P)

FC-1 N:0:1

FC-2 N:0:2

SAS ports on the controller node

IMPORTANT:

For the DP-2 port with no SAS cable attached, the amber LED will be illuminated and the greenLED will be off. This behavior is expected for the DP-2 port. For the DP-1 port with no SAS cableattached, both amber and green LEDs will be off.

The controller node has two SAS ports (DP-1 and DP-2) and each includes two LEDs.

Figure 20: SAS (DP-1 and DP-2) ports on the controller nodes of the controller node enclosure

20 SAS ports on the controller node

Figure 21: LEDs for the SAS ports

LEDs for the SAS ports

LEDIcon


Activity Green Solid No link activity



Fault Amber Solid • Fault• Only for DP-2: no SAS cable connected

Amber Flashing Locate active

Off Normal operation

Cluster interconnect link ports on the controller nodeThe controller node has two cluster interconnect link ports and each includes two LEDs.

NOTE:

• 4-node storage system—Cluster interconnect link ports are used to connect nodes together.• 2-node storage system—Cluster interconnect link ports are not used and LEDs will be off.

Cluster interconnect link ports on the controller node 21

Figure 22: Cluster interconnect link ports on the controller nodes

Figure 23: LEDs for the cluster interconnect link ports

LEDs for the cluster interconnect link ports


1 Fault Amber Solid Fault—No link established or the cable incorrectly configured

Amber Flashing • Interconnect link cabling error• Controller node in wrong slot• Serial number mismatch between controller nodes

Off No fault

2 Status Green Solid Link established


Console port on the controller nodeThe controller node has one console port (MFG) that is a serial connection.

22 Console port on the controller node

Figure 24: Console port on the controller nodes of the controller node enclosure

PCIe host adapters (optional)The types of PCIe host adapters available are dependent on the storage system model and type ofcontroller node enclosure. These adapters are optional for the storage system.

IMPORTANT:

These PCIe host adapters are installed by an authorized service provider only.

PCIe host adapters

PCIe host adapters Connectors

4-port 16 Gb Fibre Channel/10 Gb Ethernet (GbE) NIC combo adapter

IMPORTANT:

• Two of the ports are FC, and two are Ethernet.• The Ethernet ports on this PCIe host adapter can be configured for HPE 3PAR File

Persona.• There is no Fibre Channel over Ethernet (FCoE) support for this PCIe host adapter.

SFP+

4-port 10 Gb iSCSI/10 GbE NIC combo adapter

IMPORTANT:

• Two of the ports are iSCSI, and two are Ethernet.• The Ethernet ports on this PCIe host adapter can be configured for HPE 3PAR File

Persona.• There is no FCoE support for this PCIe host adapter.

SFP+

4-port 16 Gb Fibre Channel (FC) adapter

The four ports of this FC adapter can be individually configured to connect to a host or to aremote storage system in an HPE 3PAR Remote Copy configuration.

SFP+

2-port 10 Gb iSCSI/FCoE Converged Network Adapter (CNA)

The two ports of this iSCSI/FCoE adapter can be individually configured as iSCSI or FCoE.

SFP+

Table Continued

PCIe host adapters (optional) 23

PCIe host adapters

PCIe host adapters Connectors

2-port 10 GbE NIC adapter SFP+

4-port 1 GbE NIC adapter RJ45

4-port 16 Gb/s FC/10 GbE NIC combo PCIe host adapter

IMPORTANT:

There is no FCoE support for this adapter.

Ports on the 4-port 16 Gb/s FC/10 GbE NIC combo PCIe host adapter


1 (FC) N:2:1

2 (FC) N:2:2

3 (Ethernet) N:2:3

4 (Ethernet) N:2:4


LED details only for the FC ports

Green Amber Indicates

Off Off No Link

Off Amber Solid Post failure

Green Solid • Off• Amber Solid

Failure in common code module

Green Solid 1 Fast Amber Flash

2 Fast AmberFlashes

3 Fast AmberFlashes

4 Fast AmberFlashes

Link up and activity at 2 Gb/s

Link up and activity 4 Gb/s



24 4-port 16 Gb/s FC/10 GbE NIC combo PCIe host adapter


LED details only for the Ethernet ports


Off Off No link

Off Amber Solid Link at the highest speed, 10 GbE

Green Flashing Amber Solid Link at the highest speed and activity

Green Solid Off Link at the highest speed, 1 GbE

Green Flashing Off Link at lowest speed and activity

4-port 10 Gb/s iSCSI/10 GbE NIC combo PCIe host adapter

IMPORTANT:

There is no FCoE support for this adapter.

Ports on the 4-port 10 Gb/s iSCSI/10 GbE NIC combo PCIe host adapter


1 (iSCSI) N:2:1

2 (iSCSI) N:2:2

3 (Ethernet) N:2:3

4 (Ethernet) N:2:4


LED details only for the iSCSI ports


Off Off No link

Off Amber Solid Boot failure

Green Solid Amber Solid Link up at 10 Gb/s, without traffic

Green Flashing Amber Solid Link up at 10 Gb/s, with traffic

4-port 10 Gb/s iSCSI/10 GbE NIC combo PCIe host adapter 25


LED details only for the Ethernet ports


Off Off No link

Off Amber Solid Link at the highest speed, 10 GbE

Green Flashing Amber Solid Link at the highest speed and activity

Green Solid Off Link at the highest speed, 1 GbE

Green Flashing Off Link at lowest speed and activity

4-port 16 Gb/s FC PCIe host adapter

Figure 25: Ports on the 4-port 16 Gb/s FC PCIe host adapter

Ports on the 4-port 16 Gb/s FC PCIe host adapter


1 N:2:1

2 N:2:2

3 N:2:3

4 N:2:4

Figure 26: LEDs on the 4-port 16 Gb/s FC PCIe host adapter

26 4-port 16 Gb/s FC PCIe host adapter

LEDs on the 4-port 16 Gb/s FC PCIe host adapter


1 Port Speed 3 Fast AmberFlashes

Connected at 8 Gb/s

4 Fast AmberFlashes

Connected at 16 Gb/s

Off Not connected

2 Link Status Green Solid Normal/Connected – link up

Green Flashing Link down or not connected

2-port 10 Gb/s iSCSI/FCoE CNA PCIe host adapter

NOTE:

On some of the 2-port 10 Gb/s iSCSI/FCoE CNAs, the faceplate labeling is reversed, with the porton the left identified as port 2, when oriented as in the following illustration. This illustration showsthe corrected label with port 1 on the left.

Figure 27: Ports on the 2-port 10 Gb/s iSCI/FCoE CNA PCIe host adapter

Ports on the 2-port 10 Gb/s iSCI/FCoE CNA PCIe host adapter


1 N:2:1

2 N:2:2

Figure 28: LEDs on the 2-port 10 Gb/s iSCSI/FCoE CNA PCIe host adapter

2-port 10 Gb/s iSCSI/FCoE CNA PCIe host adapter 27

LEDs on the 2-port 10 Gb/s iSCSI/FCoE CNA PCIe host adapter


1 Link Status Green Solid Normal/Connected – link up

Off Link down or not connected

2 Activity Green Solid Activity

Off No activity

4-port 1 GbE NIC PCIe host adapter

NOTE:

On some of the 4-port 1 GbE NICs, the faceplate labeling is incorrect, indicating that the ports arenumbered 0 through 3. The following illustration shows the corrected label, indicating that the portsare numbered 1 through 4.

Figure 29: Ports on the 4-port 1 GbE NIC PCIe host adapter

Ports on the 4-port 1 GbE NIC PCIe host adapter


1 N:2:1

2 N:2:2

3 N:2:3

4 N:2:4

Figure 30: LEDs on the 4-port 1 GbE NIC PCIe host adapter

28 4-port 1 GbE NIC PCIe host adapter

LEDs on the 4-port 1 GbE NIC PCIe host adapter

LED Status Indicates

1 Green Solid Link speed 1 Gb/s

Off Link speed 100 Mb/s

2 Green Solid Link up


Off Link down

2-port 10 GbE NIC PCIe host adapter

NOTE:

On some of the 2-port 10 GbE NICs, the faceplate labeling is reversed, with the port on the leftidentified as port 2, when oriented as in the following illustration. This illustration shows thecorrected label with port 1 on the left.

Figure 31: Ports on the 2-port 10 GbE NIC PCIe host adapter

Ports on the 2-port 10 GbE NIC PCIe host adapter


1 N:2:1

2 N:2:2

Figure 32: LEDs on the 2-port 10 GbE NIC PCIe host adapter

2-port 10 GbE NIC PCIe host adapter 29

LEDs on the 2-port 10 GbE NIC PCIe host adapter


1 Amb=10 G Amber Solid Link speed 10 Gb/s

Off Link speed 1 Gb/s

2 ACT/Port Green Solid Link up


Power cooling modules for the controller node enclosureThe 764 watt (W) alternating current (AC) power cooling module (PCM) is an integrated power supply andcooling fan that includes a replaceable battery and is a component of the controller node enclosure.

NOTE:

Labels on the PCM for the expansion drive enclosure state: 760W PCM Gold Series.

Figure 33: LEDs on the AC PCM for the controller node enclosure

LEDs on the AC PCM for the controller node enclosure

LEDIcon


AC Input Fail Amber Solid No AC power or PCM fault

Amber Flashing • Firmware Download• Locate active

PCM OK Green Solid AC present and PCM On / OK

Green Flashing Standby mode

Fan Fail Amber Solid PCM fail or PCM fault

Amber Flashing Firmware download

DC Output Fail Amber Solid • No AC power• Fault• Out of tolerance

Table Continued

30 Power cooling modules for the controller node enclosure

LEDs on the AC PCM for the controller node enclosure

LEDIcon



Battery Fail Amber Solid Hard fault (not recoverable)

Amber Flashing Soft fault (recoverable)

Battery Good Green Solid Present and charged

Green Flashing Charging or disarmed

Figure 34: AC PCM numbers for a 2-node storage system

Figure 35: AC PCM numbers for a 4-node storage system

Expansion drive enclosure rear viewIMPORTANT:

Notice that the I/O modules are installed differently between the SFF drive enclosure and the LFFdrive enclosure.

• In the SFF drive enclosure, the I/O modules in the enclosure are inverted 180° from each other,as well as the SAS ports.

• In the LFF drive enclosure, the I/O modules in the enclosure are installed in the same direction,as well as the SAS ports.

Expansion drive enclosure rear view 31

Figure 36: Rear view of the SFF and LFF expansion drive enclosures

Rear view of the SFF and LFF expansion drive enclosures

Item Description

1 Power connection 0 This power connection requires a power cable to be attached between the powersupply and an independent electrical source capable of supporting of the entire powerload of the enclosure and controlled by its own circuit breaker.

2 Power coolingmodule 0

The power cooling module (PCM) is an integrated power supply and cooling fan. OnePCM can supply enough power for the enclosure. Each PCM needs to draw powerfrom different mains, which allows for continued operation if any one main fails.

3 I/O module 0 The I/O modules connect the controller nodes to the drive enclosures using mini-SAScables, enabling the transfer of data between the controller nodes, drives, PCMs, andenclosures.

I/O Module 0 has a red label.

4 SAS ports The SAS ports connect the I/O modules to the controller nodes using mini-SAScables.

5 I/O module 1 The I/O modules connect the controller nodes to the drive enclosures using mini-SAScables, enabling the transfer of data between the controller nodes, drives, PCMs, andenclosures.

I/O Module 1 has a green label.

Table Continued


Rear view of the SFF and LFF expansion drive enclosures

Item Description

6 Power coolingmodule 1

The power cooling module (PCM) is an integrated power supply and cooling fan. OnePCM can supply enough power for the enclosure. Each PCM needs to draw powerfrom different mains, allowing for continued operation in the event of any one mainfailing.

7 Power connection 1 This power connection requires a power cable to be attached between the powersupply and an independent electrical source capable of supporting the entire powerload of the enclosure and controlled by its own circuit breaker.

I/O Module

IMPORTANT:




Figure 37: LEDs on the I/O Module (example shows an SFF 2U drive enclosure)

LEDs on the I/O Module (example shows an SFF 2U drive enclosure)

Icon Function Status Indicates

Power Green Solid Power

Off No power

UID/Service Blue Flashing Locate active

Off Locate not active

Fault Amber Solid Fault

Off No fault

I/O Module 33

Figure 38: Numbers for the I/O modules in the SFF 2U drive enclosure

Figure 39: Numbers for the I/O modules in the LFF 4U drive enclosure

SAS ports on the I/O moduleThe I/O modules have two SAS ports (DP-1 and DP-2) and each includes two LEDs.

IMPORTANT:




Figure 40: SAS (DP-1 and DP-2) ports on the I/O modules of the SFF expansion drive enclosure

34 SAS ports on the I/O module

Figure 41: SAS (DP-1 and DP-2) ports on the I/O modules of the LFF expansion drive enclosure

Figure 42: LEDs on the SAS ports—I/O module

LEDs on the SAS ports—I/O module

LEDIcon


Activity Green On Links up, but no activity

Off No cable, bad cable, not ready or no power

Green Flashing Activity

Fault Amber On Fault

Amber Off No fault


Power cooling modules for the expansion drive enclosureThe 580 watt (W) alternating current (AC) power cooling module (PCM) is an integrated power supply andcooling fan and is a component of the expansion drive enclosure.

NOTE:

Labels on the PCM for the expansion drive enclosure state: 580W PCM Gold Series.

Figure 43: LEDs on the AC PCM for the expansion drive enclosures

LEDs on the AC PCM for the expansion drive enclosures

Icon Function Status Indicates

AC input fail Amber On No AC power or PCM fault

Amber Flashing • Partner PCM Faulty/Off or Firmware Download• Locate active

PCM OK Green On AC Present and PCM On / OK

Green Flashing Standby mode

Fan Fail Amber On PCM fail or PCM fault


DC Output Fail Amber On • No AC power• Fault• Out of tolerance


Figure 44: AC PCM numbers for the SFF (2.5 in) 2U SAS expansion drive enclosure

36 Power cooling modules for the expansion drive enclosure

Figure 45: AC PCM numbers for the LFF (3.5 in) 4U SAS expansion drive enclosure

Physical Service ProcessorThere are two types of HPE 3PAR Service Processor (SP) hardware (physical SP):

• Physical SP with a single power supply (SPS)• Physical SP with a redundant power supply (RPS)

Figure 46: Ethernet ports on the rear panel of the physical SP

Ethernet ports on the rear panel of the physical SP

Port Description

1 Left port is the MGMT port (Eth0/Port 1)

2 Right port is the Service port (Eth1/Port 2/iLO)

Physical Service Processor 37

Figure 47: LEDs on the rear panel of the physical SP

LEDs on the rear panel of the physical SP

LED/Port Function Status Indicates

1 UID/Service Blue On Activated

Blue Flashing SP managed remotely

Off Deactivated

2 NIC Link Green On Network link

Off No network link

3 NIC Activity Green On Link to network

Green Flashing Network activity

Off No network activity

4 Power Supply

NOTE:

Might not beapplicable to your SP(for hot-plug HPE CSpower suppliesONLY)

Green On Normal

Off Off represents one or more of the followingconditions:

• Power unavailable• Power supply failure• Power supply in standby mode• Power supply error

Figure 48: LEDs on the front panel of the physical SP


LEDs on the front panel of the physical SP

LED/Port Function Status Indicates

1 Power On/

Standby button and SPpower

Green Solid SP on

Green Flashing Performing power on sequence

Amber Solid SP in standby, power still on

Off Power cord not attached, no power suppliesinstalled, or power failure

2 Health Green Solid SP on and health normal

Amber Flashing SP health degraded

Red Flashing SP health critical

Off SP power off

3 NIC Status Green Solid Link to network

Green Flashing Network activity

Off No network link/activity

4 UID/Service Blue Solid Active

Blue Flashing Either remote management, firmware upgrade inprogress, or iLO manual reboot sequence initiated

Off Deactivated

Power distribution unitsFor a storage system that is factory integrated in a rack, there are four power distribution units (PDUs)mounted at the bottom of the rack.

For more information, see the HPE 3PAR StoreServ 8000 Storage Site Planning Manual available at theHewlett Packard Enterprise Information Library Storage website.


Power distribution units 39

HPE 3PAR Service ProcessorThe HPE 3PAR Service Processor (SP) is available as either a physical SP or a virtual SP. The HPE3PAR SP software is designed to provide remote error detection and reporting and to support diagnosticand maintenance activities involving the storage systems. The HPE 3PAR SP is composed of a Linux OSand the HPE 3PAR SP software, and it exists as a single undivided entity.

• Physical SP: The physical SP is a hardware device mounted in the system rack. If the customerchooses a physical SP, each storage system installed at the operating site includes a physical SPinstalled in the same rack as the controller nodes. A physical SP uses two physical networkconnections:

◦ The left, Port 1 (Eth0/Mgmt) requires a connection from the customer network to communicate withthe storage system.

◦ The right, Port 2 (Eth1/Service) is for maintenance purposes only and is not connected to thecustomer network.

• Virtual SP: The Virtual SP (VSP) software is provided in an Open Virtual Format (OVF) for VMwarevSphere Hypervisor and self-extractable Virtual Hard Disk (VHD) package for Microsoft Hyper-V. TheVSP is tested and supported on Microsoft Hyper-V (Windows Server 2012/2012 R2/2016) and theVMware vSphere hypervisor (VMware ESXi 5.5/6.0/6.5). The VSP has no physical connections. It runson a customer-owned, customer-defined server and communicates with an HPE 3PAR StoreServStorage system over its own Ethernet connections.

HPE 3PAR SP documentation:

For more information about the HPE 3PAR SP, see the HPE 3PAR Service Processor Software UserGuide.

The HPE 3PAR SP documents are available at the Hewlett Packard Enterprise Information LibraryStorage website.


Connection methods for the SPUse one of the following methods to establish a connection to the HPE 3PAR Service Processor (SP).

• Web browser connection—Use a standard web browser and browse to the HPE 3PAR SP IPaddress.

• Secure Shell (SSH) connection—Use a terminal emulator application to establish a Secure Shell(SSH) session connection.

• Laptop connection—Connect the laptop to the physical SP with an Ethernet connection (LAN).

IMPORTANT:

If firewall permissive mode for the HPE 3PAR SP is disabled, you must add firewall rules to allowaccess to port 8443 or add the hosts to the firewall. By default, permissive mode is enabled for thefirewall. To add rules using the HPE 3PAR SC interface or HPE 3PAR SPOCC interface, you mustfirst enable permissive mode through the HPE 3PAR TUI or HPE 3PAR SPMaint interface. Afteradding the rules, you can then use the interface to disable permissive mode again.

Related tasksConnecting to the SP from a web browser on page 41Connecting to the SP through an SSH on page 41Connecting to the physical SP from a laptop on page 41

40 HPE 3PAR Service Processor

Connecting to the SP from a web browser

Procedure

1. Browse to the HPE 3PAR Service Processor (SP) IP address https://<sp_ip_address>:8443.2. Enter the account credentials, and then click Login.

Related referenceAccounts and credentials for service and upgrade on page 56

Connecting to the SP through an SSH

Procedure

1. Initiate a Secure Shell (SSH) session from a host, laptop, or other computer connected on the samenetwork, and then connect to the HPE 3PAR Service Processor (SP) IP address or hostname.

2. Log in to the HPE 3PAR SP software.


Connecting to the physical SP from a laptop

Procedure

1. At the rear of the physical HPE 3PAR Service Processor (SP), connect a customer-supplied redcrossover cable (or with a small switch in between if using a straight cable) between the MGMT port(Eth0/Port 1) on the physical SP and an Ethernet port of a laptop.

IMPORTANT:

Hewlett Packard Enterprise recommends using a small private switch between the physical SPand the laptop to ensure that the laptop does not lose its network connection during the buildprocess. When the physical SP resets, the MGMT port (Eth0/Port 1) NIC port resets and dropsthe link. This connection loss can result in the failure of the software load process. Any personalswitch with four to eight ports is supported, such as the HPE 1405-5G Switch (J97982A), whichis available as a noncatalog item from HPE SmartBuy.

2. Configure the LAN settings of the laptop with the same subnet as the network for the physical SP.3. Log in to the HPE 3PAR SP software.


Connecting to the SP from a web browser 41

Interfaces for the HPE 3PAR SPInterfaces with HPE 3PAR SP 5.x:

• HPE 3PAR Service Console (SC): The HPE 3PAR SC interface is accessed when you log in to theHPE 3PAR SP and is an appliance which collects data from the managed HPE 3PAR StoreServStorage system in predefined intervals as well as an on-demand basis and sends the data to HPE3PAR Remote Support, if configured. The HPE 3PAR SC also allows service functions to beperformed by a company administrator, Hewlett Packard Enterprise Support, or an authorized serviceprovider. The HPE 3PAR SC replaces the HPE 3PAR Service Processor Onsite Customer Care(SPOCC) interface and the HPE 3PAR SC functionality is similar to HPE 3PAR SPOCC.

• HPE 3PAR Text-based User Interface (TUI): The HPE 3PAR TUI is a utility on the SP that enableslimited configuration and management of the HPE 3PAR SP and access to an the HPE 3PAR CLI forthe attached storage system. The intent of the HPE 3PAR TUI is not to duplicate the functionality ofthe HPE 3PAR SC GUI, but to allow a way to fix problems that may prevent you from using the HPE3PAR SC GUI. The HPE 3PAR TUI appears the first time you log in to the Linux console opened fromthe VMware vSphere Client or through a terminal emulator using Secure Shell (SSH). Prior to the HPE3PAR SP initialization, you can log in to the HPE 3PAR TUI with the admin user name and nopassword. To access the HPE 3PAR TUI after the HPE 3PAR SP has been initialized, log in to theconsole with the admin, hpepartner, and hpesupport accounts and credentials set during theinitialization.

Interfaces with HPE 3PAR SP 4.x:

• HPE 3PAR Service Processor Onsite Customer Care (SPOCC): The HPE 3PAR SPOCC interfaceis accessed when you log in to the HPE 3PAR SP and is a web-based graphical user interface (GUI)that is available for support of the HPE 3PAR StoreServ Storage system and its HPE 3PAR SP. HPE3PAR SPOCC is the web-based alternative to accessing most of the features and functionality that areavailable through the HPE 3PAR SPMAINT.

• HPE 3PAR SPMAINT interface (SPMAINT): The HPE 3PAR SPMAINT interface is for the support(configuration and maintenance) of both the storage system and its HPE 3PAR SP. Use HPE 3PARSPMAINT as a backup method for accessing the HPE 3PAR SP. The HPE 3PAR SPOCC is thepreferred access method. An HPE 3PAR SPMAINT session can be started either from the menuoption in HPE 3PAR SPOCC, through a connection to the HPE 3PAR SP through a Secure Shell(SSH), or logging in to the Linux console; however, only one HPE 3PAR SPMAINT session is allowedat a time.

CAUTION:

Many of the features and functions that are available through HPE 3PAR SPMAINT canadversely affect a running system. To prevent potential damage to the system and irrecoverableloss of data, do not attempt the procedures described in this manual until you have taken allnecessary safeguards.

• HPE 3PAR CPMAINT interface (CPMAINT): The HPE 3PAR CPMAINT terminal user interface is theprimary user interface for the support of the HPE 3PAR Secure Service Agent as well as amanagement interface for the HPE 3PAR Policy Server and Collector Server.

Related tasksAccessing the SP 5.x SC interface on page 43Accessing the SP 5.x TUI on page 43Accessing the SP 4.x SPOCC interface on page 43Accessing the SP 4.x SPMaint interface directly on page 43Accessing the CLI session from the SP 5.x SC interface on page 43Accessing the interactive CLI interface from the SP 5.x TUI on page 44Accessing the CLI session from the SP 4.x SPOCC interface on page 44

42 Interfaces for the HPE 3PAR SP

Accessing the interactive CLI interface from the SP 4.x SPMaint interface on page 44

Accessing the SP 5.x SC interface

Procedure

1. Connect to the HPE 3PAR Service Processor (SP) 5.x from a web browser.2. Log in to gain access to the HPE 3PAR Service Console (SC) interface.

Related referenceConnection methods for the SP on page 40

Accessing the SP 5.x TUI

Procedure

1. Connect to the HPE 3PAR Service Processor (SP) 5.x through an SSH session or log in to the Linuxconsole opened from the VMware vSphere Client.

2. Log in to gain access to the HPE 3PAR Text-based User Interface (TUI).


Accessing the SP 4.x SPOCC interface

Procedure

1. Connect to the HPE 3PAR Service Processor (SP) 4.x from a web browser.2. Log in to gain access to the HPE 3PAR Service Processor Onsite Customer Care (SPOCC) interface.


Accessing the SP 4.x SPMaint interface directly

Procedure

1. Connect to the HPE 3PAR Service Processor (SP) 4.x through an SSH session or log in to the Linuxconsole opened from the VMware vSphere Client.

2. Log in to gain access to the HPE 3PAR SPMaint main menu, HPE 3PAR Service Processor Menu.


Accessing the CLI session from the SP 5.x SC interfaceThe HPE 3PAR Service Console (SC) interface of the HPE 3PAR Service Processor (SP) 5.x provides aCLI session only for issuing noninteractive HPE 3PAR CLI commands.

Procedure

1. Connect and log in to the HPE 3PAR SP 5.x.2. On the HPE 3PAR SC main menu, select Systems.3. On the Actions menu, select Start CLI session.


Accessing the SP 5.x SC interface 43

Accessing the interactive CLI interface from the SP 5.x TUIThe HPE 3PAR Text-based User Interface (TUI) of the HPE 3PAR Service Processor (SP) 5.x providesan interactive CLI interface for issuing HPE 3PAR CLI commands.

Procedure

1. Connect to the HPE 3PAR SP 5.x either by initiating an SSH session or logging in to the Linux consoleopened from the VMware vSphere Client.

2. Log in to gain access to the HPE 3PAR TUI.3. From the HPE 3PAR TUI main menu, enter 7 for Interactive CLI for a StoreServ.


Accessing the CLI session from the SP 4.x SPOCC interfaceThe HPE 3PAR Service Processor Onsite Customer Care (SPOCC) interface of the HPE 3PAR ServiceProcessor (SP) 4.x provides a CLI session only for issuing noninteractive HPE 3PAR CLI commands.

Procedure

1. Connect and log in to the HPE 3PAR SP 4.x.2. From the left side of the HPE 3PAR SPOCC home page, click Support.3. From the Service Processor - Support page, under Service Processor, click SPMAINT on the Web

in the Action column.4. From the 3PAR Service Processor Menu, enter 7 for Execute a CLI command, and then select the

system.


Accessing the interactive CLI interface from the SP 4.x SPMaint interface

The HPE 3PAR SPMaint interface of the HPE 3PAR Service Processor (SP) 4.x provides an HPE 3PARinteractive CLI interface for issuing HPE 3PAR CLI commands.

Procedure

1. Connect to the HPE 3PAR SP 4.x either by initiating an SSH session or logging in to the Linux consoleopened from the VMware vSphere Client.

2. Log in to gain access to the HPE 3PAR SPMaint interface.3. From the HPE 3PAR SPMaint main menu, enter 7 for Interactive CLI for a StoreServ.


Check health action from the SPFrom the HPE 3PAR Service Processor (SP), the Check health action can be initiated in the followingways:

• With SP 5.x: Initiate Check health from the HPE 3PAR Service Console (SC).• With SP 4.x: Initiate Check health from the HPE 3PAR SPMaint interface.

Related tasksChecking health from the SP 5.x SC interface on page 45

44 Accessing the interactive CLI interface from the SP 5.x TUI

Checking health from the SP 4.x SPOCC interface on page 45Checking health from the SP 4.x SPMaint interface on page 45

Checking health from the SP 5.x SC interface

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP) 5.x.2. From the HPE 3PAR Service Console (SC) main menu, select Systems.3. Select Actions > Check health.


Checking health from the SP 4.x SPOCC interface

IMPORTANT:

Ensure that browser pop-ups are allowed.

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP) 4.x.2. From the HPE 3PAR Service Processor Onsite Customer Care (SPOCC) interface main menu, click

Support in the left navigation pane.3. From the Service Processor - Support page, under StoreServs, click Health Check in the Action

column.4. A pop-up window appears showing a status message while the health check runs.

NOTE:

When running the Health Check using Internet Explorer, the screen might remain blank whileinformation is gathered. This process could take a few minutes before displaying results. Wait forthe process to complete and do not attempt to cancel or close the browser.

5. When the health check process completes, it creates a report and displays in a new browser window.Click either Details or View Summary to review the report.

6. Resolve issues if any. Close the report window when you are done.


Checking health from the SP 4.x SPMaint interface

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP) 4.x.2. From the HPE 3PAR Service Processor Onsite Customer Care (SPOCC) interface main menu, select

SPMAINT in the left navigation pane.3. From the HPE 3PAR SPMaint main menu, HPE 3PAR Service Processor Menu, enter 4 for

StoreServ Product Maintenance, and then press Enter.4. From the StoreServ Product Maintenance Menu, enter 4 for Perform StoreServ Health Check, and

then press Enter.5. Enter the number corresponding to the storage system (HPE 3PAR StoreServ) you want to run the

health check on and press Enter.6. Enter: y to retrieve and transfer the check health data and press Enter.

Checking health from the SP 5.x SC interface 45

Are you sure you want to retrieve and transfer the check health data for StoreServ <StoreServ_Name>?(y or n)y...

16:44.51 Checking health of alert16:44.52 Checking health of cabling16:44.52 Checking health of cage16:44.53 Checking health of date16:44.54 Checking health of file16:44.55 Checking health of ld16:44.56 Checking health of license16:44.56 Checking health of network16:44.57 Checking health of node16:44.59 Checking health of pd16:45.05 Checking health of pdch16:45.06 Checking health of port16:45.14 Checking health of rc16:45.14 Checking health of snmp16:45.15 Checking health of sp16:45.15 Checking health of task16:45.16 Checking health of vlun16:45.16 Checking health of vv

7. After the health check completes gathering the data, the HPE 3PAR SP displays a list of files to view.

4.4.2 Show latest health check status from StoreServ

Available files

1 ==> /sp/prod/data/files/1300338/status/110420.101029.all 2 ==> /sp/prod/data/files/1300338/status/110420.101029.det 3 ==> /sp/prod/data/files/1300338/status/110420.101029.err 4 ==> /sp/prod/data/files/1300338/status/110420.101029.sum

0 ==> Abort Operation

Please select a file to display

8. To view the available files, enter the corresponding number, and then press Enter to continue.9. Select the number corresponding to the data file with the .all extension and press Enter. After the

file is reviewed, press Enter to continue, and then select option 0 to exit health check.

NOTE:

The HPE 3PAR SPMaint interface uses the more command to view files. To move to the nextpage, press the spacebar. After viewing the contents of the file, to exit press Enter then select 0(Abort Operation to return to the previous menu. After you return to the previous menu, thereport is discarded. To view the health status again, run the health check again.



Maintenance mode action from the SPFrom theHPE 3PAR Service Processor (SP), the storage system can be set to Maintenance Mode toprevent support information and local notifications of alerts related to the maintenance from being sent toHewlett Packard Enterprise.

The Maintenance Mode action can be set in the following ways:

• With HPE 3PAR SP 5.x: Set Maintenance Mode from the HPE 3PAR Service Console (SC). WhileMaintenance Mode is enabled, the status of the storage system shows as degraded in the HPE3PAR SC interface, and the state description indicates that the storage system is in maintenancemode.

• With HPE 3PAR SP 4.x: Set Maintenance Mode from the HPE 3PAR SPMaint interface.

Related tasksSetting maintenance mode from the SP 5.x SC interface on page 47Setting maintenance mode from the SP 4.x interactive CLI interface on page 47Setting or modifying maintenance mode from the SP 4.x SPMaint interface on page 47

Setting maintenance mode from the SP 5.x SC interface

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP) 5.x.2. From the HPE 3PAR Service Console (SC) main menu, select Systems.3. Select Actions > Set maintenance mode.


Setting maintenance mode from the SP 4.x interactive CLI interfaceWith HPE 3PAR Service Processor (SP) 4.x, a prompt to set Maintenance Mode automatically occurswhen starting an interactive CLI session from SPMaint.

Procedure

1. Connect and log in to the HPE 3PAR SP 4.x.2. From the HPE 3PAR SPMaint main menu, enter 7 for Interactive CLI for a StoreServ.3. To select your storage system, enter 1.4. If you are prompted to turn on Maintenance Mode, enter y. The prompt message states Do you

wish to turn ON maintenance mode for StoreServ ###### before performing anyCLI operations? (y or n).


Setting or modifying maintenance mode from the SP 4.x SPMaint interface

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP) 4.x.2. From the HPE 3PAR Service Processor Onsite Customer Care (SPOCC) main menu, select

SPMAINT in the left navigation pane.3. From the HPE 3PAR SPMaint main menu under Service Processor - SP Maintenance, select

StoreServ Configuration Management.

Maintenance mode action from the SP 47

4. Under Service Processor - StoreServ Configuration, select Modify under Action.5. Under Service Processor - StoreServ Info, select either On or Off for the Maintenance Mode

setting.


Locate action from the SPFrom the HPE 3PAR Service Processor (SP), the Locate action can be initiated in the following ways tolight a specific LED for the specified components:

• With HPE 3PAR SP 5.x: From the HPE 3PAR Service Console (SC) interface• With HPE 3PAR SP 4.x: From the HPE 3PAR Service Processor Onsite Customer Care (SPOCC)

interface, the HPE 3PAR SPMaint interface, and interactive CLI interface using HPE 3PAR CLIcommands

Related tasksRunning the locate action from the SP 5.0 SC interface on page 48Running the locate action from the SP 4.x SPOCC interface on page 48

Running the locate action from the SP 5.0 SC interface

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP) 5.0.2. From the HPE 3PAR Service Console (SC) main menu, select the system or a component.3. Run the Locate action in the following ways.

• On the Actions menu, select Locate.• From the Views menu, select Schematic, and then click the locate LED icon ( ) on the

component in the schematic diagram.


Running the locate action from the SP 4.x SPOCC interface

IMPORTANT:

Ensure that browser pop-ups are allowed.

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP) 4.x.2. From the HPE 3PAR Service Processor Onsite Customer Care (SPOCC) main menu, select Support

in the left navigation pane.3. From the Service Processor - Support page, under StoreServs, select Locate Cage in the Action

column.

When you select Locate Cage for an identified storage system, the HPE 3PAR SP queries the storagesystem to determine available drive enclosures (cages), and then prompts you to select the cage tolocate. After you select the cage, the LEDs on the cage flash amber for 30 seconds.


48 Locate action from the SP

Alert notifications from the SPAlert notifications by email from Hewlett Packard Enterprise Support or the HPE 3PAR Service Processor(SP):

During the HPE 3PAR SP setup, the Send email notification of system alerts option was eitherenabled or disabled. If enabled, the HPE 3PAR SP sends email notifications of alerts to the systemsupport contact. The email might include a Corrective Action for the failure and the spare part numberfor the failed part. The spare part number is used to order a replacement part.

Alert notifications in the HPE 3PAR SP 5.0 HPE 3PAR Service Console (SC):

In the Detail pane of the HPE 3PAR SC interface, an alert notification will display in the Notificationsbox.

Figure 49: Detail pane of the HPE 3PAR SC

Views (1)—The Views menu identifies the currently selected view. Most List panes have several viewsthat you can select. Clicking the down arrow ( ).

Actions (2)—The Actions menu allows you to perform actions on one or more resources that you haveselected, in the list pane. If you do not have permission to perform an action, the action is not displayed inthe menu. Also, some actions might not be displayed due to system configurations, user roles, orproperties of the selected resource.

Notifications box (3)—The notifications box is displayed when an alert or task has affected the resource.

Resource detail (4)—Information for the selected view is displayed in the resource detail area.

Browser warningsWhen connecting to the HPE 3PAR Service Processor (SP) IP address, you might receive a warning fromyour browser that there is a problem with the security certificate (Internet Explorer) for the website, thatthe connection is not private (Google Chrome), or the connection is not secure (Mozilla Firefox). Tocontinue to the site, clear the warning.

Alert notifications from the SP 49

Related tasksClear Internet Explorer browser warning on page 50Clear Google Chrome browser warning on page 50Clear Mozilla Firefox browser warning on page 51

Clear Internet Explorer browser warning

Procedure

• Click Continue to this website (not recommended).

Clear Google Chrome browser warning

Procedure

1. Click the Advanced link.

2. Click Proceed to <sp_ip_address> (unsafe).

50 Clear Internet Explorer browser warning

Clear Mozilla Firefox browser warning

Procedure

1. Click Advanced.

2. Click Add Exception....

Clear Mozilla Firefox browser warning 51

3. (Optional) To remove the warning for this site in the future, select Permanently store this exceptionin the Add Security Exception dialog.

4. In the Add Security Exception dialog, click Confirm Security Exception.


HPE 3PAR StoreServ Management Consolefor the storage system

The HPE 3PAR StoreServ Management Console (SSMC) provides browser-based consoles (interfaces)for monitoring an HPE 3PAR StoreServ Storage system. The HPE 3PAR SSMC procedures in this guideassume that the storage system to be serviced has already been added to the HPE 3PAR SSMC and isavailable for management through logging in to the HPE 3PAR SSMC Main Console. If that is not thecase, you must first add the storage system to the HPE 3PAR SSMC by logging in to the HPE 3PARSSMC Administrator Console.

HPE 3PAR SSMC guidelines:

• The HPE 3PAR SSMC must not be installed the HPE 3PAR Service Processor (SP) or a storagesystem running a virtual SP, and instead the HPE 3PAR SSMC must be installed on a separatecustomer system running Linux or Windows OSs.

• The HPE 3PAR SSMC should be run locally from the storage system on which it is installed.

HPE 3PAR SSMC documentation:

The following documents are available at the Hewlett Packard Enterprise Information Library Storagewebsite.

• The HPE 3PAR StoreServ Management Console Release Notes provide OS-dependent details.• The HPE 3PAR StoreServ Management Console Administrator Guide provides information on

planning, installing, and configuring HPE 3PAR SSMC server instances.• The HPE 3PAR StoreServ Management Console User Guide and the HPE 3PAR StoreServ

Management Console Online Help provide information for managing a storage system after installingan HPE 3PAR SSMC server instance.


Connection method for the SSMC

Connecting to the SSMC from a web browser

Procedure

1. Browse to the HPE 3PAR StoreServ Management Console (SSMC) with the address https://<localhost>:8443.

NOTE:

The default port number is 8443. Another port might have been assigned during installation ofthe software or the <localhost> can be 127.0.0.1.

2. Enter the username and password credentials for an HPE 3PAR SSMC user account.

HPE 3PAR StoreServ Management Console for the storage system 53

Interfaces for the storage system from the SSMCInterfaces for the HPE 3PAR StoreServ Management Console (SSMC):

• Main Console (SSMC console)—Manage a storage system.• Administrator Console (Admin console)—Add, edit, connect, disconnect, and remove a storage

system; accept certificates, and view connected and disconnected systems.

Related tasksAccessing the SSMC Main Console interface on page 54Accessing the SSMC Administrator Console interface on page 54

Accessing the SSMC Main Console interface

Procedure

1. Connect to the HPE 3PAR StoreServ Management Console (SSMC) from a web browser.2. Enter the username and password credentials for an HPE 3PAR SSMC user account.

Accessing the SSMC Administrator Console interface

Procedure

1. Connect to the HPE 3PAR StoreServ Management Console (SSMC) from a web browser.2. Select the Administrator Console check box.3. Enter the username and password credentials for the HPE 3PAR SSMC administrator account.

Checking health from the SSMCHealth panels are included in the Overview view of most detail panes in the HPE 3PAR StoreServManagement Console (SSMC). The dashboard screen summarizes the key properties and health of allconnected storage systems.

Procedure

1. Connect and log in to the HPE 3PAR SSMC.2. On the HPE 3PAR SSMC main menu, click Storage Systems > Systems.

The storage systems managed by the HPE 3PAR SSMC are listed and the health and configurationsummary panels provide a system overview and shows the system health status.

Related referenceConnection method for the SSMC on page 53

Alert notifications from the SSMCThe HPE 3PAR StoreServ Management Console (SSMC) interface displays the following types of HPE3PAR StoreServ Storage system alerts:

54 Interfaces for the storage system from the SSMC

OK / normal alert—Indicates normal activity. No action is required.

Critical alert—Indicates that immediate action is required to resolve an issue with alogical or physical component.

Major, minor, degraded alert—Indicates that action is required to resolve an issue with alogical or physical component.

Related referenceHPE 3PAR StoreServ Management Console for the storage system on page 53

HPE 3PAR StoreServ Management Console for the storage system 55

Accounts and credentials for service andupgrade

IMPORTANT:

There are separate accounts for access to the storage system or the service processor. Theaccount options and type of password vary based on the version of the software installed for thestorage system and the version of the software installed on the service processor.

• Beginning with HPE 3PAR SP 5.x for the service processor, time-based or encryption-basedpasswords are implemented for the support accounts used with the SP.

• Beginning with HPE 3PAR OS 3.2.2 for the storage system, time-based or encryption-basedpasswords are implemented for the support accounts used with the storage system.

HPE 3PAR Service Processor accounts for service andupgrade

For access to the HPE 3PAR Service Processor (SP) interfaces, there are the following account optionsfor the administrator or for HPE Support personnel and authorized service providers. Based on theaccount, there are differences in the access it provides to the HPE 3PAR SP interfaces, the type ofpassword options, and the permissions associated with the account.

Interfaces for HPE 3PAR SP 5.x:

• HPE 3PAR Service Console (SC)• HPE 3PAR Text-based User Interface (TUI)

Interfaces for HPE 3PAR SP 4.x:

• HPE 3PAR Service Processor Onsite Customer Care (SPOCC)• HPE 3PAR SPMaint utility (SPMaint)• HPE 3PAR CPMaint utility (CPMaint)

Accounts with HPE 3PAR SP 5.x for service and upgrade

Account Password options Interface access Permissions

admin Static password

• Administrator sets/changes

• SC through a web browser• TUI through a physical or

virtual console• TUI through an SSH

• Only the administrator• Default account• Can create new local SP

users

hpepartner Static password


• SC through a web browser• TUI through a physical or

virtual console• TUI through an SSH

• Only authorized serviceproviders

• Service and diagnosticfunctions

Table Continued

56 Accounts and credentials for service and upgrade

Accounts with HPE 3PAR SP 5.x for service and upgrade


hpesupport Time-based or encryption-based password

• Administrator sets thepassword optionthrough the SC or TUI

• For encryption-basedpassword, administratorregenerates ciphertext(blob) through the SCor TUI

• Authorized serviceprovider obtains theciphertext (blob) fromthe administrator andretrieves the passwordthrough the StoreFrontRemote

• SC through a web browser• TUI and Linux Shell through

a physical or virtual console• TUI and Linux Shell through

an SSH

• Only HPE Support• Service and diagnostic

functions

root Time-based or encryption-based password

• Administrator sets thepassword optionthrough the SC or TUI

• For encryption-basedpassword, administratorregenerates ciphertext(blob) through the SCor TUI

• Authorized serviceprovider obtains theciphertext (blob) fromthe administrator andretrieves the passwordthrough the StoreFrontRemote

• SP Linux shell • Only HPE Support andauthorized serviceproviders


Accounts and credentials for service and upgrade 57

Accounts with HPE 3PAR SP 4.0 for service and upgrade


3parcust Static password


• SPOCC through a webbrowser

• SPMaint through a physicalor virtual console

• SPMaint through an SSH

• Only the administrator• Default account• Can create new local SP

users

cpmaint Static password

• Administrator sets/change

• SP Linux shell• CPMaint

• Only the administrator• Administrative Secure

Service Agent (SSA)functions

spvar Static password

• Administrator sets/change




• Only HPE personnel andauthorized serviceproviders


spdood Static password

• HPE sets/changes perrelease




• Only HPE Support• Service and diagnostic

functions

root Static password

• HPE sets/changes perrelease

• SP Linux shell • Only HPE Support andauthorized serviceproviders


Related referenceInterfaces for the HPE 3PAR SP on page 42

Setting time-based or encrypted-based password option from the SP 5.xSC

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP) 5.x.2. From the HPE 3PAR Service Console (SC) main menu, select Service Processor, and then select

Actions > Set HPE Support password3. Select Time based password or Encryption based password.4. Click Apply.

Related referenceConnection methods for the SP on page 40Interfaces for the HPE 3PAR SP on page 42

58 Setting time-based or encrypted-based password option from the SP 5.x SC

Generating the encrypted-based ciphertext from the SP 5.x SCIn advance or at the time of a support session, the administrator can generate the ciphertext (blob) andprovide it to Hewlett Packard Enterprise Support to be deciphered. Before or upon arriving at the site, theapproved service provider can obtain the password from Hewlett Packard Enterprise Support over thephone, text message, or email.

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP) 5.x.2. From the HPE 3PAR Service Console (SC) main menu, select Service Processor, and then select

Actions > HPE Support password.3. Select Set HPE Support password.4. Click Show Key for either Encrypted Password Key for hpesupport or Encrypted Password Key

for root, then click Yes, show to confirm. The ciphertext (blob) is displayed for the account in the textbox.

With Show Key, the ciphertext (blob) is regenerate and makes the prior password invalid. You canalso select Regenerate under the hpesupport or root text box to regenerate the ciphertext.

5. To select all the ciphertext, click in the text box, and then copy it to the clipboard using Crtl-C or right-click and Copy.

6. To accept your changes and keep the dialog open, click Apply or OK to accept the changes and closethe dialog.

7. Copy and paste that ciphertext into an email, text message, or into an encrypted zip file and send toHewlett Packard Enterprise Support.

The ciphertext is safe to email, because the random credential contained in the ciphertext is firstencrypted and then wrapped using a public key. Only Hewlett Packard Enterprise can unwrap theencrypted credential using the corresponding private key.


Setting time-based or encrypted-based password option from the SP 5.xTUI

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP) 5.x.2. From the HPE 3PAR Text-Based User Interface (TUI) main menu, enter 5 for 5 == Secure Password

Management.

The current mode is displayed after Current password mode: as either TIME or ENCRYPT.

Generating the encrypted-based ciphertext from the SP 5.x SC 59

3. Enter 1 for 1 == Change password mode to <TIME or ENCRYPT>.


Generating the encrypted-based ciphertext from the SP 5.x TUI

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP) 5.x.2. From the HPE 3PAR Text-Based User Interface (TUI) main menu, enter 5 for 5 == Secure Password

Management.

The current mode isdisplayed as:

Current password mode:ENCRYPT

3. Enter either 2 for 2 == Display password blob for root or enter 3 for 3 == Display password blobfor hpesupport.

The ciphertext (blob) is displayed.4. Copy the entire ciphertext and paste it into an email to Hewlett Packard Enterprise Support or to the

approved service provider. The ciphertext is safe to email, because the random credential contained inthe ciphertext is first encrypted and then wrapped using a public key. Only Hewlett Packard Enterprisecan unwrap the encrypted credential using the corresponding private key.

60 Generating the encrypted-based ciphertext from the SP 5.x TUI

When copying the ciphertext,copy the text starting with:

- - - Begin tpd blob- - -and all the text ending with:

- - - End tpd blob -- -


Storage system accounts for service and upgradeFor access to the HPE 3PAR StoreServ Storage system interfaces, there are the following accountoptions for the administrator or for HPE Support personnel and authorized service providers. Based onthe account, there are differences in the access it provides to the storage system interfaces, the type ofpassword options, and the permissions associated with the account.

Storage system accounts for service and upgrade 61

Storage system accounts with HPE 3PAR OS 3.3.1 and 3.2.2 for service and upgrade

Account PW options Interface access Permissions

3paradm Static password

• Administrator sets/changes through theAdministrator console

• Main console• Administrator console• Interactive CLI

• Only the administrator• Create new CLI user

accounts• Service and diagnostic

functions• Super rights

console Time-based or encrypted-based password

• Administrator sets thepassword option throughCLI commands

• For encrypted-basedpassword, administratorretrieves/exports theciphertext (blob) throughCLI commands

• Main console• Administrator console

• Only HPE Support andauthorized service providers


root Time-based or encrypted-based password

• Administrator sets thepassword option throughCLI commands

• For encrypted-basedpassword, administratorretrieves/exports theciphertext (blob) throughCLI commands

• Linux Shell on thestorage system

• Only HPE Support andauthorized service providers


Setting time-based or encrypted-based password option for a storagesystem account

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP) and access the interactive CLI interface.2. Query the current mode by using the HPE 3PAR CLI controlrecoveryauth status command.3. To change the mode, use the controlrecoveryauth setmethod <totp|ciphertext>

command, where <totp|ciphertext> is either totp or ciphertext.


Generating the encrypted-based ciphertext for a storage system accountIn advance or at the time of a support session, the administrator can generate the ciphertext (blob) andprovide it to Hewlett Packard Enterprise Support to be deciphered. Before or upon arriving at the site, theapproved service provider can obtain the password from Hewlett Packard Enterprise Support over thephone, text message, or email.

62 Setting time-based or encrypted-based password option for a storage system account

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP) and access the interactive CLI interface.2. To generate a ciphertext, initiate the HPE 3PAR CLI controlrecoveryauth ciphertext <user>

command, where <user> is either root or console.3. Copy and paste that ciphertext into an email, text message, or into an encrypted zip file and send to

Hewlett Packard Enterprise Support.

The ciphertext is safe to email, because the random credential contained in the ciphertext is firstencrypted and then wrapped using a public key. Only Hewlett Packard Enterprise Support can unwrapthe encrypted credential using the corresponding private key.


Regenerating the encrypted-based ciphertext for a storage system account

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP) and access the interactive CLI interface.2. To regenerate a ciphertext, initiate the HPE 3PAR CLI controlrecoveryauth rollcred <user>

command, where <user> is either root or console.3. Copy and paste that ciphertext into an email to Hewlett Packard Enterprise Support or to the approved

service provider.

The ciphertext is safe to email, because the random credential contained in the ciphertext is firstencrypted and then wrapped using a public key. Only Hewlett Packard Enterprise can unwrap theencrypted credential using the corresponding private key.


Time-based password (strong password)With the time-based password option, the HPE Support person or authorized service provider can acquirethe account password when needed without the involvement of the administrator. The time-basedpassword is generated using strong cryptographic algorithms and large key sizes, valid for 60 minutes,and are automatically regenerated at the start of each hour.

During the service, upgrade, or diagnostic procedure, the account password remains active until loggingout of the account, even if 60 minutes is exceeded. During the procedure, if it is necessary to log out ofthe account and then log back in to the account (for example, closing the session or rebooting a controllernode), do either of the following:

• If 60 minutes has not been exceeded, use the same password.• If 60 minutes has been exceeded, obtain the newly generated password.

Encryption-based password (strong password)With the encryption-based (ciphertext) password option, the administrator initiates the generation orregeneration of account ciphertext that is copied and provided to the authorized service provider. Theauthorized service provider decrypts the ciphertext to obtain the account password that they will use forthe service, upgrade, or diagnostic procedure. The password does not expire. After the service, upgrade,or diagnostic procedure is completed, the administrator regenerates a new ciphertext to make the currentpassword invalid. Only the administrator initiates the generation or regeneration of the account ciphertextfor a new password.

Regenerating the encrypted-based ciphertext for a storage system account 63

Hardware service of customer self-repaircomponents

IMPORTANT:

Some Hewlett Packard Enterprise components are not designed for customer self repair (CSR). Tosatisfy the customer warranty, Hewlett Packard Enterprise requires that an authorized serviceprovider replace components that are not designed for CSR.

Hewlett Packard Enterprise products are designed with many CSR components to minimize repair timeand allow for greater flexibility in performing a replacement. If during the diagnosis period HewlettPackard Enterprise (or an authorized service provider) identifies the need for a repair and the componentis designed for CSR, Hewlett Packard Enterprise will ship that component directly to you for replacement.With a CSR, Hewlett Packard Enterprise pays all shipping and component return costs and determinesthe courier/carrier to be used.

The materials shipped with a replacement CSR component specify whether a degraded or failedcomponent must be returned to Hewlett Packard Enterprise. When required, you must do the following:

• Ship the component to Hewlett Packard Enterprise within a defined time, normally five business days.• Return the component with the associated documentation in the provided shipping material.

IMPORTANT:

Failure to return the component could result in Hewlett Packard Enterprise billing you for thereplacement.

For more information about CSR, contact an authorized service provider or go to www.hpe.com/info/selfrepair.

To order components, contact an authorized service provider or go to www.hpe.com/info/hpparts.

Parts-only warranty service

IMPORTANT:

For parts-only warranty service, customer self repair (CSR) part replacement is mandatory. If yourequest Hewlett Packard Enterprise to replace these parts, you are charged for the travel and laborcosts of this service.

Your Hewlett Packard Enterprise Limited Warranty might include a parts-only warranty service. Under theterms of parts-only warranty service, Hewlett Packard Enterprise provides replacement parts free ofcharge.

CSR types

• Mandatory—You order the component directly from Hewlett Packard Enterprise and repair theproduct yourself. Onsite or return-to-depot repair is not provided under warranty.

• Optional—You can order the component directly from Hewlett Packard Enterprise and repair theproduct yourself, or you can request that Hewlett Packard Enterprise repair the product. If you requestrepair from Hewlett Packard Enterprise, you might be charged for the repair, depending on the productwarranty.

64 Hardware service of customer self-repair components

http://www.hpe.com/info/selfrepair

http://www.hpe.com/info/selfrepair

http://www.hpe.com/info/hpparts

NOTE:

In some instances to diagnose a component failure, remote support by an authorized serviceprovider might be necessary.

• No—The replaceable component is not available for self repair. For assistance, contact an authorizedservice provider to replace the component.

General precautions for hardware servicingCAUTION:

• Some components heat up during operation. Before servicing a component, cautiouslydetermine if the component is hot. Before removal of the component, wait until the componenthas cooled off.

• To avoid damaging any circuitry, wear an electrostatic discharge (ESD) grounding strap.• Prepare a surface with an ESD safe mat for staging components for installation.

Spare part numberParts have a nine-character spare part number on their labels. For some spare parts and softwareversions, the part number is available from the software interface. Alternatively, the Hewlett PackardEnterprise Support can assist in identifying the correct spare part number.

Figure 50: Example product label with spare part number

With SP 5.x: The spare part number for a failed component is provided in the alert email and also in thealert notification in the HPE 3PAR Service Console (SC) interface.

Controller node shutdownPrerequisites

• Before shutting down a controller node in the cluster, confirm that the other controller nodes in thecluster are functioning normally. Shutting down a controller node in the cluster causes all clusterresources served by it to fail over to the other controller nodes. The failover causes any currentlyexecuting client read and write operations to fail until the cluster failover process completes. The othercontroller nodes are placed under a heavier load by the extra work until the replacement node ispowered up and rejoins the cluster.

• Give adequate warning to users connected to resources of the controller node being shut down.

General precautions for hardware servicing 65

CAUTION:

• Only shut down the controller node at the time service is going to be performed.• Shutting down single controller node causes a performance degradation of the storage system

and if host connectivity is not properly configured, may also cause an outage.

Related tasksShutting down a controller node from the SC interface on page 66Shutting down a controller node from the SPMaint utility on page 66

Shutting down a controller node from the SC interface

Procedure

1. On the HPE 3PAR Service Console (SC) main menu, select Controller Nodes.2. Select a controller node in the list pane.3. On the Actions menu, select Shutdown.4. Follow the instructions on the dialog that opens.

Shutting down a controller node from the SPMaint utility

Procedure

1. From the HPE 3PAR Service Processor Onsite Customer Care (SPOCC) interface main menu, selectSPMAINT in the left navigation pane.

2. Under Service Processor - SP Maintenance, select StoreServ Product Maintenance.3. Under Service Processor – Storage System Product Maintenance, select Halt a Storage System

Cluster or Node.4. The HPE 3PAR SP queries the storage system to determine available controller nodes and then

presents you with a page from which you can select the controller node to shut down (halt).

Controller node replacement only for 2-node storagesystems—Optional CSR componentPrerequisites

• Order a replacement controller node that matches the failed one exactly.• Label cables before replacing the controller node.

IMPORTANT:

Only a controller node for a 2-node system that does not contain a PCIe host adapter qualifies for acustomer self repair (CSR). It is the entire controller node that qualifies for a CSR and excludes therepair of internal components within the controller node. Any internal components within thecontroller node are only serviceable by an authorized service provider (ASP).

CAUTION:

• To prevent overheating, replace the controller node within the maximum service-time limit of 30minutes.

• Only remove one controller node at a time to prevent inserting a controller node in the wrongslot.

• To avoid damaging any circuitry, wear an electrostatic discharge grounding strap.

66 Shutting down a controller node from the SC interface

Replacing a controller node only for a 2-node storage system

IMPORTANT:

Only a controller node for a 2-node system that does not contain a PCIe host adapter qualifies for acustomer self repair (CSR). It is the entire controller node that qualifies for a CSR and excludes therepair of internal components within the controller node. Any internal components within thecontroller node are only serviceable by an authorized service provider (ASP).

IMPORTANT:

The procedure for replacing a controller node varies based on whether the controller node is stillonline or has already been shut down (halted) and is offline. If the controller node failed and wasautomatically shut down (halted), skip the step for shutting down the controller node in the followingprocedure.

If you shut down (halt) the controller node, there is a performance impact for the storage system, soperform this operation when there is minimal activity on the system.

When the controller node is shut down, the Status LED rapidly flashes green and the UID LED issolid blue, which indicates that the shutdown has completed (halted), and it is safe to remove thecontroller node. Also, the Fault LED might be solid amber depending on the nature of the failure.

Procedure

Preparation:1. Unpack the replacement controller node and place it on an ESD safe mat.2. Connect and log in to the service processor (SP).3. Set Maintenance Mode.4. Initiate Check Health of the storage system.

A scan of the storage system will be run to make sure that there are no issues.

CAUTION:

If health issues are identified during the Check Health scan, resolve these issues beforecontinuing. Refer to the details in the Check Health results, review the documentation, andcontact HPE support if necessary.

5. Review the information in the alert notifications.6. Locate the degraded/failed controller node.

If the failed controller node is offline, you cannot run the Locate action on it. Instead, you will identifywhich controller node to remove by either referring to the email notification or the alert notificationand the LEDs on the failed controller node.

7. Label all cables connected to the failed controller node for later connection to the replacementcontroller node.

8. If the degraded controller node was not automatically shut down (halted), manually shut it down.

CAUTION:

If the controller node is properly shut down (halted) before removal, the storage system doesnot fail, but data loss might occur if the replacement procedure is not followed correctly.

9. On the failed controller node, confirm that the Status LED is rapidly flashing green and that the UIDLED is solid blue, which indicates that the controller node has been shut down (halted). Also, theFault LED might be solid amber depending on the nature of the failure. Notice that the other healthycontroller node in the enclosure has the Fault LED as solid amber, which indicates that anothercontroller node (the failed controller node) in the cluster has failed.

Replacing a controller node only for a 2-node storage system 67

Removal:10. Remove cables from the failed controller node.11. Pull the gray controller-node rod to the extracted position out of the failed controller node.12. When the failed controller node is halfway out of the enclosure, slide it out completely and support it

from underneath.13. Place the failed controller node on the ESD safe mat and push in the gray controller-node rod to

ready it for packaging and provide differentiation from the replacement controller node.14. Move SFP transceivers to the replacement controller node.

a. Lift the retaining clip and carefully slide the SFP transceiver out of the port slot.

CAUTION:

To prevent damage when handling the SFP transceiver, do not touch the gold contact leads.

b. Carefully slide the SFP transceiver into the port slot on the replacement controller node until fullyseated, and then close the retaining clip to secure it in place.

Replacement:15. On the replacement controller node, ensure that the gray controller-node rod is in the extracted

position with the rod pulled out of the component.16. Using two hands, grasping each side of the replacement controller node, align it with the grooves in

the slot, and then gently slide it partially into the enclosure until it halts against the insertionmechanism that is inside of the enclosure. Do not fully insert it in the slot at this time, because thecables must be reconnected before it is fully seated.

CAUTION:

Confirm that the controller node is correctly oriented. The controller nodes in the controllernode enclosure are inverted 180° from each other, as well as the ports.

17. Reconnect the cables to the replacement controller node while it is still only partially inserted in theslot.

CAUTION:

Before fully seating the controller node, confirm that the network Ethernet cable is connected tothe MGMT port, which is required for the automatic Node-to-Node rescue.

18. To align and fully seat it into the enclosure, push the gray controller-node rod into the replacementcontroller node. If the UID LED is flashing blue after two minutes, this LED status indicates that thereplacement controller node is not properly seated, so repeat this step.

Once inserted, the replacement controller node powers up and goes through the automatic Node-to-Node rescue before joining the cluster. This process might take up to 10 minutes.

If the automatic Node-to-Node Rescue does not start automatically, connect your authorized serviceprovider.Verification:


19. Verify that the green Status LED on the replacement controller node is flashing in synchronizationwith the other controller nodes, indicating that it has joined the cluster.

20. Initiate Check Health of the storage system.21. If significant time is left in the maintenance window, end the Maintenance Mode.22. Follow the return instructions provided with the replacement component.

Related tasksController node shutdown on page 65Related referenceAlert notifications from the SP on page 49Alert notifications from the SSMC on page 54Check health action from the SP on page 44Connection methods for the SP on page 40Locate action from the SP on page 48Maintenance mode action from the SP on page 47

Drive replacement—mandatory CSR componentCAUTION:

• If more than one physical drive is degraded or failed, contact your authorized service provider todetermine if the repair can be done in a safe manner, preventing down time or data loss.

• To avoid damage to hardware and the loss of data, never remove a drive without confirming thatthe drive fault LED is lit.

• If you require more than 10 minutes to replace a drive, install a drive blank cover to preventoverheating while you are working.

• If the storage system is enabled with HPE 3PAR Data Encryption feature, only use FederalInformation Processing Standard (FIPS) capable drives. Using a non-self-encrypting drive mightcause errors during the replacement process.

• To avoid potential damage to equipment and loss of data, handle drives carefully followingindustry-standard practices and ESD precautions. Internal storage media can be damaged whendrives are shaken, dropped, or roughly placed on a work surface.

• Before inserting drives into enclosures, make sure that the enclosures are free of obstructions(such as loose screws, hardware, or debris). Inspect the drives before inserting them in theenclosure to make sure they are not damaged.

NOTE:

SSDs have a limited number of writes that can occur before reaching the SSD's write endurancelimit. This limit is generally high enough so wear out will not occur during the expected service life ofa HPE 3PAR StoreServ Storage system under the great majority of configurations, IO patterns, andworkloads. HPE 3PAR StoreServ Storage system tracks all writes to SSDs and can report thepercent of the total write endurance limit that has been used. This allows any SSD approaching thewrite endurance limit to be pro-actively replaced before they are automatically spared out. An SSDhas reached the maximum usage limit once it exceeds its write endurance limit. Following theproduct warranty period, SSDs that have exceeded the maximum usage limit will not be repaired orreplaced under Hewlett Packard Enterprise support contracts.

Drive replacement—mandatory CSR component 69

Replacing a drive

CAUTION:

The replacement drive must match the failed drive exactly in terms of drive type, capacity, speed,and manufacturer.

Procedure

Preparation:1. Unpack the replacement drive and place on an ESD safe mat.2. Connect and log into the HPE 3PAR Service Processor (SP).3. Set Maintenance Mode.4. Initiate Check Health of the storage system.


CAUTION:


5. Review the information in the alert notification(s).

The alert notification specifies which drive is in a Failed state. Notice that the health of the storagesystem will be in a Degraded state due to the failed drive.

6. Locate the failed drive. To avoid damaging the hardware or losing data, always confirm the drive byits amber Fault LED, before removing it.

CAUTION:

If you do not see a Fault LED lit solid amber on any of the drives, it could be the data has notbeen vacated yet. When the drive has failed and been spun down, the Fault LED becomes litsolid amber and only then can you proceed with removal. If the drive is still in a Degraded stateinstead of a Failed state, do not attempt to remove the drive from the enclosure, because thedrive is still vacating the data. If you remove a drive in a Degraded state, a loss of data willoccur. Wait to remove the drive once it enters a Failed state, which indicates that the data hasbeen vacated, and the drive is safe to replace. This process may take several hours.

Removal:7. Pinch the handle latch to release the handle into the open position, pull the handle away from the

enclosure, and slowly slide the failed drive out of the enclosure.

Do not remove the failed drive until you have the replacement drive ready. To prevent overheating,do not leave the drive bay unpopulated for more than 10 minutes.

70 Replacing a drive

Figure 51: Removing an SFF drive

Figure 52: Removing an LFF drive8. Place the failed drive on an ESD safe mat.

Replacement:9. Press the handle latch to open the handle.10. With the latch handle of the drive fully extended, align and slide the drive into the bay until the handle

begins to engage.11. Close the handle to fully seat the drive into the drive bay. It will click into place when it is fully seated.12. Observe the newly installed drive for 60 seconds to verify the amber Fault LED turns off and remains

off for 60 seconds.

Hardware service of customer self-repair components 71

Figure 53: Installing an SFF drive

Figure 54: Installing an LFF driveVerification:

13. From the HPE 3PAR SP or HPE 3PAR SSMC, verify the state of the replaced drive is Normal. Untildata has been restored, the state might not yet be updated to Normal. Also, notice that the drive IDhas changed. Any new drive added will be assigned a unique ID.


Related referenceAlert notifications from the SP on page 49Alert notifications from the SSMC on page 54Check health action from the SP on page 44Connection methods for the SP on page 40Locate action from the SP on page 48Maintenance mode action from the SP on page 47


Power cooling module (alternating current) replacement—optional CSR componentPrerequisites

• Once a notification is received about a component being in a degraded or failed state, a replacementcomponent should be sought. You must identify the spare part number so that you can order areplacement:

◦ From an email notification of failure, the spare part number will be included in that message.◦ From an alert through the service processor (SP) HPE 3PAR Service Console (SC) or the HPE

3PAR StoreServ Management Console (SSMC), you can find the spare part number by clicking thealert banner, scrolling down and looking under Component.

• Only for controller node enclosures, verify that at least one power cooling module (PCM) battery ineach controller node enclosure is functional before removing a PCM.

• Ensure that the PCM power switch is turned to the OFF position to disconnect power. Because PCMsuse a common power bus, some PCM LEDs might remain illuminated after the PCM is powered off.

• Wear an ESD strap to avoid damaging any circuitry.• Prepare a surface with an ESD mat for staging components for installation.

CAUTION:

• To prevent overheating, the replacement of the PCM requires a maximum service time of 6minutes.

• Ensure that cables are clear of the PCM when installing in the enclosure.

The PCMs are located at the rear of the system on either side of an enclosure.

There are two types of alternating-current (AC) PCMs:

• 580 W (gold series) AC PCM—Used in the drive enclosures.• 764 W (gold series) AC PCM—Used in the controller node enclosures and includes a replaceable

battery.

The battery for the PCM in the controller-node enclosure is enclosed within a compartment that opensat the top of the 764 W AC PCM. The battery can be replaced without replacing the entire PCM.

Replacing an AC power cooling module in a controller-node enclosure

Procedure

Preparation:1. Unpack the replacement AC PCM on an ESD mat.2. Connect and log into the service processor (SP).3. Set Maintenance Mode.4. Initiate Check Health of the storage system.


CAUTION:


5. Review the information in the alert notification(s).6. Locate the failed PCM.7. Confirm on the failed PCM that the AC Input Fail LED and DC Output Fail LEDs are lit solid amber.

Power cooling module (alternating current) replacement—optional CSR component 73

8. Turn off power to the PCM and disconnect the power cable.a. Loosen the cord clamp, release the cable tie tab, and slide the cord clamp off the cable tie.b. Disconnect the power cable, keeping the cord clamp on the power cable.c. Secure the power cable and cable clamp so that it will not be in the way when the PCM is

removed.Removal:

9. Remove the failed PCM.a. With thumb and forefinger, grasp and squeeze the PCM latch to release the handle.b. Rotate the PCM release handle and slide the failed PCM out of the enclosure, and then place the

PCM on the ESD mat with the battery compartment facing up.

10. Remove the battery from the PCM.a. At the back of the PCM, lift the battery release handle.b. Remove the battery from the battery compartment and place on the ESD safe mat.


Replacement:11. Install the battery in the replacement PCM.

a. With the battery handle in the upright position, insert the battery into the PCM.b. Push down the handle to install.

When the battery is correctly seated, the battery and handle are aligned with the surface of thePCM.


12. Install the replacement PCM.a. On the ESD mat, extend the PCM handle to the open position, and then carry it to the enclosure.b. Slide the replacement PCM into the enclosure, and then push until the insertion mechanism starts

to engage (the handle starts to rotate).

IMPORTANT:

Ensure that no cables get caught in the PCM insertion mechanism.

c. Close the handle until the latch clicks to fully seat the PCM in the enclosure.d. Once inserted, pull back lightly on the PCM to ensure that it is properly engaged.


13. Reconnect the power cable, and tighten the clamp.Verification:

14. Turn the PCM on and check that PCM OK LED is solid green. The Battery Good LED should also besolid green.



Replacing an AC PCM in a drive enclosure

Procedure

Preparation:1. Unpack the replacement AC PCM on an ESD mat.2. Connect and log into the service processor (SP).3. Set Maintenance Mode.4. Initiate Check Health of the storage system.


CAUTION:


Replacing an AC PCM in a drive enclosure 77

5. Review the information in the alert notification(s).6. Locate the failed PCM.7. Confirm on the failed PCM that the AC Input Fail LED and DC Output Fail LEDs are lit solid amber.8. Turn off power to the PCM and disconnect the power cable.

a. Loosen the cord clamp, release the cable tie tab, and slide the cord clamp off the cable tie.b. Disconnect the power cable, keeping the cord clamp on the power cable.c. Secure the power cable and cable clamp so that it will not be in the way when the PCM is

removed.Removal:

9. Remove the failed PCM.a. With thumb and forefinger, grasp and squeeze the PCM latch to release the handle.b. Rotate the PCM release handle and slide the failed PCM out of the enclosure, and then place the


Replacement:10. Install the replacement PCM.

a. On the ESD mat, extend the PCM handle to the open position, and then carry it to the enclosure.b. Slide the PCM into the enclosure, and then push until the insertion mechanism starts to engage

(the handle starts to rotate).

IMPORTANT:




11. Reconnect the power cable, slide the cable clamp onto the cable tie, and then tighten the clamp.Verification:

12. Turn the PCM on and check that Battery Good LED is solid green and the PCM OK LED is solidgreen.



Replace a battery in the AC PCM of the controller node enclosure

Procedure

Preparation:1. Unpack the replacement battery and place it on an ESD mat.2. Connect and log into the service processor (SP).3. Set Maintenance Mode.4. Initiate Check Health of the storage system.


Replace a battery in the AC PCM of the controller node enclosure 79

CAUTION:


Because each battery is a backup for both controller nodes in the controller node enclosure,controller nodes 0 and 1 both report a problem with a single battery. The Qty appears as 2 in outputbecause two controller nodes are reporting the problem. Battery 0 for controller node 0 is in the leftPCM, and battery 0 for controller node 1 is in the right side PCM (when looking at the controller nodeenclosure from the rear).

5. Review the information in the alert notification(s).6. Locate the failed PCM.7. Confirm on the failed PCM that the Battery Fail LED is solid amber.8. Verify that at least one PCM battery in each node enclosure is functional and identify which battery

needs to be replaced.9. Turn off power to the PCM and disconnect the power cable.

a. Loosen the cord clamp, release the cable tie tab, and slide the cord clamp off the cable tie.b. Disconnect the power cable, keeping the cord clamp on the power cable.c. Secure the power cable and cable clamp so that it will not be in the way when the PCM is

removed.Removal:

10. Remove the failed PCM.a. With thumb and forefinger, grasp and squeeze the PCM latch to release the handle.b. Rotate the PCM release handle and slide the PCM out of the enclosure, and then place the PCM

on the ESD mat with the battery compartment facing up.

11. Remove the failed battery from the PCM.a. At the back of the PCM, lift the battery release handle.b. Remove the failed battery from the battery compartment and place on the ESD safe mat.


Replacement:12. Install the replacement battery.

a. With the battery handle in the upright position, insert the replacement battery into the PCM.b. Push down the handle to install.

When the battery is correctly seated, the battery and handle are aligned with the surface of thePCM.


13. Install the PCM.a. On the ESD mat, extend the PCM handle to the open position, and then carry it to the enclosure.b. Slide the PCM into the enclosure, and then push until the insertion mechanism starts to engage

(the handle starts to rotate).

IMPORTANT:




14. Reconnect the power cable, slide the cable clamp onto the cable tie, and then tighten the clamp.Verification:

15. Turn the PCM on and check that Battery Good LED is solid green and the PCM OK LED is solidgreen.



Small form-factor pluggable transceiver replacement—mandatory CSR component

A small form-factor pluggable (SFP) transceiver is installed in each onboard Fibre Channel (FC) port andare also installed in the ports of PCIe host adapters (optional component).

Replacing a small form-factor pluggable transceiver

WARNING:

When the storage system is on, do not stare at the FC fibers, because doing so could damage youreyes.

Small form-factor pluggable transceiver replacement—mandatory CSR component 83

CAUTION:

When handling the small form-factor pluggable (SFP) transceiver, do not touch the gold contactleads to prevent damage.

Procedure

Preparation:1. Unpack the replacement SFP transceiver and place on an ESD safe mat.2. Connect and log into the HPE 3PAR Service Processor (SP).3. Access the interactive CLI interface.4. Set Maintenance Mode.5. Identify the storage system to be serviced.6. Initiate Check Health of the storage system.


CAUTION:

If health issues are identified during the Check Health scan, resolve these issues beforecontinuing. Refer to the details in the Check Health results and review the documentation.

7. Review the information in the alert notification(s).

• From the email alert notification: Information for the failed port due to the failed SFPtransceiver is provided in an email alert notification is the email notifications are enabled. The portposition in the storage system is provided as Node:Slot:Port (N:S:P)

• From the HPE 3PAR StoreServ Management Console (SSMC): On the Ports screen, a yellowalert notification banner appears that contains the information for the failed port due to the failedSFP transceiver. From the SSMC main menu, select Storage Systems > Systems, select thestorage system from the list, select Configuration view from the detail pane, click the total portshyperlink from the Ports panel. In the alert notification banner, the port position is provided asNode:Slot:Port (N:S:P).

NOTE:

The health and details listed in the SSMC for the failed port might still show as healthy. Ifthis occurs, rely on the information in the alert notification about the failed port and confirmthat you have located the failed port by its LEDs that will have the Port Speed LED off andthe Link Status LED flashing green.

• From the HPE 3PAR Service Console (SC): A yellow alert notification banner appears thatcontains the information for the failed port due to the failed SFP. In the alert notification banner,the port position is provided as Node:Slot:Port (N:S:P). Click the banner to expand the box, whichshows additional information about the nature of the alert. Click the details link to be taken to theActivity view for the appropriate component. You can also view a graphical representation of thecomponents from the Schematic view.

8. Locate the failed SFP transceiver.

Use the Node:Slot:Port position to locate the port containing the failed SFP transceiver, which willhave the Link Status LED flashing green and the Port Speed LED off.Removal:

9. Label the cable connected to the failed SFP transceiver, and then disconnect the cable.10. Open the retaining clip and carefully slide the failed SFP transceiver out of the port slot on the

controller node.Replacement:

11. Carefully slide the replacement SFP transceiver into the port slot on the controller node until fullyseated, and then close the retaining clip to secure it in place.


12. Reconnect the cable.Verification:

13. On the port with the replacement SFP transceiver, verify that the Link Status LED is solid green andthe Port Speed LED is flashing amber.

14. With the SSMC or SC, verify that the alert notification banner no longer appears and that the Statefor the port and the storage system are Normal (green).

15. Initiate Check Health of the storage system.

A scan of the storage system will be run to make sure that there are no issues after the replacement.16. If significant time is left in the maintenance window, end the Maintenance Mode .17. Follow the return instructions provided with the replacement component.



Hardware upgrade of customer self-upgradecomponents

IMPORTANT:

Some Hewlett Packard Enterprise components are not designed for customer self upgrade (CSU).To satisfy the customer warranty, Hewlett Packard Enterprise requires that an authorized serviceprovider replace such components.

HPE 3PAR StoreServ 8000 Storage products include HPE 3PAR licensing which enables all functionalityassociated with the system. A failure to register the license key might limit access and restrict upgradingof your storage system. Before you proceed with upgrading, verify all applicable licenses associated withthe storage system are registered.

Drive upgrade—mandatory CSU componentPrerequisites

IMPORTANT:

The guidelines for how the drives are installed, allocated, and balanced are critical to theperformance and reliability of your storage system.

Determine an installation plan for allocating and loading the drives based on the provided guidelines,number of drives, and drive types to install.

CAUTION:

• To avoid potential damage to equipment and loss of data, handle drives carefully followingindustry-standard practices and ESD precautions. Internal storage media can be damaged whendrives are shaken, dropped, or roughly placed on a work surface.

• To ensure proper thermal control, drive blanks are provided with the enclosures and must beinserted in all unused drive bays in the enclosure. Operate the enclosure only when all bays arepopulated with either a drive or a drive blank.

• If the storage system is enabled with the Data-at-Rest (DAR) encryption feature, only useFederal Information Processing Standard (FIPS) capable drives.

• Before inserting drives into enclosures, make sure that the enclosures are free of obstructions(such as loose screws, hardware, or debris). Inspect the drives before inserting them in theenclosure to make sure they are not damaged.

• To avoid any cabling errors when powering on the storage system, all enclosures must have atleast one drive pair installed by following the allocating and loading guidelines provided in thisdocument.

Procedure

1. Review Guidelines for allocating and loading drives on page 87.2. Review Guidelines specific to installing additional drives on page 90.3. Installing additional drives on page 90.

86 Hardware upgrade of customer self-upgrade components

Guidelines for allocating and loading drives• A pair or pairs of drives must be installed together and must be of the same capacity, speed, and type.

Never install an uneven number of drives of one type within a single enclosure.• While making sure to load drives in pairs of the same drive type, try to distribute the same number of

drives and drive types in all enclosures. An even distribution may not always be possible.• Different drive types can be loaded next to each other in the same enclosure, but load all the drives of

one drive type before loading drives of a different drive type.

IMPORTANT:

When adding new drives to an existing configuration, keep existing drives in their slots. For thenewly added drives, install the drives in the next available slots, following the rules forallocation and balancing between enclosures.

SFF drive loading guidelines and examples

SFF drives are loaded starting at bay 0, left to right. The bays are numbered 0 through 23.

Figure 55: SFF numbering of drive bays

Figure 56: SFF drive loading order

Example of a correct drive allocation in one SFF enclosure

This example demonstrates an SFF enclosure loaded correctly with these drives: two pairs of FC, threepairs of NL, and two pairs of SSD.

Guidelines for allocating and loading drives 87

Example of a correct drive allocation in two SFF enclosures

This example demonstrates two SFF enclosures loaded correctly with these drives: three pairs of FC(six drives), five pairs of NL (10 drives), and two pairs of SSD (four drives).

Example of an unbalanced allocation in two SFF enclosures

CAUTION:

This example demonstrates an unbalanced allocation due to the NL drives not being installed ineven pairs.

Avoid having an odd number of drives allocated in the drive enclosures.

LFF drive loading guidelines and examples

IMPORTANT:

Notice that the numbering for the order and direction that drives are installed in the LFF enclosuredo not follow the same number order used to identify drives from the storage system managementsoftware. Drives are installed in vertical columns instead of by sequential numbering.

LFF drives are loaded starting at bay 0, bottom to top in the left-most column, then bottom to top in thenext column, and so on. Note bay numbering does not follow how the bays are loaded. The bays are


numbered left to right, and then the next row up, left to right, and so on, from 0 to 23. The first four LFFdrives are loaded into bays 0, 4, 8, and 12.

Figure 57: LFF numbering of drive bays

Figure 58: LFF drive loading order

Example of a correct drive allocation in one LFF enclosure

This example demonstrates an LFF enclosure loaded correctly with these drives: three pairs of NL (sixdrives) and one pair of SSD (two drives).

Hardware upgrade of customer self-upgrade components 89

Example of an unbalanced allocation in one LFF enclosure

CAUTION:

This example demonstrates an unbalanced allocation due to the NL drives being installed acrossall four columns.

Instead, the correct way to load the drives is loading in the first column before moving to the nextcolumn to the right.

Guidelines specific to installing additional drivesWhen adding new drives to an existing configuration, previously installed drives do not need to beremoved for the sake of keeping drives of the same type together. Additional drives should be installed inthe next available slots, following the rules for allocation and balancing between enclosures.

• Additional drives added can include all SFF, all LFF, or a mixture of SFF and LFF drives, but they mustbe installed in pairs of the same drive type with as much of an equal distribution as possible betweenenclosures. If an equal distribution is not possible, you should get as close as possible withoutbreaking the rules.

• The first expansion drive enclosure added to a system must be populated with the same number ofdrives as the controller node enclosure.

• The same number of drives should be added to all of the drive enclosures of that type in the system.

Upgrading with a mix of SFF and LFF drives in expansion drive enclosures:

When upgrading a storage system with mixed SFF and LFF expansion drive enclosures, you must followthese guidelines to maintain a balanced work load.

• Upgrades can be just SFF, LFF, or a mixture of SFF and LFF drives.• SFF-only upgrades must split the drives evenly across all SFF enclosures.• LFF-only upgrades must split the drives evenly across all LFF enclosures.• Mixed SFF and LFF upgrades must split the SFF drives across all SFF enclosures and LFF drives

across all LFF enclosures.

Installing additional drives

Procedure

Preparation:1. Unpack the drive pairs and place on an ESD safe mat.2. Connect and log into the HPE 3PAR Service Processor (SP).

90 Guidelines specific to installing additional drives

3. Set Maintenance Mode.4. Initiate Check Health of the storage system.


CAUTION:


5. Obtain the current drive count from an HPE 3PAR SP or HPE 3PAR SSMC interface.Installation:

6. Remove the drive blank where you will be installing the drive pairs.7. To open the handle on the drive, press the handle latch.8. With the latch handle fully extended, align and push the drive from the end near the latch hinge to

slide the drive into the bay until the handle begins to engage (1).9. Close the latch handle (2) and press firmly to fully seat the drives.

Figure 59: SFF drives

Hardware upgrade of customer self-upgrade components 91

Figure 60: LFF drives10. Repeat the steps for each drive.

IMPORTANT:

For proper airflow and cooling, a drive blank must remain installed in all unused drive bays.

Verification:11. From an HPE 3PAR SP or HPE 3PAR SSMC interface, verify the installation of the additional drives.

The display refreshes periodically, and you should see the newly inserted drives, which areautomatically admitted into the storage system.

IMPORTANT:

The storage system can be used normally, but newly added drive capacity must be initializedbefore it can be allocated.

Within six minutes (depending on the storage system load and the size of the upgrade), the driveswill be assigned an ID number, and the storage system starts to initialize the chunklets to ready foruse. Chunklet initialization can take several hours to complete and the output of the availablecapacity is displayed. Once the drives are admitted, notice at the top of the list that your drive counthas increased appropriately. Scroll down to the bottom of the list to see all the drives installed in yoursystem.

12. Initiate Check Health of the storage system.

A scan of the storage system will be run to make sure that there are no issues after the addition ofdrives has been performed.

13. If significant time is left in the maintenance window, end the Maintenance Mode.

Related referenceCheck health action from the SP on page 44Connection methods for the SP on page 40


Installing system software manuallyCAUTION:

Use this procedure only in the following situations:

• With HPE 3PAR OS 3.3.1 only if the HPE Guided Setup isn't available• With HPE 3PAR OS 3.2.2 only if the HPE SmartStart or the storage system and service

processor (SP) setup wizards are not available

This appendix describes how to manually set up and configure the storage system software and SP. Youmust execute these procedures from a laptop after powering on the storage system.

Serial cable connections• The gray adapter for the laptop (PN 180-0055) is used on the serial port for connection to the MFG

port on the controller node. You will need a USB-to-serial adapter on a laptop to have a serial port.• The black adapter for the service processor (PN 180-0059-01) connects the Ethernet port on the

laptop to the maintenance port on the controller node.

Laptop connector pin-outs

Use at the laptop end of a standard Ethernet cable to connect to the maintenance port on the controllernode and in conjunction with the service processor adapter (PN 180-0059-01) and a standard Ethernetcable to connect the laptop to the Service Processor serial port.

DB9 (Female) RJ45

• Pin 2-Pin 2 (orange)• Pin 3-Pin 3 (black)• Pin 5-Pin 5 (green)

Figure 61: Laptop connector pin-outs

Service processor connector pin-outs

Use at the SP end of a standard Ethernet cable and in conjunction with the laptop adapter (PN180-0055-01) to allow serial connection to the SP.

DB9 (Female) RJ45

• Pin 2-Pin 3 (orange)• Pin 3-Pin 2 (black)• Pin 5-Pin 5 (green)

Installing system software manually 93

Figure 62: Service processor connector pin-outs

Connect a laptop to the storage systemProcedure

• Connect to the storage system with either of these methods:

◦ Connect the laptop directly to the storage system with a serial cable:

1. Configure the laptop COM port to the following settings using a terminal emulator:

Setting Value

Baud rate 57600

Data bits 8

Parity None

Stop bits 1

Flow control Xon/Xoff

2. Connect a serial cable (either a serial or usb-to-serial connector) to the Console port (MFG) onthe highest-numbered controller node and to the serial port on the laptop

3. Once connected, log in using one of the following methods:

– With HPE 3PAR OS 3.3.1, log in using the 3paradm account credentials– With HPE 3PAR OS 3.2.2, log in using the console account credentials.

◦ Connect a laptop to the storage system over a private network:

1. Connect a red crossover cable (or with a small switch in between if using a straight cable) toEthernet MGMT port on the highest numbered controller node and to the LAN port of a laptop.

2. Configure the LAN for the laptop with the same subnet as the network for the storage system.3. Use a terminal emulator application (such as Putty) to establish a Secure Shell (SSH)

communication to the storage system from the laptop one of the following methods:

94 Connect a laptop to the storage system

– With HPE 3PAR OS 3.3.1, log in using the 3paradm account credentials– With HPE 3PAR OS 3.2.2, log in using the console account credentials.

Connect a laptop to the physical SPProcedure

1. At the rear of the physical HPE 3PAR Service Processor (SP), connect a customer-supplied redcrossover cable (or with a small switch in between if using a straight cable) between the MGMT port(eth0/Port 1) on the SP and an Ethernet port of a laptop.

2. Configure the LAN settings of the laptop with the same subnet as the network for the physical SP.

Adding a storage system to the SP 5.0 SCPrerequisites

The following information is required to initialize an HPE 3PAR StoreServ Storage system:

Serial number—Serial number of the storage system being added to the HPE 3PAR Service Processor(SP). The number must be validated to generate a link local IP address, connect to the storage system,and receive information about the storage system. If the serial number is entered in an incorrect format, afield discovery error is displayed.

System settings—Storage system name and IP address, DNS, Time and Date, and 3paradm accountuser password. The password is limited to 31 characters and can be alpha-numerical plus the followingcharacters: +, -, _, *, @

Installation site—Information about the site where the HPE 3PAR SP is installed.

Contacts—Contact information for Hewlett Packard Enterprise support to contact for the system as wellas for the contacts who will receive email notifications of system alerts. At least one system supportcontact must be provided to Hewlett Packard Enterprise support for each system.

Procedure

1. Connect and log in to the HPE 3PAR SP 5.0.2. On the HPE 3PAR Service Console (SC) main menu, select Storage Systems > Systems.3. Select Add system on the Actions menu.4. Follow the instructions on the dialog that opens.

Exporting test LUNsAs the final step in verifying the storage system installation, create two or three test LUNs and confirmthat the attached host or hosts can access them. After you have created the test LUNs and verified thatthe host can access them, notify the system administrator that the storage system is ready for use.

Connect a laptop to the physical SP 95

NOTE:

Before you can export test LUNs, you must determine the host Fibre Channel (FC) connection typesand set the appropriate port personas for all target ports, or ports that connect to host computers.See the appropriate HPE 3PAR <host OS> Implementation Guides available at the Hewlett PackardEnterprise Information Library Storage website.


Creating virtual volumesProcedure

1. Connect and log in to the HPE 3PAR StoreServ Management Console (SSMC).2. From the HPE 3PAR SSMC main menu, select Block Persona > Virtual Volumes.3. On the Virtual Volumes page, click + Create virtual volume or select Actions > Create4. In the General section of the Create Virtual Volume dialog, enter the name of the virtual volume, the

system on which it will reside, the type of provisioning, the CPG it will be created from, and the VV’ssize.

5. (Optional) You can export the virtual volumes (VVs) to a host at the time you create it or export it later.6. When you have completed your choices, click Create to start the action and close the dialog, or click

Create + to start the action and keep the dialog open.

Exporting virtual volumes to a hostExporting a virtual volume (VV) means to present that virtual volume to a host. Exporting makes a volumeavailable to a host by creating an association between the volume's name and a LUN for the specifiedhost and port.

Procedure

1. Connect and log in to the HPE 3PAR StoreServ Management Console (SSMC).2. From the HPE 3PAR SSMC main menu, select Block Persona > Virtual Volumes.3. On the Virtual Volumes page, select Actions > Export and follow the instructions.

96 Creating virtual volumes

Rescuing a controller node—Automatic Node-to-Node Rescue

Each controller node has an on-board Ethernet port (MGMT port) that connects the controller nodes inthe system together through the network in a cluster, which allows for a rescue to occur between anactive controller node in the cluster and the new controller node added to the system. This rescue iscalled an automatic Node-to-Node Rescue and is used in place of needing to connect the serviceprocessor (SP) for the rescue.

IMPORTANT:

For the automatic Node-to-Node rescue to occur for the new controller node being added to thestorage system, the network Ethernet cable must be connect to the MGMT port on this newcontroller node before it is fully seated into the slot of the enclosure.

Rescuing a controller node—Automatic Node-to-Node Rescue 97

Hardware service for the DC storage systemCAUTION:

The use of alternating-current (AC) power is prohibited with any component for the direct-current(DC) power model of the HPE 3PAR StoreServ 8000 Storage system. The DC model requires theinstallation of DC-specific components.

Power cooling module for the DC storage system-48VDC input 764W PCM LEDs

The -48VDC input 764W power cooling module (PCM) is used with direct-current (DC) storage systems inboth the controller node enclosures and expansion drive enclosures. The -48V DC PCM is an integratedpower supply and cooling fan that has a compartment for adding a replaceable battery when it is installedin a controller node enclosure.

NOTE:

• Labels on the PCM for the DC storage system state: -48VDC INPUT 764W PCM.• The power switch on the -48V DC PCM is inverted 180° from the orientation of the power switch

on the AC PCM.

Figure 63: -48VDC input 764W PCM LEDs

-48VDC input 764W PCM LEDs

DC InputFail

Power Fan Fail DC OutputFail

Indicates

Off Off Off Off No DC power on any PCM

On Off Off On No DC power on this PCM only

Table Continued

98 Hardware service for the DC storage system

-48VDC input 764W PCM LEDs

DC InputFail

Power Fan Fail DC OutputFail

Indicates

Off On Off Off DC present; PCM OK

Off On Off On PCM fan speed is outside acceptable limits

Off Off On Off PCM fan has failed

On Off On On PCM fault (over temp, over voltage, over current)

Off Flashing Off Off Standby mode

Flashing Off Flashing Flashing PCM firmware download

LEDIcon


Battery Fail Amber Solid Hard fault (not recoverable)

Amber Flashing Soft fault (recoverable)

Battery Good Green Solid Present and charged

Green Flashing Charging or disarmed

Figure 64: PCM numbers in the 2-node storage system (one 2-node SFF 2U controller-node enclosure)

Figure 65: PCM numbers in the 4-node storage system (two 2-node SFF 2U controller-node enclosures)

Hardware service for the DC storage system 99

Figure 66: PCM numbers in the SFF 2U expansion drive enclosure

Figure 67: PCM numbers in the LFF 4U expansion drive enclosure

Power cooling module (-48V direct-current) replacement—Optional CSRPrerequisites

WARNING:

Due to the risk of injury from electric shock or high energy levels, only individuals knowledgeableabout the procedures, precautions, and hazards associated with DC power products must performthe power cabling, routine maintenance, and service of this product. HPE and partner servicepersonnel are not authorized to perform DC power cabling.

• The customer must arrange to have a certified electrician available during the installation to completethe power cabling connections of the direct-current (DC) power cooling module (PCM) to the storagesystem.

• Once a notification is received about a component being in a degraded or failed state, identify thespare part number and order a replacement component.

◦ From an email notification of failure, the spare part number will be included in that message.◦ From an alert through the HPE 3PAR Service Processor (SP) or the HPE 3PAR StoreServ

Management Console (SSMC), you can find the spare part number by clicking the alert banner,scrolling down and looking under Component.

• Only for the controller node enclosure, verify that at least one PCM battery in each controller nodeenclosure is functional before removing a PCM.

• Ensure that the PCM power switch is turned to the OFF position to disconnect power. Because PCMsuse a common power bus, some PCM LEDs might remain illuminated after the PCM is powered off.

• To avoid damaging any circuitry, wear an ESD strap.• Prepare a surface with an ESD mat for staging components for installation.

100 Power cooling module (-48V direct-current) replacement—Optional CSR

Replacing the -48V DC PCM in a controller node enclosure

WARNING:


CAUTION:

• To prevent overheating, the replacement of the PCM requires a maximum service time of sixminutes.

• Connecting to a DC power source outside the designated -48V DC nominal range (-36V DC to-72V DC) may damage the enclosure.


NOTE:


on the AC PCM.

Procedure

Preparation:1. Unpack the replacement -48V DC PCM and place on an ESD safe mat.2. Connect and log in to the HPE 3PAR Service Processor (SP).3. Set Maintenance Mode.4. Initiate Check Health of the storage system.


CAUTION:



5. Review the information in the alert notifications.6. Locate the failed PCM.7. Confirm on the failed PCM that the Battery Fail LED is lit solid amber.8. Turn off the power switch on the failed PCM. Some LEDs might remain illuminated after the PCM is

powered off, because PCMs use a common power bus.9. Only to be completed by a certified electrician provided by the customer: Disengage power to

the -48V DC PCM from the fuse/distribution panel and remove the power cable from the PCM. Theelectrician must remove the power cable connections from the positive terminal ( ), negativeterminal ( ), and ground terminal ( . When the plastic cap over the terminal connections isremoved, it reveals the symbols for the terminals.Removal:

Replacing the -48V DC PCM in a controller node enclosure 101

10. Remove the failed -48V DC PCM.a. With thumb and forefinger, grasp and squeeze the PCM latch to release the handle.b. Rotate the PCM release handle and slide the failed PCM out of the enclosure, and then place the


11. Remove the battery.a. At the back of the PCM, lift the battery release handle.b. Remove the battery from the battery compartment and place on the ESD safe mat.

Replacement:12. Install the battery.

a. With the battery handle in the upright position, insert the battery into the -48V DC PCM.b. Push down the handle to install.

When the battery is correctly seated, the battery and handle are aligned with the surface of the-48V DC PCM.


13. Install the replacement -48V DC PCM.a. On the ESD mat, rotate the -48V DC PCM release handle to the open position, and then carry it

to the enclosure.b. Slide the -48V DC PCM into the enclosure, and then push until the insertion mechanism starts to

engage (the handle starts to rotate).

IMPORTANT:


c. Close the handle until the latch clicks to seat the -48V DC PCM in the enclosure.d. Once inserted, pull back lightly on the PCM to ensure that it is properly engaged.

14. Only to be completed by a certified electrician provided by the customer: Install the powercable on the -48V DC PCMs and re-engage power from the fuse/distribution panel.


WARNING:

Before powering up the storage system, a certified electrician must attach all the power cablingto all the PCMs.

The power cable is connected to the -48V DC PCM with connections to the positive terminal ( ),negative terminal ( ), and ground terminal ( ).Verification:

15. Turn on the PCM and check that Power LED is on. The Battery Good LED should also be solidgreen.



Replacing a -48V DC PCM in an expansion drive enclosure

WARNING:


CAUTION:




IMPORTANT:

• After installing the DC PCMs, upgrade the HPE 3PAR OS to version 3.3.1 if applicable. The-48V DC PCMs are qualified and supported only with direct-current HPE 3PAR StoreServ 8000Storage systems running HPE 3PAR OS 3.3.1 and later versions.

• Though the -48V DC PCM has a compartment for a replaceable battery, this compartmentremains empty when the -48V DC PCM is installed in an expansion drive enclosure.

NOTE:


on the AC PCM.

104 Replacing a -48V DC PCM in an expansion drive enclosure

Procedure

Preparation:1. Unpack the replacement -48V DC PCM and place on an ESD safe mat.2. Connect and log in to the HPE 3PAR Service Processor (SP).3. Set Maintenance Mode.4. Initiate Check Health of the storage system.


CAUTION:


5. Review the information in the alert notifications.6. Locate the failed PCM.7. Confirm on the failed PCM that the Battery Fail LED is lit solid amber.8. Turn off the power switch on the failed PCM. Some LEDs might remain illuminated after the PCM is


the -48V DC PCM from the fuse/distribution panel and remove the power cable from the PCM. Theelectrician must remove the power cable connections from the positive terminal ( ), negativeterminal ( ), and ground terminal ( . When the plastic cap over the terminal connections isremoved, it reveals the symbols for the terminals.Removal:

10. Remove the failed PCM.a. With thumb and forefinger, grasp and squeeze the PCM latch to release the handle.b. Rotate the PCM release handle and slide the PCM out of the enclosure, and then place the PCM


Replacement:11. Install the replacement DC PCM.

a. On the ESD mat, rotate the -48V DC PCM release handle to the open position, and then carry itto the enclosure.

b. Slide the -48V DC PCM into the enclosure, and then push until the insertion mechanism starts toengage (the handle starts to rotate).


IMPORTANT:


c. Close the handle until the latch clicks to seat the -48V DC PCM in the enclosure.d. Once inserted, pull back lightly on the PCM to ensure that it is properly engaged.


WARNING:



13. Turn on the PCM and check that Power LED is on. The Battery Good LED should also be solidgreen.




Replacing a battery in the -48V DC PCM of a controller-node enclosure

WARNING:


CAUTION:




IMPORTANT:

If both batteries in the DC PCMs in the same controller node enclosure have failed, only replace thebattery for one DC PCM at a time.

NOTE:


on the AC PCM.

Procedure

Preparation:1. Unpack the replacement battery and place on an ESD mat.2. Connect and log in to the service processor (SP).3. Set Maintenance Mode.4. Initiate Check Health of the storage system.


CAUTION:



5. Review the information in the alert notifications.6. Locate the failed PCM.7. Confirm on the failed PCM that the Battery Fail LED is solid amber.8. Turn off the power switch on the failed PCM. Some LEDs might remain illuminated after the PCM is


the -48V DC PCM from the fuse/distribution panel and remove the power cable from the PCM. The

Replacing a battery in the -48V DC PCM of a controller-node enclosure 107

electrician must remove the power cable connections from the positive terminal ( ), negativeterminal ( ), and ground terminal ( . When the plastic cap over the terminal connections isremoved, it reveals the symbols for the terminals.Removal:

10. Remove the PCM.a. With thumb and forefinger, grasp and squeeze the PCM latch to release the handle.b. Rotate the PCM release handle and slide the PCM out of the enclosure, and then place the PCM


11. Remove the failed battery.a. At the back of the PCM, lift the battery release handle.b. Remove the battery from the battery compartment and place on the ESD safe mat.

Replacement:12. Install the replacement battery.

a. With the battery handle in the upright position, insert the battery into the -48V DC PCM.b. Push down the handle to install.

When the battery is correctly seated, the battery and handle are aligned with the surface of the-48V DC PCM.


13. Install the DC PCM.a. On the ESD mat, rotate the -48V DC PCM release handle to the open position, and then carry it

to the enclosure.b. Slide the -48V DC PCM into the enclosure, and then push until the insertion mechanism starts to

engage (the handle starts to rotate).

IMPORTANT:


c. Close the handle until the latch clicks to fully seat the -48V DC PCM in the enclosure.d. Once inserted, pull back lightly on the PCM to ensure that it is properly engaged.



WARNING:



15. Turn on the PCM and check that Battery Good LED is solid green and the Power LED is on.16. Initiate Check Health of the storage system.17. If significant time is left in the maintenance window, end the Maintenance Mode.18. Follow the return instructions provided with the replacement component.



TroubleshootingTroubleshooting issues with the storage system

Alerts issued by the storage systemAlerts are triggered by events that require intervention by the system administrator. To learn more aboutalerts, see the HPE 3PAR Alerts Reference: Customer Edition and HPE 3PAR StoreServ StorageConcepts documents available at the Hewlett Packard Enterprise Information Library Storage website.

Alerts are processed by the HPE 3PAR Service Processor (SP). The Hewlett Packard Enterprise SupportCenter (HPESC) takes action on alerts that are not customer administration alerts. Customeradministration alerts are managed by customers.


Collecting log filesFor a service event, it might be necessary to collect the HPE 3PAR Service Processor (SP) log files forHewlett Packard Enterprise Support.

Collecting HPE 3PAR SmartStart log filesTo collect the HPE 3PAR SmartStart log files for Hewlett Packard Enterprise Support, zip all the files inthis folder:C:\Users\<username>\SmartStart\log

NOTE:

You can continue to access the HPE 3PAR SmartStart log files in the Users folder after you haveremoved HPE 3PAR SmartStart from your storage system.

Collecting SP log files from the SC interfaceThe following tools collect data from the HPE 3PAR Service Processor (SP):

• Audit and Logging Information—Provides audit and logging information of an attached storagesystem and HPE 3PAR SP usage. This file is gathered as part of an SPLOR and Hewlett PackardEnterprise Support personnel can view the file using HPE Service Tools and Technical Support(STaTS).

HPE 3PAR SP audit Information is contained in the audit.log file, which provides the following auditinformation:

◦ Users who accessed the HPE 3PAR SP◦ Logon and logoff times◦ The functionality used, such as Interactive CLI.

• SPLOR—Gathers files to diagnose HPE 3PAR SP issues. The SPLOR data can be retrieved throughthe Collect support data action from the Service Processor page.

Procedure

1. Connect and log in to the HPE 3PAR SP.2. From the HPE 3PAR Service Console (SC) main menu, select Service Processor.3. Select Actions > Collect support data.4. Select SPLOR data, and then click Collect to start data retrieval.

Troubleshooting 111

When support data collection is in progress, it will start a task which will be displayed at the top of thepage. To see details for a specific collection task in Activity view, expand the task message and clickthe Details link for the task.


Collecting SP log files from the SPOCC interface

Procedure

1. Connect and log in to the HPE 3PAR Service Processor (SP).2. From the 3PAR Service Processor Onsite Customer Care (SPOCC) main menu, click Files from the

navigation pane.3. Click the folder icons for files > syslog > apilogs.4. In the Action column, click Download for each log file:

SPSETLOG.log Service Processor setup log

ARSETLOG.system_serial_number.log Storage System setup log

errorLog.log General errors

5. Zip the downloaded log files.


Troubleshooting issues with the components

Components functionsTable 1: Component functions

Component Function

alert Displays unresolved alerts

ao Displays Adaptive Optimization issues

cabling Displays drive cage cabling issues

cage Displays drive cage issues

cert Displays Certificate issues

dar Display data encryption issues

date Displays nodes having different date issues

file Displays file system issues

fs Displays Files Services health

Table Continued

112 Collecting SP log files from the SPOCC interface

Component Function

host Displays host configuration and port issues

ld Displays LD issues

license Displays license violations

network Displays Ethernet issues

node Displays node issues

pd Displays PD states or condition issues

pdch Displays chunklets state issues

port Displays port connection issues

qos Displays Quality of Service issues

rc Displays Remote Copy issues

snmp Displays issues with SNMP

task Displays failed tasks

vlun Displays VLUN issues

vv Displays VV issues

alertDisplays any unresolved alerts and shows any alerts that would be seen by showalert -n .

Format of Possible alert Exception Messages

Alert <component> <alert_text>

alert Example

Component -Identifier- --------Detailed Description--------------------Alert hw_cage:1 Cage 1 Degraded (Loop Offline)Alert sw_cli 11 authentication failures in 120 secs

alert Suggested Action

View the full Alert output using the SSMC (GUI) or the 3PAR CLIshowalert -d command.

ao• Displays Adaptive Optimization issues• Checks that all PD classes that exist on any node-pair are found on all node-pairs

Format of Possible ao Exception Messages

alert 113

AO Nodes:<nodelist> "<PDclass> PDs need to be attached to this Node pair"

ao Example

Component ------Summary Description------- QtyAO Node pairs with unmatched PD types 1

Component -Identifier- ------------Detailed Description------------AO Nodes:0&1 NL PDs need to be attached to this Node pair

ao Suggestion Action

Use the following CLI commands to view PD distribution: showpd, showpd -p -devtype NL, showpd-p -devtype NL -nodes 0,1, and showcage. In the example below, there are 72 NL PDs attachedto nodes 2&3, but none attached to nodes 0&1. Contact the Hewlett Packard Enterprise Support Centerto request support for moving NL PDs (and possibly cages) from nodes 2&3 to nodes 0&1 for yoursystem.

cli% showpd -p -devtype NL -nodes 2,3 -----Size(MB)------ ----Ports---- Id CagePos Type RPM State Total Free A B Capacity(GB)200 12:0:0 NL 7 normal 1848320 1766400 3:0:1* 2:0:1 2000201 12:1:0 NL 7 normal 1848320 1766400 3:0:1 2:0:1* 2000202 12:2:0 NL 7 normal 1848320 1765376 3:0:1* 2:0:1 2000...303 17:22:0 NL 7 normal 1848320 1765376 3:0:2 2:0:2* 2000--------------------------------------------------------------------------- 72 total 133079040 127172608

cli% showpd -p -devtype NL -nodes 0,1

cablingDisplays issues with cabling of drive enclosures.

• Cages cabled correctly to nodes• Cages cabled correctly to cage I/O modules and ports• Cages with broken cables• Cable daisy-chain lengths balanced and supported length• Cable daisy-chain order• Cages with no PDs with primary path to nodes

NOTE:

To avoid any cabling errors, all drive enclosures must have at least one or more hard drive(s)installed before powering on the enclosure.

Format of Possible cabling Exception Messages

114 cabling

Cabling <cageID> "Cabled to <nodelist>, remove a cable from <nodelist>"Cabling <nodeID> "No cabling data for <nodeID>. Check status of <nodeID>"Cabling <cageID> "Cage is connected to too many node ports (<portlist>)"Cabling <cageID> "Cage has multiple paths to <portlist>, correct cabling"Cabling <cageID> "I/O <moduleID> missing. Check status and cabling to <cageID> I/O <moduleID>"Cabling <cageID> "Cage not connected to <nodeID>, move one connection from <nodeID> to <nodeID>"Cabling <cageID> "Cage connected to different ports <node&portID> and <node&portID>"Cabling <cageID> "Cage connected to non-paired nodes <node&portID> and <node&portID>"Cabling <cageID> "Check connections or replace cable from (<cage,module,portID>) to (<cage,module,portID>) - failed links"Cabling <cageID> "Check connections or replace cable from (<cage,module,portID>) to (<cage,module,portID>) - links at <speed>"Cabling <nodepairID> "<node&portID> has <count> cages, <node&portID> has <count> cages"Cabling <cageID> "Cable in (<cage,module,portID>) should be in (<cage,module,portID>)"Cabling <cageID> "No PDs installed in cage, cabling check incomplete"Cabling <cageID> "<node&portID> has <count> cages connected, Maximum is <count> (<cagelist>)"Cabling <cageID> "<node&portID> should be cabled in the order: (<cagelist>)"

cabling Example 1

Component -Summary Description- QtyCabling Bad SAS connection 1

Component -Identifier- ----------------------------------------Detailed Description-----------------------------------------Cabling cage7 Check connections or replace cable from (cage6, I/O 0, DP-2) to (cage7, I/O 0, DP-1) - links at 6Gbps

cabling Suggested Action 1

Use the CLI showcage command to verify that both cages are available through two ports, beforereplacing the cable specified in the error message.

cli% showcage cage6 cage7

Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model FormFactor 6 cage6 0:1:1 1 1:1:1 0 10 28-30 1.76 1.76 DCS8 SFF 7 cage7 0:1:1 0 1:1:1 1 10 27-30 1.76 1.76 DCS8 SFF

cabling Example 2

Cabling

Troubleshooting 115

cli% checkhealth -detail cablingChecking cablingComponent --Summary Description--- QtyCabling Wrong I/O module or port 2-------------------------------------- 1 total 2

Component -Identifier- ---------------------Detailed Description----------------------Cabling cage2 Cable in (cage2, I/O 0, DP-2) should be in (cage2, I/O 0, DP-1)Cabling cage2 Cable in (cage2, I/O 0, DP-1) should be in (cage2, I/O 0, DP-2)-------------------------------------------------------------------------------------- 2 totalroot@jnodec103288:~# showcage cage2Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model FormFactor 2 cage2 0:1:2 1 1:1:2 0 10 13-34 402e 402e DCS7 LFF

cabling Suggested Action 2

For cables that should be moved to different ports in the same I/O module: Use the CLI showcagecommand to verify that the cage is available through two ports, before moving the cable(s) to thespecified ports. For cables that should be moved between different I/O modules and/or cages, contact theHewlett Packard Enterprise Support Center to request support for changing the cabling of your system.Moving cables on a running system can cause degraded PDs and LDs.

cli% showcage cage2

Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model FormFactor 2 cage2 0:0:2 1 1:0:2 0 10 13-34 402e 402e DCS7 LFF

cageDisplays drive cage conditions that are not optimal and reports exceptions if any of the following do nothave normal states:

• Ports• SFP signal levels (RX power low and TX failure)• Power supplies• Cage firmware (is not current)• Reports if a

servicecageoperation has been started and has not ended.

• Cages are supported for hardware platform

Format of Possible cage Exception Messages

116 cage

Cage cage:<cageid> "Missing A loop" (or "Missing B loop")Cage cage:<cageid>,mag:<magpos> "Magazine is <MAGSTATE>"Cage cage:<cageid> "Power supply <X>'s fan is <FANSTATE>"Cage cage:<cageid> "Power supply <X> is <PSSTATE>" (Degraded, Failed, Not_Present)Cage cage:<cageid> "Power supply <X>'s AC state is <PSSTATE>"Cage cage:<cageid> "Cage is in "servicing" mode (Hot-Plug LED may be illuminated)" Cage cage:<cageid> "Firmware is not current" Cage cage:<cageid> "Cage type <Model> is not supported on this platform"Cage cage:<cageid> "Missing both A and B loops"Cage cage:<cageid> "Cage state information is unavailable"

cage Example 1

Component -Summary Description- QtyCage Cages missing A loop 1

Component -Identifier- -Detailed Description--Cage cage:1 Missing A loop

cage Suggested Action 1

Troubleshooting 117

cli% showcage -d cage1

Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model FormFactor 1 cage1 0:1:1 1 1:1:1 1 8 21-23 402e 402e DCS8 SFF

-----------Cage detail info for cage1 ---------

Position: ---

Interface Board Info Card0 Card1Firmware_status Current CurrentProduct_Rev 402e 402eState(self,partner) OK,OK OK,OKVendorId,ProductId HP,DCS8 HP,DCS8Master_CPU Yes NoSAS_Addr 50050CC1178EA0BE 50050CC1178E6BBELink_Speed(DP1,DP2) 6.0Gbps,Unknown 6.0Gbps,Unknown

PS PSState ACState DCState Fan State Fan0_Speed Fan1_Speedps0 OK OK OK OK Low Lowps1 Failed Failed Failed OK Low Low

-------------Drive Info-------------- --PortA-- --PortB--Drive DeviceName State Temp(C) LoopState LoopState0:0 5000c500720387e0 Normal 21 OK OK1:0 5000c50072039188 Normal 21 OK OK2:0 5000c500720387b0 Normal 21 OK OK3:0 5000c500720395b4 Normal 21 OK OK4:0 5000c50072036fbc Normal 21 OK OK5:0 5000c50072039fc0 Normal 21 OK OK6:0 5000c50072037250 Normal 22 OK OK7:0 5000c5005737cc0c Normal 23 OK OK

Check the connection/path to the SFP in the cage and the level of signal the SFP is receiving. An RXPower reading below 100 µW signals the RX Power Low condition; typical readings are between 300 and400 µW. Helpful CLI commands are showcage -d and showcage -sfp ddm .

At least two connections are expected for drive cages, and this exception is flagged if that is not the case.

cage Example 2

Component -------------Summary Description-------------- QtyCage Degraded or failed cage power supplies 2Cage Degraded or failed cage AC power 1

Component -Identifier- ------------Detailed 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


A cage power supply or power supply fan is failed, is missing input AC power, or the switch is turned OFF.The showcage -d <cageID> and showalert commands provide more detail.

118 Troubleshooting


Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model FormFactor 1 cage1 0:1:1 1 1:1:1 1 8 21-23 402e 402e DCS8 SFF


Position: ---

Interface Board Info Card0 Card1Firmware_status Current CurrentProduct_Rev 402e 402eState(self,partner) OK,OK OK,OKVendorId,ProductId HP,DCS8 HP,DCS8Master_CPU Yes NoSAS_Addr 50050CC1178EA0BE 50050CC1178E6BBELink_Speed(DP1,DP2) 6.0Gbps,Unknown 6.0Gbps,Unknown

PS PSState ACState DCState Fan State Fan0_Speed Fan1_Speedps0 OK OK OK OK Low Lowps1 Failed Failed Failed OK Low Low

-------------Drive Info-------------- --PortA-- --PortB--Drive DeviceName State Temp(C) LoopState LoopState0:0 5000c500720387e0 Normal 21 OK OK1:0 5000c50072039188 Normal 21 OK OK2:0 5000c500720387b0 Normal 21 OK OK3:0 5000c500720395b4 Normal 21 OK OK4:0 5000c50072036fbc Normal 21 OK OK5:0 5000c50072039fc0 Normal 21 OK OK6:0 5000c50072037250 Normal 22 OK OK7:0 5000c5005737cc0c Normal 23 OK OK

cage Example 3

Component -Identifier- --------------Detailed Description----------------Cage cage:1 Cage is in "servicing" mode (Hot-Plug LED may be illuminated)


When a servicecage operation is started, it puts the targeted cage into servicing mode, and routing I/Othrough another path. When the service action is finished, the servicecage endfc command shouldbe issued to return the cage to normal status. This checkhealth exception is reported if the I/O modulecage is in servicing mode. If a maintenance activity is currently occurring on the drive cage, this conditioncan be ignored.

NOTE:

The primary path can be seen by an asterisk (*) in showpd's Ports columns.

Troubleshooting 119


Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model FormFactor1 cage1 --- 1 1:1:1 1 8 20-23 402e - DCS8 SFF


Position: ---

Interface Board Info Card0 Card1Firmware_status Current -Product_Rev 402e -State(self,partner) OK,OK -,-VendorID,ProductID HP,DCS8 -,-Master_CPU Yes -SAS_Addr 50050CC1178EA0BE -Link_Speed(DP1,DP2) 6.0Gbps,Unknown -,-

PS PSState ACState DCState Fan State Fan0_Speed Fan1_Speedps0 OK OK OK OK Low Lowps1 OK OK OK OK Low Low

-------------Drive Info------------------ ----PortA---- ----PortB----Drive DeviceName State Temp(C) LoopState LoopState 0:0 5000c500720387e0 Normal 20 - OK 0:1 5000c50072039188 Normal 21 - OK 0:2 5000c500720387b0 Normal 21 - OK 0:3 5000c500720395b4 Normal 21 - OK 0:4 5000c50072036fbc Normal 21 - OK 0:5 5000c50072039fc0 Normal 21 - OK 0:6 5000c50072037250 Normal 21 - OK 0:7 5000c5005737cc0c Normal 23 - OK

cage Example 4

SComponent ---------Summary Description--------- QtyCage Cages not on current firmware 1

Component -Identifier- ------Detailed Description------Cage cage:3 Firmware is not current


Check the drive cage firmware revision using the commands showcage and showcage -d<cageID> . The showfirwaredb command indicates what the current firmware level should be for thespecific drive cage type.

NOTE:

Use the upgradecage command to upgrade the firmware.

120 Troubleshooting

cli% showcage

Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model FormFactor0 cage0 0:1:1 0 1:1:1 0 16 13-22 402d 402d DCN2 SFF1 cage1 0:1:1 0 1:1:1 4 16 13-22 402d 402d DCN7 SFF

cli% showcage -d cage2showfirmwaredb

cert• Displays Certificate issues• Reports SSL certificates that have expired, will expire in less than 30 days, and certificates that will not

be valid until a future date

Format of Possible cert Exception Messages

cert -- "Certificate <DNSname> for Service:<servicename> will expire in <count> days"cert -- "Certificate <DNSname> for Service:<servicename> expired on <date&time>"cert -- "Certificate <DNSname> for Service:<servicename> not valid until <date&time>"

cert Example

cli% checkhealth -detail certChecking certComponent -----Summary Description------ Qtycert Certificates that have expired 1 Component -Identifier- -----------------------------Detailed Description----------------------------cert -- Certificate example.com for Service:wsapi expired on Jul 20 22:36:26 2014 GMT

cert Suggested Action

Use the CLI showcert command to display the current SSL certificates. Use the CLI removecertcommand to remove the expired SSL certificate and the CLI createcert command to create a SSLcertificate with a valid date range.

darChecks for issues with Data Encryption. If the system is not licensed for Data Encryption.

Format of Possible dar Exception Messages

cert 121

DAR -- "DAR Encryption status is unavailable"DAR -- "DAR Encryption is enabled but not licensed"DAR -- "DAR Encryption key needs backup"DAR -- "There are <number> disks that are not Self Encrypting"DAR -- "DAR Encryption status: <dar state>"DAR -- "DAR EKM status is: <EKM status>"

dar Example 1

DAR -- "There are 5 disks that are not self-encrypting"

dar Suggested Action 1

Remove the drives that are not self-encrypting from the system because the non-encrypted drives cannotbe admitted into a system that is running with data encryption. Also, if the system is not yet enabled fordata encryption, the presence of these drives prevents data encryption from being enabled.

dar Example 2

Dar -- "DAR Encryption key needs backup"


Issue the controlencryption backup command to generate a password-enabled backup file.

dar Example 3

DAR -- DAR EKM status is: Error: Unable to access EKM. Configuration or connection issue.


Use the controlencryption status -d and controlencryption checkekm cli commands toview more status about encryption. Check network status for nodes with shownetand shownet -d clicommands. Check the EKM server's status and the network connections and status.

dateChecks the date and time on all nodes and reports an error if they are not the same.

Format of Possible date Exception Messages

122 date

Date -- "Date is not the same on all nodes"

date Example

Component -Identifier- -----------Detailed Description-----------Date -- Date is not the same on all nodes

date Suggested Action

The time on the nodes should stay synchronized whether there is an NTP server or not. Use showdateto see if a node is out of sync. Use shownet and shownet -d to see the network and NTP information.NTP will not adjust the time for significant time differences, use the setdate cli command to set the time,date and time zone on all nodes.

cli% showdate

Node Date0 2010-09-08 10:56:41 PDT (America/Los_Angeles)1 2010-09-08 10:56:39 PDT (America/Los_Angeles)

cli% shownetshowdatesetdate -tz America/Denversetdate 05211532showdate

fileDisplays file system conditions that are not optimal:

• Checks that required system volumes are mounted• Checks for process, kernel and HBA cores on node disk drives• Checks for node file systems that are too full• Checks for behavior altering files on the node disk drives• Checks if an online upgrade is in progress

Many issues reported by the file component will require you to contact the Hewlett Packard EnterpriseSupport Center to request support your system.

Format of Possible file Exception Messages

File <nodeID> "Filesystem <filesystem> mounted on "<mounted on>" is over <count>% full"File <nodeID> "Behavior altering file "<filename>" exists, created on <date&time>"File <nodeID> "Dump or HBA core files found"File <nodeID> "sr_mnt is full"File -- "sr_mnt not mounted"File -- "Admin Volume is not mounted"File -- "An online upgrade is in progress"

file Example 1

file 123

File node:2 Behavior altering file "manualstartup" exists created on Oct 7 14:16

file Suggested Action 1

After understanding why the files are present, the file should be removed to prevent unwanted behavior.As root on a node, remove the file using the UNIX rm command.

Known condition: some undesirable touch files are not being detected (bug 45661).

file Example 2

Component -----------Summary Description----------- QtyFile Admin Volume is not mounted 1


Each node has a file system link so that the admin volume can be mounted if that node is the masternode. This exception is reported if the link is missing or if the System Manager (sysmgr) is not running atthe time. For example, sysmgr might have been restarted manually, due to error or during a change ofmaster-nodes. If sysmgr was restarted, it tries to remount the admin volume every few minutes.

Every node should have the following file system link so that the admin volume can be mounted, shouldthat node become the master node:

# onallnodes ls -l /dev/tpd_vvadminNode 0:lrwxrwxrwx 1 root root 12 Oct 23 09:53 /dev/tpd_vvadmin -> tpddev/vvb/0Node 1:ls: /dev/tpd_vvadmin: No such file or directory

The corresponding alert when the admin volume is not properly mounted is as follows:

Message Code: 0xd0002Severity : MinorType : PR transitionMessage : The PR is currently getting data from the internal drive on node 1, not the admin volume. Previously recorded alerts will not be visible until the PR transitions to the admin volume.

If a link for the admin volume is not present, it can be recreated by rebooting the node.

file Example 3

124 Troubleshooting

Component -----------Summary Description----------- QtyFile Nodes with Dump or HBA core files 1

Component ----Identifier----- ----Detailed Description------ File node:1 Dump or HBA core files found


This condition might be transient because the Service Processor retrieves the files and cleans up thedump directory. If the Service Processor (SP) is not gathering the dump files, check the condition andstate of the SP.

file Example 4

Component ------Summary Description------- QtyLicense An online upgrade is in progress 1

Component -Identifier- ------Detailed Description------File -- An online upgrade is in progress


Use the CLI upgradesys -status command to determine the status of the online upgrade in progress.Use the CLI upgradesys -node <nodeID> command to reboot the next node shown in the status orthe CLI upgradesys -finish command to complete the upgrade after all nodes have been rebootedto the new version of software. Be very careful with aborting or reverting an offline upgrade. Contact theHewlett Packard Enterprise Support Center to request support for aborting or reverting the upgrade ofyour system.

fsDisplays File Services health and checks the following File Services items:

• Check the health of File Services and the failover/health of each Storage Pool• Check the health of each Virtual File Server• Check the health of the node IP Addresses for File Services• Check the health of the File Services gateway

Format of Possible fs Exception Messages

fs 125

fs fpg "<error text>"fs <poolname> "<poolname> is degraded: Failed over from <primaryowner> to <currentowner>"fs <poolname> "<poolname>: <associatedMessage>. Corrective Action: <correctiveAction>fs vfs "<error text>"fs <server> "IP address failed to activate"fs <server> "Missing fsip for VFS"fs <server> "Missing cert for VFS"fs fshareobj "<error text>"fs <sharename> "<fpg/vfs/store/sharename>: <associatedMessage>. Corrective Action: <correctiveAction>"fs nodeip "<error text>"fs <nodeaddr> "<nodecuid:nodeaddr>: <associatedMessage>. Corrective Action: <correctiveAction>"fs gw "<error text>"fs <gatewayaddr> "<gatewayaddr>: <associatedMessage>"fs dns "<error text>"fs <dnssuffixlist> "<dnsaddresslist>: <associatedMessage>"

fs Example

Component ---------Summary Description----------- Qtyfs File Services provisioning group issues 1

Component -Identifier- -------------------Detailed Description--------------------fs fsp2 fsp2: FPG is not activated. Corrective Action: Activate FPG

fs Suggested Action

Use the CLI showfpg command to determine the state of the listed FPG. Use the CLI setfpg andsetfpg -activate commands to start the listed FPG or the CLI removefpg command to remove theFPG if no longer wanted. For other File Services issues, use the CLI showfs, showvfs, showvfscommands (and the associated set and stop commands) to investigate and solve issues.

host• Displays Adaptive Optimization issues• Checks that all PD classes that exist on any node-pair are found on all node-pairs• Checks that FC Fabric connected host ports are configured to support Persistent Ports• Checks that the FC switch ports are configured for NPIV support• Checks that FC Fabric connected host partner ports are found on same FC SAN• Checks that VLUNs are visible to their configured host through more than one node

Format of Possible host Exception Messages

126 host

Host <portID> "Port failover state is <failoverstate>, port state is <state>"Host <portID> "Port not connected to fabric like <portID>"Host <portID> "Port not configured as host like <portID>"Host <portID> "Port not FC like <portID>"Host <portID> "Port state is <state>, not ready like <portID>"Host <portID> "Port WWN not found on FC Fabric attached to <portID>"Host <portID> "Host port connected to FC Fabric switch port without NPIV support"Host <portID> "Host is not seen by multiple nodes, only seen from node <nodeID>"

host Example 1

Component -------Summary Description-------- QtyHost Ports not configured symmetrically 1

Component -Identifier- ------------Detailed Description------------Host Port:0:1:1 Port not connected to fabric like Port:1:1:1

host Action 1

Use the CLI showport, showport -par, and controlport commands to configure port 1:0:1 forpoint mode (fabric connect) or configure port 0:1:1 to loop mode (for direct connect).

cli% showport -par 0:0:1 1:0:1

N:S:P Connmode ConnType CfgRate MaxRate Class2 UniqNodeWwn VCN IntCoal TMWO Smart_SAN0:1:1 host loop auto 8Gbps disabled disabled disabled disabled enabled n/a1:0:1 host point auto 8Gbps disabled disabled disabled disabled enabled n/a

host Example 2

Component ------Summary Description------- Qtyhost Hosts not seen by multiple nodes 1

Component -Identifier- ------------------Detailed Description-------------------host testhost Host is not seen by multiple nodes, only seen from node 3

host Action 2

Use CLI showvlun -v and showhost commands to determine what issue is reported. If the host isdefined with only connections from one node, use the CLI createhost -add command to add host

Troubleshooting 127

connections for an additional to the host definitions. If the host is defined with ports from multiple nodes,use the CLI showport command to determine if a port is offline or misconfigured. A missing or rebootingnode will cause a port to be offline.

cli% showvlun -v testvvActive VLUNsLun VVName HostName -Host_WWN/iSCSI_Name- Port Type Status ID 2 testvv testhost 10000000C9E5E0B9 3:1:1 host active 1

cli% showhost testhostcreatehost -add testhost 10000000C9E5E0B8showhost testhost

ldChecks the following and displays Logical Drives (LDs) that are not optimal:

• Preserved LDs• Verfies that current and created availability are the same• Owner and backup are correct• Verfies preserved data space (

pdsld) is the same as total data cache

• Size and number of logging LDs• LDs that are in failed or degraded state• LDs are mapped to volumes• LDs that are in write-through mode

Format of Possible ld Exception Messages

LD 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" 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> "Logical Disk is owned by <owner>, but preferred owner is <powner>"LD ld:<ldname> "Logical Disk is backed by <backup>, but preferred backup is <pbackup>"LD ld:<ldname> "A logging LD is smaller than 20G in size" LD ld:<ldname> "Detailed State:<ldstate>" (degraded or failed)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"

ld Example 1

128 ld

Component -------Summary Description-------- QtyLD LDs not mapped to a volume 1

Component -Identifier-- --------Detailed Description---------LD ld:vv.9.usr.3 LD is not mapped to a volume

ld Suggested Action 1

Examine the identified LDs using CLI commands such as showld, showld –d , showldmap,showvvmap, and other such commands.

LDs are normally mapped to (used by) VVs but they can be disassociated with a VV if a VV is deletedwithout the underlying LDs being deleted, or by an aborted tune operation. Normally, you would removethe unmapped LD to return its chunklets to the free pool.

cli% showld vv.9.usr.3

Id Name RAID -Detailed_State- Own SizeMB UsedMB Use Lgct LgId WThru MapV

57 vv.9.usr.3 1 normal 1/0 8192 0 C,V 0 --- N N--------------------------------------------------------------------- 1 8192 0

cli% showldmap vv.9.usr.3Ld space not used by any vv

ld Example 2

Component -------Summary Description-------- QtyLD LDs in write through mode 3

Component -Identifier-- --------Detailed Description---------LD ld:Ten.usr.12 LD is in write-through mode


Examine the identified LDs using CLI commands such as showld, showld –d , showldch, andshowpd for any failed or missing drives. Write-through mode (WThru) indicates that host I/O operationsmust be written through to the drive before the host I/O command is acknowledged. This is usually due toa node-down condition, when node batteries are not working, or where drive redundancy is not optimal.

Troubleshooting 129

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.12showpd 104

ld Example 3

Component ---------Summary Description--------- QtyLD LDs with reduced availability 1

Component --Identifier-- ------------Detailed Description---------------LD ld:R1.usr.0 LD has reduced availability. Current: ch, Configured: cage


LDs are created with certain high-availability characteristics, such as -ha -cage. If chunklets in an LDget moved to locations where the Current Availability (CAvail) is not at least as good as the desired levelof availability (Avail), this condition is reported. Chunklets might have been manually moved withmovech or by specifying it during a tune operation or during failure conditions such as node, path, or cagefailures. The HA levels from highest to lowest are port, cage, mag, and ch (disk).

Examine the identified LDs using CLI commands such as showld, showld –d , showldch, andshowpd for any failed or missing drives. In the example below, the LD should have cage-level availability,but it currently has chunklet (drive) level availability (the chunklets are on the same drive).

cli% showld -d R1.usr.0

Id 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.0

ld Example 4

Component -Identifier-- -----Detailed Description-------------LD -- Preserved data storage space does not equal total node's Data memory

130 Troubleshooting

ld Suggested Action 4Preserved data LDs (pdsld) are created during system initialization (OOTB) and after some hardwareupgrades (via admithw). The total size of the pdsld should match the total size of all data-cache in thestorage system (see below). This message appears if a node is offline because the comparison of LDsize to data cache size does not match. This message can be ignored unless all nodes are online. If allnodes are online and the error condition persists, determine the cause of the failure. Use the admithwcommand 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*

licenseDisplays license violations. Returns information if a license is temporary or if it has expired.

Format of Possible license Exception Messages

License <feature_name> "License has expired"

license Example

Component -Identifier- --------Detailed Description-------------License -- System Tuner License has expired

license Suggested Action

If desired, request a new or updated license from your Sales Engineer.

networkDisplays Ethernet issues for the Administrative, File Services, and Remote Copy over IP (RCIP) networksthat have been logged in the previous 24-hour sampling window. Reports if the storage system has fewerthan two nodes with working admin Ethernet connections.

• Check whether the number of collisions is greater than 5% of total packets in previous day’s log.• Check for Ethernet errors and transmit (TX) or receive (RX) errors in previous day’s log.

Format of Possible network Exception Messages

license 131

Network -- "IP address change has not been completed" Network "Node<node>:<type>" "Errors detected on network"Network "Node<node>:<type>" "There is less than one day of network history for this node"Network -- "No nodes have working admin network connections"Network -- "Node <node> has no admin network link detected"Network -- "Nodes <nodelist> have no admin network link detected"Network -- "checkhealth was unable to determine admin link status

network Example 1

Network -- "IP address change has not been completed"

network Suggested Action 1

The setnet command was issued to change some network parameter, such as the IP address, but theaction has not been completed. Use setnet finish to complete the change, or setnet abort tocancel. 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

network Example 2

Component ---Identifier---- -----Detailed Description----------Network Node0:Admin Errors detected on network

network Suggested Action 2

Network errors have been detected on the specified node and network interface. Commands such asshownet and shownet -d are useful for troubleshooting network problems. These commands displaycurrent network counters as checkhealth compares error with the last logging sample.

NOTE:

The error counters shown by shownet and shownet -d cannot be cleared except by rebooting acontroller node. Because checkhealth is comparing network counters with a history log,checkhealth stops reporting the issue if there is no increase in error in the next log entry.

132 Troubleshooting

cli% shownet -dIP Address: 192.168.56.209 Netmask 255.255.255.0 Assigned to nodes: 0123Connected through node 0Status: Active

Admin interface on node 0MAC 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

pdDisplays Physical Drives (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 drives than Port-B• Checks for an Unknown Sparing Algorithm. For example, when it hasn't been set

• Checks for drives experiencing a high number of IOPS• Reports if a servicemag operation is outstanding (servicemag status)• Reports if there are PDs that do not have entries in the firmware DB file• Reports PDs with slow SAS connections• Reports minimum number of PDs in a cage and behind a node pair• Reports PDs that are not admitted to the system

Format of Possible pd Exception Messages

pd 133

PD disk:<pdid> "Degraded States: <showpd -s -degraded>"PD disk:<pdid> "Failed States: <showpd -s -failed">PD -- "Sparing algorithm is not set"PD disk:<pdid> "Disk is experiencing a high level of I/O per second: <iops>" PD File: <filename> "Folder not found on all Nodes in <folder>"PD File: <filename> "Folder not found on some Nodes in <folder>"PD File: <filename> "File not found on all Nodes in <folder>"PD File: <filename> "File not found on some Nodes in <folder>"PD Disk:<pdID> "<pdmodel> PD for cage type <cagetype> in cage position <pos> is missing from firmware database" PD Cage:<cageID> "There must be at least 1 PD with primary path to Node:<nodeID>"PD Cage:<cageID> "PDs <class/rpm/cap> unbalanced. Primary path: <p_count> on Node:<nodeID>, <c_count> on Node:<nodeID>"PD Nodes:<nodelist> "Only <count> <class/rpm/cap> PDs are attached to these nodes; the minimum is <MINDISKCNT>"PD pd:<pdID> "PD SAS speed is <speed> instead of <speed> on both ports"PD pd:<pdID> "PD SAS speed is <speed> instead of <speed> from port <0|1>"PD disk:<pdWWN> "Unadmitted PD in cage position <CagePos> Type <devType>"PD cage:<cageID>,mag:<magID> "Magazine has a failed servicemag operation"PD cage:<cageID>,mag:<magID> "Magazine is being serviced"PD cage:<cageID>,mag:<magID> "Magazine has an active servicemag operation in progress"

pd Example 1

Component -------------------Summary Description------------------- QtyPD PDs that are degraded or failed 40

Component -Identifier- ---------------Detailed Description-----------------PD disk:48 Detailed State: missing_B_port,loop_failure PD disk:49 Detailed State: missing_B_port,loop_failure ...PD disk:107 Detailed State: failed,notready,missing_A_port

pd Suggested Action 1

Both degraded and failed drives show up in this report. When an FC path to a drive cage is not working,all drives in the cage have a state of Degraded due to the non-redundant condition. Use commands suchas showpd, showpd -s, showcage, showcage -d.

134 Troubleshooting

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:2* ----- 49 3:1:0 FC 10 degraded 139520 121344 2:0:2* -----…107 4:9:3 FC 15 failed 428800 0 ----- 3:0:1*

cli% showpd -s -degraded -failedshowcage -d cage3

pd Example 2

cli% checkhealth -detail pdChecking pdComponent -------------------Summary Description------------------- QtyPD Unbalanced PD types in cages 1PD PDs that a degraded 1------------------------------------------------------------------------ 2 total 2

Component --Identifier-- ----------------------------Detailed Description----------------------------PD Cage:0 PDs FC/10K/450GB unbalanced. Primary path: 5 on Node:0,3 on Node:1PD disk:0 Degraded States: missing_A_port,servicing-------------------------------------------------------------------------------------------- 2 total


The primary and secondary I/O paths for drives (PDs) are balanced between nodes. The primary path isindicated in the showpd -path output and by an asterisk in the showpd output. An imbalance of activeports is usually caused by a non-functioning path/loop to a cage, or because an odd number of drives isinstalled or detected, or drives were installed in the wrong slots. To diagnose further, use CLI commandssuch as showpd, showpd -path, showcage, and showcage -d.

Troubleshooting 135

cli% showcage -d cage0Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model FormFactor 0 cage0 0:1:1 0 1:1:1 0 8 20-22 402e 402e DCN2 SFF


Position: ---

Interface Board Info Card0 Card1Firmware_status Current CurrentProduct_Rev 402e 402eState(self,partner) OK,OK OK,OKVendorID,ProductID HP,DCN2 HP,DCN2Master_CPU Yes NoSAS_Addr 50050CC10230567E 50050CC10230567ELink_Speed(DP1,Internal) 6.0Gbps,6.0Gbps 6.0Gbps,6.0Gbps

PS PSState ACState DCState Fan State Fan0_Speed Fan1_Speedps0 OK OK OK OK Low Lowps1 OK OK OK OK Low Low

-------------Drive Info------------------ ----PortA---- ----PortB----Drive DeviceName State Temp(C) LoopState LoopState 0:0 5000c500725333e0 Normal 20 OK OK 0:1 5000c50072533d24 Normal 21 OK OK 0:2 5000c500725314a0 Normal 21 OK OK 0:3 5000c50072531bf4 Normal 22 OK OK 0:4 5000c50072531c74 Normal 22 OK OK 0:5 5000c50072531ec8 Normal 21 OK OK 0:6 5000c50072531384 Normal 22 OK OK 0:7 5000c5005f4848bc Normal 22 OK OK

cl% showpd

pd Example 3

Component -------------------Summary Description------------------- QtyPD Disks experiencing a high level of I/O per second 93

Component --Identifier-- ---------Detailed Description---------- PD disk:100 Disk is experiencing a high level of I/O per second: 789.0


This check samples the I/O per second (IOPS) information in statpd to see if any drives are beingoverworked, and then it samples again after five seconds. This does not necessarily indicate a problem,but it could negatively affect system performance. The IOPS thresholds currently set for this condition are:

• NL drives < 75• FC 10K RPM drives < 150• FC 15K RPM drives < 200• SSD < 12000

136 Troubleshooting

Operations such as servicemag and tunevv can cause this condition. If the IOPS rate is very highand/or a large number of drives are experiencing very heavy I/O, examine the system further usingstatistical monitoring commands/utilities such as statpd, the SSMC (GUI) and System Reporter. Thefollowing example reports drives 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

pd Example 4

Component --Identifier-- -------Detailed Description----------PD disk:3 Detailed State: old_firmware


The identified drive does not have firmware that the storage system considers current. When a drive isreplaced, the servicemag operation should upgrade the drive's firmware. When drives are installed oradded to a system, the admithw command can perform the firmware upgrade. Check the state of thedrive using CLI commands such as showpd -s , showpd -i , and showfirmwaredb.

cli% showpd -s 3Id CagePos Type -State-- -Detailed_State- --SedState 3 0:3:0 FC degraded old_firmware fips_capable ------------------------------------------------------ 1 total

cli% showpd -i 3showfirmwaredb

pd Example 5

Component --Identifier-- -------Detailed Description----------PD -- Sparing Algorithm is not set


Check the system’s Sparing Algorithm value using the CLI command showsys -param . The value isnormally set during the initial installation (OOTB). If it must be set later, use the command setsysSparingAlgorithm ; valid values are Default, Minimal, Maximal, and Custom. After setting theparameter, use the admithw command to programmatically create and distribute the spare chunklets.

Troubleshooting 137

cli% showsys -paramSystem parameters from configured settings

----Parameter----- --Value--RawSpaceAlertFC : 0RawSpaceAlertNL : 0RawSpaceAlertSSD : 0RemoteSyslog : 0RemoteSyslogHost : 0.0.0.0SparingAlgorithm : Unknown

pd Example 6

Component --Identifier-- -------Detailed Description----------PD Disk:32 ST3400755FC PD for cage type DCS2 in cage position 2:0:0 is missing from the firmware database


Check the release notes for mandatory updates and patches to the HPE 3PAR OS version that isinstalled and install as needed to support this PD in this cage.

pdch• Displays chunklets state issues• Checks LD connection paths, remote chunklets, and remote disks

Format of Possible pdch Exception Messages

pdch LD:<ldid> "Connection path is not the same as LD ownership" pdch ch:<initpdid>:<initpdpos> "Chunklet is on a remote disk" pdch LD:<ldid> "LD has <count> remote chunklets"

pdch Example 1

Component ------------Summary Description------------ Qtypdch LDs wwith connection path different than ownership 1

Component -Identifier- -------Detailed Description--------pdch ld:tp-0-sd-0.1 Connection path is not the same as LD ownership

pdch Suggested Action 1

Use the CLI showld, showpd, and shownode commands. If the ownership issue is not created due to anode missing or failed PD, Contact the Hewlett Packard Enterprise Support Center to request support formoving the LDs to the desired location for your system.

138 pdch

cli% showldId Name RAID -Detailed_State- Own SizeMB UsedMB Use Lgct LgId WThru MapV19 pdsld0.0 1 normal 1/0 256 0 P,F 0 --- Y N20 pdsld0.1 1 normal 1/0 7680 0 P 0 --- Y N21 pdsld0.2 1 normal 1/0 256 0 P 0 --- Y N

pdch Example 2

Component -------------------Summary Description------------------- Qtypdch LDs with connection path different than ownership 23pdch LDs with chunklets on a remote disk 18

Component -Identifier- ---------------Detailed Description--------------pdch LD:35 Connection path is not the same as LD ownershippdch ld:35 LD has 1 remote chunklet

pdch Suggested Action 2

The primary I/O paths for drives are balanced between the two nodes that are physically connected to thedrive cage. The node that normally has the primary path to a drive is considered the owning node. If thesecondary node's path has to be used for I/O to the drive, that is considered remote I/O.

These messages usually indicate a node-to-cage FC path problem because the drives (chunklets) arebeing accessed through their secondary path. These are usually a by product of other conditions such asdrive-cage/node-port/FC-loop problems; focus on troubleshooting those. If a node is offline due to aservice action, such as hardware or software upgrades, these exceptions can be ignored until that actionhas finished and the node is online.

In this example, LD 35, with a name of R1.usr.3, is owned (Own) by nodes 3/2/0/1, respectively, and theprimary/secondary physical paths to the drives (chunklets) in this LD are from nodes 3 and 2,respectively. However, the FC path (Port B) from node 3 to PD 91 is failed/missing, so node 2 isperforming the I/O to PD 91. When the path from node 3 to cage 3 gets fixed (N:S:P 3:0:4 in thisexample), this condition should disappear.

cli% showldId Name RAID -Detailed_State- Own SizeMB UsedMB Use Lgct LgId WThru MapV35 R1.usr.3 1 normal 3/2/0/1 256 256 V 0 --- N Y

cli% showldch R1.usr.3showpd -s -failed -degradedshowcage

Normal condition (after fixing):

Troubleshooting 139

cli% showpd 91 63

----Size(MB)---- ----Ports---- Id CagePos Type Speed(K) State Total Free A B 63 2:2:3 FC 10 normal 139520 124416 2:0:3* 3:0:3 91 3:8:3 FC 10 normal 139520 124416 2:0:4 3:0:4*

portChecks for the following port connection issues:

• Ports in unacceptable states• 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• Degraded SFPs and those with low power; perform this check only if this FC Adapter type uses SFPs• Ports listed as hosts in "showhost" that are not ready or not configured as host• Host ports or systesm with too many initiators connected

Format of Possible port Exception Messages

Port 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 <state>" (degraded or failed) Port port:<nsp> "SFP is disabled" Port port:<nsp> "Receiver Power Low: Check FC Cable" Port port:<nsp> "Transmit Power Low: Check FC Cable" Port port:<nsp> "SFP has TX fault" Port port:<portID> "Port listed as host path but is State:<state>, Mode:<mode> and Type:<type>"Port port:<portID> "<count> initiators attached exceeds the supported limit of <max port count>"Port -- "Connected <protocol> host initiators of <count> exceeds the supported limit of <max system count>"

port Suggested Actions, General

Some specific examples are displayed below, but in general, use the following CLI commands to checkfor these conditions:

• For port SFP errors, use commands such as

showport,

showport -sfp, and

showport -sfp -ddm.

port Example 1

140 port

Component ------Summary Description------ QtyPort Degraded or failed SFPs 1

Component -Identifier- --Detailed Description--Port port:0:1:1 SFP is Degraded

port Suggested Action 1

An SFP in a Node-Port is reporting a degraded condition. This is most often caused by the SFP receivercircuit detecting a low signal level (RX Power Low), and that is usually caused by a poor or contaminatedFC connection, such as a cable. An alert should identify the condition, such as the following:

Port 0:1:1, SFP Degraded (Receiver Power Low: Check FC Cable)

Check SFP statistics using CLI commands such as showport -sfp, showport -sfp -ddm.

cli% showport -sfp 0:1:1N:S:P -State-- -Manufacturer- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM0:1:1 OK HP-F 8.5 No No No Yes-------------------------------------------------------------------------- 1

In the following example an RX power level of 522 microwatts (uW) for Port 0:1:1 DDM is a good reading;and 12 uW for Port 1:1:1 is a weak reading ( < 15 uW). Normal RX power level readings are 300-700 uW.

cli% showport -sfp -ddm 0:1:1 1:1:1--------------Port 0:1:1 DDM-------------- -Warning- --Alarm----Type-- Units Reading Low High Low HighTemp C 29 -5 85 -10 90 Voltage mV 3339 3000 3600 2900 3700TX Bias mA 8 2 14 1 17 TX Power uW 478 158 562 125 631 RX Power uW 522 15 1000 10 1258

--------------Port 1:1:1 DDM-------------- -Warning- --Alarm----Type-- Units Reading Low High Low HighTemp C 33 -5 85 -10 90 Voltage mV 3332 3000 3600 2900 3700TX Bias mA 7 2 14 1 17 TX Power uW 476 158 562 125 631 RX Power uW 98 15 1000 10 1258

port Example 2

Troubleshooting 141

Component -Summary Description- QtyPort Missing SFPs 1

Component -Identifier- -Detailed Description--Port port:0:3:1 SFP is missing


FC node-ports that normally contain SFPs will report an error if the SFP has been removed. The conditioncan be checked using the showport -sfp command. In this example, the SFP in 1:1:1 has beenremoved from the adapter:

cli% showport -sfpN:S:P -State- -Manufacturer- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM0:1:1 OK HP-F 8.5 No No No Yes0:1:2 OK HP-F 8.5 No No Yes Yes1:1:1 - - - - - - - 1:1:2 OK HP-F 8.5 No No Yes Yes

port Example 3

cli% checkhealth -detail port


Check the state of the port with showport. If a port is offline, it was deliberately put in that state using thecontrolport offline command. Offline ports might be restored using controlport rst.

cli% showportN:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol Label Partner FailoverState...0:0:1 target ready 2FF70002AC00006E 20110002AC00006E host FC - 1:0:1 none0:0:2 target offline 2FF70002AC00006E 20120002AC00006E free FC - 1:0:2 none...

port Example 4

Component ------------Summary Description------------ QtyPort Ports with mismatched mode and type 1

Component -Identifier- ------Detailed Description-------Port port:2:0:3 Mismatched mode and type

142 Troubleshooting


This output indicates that the port's mode, such as an initiator or target, is not correct for the connectiontype, such as drive, host, ISCSI, FCoE, or RCFC. Useful HPE 3PAR CLI commands are showport,showport -c, showport -par, showport -rcfc, showcage, etc.

cli% showport

Component -Identifier- ------Detailed 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

qos• Displays Quality of Service (QOS) issues• Checks for Quality of Service rejects over the previous 24 hours

Format of Possible qos Exception Messages

QOS <vvsetname> "VVSet has logged <count> rejects in 24 hours"

qos Example

Component -------Summary Description-------- QtyQoS VVSets with non-zero reject counts 1

Component -Identifier- -----------Detailed Description------------QoS vvset6 VVSet has logged 1756.0 rejects in 24 hours

qos Suggested Action

Use the CLI showqos command to determine if the QOS rules fit the needs of the host and applicationaccess. If the QOS rules for this vvset need to be adjusted or removed, use the CLI setqos commandto set new limits, to remove or disable the QOS rules for this vvset. If the QOS rules appear correct, usethe CLI statvv command to determine if there are other VVs that are causing QOS to reject I/O requestsfor this vvset. Either change the QOS rules to match the host/application load or adjust the load to theVVs on this system.

rcChecks for the following Remote Copy issues.

• Remote Copy targets• Remote Copy links• Remote Copy Groups and VVs

qos 143

• Remote Copy internal structure• Too many Remote Copy targets configured as sync

Format of Possible rc Exception Messages

RC 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>." RC Structure "Remote Copy internal structure is incompatible."RC rc: "Target" "More than 8 sync targets have been setup."

rc Example

Component --Detailed Description-- QtyRC Stale volumes 1

Component --Identifier--- ---------Detailed Description---------------RC rc:yush_tpvv.rc VV yush_tpvv.rc of group yush_group.r1127 is stale on target S400_Async_Primary.

rc Suggested Action

Perform remote copy troubleshooting such as checking the physical links between the storage system,and using CLI commands such as showrcopy, showrcopy -d , showport -rcip , showport -rcfc , shownet -d , controlport rcip ping , etc.

snmpDisplays issues with SNMP. Attempts the showsnmpmgr command and reports errors if the CLI returnsan error.

Format of Possible snmp Exception Messages

SNMP -- <err>

snmp Example

Component -Identifier- ----------Detailed Description---------------SNMP -- Could not obtain snmp agent handle. Could be misconfigured.

snmp Suggested Action

Any error message that can be produced by showsnmpmgr might be displayed.

144 snmp

spChecks the status of the Ethernet connection between the Service Processor (SP) and nodes.

This can only be run from the SP because it performs a short Ethernet transfer check between the SPand the storage system.

Format of Possible sp Exception Messages

Network SP->InServ "SP ethernet Stat <stat> has increased too quickly check SP network settings"

sp Example

Component -Identifier- --------Detailed Description------------------------SP ethernet "State rx_errs has increased too quickly check SP network settings"

sp Suggested Action

The <stat> variable can be any of the following: rx_errs, rx_dropped, rx_fifo, rx_frame,tx_errs, tx_dropped, tx_fifo.

This message is usually caused by customer network issues, but might be caused by conflicting ormismatching network settings between the Service Processor (SP), customer switch(es), and the storagesystem. Check the SP network interface settings using the SPMAINT interface or SPOCC. Check thestorage system settings using commands such as shownet and shownet -d .

taskDisplays failed tasks. Checks for any tasks that have failed within the past 24 hours. This is the defaulttime frame for the showtask -failed all command.

Format of Possible task Exception Messages

Task Task:<Taskid> "Failed Task"

task Example

Component --Identifier--- -------Detailed Description--------Task Task:6313 Failed Task

In this example, checkhealth also showed an Alert. The task failed, because the command wasentered with a syntax error:

sp 145

Component -Identifier- --------Detailed Description------------------------Alert sw_task:6313 Task 6313 (type 'background_command', name 'upgradecage -a -f') has failed (Task Failed). Please see task status for details.

task Suggested Action

The CLI command showtask -d <Task_id> will display detailed information about the task. To cleanup the Alerts and the Alert-reporting of checkhealth, you can delete the failed-task alerts if they are ofno further use. They will not be auto-resolved and they will remain until they are manually removed withthe SSMC (GUI) or CLI with removealert or setalert ack . To display system-initiated tasks, useshowtask -all .

cli% showtask -d 6313 Id Type Name Status Phase Step 6313 background_command upgradecage -a -f failed --- ---

Detailed status is as follows:

2010-10-22 10:35:36 PDT Created task.2010-10-22 10:35:36 PDT Updated Executing "upgradecage -a -f" as 0:121092010-10-22 10:35:36 PDT Errored upgradecage: Invalid option: -f

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• Displays when too many VLUNs have been created

Format of Possible vlun Exception Messages

vlun vlun:(<vvID>, <lunID>, <hostname>)"Path to <wwn> is not is not seen by host" vlunvlun:(<vvID>, <lunID>, <hostname>) "Path to <wwn> is failed" vlun host:<hostname> "Host <ident>(<type>):<connection> is not connected to a port"vlun -- "<count> active VLUNs exceeds the supported limit of <max count>"

vlun Example

146 vlun

Component ---------Summary Description--------- Qtyvlun Hosts not connected to a port 1

Component -----Identifier----- ---------Detailed Description--------vlun host:cs-wintec-test1 Host wwn:10000000C964121D is not connected to a port

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:1cli% servicehost listHostName -WWN/iSCSI_Name- Porthost0 10000000C98EC67A 1:1:2host1 210100E08B289350 0:5:2

Lun VVName HostName -Host_WWN/iSCSI_Name- Port Type 2 BigVV cs-wintec-test1 10000000C964121D 3:5:1 unknown

vvDisplays Virtual Volumes (VV) that are not optimal. Checks for VVs and Common Provisioning Groups(CPG) whose State is not normal.

Format of Possible vv Exception Messages

VV 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"VV vv:<vvname> "Detailed State: <state>" (failed or degraded)VV cpg:<cpg> "CPG is unable to grow SA (or SD) space"VV cpg:<cpgname> "CPG growth increment is below threshold"

vv Suggested Action

vv 147

Check status with CLI commands such as showvv, showvv -d , showvv -cpg .

Controlled thermal shutdown

Symptom

If the thermal temperature of the controller nodes or drives increases to the point that temperatureexceeds the acceptable range, alert notifications are displayed in the HPE 3PAR StoreServ ManagementConsole (SSMC), and then a controlled shutdown of the component occurs automatically as a protectiveaction.

Cause

Internal sensors monitor the temperature of the controller nodes and drives. If the temperature of thesecomponents exceeds the specified component temperature threshold, a controlled shutdown occurs. Thestorage system attempts to remain online and not shutdown any additional controller nodes, unlessmultiple drives have been spun down due to exceeding the acceptable temperature range. If the systemshuts down due to a pending TOC quorum loss from the spin down of too many drives, power remains onfor the nodes, drives, and drive enclosures.

For overheated controller nodes, a single controller node is shut down if one of its sensors reports acritical temperature.

For overheated drives, the drives are spun down individually. With multiple overheated drives being spundown, there is the danger of a TOC quorum loss, so the system executes a controlled shutdown. For acontrolled shutdown, the hardware remains powered on and the controller nodes reboot when theambient temperature has reduced and remains in the acceptable range for at least 30 minutes.

148 Controlled thermal shutdown

Parts catalog

Bezel (ear cap) parts listPart number Description Customer self

repair (CSR)

683256-001 SPS-Bezel A-Class Drive Shelf Left Mandatory

690778-001 SPS-Bezel 2U Shelf, left Mandatory

786046-001 SPS-BEZEL, RIGHT, 2U 8400 Array Mandatory



786049-001 SPS-BEZEL, RIGHT, 2U 8000 EBOD Mandatory

786050-001 SPS-BEZEL, RIGHT, 4U 8000 EBOD Mandatory


Cable parts listPart number Description Customer self

repair (CSR)

656428-001 SPS-CA 2m PREMIER FLEX FC OM4 Mandatory





683808-001 SPS-Cable Node Link PCIe 74xx/84xx No

717432-001 SPS-CBL 12Gb Mini-SAS HD 1m No

717433-001 SPS-CBL 12Gb Mini-SAS HD 2m No

793446-001 SPS-CBL 12Gb Mini-SAS HD AOC 10m No

793447-001 SPS-CBL 12Gb Mini-SAS HD AOC 25m No

Parts catalog 149

SAS3 cables—passive copper SAS3 cables—active optical

Controller node parts listPart number Description Customer self

repair (CSR)

683249-001 SPS-Node TOD Battery No

710577-001 SPS-SHIPPING BRACKET NODE LINK CBL ASSY Mandatory

792653-001 SPS-Node; 8400 No

792654-001 SPS-Node; 8440 No

792655-001 SPS-Node; 8450 No

793444-001 SPS-SFP Transceiver; 16 GBIT; LC (E7Y10A) Mandatory

809800-001 SPS-PCIE SS 8000 Riser Assy No

809805-001 SPS-Node; 8200 Optional

809806-001 SPS-Memory DIMM 8GB DDR3L Control and Data Cache No

809807-001 SPS-Memory DIMM 16GB DDR3L (Micron or SK Hynix) No

809808-001 SPS-Memory DIMM 32GB DDR3L (SH4097RV310493SDV) No

809813-001 SPS-BOOT DRIVE SS 128G SATA M.2 SDX300 No

150 Controller node parts list

Controller node

1. Control Cache DIMM (CC 0:0)2. Control Cache DIMM (CC 1:0)3. TOD clock battery4. Controller node boot drive5. PCIe riser card6. PCIe adapter7. PCIe riser slot8. Data Cache DIMM (DC 0:0)9. Data Cache DIMM (DC 1:0)

Figure 68: Controller node internal components

Parts catalog 151

Drive parts listPart number Description Customer self

repair (CSR)

697273-001 SPS-Drive blank LFF Mandatory

730772-001 SPS-Drive Blank SFF w/Yellow Touch Point Mandatory

810758-001 SPS-DRIVE SAS SD 1.92TB cMLC SFF FIPS Mandatory

810759-001 SPS-DRIVE SAS FC 1.2TB 10K SFF Mandatory

810760-001 SPS-DRIVE SAS 1.8TB 10K SFF Mandatory

810761-001 SPS-DRIVE SAS FC 600GB 10K SFF Mandatory

810762-001 SPS-DRIVE SAS FC 1.2TB 10K SFF FIPS Mandatory

810763-001 SPS-DRIVE SAS FC 300GB HDD 15K SFF Mandatory

810764-001 SPS-DRIVE SAS FC 600GB 15K SFF Mandatory

810765-001 SPS-DRIVE SAS FC 600GB 15K SFF FIPS Mandatory

810766-001 SPS-DRIVE SAS NL 4TB SAS 7.2K LFF Mandatory

810767-001 SPS-DRIVE SAS NL 2TB 7.2K LFF Mandatory


810769-001 SPS-DRIVE SAS NL 6TB 7.2K LFF FIPS Mandatory

810770-001 SPS-DRIVE SAS SSD 480GB cMLC SFF Mandatory

810771-001 SPS-DRIVE SAS SSD 1.92TB SSD cMLC SFF Mandatory

810772-001 SPS-DRIVE SAS SSD 480GB SSD cMLC LFF Mandatory

810773-001 SPS-DRIVE SAS SSD 3.84TB cMLC SFF Mandatory

810774-001 SPS-DRIVE SAS SSD 480GB MLC SFF Mandatory

810775-001 SPS-DRIVE SAS SSD 920GB MLC SFF FIPS Mandatory

814668-001 SPS-DRIVE SAS NL 2TB HDD 12G 7.2K SFF Mandatory

823123-001 SPS-DRIVE SAS NL 6TB 12G 7.2K LFF Mandatory

823124-001 SPS-DRIVE SAS NL 4TB 12G 7.2K LFF Mandatory


Table Continued

152 Drive parts list

Part number Description Customer selfrepair (CSR)

834598-001 SPS-DRIVE SAS SSD 3.84TB cMLC SFF FIPS Mandatory


840458-001 SPS-DRIVE SAS FC 600GB 6G SFF Mandatory

840459-001 SPS-DRIVE SAS FC 1.2TB 6G SFF Mandatory

840460-001 SPS DRIVE SAS 1.8TB 6G SFF Mandatory

840461-001 SPS-DRIVE SAS SSD 1.92TB 12G SAS cMLC SFF FIPS Mandatory

844272-001 SPS-DRIVE SAS SSD 480GB cMLC SFF Mandatory



844282-001 SPS-DRIVE SAS NL 4TB 7.2K LFF FIPS Mandatory



846593-001 SPS-DRV HD 8TB 7.2K LFF SAS FE 3PAR 8000 Mandatory

863460-001 SPS-DRV 7.68TB SSD SAS SFF SS8000 SM Mandatory

867545-001 SPS-DRV 15.36TB SSD SFF SS8000 SM FIPS Mandatory

869337-001 SPS-DRV 7.68TB SSD SAS SFF SS8K SM FIPS Mandatory

SFF drive LFF drive

Parts catalog 153

SFF drive assembly blank w/ yellow touch point LFF drive assembly blank

Drive enclosure parts listPart number Description Customer self

repair (CSR)

756484-001 SPS-Drive Enclosure 2U24 12G Assy No

756485-001 SPS-Drive Enclosure 4U24 12G Assy No

SFF drive enclosure (2U) LFF drive enclosure (4U)

I/O module parts listPart number Description Customer self

repair (CSR)

756487-001 SPS-EBOD 12G SAS IO module No

154 Drive enclosure parts list

I/O module

PCIe host adapter parts listPart number Description Customer self

repair (CSR)

657884-001 SPS-SFP TRANSCEIVER; LC; 10GBIT; CNA and Ethernet Mandatory

809799-001 SPS-Adapter iSCSI/FCoE CNA 10Gb 2 Port (QTH8362) No

809803-001 SPS-Adapter Eth 10Gbit 2 Port SS 8000 (560SFP+) No

809804-001 SPS-Adapter Eth 1Gb 4 Port SS 8000 (I350T4) No

817913-001 SPS-Adapter FC 16Gb 4 Port SS 8000 (LPE16004) No

864970-001 SPS-Adapter FC 10GbE/16Gb 4 Port (SS8000) No

864971-001 SPS-Combo Adapter 10GbE 4 Port (SS8000) No

Power cooling modules parts listCAUTION:

The use of alternating-current (AC) power is prohibited with any component for the direct-current(DC) power model of the HPE 3PAR StoreServ 8000 Storage system. The DC model requires theinstallation of DC-specific components.


727386-001 SPS-PCM 764W Assy without Battery Gold Optional

683240-001 SPS-Battery for PCM 764W Assy Optional

756486-001 SPS-PCM 580W Assy w/o Battery Gold Optional

866966-001 SPS-PCM 48 VDC, 764W, Gold, SS8000 Optional

PCIe host adapter parts list 155

764 W PCM Replaceable battery for the 764 W PCM

580 W PCM (no replaceable battery) -48V DC 764 W PCM

Rail kit parts listPart number Description Customer self

repair (CSR)

809809-001 SPS-Rail Kit 2U24 Fasteners (SS 8000) Mandatory

809810-001 SPS-Rail Kit 4U24 Fasteners (SS 8000) Mandatory

Service processor parts listPart number Description Customer self

repair (CSR)

5183-2683 Ethernet Cable 4 ft CAT5 M/M Mandatory

5183-2685 CA ASSY, CAT 5 Mandatory

5183-2686 CA ASSY, ETHERNET,14 FOOT CT05 Mandatory

Table Continued

156 Rail kit parts list


5183–2687 Ethernet Cable 25 ft CAT5 M/M Mandatory

5183–2691 Ethernet Cable 50 ft. CAT5 RJ45 M/M Mandatory

744111-001 SPS-KIT RK MNTG 1U Easy Install SFF Mandatory

818723-001 SPS-SERVICE PROCESSOR DL120 Gen 9 No

818724-001 RPS-SERVICE PROCESSOR DL120 Gen 9 No

818725-001 SPS-CABLE ADAPTER for SERVICE PROCESSOR No

HPE3PAR Service Processor

Parts catalog 157

WebsitesHewlett Packard Enterprise general websites

Information Library www.hpe.com/info/EIL

Customer Self Repair Services MediaLibrary Videos

www.hpe.com/support/sml-csr

HPE Licensing enterpriselicense.hpe.com/

Safety and Compliance www.hpe.com/support/Safety-Compliance-EnterpriseProducts

Software Depot home www.hpe.com/support/softwaredepot

Software updates and licensing www.hpe.com/downloads/software

Support Center www.hpe.com/support/hpesc

SPOCK www.hpe.com/storage/spock

StoreFront Remote www.storefrontremote.com

White papers and analyst reports www.hpe.com/storage/whitepapers

Hewlett Packard Enterprise storage websites

Information Library Storage www.hpe.com/info/storage/docs

Storage www.hpe.com/info/storage

Hewlett Packard Enterprise HPE 3PAR StoreServ 8000 Storage websites

Customer Self Install forum www.hpe.com/forum/3PAR8000CSIHELP

Customer Self Install Videos www.hpe.com/support/3PAR8000CSIVideo

Customer Self Repair Videos www.hpe.com/support/3PAR8000CSRVideo

Customer Self Upgrade Videos www.hpe.com/support/3PAR8000CSUVideo

Non-Hewlett Packard Enterprise websites

VMware Support www.vmware.com/support.html

VMware All Downloads my.vmware.com/web/vmware/downloads

VMware vSphereDocumentation

www.vmware.com/support/pubs/vsphere-esxi-vcenter-server-pubs.html

158 Websites

http://www.hpe.com/info/EIL

https://www.hpe.com/support/sml-csr

http://enterpriselicense.hpe.com/

http://www.hpe.com/support/Safety-Compliance-EnterpriseProducts


http://www.hpe.com/support/softwaredepot

https://www.hpe.com/downloads/software

http://www.hpe.com/support/hpesc

http://www.hpe.com/storage/spock

https://www.storefrontremote.com

http://www.hpe.com/storage/whitepapers

http://www.hpe.com/info/storage/docs

http://www.hpe.com/info/storage

http://www.hpe.com/forum/3PAR8000CSIHELP

http://www.hpe.com/support/3PAR8000CSIVideo

https://www.hpe.com/support/3PAR8000CSRVideo

https://www.hpe.com/support/3PAR8000CSUVideo

http://www.vmware.com/support.html

https://my.vmware.com/web/vmware/downloads

http://www.vmware.com/support/pubs/vsphere-esxi-vcenter-server-pubs.html

http://www.vmware.com/support/pubs/vsphere-esxi-vcenter-server-pubs.html

Support and other resources

Accessing Hewlett Packard Enterprise Support• For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:

http://www.hpe.com/assistance• To access documentation and support services, go to the Hewlett Packard Enterprise Support Center

website:


Information to collect

• Technical support registration number (if applicable)• Product name, model or version, and serial number• Operating system name and version• Firmware version• Error messages• Product-specific reports and logs• Add-on products or components• Third-party products or components

Accessing updates• Some software products provide a mechanism for accessing software updates through the product

interface. Review your product documentation to identify the recommended software update method.• To download product updates:

Hewlett Packard Enterprise Support Center www.hpe.com/support/hpesc

Hewlett Packard Enterprise Support Center: Softwaredownloads

www.hpe.com/support/downloads

Software Depot www.hpe.com/support/softwaredepot• To subscribe to eNewsletters and alerts:

www.hpe.com/support/e-updates• To view and update your entitlements, and to link your contracts and warranties with your profile, go to

the Hewlett Packard Enterprise Support Center More Information on Access to Support Materialspage:

www.hpe.com/support/AccessToSupportMaterials

IMPORTANT:

Access to some updates might require product entitlement when accessed through the HewlettPackard Enterprise Support Center. You must have an HPE Passport set up with relevantentitlements.

Customer self repairHewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If aCSR part needs to be replaced, it will be shipped directly to you so that you can install it at your

Support and other resources 159

http://www.hpe.com/assistance



http://www.hpe.com/support/downloads

http://www.hpe.com/support/softwaredepot

http://www.hpe.com/support/e-updates

http://www.hpe.com/support/AccessToSupportMaterials

convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized serviceprovider will determine whether a repair can be accomplished by CSR.

For more information about CSR, contact your local service provider or go to the CSR website:

http://www.hpe.com/support/selfrepair

Remote supportRemote support is available with supported devices as part of your warranty or contractual supportagreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware eventnotifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on yourproduct's service level. Hewlett Packard Enterprise strongly recommends that you register your device forremote support.

If your product includes additional remote support details, use search to locate that information.

Remote support and Proactive Care information

HPE Get Connected www.hpe.com/services/getconnected

HPE Proactive Care services www.hpe.com/services/proactivecare

HPE Proactive Care service:Supported products list

www.hpe.com/services/proactivecaresupportedproducts

HPE Proactive Care advancedservice: Supported products list

www.hpe.com/services/proactivecareadvancedsupportedproducts

Proactive Care customer information

Proactive Care central www.hpe.com/services/proactivecarecentral

Proactive Care service activation www.hpe.com/services/proactivecarecentralgetstarted

Warranty informationTo view the warranty for your product, see the Safety and Compliance Information for Server, Storage,Power, Networking, and Rack Products document, available at the Hewlett Packard Enterprise SupportCenter:

www.hpe.com/support/Safety-Compliance-EnterpriseProducts

Additional warranty information

HPE ProLiant and x86 Servers and Options www.hpe.com/support/ProLiantServers-Warranties

HPE Enterprise Servers www.hpe.com/support/EnterpriseServers-Warranties

HPE Storage Products www.hpe.com/support/Storage-Warranties

HPE Networking Products www.hpe.com/support/Networking-Warranties

Regulatory informationTo view the regulatory information for your product, view the Safety and Compliance Information forServer, Storage, Power, Networking, and Rack Products, available at the Hewlett Packard EnterpriseSupport Center:

www.hpe.com/support/Safety-Compliance-EnterpriseProducts

160 Remote support

http://www.hpe.com/support/selfrepair

http://www.hpe.com/services/getconnected

http://www.hpe.com/services/proactivecare

http://www.hpe.com/services/proactivecaresupportedproducts

http://www.hpe.com/services/proactivecareadvancedsupportedproducts

http://www.hpe.com/services/proactivecareadvancedsupportedproducts

http://www.hpe.com/services/proactivecarecentral

http://www.hpe.com/services/proactivecarecentralgetstarted


http://www.hpe.com/support/ProLiantServers-Warranties

http://www.hpe.com/support/EnterpriseServers-Warranties

http://www.hpe.com/support/Storage-Warranties

http://www.hpe.com/support/Networking-Warranties


Additional regulatory information

Hewlett Packard Enterprise is committed to providing our customers with information about the chemicalsubstances in our products as needed to comply with legal requirements such as REACH (Regulation ECNo 1907/2006 of the European Parliament and the Council). A chemical information report for this productcan be found at:

www.hpe.com/info/reach

For Hewlett Packard Enterprise product environmental and safety information and compliance data,including RoHS and REACH, see:

www.hpe.com/info/ecodata

For Hewlett Packard Enterprise environmental information, including company programs, productrecycling, and energy efficiency, see:

www.hpe.com/info/environment

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs. To help usimprove the documentation, send any errors, suggestions, or comments to Documentation Feedback([email protected]). When submitting your feedback, include the document title, part number,edition, and publication date located on the front cover of the document. For online help content, includethe product name, product version, help edition, and publication date located on the legal notices page.

Documentation feedback 161

http://www.hpe.com/info/reach

http://www.hpe.com/info/ecodata

http://www.hpe.com/info/environment

mailto:[email protected]

Acronyms2U two-unit rack space

4U four-unit rack space

AC alternating current

AFA all flash array

CC control cache (DIMMs)

CDA confidential disclosure agreement

CLI command line interface

CNA converged network adapter

DAR data at rest

DC direct current (power) or data cache (DIMMs)

DHCP dynamic host configuration protocol

DNS domain name system

ESD electrostatic discharge

FC Fibre Channel (protocol) or fast class (drive type)

FCoE Fibre Channel over Ethernet (protocol)

FIPS Federal Information Processing Standard

FRU field replaceable unit

Gb Gigabits

Gb/s Gigabits per second

GbE Gigabit Ethernet

GUI graphical user interface

HBA host bus adapter

I/O input/output

iLO integrated lights out

LAN local area network

LFF large form factor

162 Acronyms

LUN logical unit number

MOB moment of birth

NIC network interface controller

NL near line (drive type)

NTP network time protocol

OOTB out of the box

OVF open virtual format

PCIe peripheral component interconnect express

PCM power cooling module

PDU power distribution unit

RAID redundant array of independent disks

RPS redundant power supply

SAN storage area network

SAS serial attached SCSI

SC HPE 3PAR Service Console

SFF small form factor

SFP small form-factor pluggable

SFRM Hewlett Packard Enterprise StoreFront Remote

SP HPE 3PAR Service Processor

SPOCC HPE 3PAR Service Processor Onsite Customer Care

SPOCK Single Point of Connectivity Knowledge

SPS single power supply

SSA secure service agent

SSD solid state drive (drive type)

SSH Secure Shell

SSMC HPE 3PAR StoreServ Management Console

TCP transmission control protocol

TOTP time-based password

Acronyms 163

TUI HPE 3PAR Text-based User Interface

U unit of space in a rack

UID unit identification

VM virtual machine

VV virtual volume

W watt

164 Acronyms

Documents

HPE 3PAR StoreServ 8000 Storage - Apache Welcome Pageh20628. · HPE 3PAR StoreServ 8000 Storage Service and Upgrade Guide Customer Edition Part Number: QL226-99284 Published: March