hp 3par p10000 storage system maintenance manual (mar 2012) [105p]

HP P10000 3PAR Storage SystemMaintenance Manual

AbstractThis manual is for authorized service personnel who are responsible for the maintenance of the HP 3PAR Storage System andits service processor. Use this manual to perform removal and replacement procedures on the storage system components whenonline guided maintenance is not available.

HP Part Number: QL226-96259Published: March 2012

© Copyright 2012 Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shallnot be liable for technical or editorial errors or omissions contained herein.

Acknowledgments

Microsoft®, Windows®, Windows® XP, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.

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

Warranty

WARRANTY STATEMENT: To obtain a copy of the warranty for this product, see the warranty information website:

http://www.hp.com/go/storagewarranty

For the latest version of this document, go to the Services Access Workbench at http://sawpro.atlanta.hp.com/km/saw/pmBrowse.do?oid=5044215.

http://www.hp.com/go/storagewarranty

ContentsIntroduction..................................................................................................5

Related Documentation..............................................................................................................51 Drive Chassis Maintenance Procedures.........................................................6

Replacing a Drive Magazine and a Disk in a Drive Magazine........................................................6Planning...........................................................................................................................14Logging Mode...................................................................................................................14

Replacing a Drive Cage SFP Module on an FC-AL......................................................................14Replacing a Drive Cage FC-AL Module......................................................................................17Replacing a Drive-side Fibre Channel Cable...............................................................................20Replacing a Midplane Assembly...............................................................................................21

Migrating Data Off the Drive Cage......................................................................................24Migrating Data Back to the Drive Cage................................................................................25

Replacing a Drive Chassis Power Supply....................................................................................272 Controller Node Maintenance Procedures...................................................31

Replacing a Controller Node Fan Module..................................................................................31Replacing a Controller Node Power Supply................................................................................32Replacing a Battery Module.....................................................................................................34Replacing a Controller Node...................................................................................................35Replacing a Node Disk...........................................................................................................40Replacing an SFP Module........................................................................................................42Replacing a PCI Adapter.........................................................................................................44Replacing a Cache DIMM.......................................................................................................47Replacing a Clock Battery........................................................................................................53Replacing the LED Status Board................................................................................................54Replacing a Controller Node Chassis........................................................................................55

3 Power System Maintenance Procedures.......................................................57Replacing a Power Distribution Unit...........................................................................................57Replacing an AC Cord............................................................................................................60

4 Replacing a Service Processor....................................................................62Replacing a Service Processor..................................................................................................62

5 Understanding HP P10000 3PAR Storage System LED Status..........................64Drive Cage LEDs....................................................................................................................64

DC4 Drive Cage FC-AL Module LEDs...................................................................................65Drive Magazine LEDs.........................................................................................................67

Controller Node LEDs..............................................................................................................68Controller Node Status Panel LEDs.......................................................................................69

Fan Module LEDs....................................................................................................................70Fibre Channel Adapter Port LEDs..............................................................................................71CNA Port LEDs.......................................................................................................................72Ethernet LEDs.........................................................................................................................73Power Supply LEDs..................................................................................................................74

Drive Chassis Power Supply LEDs.........................................................................................74Controller Node Power Supply LEDs.....................................................................................75

Battery Module LEDs...............................................................................................................76Power Distribution Unit Lamps...................................................................................................77Service Processor LEDs............................................................................................................78

6 Powering Off the Storage System................................................................79Powering Off the Storage System..............................................................................................79

Contents 3

7 Connecting the Maintenance PC................................................................80Connecting to a Controller Node..............................................................................................80Connecting to the Service Processor..........................................................................................80

Using a Serial Connection...................................................................................................81Serial Settings...............................................................................................................81

Enabling Session Logging..........................................................................................82Connecting to the CLI................................................................................................82

Using an Ethernet Connection..............................................................................................82Configuring the LAN Settings on the Maintenance PC........................................................83Using PuTTY.................................................................................................................84

Logging into SPOCC.................................................................................................85Serial Cable Pinouts................................................................................................................85

Crossover Adapter Assembly...............................................................................................85Straight-Through Adapter....................................................................................................86

A Precautions..............................................................................................87General Precautions................................................................................................................87Disk and Drive Magazine Precautions.......................................................................................87Controller Node Precaution......................................................................................................88Clock Battery Precaution..........................................................................................................88Drive Chassis and Node Power Supply Precaution......................................................................88Battery Module Precautions......................................................................................................88Power Distribution Unit Precautions............................................................................................88AC Cord Precaution................................................................................................................88

B Tools.......................................................................................................89Tools Required to Perform Maintenance.....................................................................................89

C Guided Maintenance...............................................................................90Overview..............................................................................................................................90Accessing Guided Maintenance...............................................................................................90

D Performing Node Rescue...........................................................................93Performing Auto-Node Rescue..................................................................................................93Performing Manual Node Rescue..............................................................................................95

E Illustrated Parts Catalog.............................................................................99Storage System Frame Components...........................................................................................99Internal Node Components....................................................................................................101Drive Chassis Components.....................................................................................................103Miscellaneous Components....................................................................................................104

4 Contents

IntroductionUse this manual to perform removal and replacement procedures on the HP P10000 3PAR StorageSystem. The maintenance procedures described here should only be used in instances where onlineguided maintenance is not available for the hardware that requires servicing. See GuidedMaintenance for a list of Field Replaceable Units (FRUs) with available guided maintenance. Toaccess guided maintenance via SPOCC, refer to Connecting to the Maintenance PC.Before beginning the procedures in this manual, you must read the Appendices at the end of themanual and connect your maintenance PC to the node or Service Processor (SP). After connectingthe storage system to the maintenance PC, you can then perform the procedures listed in thismanual. This manual also references storage system component LED indicators.

NOTE: The InServ Storage Server has been rebranded as HP 3PAR Storage System. There areinstances in this document where menu items and command output refer to the HP 3PAR StorageSystem as InServ or InServ Storage Server.

Related DocumentationThe following related documents also provide information related to the HP 3PAR Storage Systemsand the InForm OS environment:

Table 1 Related Documentation

Read the…For Information About…

HP P10000 3PAR Storage System Physical PlanningManual

Planning and preparing for a storage system installation

HP P10000 3PAR Storage System Installation Checklist(for HP 3PAR Cabinets)

Checklist for installation tasks to be completed

HP P10000 3PAR Storage System Upgrades GuideUpgrading HP 3PAR Storage Systems

HP 3PAR OS Concepts GuideUnderstanding the basics of the InForm OS and HP 3PARStorage System

HP 3PAR OS CLI Administrator’s ManualUsing the InForm Command Line Interface (CLI) to configureand manage the HP 3PAR Storage System

HP 3PAR InForm Management Console Online HelpUsing the InForm Management Console’s (IMC) user interfaceto configure and manage the HP 3PAR Storage System

HP 3PAR InForm OS Messages and Operators Guide:Service Edition

Identifying storage system components, detailed alertinformation, and service messages

Related Documentation 5

1 Drive Chassis Maintenance Procedures

CAUTION: When handling the drive chassis components, observe the precautions as describedin “Precautions” (page 87).

NOTE: Guided maintenance scripts are available to facilitate this procedure. See “GuidedMaintenance” (page 90) for additional information.

Replacing a Drive Magazine and a Disk in a Drive MagazineBefore beginning this procedure, you must read the planning section and perform the steps in thelogging mode section to prepare the disk or drive magazine for replacement. See “Planning”(page 14) and “Logging Mode” (page 14).To replace a drive magazine and a disk in a drive magazine:1. Connect the maintenance PC to the SP using the serial connection and start an spmaint

session.2. In the 3PAR Service Processor Menu, select option 7 Interactive CLI for an InServ, then select

the desired system.3. Issue the showpd command to verify the location of the failed disk or drive magazine and

whether there are adequate spare chunklets defined.

NOTE: If there are not enough spare chunklets defined, contact your technical supportrepresentative for assistance.

4. Issue the servicemagcommand:• For a failed disk, issue servicemag start -log -pdid <disk_id> command,

where <disk_id> is the ID of the failed disk.

cli% servicemag start -log -pdid 3Are you sure you want to run servicemag?select q=quit y=yes n=no: yservicemag start -log -pdid 3... servicing disks in mag: 0 3... valid disks: WWN [2000001D38B11AC7] Id [ 1204] diskpos [0] .................... WWN [2000001D38B114FE] Id [ 1205] diskpos [1] .................... WWN [2000001D38B119AB] Id [ 1206] diskpos [2] .................... WWN [2000001D38B11277] Id [ 1207] diskpos [3] ... not valid disks: The servicemag start operation will continue in the background.

• For a failed drive magazine, issue servicemag start -log -nodisks <cage_id><mag_id>.

NOTE: The servicemag start command moves all the required, used chunklets on themagazine. This is executed simultaneously for each hard drive and takes approximately 20seconds for each used chunklet.

cli% servicemag start -log -nodisks 0 3Are you sure you want to run servicemag?select q=quit y=yes n=no: yservicemag start -log -nodisks 0 3... servicing disks in mag: 0 3


... valid disks: WWN [5000C50002841761] Id [56] diskpos [0]

.................... WWN [5000C500028486F2] Id [57] diskpos [1]

.................... WWN [5000C5000284173F] Id [58] diskpos [2]

.................... WWN [5000C50002841675] Id [59] diskpos [3]

... not valid disks: The servicemag start operation will continue in the background.

5. To monitor progress, issue the servicemag and identify the drive magazine containing thepdid to be replaced.• For a disk, issue servicemag status -d:

cli% servicemag status -dCage 0, magazine 3:The magazine was successfully brought offline by a servicemag start command.The command completed Thu Feb 11 10:49:30 2011.The output of the servicemag start was:servicemag start -log -pdid 3... servicing disks in mag: 0 3... normal disks: WWN [2000001D38B11AC7] Id [1204] diskpos [0] .................... WWN [2000001D38B114FE] Id [1205] diskpos [1] .................... WWN [2000001D38B119AB] Id [1207] diskpos [3] ... not normal disks: WWN [2000001D38B11277] Id [1206] diskpos [2] ... relocating chunklets to spare space...... relocating chunklets from degraded raid sets to spare space... relocating chunklets from degraded raid sets to spare space... logging chunklets from pd WWN [2000001D38B11AC7] Id [0] ... logging chunklets from pd WWN [2000001D38B114FE] Id [1] ... logging chunklets from pd WWN [2000001D38B119AB] Id [2] ... retrying logging chunklets...... spinning down disk WWN [2000001D38B11AC7] Id [0]... spinning down disk WWN [2000001D38B114FE] Id [1]... spinning down disk WWN [2000001D38B119AB] Id [2]... spinning down disk WWN [2000001D38B11277] Id [3]... bypassing mag 0 3... bypassed mag 0 3servicemag start -log -pdid 3 -- Succeeded

• For a drive magazine, issue servicemag status -d <cageID> <magazine>.

cli% servicemag status -d 0 3Cage 0, magazine 3:The magazine is being brought offline due to a servicemag start.The last status update was at Wed Nov 21 07:52:29 2010.The cumulative output so far is:servicemag start -log -nodisks 0 3... servicing disks in mag: 0 3... valid disks: WWN [5000C50002841761] Id [56] diskpos [0] .................... WWN [5000C500028486F2] Id [57] diskpos [1] .................... WWN [5000C5000284173F] Id [58] diskpos [2] .................... WWN [5000C50002841675] Id [59] diskpos [3] ... not valid disks: ... relocating chunklets to spare space...... relocating chunklets from degraded raid sets to spare space... logging chunklets from pd WWN [5000C50002841761] Id [56] ... logging chunklets from pd WWN [5000C500028486F2] Id [57] ... logging chunklets from pd WWN [5000C5000284173F] Id [58] ... logging chunklets from pd WWN [5000C50002841675] Id [59]

Replacing a Drive Magazine and a Disk in a Drive Magazine 7

When the command completes successfully, Succeeded displays, the hot-plug LED illuminatesand the drive magazine status LEDs blink slowly (“DC4 Drive Magazine LEDs” (page 8)).

Figure 1 DC4 Drive Magazine LEDs

6. Issue the locatecage cage <ID> command to turn on all LEDs for a short duration (“DC4Drive Magazine Locations in the Drive Cage” (page 8)) to locate the drive caged to bereplaced.

Figure 2 DC4 Drive Magazine Locations in the Drive Cage

7. Wearing a wrist- grounding strap, use a #2 Phillips screwdriver to loosen the captive screwthat secures the drive magazine to the chassis (“Loosening the Captive Screw on the DriveMagazine” (page 9)).


Figure 3 Loosening the Captive Screw on the Drive Magazine

8. With your right hand on the handle of the drive magazine and your left hand supporting thedrive magazine from beneath, slide the magazine out of the chassis and place it on anESD-safe, level work surface with the solid back panel facing down.

9. To remove a drive magazine:a. Remove the replacement magazine from its protective packaging and set aside any

electrostatic preventative packing material protecting the magazine. It will be used topackage the replaced drive magazine.

b. Place the replacement magazine on the ESD-safe work surface next to the failed magazine.c. Perform step 11 through step 13 for each disk.

10. To replace a failed disk, identify the disk requiring replacement. The disk status LEDs numberedon the front of the drive magazine corresponds to the disks mounted on the drive magazine.The numbers are also indicated along the side of the drive magazine (“Numbering of Diskson a DC4 Magazine” (page 10)).


Figure 4 Numbering of Disks on a DC4 Magazine

11. Use a #2 Phillips screwdriver to remove the screws from the drive mount on a DC4 drivemagazine (Figure 5 (page 10)).• For DC4 drive magazines, unscrew and remove each screw securing the disk drives.

Figure 5 Screws Securing the Disks


12. Slide it out of the magazine (“Sliding a Disk Out of the Magazine” (page 11)). Avoid touchingthe exposed underside of the disk.

Figure 6 Sliding a Disk Out of the Magazine

13. Remove the replacement disk from its protective packaging and avoid touching the exposedunderside of the replacement disk.

14. Replace the disk into the new drive magazine:a. Carefully insert the replacement disk into the same opening in the drive magazine.b. Slide the disk down until the screw holes align with the screw holes in the drive mount.

At this point, the drive should be seated in its connector and the top of the disk shouldbe near flush with the top of the drive magazine and should lay flat within the magazine.

c. Secure the disk to the drive mount with the screws. Do not overtighten the screws.15. Remove all disks from the failed drive magazine and transfer them to the replacement drive

magazine.


16. Replace the drive magazine:a. With the magazine ejector handle completely lowered, use the notch at the top of the

chassis housing as a guide to slide the drive magazine into the chassis (Figure 7(page 12)).

Figure 7 Inserting a Drive Magazine into a Drive Chassis

CAUTION: The drive magazines should slide in-and-out easily. If a magazine does notinsert smoothly, do not force it. Confirm whether the magazine is properly aligned withthe guide notch at the top of the chassis housing and apply moderate pressure towardthe left side of the magazine while inserting. If you have difficulty inserting magazinesinto the chassis that also have magazine filler panels installed, it may be necessary toremove the adjacent filler panel to insert the magazine more easily.

b. When the drive magazine slides to a stop, quickly lift the ejector handle up to engagethe magazine into the drive chassis midplane.

c. Secure the magazine to the chassis by tightening the captive screw at the front of themagazine. Do not overtighten the screw.

NOTE: After inserting the magazine into the chassis, allow approximately one minutefor the disks on the magazine to spin up before checking the magazine LEDs. If any disksin the drive magazine fail to spin up, reseat the drive magazine and be sure to close theejector handle quickly.

17. Place the removed disk or disk magazine in the protective packaging for return to HP.18. Verify all disk status LEDs on the drive magazine appear steady green and the hot-plug LED

is not illuminated.19. In the SP window, issue the showpd command and verify that the removed disk is listed as

failed and the replacement disk is listed as new.

NOTE: The new disk appears at the top of the disk list in the showpd command output.

20. Issue the servicemag resume <cage_id> <mag_id> where <cage_id> is the drivecage number and <mag_id> is the location of the drive magazine in the drive chassis.

cli% servicemag resume 0 3Are you sure you want to run servicemag?select q=quit y=yes n=no: yservicemag resume 0 3... mag 0 3 already onlooped... firmware is current on pd WWN [20000024B6284FE8] Id [933]


... firmware is current on pd WWN [2000001D38B11AC7] Id [1204]

... firmware is current on pd WWN [2000001D38B114FE] Id [1205]

... firmware is current on pd WWN [2000001D38B119AB] Id [1207]

... firmware is current on pd WWN [2000001D38B11277] Id [1206]

... checking for valid disks...

... disks in mag : 0 3

... normal disks: WWN [20000024B6284FE8] Id [933] diskpos [2]

.................... WWN [2000001D38B11AC7] Id [1204] diskpos [0]

.................... WWN [2000001D38B114FE] Id [1205] diskpos [1]

.................... WWN [2000001D38B119AB] Id [1207] diskpos [3]

... not normal disks: WWN [2000001D38B11277] Id [1206]

... verifying spare space for disks 1204 and 1204



... playback chunklets from pd WWN [20000024B6284FE8] Id [933]

... playback chunklets from pd WWN [2000001D38B11AC7] Id [1204]

... playback chunklets from pd WWN [2000001D38B114FE] Id [1205]

... playback chunklets from pd WWN [2000001D38B119AB] Id [1207] The servicemag resume operation will continue in the background.

The servicemag resume process may take several hours or more to complete, depending onthe number of chunklets to be relocated. Once servicemag status shows chunklets have begunrelocating from spare space, issue the servicemag status command (the -d is optional foradditional detailed information) to monitor the servicemag completion.

21. Issue the servicemag status -d <cage_id> <mag_id> command.

cli% servicemag status -dCage 0, magazine 3:The magazine is being brought online due to a servicemag resume.The last status update was at Thu Feb 11 11:09:21 2011.Unable to provide a relocation estimateThe cumulative output so far is:servicemag resume 0 3... mag 0 3 already onlooped... firmware is current on pd WWN [20000024B6284FE8] Id [933] ... firmware is current on pd WWN [2000001D38B11AC7] Id [1204] ... firmware is current on pd WWN [2000001D38B114FE] Id [1205] ... firmware is current on pd WWN [2000001D38B119AB] Id [1207] ... firmware is current on pd WWN [2000001D38B11277] Id [1206] ... checking for valid disks...... disks in mag : 0 3... normal disks: WWN [20000024B6284FE8] Id [933] diskpos [2] .................... WWN [2000001D38B11AC7] Id [1204] diskpos [0] .................... WWN [2000001D38B114FE] Id [1205] diskpos [1] .................... WWN [2000001D38B119AB] Id [1207] diskpos [3] ... not normal disks: WWN [2000001D38B11277] Id [1206] ... verifying spare space for disks 1204 and 1204... verifying spare space for disks 1205 and 1205... verifying spare space for disks 1207 and 1207... playback chunklets from pd WWN [20000024B6284FE8] Id [933] ... playback chunklets from pd WWN [2000001D38B11AC7] Id [1204] ... playback chunklets from pd WWN [2000001D38B114FE] Id [1205] ... playback chunklets from pd WWN [2000001D38B119AB] Id [1207] ... 170 chunklets still waiting to be played back or relocating...... All chunklets played back / relocated.... relocating chunklets from raid set to new disk... relocating chunklets from spare space


22. For replacement disks:

NOTE: When using the CLI command option -pdid, step 22 is not required and you canskip to step 23, if applicable.

a. Issue the dismisspd <PD_ID>command to remove the replaced disk, where <PD_ID>is the ID of the replaced physical disk.

b. Issue the showpd <PD_ID> command and verify if the replaced disk is removed.23. Issue the checkhealth -svc -detail command to verify the system is healthy.24. In the SP window, issue the exit command and select X to exit from the 3PAR Service Processor

Menu and to log out of the session.25. Disconnect the serial cable from the maintenance PC or the red cross-over Ethernet cable from

the laptop and coil and replace the cable behind the SP.26. Close and lock the rear door.

PlanningPreparation prior to completing the physical replacement procedure can take between:

• 2-12 hours for a disk

• 20 minutes to 12 hours for a drive magazineThe table below shows examples of the time allotment needed for running the CLI commandservicemag on disks or drive magazines at or near capacity and estimate times for migrating data.

Estimated Time RequiredDrive Magazine Size

1 Hour or less50GB

6 Hours300GB

10-12 Hours500GB or larger

Logging ModeFor slower or large disks and when replacing a drive magazine, use the -log option with the CLIservicemag command.Conditions for using logging mode:

• If only a single disk has failed

• If the disk replacement can be completed within 30 minutesConditions when logging mode is not recommended and should not be used:

• If you have any RAID-0 sets on the drive magazine

• If there are multiple failed disks or multiple problems or failures

• If there are multiple failures in the same drive cageAdditional CLI commands:

• servicemag start -log -pdid <pd_id> . Use the -pdid option in conjunction tospecify the disk to be replaced. This ensures the data vacates from the disk to be replaced.

• servicemag start -log -nodisks <cage_id> <mag_id>. Use the -nodisksoption only in conjunction with the-log option when servicing a drive magazine which hasall valid drives and no disks need to be replaced.

Replacing a Drive Cage SFP Module on an FC-ALTo replace a drive cage SFP module:


1. Connect the maintenance PC to the SP using the serial connection and start an spmaintsession.

2. In the 3PAR Service Processor Menu, select option 7 Interactive CLI for an InServ, then selectthe desired system.

3. Issue the servicecage startfc <x> <cage> command, where <x> is the SFP moduleto be replaced and <cage> is the name of the drive cage to be serviced.

cli% servicecage startfc 1 cage4

4. To locate the drive cage, issue the locatecage –t 15 <cage> command to turn on allLEDs for a short duration, where 15 is the number of seconds the LEDs are illuminated and<cage> is the cage number.

5. Issue the showcage –d <cage> command, where <cage>is the cage name and verifythat the FC-AL hot-plug LED is Amber.

cli% showcage -d cage4Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 4 cage4 2:2:1 0 3:2:1 0 8 30-38 2.37 2.37 DC4 n/a -----------Cage detail info for cage4 ---------Position: ---Fibre Channel Info PortA0 PortB0 PortA1 PortB1 Link_Speed 4Gbps -- -- 4Gbps----------------------------------SFP Info-----------------------------------FCAL SFP -State- --Manufacturer-- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM 0 0 OK FINISAR CORP. 4.1 No No No Yes 1 1 OK FINISAR CORP. 4.1 No No No YesInterface Board Info FCAL0 FCAL1 Link A RXLEDs Green Off Link A TXLEDs Green Off Link B RXLEDs Off Green Link B TXLEDs Off Green LED(Loop_Split) Off OffLEDS(system,hotplug) Green,Off Green,Amber

6. Verify that the FC-AL module hot-plug LED is amber and ready to service.

Replacing a Drive Cage SFP Module on an FC-AL 15

Figure 8 FC-AL LED and Port Locations

7. Squeeze the tabs on the sides of the Fibre Channel cable and pull to disconnect from the SFP.8. Wearing a wrist-grounding strap, lift the retaining clip of the defective SFP module and slide

the defective SFP module out of the SFP slot.9. Remove the replacement SFP module from its protective packaging.10. Place the removed SFP module into the protective packaging for return to HP.11. Insert the replacement SFP module into the FC-AL until fully seated.12. Lock the SFP retaining clip in place.13. Reconnect the Fibre Channel cable.14. Verify that the TX (Transmit) and RX (Receive) LEDs are illuminated.15. Issue the servicecage endfc <x> <cagename> command, where <x>is the FC-AL

module and <cagename> is the name of the drive cage.

cli% servicecage endfc 1 cage4

16. Issue theshowpd command and verify that the port for the replaced SFP is now active andthe disks are on the loop.

cli% showpd ---Size(MB)---- ----Ports----Id CagePos Type RPM State Total Free A B 0 0:4:0 FC 15 normal 279808 250112 0:3:1* 1:4:1 1 0:0:1 FC 15 normal 279808 262400 0:3:1 1:4:1* 2 0:0:2 FC 15 normal 279808 250112 0:3:1* 1:4:1 3 0:0:3 FC 15 normal 279808 262656 0:3:1 1:4:1* 4 0:1:0 FC 15 normal 279808 250112 0:3:1* 1:4:1 5 0:1:1 FC 15 normal 279808 262656 0:3:1 1:4:1* 6 0:1:2 FC 15 normal 279808 250368 0:3:1* 1:4:1 7 0:1:3 FC 15 normal 279808 262912 0:3:1 1:4:1*


17. Issue the showcage –d <cagename> command and verify that the SFP hot-plug LED isGreen.

cli% showcage -d cage1Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 1 cage1 0:3:4 0 1:4:4 0 16 30-38 2.37 2.37 DC4 n/a -----------Cage detail info for cage1 ---------Position: ---Fibre Channel Info PortA0 PortB0 PortA1 PortB1 Link_Speed 4Gbps -- -- 4Gbps----------------------------------SFP Info-----------------------------------FCAL SFP -State- --Manufacturer-- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM 0 0 OK FINISAR CORP. 4.2 No No No Yes 1 1 OK FINISAR CORP. 4.2 No No No YesInterface Board Info FCAL0 FCAL1 Link A RXLEDs Green Off Link A TXLEDs Green Off Link B RXLEDs Off Green Link B TXLEDs Off Green LED(Loop_Split) Off OffLEDS(system,hotplug) Green,Off Green,Off

18. Issue the checkhealth -svc -detail command to verify the system is healthy.19. In the SP window, issue the exit command and select X to exit from the 3PAR Service Processor

Menu and to log out of the session.20. Disconnect the serial cable from the maintenance PC and coil and replace the cable behind

the SP.21. Close and lock the rear door.

Replacing a Drive Cage FC-AL ModuleTo replace a drive cage FC-AL module:1. Connect the maintenance PC to the SP using the serial connection and start an spmaint


the desired system.3. Issue the servicecage startfc <x> <cage> command, where <x> is the FC-AL

module to be replaced and <cagename> is the cage name.

cli% servicecage startfc 1 cage1Are you sure you want to run "servicecage startfc 1 cage1"?select q=quit y=yes n=no: y

4. Issue the showcage –d <cagename> command, where <cagename>is the cage name andverify the FC-AL hot-plug LED is Amber by checking the LED system,hotplug line:

cli% showcage -d cage1Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 1 cage1 0:3:4 0 1:4:4 0 16 30-38 2.37 2.37 DC4 n/a -----------Cage detail info for cage1 ---------Position: ---Fibre Channel Info PortA0 PortB0 PortA1 PortB1 Link_Speed 4Gbps -- -- 4Gbps----------------------------------SFP Info-----------------------------------FCAL SFP -State- --Manufacturer-- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM 0 0 OK FINISAR CORP. 4.2 No No No Yes 1 1 OK FINISAR CORP. 4.2 No No No Yes

Replacing a Drive Cage FC-AL Module 17

Interface Board Info FCAL0 FCAL1 Link A RXLEDs Green Off Link A TXLEDs Green Off Link B RXLEDs Off Green Link B TXLEDs Off Green LED(Loop_Split) Off OffLEDS(system,hotplug) Green,Off Amber,Off-----------Midplane Info----------- Firmware_status Old Product_Rev 2.37 State Normal Op Loop_Split 0VendorId,ProductId 3PARdata,DC4 Unique_ID 10620300000B6300-----------Midplane Info----------- Firmware_status Old Product_Rev 2.36 State Normal Op Loop_Split 0VendorId,ProductId 3PARdata,DC4 Unique_ID 1062030000098E00

5. Note the location of all Fibre Channel cables to be reconnected after FC-AL replacement. Ifnecessary, mark the cables that connect to the FC-AL before removing them. The drive-sideFibre Channel cables are marked to simplify this task.

6. Squeeze the tabs on the sides of the Fibre Channel cables and pull to disconnect them fromthe SFP.

7. Wearing a wrist-grounding strap, remove the FC-AL module:a. Pull down the retaining clip of the SFP module (Figure 9 (page 18)).

Figure 9 SFP Module

b. Holding the retaining clip, slide the SFP module out of the defective FC-AL.c. Use a #2 Phillips screwdriver to loosen the captive screw that secures the FC-AL (Figure 10

(page 19)).


Figure 10 FC-AL Captive Screw

d. Pull the FC-AL handle down and slide the FC-AL module out of the drive chassis using thehandle on the side of the module.

8. Remove the replacement FC-AL module from its protective packaging and electrostatic packingmaterial and set aside.

9. Place the removed FC-AL module into the protective packaging for return to HP.10. Replace the FC-AL module:

a. Insert the replacement FC-AL module into the drive chassis and lift up the FC-AL handleuntil fully seated.

CAUTION: Drive cage FC-AL modules should slide in and out smoothly. If an FC-ALmodule does not easily insert, do not force it. Before continuing, confirm that the FC-ALmodule is properly aligned with the card guides at the top and bottom of the drive chassishousing.

b. Tighten the screw that secures the FC-AL module to the drive chassis housing. Do notovertighten the screw.

c. Insert the SFP module into the FC-AL until fully seated.d. Lock the retaining clip in place.

11. Reconnect all Fibre Channel cables.12. Issue the servicecage endfc <x> <cagename>command, where <x> is the FC-AL

module replaced and<cagename> is the drive cage being updated.

cli% servicecage endfc 1 cage1Are you sure you want to run "servicecage endfc 1 cage1"?select q=quit y=yes n=no: yUpgrading cage cage1 cpuA from rev 2.36 to revision in file /opt/tpd/fw/cage/dc4/lbod_fw.bin-2.37.Beginning test after upgrade for cage1cage1 passed test after upgrade

Replacing a Drive Cage FC-AL Module 19

13. Issue the showcage –d <cagename> command, where <cage> is the name of the drivecage where the FC-AL module is replaced and verify that the drive cage now includes thecorrect firmware level shown below RevA and RevB.

cli% showcage -d cage1Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 1 cage1 0:3:4 0 1:4:4 0 16 30-38 2.37 2.37 DC4 n/a -----------Cage detail info for cage1 ---------Position: ---Fibre Channel Info PortA0 PortB0 PortA1 PortB1 Link_Speed 4Gbps -- -- 4Gbps----------------------------------SFP Info-----------------------------------FCAL SFP -State- --Manufacturer-- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM 0 0 OK FINISAR CORP. 4.2 No No No Yes 1 1 OK FINISAR CORP. 4.2 No No No YesInterface Board Info FCAL0 FCAL1 Link A RXLEDs Green Off Link A TXLEDs Green Off Link B RXLEDs Off Green Link B TXLEDs Off Green LED(Loop_Split) Off OffLEDS(system,hotplug) Green,Off Green,Off-----------Midplane Info----------- Firmware_status Old Product_Rev 2.37 State Normal Op Loop_Split 0VendorId,ProductId 3PARdata,DC4 Unique_ID 10620300000B6300

14. Issue the showpd command to verify that the port for the replaced FC-AL module is now activeand the disks are on the loop.

cli% showpd ----Size(MB)----- ----Ports----Id CagePos Type RPM State Total Free A B 0 0:0:0 FC 15 normal 279808 250112 0:3:1* 1:4:1 1 0:0:1 FC 15 normal 279808 262400 0:3:1 1:4:1* 2 0:0:2 FC 15 normal 279808 250112 0:3:1* 1:4:1 3 0:0:3 FC 15 normal 279808 262656 0:3:1 1:4:1* 4 0:1:0 FC 15 normal 279808 250112 0:3:1* 1:4:1 5 0:1:1 FC 15 normal 279808 262656 0:3:1 1:4:1* 6 0:1:2 FC 15 normal 279808 250368 0:3:1* 1:4:1 7 0:1:3 FC 15 normal 279808 262912 0:3:1 1:4:1*




Replacing a Drive-side Fibre Channel CableTo replace the node-to-drive chassis Fibre Channel cables:1. Connect the maintenance PC to the SP using the serial connection and start an spmaint


the desired system.


3. Issue the showport command and view the node:slot:port information to identify the locationof the cable to be replaced.a. Issue the showcage command to identify the FC-AL module location.

cli% showcageId Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 0 cage0 0:3:1 0 1:4:1 0 16 29-35 2.37 2.37 DC4 n/a 1 cage1 0:3:4 0 1:4:4 0 16 27-36 2.37 2.37 DC4 n/a

b. To locate the drive cage, issue the locatecage cage <ID> command to turn on allLEDs for a short duration.

4. Physically identify the cable and remove it from the node port.5. Physically identify the cable and remove it from the cage port (FC-AL module).6. Carefully remove the cable from the cabinet/rack.7. Install and neatly dress the new cable along the same route.8. Connect the cable at both ends.9. Verify the appropriate LEDs on the controller node and cage ports illuminate.10. Issue the showport command to view the ports’ state.

root@inoded1040:~# showportN:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol0:3:1 initiator ready 2FF70002AC00017F 20310002AC00017F disk FC0:3:2 initiator loss_sync 2FF70002AC00017F 20320002AC00017F free FC0:3:3 initiator loss_sync 2FF70002AC00017F 20330002AC00017F free FC0:3:4 initiator ready 2FF70002AC00017F 20340002AC00017F disk FC0:9:1 peer offline - 0002AC800131 rcip IP



the SP.

Replacing a Midplane AssemblyBefore beginning this procedure, you must migrate data off the drive cage before removing themidplane and migrate data back after replacing a midplane. See “Migrating Data Off the DriveCage” (page 24).Replacing a drive cage midplane requires preparations which are determined after reviewing thecustomer’s system layout. Each site must be evaluated for an efficient and safe replacement withoutbringing down the entire storage system. Determine if there is free disk space to migrate data fromthe drive cage midplane that is being replaced.If applicable, remove the storage system rear door before beginning this procedure.To replace a drive cage midplane assembly:

Replacing a Midplane Assembly 21

1. Wearing a wrist-grounding strap, remove the drive chassis power supplies:a. Identify the power supply and set it to OFF. The power supplies must be removed to

replace the midplane assembly.b. On the cord lock, unfasten the strap wrapped around the AC cord and disconnect the

cord.c. Use a #1 Phillips screwdriver to remove the two screws securing each power supply to

the chassis.d. Pull the handle to remove the power supply from the drive chassis.

2. Note the location of all Fibre Channel cables to be reconnected after FC-AL replacement. Ifnecessary, mark the cables that connect to the FC-AL before removing them. The drive-sideFibre Channel cables are marked to simplify this task.

3. Squeeze the tabs on the sides of the Fibre Channel cables and pull to disconnect them fromthe SFP.

4. Use a #2 Phillips screwdriver to loosen the screws that secure the two FC-AL modules to thedrive cage, then slide the boards out slightly to disengage from the midplane.

5. Use a #2 Phillips screwdriver to loosen the captive screw that secures the drive magazine tothe chassis.

6. Pull each drive magazine out slightly to disengage from the drive cage.7. Use a #1 Phillips screwdriver to remove the four screws and spacers that secure the assembly

to the drive chassis housing and grasp the midplane bracket at the middle to pull the assemblyout of the drive chassis (“Removing the Midplane Assembly” (page 22)).

Figure 11 Removing the Midplane Assembly

8. Use a #1 Phillips screwdriver to remove the eight screws that attach the midplane to themidplane assembly (“Midplane Removal” (page 23)).


Figure 12 Midplane Removal

9. Remove the replacement midplane from its shipping container.10. Verify the replacement midplane speed is switched to 4GB (“Midplane Switch” (page 23)).

Figure 13 Midplane Switch

11. Place the removed midplane into the container for return to HP.12. Use a #1 Phillips screwdriver to attach the new midplane to the midplane assembly by securing

the eight screws previously removed.13. Slide the replacement drive cage midplane assembly into the drive chassis until it is fully

seated.14. Reinstall and tighten the screws that secure the drive cage midplane assembly to the drive

chassis housing. Do not overtighten the screws.


15. At the front of the system, slide each drive magazine back into the drive cage and tighten thecaptive screw. Do not overtighten the screws.

16. Slide the two FC-AL cards back into the drive cage and tighten the screws securing them tothe drive cage. Do not overtighten the screws.

17. Reconnect the Fibre Channel cables to their respective FC-AL modules in the drive chassis.18. Replace the drive chassis power supplies:

a. Slide the replacement power supply into the rear of the drive chassis until fully seated.b. Use a #1 Phillips screwdriver to tighten the screws that secure the power supply to the

drive chassis housing. Do not overtighten the screws.c. Reconnect the AC cord and fasten the strap around the cord and cord lock.d. Set the power supply to the ON position and verify that the power supply LEDs are green.

19. Verify that all LEDs in the drive magazines and FC-AL modules appear green or flashing greenand the hot-plug LEDs on the drive magazines and drive cage FC-AL modules are not lit.

20. After completing the drive cage midplane replacement procedure, migrate data back ontothe system. See “Migrating Data Back to the Drive Cage” (page 25).

Migrating Data Off the Drive CageTo migrate data off the drive cage:1. Connect the maintenance PC to the SP using the serial connection and start an spmaint


the desired system.3. Issue the showpd -sortcol 1 command to determine all PD IDs in the cage. The 1 indicates

which column to sort by.4. Issue the setpd ldalloc off <pdid> command to set the selected PD’s allocation flags

to OFF for each disk ID, where <PD_ID> is the physical disk identification.5. Issue the showpd -sortcol 1 command to confirm the setting. The PDs set to OFF will

indicate 0 free space.

cli% showpd -sortcol 1 ---Size(MB)---- -----------Ports-----------Id CagePos Type RPM State Total Free A B 0 0:0:0 FC 15 normal 279808 250112 0:3:1* 1:4:1 1 0:0:1 FC 15 normal 279808 262400 0:3:1 1:4:1* 2 0:0:2 FC 15 normal 279808 250112 0:3:1* 1:4:1 3 0:0:3 FC 15 normal 279808 262656 0:3:1 1:4:1* 4 0:1:0 FC 15 normal 279808 250112 0:3:1* 1:4:1 5 0:1:1 FC 15 normal 279808 262656 0:3:1 1:4:1* 6 0:1:2 FC 15 normal 279808 250368 0:3:1* 1:4:1 7 0:1:3 FC 15 normal 279808 262912 0:3:1 1:4:1*

6. Issue the servicemag start <X Z> command, where X is the drive cage number andZ is the location of the drive magazine in the drive chassis.

NOTE: The servicemag start command moves all used chunklets on the magazine.This is executed simultaneously for each disk drive and takes approximately 20 seconds foreach used chunklet.

cli% servicemag start 0 1Are you sure you want to run servicemag?select q=quit y=yes n=no: y


servicemag start 0 1... servicing disks in mag: 0 1... normal disks: WWN [5000C50002841761] Id [56] diskpos [0] .................... WWN [5000C500028486F2] Id [57] diskpos [1] .................... WWN [5000C5000284173F] Id [58] diskpos [2] .................... WWN [5000C50002841675] Id [59] diskpos [3] ... not normal disks: The servicemag start operation will continue in the background.

7. Issue the servicemag status -d <X Z> command to monitor progress, where X is thedrive cage number and Z is the location of the drive magazine from the previously issuedservicemag start command.

cli% servicemag status -dCage 0, magazine 1:The magazine is being brought offline due to a servicemag start.The last status update was at Wed Sep 16 07:52:29 2010.The cumulative output so far is:servicemag start 0 1... servicing disks in mag: 0 1... normal disks: WWN [5000C50002841761] Id [56] diskpos [0] .................... WWN [5000C500028486F2] Id [57] diskpos [1] .................... WWN [5000C5000284173F] Id [58] diskpos [2] .................... WWN [5000C50002841675] Id [59] diskpos [3] ... not normal disks: ... relocating chunklets to spare space...... relocating chunklets from degraded raid sets to spare space

8. Repeat step 6 for all drive magazines in the cage then continue to “Replacing a MidplaneAssembly” (page 21).

NOTE: Up to five servicemag -start commands may be running at once. Ensure oneis proceeding before starting the next.

When the command completes successfully, Succeeded displays, the hot-plug LED illuminatesand the drive magazine status LEDs blink slowly.

NOTE: Servicemag cannot bypass and set the hot-plug LED on the last drive magazinebecause the system does not want to lose communication with the cage. Consequently, thelast ESI drive magazine will not have the hot-plug LED illuminated, but three of the four disksshould be spundown. If this is the case and all other servicemag operations in the cage aresuccessful, the midplane may be replaced.

NOTE: Allow two minutes for the disks on the magazine to spin up before checking themagazine LEDs.

Migrating Data Back to the Drive Cage

NOTE: The replacement of a midplane will give the cage a new number because the midplaneserial number is different. Because the old cage number (name) will no longer exist, servicemagresume must be issued to the new cage number (name).

To migrate data back to the drive cage:1. In the SP window, issue theshowcage command and note the new cage number to be used

with the servicemag resume command.


2. Issue the showpd command and check that all drive magazines are in a valid state.

cli% showpd ---Size(MB)---- ----Ports----Id CagePos Type RPM State Total Free A B 0 0:0:0 FC 15 degraded 279808 250112 0:3:1* 1:4:1 1 0:0:1 FC 15 normal 279808 262400 0:3:1 1:4:1* 2 0:0:2 FC 15 normal 279808 250112 0:3:1* 1:4:1 3 0:0:3 FC 15 normal 279808 262656 0:3:1 1:4:1*

3. Issue the servicemag resume <X Z> command, where X is the new drive cage numberand Z is the location of the drive magazine in the drive chassis.

cli% servicemag resume 4 0Are you sure you want to run servicemag?select q=quit y=yes n=no: yservicemag resume 4 0... onlooping mag 4 0... checking for valid disks...... disks in mag : 4 0... valid disks: WWN [5000C50002841761] Id [56] diskpos [0] .................... WWN [5000C500028486F2] Id [57] diskpos [1] .................... WWN [5000C5000284173F] Id [58] diskpos [2] .................... WWN [5000C50002841675] Id [59] diskpos [3] ... not valid disks: ... firmware is current on pd WWN [5000C50002841761] Id [56] ... firmware is current on pd WWN [5000C500028486F2] Id [57] ... firmware is current on pd WWN [5000C5000284173F] Id [58] ... firmware is current on pd WWN [5000C50002841675] Id [59] ... verifying disk 56 ... verifying spare space for disks 56 and 56... verifying disk 57 ... verifying spare space for disks 57 and 57... verifying disk 58 ... verifying spare space for disks 58 and 58... verifying disk 59 ... verifying spare space for disks 59 and 59... playback chunklets from pd WWN [5000C50002841761] Id [56] ... playback chunklets from pd WWN [5000C500028486F2] Id [57] ... playback chunklets from pd WWN [5000C5000284173F] Id [58] ... playback chunklets from pd WWN [5000C50002841675] Id [59] The servicemag resume operation will continue in the background.

The servicemag resume process can take several hours or more to complete, depending onthe number of chunklets to be relocated. Once servicemag status shows that chunklets arebeing relocated from spare space, continue to start the next servicemag. Servicemagcompletion may be monitored with the servicemag status command.

NOTE: Up to five servicemag -resume commands may be running at once. Ensure oneis proceeding before starting the next.

4. Issue the servicemag status -d <X Z> command where X is the drive cage numberand Z is the location of the drive magazine from the previously issued servicemag startcommand.

cli% servicemag status -d 4 0The magazine was brought online by a successful servicemag resume command.


The command completed at Wed Nov 21 07:57:38 2010.The output of the servicemag resume was:servicemag resume 4 0... onlooping mag 4 0... checking for valid disks...... disks in mag : 4 0... valid disks: WWN [5000C50002841761] Id [56] diskpos [0] .................... WWN [5000C500028486F2] Id [57] diskpos [1] .................... WWN [5000C5000284173F] Id [58] diskpos [2] .................... WWN [5000C50002841675] Id [59] diskpos [3] ... not valid disks: ... firmware is current on pd WWN [5000C50002841761] Id [56] ... firmware is current on pd WWN [5000C500028486F2] Id [57] ... firmware is current on pd WWN [5000C5000284173F] Id [58] ... firmware is current on pd WWN [5000C50002841675] Id [59] ... verifying disk 56 ... verifying spare space for disks 56 and 56... verifying disk 57 ... verifying spare space for disks 57 and 57... verifying disk 58 ... verifying spare space for disks 58 and 58... verifying disk 59 ... verifying spare space for disks 59 and 59... playback chunklets from pd WWN [5000C50002841761] Id [56] ... playback chunklets from pd WWN [5000C500028486F2] Id [57] ... playback chunklets from pd WWN [5000C5000284173F] Id [58] ... playback chunklets from pd WWN [5000C50002841675] Id [59] ... All chunklets played back / relocated.... no chunklets to moveservicemag resume 4 0 -- Succeeded

When the command completes successfully, Succeeded displays.

5. Repeat step 3 until all drive magazines in the cage have been restored then continue to thenext step.

6. Issue the showcage -d command and check all the ports and connections are in operablecondition.

cli% showcage -d cage0Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side 0 cage0 0:3:1 0 1:4:1 0 16 32-38 2.37 2.37 DC4 n/a

7. When all servicemag -resume operations have successfully completed, the old cage nameshould be removed from the system’s memory. Enter servicecage remove <cage_name>where cage_name is the old (missing) cage number (name) to remove the old cage name.


Menu and to log out of the session.10. Disconnect the serial cable from the maintenance PC or the red cross-over Ethernet cable from

the laptop and coil and replace the cable behind the SP.11. Close and lock the rear door.

Replacing a Drive Chassis Power SupplyTo replace a power supply in a drive chassis:1. Connect the maintenance PC to the SP using the serial connection and start an spmaint

session.

Replacing a Drive Chassis Power Supply 27


3. Issue the showcage –d <cageID> command to verify the power supply LED and powersupply state.

cli% showcage -d cage0 -----LoopA----- -----LoopB-----Id Name A0 A1 Pos B0 B1 Pos Drives Temp RevA RevB Model Side 0 cage0 0:0:1 1:0:1 0 2:0:1 3:0:1 0 1I though6 31-35 08 08 DC4 n/a-----------Cage detail info for cage0 ---------Position: --------------Midplane Info------------ VendorId,ProductId 3PARdata,DC4 Serial_Num OPS69907C0149F3 Node_WWN 20000050CC0149F3 TempSensor_State OK TempSensor_Value 39 OpsPanel_State OKAudible_Alarm_State Muted ID_Switch 1 Cage_State OKInterface Board Info LoopA LoopB Firmware_status Current Current Product_Rev 08 08 IFC_State OK OK ESH_State OK OK Master_CPU Yes No Loop_Map valid valid Link_Speed 4Gbps 4Gbps Port0_State OK OK Port1_State No_SFP No_SFP Port2_State No_SFP No_SFP Port3_State OK OKPower Supply Info State Fan State AC Model ps0 Failed Med Speed Failed -- ps1 OK Med Speed OK --

4. Remove a power supply from the rear of the drive chassis:a. Identify the power supply requiring replacement and set it to the OFF position.b. On the cord lock, unfasten the strap wrapped around the AC cord and disconnect the

cord.c. Use a #1 Phillips screwdriver to remove the two screws securing each power supply to

the chassis (Figure 14 (page 29)).


d. Pull the handle to remove the power supply from the drive chassis.

Figure 14 Removing a Power Supply

5. Remove the replacement power supply from its protective packaging and verify that the powersupply is set to the OFF position.

6. Place the removed power supply into the protective packaging for return to HP.7. Replace a power supply:

a. Slide the replacement power supply into the rear of the drive chassis until fully seated.b. Use a #1 Phillips screwdriver to tighten the screws that secure the power supply to the

drive chassis housing. Do not overtighten the screws.c. Reconnect the AC cord and fasten the strap around the cord and cord lock.d. Set the power supply to the ON position and verify that the power supply LEDs are green.

8. In the SP window, issue the showcage –d <cageID> command to verify the power statusof the drive cage power supply is OK.

cli% showcage -d cage0 -----LoopA----- -----LoopB-----Id Name A0 A1 Pos B0 B1 Pos Drives Temp RevA RevB Model Side 0 cage0 0:0:1 1:0:1 0 2:0:1 3:0:1 0 16 31-35 08 08 DC4 n/a-----------Cage detail info for cage0 ---------Position: --------------Midplane Info------------ VendorId,ProductId 3PARdata,DC4 Serial_Num OPS69907C0149F3 Node_WWN 20000050CC0149F3 TempSensor_State OK TempSensor_Value 39 OpsPanel_State OKAudible_Alarm_State Muted ID_Switch 1 Cage_State OKInterface Board Info LoopA LoopB Firmware_status Current Current

Replacing a Drive Chassis Power Supply 29

Product_Rev 08 08 IFC_State OK OK ESH_State OK OK Master_CPU Yes No Loop_Map valid valid Link_Speed 4Gbps 4Gbps Port0_State OK OK Port1_State No_SFP No_SFP Port2_State No_SFP No_SFP Port3_State OK OKPower Supply Info State Fan State AC Model ps0 OK MedSpeed OK -- ps1 OK MedSpeed OK --





2 Controller Node Maintenance Procedures

CAUTION: When handling controller node components, observe the precautions in “Precautions”(page 87).

NOTE: Guided maintenance scripts are available to facilitate these procedures. Refer to “ControllerNode Maintenance Procedures” (page 31) for additional information.

Replacing a Controller Node Fan Module

CAUTION: In a controller node, you may remove only one fan at a time. If two fans for one nodeare inoperable at the same time, the storage system will shutdown.

The V400 controller node chassis can hold up to eight fan modules, that each hold two fans, andthe V800 can hold up to 16.

CAUTION: Before removing a node fan module, the replacement node fan module should beready for installation and removed from its packaging, inspected for any packaging material insideand placed where it can be quickly and easily accessed to ensure actual service time is less thanthe maximum service time (60 seconds or less) and to avoid overheating of other components.

To replace a node fan module:1. Connect the maintenance PC to the SP using the serial connection and start an spmaint


the desired system.3. To identify the node fan module that needs to be replaced, issue the shownode -fan

command and note the fan ID and node number to use in the next step.4. Issue the servicenode start -fan <fanID> <nodeID> command to prepare the

node fan for service.

NOTE: The system will light the service LED blue when there is a failure, but theservicenode start command confirms the correct component is being serviced.

5. Identify the fan to remove and verify that the service LED is blue.6. Pull the node fan lever outward to disengage the node fan and gently pull the lever and node

fan out of the chassis (Figure 15 (page 31)).

Figure 15 Removing the Controller Node Fan

7. Remove the replacement fan from its protective packaging.8. While the node fan lever is in the open position, gently slide the replacement fan into the node

chassis compartment and press the lever into the closed position.9. Issue the servicenode end <nodeID> command to end servicing mode.10. Issue the shownode -fan command to verify that the node fan’s state and speed are normal

and the node fan LED is green.

Replacing a Controller Node Fan Module 31


Menu and to log out of the session.13. Place the removed fan into protective packaging for return to HP.

Replacing a Controller Node Power SupplyTo replace a controller node power supply:1. Connect the maintenance PC to the SP using the serial connection and start an spmaint


the desired system.3. Issue the shownode -ps command to confirm the power supply state.

cli% shownode -psNode PS ---Serial--- -PSState- FanState ACState DCState 0 0 091392-00FM7 OK OK OK OK 0 1 091392-00FPY OK OK OK OK 1 0 091392-00FLJ OK OK OK OK 1 1 091392-00FN0 OK OK OK OK

4. Issue the servicenode start -ps <psID> <nodeID> command to prepare the powersupply for service.


5. Identify the power supply that requires replacement and verify that the service LED next to itis blue, indicating the power supply is ready to be serviced.

6. Rotate the cable manager tray towards the nodes in order for the power supplies to be serviced.


7. Remove the power supply:a. On the power supply, push the cord lock towards the nodes to disengage the cord lock

from the AC cord (Figure 16 (page 33)).

Figure 16 Cord Lock on a Controller Node Power Supply

b. Detach the AC cord from the power supply.c. Grab the handle and press the release lever with your thumb and pull the power supply

to remove (Figure 17 (page 33)).

Figure 17 Release Lever on a Power Supply

8. Remove the replacement power supply from its protective packaging.9. Place the removed power supply into the protective packaging for return to HP.10. Replace the power supply:

a. Grab the handle and slide the replacement power supply into the slot until it is fully seated.b. Reconnect the AC cord to the power supply and push the cord lock into position around

the AC cord.c. Confirm that the power supply status and AC LEDs are green.

11. Reconnect the AC cord to the power supply and push the cord lock into position around theAC cord.

12. Confirm that the power supply status and AC LEDs are green.13. Return the cable manager tray to its normal position.14. In the SP window, issue the shownode -ps command to verify the power supply state.

cli% shownode -ps

Node PS ---Serial--- -PSState- FanState ACState DCState 0 0 091392-00FM7 OK OK OK OK 0 1 091392-00FPY OK OK OK OK

Replacing a Controller Node Power Supply 33

1 0 091392-00FLJ OK OK OK OK 1 1 091392-00FN0 OK OK OK OK

15. Issue the servicenode end <nodeID> command to end servicing mode.16. Issue the checkhealth -svc -detail command to verify the system is healthy.17. In the SP window, issue the exit command and select X to exit from the 3PAR Service Processor

Menu and to log out of the session.18. Disconnect the serial cable from the maintenance PC and replace the cable behind the SP.19. Close and lock the rear door.

Replacing a Battery ModuleTo replace a battery module:1. Connect the maintenance PC to the SP using the serial connection and start an spmaint


the desired system.3. Issue the showbattery command to verify the battery’s state is failed.

cli% showbatteryNode PS Bat Serial -State- ChrgLvl(%) -ExpDate-- Expired Testing 0 0 0 00000153 Failed 0 05/13/2013 No No 1 1 0 00000147 OK 100 05/13/2013 No No

4. Issue the servicenode start -bat <nodeID> command to prepare the battery modulefor service.


5. At the front of the system, identify the battery module that requires replacement and verify thatthe service LED is blue.

6. Remove the bezel that covers the battery module to be replaced.7. Loosen the captive screw in the center of the battery module.

Figure 18 Loosening the Battery Module Screw

8. Grab the handle and pull the battery module out of the chassis. Removing the battery moduleautomatically turns off all LEDs.

CAUTION: The battery module weighs approximately 20 pounds. Use caution when removingthe module from the battery compartment.

9. Remove the replacement battery module from its protective packaging.10. Unscrew and fully open the handle and slide the battery module into the chassis opening until

it stops. Push the center of the battery module while gently pushing the handle closed tocomplete installation.


NOTE: If you attempt to close the handle, but if the handle starts deforming (for example,the top moves but the bottom does not), push in at the center of the battery module while gentlypushing the handle closed to overcome the resistance between the guide pins and the holesin the battery module.

11. Tighten the captive screw that secures the battery module to the battery compartment. Do notovertighten the screw.

12. Place the removed battery module into the protective packaging for return to HP.

CAUTION: Battery modules contain hazardous materials and should be disposed of properly.

13. Issue the servicenode end <nodeID> command to end servicing mode.14. Issue the showbattery command to verify that the battery module information is properly

set.

cli% showbatteryNode Serial -State- ChrgLvl(%) -ExpDate- Expired Testing 0 00000153 OK 100 05/03/2013 No No 1 00000147 OK 100 05/03/2013 No No

NOTE: The serial number and expiration date is read by the system and automatically set.

15. Verify that the LEDs are green.16. Replace the bezel that covers the battery module.17. Issue the checkhealth -svc -detail command to verify the system is healthy.18. In the SP window, issue the exit command and select X to exit from the 3PAR Service Processor

Menu and to log out of the session.19. Disconnect the serial cable from the maintenance PC and replace the cable behind the SP.

Replacing a Controller NodeNOTE: If the failed node is already offline, it is not necessary to shutdown the node because itis already not part of the cluster. Skip to step 12.

To replace a controller node:1. Connect the maintenance PC to the SP using the serial connection and start an spmaint


the desired system.3. Issue the shownode command to verify the node’s state.

cli% shownode Control Data Cache Node -Name- -State- Master InCluster --LED-- Mem(MB) Mem(MB) Available(%) 0 1400510-0 OK Yes Yes GreenBlnk 16384 32768 100 1 1400510-1 DEGRADED No Yes AmberBlnk 16384 32768 100

4. Issue the servicenode start <nodeID> command to service the node. The node LEDswill appear blue.

5. Type exit to end the CLI session and return to the 3PAR Service Processor Menu.

Replacing a Controller Node 35

6. Before disconnecting the cables from the front of the controller node, note the locations ot thecables, or note or label them. The drive-side Fibre Channel cables are marked to simplify thistask.

7. Select option 4 InServ Product Maintenance.8. Select option 6 Halt an InServ cluster/node, then select the desired system.9. Select the desired node and confirm all prompts to halt the node.10. Allow 2-3 minutes for the node to halt, then verify that the node status LED is flashing green

and the node service LED is blue indicating that the node has been halted.11. Set the node power switch to the OFF position to turn off power on the node.


12. Wearing a wrist-grounding strap, remove the node:a. Pull the insertion/removal levers out to release the node.

Figure 19 Opening the Insertion/Removal Levers on a Controller Node

b. Pull the controller node insertion/removal lever out to disengage the node from the chassismidplane.

c. Slide the node part way out of the chassis and hold the node by the bottom and top toremove and carry (Figure 20 (page 37)) and place it on an ESD-safe work surface.

Figure 20 Removing the Controller Node from the Chassis


13. Remove the replacement controller node from its protective packaging and place it onto anESD-safe work surface next to the failed node.

14. Because the replacement node will not contain any node-disk (SSD), PCI adapters or memory,the following must be performed:a. One at a time, remove the node-disk and PCI adapters from the failed node and install

them in the same slots in the replacement node. See “Replacing a Node Disk” (page 40)and “Replacing a PCI Adapter” (page 44).

NOTE: It may be necessary to remove some blank PCI slot covers from the replacementnode to install PCI adapters. Install these slot covers in the failed node for return to HP.

b. Remove the top cover from both nodes and move the four control cache DIMMs and theeight data cache DIMMs to the replacement node, see “Replacing a Cache DIMM”(page 47). Reinstall the top covers on both nodes.

15. Properly install the blank disk into the failed node. Refer to “Replacing a Node Disk” (page 40)for more information. If the disk in the failed node is questionable, replace the node disk andperform node rescue on the blank disk in the replacement node to install necessary software.When the node disk is being replaced, you must perform node rescue. See “Performing NodeRescue” (page 93).

16. Properly secure the parts and cover on the failed controller node then place it into the protectivepackaging for return to HP.

WARNING! Make sure the node power switch is set to the OFF position before insertingthe node into the node chassis.


17. Replace the node:a. Orient the node properly and align the bottom of the node with the grooves in its slot

and slide the node into the node chassis.

Figure 21 Replacing the Node

b. Push the insertion levers in quickly until the node is seated securely.

Figure 22 Pushing the Node Insertion Levers

WARNING! Do not connect the cables to the node at this time.

18. Set the node power switch to the ON position to turn on power on the node.


NOTE: Once power is applied to the node, it begins to boot. This process can takeapproximately 5-10 minutes. When complete, the node becomes part of the cluster.

19. Verify that the node LED is blinking green indicating that the node has joined the cluster.20. In the 3PAR Service Processor Menu, select option 7 Interactive CLI for an InServ, then select

the desired system.21. Issue the shownode command to verify the node has joined the cluster.

cli% shownode Control Data CacheNode --Name--- -State-- Master InCluster ---LED--- Mem(MB) Mem(MB) Available(%) 0 1400510-0 OK Yes Yes GreenBlnk 16384 32768 100 1 1400510-1 OK No Yes AmberBlnk 16384 32768 100

22. Reboot the replaced node one more time to synchronize software and hardware values byissuing the shutdownnode reboot <node_ID> command.

23. After the node reboots a second time, monitor the node status LED and verify again that allnodes have joined the cluster by issuing the shownode command.

24. Reconnect the customer’s Ethernet cable, if applicable, and all other cables to the node oncethe node has rebooted.

CAUTION: Do not reconnect host cables without verifying the controller node is functioningproperly.



Replacing a Node DiskTo replace the node disk:1. Connect the maintenance PC to the SP using the serial connection and start an spmaint session.2. Select option 4 InServ Product Maintenance.3. Select option 6 Halt an InServ cluster/node, then select the desired system.

NOTE: If the failed node is already offline, it is not necessary to shutdown the node becauseit is not part of the cluster.

4. Select the desired node and confirm all prompts to halt the node.5. Allow 2-3 minutes for the node to halt, then verify that the node status LED is flashing green

(three blinks per second) and the node service LED is blue indicating that the node has beenhalted.

6. Set the node power switch to the OFF position to turn off power on the node.7. Loosen the captive screw on the node disk and pull the disk from the node to remove.


Figure 23 Replacing the Disk in the Node

8. Remove the replacement node disk from its protective packaging.9. Place the failed node disk in the electrostatic packaging for return to HP.10. Slide the replacement disk into the node and finger-tighten the captive screw to secure the

disk in the node.11. Perform node rescue, as described in “Performing Node Rescue” (page 93).

Replacing a Node Disk 41

Replacing an SFP ModuleA maximum of four SFP modules are located in each adapter located at the rear of the cabinetand node chassis (Figure 24 (page 42)).

Figure 24 PCI Adapter

To replace an SFP module:1. Connect the maintenance PC to the SP using the serial connection and start an spmaint


the desired system.3. Issue the showport command to view the ports’ state.


4. Issue the showport -sfp command to verify which SFP requires replacement.

cli% showport -sfpN:S:P -State- -Manufacturer- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM0:3:1 OK FINISAR_CORP. 8.3 No No No Yes0:3:2 DEGRADED AVAGO 8.3 No No Yes Yes0:3:3 OK AVAGO 8.3 No No Yes Yes0:3:4 OK FINISAR_CORP. 8.3 No No No Yes0:9:1 OK FINISAR_CORP. 8.3 No No No Yes

5. Issue theservicenode start -pci <slot> <nodeID> command to prepare the SFPfor service. Verify that the service LED for the PCI adapter is blue.

6. Identify the SFP module that requires replacement.7. Wearing a wrist-grounding strap, disconnect the cable from the SFP.8. Lift out the retaining clip of the SFP and carefully slide it out of the slot.


Figure 25 Removing the SFP on a PCI Adapter

9. Remove the replacement SFP module from its protective packaging.10. Place the defective SFP module into the protective packaging for return to HP.11. Carefully slide the replacement SFP module into the adapter until fully seated and close the

wire handle to secure it in place.12. Reconnect the cable to the SFP module and verify that the link status LED is solid green.13. Issue the showport command to verify that the ports are in good condition.


14. Issue the showport -sfp command to verify that the replaced SFP is connected and theState is listed as OK (not degraded).

cli% showport -sfpN:S:P -State- -Manufacturer- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM0:3:1 OK FINISAR_CORP. 8.3 No No No Yes0:3:2 OK AVAGO 8.3 No No Yes Yes0:3:3 OK AVAGO 8.3 No No Yes Yes0:3:4 OK FINISAR_CORP. 8.3 No No No Yes0:9:1 OK FINISAR_CORP. 8.3 No No No Yes



Replacing an SFP Module 43

Replacing a PCI AdapterA maximum of nine PCI adapters are located in the controller nodes (Figure 26 (page 44)).

Figure 26 PCI Adapters in the Controller Node

To replace a PCI adapter:

NOTE: If the node previously halted due to a PCI adapter problem, it is not necessary to shutdownthe node because it is already not part of the cluster.

1. Connect the maintenance PC to the SP using the serial connection and start an spmaintsession.


3. Issue the servicenode start -pci <slot> <nodeID> command to prepare the PCIadapter for service.


4. Identify the PCI adapter to remove and verify that the service LED is blue (located on the slotabove or below the adapter).

5. In the SP window, issue the exit command to return to the 3PAR Service Processor Menu.6. Before disconnecting the cables from the front of the controller node, note the locations of the

cables, or note and label them. The drive-side Fibre Channel cables are marked to simplifythis task.



and the node service LED is blue indicating that the node has been halted.11. Set the node power switch to the OFF position to turn off power on the node.

NOTE: PCI adapters are not hot pluggable. You must turn off power on the node.

12. Press your thumb at the base of the adapter and press in on the ejector handle release triggerwhile pulling the ejector handle outward to remove the PCI adapter from the slot.

Figure 27 Removing the PCI Adapter

13. Remove the new adapter from the protective packaging.14. Move all the SFPs from the old PCI adapter to the replacement PCI adapter:

a. In the old adapter, lift out the SFP retaining clip and carefully slide it out of the slot.b. Close the clip on the SFP and fully insert it into the new adapter.

15. Place the removed PCI adapter (with the SFPs removed) into the protective packaging forreturn to HP.

16. Press down the ejector handle release trigger and pull the push rod to fully extend thereplacement PCI adapter.

17. Insert the replacement adapter into the same slot that held the removed adapter. Push in thepushrod until the adapter is fully inserted and locked in place.

Replacing a PCI Adapter 45

Figure 28 Replacing a PCI Adapter

18. Reconnect the Fibre Channel cables to the adapter.19. Set the node power switch to the ON position to apply power to the node.


20. Verify that the node status LED is blinking green in unison with other node LEDs, indicatingthat the node has joined the cluster.

21. In the SP window, select option 7 Interactive CLI for an InServ, then select the desired system.22. Issue the shownode command to verify the node has joined the cluster.

cli% shownodeControl Data CacheNode ---Name--- -State- Master InCluster --LED-- Mem(MB) Mem(MB) Available(%) 0 inoded1040 OK Yes Yes GreenBlnk 16384 32768 100 1 inoded108c OK No Yes GreenBlnk 16384 32768 100

23. Issue the showport command to verify the ports that are connected are ready.

NOTE: A port must be connected and correctly communicating to be ready. Verify if theport (State column) is ready.

cli% showportN:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol0:3:1 initiator ready 2FF70002AC00017F 20310002AC00017F disk FC0:3:2 initiator loss_sync 2FF70002AC00017F 20320002AC00017F free FC0:3:3 initiator loss_sync 2FF70002AC00017F 20330002AC00017F free FC0:3:4 initiator ready 2FF70002AC00017F 20340002AC00017F disk FC

24. Issue the showport -i command to verify that the correct card is installed in the correctslot.

cli% showport -iN:S:P Brand Model Rev Firmware Serial HWType


0:3:1 EMULEX LPe12004 03 2.00.X.1 BT94849061 FC 0:3:2 EMULEX LPe12004 03 2.00.X.1 BT94849061 FC 0:3:3 EMULEX LPe12004 03 2.00.X.1 BT94849061 FC 0:3:4 EMULEX LPe12004 03 2.00.X.1 BT94849061 FC



Replacing a Cache DIMMController nodes contain two types of DIMMs, control cache and data cache.

NOTE: If the failed node is already halted, it is not necessary to shutdown the node because itis not part of the cluster.

To replace a cache DIMM:1. Connect the maintenance PC to the SP using the serial connection and start an spmaint


the desired system.3. Issue the shownode -i command to identify the DIMM manufacturer and manufacturer part

number.

cli% shownode -i----------------------------------------Physical Memory-----------------------NodeSlotSlotIDName Type Manufacturer -PartNumber- -Serial- -Rev-Size(MB)0 0 J4200 DIMM0 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F1023 4731 40960 1 J4300 DIMM1 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F1037 4731 40960 2 J4400 DIMM2 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F0FAD 4731 40960 3 J4500 DIMM3 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F0FBA 4731 40960 0 J10700 DIMM0.0.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9AE 0100 40960 1 J10900 DIMM0.1.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9A8 0100 40960 2 J10800 DIMM0.0.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9AD 0100 40960 3 J11000 DIMM0.1.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9AA 0100 40960 4 J11300 DIMM1.0.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9AF 0100 40960 5 J11500 DIMM1.1.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9AC 0100 40960 6 J11400 DIMM1.0.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9B0 0100 40960 7 J11600 DIMM1.1.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9AB 0100 40961 0 J4200 DIMM0 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F11A3 4731 40961 1 J4300 DIMM1 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F11A4 4731 4096

Replacing a Cache DIMM 47

1 2 J4400 DIMM2 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F11A6 4731 40961 3 J4500 DIMM3 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F11A7 4731 40961 0 J10700 DIMM0.0.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 D44DDFD1 0100 40961 1 J10900 DIMM0.1.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E13D90D4 0100 40961 2 J10800 DIMM0.0.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 D44DDFD5 0100 40961 3 J11000 DIMM0.1.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E13D909E 0100 40961 4 J11300 DIMM1.0.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E13D909F 0100 40961 5 J11500 DIMM1.1.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 D44DDFD9 0100 40961 6 J11400 DIMM1.0.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 D44DDFDE 0100 40961 7 J11600 DIMM1.1.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 D44DDFBD 0100 4096

4. Issue the servicenode start <nodeID> command to service the node. The node LEDswill appear blue.

5. Type exit to end the CLI session and to return to the 3PAR Service Processor Menu.6. Before disconnecting the cables from the front of the controller node, note the locations ot the

cables, or note or label them. The drive-side Fibre Channel cables are marked to simplify thistask.


and the node service LED is blue indicating that the node has been halted.11. Set the node power switch to the OFF position to turn off power on the node.12. Wearing a wrist-grounding strap, remove the node:

a. Pull the insertion/removal levers out to release the node.b. Pull the controller node insertion/removal lever out to disengage the node from the chassis

midplane.c. Slide the node part way out of the chassis and hold the node by the bottom and top to

remove and carry, and place it on an ESD-safe work surface.13. Loosen the captive screw then slide and lift the controller node cover to remove.


Figure 29 Removing the Controller Node Cover

14. Identify the cache DIMM that requires replacement.

Figure 30 Controller Node Board Layout

15. To remove, press outward on the two tabs on the sides of the DIMM.


Figure 31 Removing a DIMM

16. Remove the replacement DIMM from its protective packaging.17. Avoid touching the surface of the DIMM when inserting it into the vacant slot in the controller

node.

Figure 32 Replacing a DIMM

18. Insert the DIMM by pushing downward on the edge of the DIMM until the tabs on both sidessnap into place.


19. Replace the node cover:a. Align the controller node cover with the pegs in their grooves, then slide the cover until

it is properly seated.

Figure 33 Aligning the Pegs on the Node Cover

b. Tighten the captive screw on the node cover.

Figure 34 Tightening the Captive Screw

20. Install the node:a. Align the bottom of the node with the grooves in its slot and slide the node into the node

chassis.b. Push the insertion levers in quickly until the node is seated securely.



22. While the node is booting, connect the Fibre Channel cables and Ethernet cables to the node,if applicable.

23. Verify that the node LED is blinking green indicating that the node has joined the cluster.24. In the SP window, select option 7 Interactive CLI for an InServ, then select the desired system.25. Issue the shownode command to verify the node has joined the cluster.


26. Issue the shownode -i command to verify the memory is operational.

cli% shownode -i-----------------------------------------Physical Memory-----------------------------------Node Slot SlotID Name Type -Manufacturer- -PartNumber---- -Serial- -Rev- Size(MB) 0 0 J4200 DIMM0 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F1023 4731 4096 0 1 J4300 DIMM1 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F1037 4731 4096 0 2 J4400 DIMM2 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F0FAD 4731 4096 0 3 J4500 DIMM3 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F0FBA 4731 4096 0 0 J10700 DIMM0.0.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9AE 0100 4096 0 1 J10900 DIMM0.1.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9A8 0100 4096 0 2 J10800 DIMM0.0.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9AD 0100 4096 0 3 J11000 DIMM0.1.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9AA 0100 4096 0 4 J11300 DIMM1.0.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9AF 0100 4096 0 5 J11500 DIMM1.1.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9AC 0100 4096 0 6 J11400 DIMM1.0.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9B0 0100 4096 0 7 J11600 DIMM1.1.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E40FF9AB 0100 4096 1 0 J4200 DIMM0 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F11A3 4731 4096 1 1 J4300 DIMM1 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F11A4 4731 4096 1 2 J4400 DIMM2 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F11A6 4731 4096 1 3 J4500 DIMM3 FB-DIMM Micron Technology 36HTF51272F667G1D6 DF4F11A7 4731 4096 1 0 J10700 DIMM0.0.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 D44DDFD1 0100 4096 1 1 J10900 DIMM0.1.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E13D90D4 0100 4096 1 2 J10800 DIMM0.0.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 D44DDFD5 0100 4096 1 3 J11000 DIMM0.1.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E13D909E 0100 4096 1 4 J11300 DIMM1.0.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 E13D909F 0100 4096 1 5 J11500 DIMM1.1.0 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 D44DDFD9 0100 4096 1 6 J11400 DIMM1.0.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 D44DDFDE 0100 4096 1 7 J11600 DIMM1.1.1 DDR2_SDRAM Micron Technology 36HTF51272PY-667G1 D44DDFBD 0100 4096




Replacing a Clock BatteryThe clock inside the controller node uses a 3-V lithium coin battery.To replace the clock battery inside the controller node:1. Connect the maintenance PC to the SP using the serial connection and start a spmaint session.2. In the 3PAR Service Processor Menu, select option 4 InServ Product Maintenance.3. Select option 6 Halt an InServ cluster/node, then select the desired system.

NOTE: If the node is already offline, it is not necessary to shutdown the node because it isalready not part of the cluster.

4. Select the desired node and confirm all prompts to halt the node.5. Allow 2-3 minutes for the node to halt, then verify that the node status LED is flashing green

and the node service LED is blue indicating that the node has been halted.6. Before disconnecting the cables from the front of the controller node, note the locations ot the


7. Set the node power switch to the OFF position to turn off power on the node.8. Wearing a wrist-grounding strap, remove the node:

a. Pull the insertion/removal levers out to release the node.b. Pull the controller node insertion/removal levers out to disengage the node from the

chassis midplane.c. Slide the node part way out of the chassis and hold the node by the bottom and top to

remove and carry, and place it on an ESD-safe work surface.9. Loosen the captive screw then slide and lift the controller node cover to remove.10. Locate the clock battery.11. Remove the clock battery by pulling aside the retainer clip and pulling the battery up from the

battery holder (Figure 35 (page 53)). Avoid touching the internal node components whenremoving the battery.

Figure 35 Removing the Clock Battery

Replacing a Clock Battery 53

12. Insert the replacement 3-V lithium coin battery into the clock battery slot with the positive-sidefacing away from the retaining clip.

13. Install the node cover:a. Align the controller node cover with the pegs in their grooves, then slide the cover until

it is properly sealed.b. Tighten the captive screw on the node cover.

14. Install the node:a. Align the bottom of the node with the grooves in the slot and slide the node into the node

chassis.b. Close the insertion levers in quickly until the node is seated securely.



16. While the node is booting, connect the Fibre Channel cables and Ethernet cables to the node,if applicable.

17. Verify that the node LED is blinking green indicating that the node has joined the cluster.18. In the SP window, select option 7 Interactive CLI for an InServ, then select the desired system.19. Issue the shownode command to verify that the node has joined the cluster.20. Issue the showdate command to confirm the clock setting is correct.21. Issue the checkhealth -svc -detail command to verify the system is healthy.22. In the SP window, issue the exit command and select X to exit from the 3PAR Service Processor


Replacing the LED Status BoardTo replace the LED status board:1. At the front of the system, unscrew the captive screws on both sides of the LED assembly, then

pull it from the controller node chassis and place on an ESD-safe mat.2. Locate the LED status board on the right side and remove the four screws with a Phillips-head

screwdriver, then lift and remove the LED status board from the assembly (Figure 36 (page 54)).3. Remove the replacement LED status board from its protective packaging.4. Carefully insert the LED status board onto the screw posts, then tighten the four screws to secure

the LED status board to the assembly.

Figure 36 LED Status Board and Assembly


5. Slide the assembly into the slots in the node chassis and hand-tighten the captive screws tosecure it.

6. Verify that the appropriate LEDs illuminate.

NOTE: The controller node status LEDs on the front of the system should match the nodestatus LED of each individual controller node, as seen from the rear of the storage system.

7. Place the removed LED status board into protective packaging for return to HP.8. Connect the maintenance PC to the SP using the serial connection and start an spmaint session.9. In the 3PAR Service Processor Menu, select option 7 Interactive CLI for an InServ, then select

the desired system.10. Issue the checkhealth -svc -detail command to verify the system is healthy.11. Disconnect the serial cable from the maintenance PC and replace the cable behind the SP.12. In the SP window, issue the exit command and select X to exit from the 3PAR Service Processor

Menu and to log out of the session.

Replacing a Controller Node ChassisNOTE: This procedure requires a complete shutdown of the system and requires two people toreplace the node chassis, which weighs 100 lb (45kg).

Procedure 1 To replace a controller node chassis in a V400:1. Connect the maintenance PC to the SP using the serial connection and start an spmaint session.2. In the 3PAR Service Processor Menu, select option 7 Interactive CLI for an InServ, then select

the desired system.3. Shutdown the system and remove power from the storage system. Refer to “Powering Off the

Storage System” (page 79).4. Remove the node power supplies and set them aside for reuse. Refer to step 7 in “Replacing

a Controller Node Power Supply” (page 32).5. Remove the battery modules and set them aside for reuse. Refer to “Replacing a Battery

Module” (page 34).6. Remove the controller node fan modules and set them aside for reuse. Refer to “Replacing a

Controller Node Fan Module” (page 31).7. Before disconnecting the cables from the front of the controller node, note the locations ot the


8. Note the location of all controller nodes in the chassis and mark the controller nodes withthese locations.

9. Move the cable manager tray in service position to clear space to ensure that no cables willbe obstructing the path of the chassis that you are removing. You may need to remove thecable manager tray from the chassis by removing the screws.

10. Remove the nodes from the chassis. Refer to zstep 12 in“Replacing a Controller Node”(page 35).

11. Use a #2 Phillips to loosen the panhead screws that secure the chassis to the rack.

CAUTION: To prevent damage to the controller node chassis, do not hold or lift the chassisby the top cover.

12. With the help of another person, carefully slide the chassis out of the cabinet. Use cautionwhen lifting, as the chassis is heavy.

Replacing a Controller Node Chassis 55

13. Unpack the V400 chassis from the wooden crate:

WARNING! The shipping crates are heavy. Do not attempt to move a crate without usinga pallet jack or fork lift.

a. Use a slotted screwdriver or crowbar to pry off the four spring clamps that secure thecrate door.

b. Remove the crate cover from the base by using the wooden side rails and remove anypacking material that surrounds the controller node chassis.

CAUTION: To prevent damage to the controller node chassis, do not hold or lift thechassis by the top cover.

c. With the help of another person, lift the chassis to remove it from the crate.

NOTE: After unpacking the replacement controller node chassis, place the failednode-chassis into the crate for return to HP.

14. Replace the controller node chassis:a. Slide the replacement controller node chassis into the rack until it rests flush against the

rack and the screw holes in the chassis align with the screw holes in the rack.b. Use a #2 Phillips to tighten the panhead screws that secure the chassis to the rack.

15. Replace the nodes in the chassis. Refer to step 17 in, “Replacing a Controller Node” (page 35).16. Replace the power supplies. Refer to step 10, “Replacing a Controller Node Power Supply”

(page 32).17. Install the battery modules. Refer to “Replacing a Battery Module” (page 34).18. Install the controller node fan modules. Refer to “Replacing a Controller Node Fan Module”

(page 31).19. Push the cable manager tray into normal position or reattach it.20. Install the Ethernet and Fibre Channel cables that connect to the front of the controller node.21. Turn all node power switches to the ON position.22. Wait approximately 10 minutes for the nodes to boot, then verify that all controller node status

LEDs are blinking in unison.23. In the SP window, issue the shownode command to verify all nodes are present.

cli% shownodeControl Data CacheNode ---Name--- -State- Master InCluster ---LED--- Mem(MB) Mem(MB) Available(%) 0 inoded1040 OK Yes Yes GreenBlnk 16384 32768 100 1 inoded108c OK No Yes GreenBlnk 16384 32768 100

24. Issue the checkhealth -svc detail command to verify the system is healthy.25. In the SP window, issue the exit command and select X to exit from the 3PAR Service Processor



3 Power System Maintenance Procedures

CAUTION: When handling a Power Distribution Unit (PDU), observe the precautions as describedin “Precautions” (page 87).

NOTE: Guided maintenance scripts are available to facilitate this procedure. See “GuidedMaintenance” (page 90) for additional information.

Replacing a Power Distribution UnitIn an storage cabinet, the PDUs are located at the rear of the storage system along the left panel.To support redundant power, each power domain must include two power supplies that connectto separate PDUs, and each PDU must connect to an independent AC line (four PDUs are requiredfor redundancy for each cabinet). For more information on redundant power, see the HP P100003PAR Storage System Upgrades Guide.Procedure 2To replace a PDU:1. Remove the rear door of the storage system.2. Set the power breakers on the failed PDU to the OFF position (Figure 37 (page 57)).

Figure 37 Setting the Power Breakers to the OFF Position

3. Use a #2 Phillips screwdriver to loosen the silver captive screws and remove the power cordretaining brackets from the PDU. Set the retaining brackets aside.

Replacing a Power Distribution Unit 57

4. Disconnect the AC cords that connect the power supplies to the failed PDU:a. Note the numbers indicated on the AC cords labels and the PDU circuit breakers to which

they connect (Figure 38 (page 58)).

Figure 38 PDU Circuit Breakers

b. Tuck the disconnected AC cords out of the way so that the PDU can be removed.5. Use a #2 Phillips screwdriver to loosen the black captive screws on the top right and bottom

left of the PDU.

Figure 39 Loosening the PDU Captive Screws

6. Grab the handle and pull the PDU out of the cabinet to remove.


Figure 40 Removing the PDU

7. On the back of the PDU, twist the connector counter-clockwise (1) to disconnect the AC cord(2) (Figure 41 (page 59)).

Figure 41 Disconnecting the Main AC Cord from the PDU

8. Use a #2 Phillips screwdriver to disconnect the green/yellow wire from the back of the failedPDU. The wire should hang from the cabinet.

9. Remove the replacement PDU from its protective packaging.10. Use a #2 Phillips screwdriver to remove the green/yellow wire from the back of the replacement

PDU.11. Place the failed PDU into the packaging for return to HP.

Replacing a Power Distribution Unit 59

12. Use a #2 Phillips screwdriver to connect the green/yellow wire (in the cabinet) to the back ofthe replacement PDU.

13. Confirm the power breakers on the replacement PDU are set to the OFF position beforereconnecting any AC cords.

14. On the back of the replacement PDU, twist the connector counter-clockwise to reconnect theAC cord.

15. Align the two tabs on the PDU with the two notches on the left side of the cabinet and slidethe PDU into the cabinet.

Figure 42 Replacing the PDU

16. Finger-tighten the black captive screws on the top left and bottom right of the PDU, securingthe PDU to the cabinet.

17. Reconnect the AC cords that connect the power supplies to the PDU in the order that they weredisconnected.

18. Use a #2 Phillips screwdriver to reinstall the power cord retaining brackets and secure themto the PDU.

19. Set the PDU circuit breakers to the ON position.20. Verify that the status LEDs on the PDU, and power supplies connected to the PDU, are green.21. Connect the maintenance PC to the SP using the serial connection and start an spmaint


the desired system.23. Issue the checkhealth -svc -detail command to verify the system is healthy.24. In the SP window, issue the exit command and select X to exit from the 3PAR Service Processor

Menu and to log out of the session.25. Disconnect the serial cable from the maintenance PC and replace the cable behind the SP.26. Replace the storage system rear door.

Replacing an AC CordTo replace a PDU:1. For drive chassis power supplies, turn off the power supply that connects to the AC cord.2. Locate the faulty cable in the cable bundles secured to the frame and make note of its location.3. Unfasten the strap that secures the faulty cable to the frame.4. Use a #2 Phillips screwdriver to loosen the silver captive screws of the power cord retaining

bracket and remove from the PDU. Set the retaining bracket aside.5. Unplug the AC cord from the PDU.


6. Unfasten the strap that secures the AC cord to the power supply cord lock.7. Disconnect the damaged AC cord from the power supply.8. Remove the faulty cord from the cabinet.9. Remove the replacement AC cord from its packaging.10. Locate the cable bundle from which the faulty cable was removed and add the replacement

cable to the bundle.11. Label the replacement cable to correspond with the cable being replaced and then route the

replacement through the frame. If possible, reuse the labels from the failed AC cord.12. Connect the replacement AC cord to the power supply and fasten the strap around the cord

and cord lock.13. Connect the replacement AC cord to the PDU receptacle previously occupied by the damaged

cord and reinstall the power cord retaining brackets to the PDU using a #2 Phillips screwdriver.

Figure 43 Securing the AC Cord to the PDU

14. Secure the AC cord to the PDU:a. Position the AC cord between two holes in the cord retention bracket of the PDU.b. Fasten the strap through the holes in the bracket on either side of the AC cord and tighten.c. Push on the AC cord connector to ensure it is fully seated.

15. Fasten the strap to secure the bundle to its original location on the storage system.16. For a drive chassis power supply, turn on the power supply and verify that the LEDs are green.17. Close and lock the rear door.

Replacing an AC Cord 61

4 Replacing a Service Processor

CAUTION: When handling the Service Processor (SP), observe precautions as described in“Precautions” (page 87).

Replacing a Service ProcessorNOTE: If the SP is still functional, refer to the HP 3PAR Service Processor Software RebuildInstructions for SP configuration information retrieval.

To replace a SP:1. Unlock and open the rear door of the storage system.2. Connect the maintenance PC to the SP using the serial connection and start an spmaint

session.

NOTE: If the SP is not functional, power down from the power switch and obtain the SP IPaddress, netmask, gateway address and storage system IP address from the following sources:Installation Checklist or the Systems Assurance and spconfig file or RESCUE file on theconnection portal.

3. In the 3PAR Service Processor Menu, select option 1 SP Control/Status.4. Select option 3 Halt SP and confirm all prompts to halt the SP.5. On the front of the SP, verify that the power LED is no longer illuminated.6. At the rear of the storage system, disconnect all cables from the SP making note of their

locations so they can be reconnected later.7. Remove the AC cord from the rear.8. At the front of the storage system, use a #2 Phillips screwdriver to remove the two screws from

the retainer securing the SP to the storage system.9. Remove the SP from the cabinet.10. Remove the replacement SP from its packaging.11. Insert the failed SP into the packaging for return to HP.12. Align the replacement SP with its shelf on the storage system chassis. Slide the SP into the

cabinet until it is flush with the front.13. Use a #2 Phillips screwdriver to secure the two screws on the SP retainer.14. Open the AC cord lock and place it around the cord end that connects to the SP and use a

#1 Phillips screwdriver to secure the screw (Figure 44 (page 62)).15. At the rear of the storage system, connect the AC cord and any removed cabling.16. Use a #2 Phillips screwdriver to secure the AC cord lock to the rear of the SP.

Figure 44 Connecting the AC Cord Lock to the SP

17. At the front of the storage system, press the power button. On the SP, verify that the powerLED is illuminated.

62 Replacing a Service Processor

18. Initialize software on the SP. Refer to the HP P10000 3PAR Storage System Installation andDeinstallation Guide to begin the Moment of Birth (MOB) process.

Replacing a Service Processor 63

5 Understanding HP P10000 3PAR Storage System LEDStatus

The storage system components have LEDs to indicate whether or not the hardware is functioningproperly and to help identify errors. The LEDs help diagnose basic hardware problems. You canquickly identify hardware problems by examining the LEDs on all of the components and using thetables and illustrations in this chapter.If you detect any problems during inspection of the LEDs, contact your Authorized Service Provider.

Drive Cage LEDsThe DC4 drive chassis holds one DC4 drive cage housing two drive cage FC-AL modules and amaximum of ten drive magazines.

Figure 45 DC4 Drive Cage

64 Understanding HP P10000 3PAR Storage System LED Status

DC4 Drive Cage FC-AL Module LEDsThe DC4 drive cage FC-AL modules have the following LEDs:

Figure 46 FC-AL LED and Port Locations

Table 2 Drive Cage DC4 FC-AL Module LEDs

IndicatesAppearanceLED

A presence of a small form-factorpluggable optical transceiver (SFP) anda valid signal from the node.

Steady green lightRX

No connection to the node or no SFPis installed.

No light

A presence of an SFP and that the LEDis on and transmitting.

Steady green lightTX

No SFP is present or the SFP transmitterfailed.

No light

The drive cage is functioning properly,but is not communicating with anynodes.

Steady green lightFC-AL status

The drive cage is connected andcommunicating with the systemmanager of a node in the cluster.

Flashing green light (1 blink persecond)

Normal, initial indication for twoseconds upon power up. Otherwise,

Steady amber light

Drive Cage LEDs 65

Table 2 Drive Cage DC4 FC-AL Module LEDs (continued)


FC-AL module error or other cage error.If both FC-AL modules have a steadylight, the temperature of a disk drive inthe drive-cage has exceeded itshigh-level threshold, or a power supplyhas failed.

The drive cage has some type of error,such as a failed or missing power

Flashing amber light (1 blink persecond)

supply, but is communicating with anode.

A cage firmware upgrade initiated bythe upgradecage CLI command is

Rapid toggle between amber andgreen light

in progress. A firmware upgradenormally takes less than two minutes tocomplete.

The FC-AL module is prepared for hotplug replacement.

Steady amber lightHot plug

The FC-AL module is not prepared forhot plug.

No light

The transfer rate is operating at 4GB/s.Steady green light4GB/s

The transfer rate is not operating at4GB/s.

No light


Drive Magazine LEDs

NOTE: After powering on, allow approximately two minutes for the disks on the drive magazineto spin up before checking the drive magazine LEDs.

Drive magazines have the following LEDs:

Figure 47 Drive Magazine LEDs

Table 3 Drive Magazine LEDs


The drive magazine is functioningproperly.

Steady green lightDrive magazine status

A drive magazine error, or one or moredrives are bypassed on at least onepath.

Steady amber light

The disk is not spun up but has power.Quick flashing, or 20 percent on, 80percent off green light

Disk status

The disk is spun up and waiting for acommand.

Steady green light

The disk is executing commands.Flashing green light

No disk is present.No light

A disk error, or the disk is bypassed onboth paths (loops).

Steady amber light

The drive magazine is prepared for hotplug replacement.

Steady amber lightHot plug

That there is a connection failurebetween the drive magazine and thedrive chassis.

Flashing amber light

The drive magazine is not prepared forhot plug.

No light

Drive Cage LEDs 67

Controller Node LEDsDepending on configuration, storage systems contain between two and eight controller nodes, alllocated in the chassis. Controller nodes have the following LEDs:

NOTE: You can issue the locatenode command to flash all service LEDs associated to acontroller node blue. This includes the power supplies, battery modules, and fan module LEDs.

Table 4 Controller Node LEDs


Normal operation.No lightNode Disk

Steady blueNode Service • In combination with the status LEDblinking green three times persecond, indicates the controller nodeis prepared for removal.

• In combination with the status LEDbeing solid, indicates a fatal nodefailure.

• In combination with the node statusLED blinking green or amber onetime per second, indicates theservicenode start commandwas issued to illuminate the nodeservice LEDs.

Normal operation.No light

The locatenode command was issuedto locate the node or the FRU is not fullyseated.

Flashing blue light

A quick flashing light means the nodeis booting. A slow flashing light meansthe node is part of the cluster.

Flashing green lightNode Status

The node is booting but has not joinedthe cluster.

Steady green light


Table 4 Controller Node LEDs (continued)


The node is booting, or, in combinationwith a blue service LED, the node is safeto remove.

Rapidly flashing green light (threetimes per second)

The node has joined the cluster butthere is a degraded component

Flashing amber light

associated with the node. A slowflashing light means the node is part ofthe cluster.

An error within the node.Steady amber light

The servicenode start commandwas issued to illuminate the service LED

BlueHBA Service

or the HBA has failed and needs to bereplaced. If the LED is off, the HBA isnormal.

Controller Node Status Panel LEDsThe controller node LED status panel is located at the front of the system. The V400 includes fourLEDs and the V800 has eight LEDs. Each LED on the node-chassis panel should be identical to theindividual controller node status LED, as shown in the Node Status LED section of the ControllerNode LEDs table.

Figure 48 LED Status Panel on a V400

Controller Node LEDs 69

Fan Module LEDsThe V400 controller node chassis can hold up to eight fan modules that each hold two fans, andthe V800 can hold up to 16. Fan modules have the following LEDs:

Table 5 Fan Module LEDs


Normal operation, no faults.GreenStatus

Fan speed is too low, failed, off or notworking properly. With a blue service

Amber

LED, the fan module failed and was notable to recover in 60 seconds. Replacethe fan module.

The servicenode start fan hasbeen issued. With the amber status LED,

Solid BlueService

the fan module is failed and needsservicing.

The locatenode fan command hasbeen issued.

Blue Blinking

Node fan module no longer needsservicing.

Off


Fibre Channel Adapter Port LEDsThe Fibre Channel adapter in the controller node also contains Fibre Channel port LEDs:

Figure 49 Fibre Channel LEDs

Table 6 Fibre Channel Adapter LEDs


Wake up failure (dead device) orpower is not applied.

No lightPort 1-4

Not connected.Amber light off(Port speed)

Connected at 4GB/sec.Amber (3 fast blinks)

Connected at 8GB/sec.Amber (4 fast blinks)

Normal/Connected - link up.Steady green light(Link status)

Link down or not connected.Flashing green light

Fibre Channel Adapter Port LEDs 71

CNA Port LEDsThe Converged Network Adapter (CNA) includes two ports with corresponding LEDs:

Figure 50 CNA Port LEDs

Table 7 CNA Port LEDs


Link downNo lightLink

Link upSteady green light

No activity.No lightACT (Activity)

ActivityFlashing green light


Ethernet LEDsThe controller node has two built-in Ethernet ports and each port contains two LEDs:

Figure 51 Ethernet LEDs

Table 8 Ethernet LEDs


Valid link partnerSteady green lightACT/LNK (top E0, E1)

Data activityFlashing green light

ACT/LNK is offNo light

1000Mb/sec modeSteady yellow lightSpeed (bottom E0, E1)

100Mb/sec modeSteady green light

10Mb/sec modeNo light

Ethernet LEDs 73

Power Supply LEDsPower supplies are located at the rear of the storage system. The drive chassis and controller nodepower supplies have the following LEDs:

Drive Chassis Power Supply LEDsDrive chassis power supplies are located at the rear of the drive chassis.

Figure 52 Drive Chassis Power Supply LEDs

Table 9 Drive Chassis Power Supply LEDs


Power is on.Steady green lightPower Supply Status

Power supply error.Steady amber light

Broken connection.No light

AC is entering from an external source.Steady green lightAC

Power supply output is off.No light


Controller Node Power Supply LEDsThe controller node power supplies are located behind the cable management tray in the nodechassis.

Figure 53 Controller Node Power Supply LEDs

The power supply service LED is located on the dividers between the power supplies.

Figure 54 Controller Node Power Supply Service LED

Table 10 Controller Node Power Supply LEDs


Power is on.Steady green lightPower Status

Power supply error.Steady amber light

Broken connection.No light

AC is entering from an external source.Steady green lightAC Status

Power supply output is off.No light

Failed power supply.Steady amber lightFault

The servicenode start orlocatenode command was issued to

BlueService

illuminate the service LED or the powersupply has failed and needs to bereplaced.

Power Supply LEDs 75

Battery Module LEDsDepending on configuration, storage systems include one or two battery compartments that holdup to four battery modules each. Each node has one battery module. Each battery module hasthree LEDs:

Figure 55 Battery Module LEDs

Table 11 Battery Module LEDs


Battery modules is being charged.GreenCharging

Battery module is at fault.Amber

Battery module is not in node orconnected.

Off

Battery module output is on andsupplying power to the node.

GreenDischarging

Battery module is not providing powerto the node.

Off

Battery module needs servicing or theservicenode start orlocatenode command was issued.

BlueService LED

Battery module no longer needsservicing.

Off


Power Distribution Unit LampsEach storage system includes four PDUs that contain two power bank lamps:

Figure 56 PDU Lamps

Table 12 PDU Lamps


Power is being supplied to a powerbank and the circuit breaker is turnedON.

Steady green lightLamp

Power bank is not receiving AC inputor the circuit breaker is turned OFF.

Off

Power Distribution Unit Lamps 77

Service Processor LEDsThe LEDs are located at the top of the SP:

Figure 57 Service Processor LEDs

Table 13 SP LEDs


Service processor is off.No lightPower

Service processor is on.Steady green light

No hard drive activity.No lightHard disk drive

Hard drive activity.Flashing amber light

Port is not connected.No lightNIC Port 1/2

Port is connected.Steady green light

Network activity.Flashing green light

Service processor temperature isnormal.

No lightOverheat

Service processor temperature isoverheating.

Steady red light

Service processor has a failed fan.Flashing red light


6 Powering Off the Storage System

CAUTION: When powering off the storage system, observe the precautions as described in“Precautions” (page 87). Never power off or remove a controller node without confirming that theservice LED is solid blue.

Powering Off the Storage SystemTo power off the storage system:1. Connect the maintenance PC to the SP using the serial connection and start an spmaint

session.2. In the 3PAR Service Processor Menu, select option 4, InServ Product Maintenance.3. Select option 6, Halt an InServ cluster/node, then select the desired system.4. Confirm all prompts to halt the system.5. Press x to return to the 3PAR Service Processor Menu.6. Allow 2-3 minutes for the storage system to halt, then verify that the node status LEDs are

flashing green and the service LEDs are solid blue, which indicate the nodes have halted.7. Select option 1, SP Control/Status.8. Select option 3, Halt SP.9. When prompted, press y to confirm halting the SP.10. Wait approximately 30 seconds and verify if the LED on the front of the SP is no longer

illuminated.11. Turn off all eight PDU circuit breakers (two per PDU) to remove AC power.12. Close and lock the rear door of the system.

Powering Off the Storage System 79

7 Connecting the Maintenance PCConnecting to a Controller Node

The maintenance PC connects directly to a controller node using a serial cable.To connect the maintenance PC to a node:1. Insert a standard Category 5 Ethernet cable into the maintenance port (S0) of one of the

controller nodes (“Location of the Maintenance Port ” (page 80)).

Figure 58 Location of the Maintenance Port

NOTE: A cable with adapter (P/N 180-0055) should be connected to the SP. Disconnectthe Ethernet cable from the RJ-45 to DB-9 adapter attached to the SP (P/N 180-0059).

2. Attach the RJ 45 adapter assembly (P/N 180-055) to the PC serial port or USB to serialadapter (Triplite USA-19HS is recommended).

Figure 59 Connecting the Ethernet Cable

3. Power on the maintenance PC.4. After you are connected, use a terminal emulator to communicate with the SP and perform

various tasks to support the storage system. See Serial Settings.

Connecting to the Service ProcessorThe maintenance PC can connect to the SP either through a serial connection or an Ethernetconnection (LAN).

80 Connecting the Maintenance PC

Once you are connected to the SP using an serial or Ethernet connection, there are two SP userinterfaces, SPOCC and SPMAINT, that you can use to perform various administrative and diagnostictasks to support of both the system and the SP.Refer to “Connecting to the CLI” (page 82) to start an SPMAINT session or “Logging into SPOCC”(page 85).

NOTE: Connecting to the SP through the LAN (Ethernet) requires establishing a Secure ShellSession (SSH). Refer to “Using PuTTY” (page 84).If you do not have SSH, connect to the serial port of the SP. Refer to “Serial Settings” (page 81)

Using a Serial ConnectionTo use a serial connection:1. Locate the SP. Attach the DB9 female serial adapter (P/N 180–0055) that is at the free end

of the blue Ethernet cable to the Serial port on your maintenance PC. A standard Category 5Ethernet cable with the appropriate RJ-45 to DB9 adapters at each end should already beconnected to the SP's DB9 Serial port (Figure 60 (page 81)).

2. If necessary, insert a standard Category 5 Ethernet cable into the SP serial port with the DB9female serial to RJ45 adapter (P/N 180–0055).

NOTE: See “Serial Cable Pinouts” (page 85) for serial cable pinout diagrams.

Figure 60 Supermicro Service Processor Serial Port and Adapter

3. Power on the maintenance PC.4. After you are connected, use a terminal emulator, such as HyperTerminal, Attachmate Reflection

X, SecureCRT, or TeemTalk to communicate with the SP and perform various tasks to supportthe storage system. See Serial Settings.

Serial SettingsTo connect to the SP using a terminal emulator, such as HyperTerminal, Attachmate Reflection X,SecureCRT, or TeemTalk:1. Establish a serial connection to the SP. Refer to “Using a Serial Connection” (page 81).2. Open HyperTerminal, Attachmate Reflection X, SecureCRT, or TeemTalk. For this example,

Reflection X is used:3. On the menu bar, select Connection and select from the Connection Setup drop-down list.4. In the Connection Setup window, select the Serial Port radio button:

a. In the Communications Port field, select the port being used by the USB adapter (COMx).b. Select 38400 (for SP, for node 57600) for the Baud Rate.

5. Keep the default serial settings on the remaining fields:• Parity - None

• Word Length - 8

Connecting to the Service Processor 81

• Stop Bits - 1

• Flow Control - Both6. Click the More settings button to open the More Settings Window, confirm the following

settings:• Transmit: Xon/Xoff

• Receive: Xon/Xoff

• Char transmit delay: 0

• Line transmit delay: 07. Click OK.8. Enter your user name and password. Proceed to connect to the CLI. If you want to log your

session, see Enabling Session Logging.

Enabling Session LoggingTo enable session logging:1. On the menu bar, select File and select from the Logging.2. In the Logging window, select only the Disk checkbox.3. Click the Browse button or enter the path where the log is to be saved, then click OK.

Connecting to the CLI1. Connect to the SP using a terminal emulator. Refer to “Serial Settings” (page 81).2. The 3PAR Service Processor Menu appears. Select option 7, Interactive CLI for an InServ, then

select the desired system.3. Proceed to the drive and node chassis maintenance procedures in this document.

Using an Ethernet ConnectionYou can connect the maintenance to the SP using an Ethernet cable. When you use an Ethernetconnection, you have to configure LAN settings on the maintenance PC (refer to “Configuring theLAN Settings on the Maintenance PC” (page 83)) and establish a Secure Shell Session (SSH) usingPuTTY. Refer to “Using PuTTY” (page 84).To connect using an Ethernet connection:1. Your system should already have a crossover Category 5 Ethernet cable inserted into the

appropriate Ethernet port. If necessary, insert a crossover Category 5 Ethernet cable (RJ45 toRJ45) into the Int (private) Ethernet port. Use port ETH1 at the rear of the SP (Figure 61(page 82)).

Figure 61 Supermicro Service Processor Ethernet Ports

2. Connect the free end of the crossover Ethernet cable to the Ethernet port in the maintenancePC.

3. Power on the maintenance PC.


4. Configure the LAN settings on the maintenance PC. See “Configuring the LAN Settings on theMaintenance PC” (page 83).

Configuring the LAN Settings on the Maintenance PC1. Go to Control Panel > Network and Internet > Network Connections.2. Right-click the Local Area Connection icon to open the menu and click Properties.3. The Local Area Connection Properties dialog box appears (Figure 62 (page 83)). On the

Networking tab, double-click Internet Protocol (TCP/IP).

Figure 62 Local Area Connection Properties Dialog Box

4. The Internet Protocol (TCP/IP) Properties dialog box appears (Figure 63 (page 84)). Selectthe Use the following IP address button and then type the following IP addresses, then clickOK.• IP address - 10.255.155.49

• Subnet mask - 255.255.255.248

• Default gateway - None

Connecting to the Service Processor 83

Figure 63 Internet Protocol (TCP/IP) Properties Dialog Box

5. Click OK in the Advanced TCP/IP Settings dialog box to finish configuring the LAN connection.6. Establish a SSH using PuTTY. Refer to “Using PuTTY” (page 84).

Using PuTTYAfter you have configured LAN settings and established an Ethernet connection, use PuTTY toinitiate a secure shell session between the maintenance PC and the SP.To use PuTTY:1. Double-click the putty.exe file in its permanent location on your PC.2. In the PuTTY Configuration dialog box, type the SP IP address in the Host Name (or IP address)

field, select the SSH radio button, then click Open (Figure 64 (page 84)).

Figure 64 PuTTY Configuration Dialog Box

3. If you are connecting to the SP for the first time, the PuTTY Security Alert dialog box appears.Click Yes.


4. In the PuTTY main window, type your user ID and press enter, then type your password andpress enter.

Logging into SPOCCAfter the Ethernet connection is configured, log in to the SPOCC interface from the maintenancePC using a supported Web browser. For additional details on SPOCC, refer to Section (page 90).To log into SPOCC using a Web browser:1. Type IP address of the SP in the Web browser and press Enter.

NOTE: If you are using the crossover cable to the SP’s ETH1 (Int) port, use IP address:10.255.155.54.

2. On the Service Processor Login screen, click the Login button.3. In the Enter Network Password dialog box, type your user name and password, then click

OK.

NOTE: If you do not have a user ID and password, contact your Authorized Service Provider.

Serial Cable PinoutsThe following tables and diagrams illustrate the serial cable pinouts for the crossover DB9 femaleserial to RJ45 adapter assembly (P/N 180–0055) and the straight-through DB9 to RJ45 serialadapter (P/N 180–0059).

Crossover Adapter AssemblyThe following table lists cable pinouts for the crossover DB9 female serial to RJ45 adapter assembly(P/N 180–0055). This connector inserts into the COM port on the maintenance PC.

Table 14 Crossover DB9 Female Serial to RJ45 Serial Connector Pinouts

RJ45 PinDB9 (Female) PinColor

32Black

23Orange

55Green

Figure 65 (page 85) illustrates the pin locations and connections for the crossover DB9 femaleserial to RJ45 adapter assembly (P/N 180–0055).

Figure 65 Crossover DB9 Female Serial to RJ45 Serial Connector Pinouts

Serial Cable Pinouts 85

Straight-Through AdapterThe following table lists connector pinouts for the straight-through DB9 to RJ45 adapter (P/N180–0059). This connector inserts into the COM port on the SP.

Table 15 Straight-Through DB9 to RJ45 Adapter Serial Cable Pinouts

RJ45 PinDB9 (Female) PinColor

22Orange

33Black

55Green

Figure 66 (page 86) illustrates the pin locations and connections for the straight-through DB9 toRJ45 adapter (P/N 180–0059).

Figure 66 Straight-Through DB9 to RJ45 Serial Connector Pinouts


A PrecautionsGeneral Precautions

Follow these general precautions when servicing the storage system to avoid injury, data loss anddamage:

CAUTION: Field Replaceable Units (FRUs) should be within 10° C (18° F) of the temperature ofthe computer room before power is applied to them in a storage system. This is especially true fordisk drives. The maximum rate of change (gradient) in temperature for the FRU should be 10° C(18° F) per hour. See Table 16 (page 87) for additional environmental specifications.

Table 16 Environmental Specifications

ValueSpecification

0 –10,000 ft (3,048 m) 0 –40,000 ft (12,192 m)Altitude Operating Non-operating

50 –104° F (10–40° C) 0–3,000 ft (914.4 m) 50 –95° F(10 –35° C) 3,000–10,000 ft (914–3,048 m) –40 –203°F (–40– 95° C) 0–40,000 ft (0–12,192 m)

Ambient temperature Operating Non-operating

18° F/hr. (10° C/hr.) 18° F/hr. (10° C/hr.)Temperature gradient Operating Non-operating

20 – 80 percent noncondensing, maximum gradient 10percent per hour

Relative humidity

CAUTION: Using improper tools can result in damage to the storage system. See the tools list in“Tools” (page 89).

• Prepare an Electrostatic Discharge-safe (ESD) work surface by placing an antistatic mat onthe floor, or table, near the storage system. Attach the ground lead of the mat to an unpaintedsurface of the rack.

• Always use a wrist-grounding strap. A wrist-grounding strap is provided with the storagesystem. Attach the grounding strap clip directly to an unpainted surface of the rack.

• Avoid contact between electronic components and clothing, which can carry an electrostaticcharge.

• If applicable, ensure all cables are properly labeled and easily identifiable prior to removinga component.

Disk and Drive Magazine PrecautionsYou should always observe caution when handling drive magazines. When carrying a drivemagazine, always support it with both hands. With the solid back panel of the magazine facingyou and with one hand on the handle, support the bottom of the magazine with your other hand.

CAUTION: If you require more than 30 minutes to replace a disk on a drive magazine, install adrive magazine filler panel over the empty drive magazine slot to prevent overheating while youare working.

CAUTION: To avoid damage to hardware and the loss of data, never remove a drive magazinefrom the storage system without confirming that the hot-plug LED on the drive magazine is lit.

CAUTION: To avoid potential damage to equipment and loss of data, handle disks and drivemagazines carefully.

General Precautions 87

Controller Node PrecautionSlide the node part way out of the chassis and hold the node by the bottom and top to removeand carry.

CAUTION: To avoid potential damage to equipment and loss of data, handle controller nodescarefully.

Clock Battery PrecautionWhen replacing a controller node clock battery, observe the following precaution:

WARNING! The lithium coin battery may explode if it is incorrectly installed in the controllernode . Replace the coin battery only with a recommended equivalent type.

WARNING! Dispose of used batteries according to the manufacturer’s instructions.

Drive Chassis and Node Power Supply PrecautionWhen handling a power supply, observe the following precaution:

CAUTION: To prevent overheating, this procedure requires a maximum service time of 10 minutes.

Battery Module PrecautionsWhen handling a battery module observe the following precautions:

WARNING! Do not attempt to disassemble the battery module.

WARNING! Battery modules are heavy. Use care when replacing them.

CAUTION: Verify the storage system cabinet is completely immobilized before removing batterymodules. For storage systems with HP 3PAR cabinets, confirm that the leveling feet at the bottomof the cabinet rest firmly on the ground before removing a battery module.

One battery module is connected to each controller node and supplies enough power for the nodeto write unwritten data-cache to the node's internal disk during a loss of AC power. Following anAC loss or the replacement of a battery module, the level of the battery module's charge cannotbe fully determined so the system limits and continuously adjusts the amount of available write-cache.The battery module is considered fully charged and write-cache is 100% available after 24 hours.

Power Distribution Unit PrecautionsWhen handling a Power Distribution Unit (PDU), observe the following precautions:

WARNING! Do not operate a storage system if any of the main power cords show evidence ofdamage or wear. Immediately replace all PDUs that have a damaged or worn power cord.

WARNING! To avoid possible injury, damage to storage system equipment, and potential lossof data, do not use the surplus power outlets in the storage system PDUs. Never use outlets in thePDUs to power components that do not belong to the storage system or to power storage systemcomponents that reside in other cabinets.

AC Cord PrecautionWhen handling an AC cord, observe the following precaution:

WARNING! To avoid serious injury, never touch a damaged power cord before switching offthe PDU and power supply connected to the damaged cord.

88 Precautions

B ToolsTools Required to Perform Maintenance

The following tools may be required to perform the maintenance procedures on a storage systemas described in this manual:• Electrostatic discharge (ESD) wrist-grounding strap (provided with cabinet)• Electrostatic discharge (ESD) mat• #1 Phillips screwdriver• #2 Phillips screwdriver• 1/8 -in. (3 mm) slotted screwdriver• 3/16 -in. (5 mm) slotted screwdriver• Diagonal cutting pliers• Adjustable wrench

Tools Required to Perform Maintenance 89

C Guided MaintenanceOverview

Guided maintenance scripts are provided with the service processor to help facilitate the removaland replacement of Field Replaceable Units (FRUs). The maintenance scripts execute all CLIcommands and, in some cases, select the appropriate failed component to minimize user errorwhen performing maintenance procedures. Guided maintenance is currently available for thefollowing FRUs:• Controller node FRUs:

Controller node◦◦ Internal node disk◦ Battery module◦ Control cache and data cache DIMMs◦ PCI adapter cards◦ Controller node power supply◦ SFP◦ Fan modules

• Drive cage FRUs:Drive magazine◦

◦ Power supply◦ FC-AL module◦ SFP◦ Drive

• Power system FRUs:AC power cord◦

◦ Power distribution unit

Accessing Guided MaintenanceTo access the guided maintenance scripts:1. Log in to SPOCC. See “Logging into SPOCC” (page 85) for further instructions.2. Click Support to access the guided maintenance procedures (Figure 67 (page 91)).

90 Guided Maintenance

Figure 67 SPOCC Home Page

3. On the Service Processor - Support page, under the Action column, click Guided Maintenanceto perform maintenance (Figure 68 (page 91)).

Figure 68 SPOCC Support Page

A new browser window is launched; select a specific maintenance procedure.

Accessing Guided Maintenance 91

4. In the Guided Maintenance window, select the guided maintenance procedure to start areplacement activity (Figure 69 (page 92)).

Figure 69 Guided Maintenance Window

92 Guided Maintenance

D Performing Node RescueThis appendix provides instructions on performing both auto-node and manual node rescue. Alwaysperform the auto-node rescue procedure unless otherwise instructed.

Performing Auto-Node RescueTo perform auto-node rescue:1. Uncoil the red crossover Ethernet cable connected to the private network connection. Using

the red crossover cable, connect ETH1 of the SP to the Ethernet port (E0) port of the node thatis being rescued. This may require you to remove an existing customer network cable whichcan be reinstalled after the node rescue is completed.

Figure 70 Connecting the SP-to-Node Cable

2. Connect the maintenance PC to the SP using the serial connection and start an spmaint session.3. In the 3PAR Service Processor Menu, select option 4, InServ Product Maintenance.4. Select option 11, Node Rescue.5. Select option 1, Configure Node Rescue, then select the desired system.6. Select option 3, Automatic Node Rescue.7. Enter the desired node number.8. Turn the node power switch to the ON position.9. Select y to confirm the correct node number. When communication from the SP to the node

is established, output similar to the following appears:

root@1200163-0 Tue Apr 01 16:53:19:~# beginning rescue function....255.248 -s 10.255.155.54155.53 -m 255.255 Informing system manager to not autoreset node1Resetting node 1Attempting to contact node 1 via internal serial portWaiting for node to respond (10 seconds elapsed)...Waiting for node to respond (20 seconds elapsed)...Waiting for node to respond (30 seconds elapsed)...=Successfully started inter-node serial link communicationStarting Whack, setting values, and loading image:Interacting with CBIOS on the node......Booting from net...TFTP "install" from 10.255.155.54................................completemknbi-1.2-7/first32.c (GPL)

Performing Auto-Node Rescue 93

Top of ramdisk is 0X1FFFF000Ramdisk at 0X00800000, size 0X00500000...Kernel on remote node has been started.Waiting for node to join cluster. This usually takes around 10 minutes, but maytake 20 minutes or longer.Install kernel is running - please wait...Waiting for node to join cluster (0 minutes and 15 seconds elapsed)=Waiting for node to join cluster (0 minutes and 30 seconds elapsed)..Waiting for node to join cluster (13 minutes and 15 seconds elapsed)=Node 1 has joined the cluster; node rescue successful...Please wait...Starting SP tasks.....

NOTE: This process takes approximately 15 minutes. When complete, the node rebootsand becomes part of the cluster. If this takes longer than twenty minutes, problems may existand the node rescue process needs to be corrected.

10. After the node has booted, verify that the node status LED is blinking green in unison with theother node LEDs, indicating that the node has joined the cluster, then press ENTER to continue.

11. Select 1, Deconfigure <name of cluster> Node Rescue.12. Select x Return to previous menu until you return to the main menu.13. Select option 7, Interactive CLI for an InServ, then select the desired system.14. Issue the shownode command to verify that all nodes have joined the cluster.

cli% shownode Control Data CacheNode --Name--- -State- Master InCluster ---LED--- Mem(MB) Mem(MB) Available(%) 2 1201553-2 OK No Yes GreenBlnk 4096 12288 100 3 1201553-3 OK Yes Yes GreenBlnk 4096 12288 100


Menu and to log out of the session.17. Disconnect the serial cable from the maintenance PC and the red cross-over Ethernet cable

from the node and coil and replace the cables behind the SP. If applicable, reconnect thecustomer's network cable and any other cables that may have been disconnected.

18. Close and lock the rear door.

94 Performing Node Rescue

Performing Manual Node RescueTo perform manual node rescue:1. At the rear of the storage system, uncoil the red crossover Ethernet cable connected to the

SP’s (ETH1) private network connection. Connect this cross-over cable to the E0 port of thenode that is being rescued. This may require you to remove an existing customer networkcable which can be reinstalled after the node rescue is completed.

2. Connect the maintenance PC to the SP using the serial connection and start an spmaint session.3. In the 3PAR Service Processor Menu, select option 4, InServ Product Maintenance.

NOTE: Manual node rescue builds the node disk so it contains the proper software for thecluster.

4. Select option 11, Node Rescue.5. Select option 1, Configure Node Rescue, then select the desired system.6. Select option 2, Manual Node Rescue.

A screen appears displaying the steps to perform a manual node rescue:

This is the procedure for manually rescuing node(s) in InServ <name>

1. Connect the node to be rescued to the SP's private network (Eth-1).NOTE: This requires a hub or crossover cable.2. Connect a laptop to the serial interface on the node to be rescued.NOTE: 57600 baud,8,None,1,XON/XOFF3. Power-on, or power cycle, the node to be rescued.4. After the node Status LED starts rapidly blinking green, press CTRL-w on the laptop to get into the node's BIOS (Whack) environment.5. Type: boot rescue <enter>6. When the node asks for confirmation to erase the disk type: y

The system will install the base OS, InForm OS, and reboot the node so it can join the cluster. This process normally takes 10-20 minutes.

7. Disconnect the blue Ethernet (serial) cable from the adapter on the SP.8. Connect the cable to the serial port (S0) on the node being rescued.

Performing Manual Node Rescue 95

9. Change the baud rate of the laptop connection to 57600.10. Set the node power switch to the ON position to turn on power on the node.


11. After the node status LED starts rapidly blinking green (approximately 40 seconds), pressCTRL+W.a. Type boot rescue and press enter.b. The node will continue to run POST then it will stop and display instructions for running

node-rescue (see output on the following page). Select y to continue.The node will continue to run POST then it will stop and display instructions for runningnode-rescue (see output on the following page). Select y to continue.The system installs the base OS and InForm OS.

NOTE: This process takes approximately 10 to 15 minutes (rescue and rebuild of disk = 5minutes) + (reboot = 5-10 minutes). When complete, the node restarts and becomes part ofthe cluster.

Whack>boot rescueThis is the procedure for manually rescuing a 3PAR InServ node (i.e.,rebuilding the software on the node's internal disk). The system will installthe base OS, BIOS, and InForm OS for the node before it joins the cluster.

You must first connect a Category 5 crossover Ethernet cable between the SP'sprivate/internal network (ETH-1) and the "E0" Ethernet port of the node to berescued. Note that the diagram below does not represent the physical portnumbers or configuration of all node types.

New Node Service Processor +------------+ +-----------------+ ||||||| | | | ||||||| | |ETH-0 ETH-1(Int) | ||||||| E0 C0| +-----------------+ +------------+ ^ ^ ^ |____Crossover ETH____| |__Maintenance PC (serial connection)

This procedure will execute the following Whack commands: 1. net addr 10.255.155.53 2. net netmask 255.255.255.248 3. net server 10.255.155.54 4. boot net install ipaddr=10.255.155.53 nm=255.255.255.248 rp=10.255.155.54::rescueide

This operation will completely erase and reinstall the node's local disk.Are you sure? (Y/N) YesTFTP "install" from 10.255.155.54....

12. After 10 to 15 minutes, verify that the node status LED is slowly blinking green in unison withthe other node LEDs, which indicates the node has joined the cluster.

13. Disconnect the blue Ethernet cable (serial) from the node and reconnect to the adapter on theSP.

14. Change the baud rate of the maintenance PC to 38400.15. Log into spmaint. When you log in, you are prompted to confirm that node rescue is complete.16. Select option 1, Deconfigure Node Rescue.17. Select option X Return to previous menu until you return to the main menu.18. Select option 7, Interactive CLI for an InServ, then select the desired system.19. Issue the shownode command to verify that all nodes have joined the cluster.

cli% shownode Control Data CacheNode --Name--- -State- Master InCluster ---LED--- Mem(MB) Mem(MB) Available(%)

Performing Manual Node Rescue 97

0 1000163-0 OK No Yes GreenBlnk 4096 6144 100 1 1000163-1 OK Yes Yes GreenBlnk 4096 6144 100


Menu and to log out of the session.22. Disconnect the serial cable from the maintenance PC and the red cross-over Ethernet cable

from the node and coil and replace the cable behind the SP. If applicable, reconnect thecustomer's network cable and any other cables that may have been disconnected.

23. Close and lock the rear door.


E Illustrated Parts CatalogThis appendix contains the illustrated parts catalog for all Field Replaceable Units (FRUs) andreplaceable hardware. Following each page of illustrated parts is a parts list containing materialnumbers, descriptions, and quantities.

Storage System Frame ComponentsFigure 71 Storage System Frame FRUs

Table 17 Storage System Frame FRUs

Qty.DescriptionMaterial NumberRef. Number

up to 8SPS- BATTERY MODULENODE

657885-0011

4SPS- PDU 1U V CLASS657886-0012

up to 16SPS- FAN MODULE NODE657911-0013

up to 8SPS- CORD PWR PDU toNODE 4.5FT

657893-001657894-001

Not shownup to 24

SPS- CORD PWR PDU toDC4 6FT

657895-001657896-001

11

SPS- CABLE POWER PDU30A 15FTSPS- CABLE POWER PDU30A 15FT-EU

Storage System Frame Components 99

Figure 72 Service Processor FRU

Table 18 Service Processor FRUs


1SPS- PROCESSOR 1USUPERMICRO II

641719-0011

1SPS- BD LED STATUS V800657897-001Not shown1SPS- BD LED STATUS V400657898-001

Figure 73 V400 Node Chassis

Table 19 Node Chassis


1SPS- CHASSIS NODE V400657901-0011

100 Illustrated Parts Catalog

Figure 74 Controller Node Power Supply

Table 20 Controller Node Power Supply


2 per nodeSPS- POWER SUPPLY NODESFP650

657887-0011

Internal Node ComponentsFigure 75 Internal Node Components

Internal Node Components 101

Table 21 Internal Node FRUs


1SPS- NODE V CLASS 2.83GHZ657902-0011

1SPS- SFP TRANSCEIVER 10GBIT LCCNA

657884-001657883-001

Not shown

SPS- SFP TRANSCEIVER 8GBIT LC

up to 9SPS-BD ADAPTER 10GBIT PCI E CNA2 PORT

657904-0012

up to 9SPS- BD ADAPTER 8GBIT FC 4 PORT657903-0013

1SPS- DRV HD 128GB SSDNODE C400657909-0014SPS- DRV HD 256GB SSD NODE C400657910-001

Figure 76 DIMMs

Table 22 DIMMs and TOD Battery for the Controller Node


8SPS- MEMORY RDIMM 4GBDATA CACHE DDR2

657899-001657908-001

A-H

SPS- MEMORY RDIMM 8GBDATA CACHE DDR2

1SPS- BATTERY TOD CLOCK642702-001M

4SPS- MEMORY FBDIMM4GB CNTRL CACHE DDR2

657900-001657907-001

I-L

SPS- MEMORY FBDIMM8GB CNTRL CACHE DDR2


Drive Chassis ComponentsFigure 77 Drive Chassis Component FRUs

Table 23 Drive Chassis FRUs

Qty Per ChassisDescriptionMaterial NumberRef. Number

up to 10SPS-MAGAZINE DRV 4GBNL SATA 520 BLACK

672608-0011

up to 10SPS- MAGAZINE DRV4GBIT FC DC4 BLACK

649998-0012

2SPS- MODULE FCAL 4GBITDC4 BLACK

649996-0013

up to 40SPS- DRV HD 300GB 15KRPM 520 FORMAT

657888-001657891-001

4,5

up to 40SPS- DRV HD 2TB SATA 7K520 FORMAT

657890-001677194-001

6,7

up to 40SPS- DRV HD 600GB 15KRPM 520 FORMAT

657892-0018, 9 (not used)

up to 8SPS- DRV HD 100GB SSD520 FORMAT DC4

657905-00110

up to 8SPS- DRV HD 200GB SSD520 FORMAT DC4

657906-00111

2SPS-SFP TRANSCEIVER4GBIT LC

640842-00112

Drive Chassis Components 103

Figure 78 Drive Chassis Power Supply

Table 24 Drive Chassis Power Supply

Qty per ChassisDescriptionMaterial NumberRef. Number

4SPS- POWER SUPPLY DRIVECHASSIS DC4

640843-0011

Miscellaneous ComponentsFigure 79 Storage System Cables


Table 25 Storage System Cables


Configuration DependentSPS- CABLE FIBRECHANNEL LC-LC OM3 6M

659061-001649991-001

1

SPS- CABLE FIBRECHANNEL LC-LCOM3 10M

649993-001649994-001

SPS- CABLE FIBRECHANNEL LC-LC OM3 50M649992-001

SPS- CABLE FIBRECHANNEL LC-LC OM3100MSPS- CABLE FIBRECHANNEL LC-LC OM3 25M

RJ45 to DB9 Adapter,crossover

F180–0055F180–0059

Not shown

RJ45 to DB9 Adapter,straight

F850–0033

Ethernet Cable, crossover,20FT

Miscellaneous Components 105

hp 3par p10000 storage system maintenance manual (mar 2012) [105p]

Documents

drive magazine

drive cage sfp module

drive cage fcal module

drive chassis power

hp products

hp p10000

hp shallnot

controller node fan