ibm n6k hardware and service guide

IBM System Storage

N6000 Series Hardware and ServiceGuide

GC53-1142-03

��

Note:Before using this information and the product it supports, be sure to read the general information in “Notices”on page 121.

The following paragraph does not apply to any country (or region) where such provisions are inconsistent with locallaw.

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states (or regions) donot allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not applyto you.

Order publications through your IBM representative or the IBM branch office serving your locality.

© Copyright International Business Machines Corporation 2008, 2009.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Safety notices

This section contains information about:v “Safety notices and labels”v “Laser safety” on page viiv “Rack safety” on page viiiv “Fire suppression systems ” on page xi

For information about environmental notices, see the IBM® EnvironmentalNotices and User Guide, Z125-5823.

Safety notices and labels

When using this product, observe the danger, caution, and attention noticescontained in this guide. The notices are accompanied by symbols thatrepresent the severity of the safety condition.

The following sections define each type of safety notice and provideexamples.

The following notices and statements are used in IBM documents. They arelisted below in order of increasing severity of potential hazards. Follow thelinks for more detailed descriptions and examples of the danger, caution, andattention notices in the sections that follow.v Note: These notices provide important tips, guidance, or advice.v “Attention notices” on page vii: These notices indicate potential damage to

programs, devices, or data.v “Caution notices” on page vi: These statements indicate situations that can

be potentially hazardous to you.v “Danger notices”: These statements indicate situations that can be

potentially lethal or extremely hazardous to you. Safety labels are alsoattached directly to products to warn of these situations.

v In addition to these notices, “Labels” on page vi may be attached to theproduct to warn of potential hazards.

Danger noticesA danger notice calls attention to a situation that is potentially lethal orextremely hazardous to people. A lightning bolt symbol accompanies a dangernotice to represent a dangerous electrical condition. A sample danger noticefollows.

© Copyright IBM Corp. 2008, 2009 iii

DANGER

An electrical outlet that is not correctly wired could placehazardous voltage on metal parts of the system or the devicesthat attach to the system. It is the responsibility of thecustomer to ensure that the outlet is correctly wired andgrounded to prevent an electrical shock. (D004)

A general danger notice provides instructions on how to avoid shock hazardswhen servicing equipment. Unless instructed otherwise, follow the proceduresin the following danger notice.

iv IBM System Storage: N6000 Series Hardware and Service Guide

DANGER

When working on or around the system, observe the followingprecautions:

Electrical voltage and current from power, telephone, andcommunication cables are hazardous. To avoid a shock hazard:

v Connect power to this unit only with the IBM providedpower cord. Do not use the IBM provided power cord forany other product.

v Do not open or service any power supply assembly.

v Do not connect or disconnect any cables or performinstallation, maintenance, or reconfiguration of this productduring an electrical storm.

v The product might be equipped with multiple power cords.To remove all hazardous voltages, disconnect all powercords.

v Connect all power cords to a properly wired and groundedelectrical outlet. Ensure outlet supplies proper voltage andphase rotation according to the system rating plate.

v Connect any equipment that will be attached to this productto properly wired outlets.

v When possible, use one hand only to connect or disconnectsignal cables.

v Never turn on any equipment when there is evidence of fire,water, or structural damage.

v Disconnect the attached power cords, telecommunicationssystems, networks, and modems before you open the devicecovers, unless instructed otherwise in the installation andconfiguration procedures.

v Connect and disconnect cables as described below wheninstalling, moving, or opening covers on this product orattached devices.

To Disconnect:

1. Turn off everything (unless instructed otherwise).

2. Remove power cords from the outlet.

3. Remove signal cables from connectors.

4. Remove all cables from devices.

To Connect:

1. Turn off everything (unless instructed otherwise).

2. Attach all cables to devices.

3. Attach signal cables to the connectors.

4. Attach power cords to the outlets.

5. Turn on the devices.

(D005)Safety notices v

LabelsAs an added precaution, safety labels are often installed directly on productsor product components to warn of potential hazards.

The actual product safety labels may differ from these sample safety labels:

(L001)

DANGER

Hazardous voltage, current, or energy levels arepresent inside any component that has this labelattached. Do not open any cover or barrier thatcontains this label.

(L003)

DANGER

Multiple power cords. The product might be equippedwith multiple power cords. To remove all hazardousvoltages, disconnect all power cords.

Caution noticesA caution notice calls attention to a situation that is potentially hazardous topeople because of some existing condition. A caution notice can beaccompanied by different symbols, as in the examples below:

If the symbol is... It means....

A hazardous electrical condition with less severity thanelectrical danger.

A generally hazardous condition not represented byother safety symbols.

A hazardous condition due to the use of a laser in theproduct. Laser symbols are always accompanied by theclassification of the laser as defined by the U. S.Department of Health and Human Services (forexample, Class I, Class II, and so forth).

vi IBM System Storage: N6000 Series Hardware and Service Guide

Attention noticesAn attention notice indicates the possibility of damage to a program, device,or system, or to data. An exclamation point symbol may accompany anattention notice, but is not required. A sample attention notice follows:

Attention: Do not bend a fiber cable to a radius less than 5 cm (2in.); you can damage the cable. Tie wraps are not recommended foroptical cables because they can be easily overtightened, causingdamage to the cable.

Laser safety

CAUTION:This product contains a Class 1M laser. Do not view directly withoptical instruments. (C028)

This equipment contains Class 1 laser products, and complies with FDAradiation Performance Standards, 21 CFR Subchapter J and the internationallaser safety standard IEC 825-2.

CAUTION:Data processing environments can contain equipment transmitting onsystem links with laser modules that operate at greater than Class 1power levels. For this reason, never look into the end of an opticalfiber cable or open receptacle. (C027)

Attention: In the United States, use only SFP or GBIC optical transceiversthat comply with the FDA radiation performance standards, 21 CFRSubchapter J. Internationally, use only SFP or GBIC optical transceivers thatcomply with IEC standard 825–1. Optical products that do not comply withthese standards may produce light that is hazardous to the eyes.

Usage restrictionsThe optical ports of the modules must be terminated with an opticalconnector or with a dust plug.

Safety notices vii

Rack safety

Rack installation

DANGER

Observe the following precautions when working on oraround your IT rack system:

v Heavy equipment - personal injury or equipment damagemight result if mishandled.

v Always lower the leveling pads on the rack cabinet.

v Always install stabilizer brackets on the rack cabinet.

v To avoid hazardous conditions due to uneven mechanicalloading, always install the heaviest devices in the bottom ofthe rack cabinet. Always install servers and optional devicesstarting from the bottom of the rack cabinet.

v Rack-mounted devices are not to be used as shelves or workspaces. Do not place objects on top of rack-mounteddevices.

v Each rack cabinet might have more than one power cord. Besure to disconnect all power cords in the rack cabinet whendirected to disconnect power during servicing.

v Connect all devices installed in a rack cabinet to powerdevices installed in the same rack cabinet. Do not plug apower cord from a device installed in one rack cabinet intoa power device installed in a different rack cabinet.

v An electrical outlet that is not correctly wired could placehazardous voltage on the metal parts of the system or thedevices that attach to the system. It is the responsibility ofthe customer to ensure that the outlet is correctly wired andgrounded to prevent an electrical shock.

(R001 part 1 of 2

viii IBM System Storage: N6000 Series Hardware and Service Guide

CAUTION:

v Do not install a unit in a rack where the internal rack ambienttemperatures will exceed the manufacturer’s recommended ambienttemperature for all your rack-mounted devices.

v Do not install a unit in a rack where the air flow is compromised. Ensurethat air flow is not blocked or reduced on any side, front, or back of aunit used for air flow through the unit.

v Consideration should be given to the connection of the equipment to thesupply circuit so that overloading of the circuits does not compromise thesupply wiring or overcurrent protection. To provide the correct powerconnection to a rack, refer to the rating labels located on the equipmentin the rack to determine the total power requirement of the supplycircuit.

v (For sliding drawers.) Do not pull out or install any drawer or feature if therack stabilizer brackets are not attached to the rack. Do not pull out morethan one drawer at a time. The rack might become unstable if you pullout more than one drawer at a time.

v (For fixed drawers) This drawer is a fixed drawer and should not be movedfor servicing unless specified by manufacturer. Attempting to move thedrawer partially or completely out of the rack may cause the rack tobecome unstable or cause the drawer to fall out of the rack.

(R001 part 2 of 2)

Safety notices ix

Rack relocation (19″ rack)

CAUTION:Removing components from the upper positions in the rack cabinetimproves rack stability during relocation. Follow these general guidelineswhenever you relocate a populated rack cabinet within a room or building:

v Reduce the weight of the rack cabinet by removing equipment starting atthe top of the rack cabinet. When possible, restore the rack cabinet to theconfiguration of the rack cabinet as you received it. If this configurationis not known, you must do the following:

– Remove all devices in the 32U position and above.

– Ensure that the heaviest devices are installed in the bottom of the rackcabinet.

– Ensure that there are no empty U-levels between devices installed inthe rack cabinet below the 32U level.

– If the rack cabinet you are relocating is part of a suite of rack cabinets,detach the rack cabinet from the suite.

– Inspect the route that you plan to take when moving the rack toeliminate potential hazards.

– Verify that the route that you choose can support the weight of theloaded rack cabinet. Refer to the documentation that came with yourrack cabinet for the weight of a loaded rack cabinet.

– Verify that all door openings are at least 760 x 2030 mm (30 x 80 in.).

– Ensure that all devices, shelves, drawers, doors, and cables are secure.

– Ensure that the four leveling pads are raised to their highest position.

– Ensure that there is no stabilizer bracket installed on the rack cabinetduring movement.

– Do not use a ramp inclined at more than ten degrees.

– Once the rack cabinet is in the new location, do the following:

- Lower the four leveling pads.

- Install stabilizer brackets on the rack cabinet.

- If you removed any devices from the rack cabinet, repopulate therack cabinet from the lowest position to the highest position.

– If a long distance relocation is required, restore the rack cabinet to theconfiguration of the rack cabinet as you received it. Pack the rackcabinet in the original packaging material, or equivalent. Also, lowerthe leveling pads to raise the casters off of the pallet and bolt the rackcabinet to the pallet.

(R002)

x IBM System Storage: N6000 Series Hardware and Service Guide

Fire suppression systems

A fire suppression system is the responsibility of the customer. The customer’sown insurance underwriter, local fire marshal, or a local building inspector, orboth, should be consulted in selecting a fire suppression system that providesthe correct level of coverage and protection. IBM designs and manufacturesequipment to internal and external standards that require certainenvironments for reliable operation. Because IBM does not test any equipmentfor compatibility with fire suppression systems, IBM does not makecompatibility claims of any kind nor does IBM provide recommendations onfire suppression systems.

Safety notices xi

xii IBM System Storage: N6000 Series Hardware and Service Guide

Contents

Safety notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iiiSafety notices and labels . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Danger notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iiiLabels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viCaution notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viAttention notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Laser safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiUsage restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Rack safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiRack installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiRack relocation (19″ rack) . . . . . . . . . . . . . . . . . . . . . . . . . . x

Fire suppression systems . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

About this document. . . . . . . . . . . . . . . . . . . . . . . . . . . xxiiiWho should read this document . . . . . . . . . . . . . . . . . . . . . . . xxiiiSupported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiiiHow this document is organized . . . . . . . . . . . . . . . . . . . . . . . xxivGetting information, help, and service . . . . . . . . . . . . . . . . . . . . . xxiv

Before you call . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvUsing the documentation . . . . . . . . . . . . . . . . . . . . . . . . . xxvWeb sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvHardware service and support . . . . . . . . . . . . . . . . . . . . . . . xxvSupported servers and operating systems . . . . . . . . . . . . . . . . . . . xxviFirmware updates . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi

Conventions and terminology used in this document . . . . . . . . . . . . . . . . xxviTerminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviCommand conventions . . . . . . . . . . . . . . . . . . . . . . . . . xxviiFormatting conventions . . . . . . . . . . . . . . . . . . . . . . . . . xxviiKeyboard conventions . . . . . . . . . . . . . . . . . . . . . . . . . xxviii

How to send your comments . . . . . . . . . . . . . . . . . . . . . . . . xxix

Chapter 1. Preparing for the installation . . . . . . . . . . . . . . . . . . . . . 1Required manuals, tools and equipment . . . . . . . . . . . . . . . . . . . . . . 1Handling static-sensitive devices . . . . . . . . . . . . . . . . . . . . . . . . 2Planning and organizing the installation . . . . . . . . . . . . . . . . . . . . . . 2

Hardware specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 3Checking shipment package contents . . . . . . . . . . . . . . . . . . . . . . 9Rules for installing the system in a rack . . . . . . . . . . . . . . . . . . . . 10Guide to the installation process . . . . . . . . . . . . . . . . . . . . . . . 11

© Copyright IBM Corp. 2008, 2009 xiii

Chapter 2. Connecting an N6000 series system . . . . . . . . . . . . . . . . . . 13Handling fiber-optic cables . . . . . . . . . . . . . . . . . . . . . . . . . . 13Connecting your system to an IP network . . . . . . . . . . . . . . . . . . . . . 13

About the e0M interface . . . . . . . . . . . . . . . . . . . . . . . . . . 14Connecting your system to a power source . . . . . . . . . . . . . . . . . . . . 15Connecting your system to storage . . . . . . . . . . . . . . . . . . . . . . . 15

Connecting a filer to storage expansion units . . . . . . . . . . . . . . . . . . . 16Cabling your system using Fibre Channel expansion adapters . . . . . . . . . . . . 16

Connecting a gateway to external storage . . . . . . . . . . . . . . . . . . . . 20Connecting to a third-party device . . . . . . . . . . . . . . . . . . . . . . 21

Rules for connecting the third-party devices . . . . . . . . . . . . . . . . . . 21Connecting your system to an ASCII terminal console . . . . . . . . . . . . . . . . . 21

ASCII terminal console wiring . . . . . . . . . . . . . . . . . . . . . . . . 21DB-9 to RJ-45 console adapter pin connections . . . . . . . . . . . . . . . . . . 22Connecting to an ASCII terminal console . . . . . . . . . . . . . . . . . . . . 22

Chapter 3. Configuring an N6000 series system . . . . . . . . . . . . . . . . . . 25Configuring the N6000 series system . . . . . . . . . . . . . . . . . . . . . . 25

System setup information worksheet . . . . . . . . . . . . . . . . . . . . . 25Configuring the Fibre Channel port . . . . . . . . . . . . . . . . . . . . . . . 27

N6000 series system active/active or high availability configurations . . . . . . . . . . . 28Configuring for initiator mode. . . . . . . . . . . . . . . . . . . . . . . . 28

Configuring and using the RLM . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 4. Monitoring your system . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 5. Replacing N6000 series system devices . . . . . . . . . . . . . . . . 33Shutting down a controller module . . . . . . . . . . . . . . . . . . . . . . . 34

Shutting down a node in an active/active or high availability configuration . . . . . . . . 34Shutting down a node in an single-controller configuration . . . . . . . . . . . . . . 35

Opening the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Closing the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Replacing the controller module . . . . . . . . . . . . . . . . . . . . . . . . 38

Removing the controller module . . . . . . . . . . . . . . . . . . . . . . . 38Shutting down the controller module . . . . . . . . . . . . . . . . . . . . 39Removing the PCI card and riser . . . . . . . . . . . . . . . . . . . . . . 40Removing the CompactFlash card . . . . . . . . . . . . . . . . . . . . . 40Removing the RLM module . . . . . . . . . . . . . . . . . . . . . . . 40Removing the NVRAM memory DIMM . . . . . . . . . . . . . . . . . . . 41Removing the system memory DIMMs . . . . . . . . . . . . . . . . . . . . 41Removing the NVRAM battery . . . . . . . . . . . . . . . . . . . . . . 41

Installing the controller module . . . . . . . . . . . . . . . . . . . . . . . 41Installing the CompactFlash card . . . . . . . . . . . . . . . . . . . . . . 42Installing the riser and PCI card . . . . . . . . . . . . . . . . . . . . . . 42Installing the RLM module . . . . . . . . . . . . . . . . . . . . . . . . 42Installing the NVRAM and system memory DIMMs . . . . . . . . . . . . . . . 42Installing the NVRAM battery . . . . . . . . . . . . . . . . . . . . . . . 43Closing the system . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Installing the firmware . . . . . . . . . . . . . . . . . . . . . . . . . . 44Reassigning disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

xiv IBM System Storage: N6000 Series Hardware and Service Guide

Testing the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Rebooting the controller module . . . . . . . . . . . . . . . . . . . . . . . 46

Restoring the onboard port configuration (active/active or high availability SAN configurationsonly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Completing the replacement process. . . . . . . . . . . . . . . . . . . . . . 48Replacing the fan module . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Removing a fan module . . . . . . . . . . . . . . . . . . . . . . . . . . 48Installing the replacement fan module . . . . . . . . . . . . . . . . . . . . . 50Completing the replacement process. . . . . . . . . . . . . . . . . . . . . . 51

Replacing DIMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Removing a DIMM . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Installing a DIMM. . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Completing the replacement process. . . . . . . . . . . . . . . . . . . . . . 55

Replacing a PCIe card and riser . . . . . . . . . . . . . . . . . . . . . . . . 55Removing a PCIe card . . . . . . . . . . . . . . . . . . . . . . . . . . 56Installing a PCIe card. . . . . . . . . . . . . . . . . . . . . . . . . . . 57Removing a riser . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Installing a riser . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Completing the replacement process. . . . . . . . . . . . . . . . . . . . . . 60

Replacing a power supply . . . . . . . . . . . . . . . . . . . . . . . . . . 60Removing a power supply . . . . . . . . . . . . . . . . . . . . . . . . . 60Installing a power supply . . . . . . . . . . . . . . . . . . . . . . . . . 61Completing the replacement process. . . . . . . . . . . . . . . . . . . . . . 62

Replacing an NVRAM battery . . . . . . . . . . . . . . . . . . . . . . . . . 62Removing the NVRAM battery . . . . . . . . . . . . . . . . . . . . . . . 62Installing the NVRAM battery . . . . . . . . . . . . . . . . . . . . . . . . 65Completing the replacement process. . . . . . . . . . . . . . . . . . . . . . 67

Battery disposal . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Replacing the Real-time Clock (RTC) battery . . . . . . . . . . . . . . . . . . . . 67

Removing the RTC battery . . . . . . . . . . . . . . . . . . . . . . . . . 68Installing the RTC battery . . . . . . . . . . . . . . . . . . . . . . . . . 69Resetting the date and time on the controller module . . . . . . . . . . . . . . . . 70Completing the replacement process. . . . . . . . . . . . . . . . . . . . . . 71

Battery disposal . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Installing or replacing a Remote LAN Module . . . . . . . . . . . . . . . . . . . 71

Removing the RLM . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Shutting down the controller module . . . . . . . . . . . . . . . . . . . . 72

Installing an RLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Testing the RLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Testing and booting the system . . . . . . . . . . . . . . . . . . . . . . . 77Completing the replacement process. . . . . . . . . . . . . . . . . . . . . . 78Information on using the RLM . . . . . . . . . . . . . . . . . . . . . . . 78

Replacing a CompactFlash card in N6000 series systems . . . . . . . . . . . . . . . . 78Verifying system requirements. . . . . . . . . . . . . . . . . . . . . . . . 79Replacing a CompactFlash card in a single-controller system . . . . . . . . . . . . . 79

Removing the CompactFlash card . . . . . . . . . . . . . . . . . . . . . 79Installing the CompactFlash card . . . . . . . . . . . . . . . . . . . . . . 81Placing the system files on the CompactFlash card . . . . . . . . . . . . . . . . 81Updating the CompactFlash card . . . . . . . . . . . . . . . . . . . . . . 83Restoring environment variables . . . . . . . . . . . . . . . . . . . . . . 84

Contents xv

Replacing a CompactFlash card in an active/active or high availability configuration . . . . . 84Preparing for the CompactFlash card replacement . . . . . . . . . . . . . . . . 85Removing the CompactFlash card . . . . . . . . . . . . . . . . . . . . . 86Installing the replacement CompactFlash card . . . . . . . . . . . . . . . . . 86Updating the CompactFlash card . . . . . . . . . . . . . . . . . . . . . . 88Restoring environment variables and onboard Fibre Channel port configurations . . . . . . 89

Completing the replacement process. . . . . . . . . . . . . . . . . . . . . . 90

Appendix A. Recommended power line sizes . . . . . . . . . . . . . . . . . . . 91Recommended AC power line sizes . . . . . . . . . . . . . . . . . . . . . . . 91

Appendix B. FRU/CRU and power cord list for N series products. . . . . . . . . . . . 93FRU/CRU list for N series products . . . . . . . . . . . . . . . . . . . . . . . 93Power cord list for N series products . . . . . . . . . . . . . . . . . . . . . . 93

Appendix C. Optional adapter cards . . . . . . . . . . . . . . . . . . . . . . 97Dual-port Gigabit Ethernet (GbE) adapter (optical) (FC 1012) . . . . . . . . . . . . . . 98Dual-port 10/100/1000 Ethernet adapter (copper) (FC 1013) . . . . . . . . . . . . . . . 99Dual-port 4-Gbps Fibre Channel HBA for disk attachment (FC 1014) . . . . . . . . . . . . 99Dual-port 4-Gbps Fibre Channel HBA for tape attachment (FC 1015) . . . . . . . . . . . . 99Dual-port 4-Gbps Fibre Channel target HBA (FC 1017) . . . . . . . . . . . . . . . . 100Dual-port GbE iSCSI adapter (optical) (FC 1021) . . . . . . . . . . . . . . . . . . 100Quad-port GbE Ethernet TOE adapter (copper) (FC 1022) . . . . . . . . . . . . . . . 101Quad-port GbE Ethernet adapter (copper) (FC 1023) . . . . . . . . . . . . . . . . . 101Dual-port Ultra320 SCSI HBA for tape attachment (FC 1024) . . . . . . . . . . . . . . 101Dual-port GbE iSCSI target adapter (copper) (FC 1026) . . . . . . . . . . . . . . . . 101Quad-port 4-Gbps Fibre Channel HBA for disk and tape attachment (FC 1029) . . . . . . . . 102Quad-port 4-Gbps Fibre Channel Target adapter (FC 1030) . . . . . . . . . . . . . . . 102Dual-port 10 GbE Ethernet adapter (FC 1031) . . . . . . . . . . . . . . . . . . . 103Dual-port MetroCluster VI HBA (Models A20/A21/A22 only) (FC 1032) . . . . . . . . . . 103SnapMirror over Fibre Channel HBA (FC 1033). . . . . . . . . . . . . . . . . . . 103Quad-port 4-Gbps Fibre Channel HBA for tape and disk attachment (FC 1035) . . . . . . . . 104Dual-port 8-Gbps Fibre Channel target HBA (FC 1036) . . . . . . . . . . . . . . . . 10416 GB Performance Acceleration Module (FC 1056) . . . . . . . . . . . . . . . . . 105512 GB Performance Acceleration Module II (FC 1057) . . . . . . . . . . . . . . . . 105256 GB Performance Acceleration Module II (FC 1058) . . . . . . . . . . . . . . . . 106Quad-port 3-Gbps SAS Adapter (FC 1061) . . . . . . . . . . . . . . . . . . . . 106Dual-port Fibre Channel over Ethernet (FCoE) Target Adapter (optical) (FC 1063) . . . . . . . 107Dual-port Fibre Channel over Ethernet (FCoE) Target Adapter (copper) (FC 1064) . . . . . . . 107Dual-port 10-Gbps NIC (FC 1065) . . . . . . . . . . . . . . . . . . . . . . . 107

Appendix D. Installing or replacing a Performance Acceleration Module . . . . . . . . . 109System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

First time installations: . . . . . . . . . . . . . . . . . . . . . . . . . . 109Replacement or additional module installations. . . . . . . . . . . . . . . . . . 110

Installing or replacing a Performance Acceleration Module . . . . . . . . . . . . . . . 110Enabling the WAFL extended cache software license and functionality . . . . . . . . . . . 111Enabling the WAFL extended cache configuration options . . . . . . . . . . . . . . . 112Completing the replacement process . . . . . . . . . . . . . . . . . . . . . . 113

xvi IBM System Storage: N6000 Series Hardware and Service Guide

Appendix E. IBM System Storage N series documentation. . . . . . . . . . . . . . 115N7000 series systems library . . . . . . . . . . . . . . . . . . . . . . . . . 115N6000 series systems library . . . . . . . . . . . . . . . . . . . . . . . . . 115N5000 series systems library . . . . . . . . . . . . . . . . . . . . . . . . . 115N3300 and N3600 storage systems library . . . . . . . . . . . . . . . . . . . . 115N3700 storage system library . . . . . . . . . . . . . . . . . . . . . . . . . 116EXN1000, EXN2000, EXN3000and EXN4000 storage expansion units library . . . . . . . . . 116Data ONTAP 7.3 filer library . . . . . . . . . . . . . . . . . . . . . . . . . 116Data ONTAP 7.2 filer library . . . . . . . . . . . . . . . . . . . . . . . . . 117Data ONTAP 7.1 filer library . . . . . . . . . . . . . . . . . . . . . . . . . 118Data ONTAP 7.2 and 7.3 gateway systems library . . . . . . . . . . . . . . . . . . 118Data ONTAP 7.1 gateway systems library . . . . . . . . . . . . . . . . . . . . 119Other N series and N series-related documents . . . . . . . . . . . . . . . . . . . 120

Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Important notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Electronic emission notices . . . . . . . . . . . . . . . . . . . . . . . . . 124

Federal Communications Commission (FCC) Class A Statement . . . . . . . . . . . . 124Industry Canada Class A Emission Compliance Statement . . . . . . . . . . . . . . 125Avis de conformité à la réglementation d’Industrie Canada. . . . . . . . . . . . . . 125European Union (EU) Electromagnetic Compatibility Directive . . . . . . . . . . . . 125Germany Electromagnetic Compatibility Directive . . . . . . . . . . . . . . . . . 125People’s Republic of China Class A Electronic Emission Statement . . . . . . . . . . . 127Japan VCCI Class A ITE Electronic Emission Statement . . . . . . . . . . . . . . . 127Taiwan Class A warning statement . . . . . . . . . . . . . . . . . . . . . . 127Korea Class A Electronic Emission Statement . . . . . . . . . . . . . . . . . . 127

Power cords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Contents xvii

xviii IBM System Storage: N6000 Series Hardware and Service Guide

Figures

1. Onboard port locations (Ethernet) . . . . . . . . . . . . . . . . . . . . . . 142. e0M interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153. Onboard port locations (Fibre Channel) . . . . . . . . . . . . . . . . . . . . 164. Cabling ports 0b and 0d to switches . . . . . . . . . . . . . . . . . . . . . 185. Cabling ports 0a and 0c to storage expansion units . . . . . . . . . . . . . . . . 196. Cabling expansion cards to storage expansion units for dual-path Fibre Channel cabling 207. N6000 series system components - Front . . . . . . . . . . . . . . . . . . . 338. N6000 series system components - Rear . . . . . . . . . . . . . . . . . . . . 349. N6000 series exterior components . . . . . . . . . . . . . . . . . . . . . . 36

10. N6000 series system components - Exploded view . . . . . . . . . . . . . . . . 3711. Fan module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5012. Replacing DIMMs on an N6070 system . . . . . . . . . . . . . . . . . . . . 5313. Replacing DIMMs on an N6040 system . . . . . . . . . . . . . . . . . . . . 5314. Lifting the DIMM from the slot . . . . . . . . . . . . . . . . . . . . . . 5415. Replacing a PCIe card and riser . . . . . . . . . . . . . . . . . . . . . . 5716. Replacing a power supply . . . . . . . . . . . . . . . . . . . . . . . . 6117. NVRAM locations . . . . . . . . . . . . . . . . . . . . . . . . . . . 6418. NVRAM battery removal . . . . . . . . . . . . . . . . . . . . . . . . 6519. RTC battery removal . . . . . . . . . . . . . . . . . . . . . . . . . . 6920. CompactFlash card removal. . . . . . . . . . . . . . . . . . . . . . . . 80

© Copyright IBM Corp. 2008, 2009 xix

xx IBM System Storage: N6000 Series Hardware and Service Guide

Tables

1. N6000 series physical characteristics and environmental requirements . . . . . . . . . . 32. N6000 series systems maximum electrical power . . . . . . . . . . . . . . . . . 43. N6040 electrical requirements–one controller module . . . . . . . . . . . . . . . . 44. N6040 electrical requirements–two controller modules . . . . . . . . . . . . . . . 55. N6040 electrical requirements with two PAM I or II cards–one controller module . . . . . . 56. N6040 electrical requirements with four PAM I or II cards–two controller modules . . . . . . 67. N6060 electrical requirements–one controller module . . . . . . . . . . . . . . . . 68. N6060 electrical requirements–two controller modules . . . . . . . . . . . . . . . 69. N6060 electrical requirements with two PAM I or II cards–one controller module . . . . . . 7

10. N6060 electrical requirements with four PAM I or II cards–two controller modules . . . . . . 711. N6070 electrical requirements–one controller module . . . . . . . . . . . . . . . . 812. N6070 electrical requirements–two controller modules . . . . . . . . . . . . . . . 813. N6070 electrical requirements with four PAM I or II cards–one controller module . . . . . . 914. N6070 electrical requirements with eight PAM I or II cards–two controller modules . . . . . 915. Filer installation process procedures . . . . . . . . . . . . . . . . . . . . . 1216. RJ-45 connection pinout for the ASCII terminal wiring . . . . . . . . . . . . . . . 2117. Console adapter pin number connections . . . . . . . . . . . . . . . . . . . 2218. Communication parameters . . . . . . . . . . . . . . . . . . . . . . . . 2319. N series system setup worksheet . . . . . . . . . . . . . . . . . . . . . . 2620. RLM configuration manuals. . . . . . . . . . . . . . . . . . . . . . . . 2921. 110V, single phase recommended conductor sizes . . . . . . . . . . . . . . . . 9122. 220V, single phase recommended conductor sizes . . . . . . . . . . . . . . . . 9123. American Wire Gage to Harmonized Cordage equivalents . . . . . . . . . . . . . 9124. Optional adapter cards supported by N6000 series systems . . . . . . . . . . . . . 9725. Dual-port 4-Gbps Fibre Channel HBA for disk (FC 1014) - maximum cable lengths . . . . . 9926. Dual-port 4-Gbps Fibre Channel HBA for tape (FC 1015) - maximum cable lengths . . . . . 10027. Dual-port 4-Gbps Fibre Channel target HBA (FC 1017) - maximum cable lengths . . . . . 10028. Quad-port 4-Gbps Fibre Channel HBA for disk and tape attachment (FC 1029) - maximum

cable lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10229. Quad-port 4-Gbps Fibre Channel Target adapter (PCIe) (FC 1030) - maximum cable lengths 10230. Quad-port 4-Gbps Fibre Channel HBA for tape and disk attachment (FC 1035) - maximum

cable lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10431. Dual-port 8-Gbps Fibre Channel target HBA (FC 1036) - maximum cable lengths . . . . . 104

© Copyright IBM Corp. 2008, 2009 xxi

xxii IBM System Storage: N6000 Series Hardware and Service Guide

About this document

This guide describes how to connect and manage the following IBM SystemStorage™ N6000 series systems:v N6040 (model numbers 2858-A10 and 2858-A20)v N6060 (model numbers 2858-A12 and 2858-A22)v N6070 (model numbers 2858-A11 and 2858-A21)

Note: Throughout this document, the N6040, N6060, and N6070 systems arereferred to generically as N6000 series systems unless information appliesonly to a specific product, in which case the specific machine name isused.

For information about installation and setup, see the Installation and SetupInstructions that came with your system.

For information about error messages and troubleshooting, see the IBM SystemStorage N series Platform Monitoring Guide.

Compliance ID 2858-NAS covers MT/models 2858-A10, 2858-A11, 2858-A20,2858-A21, 2858-A12, and 2858-A22.

Who should read this document

This guide is for qualified system administrators and service personnel whoare familiar with IBM storage systems. This document is for customer use. Itaddresses setup, operation, and servicing of the 2858 models A10, A11, A20,A21, A12, and A22. This document is intended to provide information tocustomers, operators, administrators, installers, and service personnel.

Supported features

IBM System Storage N series storage systems and expansion boxes are drivenby NetApp Data ONTAP software. Some features described in the productsoftware documentation are neither offered nor supported by IBM. Pleasecontact your local IBM representative or reseller for further details.

Information about supported features can also be found at the following website:

www.ibm.com/storage/support/nas/

© Copyright IBM Corp. 2008, 2009 xxiii

http://www.ibm.com/storage/support/nas/

A listing of currently available N series products and features can be found atthe following web site:

www.ibm.com/storage/nas/

How this document is organized

This document contains the following chapters:v Chapter 1, “Preparing for the installation,” on page 1 provides an overview

of the entire system installation process, hardware specifications, and theappropriate documentation references for the procedures.

v Chapter 2, “Connecting an N6000 series system,” on page 13 describes howto connect an N6000 series system.

v Chapter 3, “Configuring an N6000 series system,” on page 25 describes howto configure an N6000 series system.

v Chapter 4, “Monitoring your system,” on page 31 describes how to monitoryour system based on the LEDs for your system.

v Chapter 5, “Replacing N6000 series system devices,” on page 33 describeshow to replace devices in your system.

v Appendix A, “Recommended power line sizes,” on page 91 discusses howto determine the power line lengths running from your system to thepower source.

v Appendix B, “FRU/CRU and power cord list for N series products,” onpage 93 lists the feature codes for the power cords for N6000 series systems.

v Appendix C, “Optional adapter cards,” on page 97 describes the optionaladapter cards supported for N6000 series systems.

v Appendix D, “Installing or replacing a Performance Acceleration Module,”on page 109 describes the PAM I and II cards supported for the N6000series systems.

v Appendix E, “IBM System Storage N series documentation,” on page 115lists the documents in the IBM System Storage N series hardware and DataONTAP product libraries, as well as other related documents.

Getting information, help, and service

If you need help, service, or technical assistance or just want moreinformation about IBM products, you will find a wide variety of sourcesavailable from IBM to assist you. This section contains information aboutwhere to go for additional information about IBM and IBM products, what todo if you experience a problem with your IBM System Storage N seriesproduct, and whom to call for service, if it is necessary.

The following applies in Taiwan:

xxiv IBM System Storage: N6000 Series Hardware and Service Guide

http://www.ibm.com/storage/nas/

IBM Taiwan Product Service Contact Info:IBM Taiwan Corporation3F, No 7, Song Ren Rd., Taipei TaiwanTel: 0800-016-888

Before you callBefore you call, make sure that you have taken these steps to try to solve theproblem yourself:v Check all cables to make sure that they are connected.v Check the power switches to make sure that the system is turned on.v Use the troubleshooting information in your system documentation and use

the diagnostic tools that come with your system.v Check the IBM support web site for known problems and limitations.

Using the documentationInformation about the N series product and Data ONTAP software is availablein printed documents and a documentation CD that comes with your system.The same documentation is available as PDF files on the IBM NAS supportweb site:


Web sitesIBM maintains pages on the World Wide Web where you can get the latesttechnical information and download device drivers and updates.v For NAS product information, go to the following web site:

www.ibm.com/storage/nas/v For NAS support information, go to the following web site:

www.ibm.com/storage/support/nas/v For AutoSupport information, go to the following web site:


Hardware service and supportYou can receive hardware service through IBM Integrated TechnologyServices. Visit the following web site for support telephone numbers:

www.ibm.com/planetwide/

About this document xxv





http://www.ibm.com/planetwide

Supported servers and operating systemsIBM N series products attach to many servers and many operating systems.To determine the latest supported attachments, visit the following web siteand access the IBM System Storage N series interoperability matrix:


Firmware updatesAs with all devices, it is recommended that you run the latest level offirmware, which is embedded in Data ONTAP. If there are changes, they willbe posted to the following web site:


Note: If you do not see new changes on the web site, you are running thelatest level of firmware.

Verify that the latest level of firmware is installed on your machine beforecontacting IBM for technical support.

Conventions and terminology used in this document

This guide uses the following terminology, command conventions, formatconventions and keyboard conventions:

TerminologyIn this and other IBM N series documents, the term filer describes IBM Nseries systems that either contain internal disk storage or attach to the diskstorage expansion units specifically designed for the IBM N series systems.The following disk storage expansion units specifically designed for the IBMN series filers:v IBM EXN4000 Fibre Channel disk storage expansion unitv IBM EXN3000 SAS/SATA disk storage expansion unitv IBM EXN2000 Fibre Channel disk storage expansion unitv IBM EXN1000 serial advanced technology attachment (SATA) storage

expansion unit

The term gateway describes IBM N series storage controller models that areconfigured as storage gateways. Gateways do not contain internal disk storage.IBM N series gateways attach to external storage devices on a Storage AreaNetwork (SAN).

The terms system or storage system refer to either a gateway by itself or a filer,either by itself or with additional disk drives.

In addition, this guide uses the following terms:

xxvi IBM System Storage: N6000 Series Hardware and Service Guide



v AT-FCX refers to the controller module of the serial advanced technologyattachment (SATA) storage expansion unit (EXN1000).

v Active/active configuration or high availability configuration refers to a HighAvailability system with at least two nodes that share resources to provideredundancy.

v Device carrier refers to the container that encases a fan/power supply unitor a disk.

v Disk applies to any hard disk drive.v Disk shelf or shelf refers to any storage expansion unit containing hard disk

drives.v ESH2 refers to the controller module of the EXN2000 Fibre Channel disk

storage expansion unit.v ESH4 refers to the controller module of the EXN4000 Fibre Channel disk

storage expansion unit.v IOM refers to the Input/Output module of the EXN3000 SAS/SATA disk

storage expansion unit.v Loop or Fibre-Channel Arbitrated Loop refers to one or more daisy-chained

EXN1000, EXN2000, or EXN4000 storage expansion units connected to an Nseries storage system.

v Node refers to the system controller module that executes the software onan N series system. There is one node in the A10/A11/A12(single-controller) models; there are two nodes in the A20/A21/A22(active/active or high availability) models. In a dual-controller N6000 seriessystem, the nodes are located one over the other. The top one is controllermodule A and the bottom one is controller module B, as labeled on thesystem chassis.

v Stack or SAS stack refers to a stack of one or more EXN3000 storageexpansion units using IOM modules connected to the storage system. Themaximum number of storage expansion units in a stack of storageexpansion units and the number of storage expansion unit stacks in aconfiguration are dependent on the type of storage system.

Command conventionsYou can enter commands on the system console or from any client that canobtain access to the storage system using a Telnet session. In examples thatillustrate commands executed on a UNIX® workstation, the command syntaxand output might differ, depending on your version of UNIX.

Formatting conventionsThe following table lists different character formats used in this guide to setoff special information.

About this document xxvii

Formatting convention Type of information

Italic type v Words or characters that require specialattention.

v Placeholders for information you mustsupply. For example, if the guiderequires you to enter the fctestadaptername command, you enter thecharacters “fctest” followed by theactual name of the adapter.

v Book titles in cross-references.

Monospaced font v Command and daemon names.

v Information displayed on the systemconsole or other computer monitors.

v The contents of files.

Bold monospaced font Words or characters you type. What youtype is always shown in lowercase letters,unless your program is case-sensitive anduppercase letters are necessary for it towork properly.

Keyboard conventionsThis guide uses capitalization and some abbreviations to refer to the keys onthe keyboard. The keys on your keyboard might not be labeled exactly as theyare in this guide.

What is in this guide... What it means...

hyphen (-) Used to separate individual keys. Forexample, Ctrl-D means holding down theCtrl key while pressing the D key.

Enter Used to refer to the key that generates acarriage return, although the key isnamed Return on some keyboards.

type Used to mean pressing one or more keyson the keyboard.

enter Used to mean pressing one or more keysand then pressing the Enter key.

xxviii IBM System Storage: N6000 Series Hardware and Service Guide

How to send your comments

Your feedback is important in helping us provide the most accurate andhigh-quality information. If you have comments or suggestions for improvingthis document, send us your comments by e-mail to [email protected].

Be sure to include the following:v Exact publication titlev Publication form number (for example, GC26-1234-02)v Page, table, or illustration numbersv A detailed description of any information that should be changed

About this document xxix

mailto:[email protected]?subject=IBM System Storage N6000 Series Hardware and Service Guide (GC53-1142-03)

xxx IBM System Storage: N6000 Series Hardware and Service Guide

Chapter 1. Preparing for the installation

This chapter provides an overview of the entire IBM System Storage N6000series system installation process, hardware specifications, and the appropriatedocumentation references for the procedures.

Refer to the Installation and Setup Instructions that came with your system forfurther information about installing your equipment.

This chapter discusses the following topics:v “Required manuals, tools and equipment”v “Handling static-sensitive devices” on page 2v “Planning and organizing the installation” on page 2

Required manuals, tools and equipment

You need the following manuals in addition to this manual:v Installation and Setup Instructions for your system and storage expansion

unitsv Data ONTAP Software Setup Guide for your version of Data ONTAP, if

applicablev Data ONTAP Active/Active Configuration Guide or Data ONTAP High

Availability Configuration Guide for your version of Data ONTAP, ifapplicable

You need to supply the following tools and equipment:v Ethernet LAN cablesv Fibre Channel cablesv Console (for example, a PC or laptop) with a serial portv #2 Phillips screwdriver and slotted screwdriverv Grounding leash and ESD strapv 7-mm nut driver (required if removing or installing storage expansion

units)

© Copyright IBM Corp. 2008, 2009 1

Handling static-sensitive devices

CAUTION:This system uses electronic components that are sensitive to staticelectricity. Static discharge from your clothing or other fixtures aroundyou can damage these components. Put on an antistatic ESD strap andgrounding leash to free yourself of static electricity before touching anyelectronic components.

Attention: Static electricity can damage electronic devices and your system.To avoid damage, keep static-sensitive devices in their static-protectivepackages until you are ready to install them.

To reduce the possibility of electrostatic discharge (ESD), observe thefollowing precautions:v Limit your movement. Movement can cause static electricity to build up

around you.v Handle the device carefully, holding it by its edges or its frame.v Do not touch solder joints, pins, or exposed printed circuitry.v Do not leave the device where others can handle and possibly damage the

device.v While the device is still in its static-protective package, touch it to an

unpainted metal part of the system unit for at least two seconds. Thisdrains static electricity from the package and from your body.

v Remove the device from its package and install it directly into your systemunit without setting it down. If it is necessary to set the device down, placeit in its static-protective package. Do not place the device on your systemunit cover or on a metal table. Take additional care when handling devicesduring cold weather because heating reduces indoor humidity andincreases static electricity.

Planning and organizing the installation

This section identifies the shipment contents and the rules and regulationsyou need to observe for the proper installation of your system. It alsoprovides an overview of the entire system installation process and theappropriate documentation references for the procedures.

For detailed information, see the following topics:v “Hardware specifications” on page 3v “Checking shipment package contents” on page 9v “Rules for installing the system in a rack” on page 10v “Guide to the installation process” on page 11

2 IBM System Storage: N6000 Series Hardware and Service Guide

Hardware specificationsThe following table lists the characteristics and requirements for yourhardware.

svc00168

32-55 kg (70.5-121.2 lbs)

DANGER

The weight of this part or unit is between 44 and 54 kg (97 and 118 lb). Ittakes three persons to safely lift this part or unit. (C010)

Table 1. N6000 series physical characteristics and environmental requirements

Physical characteristics

Weight v A10: 44.4 kg (97.8 lb)

v A20: 52.2 kg (115 lb)

v A11: 44.9 kg (99 lb)

v A21: 53.2 kg (117.3 lb)

v A12: 44.8 kg (98.8 lb)

v A22: 53.1 kg (117 lb)

Rack units 6U

Height 25.9 cm (10.2 in.)

Width 44.7 cm (17.6 in.)

Depth 61.7 cm (24.3 in.) without cabletray

71.3 cm (28.1 in.) with cabletray

Clearance dimensions

Front-cooling All versions 6 in. (15.2 cm)

Rear-cooling All versions 12 in. (30.5 cm)

Front-maintenance All versions 30 in. (76.2 cm)

Rear-maintenance All versions 36 in. (91.4 cm)

Environmental requirementsNote: Operating at the extremes of the following environmental requirements mightincrease the risk of device failure.

Operating temperature maximum range 50° F to 104° F

(10° C to 40° C)

Chapter 1. Preparing for the installation 3

Table 1. N6000 series physical characteristics and environmentalrequirements (continued)

Operating temperature recommended range 68° F to 77° F

(20° C to 25° C)

Nonoperating temperature range -40° F to 149° F

(-40° C to 65° C)

Relative humidity 20 to 80% noncondensing

Recommended operating temperature relativehumidity range

40 to 55%

Maximum wet bulb temperature 28° C (82° F)

Maximum altitude 3050 m (10,000 ft.)

Acoustic level 56 dBA @ 23° C

7.4 bels @ 23° C

The following tables list the maximum electrical power for the N6000 seriessystems and the electrical requirements for different configurations of theN6000 series systems.

Table 2. N6000 series systems maximum electrical power

System Maximum electrical power

N6000 series systems 100-240 V ac, 12-8 A, 47-63 Hz

In the following tables, Worst-case indicates a system running with one PSUand high fan speed. Typical Per PSU/System, two PSUs indicates a systemrunning one PSU on one circuit and a system running two PSUs on twocircuits.

Table 3. N6040 electrical requirements–one controller module

Input voltage 100 to 120V 200 to 240V

Worst-case,singlePSU

Typical Worst-case,singlePSU

Typical

Per PSU System,two PSUs


Input currentmeasured, A

3.98 1.89 3.77 1.97 0.97 1.93

Input powermeasured, W

396 187 373 385 183 366


Table 3. N6040 electrical requirements–one controller module (continued)


Thermaldissipation,BTU/hr

1350™ 636 1272 1313 625 1249

Input powerfrequency, Hz

50 to 60

Table 4. N6040 electrical requirements–two controller modules




Typical




7.38 2.99 5.97 3.60 1.49 2.98


736 297 594 712 291 581


2509 1013 2026 2427 991 1981


50 to 60

Table 5. N6040 electrical requirements with two PAM I or II cards–one controllermodule




Typical




4.06 1.93 3.86 2.01 0.99 1.98


402 192 383 396 190 379


1372 654 1307 1352 647 1293


50 to 60


Table 6. N6040 electrical requirements with four PAM I or II cards–two controllermodules




Typical




7.69 3.29 6.58 3.75 1.58 3.15


769 328 655 745 315 630


2625 1117 2234 2543 1075 2150


50 to 60





Typical




4.80 2.25 4.50 2.38 1.16 2.32


476 220 440 460 225 450


1625 751 1502 1570 768 1535


50 to 60





Typical




9.25 3.88 7.76 4.40 2.15 4.30


Table 8. N6060 electrical requirements–two controller modules (continued)



916 380 760 860 419 838


3126 1297 2594 2935 1430 2860


50 to 60

Table 9. N6060 electrical requirements with two PAM I or II cards–one controllermodule




Typical




4.90 2.31 4.62 2.44 1.19 2.38


487 227 453 478 230 460


1662 773 1546 1631 785 1570


50 to 60

Table 10. N6060 electrical requirements with four PAM I or II cards–two controllermodules




Typical




9.65 4.09 8.17 4.51 2.28 4.55


959 405 809 890 441 882


3273 1381 2761 3037 1505 3010


Table 10. N6060 electrical requirements with four PAM I or II cards–two controllermodules (continued)



50 to 60





Typical




5.07 2.37 4.74 2.52 1.19 2.38


505 235 470 493 230 459


1722 801 1602 1680 782 1564


50 to 60





Typical




9.74 4.07 8.14 4.69 2.02 4.03


969 405 810 930 394 788


3305 1381 2761 3170 1343 2686


50 to 60


Table 13. N6070 electrical requirements with four PAM I or II cards–one controllermodule




Typical




5.27 2.49 4.98 2.62 1.25 2.5


525 247 494 513 241 482


1790 843 1685 1749 822 1644


50 to 60

Table 14. N6070 electrical requirements with eight PAM I or II cards–two controllermodules




Typical




10.54 4.49 8.98 5.08 2.22 4.44


1048 447 894 1006 434 868


3574 1525 3049 3430 1480 2960


50 to 60

Checking shipment package contentsMake sure that your shipment package includes the following items, inaddition to the IBM System Storage N6000 Series Hardware and Service Guide.v Single-controller system

– 1 single-controller system containing the power supplies and any optionsyou ordered

– 1 console adapter cable, RJ-45 to DB-9


– 1 cable management tray– 1 ESD wrist strap– 1 serial null modem cable– 1 set of IBM publications– 2 power cords– 4 SFPsThere will also be envelopes with the software EULA and license keys.A rail kit for mounting the single-controller system in a standard IBM19–inch rack may also be present.

v Dual-controller (active/active or high availability) system– 1 dual-controller system containing the power supplies and any options

you ordered– 2 console adapter cables, RJ-45 to DB-9– 2 cable management trays– 1 wrist ESD straps– 2 serial null modem cables– 1 set of IBM publications– 2 power cords– 8 SFPsThere will also be envelopes with the software EULA and license keys.A rail kit for mounting the dual-controller (active/active or highavailability) system in a standard IBM 19–inch rack may also be present.

Rules for installing the system in a rack

Attention: The rack installation instructions provided in this document andin the Installation and Setup Instructions for your N series product applyspecifically to the installation of the N series product in an IBM 19-inch rack.IBM service personnel cannot install the N series product in a non-IBM rack.

If the N series product is being installed in a non-IBM rack, the rails shippedwith the N series product may or may not work with the non-IBM rack.Physical installation of the N series product in a non-IBM rack is thecustomer’s responsibility.

You need to observe the following rules and restrictions when installing anN6000 series system in a standard IBM 19-inch (48.26 cm) equipment rackwith mounting rails:


svc00168

32-55 kg (70.5-121.2 lbs)

DANGER

The weight of this part or unit is between 44 and 54 kg (97 and 118 lb). Ittakes three persons to safely lift this part or unit. (C010)

v You must work with two other people.CAUTION:The system is extremely heavy. To avoid injuring yourself or damagingthe system, you must work with at least two other people when youinstall the system in the rack.

v Install the system at the bottom of your configuration, so that loops extendabove your system.DANGER

To avoid hazardous conditions due to uneven mechanical loading,always install the heaviest devices in the bottom of the rack cabinet.Always install servers and optional devices starting from the bottom ofthe rack cabinet. (R001 part 1 of 2)

v When installing storage expansion units in a rack, do not exceed themaximum storage limit for your system.

v Make sure that the ID on the back panel of each storage expansion unitmatches the ID specified on its label.

v Always install the storage expansion units fully loaded. Do not remove diskdrives to reduce the weight.

Guide to the installation processThe following table provides a guide to the filer installation process.

Refer to the Installation and Setup Instructions that came with your system orstorage expansion unit for complete installation details.

Note: The initial hardware installation of an N6000 series gateway isperformed by IBM. Additional installation services can be performed byIBM through an IBM services offering. Contact your IBM representativefor more information.


Table 15. Filer installation process procedures

Stage Procedure

Is theprocedurerequired?

Procedure is performed by...

For instructions, see...Filer Gateway

1 Install the systemin a standardIBM 19-inch rack.

Yes Customer IBM The Installation and SetupInstructions for yoursystem

2 Connect thesystem to the IP(InternetProtocol)network.

Yes Customer Customer “Connecting your systemto an IP network” onpage 13, or the Installationand Setup Instructions thatcame with your system

3 Filer: Connectthe storagesystem to storageexpansion units.

Yes Customer n/a “Connecting a filer tostorage expansion units”on page 16, or theInstallation and SetupInstructions that camewith your system

Gateway:Connect thesystem to theback-end storage.

Yes n/a Customer Refer to thedocumentation for yourexternal storage foradditional information.

4 Connect thesystem to apower source.

Yes Customer Customer “Connecting your systemto a power source” onpage 15, or the Installationand Setup Instructions thatcame with your system

5 Configure thesystem.

Yes Customer Customer The IBM System Storage Nseries Data ONTAPSoftware Setup Guide foryour version of DataONTAP, or the Installationand Setup Instructions thatcame with your system

6 Connect thesystem to athird-partydevice.

No Customer Customer “Connecting your systemto storage” on page 15


Chapter 2. Connecting an N6000 series system

This chapter describes how to connect an N6000 series system in the followingtopics:v “Handling fiber-optic cables”v “Connecting your system to an IP network”v “Connecting your system to a power source” on page 15v “Connecting your system to storage” on page 15

Handling fiber-optic cables

Before you use fiber-optic cables, read the following precautions.

Attention: To avoid damage to the fiber-optic cables, follow these guidelines:v Do not route the cable along a folding cable-management arm.v When attaching to a device on slide rails, leave enough slack in the cable so

that it does not bend to a radius of less than 38 mm (1.5 in.) when extendedor become pinched when retracted.

v Route the cable away from places where it can be snagged by other devicesin the rack cabinet.

v Do not overtighten the cable straps or bend the cables to a radius of lessthan 38 mm (1.5 in.).

v Do not put excess weight on the cable at the connection point. Be sure thatthe cable is well supported.

CAUTION:Data processing environments can contain equipment transmitting onsystem links with laser modules that operate at greater than Class 1power levels. For this reason, never look into the end of an opticalfiber cable or open receptacle.

Connecting your system to an IP network

Each node of your system connects to an IP network. If you have anactive/active or high availability system, both nodes need to connect to thenetwork. For information that describes how to connect your system, refer tothe Installation and Setup Instructions that came with your system.


The N6000 series system has two onboard Ethernet ports per node, labelede0a and e0b, as shown in Figure 1. Up to four Network Interface Cards (NICs)per node can be plugged into the PCI slots to provide additional Ethernetports.

The integrated Ethernet RJ-45 twisted-pair connectors are compatible with theIEEE 802.3 Ethernet network 10/100/1000 BASE-TX link. When connecting tothe Ethernet port, connect a twisted-pair (CAT-5 or better) cable to the RJ-45Ethernet port located on the back of the system drawer.

If you are connecting to a copper NIC, use RJ-45 CAT-5 or better coppercables.

If you are connecting to a fiber NIC, use (50- or 62.5-micron) fiber-optic cableswith LC connectors.

For information about monitoring the Ethernet port LEDs, see the IBM SystemStorage N Series Platform Monitoring Guide.

About the e0M interfaceThe e0M is the preferred Data ONTAP interface for the management LAN forenvironments that use dedicated LANs to isolate management traffic fromdata traffic. You use the e0M interface for Data ONTAP administrative tasks.See Figure 2 on page 15.

The e0M interface is separate from the RLM interface, but both interfaces sitbehind the RJ-45 port (labeled with a wrench icon). This port is called theManagement port and connects to an internal Ethernet switch, which providesconnectivity to both interfaces. It is recommended that you configure bothinterfaces.

0c 0d0a 0be0be0a!

n6hw014

Figure 1. Onboard port locations (Ethernet)


See the Data ONTAP System Administration Guide for more information.

Connecting your system to a power source

The N6000 series systems are shipped with redundant power supplies,referred to as PSU1 and PSU2. Each power supply has its own AC powercord. You should have separate circuit breakers for each power supply toensure power redundancy.

For information on connecting your N6000 series system to a power source,see the Installation and Setup Instructions that came with your system.

Connecting your system to storage

The N6000 series system has four onboard Fibre Channel ports per node,labeled 0a thru 0d, as shown in Figure 3 on page 16. Up to four HBAs pernode can be plugged into the PCI slots to provide additional Fibre Channelports. Attach the (50- or 62.5-micron) fiber-optic cables with LC connectors tothe Fibre Channel ports.

Note: SFPs must be firmly seated in the Fibre Channel ports before makingconnections.

e0a e0b

DataLAN

ManagementLAN

Ethernetswitch

e0MRLM

DataONTAP

Storage controller

n6hw015

Figure 2. e0M interface

Chapter 2. Connecting an N6000 series system 15

Connecting a filer to storage expansion unitsYou must connect at least one storage expansion unit per node to your N6000series filer. A single-controller filer (A10/A11/A12) must be connected to atleast one storage expansion unit. A dual-controller (active/active or highavailability) filer (A20/A21/A22) must be connected to at least two storageexpansion units. Fiber-optic cables must be used for the connection from thefiler to the first storage expansion unit.

Attention: Make sure that all storage expansion unit (1Gb/2Gb/4Gb)switches are set to the 2Gb or 4Gb (if supported) position. If necessary, referto the documents that came with the storage expansion unit for informationabout checking and changing the switch setting.

For information that describes how to connect your N6000 series filer usingthe onboard Fibre Channel ports to storage expansion units, see the Installationand Setup Instructions that came with your system.

Attention: If you are using optional adapter cards instead of the onboardFibre Channel ports to connect your N6000 series filer to storage expansionunits, see the cabling instructions described in “Cabling your system usingFibre Channel expansion adapters.”

Dual-path Fibre Channel cabling is supported for N6000 series filers.Dual-path Fibre Channel cabling is designed to improve reliability, availabilityand serviceability of the storage expansion units attached to the storagecontroller by creating two redundant paths from each storage controller toeach loop of the storage expansion units. For more information about usingdual-path Fibre Channel cabling, see the Installation and Setup Instructions thatcame with your system.

Cabling your system using Fibre Channel expansion adaptersThe illustrations in this section provide an example of cabling for a dual-nodeactive/active or high availability N6000 series filer SAN configuration withfour FCP host-side SAN connections and two loops of disk storage expansionunits, each with dual-path (also called multipath) Fibre Channel cabling to the

0c 0d0a 0be0be0a!

n6hw014

Figure 3. Onboard port locations (Fibre Channel)


disk storage expansion units in each loop. The cabling shown in this exampleuses both onboard Fibre Channel ports and Fibre Channel expansion adaptersfor connections to expansion unit storage.

Attention: If you are connecting to EXN3000 storage expansion units, referto the cabling instructions provided in the IBM System Storage EXN3000Storage Expansion Unit Hardware and Service Guide.

For additional information about optional adapter cards, see Appendix C,“Optional adapter cards,” on page 97.

Important: If you are not using the onboard ports for storage, then you mustset your onboard ports to Target mode, as described in the IBMSystem Storage N series Data ONTAP Block Access Management Guidefor your version of Data ONTAP.

Notes:

1. The illustrations in the following sections show N6000 series storagesystem connections to EXN4000 or EXN2000 storage expansion units. InEXN1000 storage expansion units, the positions of the In and Out ports arereversed from those of the EXN4000 or EXN2000.

2. The ESH4 and ESH2 are self-terminating and do not have a terminateswitch. The AT-FCX is self-terminating as long as no cable is plugged intothe Out port of the last storage expansion unit.

3. Terminate unused Fibre Channel ports with Fibre Channel loopback plugs.

Step 1: Connecting the storage controller to the Fibre Channel SAN:Connect Fibre Channel ports 0b and 0d of each storage controller to separate(dual-fabric) SAN switches, as shown in Figure 4 on page 18.


2. Connecting the storage controllers to the disk storage expansion units:Using Fibre Channel ports 0a and 0c on each storage controller, connect thestorage controllers to each of the two loops of disk storage expansion units asfollows.1. Connect upper storage controller A Fibre Channel port 0a to the FC IN

port of the upper ESH4 (or AT-FCX) controller in the first disk storageexpansion unit of loop 1.

2. Connect lower storage controller B Fibre Channel port 0a to the FC INport of the lower ESH4 (or AT-FCX) controller in the first disk storageexpansion unit of loop 1.

3. Connect lower storage controller B Fibre Channel port 0c to the FC IN portof the upper ESH4 (or AT-FCX) controller in the first disk storageexpansion unit of loop 2.

4. Connect upper storage controller A Fibre Channel port 0c to the FC INport of the lower ESH4 (or AT-FCX) controller in the first disk storageexpansion unit of loop 2.

Figure 5 on page 19 shows the Fibre Channel connections from the onboardFibre Channel ports on the N6000 series active/active or high availabilitysystem to storage expansion units.

INOUTIN OUTPSU PSU

INOUTIN OUT

Module A

Module BPSU PSU

PSU

PSU

0d0c0b0a

0d0c0b0a

n6hw016

ControllerA

ControllerB

Loop 1Disk EXN 1

Loop 2Disk EXN 1

Figure 4. Cabling ports 0b and 0d to switches


Step 3: Connecting disk storage expansion units to disk storage expansionunits: If there are more than one disk storage expansion units in each loop,connect the disk storage expansion units together as follows. For each storageexpansion unit in the loop:1. Connect the FC OUT port of the upper ESH4 (or AT-FCX) controller to the

FC IN port of the upper ESH4 (or AT-FCX) on the next disk storageexpansion unit in the loop.

2. Connect the FC OUT port of the lower ESH4 (or AT-FCX) controller to theFC IN port of the lower ESH4 (or AT-FCX) on the next disk storageexpansion unit in the loop.

Step 4. Connecting the last disk storage expansion unit in each loop back tothe storage controller (dual-path Fibre Channel cabling): If implementingdual-path Fibre Channel cabling, connect the last disk storage expansion unitin each loop back to the other storage controller, as shown in Figure 6 on page20. In this example, the dual-path cabling is achieved using expansion adaptercards.1. Connect the upper ESH4 (or AT-FCX) controller FC OUT port of the last

disk storage expansion unit in loop 1 to a Fibre Channel port in the lowerstorage controller B (shown being connected to Fibre Channel port A inthe optional expansion adapter in slot 4 of the lower storage controller B).

2. Connect the lower ESH4 (or AT-FCX) controller FC OUT port of the lastdisk storage expansion unit in loop 1 to a Fibre Channel port in the upper

0d0c0b0a

0d0c0b0a

INOUTIN OUT

INOUTIN OUT

n6hw017

ControllerA

ControllerB

Loop 1Disk EXN 1

Loop 2Disk EXN 1

Figure 5. Cabling ports 0a and 0c to storage expansion units


storage controller A (shown being connected to Fibre Channel port A inthe optional expansion adapter in slot 4 of the upper storage controller A).

3. Connect the upper ESH4 (or AT-FCX) controller FC OUT port of the lastdisk storage expansion unit in loop 2 to a Fibre Channel port in the upperstorage controller A (shown being connected to Fibre Channel port B inthe optional expansion adapter in slot 4 of the lower storage controller A).

4. Connect the lower ESH4 (or AT-FCX) controller FC OUT port of the lastdisk storage expansion unit in loop 2 to a Fibre Channel port in the lowerstorage controller B (shown being connected to Fibre Channel port B in theoptional expansion adapter in slot 4 of the upper storage controller B).

Connecting a gateway to external storageYou must use fiber-optic cables to connect a gateway to external storage on aFibre Channel SAN.

See the Interoperability Matrix at the following web site for supported devicesfor your N6000 series system.


Refer to the documentation for your external storage for additionalinformation.

ControllerA

0d0c0b0a

0d0c0b0a

INOUTIN OUT PSU

INOUTIN OUT

PSU

n6hw018

ControllerB

Loop 1Disk EXN 1

Loop 2Disk EXN 1

Figure 6. Cabling expansion cards to storage expansion units for dual-path Fibre Channel cabling



Connecting to a third-party deviceYou can connect third-party devices to your system through an optical FibreChannel interface using any Fibre Channel port on the back of the chassis.

The N6000 series systems only support third-party devices with an opticalFibre Channel interface. See the Interoperability Matrix at the following website for supported devices for your N6000 series system.


Refer to the documentation that comes with the third-party device forconnection information.

Rules for connecting the third-party devicesObserve the following rules for connecting the third-party devices:v Use a fiber-optic cable that is:

– Appropriate to the Fibre Channel connection on your N6000 seriessystem

– Of an approved length for the third-party device

Note: See the documentation for the third-party device.v Check the Interoperability Matrix at the following web site to verify support

for your third-party device:www.ibm.com/storage/support/nas/An unsupported tape backup device might cause the system to halt.

v For additional information about Fibre Channel cables, see the followingweb site:www.ibm.com/storage/support/nas/

Connecting your system to an ASCII terminal console

The ASCII terminal console enables you to monitor the boot process, helpsyou configure your system after it boots, and enables you to perform systemadministration.

ASCII terminal console wiringThe following table lists the RJ-45 connection pinout for the ASCII terminalconsole wiring.

Table 16. RJ-45 connection pinout for the ASCII terminal wiring

Pin number Signal

1 Connected to pin 8

2 Not connected





Table 16. RJ-45 connection pinout for the ASCII terminal wiring (continued)

Pin number Signal

3 TXD (from system)

4 GND

5 GND

6 RXD (to system)

7 Not connected

8 Connected to pin 1

DB-9 to RJ-45 console adapter pin connectionsYou use the DB-9 to RJ-45 console adapter to connect the ASCII terminalconsole to your N6000 series system. Its purpose is to convert the RJ-45 pinouton the system to the DB-9 pinout, like those on other IBM products, and allPCs.

The following table lists the console adapter pin number connections betweenthe PC-style DB-9 male connector and the RJ-45 connection on your system.

Table 17. Console adapter pin number connections

RJ-45 Signal DB-9 male

1 [not connected]

2 [not connected]

3 (connected to pin 3 onDB-9)

TXD 3 (connected to pin 3 on RJ-45)


GND 5 (connected to pin 4 on RJ-45)

5 [not connected]


RXD 2 (connected to pin 6 on RJ-45)

7 [not connected] [not connected] 1

8 [not connected] [not connected] 4

[not connected] 6 through 9

Connecting to an ASCII terminal consoleTo connect an ASCII terminal console to the system, complete the followingsteps.1. Set the following communications parameters to the same values for both

the N series system and ASCII terminal.


Table 18. Communication parameters

Parameter Setting

Baud 9600

Data bit 8

Parity None

Stop bits 1

Flow control None

Note: See your terminal documentation for information about changingyour ASCII console terminal settings.

2. Connect the DB-9 null modem cable to the DB-9 to RJ-45 adapter cable,and then connect the RJ-45 end to the console port on the system and theother end to the ASCII terminal.


Chapter 3. Configuring an N6000 series system

This chapter describes how to configure an N6000 series system in thefollowing topics:v “Configuring the N6000 series system”v “Configuring the Fibre Channel port” on page 27

Configuring the N6000 series system

Gather and record information about each N6000 series system node in“System setup information worksheet.”

For information about how to boot your filer for the first time, refer to theInstallation and Setup Instructions that came with your system.

For gateway systems, initial startup and configuration tasks must beperformed by IBM. For additional information about gateway systems, see thedocumentation listed in Appendix E, “IBM System Storage N seriesdocumentation,” on page 115.

System setup information worksheetThis worksheet is a planning aid for setting up either a stand-alone system oran active/active or high availability configuration. The entries in thisworksheet are based on the typical questions you encounter while runningsetup. You might encounter slightly different questions, depending on youranswers to some questions and also which version of Data ONTAP yoursystem is running. To use this worksheet, complete the following steps:1. Copy this form; make one copy for each node in your system.2. Gather the appropriate information for your system and fill in the blanks

with the data for the node. You may not need all rows or columns in thisform.

3. Rack and cable your system, as described in the documentationaccompanying your system.

4. Run the setup script. The script automatically loads and runs when youfirst apply power to your system. Use the data you collected in thisworksheet to complete the initial setup process.


Table 19. N series system setup worksheet

Hostname:

Network Configuration Information e0a e0b e0c e0d e0e e0f

Virtual interfaces: [Y/N]

IP addresses: First 3 #s______._____._____

Netmask: First 3 #s ______._____._____

Should interface e0a/e0b take overpartner IP address during failover?[Y/N] (N3600/N3300)

N/A N/A N/A N/A

Media type/speed (100tx-fd, 100tx, auto[100/1000])

Flow control (none, receive, send, full):

Enable jumbo frames?

Complete setup through the web interface?[Y/N]

Default gateway IP address/name:

IP address or name of administration host:(Leave blank for root access to /etc fromany NFS client)

Timezone (name of city or region in/etc/zoneinfo file) [EST5EDT]

Where is the N series system located? (Textstring)

Enter the root directory for the HTTP files[/vol/vol0/home/http]

Do you want to run DNS resolver? [Y/N]

DNS domain name (you can enter up to 3 nameservers)

IP address for DNS first nameserver

Do you want another nameserver? [Y/N]

IP address for alternate nameserver

Do you want another nameserver? [Y/N]

IP address for alternate nameserver

Do you want to run NIS client? [Y/N]

Remote system management (RLM, RM, or BMC):


Table 19. N series system setup worksheet (continued)

RLM:

Would you like to configure the RLMLAN interface? [y]

Would you like to enable DHCP on theRLM LAN interface? [y]

Please enter the name or IP address ofthe mail host:

BMC: (N3600/N3300)The Baseboard Management Controller (BMC) provides remote management capabilitiesincluding console redirection, logging, and power control. It also extends AutoSupport bysending down filer event alerts.

Would you like to configure the BMC?[Y/N]

Enable DHCP on the BMC LANinterface? [Y/N]

IP address for the BMC

Netmask for the BMC

IP address for the BMC Gateway

Gratuitous ARP interval for the BMC[10 second (max 60)]

The mail host is required by your system to enable BMC to sense AutoSupport messages when thefiler is down.

IP address or name of the mail host

IP address for the mail host

Note: You may use AutoSupport options to configure alert destinations.

Configuring the Fibre Channel port

Each system controller module provides four independent Fibre Channelports, identified as 0a, 0b, 0c and 0d. SFPs must be firmly seated in all fourports before connecting cables.

The Fibre Channel ports can operate in target or initiator mode. Fibre Channelports do not support mixed initiator/target mode. The default mode for theports is initiator mode. You do not need to configure the ports to use them ininitiator mode.

The Fibre Channel ports should be used in initiator mode to communicatewith tape backup devices, such as in a TapeSAN backup configuration.

Chapter 3. Configuring an N6000 series system 27

Fibre Channel ports on HBAs cannot be configured in target mode. They canonly be used in initiator mode.

N6000 series system active/active or high availability configurationsActive/active or high availability configurations must be cabled to switchesthat support public loop topology. To connect an N6000 series system to afabric topology that includes switches that only support point-to-pointtopology, such as McDATA Director class switches, you must connect theactive/active or high availability configuration to an edge switch and use thisswitch as a bridge to the fabric. For information about specific switch modelssupported and fabric configuration guidelines, see the IBM System Storage Nseries FCP and iSCSI Configuration Guide at the following web site:


Configuring for initiator modeTo configure the system back to initiator mode, complete the following steps.1. Set the specified onboard ports to operate in initiator mode by entering the

following command:fcadmin config -t initiator adapter

where adapter is the port number. You can specify more than one port.Example: The following example sets onboard ports 0c and 0d to initiatormode.fcadmin config -t initiator 0c 0d

2. Reboot the system by entering the following command:reboot

3. Verify that the Fibre Channel ports are online and configured in the correctstate for your configuration by entering the following command:fcadmin config

Example: The following output example shows two ports configured asFibre Channel targets and two ports configured as initiators.n6000a> fcadmin config

LocalAdapter Type State Status---------------------------------------------------

0a target CONFIGURED online0b target CONFIGURED online0c initiator CONFIGURED online0d initiator CONFIGURED online

For information on converting the onboard ports to target mode andconfiguring your SAN, see the IBM System Storage N series Data ONTAP BlockAccess Management Guide for your version of Data ONTAP.



Configuring and using the RLM

The following table provides a list of manuals for configuring and using theRLM. You can view the manuals at www.ibm.com/storage/nas.

Table 20. RLM configuration manuals

Manual Title Information Provided

Installation and Setup Instructions that camewith your system

Describes the system and RLM cabling.

IBM System Storage N series DiagnosticsGuide

Lists and describes the diagnostic tests fora new or existing RLM.

IBM System Storage N series Data ONTAPSystem Administration Guide for yourversion of Data ONTAP

Describes RLM configuration and use.

IBM System Storage N series PlatformMonitoring Guide

Lists RLM error messages and givescorrective action for the error.

Chapter 3. Configuring an N6000 series system 29


Chapter 4. Monitoring your system

For information about monitoring the LEDs for your N6000 series system andoptional adapter cards, refer to the IBM System Storage N series PlatformMonitoring Guide.


Chapter 5. Replacing N6000 series system devices

This chapter describes how to replace parts in your N6000 series system.

This chapter discusses the following topics:v “Shutting down a controller module” on page 34v “Opening the system” on page 35v “Closing the system” on page 37v “Replacing the controller module” on page 38v “Replacing the fan module” on page 48v “Replacing DIMMs” on page 51v “Replacing a PCIe card and riser” on page 55v “Replacing a power supply” on page 60v “Replacing an NVRAM battery” on page 62v “Replacing the Real-time Clock (RTC) battery” on page 67v “Installing or replacing a Remote LAN Module” on page 71v “Replacing a CompactFlash card in N6000 series systems” on page 78

Figure 7 shows the locations of components at the front of your N6000 seriessystem.

Figure 8 on page 34 shows the locations of components at the rear of yourN6000 series system.

n6hw011

Fan fault LEDCam handle withtab release

6 Fan modulesfor Active/Activeconfigurations

Controller Aactivity

3 Fan modulesfor single-controllerconfigurations

Controller Bactivity

Power

Fault

Figure 7. N6000 series system components - Front


Shutting down a controller module

To shut down a controller module (called a node in an active/active or highavailability configuration), complete the applicable procedure:

Shutting down a node in an active/active or high availability configuration1. Check the status of the target node by entering the following command at

the system console of either node:cf status

2. Take one of the following actions, depending on the result of the cfstatus command:v If clustering is enabled and neither node is in takeover mode, go to step

3.v If clustering is enabled and the partner node took over the target node,

go to “Opening the system” on page 35 if you plan to open the system.v If clustering is enabled and the target node took over the partner node,

correct the problem, run the cf giveback command from the target nodeconsole, and go back to 1.

3. Take over the target node by entering the following command from thepartner node’s console:partner> cf takeover

4. Go to “Opening the system” on page 35 when the takeover is complete ifyou plan to open the system.

Note: Leave the power supplies turned on.

Console port

Management port

2 Network ports

Fault status LED

4 OnboardFibre Channel ports

4 Expansionadapter slots

Controller module AThumbscrewand cam handle

Cam handle withtab release

2 Power supplieswith power andfault LEDs

Controller module B(for Active/Activeconfigurations only)

n6hw010

Figure 8. N6000 series system components - Rear


Shutting down a node in an single-controller configuration1. Enter the following command from the system console:

halt

2. Turn off the power supplies and unplug both power supplies from thepower source.

3. Check the NVRAM LEDs on the controller module (see Figure 17 on page64).If the LEDs are not flashing, go to “Opening the system” if you plan toopen the system.If the LEDs are flashing red, there is content in the NVRAM that has notbeen saved to disk. Reconnect the power supplies to the power source,reboot the controller module, and repeat steps 1 through 3. If repeatedattempts to cleanly shut down the controller module fail, be aware thatyou might lose any data that was not saved to disk.

4. Go to “Opening the system” if you plan to open the system.

Opening the system

Perform the following steps to open the N6000 series system, using Figure 9on page 36 and Figure 10 on page 37 for reference.1. Properly ground yourself.2. Loosen the thumbscrew on the controller module cam handle.3. Pull the controller module cam handle downward and slide the controller

module toward you until it stops.4. Unplug system cables from the controller module, as needed, and keep

track of where the cables were connected to the controller module. Leavethe cables in the cable clips of the cable management tray.

5. Grasp the cable management tray by the blue touch points on the arms,gently push one arm of the tray so that the arm slides off the retainingpin, and then lift the tray off the back of the controller module and set itaside.

6. Push in the controller module release tab on the left side of the controllermodule and slide the controller module out of the system. Release the tabafter you can slide the controller module. Make sure that you support thebottom of the controller module with your free hand.

Chapter 5. Replacing N6000 series system devices 35

Figure 9 shows a view of the exterior components of your N6000 seriessystem.

Folding handles

Fan module

Power supply

Controller module

n6hw013

Cable management tray

Figure 9. N6000 series exterior components


Figure 10 shows an exploded view of the components of your N6000 seriessystem.

Closing the system

1. Close the DIMM cover, and close the side panel if needed.2. Align the end of the controller module with the opening in the chassis.3. Gently push the controller module halfway into the chassis, recable the

controller module, and attach the cable management tray. Then push thecontroller module all the way into the chassis.

Note: For active/active or high availability configurations, recable thecontroller before seating it all the way into the chassis, since itreboots once fully seated.

RTC battery

CompactFlash cardRLM card

System memory DIMMs

NVRAMmemoryDIMM

Side panel

PCIe riserNVRAM LED

NVRAMbattery

NVRAMmemoryDIMM

DIMMcover

Controller modulerelease tab

NVRAM LED

Console,network andmanagementports

n6hw012

Controller system board

Figure 10. N6000 series system components - Exploded view


4. Firmly push up the cam handle to finish seating the controller module inthe system, and then push the cam handle to the closed position andtighten the thumbscrew beneath the cam handle.

5. Complete the boot process.If your system has a single controller module, plug in the power supplyand turn on the power.If your system is in an active/active or high availability configuration,wait a few seconds for the node to boot, then enter the followingcommand from the partner console:cf giveback

Replacing the controller module

The controller module field-replaceable unit (FRU) arrives without the PCIcards, PCI card riser, CompactFlash card, RLM module, nonvolatile RAM(NVRAM) DIMM, NVRAM battery, system memory DIMMs, and SFPmodules. You must remove these components from the old controller moduleand install them in the replacement controller module.

Note: To reduce the possibility of damage to the FRU parts, minimize thehandling of the parts by installing them into the new controller moduleas soon as you have removed them from the old controller module.

This section describes how to perform the following tasks:v “Removing the controller module”v “Installing the controller module” on page 41v “Installing the firmware” on page 44v “Reassigning disks” on page 44v “Testing the system” on page 46v “Rebooting the controller module” on page 46v “Completing the replacement process” on page 48

Removing the controller moduleThis section describes how to perform the following tasks:v “Shutting down the controller module” on page 39v “Removing the PCI card and riser” on page 40v “Removing the CompactFlash card” on page 40v “Removing the RLM module” on page 40v “Removing the NVRAM memory DIMM” on page 41v “Removing the system memory DIMMs” on page 41v “Removing the NVRAM battery” on page 41


Shutting down the controller module1. Shut down the target controller module (called a node in an active/active

or high availability configuration) by completing the applicable procedure:v Shutting down a node in an active/active or high availability

configuration

– If your system is in an active/active or high availability NASconfiguration, go to substep c.

– If your system is in an active/active or high availability SANconfiguration, complete substeps a and b, and then go to substep c.

a. Enter the following command from Node B to save Node A’sonboard Fibre Channel port configuration information: partnerfcadmin config

b. Copy and save the screen display to a safe location for the steps in“Restoring the onboard port configuration (active/active or highavailability SAN configurations only)” on page 47”.

Note: To perform this procedure, the partner node must be able totake over the target node. If this criteria cannot be met,contact technical support.

c. Check the status of the target node by entering the followingcommand at the system console of either node:cf status

d. Take one of the following actions, depending on the result of the cfstatus command:If clustering is enabled and neither node is in takeover mode, go tosubstep e.If clustering is enabled and the partner node took over the targetnode, go to step 2 on page 40.If clustering is enabled and the target node took over the partnernode, correct the problem, run the cf giveback command from thetarget node console, and go back to substep c.

e. Take over the target node by entering the following command fromthe partner node’s console:cf takeover

f. Go to step 2 on page 40 when the takeover is complete.v Shutting down a controller module in a single-controller configuration

a. Enter the following command from the system console:halt

b. Turn off the power supplies, unplug both power cords from thepower source, and then remove the power cords.


2. While grounded, remove the controller module, unplug the cables, andthen remove the cable management tray as described in “Opening thesystem” on page 35.

3. Check whether the NVRAM LEDs on the controller module are flashingred (see Figure 17 on page 64).Flashing red LEDs means there is content in the NVRAM that has notbeen saved to disk.v If your system is in an active/active or high availability configuration,

ignore the LEDs because content in the NVRAM was saved through thetakeover process.

v If your system is in a single-controller module configuration, complete thefollowing substeps:a. Reconnect the power supplies to the power source.b. Reboot the controller module.

Repeat substeps 6a on page 39 and 6b on page 39 from "Shuttingdown a controller module in a single-controller configuration", andthen repeat step 2.

4. If you left the SFP modules in the system after removing the cables, movethem to the new controller module.

5. Go to “Removing the PCI card and riser.”

Removing the PCI card and riser1. While grounded, loosen the thumbscrew on the controller module side

panel.2. Swing the side panel open until it comes off the controller module.3. Remove the PCI card or cards.4. Loosen the PCI card riser thumbscrew and pull the riser up and out of the

sockets.5. Replace the controller module side panel and tighten the thumbscrew.6. Go to “Removing the CompactFlash card.”

Removing the CompactFlash card1. Locate the CompactFlash card using the CF Card label on the controller

module DIMM cover as a reference.2. Pull the card up and out of the socket.3. Go to “Removing the RLM module.”

Removing the RLM module1. Locate the RLM using the RLM label on the controller module DIMM

cover as a reference.


2. Pinch the retaining tabs on the RLM, and then lift the RLM straight out ofthe socket and housing.

3. Go to “Removing the NVRAM memory DIMM.”

Removing the NVRAM memory DIMM1. Locate the NVRAM memory DIMM using the NVRAM Memory label on

the controller module as a reference.2. Note the orientation of the DIMM in the socket so that you can insert the

DIMM correctly in the new controller module.3. Push apart the latches on either side of the DIMM to release the DIMM

from its slot, and then lift it out of the slot.4. Go to “Removing the system memory DIMMs.”

Removing the system memory DIMMs1. Locate the system memory DIMMs under the controller module DIMM

cover.2. Note the locations and orientation of the DIMMs in the sockets so that you

can insert the DIMMs correctly in the new controller module.3. Push apart the latches on either side of the DIMM to release the DIMM

from its slot, and then lift it out of the slot.4. Repeat step 2 for each DIMM.5. Go to “Removing the NVRAM battery.”

Removing the NVRAM battery1. Locate the NVRAM battery using the label on the battery cover as a

reference.2. Loosen the two thumbscrews on the battery cover.

You might need to push down on the cover with one hand to loosen thethumbscrews.

3. Swing the cover up and away from the battery.4. Lift the battery out of the socket and housing.5. Go to “Installing the controller module.”

Installing the controller moduleThis section describes how to perform the following tasks:v “Installing the CompactFlash card” on page 42v “Installing the riser and PCI card” on page 42v “Installing the RLM module” on page 42v “Installing the NVRAM and system memory DIMMs” on page 42v “Installing the NVRAM battery” on page 43


Installing the CompactFlash card1. While grounded, position the CompactFlash card by aligning the card with

the edges of the card socket in the new controller module.The lip on the top of the card should point in the direction shown in theCF Card label on the controller module DIMM cover.

2. Seat the card by pushing it into the socket.The card should be squarely seated and should not move. Reseat the card,if necessary.

Note: The CompactFlash socket is keyed. If you feel resistance whilepushing the card into the socket, check the orientation of the card.

3. Go to “Installing the riser and PCI card.”

Installing the riser and PCI card1. Loosen the thumbscrew on the new controller module’s side panel.2. Swing the side panel open until it comes off the controller module.3. Align the riser with the guide slots on the chassis, and then firmly push

down until the riser is in place.4. Examine the riser to make sure that it is seated squarely and completely in

the socket.If it is not seated squarely, repeat step 3.

5. Tighten the riser thumbscrew.6. Reinstall the PCI card by properly aligning the card in the slot and

exerting even pressure on the card when seating it in the socket.7. Repeat step 6 if you are installing additional PCI cards.8. Reattach the controller module side panel, close it, and then tighten the

thumbscrew.9. Go to “Installing the RLM module.”

Installing the RLM module1. Align the edges of the RLM with the guide slots on the edges of the

housing, lower the RLM into place in the housing, and then press it intothe socket by using your thumb in the top center of the RLM. Make surethe retaining tabs lock firmly in place.

2. Go to “Installing the NVRAM and system memory DIMMs.”

Installing the NVRAM and system memory DIMMs1. Identify the NVRAM memory DIMM slot using the NVRAM Memory

label on the controller module as a reference.2. Hold the DIMM by the corners and align it over the slot.

The voltage notch among the pins on the DIMM should line up with thetab in the socket.


3. Insert the DIMM straight into the slot.The DIMM fits tightly in the slot, but should go in easily. If not, realignthe DIMM with the slot and reinsert it.Attention: Visually inspect the DIMM to verify that it is evenly alignedand fully inserted into the slot. The edge connector on the DIMM mustmake complete contact with the slot.

4. Push carefully, but firmly, on the top edge of the DIMM until the latchessnap into place over the notches at the ends of the DIMM.

5. Identify the system memory DIMM slots using the DIMM label on thecontroller module DIMM cover as a reference.

6. Repeat steps 2 on page 42 through 4 to install the system memory DIMMs.7. Go to “Installing the NVRAM battery.”

Installing the NVRAM battery1. Locate the NVRAM battery using the label on the battery cover as a

reference.2. Loosen the two thumbscrews on the battery cover.

You might need to push down on the cover with one hand to loosen thethumbscrews.

3. Swing the cover up and away from the battery.4. Align the battery socket with the edge connector in the floor of the

housing.5. Seat the battery.6. Close the battery cover and tighten the thumbscrews.

You might need to push down on the cover with one hand to tighten thethumbscrews.

7. Go to “Closing the system.”

Closing the system1. Reinstall the controller module by completing the following steps:

Attention: For active/active or high availability configurations, thesequence in which you reinstall the controller module is important becauseit attempts to reboot as soon as you completely seat it in the chassis.a. Gently push the controller module halfway into the chassis.b. Recable the controller module and PCI cards that you removed at the

beginning of the procedure.c. Attach the cable management tray.d. Push the controller module all the way into the chassis.

Note: If you are recabling a gateway system, see the GatewayInstallation Requirements and Reference Guide.


2. Go to “Installing the firmware.”

Installing the firmware1. Select the most current version of firmware for your system from those

listed at www.ibm.com/storage/support/nas/ and then follow theinstructions for downloading and installing the new firmware.

Note: Installing a new controller module changes the World Wide PortName (WWPN) and World Wide Node Name (WWNN) valuesassociated with each onboard Fibre Channel port. If yourconfiguration uses switched-based zoning, you must adjust theswitch zoning to reflect the new WWPN and WWNN values. Ifyour configuration includes a gateway system, you must also adjustthe WWPN values in the host or volume groups associated witharrays on the storage subsystem.

2. Go to “Reassigning disks.”

Reassigning disksAttention: This information does not apply to EXN3000 storage expansionunits, which use software-based disk ownership. For more information, seethe description of software-based disk ownership, as well as the "General cablingrules for SAS and ACP" section, in the IBM System Storage EXN3000 StorageExpansion Unit Hardware and Service Guide.

Reassign disks to the failed node, by completing the following steps foractive/active or high availability and single-controller module configurations:1. Power on to reboot the system.2. Press Ctrl-C to interrupt the boot process and go to the Special Boot

menu when you see the following message:Press Ctrl-C for the special boot menu

Note: If your system has the AUTOBOOT option set to False, the systemstops at the boot prompt and you must enter boot_ontap to bootthe system, then press Ctrl-C to interrupt.

3. On the failed node, select Maintenance Mode from the Special Bootmenu.

4. On the failed node, view the old and new system IDs by entering thefollowing command:disk show -v

The new ID is listed in the output after Local System ID. The old ID islisted in parentheses following the host name.

Note: Make note of the new system ID at the very beginning of theoutput.



5. Reassign the disks to the new controller module based on your system’sconfiguration.Attention: For an active/active or high availability configuration, thefollowing commands must be entered from the partner node’s console.v If the controller module is a node in an active/active or high availability

configuration, complete the following substeps on the partner node:a. On the partner node, enter the following command to enter

advanced privilege mode:priv set advanced

b. On the partner node, reassign disk ownership for filer systems (orLUN ownership for gateway systems), using the system IDinformation obtained from the disk show -v command:disk reassign -s <old_system_ID> -d <new_system_ID>

v If the controller module is part of a single-controller module configuration,enter the following command at the Maintenance mode prompt:disk reassign -s <old_system_ID> -d <new system ID>

6. On the partner node, verify that the disks (or gateway LUNs) wereassigned correctly by entering the following command:disk show -v

Disks are shown as assigned to the system and should show the newsystem ID for the failed node. If your system is in an active/active orhigh availability configuration, disk ownership must be shown as thesame for both nodes.

7. On the failed node, check the status of your disk aggregates and volumesby entering the following command:aggr status

8. On the failed node, halt the system to leave Maintenance Mode andreturn to the boot prompt.halt

9. On the failed node, boot the operating system with the followingcommand. For active/active or high availability configurations, this putsthe node in Waiting for Giveback state.boot_ontap

10. If the controller module is part of a single-controller moduleconfiguration, go to step 13 on page 46.

11. On the partner node, enter the following command to return to standardprivilege mode:priv set admin

12. On the partner node, give back the failed node with the followingcommand:


cf giveback -f

13. Go to “Testing the system.”

Testing the systemAfter you update the controller module firmware, you should run diagnosticson the controller module and controller module FRUs. If the system passesthe diagnostic tests, boot the system and bring it back online.1. Enter the following command to stop the system and bring up the boot

loader prompt:halt

2. Enter the following command at the boot loader prompt to enterdiagnostics:boot_diags

3. Enter the following command at the main diagnostics prompt to beginthe diagnostics tests on the new controller module:run mb

4. Enter the following command at the prompt:config

5. Confirm that the output shows all adapters plugged into the PCI riser aredetected.

6. Enter the following command at the prompt to access the memory menu:mem

7. Confirm that the total memory output is consistent with expectations.8. If the RLM is connected, go to the Agent menu to run the RLM-Agent

interface test.9. Enter the following command at the prompt to exit diagnostics:

exit

10. Go to “Rebooting the controller module.”

Rebooting the controller module1. Boot your system.

If your system is in an active/active or high availability SANconfiguration, go to “Restoring the onboard port configuration(active/active or high availability SAN configurations only)” on page 47.If your system is in an active/active or high availability NAS or iSCSIconfiguration, complete the following substeps:a. Enter the following command:

boot_ontap

The message Waiting for Giveback is displayed during the bootprocess.


b. Complete the boot process by entering the following command fromthe partner node console:cf giveback

Results:

The target node reboots and functions normally. A successful givebackends with the following message on the partner node:giveback completed

Note: If Waiting for Giveback is not displayed prior to giveback,reboot the controller module. If this continues, contact technicalsupport.

c. Display the date and time on the partner node and set the target nodeto the same date and time.

If your system is in a single-controller module configuration, go to 2 afterbooting is complete.

2. Go to “Completing the replacement process” on page 48.

Restoring the onboard port configuration (active/active or highavailability SAN configurations only)When you replace the controller module of a system in an active/active orhigh availability configuration, the failed controller module is shut down andthe partner controller module takes over. If your configuration is FCP-licensedand cabled to a Fibre Channel fabric, you must restore the configuration ofthe onboard Fibre Channel ports before you perform the first giveback;otherwise, you might experience a disruption in service.

The onboard Fibre Channel ports on a replacement controller module are notpreconfigured. If you do not configure the onboard Fibre Channel ports beforethe first giveback, Data ONTAP restores the original onboard Fibre Channelport configuration and then automatically reboots the controller moduleduring the giveback. SAN hosts that are failing back to the replaced controllermodule might lose access to their LUNs during the reboot.

Note: See the na_fcadmin(1) man page for more information about FibreChannel port configuration.

1. Boot the controller module by entering the following command:boot_ontap

2. Press Ctrl-C to interrupt the boot process.3. From the boot menu, select Maintenance mode boot.4. Program the onboard ports with the information you obtained in

“Shutting down the controller module” on page 39 by entering thefollowing commands:v Set ports to Target mode: fcadmin config -t target adapter_name ...


v Set ports to Initiator mode: fcadmin config -t initiatoradapter_name ...

v Set ports to the unconfigured state: fcadmin config -t unconfigadapter_name ...

adapter_name is the port number (for example, 0c). You can specify morethan one port.

5. Recable the target and initiator ports.v Connect the target ports to the Fibre Channel fabric.v Connect initiator ports to the local and partner disk shelves and/or the

TapeSAN fabric.6. Exit Maintenance mode by entering the following command:

halt

7. Reboot the controller module by entering the following command:boot_ontap

8. After the controller module reboots, perform the giveback by entering thefollowing command on the console of the takeover (partner) controllermodule:cf giveback

9. Display the date and time on the partner node and set the target node tothe same date and time.

10. Go to “Completing the replacement process.”

Completing the replacement processReturn the failed part to IBM. Contact IBM Service and Support at1-800-IBM-SERV (1-800-426-7378) for more information on the returnprocedure.

Replacing the fan module

Attention: A fan must be replaced within two minutes of removal or thesystem shuts down. Have the replacement fan module ready for insertion.

This section describes the following tasks:v “Removing a fan module”v “Installing the replacement fan module” on page 50v “Completing the replacement process” on page 51

Removing a fan module1. While grounded, remove the bezel (if necessary) with two hands, by

grasping the openings on each side of the bezel, and then pulling ittoward you until the bezel releases from the four ball studs on the chassisframe.


2. Identify the fan module that you must replace by checking the consoleerror messages and looking at the Status LED on each fan module camhandle.A failed fan LED is solid amber, indicating that the fan has failed or nopower is reaching the fan module.

3. Press down the release latch on the fan module cam handle and pull thecam handle downward.The fan module moves a little bit away from the chassis.

4. Pull the fan module straight out from the chassis, making sure that yousupport it with your free hand, so that it does not swing out of thechassis.Attention: The fan modules are short. Always support the bottom of themodule with your free hand so that it does not suddenly drop free fromthe chassis and injure you.Attention: You must replace the fan within two minutes of removing itfrom the chassis. System airflow is disrupted and the controller moduleshuts down after two minutes to avoid overheating. In active/active orhigh availability configurations, a take-over occurs.

5. Set the fan module aside.


Installing the replacement fan module1. While grounded, remove the bezel, if necessary.2. Insert the replacement fan module into the chassis by aligning it with the

opening and sliding it into the chassis.3. Push firmly on the fan module housing to ensure that it is seated all the

way into the chassis.4. Push the cam handle up, to its closed position, making sure that the cam

handle release latch clicks into the locked position.5. Reinstall the bezel by aligning it with the four ball studs on the chassis

frame, and then firmly pushing the bezel onto the ball studs.6. Run diagnostics on the replacement fan module during the next scheduled

system downtime.

See the IBM System Storage N series Diagnostics Guide for more information.

n6hw003

Fan module

Cam handlerelease latch

Fan LEDFan camhandle

Figure 11. Fan module



Replacing DIMMs

This section describes how to perform the following tasks:v “Removing a DIMM”v “Installing a DIMM” on page 54v “Completing the replacement process” on page 55

Removing a DIMM1. Shut down the target controller module (called a node in an active/active

or high availability configuration) by completing the applicable procedure:v To shut down a node in an active/active or high availability

configuration

a. Check the status of the target node by entering the followingcommand at the system console of either node:cf status

b. Take one of the following actions, depending on the result of the cfstatus command:– If clustering is enabled and neither node is in takeover mode, go

to substep 1c.– If clustering is enabled and the partner node took over the target

node, go to step 2.– If clustering is enabled and the target node took over the partner

node, correct the problem, run the cf giveback command fromthe target node console, and go back to substep 1a.

c. Take over the target node by entering the following command fromthe partner node’s console:cf takeover

d. Go to step 2 when the takeover is complete.v To shut down a controller module in a single-controller configuration





3. Check whether the NVRAM LEDs on the controller module are flashingred (see Figure 17 on page 64).Flashing red LEDs means there is content in the NVRAM that has notbeen saved to disk.If your system is in an active/active or high availability configuration,ignore the LEDs because content in the NVRAM was saved through thetakeover process.If your system is in a single-controller module configuration, complete thefollowing substeps:a. Reconnect the power supplies to the power source.b. Reboot the controller module.c. Repeat the substeps for "To shut down a controller module in a

single-controller configuration" on page 51, and then repeat step 2 onpage 51.

Note: If repeated attempts to cleanly shut down the controller module fail,be aware that you might lose any data that was not saved to disk.

4. Open the DIMM cover in the controller module.5. Locate the DIMM that you want to remove.

Note: Each system memory DIMM has an LED located on the board nextto each DIMM slot. The LED is illuminated if the DIMM needs tobe replaced.

Attention: You must replace the same number of DIMMs as you receivein your replacement package.If you are replacing DIMMs on an N6070 system, see Figure 12 on page 53.


If you are replacing DIMMs on an N6040 system, see Figure 13.

6. Note the orientation of the DIMM in the socket so that you can insert thereplacement DIMM in the proper orientation.

7. Push apart the latches on either side of the DIMM to release the DIMMfrom its slot, and then lift it out of the slot.

System memory DIMMs

NVRAM LED

NVRAM memory DIMMNVRAM LED

n6hw008

Figure 12. Replacing DIMMs on an N6070 system

System memory DIMMsNVRAM LED


n6hw009

Figure 13. Replacing DIMMs on an N6040 system


8. Repeat step 5 on page 52 through step 7 on page 53 to remove additionalDIMMs as needed.

9. Go to “Installing a DIMM.”

Installing a DIMM1. Locate the slot where you are installing the new DIMM.2. While grounded, remove the replacement DIMM from the antistatic

shipping bag, hold the DIMM by the corners, and align it over the slot.The voltage notch among the pins on the DIMM should line up with thetab in the socket.

3. Insert the DIMM straight into the slot.The DIMM fits tightly in the slot, but should go in easily. If not, realignthe DIMM with the slot and reinsert it.

Note: Visually inspect the DIMM to verify that it is evenly aligned andfully inserted into the slot. The edge connector on the DIMM mustmake complete contact with the slot.

4. Push carefully, but firmly, on the top edge of the DIMM until the latchessnap into place over the notches at the ends of the DIMM.

5. Repeat steps 1 through 4 to install additional DIMMs as needed.6. Close the DIMM cover.7. Reinstall the controller module by completing the following steps:

Attention: For active/active or high availability configurations, thesequence in which you reinstall the controller module is important becauseit attempts to reboot as soon as you completely seat it in the chassis.a. Gently push the controller module halfway into the chassis.

n50hw031

Voltage notch

Figure 14. Lifting the DIMM from the slot


b. Recable the controller module and PCI cards that you removed at thebeginning of the procedure.

c. Attach the cable management tray.d. Push the controller module all the way into the chassis.

Note: If you are recabling a gateway system, see the Gateway InstallationRequirements and Reference Guide.

8. Boot the system.9. To run diagnostics on your DIMM, complete the following substeps. If you

do not want to run diagnostics, go to “Completing the replacementprocess.”a. Stop the boot process before LOADER completes loading, and enter

boot_diags at the boot loader prompt.b. Enter the following command at the main diagnostics prompt to enter

the memory menu:mem

c. Confirm that the total memory output is consistent with expectations.d. Run the Comprehensive memory tests: option 1.e. After you complete the tests, exit diagnostics.f. Enter the following command at the prompt to boot the system:

boot_ontap

Attention: If your system is in an active/active or high availabilityconfiguration, use the cf giveback command from the partner node’sconsole to enable your active/active or high availability configuration.

g. Go to “Completing the replacement process.”


Replacing a PCIe card and riser

This section describes how to perform the following tasks:v “Removing a PCIe card” on page 56v “Installing a PCIe card” on page 57v “Removing a riser” on page 59v “Installing a riser” on page 59v “Completing the replacement process” on page 60


Removing a PCIe card

Note: This procedure is written with the assumption that all othercomponents of the system are functioning properly. If your system doesnot meet this criteria, contact technical support.

1. Shut down the target controller module (called a node in an active/activeor high availability configuration) by completing the applicable procedure:v Shutting down a node in an active/active or high availability

configuration







d. Go to step 2 when the takeover is complete.v Shutting down a controller module in a single-controller configuration







v If your system is in a single-controller module configuration, completethe following substeps:a. Reconnect the power supplies to the power source.b. Reboot the controller module.c. Repeat substeps a and b from step 1 of "Shutting Down a Controller

Module in a Single-Controller Configuration," and then repeat step 2.


4. Remove the failing PCIe card by completing the following substeps, usingthe PCIe card label on the controller DIMM cover for reference:a. Loosen the thumbscrew on the controller module side panel.b. Swing the side panel open until it comes off the controller module.c. Remove the PCIe card from the controller module and set it aside.d. Go to “Installing a PCIe card.”

Installing a PCIe card1. While grounded, shut down the system, and remove the controller module

from the chassis, if necessary, as described in “Shutting down a controllermodule” on page 34 and “Opening the system” on page 35.

Riser

PCIe card n6hw002

Figure 15. Replacing a PCIe card and riser


2. Open the controller module side panel. If you are adding a new PCIe card,remove the slot cover. Install the PCIe card.Be sure that you properly align the card in the slot and exert evenpressure on the card when seating it in the socket.

3. Close the side panel and tighten the thumbscrew.4. Reinstall the controller module by completing the following steps:




5. Cable the PCIe card as needed.Attention: If your system is in an active/active or high availabilityconfiguration, seat the controller module in the chassis, then go to step 6.

6. Boot the system by entering the following command:boot_ontap

7. To run diagnostics on your PCI card, complete the following substeps. Ifyou do not want to run diagnostics, go to step 8 on page 59.a. Stop the boot process before LOADER completes loading and enter

boot_diags at the boot loader prompt.b. Enter the following command at the main diagnostics prompt:

config

c. Confirm that the output shows that all the installed adapters aredetected.

d. Enter the test menu for the adapter type that you replaced, and thenrun the Comprehensive tests menu option.

e. Correct any errors, and then exit diagnostics.f. Boot the system by entering the following command:

boot_ontap

Attention: If your system is an active/active or high availabilityconfiguration, use the cf giveback command from the partner node’sconsole to enable your active/active or high availability configuration.


8. Check the functioning of the new card by completing the followingsubsteps:a. Look for the card in the system configuration tables on the controller

module.b. Check that the card LEDs report traffic or network connections.c. Make corrections as needed.


Removing a riser1. While grounded, remove the controller module, as described in “Opening

the system” on page 35.2. Remove any applicable PCIe cards from the riser, as described in

“Removing a PCIe card” on page 56.3. Using the PCIe card label on the controller DIMM cover for reference,

loosen the riser thumbscrew, and then pull the riser up and out of thesockets.

4. Go to “Installing a riser.”

Installing a riser1. While grounded, align the riser with the guide slots on the chassis, and

then firmly push down until the riser is in place.2. Examine the riser to make sure that it is seated squarely and completely in

the sockets.If it is not seated squarely, repeat step 1 to reinstall it.

3. Tighten the riser thumbscrew.4. Open the controller side panel, if necessary, to reinstall the PCIe cards, and

then close the side panel and tighten the thumbscrew.5. Reinstall the controller module by completing the following steps:




6. Boot the system by entering the following command:boot_ontap


7. To run diagnostics on any of the reinstalled PCI cards, complete thefollowing substeps. If you do not want to run diagnostics, go to step 8.a. Stop the boot process before LOADER completes loading and enter

boot_diags at the boot loader prompt.b. Enter the following command at the main diagnostics prompt:

config

c. Confirm that the output shows that all the installed adapters aredetected.

d. Enter the test menu for the adapter type that you replaced, and thenrun the Comprehensive tests menu option.

e. Correct any errors, and then exit diagnostics.f. Boot the system by entering the following command:

boot_ontap




Replacing a power supply

This section describes the following tasks:v “Removing a power supply”v “Installing a power supply” on page 61v “Completing the replacement process” on page 62

This procedure is written with the following assumptions:v You are replacing only one power supply at a time. This prevents system

downtime.v All other components in the system are functioning properly.

If your system does not meet these criteria, contact IBM technical support.

Removing a power supply1. Make sure that you are properly grounded, then turn off the target power

supply.2. Remove the power cord by completing the following substeps:


a. Pinch the tab on the locking mechanism of the cable retainer clip, andopen the retainer clip.

b. Slide the retainer clip off the cable.c. Unplug the power cords from the power source, and then remove the

power cords.3. Press down the release latch on the power supply cam handle, lower the

cam handle to the fully open position, and then slide the power supplyout of the chassis.Make sure that you support the power supply with your free hand.Attention: You must replace the power supply within 60 minutes ofremoving it from the chassis.

Installing a power supply1. Make sure the on/off switch of the new power supply is in the Off

position.

Power cordlockingmechanism

Camhandle

LEDs

Cam handlerelease latch

Power supply

n6hw001

Figure 16. Replacing a power supply


2. Align the edges of the new power supply with the opening in the systemchassis and gently push the power supply into the chassis until it isalmost flush with the back of the system.

3. Push on the edges of the power supply to seat it all the way into thechassis, and then push the cam handle up to the closed position to seat thepower supply, making sure that the cam handle release latch clicks into itslocked position.

4. Reconnect the power cord and secure it to the power supply using thecable retaining clip.

5. Reconnect the power supply to the power source, and then turn it on.The power supply should run with no fault LEDs lit.



Replacing an NVRAM battery

This section describes how to perform the following tasks:v “Removing the NVRAM battery”v “Installing the NVRAM battery” on page 65v “Completing the replacement process” on page 67

Removing the NVRAM battery1. Shut down the target controller module (called a node in an active/active


configuration



to substep 1c on page 63.– If clustering is enabled and the partner node took over the target

node, go to step 2 on page 63.– If clustering is enabled and the target node took over the partner










v If your system is in a single-controller module configuration, completethe following substeps:a. Reconnect the power supplies to the power source.b. Reboot the controller module.c. Repeat substeps 1a on page 62 and 1b on page 62, and then repeat

step 2.

Note: If repeated attempts to cleanly shut down the controller modulefail, be aware that you might lose any data that was not saved todisk.


4. Remove the NVRAM battery by completing the following substeps andusing the label on the battery cover for reference:a. Loosen the two thumbscrews on the battery cover.

You might need to push down on the cover with one hand to loosenthe thumbscrews.

b. Swing the cover up and away from the battery.c. Lift the battery out of the floor of the housing, as shown in the

following figure.

System memory DIMMs

NVRAM LED


n6hw008

Figure 17. NVRAM locations


Installing the NVRAM battery1. Align the battery socket with the edge connector in the floor of the

housing.2. Seat the battery.3. Close the battery cover and tighten the thumbscrews.

You might need to push down on the cover with one hand to tighten thethumbscrews.

4. Reinstall the controller module by completing the following steps:Attention: For active/active or high availability configurations, thesequence in which you reinstall the controller module is important becauseit attempts to reboot as soon as you completely seat it in the chassis.a. Gently push the controller module halfway into the chassis.b. Recable the controller module and PCI cards that you removed at the

beginning of the procedure.

n6hw007

Figure 18. NVRAM battery removal


c. Attach the cable management tray.d. Push the controller module all the way into the chassis. Close the cam

handle and tighten the thumbscrew.Attention: An active/active or high availability configurationattempts to boot as soon as you completely seat it in the chassis. Whenyou receive the message Waiting for giveback, enter the cf givebackcommand from the partner node’s console to enable your active/activeor high availability configuration.

Note: If you are recabling a gateway system, see the Gateway InstallationRequirements and Reference Guide.

5. An active/active or high availability configuration attempts to boot assoon as you completely seat it in the chassis.For a single-controller configuration, boot the system by entering thefollowing command:boot_ontap

Note: Data ONTAP checks the battery charge during system boot. If thebattery is not charged enough to hold the NVRAM contents for asufficient period, the boot process is stopped until the battery isproperly recharged. The system also prints an error message andgives an override command on the console screen.

6. Check the status of the NVRAM battery from the system commandprompt on the console by entering the following command:environ chassis NVRAM7-battery-0 print

Result:

The output display shows the following information. The state is shown asnormal when the battery is good and fully charged.Sensor name: NVRAM7-battery-0

type: voltage

owner: NVRAM7-0

phys_id: 1

state: normal

curr_reading: 3924mV

crit.low: 3499mV

warn.low: 3699mV

warn.high: 4250mV

crit.high: 4250mV

Note: The displayed field’s values can change without notice. All fieldswill be present and have values.


If the command fails or the state is not normal, reinstall the battery andcheck the status again.If you want to run diagnostics on the NVRAM battery, continue with thenext step.

7. To run diagnostics on the NVRAM battery, complete the followingsubsteps. If you do not want to run diagnostics, go to “Completing thereplacement process.”a. Halt the controller to the LOADER prompt by entering the command:

halt. Enter boot_diags from the LOADER prompt.b. Enter the following command at the main diagnostics prompt:

mb.c. Select option 6, On-board NVRAM Test.d. Select option 5, the NVRAM Environmental menu.e. Select the third test, NVRAM Battery Test.f. After you complete the tests, exit diagnostics by selecting 99 until the

prompt Enter Diag, Command or Option is displayed. Then enter theexit command.

g. Enter the following command at the LOADER prompt to boot thesystem:boot_ontap


h. Go to “Completing the replacement process.”


Battery disposalDispose of batteries according to local regulations regarding battery recyclingor disposal. For more information, see the IBM Environmental Notices and UserGuide, Z125-5823.

Replacing the Real-time Clock (RTC) battery

This section describes how to perform the following tasks:v “Removing the RTC battery” on page 68v “Installing the RTC battery” on page 69v “Resetting the date and time on the controller module” on page 70v “Completing the replacement process” on page 71


Removing the RTC battery1. Shut down the target controller module (called a node in an active/active


configuration:


b. Take one of the following actions, depending on the result of the cfstatus command:If clustering is enabled and neither node is in takeover mode, go tosubstep c.If clustering is enabled and the partner node took over the targetnode, go to step 2.If clustering is enabled and the target node took over the partnernode, correct the problem, run the cf giveback command from thetarget node console, and go back to substep 1a.

c. Take over the target node by entering the following command fromthe partner node’s console:partner> cf takeover



Turn off the power supplies, unplug the power cords from thepower source, and remove the power cords.

b. Check the NVRAM LEDs on the controller module (see Figure 17 onpage 64).If the LED is not flashing, go to step 2.If the LEDs are flashing red, there is content in the NVRAM that hasnot been saved to disk. Reconnect the power supplies to the powersource, reboot the controller module, and repeat substeps 4a and 4b.If repeated attempts to cleanly shut down the controller module fail,be aware that you might lose any data that was not saved to disk,and go to step 2.

2. While grounded, remove the controller module, as described in “Openingthe system” on page 35.

3. Locate the RTC battery at the right-rear of the controller module. See the’RTC Battery’ illustration on the controller module DIMM cover.It is the coin cell battery in the vertical holder near the CompactFlash card.


4. Remove the RTC battery by completing the following substeps, using theillustration for reference:

a. With your fingernail, gently pry the retaining clip away from the topedge of the battery.Attention: Do not pry the clip too much; the clip bends if you use toomuch force.

b. Grasp the sides of the battery with your thumb and forefinger, lift thebattery out of the holder, and set it aside.

c. Go to “Installing the RTC battery.”

Installing the RTC battery1. While grounded, remove the replacement battery from the antistatic

shipping bag.2. Locate the empty battery holder on the controller module and insert the

battery into the holder.3. Visually inspect the battery to make sure that it is completely installed into

the holder and that the polarity is correct.See the RTC Battery illustration on the controller module DIMM cover forbattery polarity. There is also a large “+” on the controller moduleindicating battery polarity.

4. Reinstall the controller module or node partially into the system chassis,and then recable and close it as described in “Closing the system” on page37.

n6hw005

Figure 19. RTC battery removal


Attention: The node attempts to boot in an active/active or highavailability configuration or when you apply power to a stand-alonesystem. The system detects the incorrect date and time and halts thesystem at the boot loader prompt.

5. Go to “Resetting the date and time on the controller module.”

Resetting the date and time on the controller moduleYou must reset the date and time on the controller module or node afterreplacing the RTC battery and rebooting Data ONTAP.1. If you want to run diagnostics, complete the following substeps:

a. Halt the controller to the LOADER prompt by entering the haltcommand.

b. Enter boot_diags from the boot loader prompt.c. Select and complete the appropriate tests.

See the IBM System Storage N series Diagnostics Guide for informationabout specific diagnostics tests you can perform.

d. Exit diagnostics and then continue with the next step.

If you do not want to run diagnostics, continue with the next step.

2. Boot the controller module by entering the boot_ontap command at theboot loader prompt:Attention: For an active/active or high availability configuration, whenyou receive the message Waiting for giveback, enter the cf givebackcommand from the partner node’s console to enable your active/active orhigh availability configuration.

3. Display the current date on the controller module or node by entering thefollowing command:date

Attention: If your system is in an active/active or high availabilityconfiguration, make sure that both nodes are set to the same date and timeby displaying the date and time on the partner node and setting the targetnode to those values.

4. Set the date by entering the following command:date [-u] [[[CC]yy]mmddhhmm>[.<ss>]]

-u sets the date and time to Greenwich Mean Time instead of the localtime.CC is the first two digits of the current year.yy is the second two digits of the current year.mm is the current month. If you omit the month, the default is the currentmonth.dd is the current day. If you omit the day, the default is the current day.hh is the current hour, using a 24-hour clock.


mm is the current minute.ss is the current second. If you omit the seconds, the default is 0.Example:

The following command sets the date and time to 22 May 2007 at 9:25 a.m.date 200705220925

5. Boot the controller module by entering the following command at the bootloader prompt: boot_ontapIf you want to run diagnostics, complete the following substeps:

a. Halt the controller to the LOADER prompt by entering the haltcommand.

b. Enter boot_diags from the boot loader prompt.c. Select and complete the appropriate tests.

See the IBM System Storage N series Diagnostics Guide for informationabout specific diagnostics tests you can perform.If you do not want to run diagnostics, continue with the next step.

Attention: Use the cf giveback command from the partner node’sconsole to enable your active/active or high availability configuration.

d. Exit diagnostics and then continue with the next step.6. Go to “Completing the replacement process.”


Battery disposalDispose of batteries according to local regulations regarding battery recyclingor disposal. For more information, see the IBM Environmental Notices and UserGuide, Z125-5823.

Installing or replacing a Remote LAN Module

This section describes how to perform the following tasks:v “Removing the RLM” on page 72v “Installing an RLM” on page 73v “Testing the RLM” on page 76v “Testing and booting the system” on page 77v “Completing the replacement process” on page 78v “Information on using the RLM” on page 78


The N6000 series storage systems require an RLM card with firmware version2.0 or later. This section includes the procedure for verifying the firmwareversion on your new RLM card and directs you to instructions fordownloading updated firmware, if needed.

Removing the RLM

Note: This procedure assumes that all other components of the system arefunctioning properly. If your system does not meet this criteria, contacttechnical support.

Shutting down the controller module1. Shut down the target controller module (called a node in an active/active


configuration











3. Check whether the NVRAM LEDs on the controller module are flashingred (see Figure 17 on page 64).


Flashing red LEDs indicate that there is content in the NVRAM that hasnot been saved to disk.v If your system is in an active/active or high availability configuration,


v If your system is in a single-controller module configuration, completethe following substeps:a. Reconnect the power supplies to the power source.b. Reboot the controller module.c. Repeat substeps 1a on page 72 and 1b on page 72, and then repeat

step 2 on page 72.


4. Locate the RLM, in the center of the riser housing.Refer to the controller module DIMM cover for the illustration showingthe location and removal of the RLM.

5. Pinch the retaining tabs on the RLM, and then lift the RLM straight out ofthe socket and the housing.

6. Go to “Installing an RLM.”

Installing an RLM1. Remove the RLM, as described in “Removing the RLM” on page 72, if

necessary.2. Align the edges of the RLM with the guide slots on the edges of the riser

housing, lower the RLM into place in the housing, and then press theRLM into the socket by using your thumbs in the top center of the RLM.Make sure that you press down at the places indicated by the sticker onthe RLM housing. Make sure that the retaining tabs latch in place.

3. Reinstall the controller module by completing the following steps:Attention: For active/active or high availability configurations, thesequence in which you reinstall the controller module is important becauseit attempts to reboot as soon as you completely seat it in the chassis.a. Gently push the controller module halfway into the chassis.b. Recable the controller module.v If you are replacing an existing RLM, recable the controller module,

as needed.v If you are installing an RLM for the first time, plug one end of the

RJ-45 cable into the RLM port, and then plug the other end into a10/100 Ethernet network port.

c. Attach the cable management tray.


d. Push the controller module all the way into the chassis.


4. Check the link LED on the RLM port to ensure that it is green and that thelink is active.

Note: The network for the RLM should be a 10/100 Ethernet network, ora network that can autonegotiate settings to a 10/100 Ethernetnetwork.

5. Verify that the RLM you installed has firmware version 2.0 or later.a. Log into the RLM console from a remote host acting as a system

console by entering the following command from the administrationhost prompt:admin-host> ssh user_name@RLM_IP_address

Example:admin-host> ssh [email protected]

[email protected]’s password:*********

RLM admin-host>

Note: Root login is not allowed for the RLM. If you need to log inwith root credentials, use naroot for root login.

b. Verify the version of RLM firmware by entering the followingcommand in administration mode:version

v If the firmware version of the new RLM is 2.0 or later, continue withthe next step.

v If the firmware version of the RLM is earlier than 2.0, you mustupdate the firmware. For instructions on downloading firmware foryour RLM, see the IBM System Storage N series Data ONTAP UpgradeGuide.

6. Enter the following command to boot the system:boot_ontap

v If you are replacing an existing RLM, run diagnostics, as described in“Testing and booting the system” on page 77.

v If you are installing an RLM for the first time, complete the followingsubsteps:a. Enter the following command from the system console to begin the

RLM setup script:mysystem-1> rlm setup

Example:


mysystem-1> rlm setup

The Remote LAN Module (RLM) provides remote managementcapabilities including console redirection, logging and powercontrol.

It also extends AutoSupport by sending additional system eventalerts. Your AutoSupport settings are used for sending thesealerts via email over the RLM LAN interface.

Would you like to configure the RLM [y]: y

Would you like to enable DHCP on the RLM LAN interface [y]: n

Please enter the IP address for the RLM []: 10.10.123.45

Please enter the netmask for the RLM []: 255.255.224.0

Please enter the IP address for the RLM gateway []:10.10.123.1

mysystem-1>

Note: The RLM requires AutoSupport to be activated andconfigured. If AutoSupport is not set up and configured, do soat this time. See the IBM System Storage N series Data ONTAPSystem Administration Guide for AutoSupport setupinformation.

b. Enter the following command from the system console to check thestatus and settings of the RLM:mysystem-1> rlm status

Example:mysystem-1> rlm status

Remote LAN Manager

Part Number: 110-00030

Revision: 32

Serial Number: 2P6256

Firmware Version: 1.0.10 Mon Jan 17 16:27:58 PST 2005

Mgmt MAC Address: 00:A0:98:01:9A:F8

Using DHCP no

IP Address: 172.22.136.61

Netmask: 255.255.224.0

Gateway: 172.22.128.1

c. Go to “Testing the RLM” on page 76 to ensure that you can accessthe RLM from the administration console.


Testing the RLMThe RLM provides a command-line interface (CLI) to access its features. Youmust log in to the RLM over its network interface by using a secure shellclient application, such as SSH, OpenSSH, or PuTTY. Insecure connectionprotocol applications, such as telnet, are not available. See the IBM SystemStorage N series Data ONTAP System Administration Guide for more informationabout secure shell client applications.

To test the RLM, complete the following steps:1. To test the RLM, complete the following steps, as appropriate for your

configuration:v In an active/active or high availability configuration:

To run diagnostics on the RLM in an active/active or high availabilityconfiguration, complete the following steps:a. Press Ctrl-C to halt the system at the Waiting for giveback prompt.b. Answer y to the prompt Do you wish to halt this node rather

than wait [y/n]?

c. Enter the boot_diags command at the boot loader prompt.d. Continue with step 2.

v In a single-controller configuration:

To run diagnostics on the RLM in a single-controller configuration,complete the following steps:a. Log into the RLM console from a remote host acting as a system

console by entering the following command from the administrationhost prompt:admin-host> ssh user_name@RLM_IP_address

Example:admin-host> ssh [email protected]

[email protected]’s password:*********

RLM admin-host>

Note: Root login is not allowed for the RLM. If you need to log inwith root credentials, use naroot for root login.

b. Check RLM status by entering the following command from theRLM console:RLM admin-host> rlm status

c. Continue with step 2.2. Exit the RLM console by entering the following command:

RLM admin-host> exit


3. Connect to the system console using the serial connection or throughtelnet.

4. Test the RLM AutoSupport functions by sending a test e-mail toAutoSupport with the following command from the system console:mysystem-1> rlm test autosupport

5. Go to “Testing and booting the system.”

Testing and booting the systemAfter you recable your system and connect it to the power source, you shouldrun diagnostics on the RLM. If the system passes the diagnostic tests, you canboot the system and bring it back online.1. Run diagnostics on the RLM:v In an active/active or high availability configuration:

To run diagnostics on the RLM in an active/active or high availabilityconfiguration, complete the following steps:a. Press Ctrl-C to halt the system at the Waiting for giveback prompt.b. Answer y to the prompt: Do you wish to halt this node rather

than wait [y/n]?c. Enter the boot_diags command at the boot loader prompt.d. Continue with step 2.

v In a single-controller configuration:

To run diagnostics on the RLM in a single controller configuration,complete the following steps:a. Turn on the system or reboot it by entering the boot_ontap

command.b. Stop the boot process before LOADER completes loading and enter

boot_diags at the boot loader prompt.c. Continue with step 2.

2. Select the Agent and RLM Diagnostic option from the main menu, andthen run the Comprehensive Test.

3. Correct any errors, and then exit diagnostics.4. Enter the following command at the prompt to boot the system:

boot_ontap





Information on using the RLMThe following table provides a list of manuals for configuring and using theRLM.

Manual title Information needed

Installation and Setup Instructions foryour platform

Describes the system and RLM cabling.

Diagnostics Guide Lists and describes the diagnostic tests for anew or existing RLM.

Data ONTAP System AdministrationGuide

Describes RLM configuration and use.

Platform Monitoring Guide Lists RLM error messages and givescorrective action for the error.

Replacing a CompactFlash card in N6000 series systems

Note: This section contains procedures for two different configurations. Youmust use the correct procedure for your configuration:v If you have a single-controller configuration, see “Replacing a

CompactFlash card in a single-controller system” on page 79.v If you have an active/active or high availability configuration, see

“Replacing a CompactFlash card in an active/active or highavailability configuration” on page 84.

You might also need the following documentation to perform the identifiedprocedures:v IBM System Storage N series Data ONTAP Upgrade Guide, as applicablev IBM System Storage N series Data ONTAP Commands: Manual Page Reference,

if applicablev IBM System Storage N series Data ONTAP System Administration Guide, if

applicable

These procedures are written with the assumption that you have access to atleast one of the following:v A system on your network that you can use to netboot your system.v A PC with a card reader/writer and with access to the IBM web site.


If your system does not meet these criteria, contact IBM technical support.

Verifying system requirementsSoftware release information and downloads, including Data ONTAPsoftware, firmware, and diagnostics upgrades, are available at the followingsite:


Replacing a CompactFlash card in a single-controller systemThis procedure describes how to replace a CompactFlash card in asingle-controller configuration.

If your system is in an active/active or high availability configuration, use theprocedure in “Replacing a CompactFlash card in an active/active or highavailability configuration” on page 84.

This section describes how to perform the following tasks:v “Removing the CompactFlash card”v “Installing the CompactFlash card” on page 81v “Placing the system files on the CompactFlash card” on page 81v “Updating the CompactFlash card” on page 83

Removing the CompactFlash card



1. Retrieve and save the system environment variables, if possible, bycompleting the following substeps:a. Bring the system down to the boot loader prompt.v If the system is running, reboot it, press Ctrl-C when prompted by

the system, and then go to substep 1b.v If the system is at the boot loader prompt, go to substep 1b.

b. Display the system environment variables by entering the followingcommand:printenv

c. Copy the environment variable values.You need these variable values for the replacement CompactFlash card.

Note: You do not need to retrieve the Fibre Channel port settings for astand-alone configuration. Fibre Channel port settings are storedin the boot environment and also on disk in the system rootvolume. When you reboot the system, Fibre Channel settings arerestored from the saved settings.

2. Turn off the power supplies, unplug both power cords from the powersource, and then remove the power cords.

n6hw004Front

CompactFlash Card

Figure 20. CompactFlash card removal


3. While grounded, remove the controller module from the chassis, asdescribed in “Opening the system” on page 35.

4. Check the NVRAM memory LEDs on the controller module board.If the LEDs are flashing red, there is content in the NVRAM that has notbeen saved to disk. Complete the following substeps:a. Reinstall the controller module and reconnect the power supplies to the

power source.b. Reboot the controller module.c. Repeat Steps 1 and 2.v If the NVRAM memory LEDs are no longer flashing red, go to step

5.v If repeated attempts to cleanly shut down the controller module fail,

remove the controller module and proceed to step 5. However, beaware that you might lose any data that was not saved to disk.

5. Turn the controller module so that the cables are facing away from you,and then locate the CompactFlash card inside and on the left of thecontroller module.

6. Grasp the CompactFlash card and lift it straight up and out of the socket.7. Go to “Installing the CompactFlash card.”

Installing the CompactFlash cardAttention: If you are copying the system files to the CompactFlash cardusing a PC or laptop with a card writer, you must copy the system files to theCompactFlash card prior to installing it in the controller module. See“Transferring the system files using a PC or laptop” on page 82 forinformation.1. While grounded, align the CompactFlash card with the edges of the

CompactFlash card socket. Seat the CompactFlash card by firmly pushingit down into the CompactFlash socket.The CompactFlash card should be squarely seated and should not move.Reseat the CompactFlash card, if necessary.

2. Reinstall the controller module, as described in “Closing the system” onpage 37.

3. Go to “Placing the system files on the CompactFlash card.”

Placing the system files on the CompactFlash cardYou can transfer system files to the new CompactFlash card using netboot ora PC or laptop. The method you select depends on the following situations:v Use netboot when you cannot copy the system files to the CompactFlash

card because you do not have access to a card reader/writer but can accessa network server.


v Use a PC or laptop when you can access a card reader/writer but you canonly take the CompactFlash card to the system; you cannot leave withanything you take to the system. For example, you are entering a securedlocation and must leave behind whatever you take into the location.

This section describes how to perform the following tasks:v “Transferring the system files using netboot”v “Transferring the system files using a PC or laptop”

Note: This procedure is written with the assumption that you have accessto a PC running Windows® XP or later and have a zip program.

Transferring the system files using netboot:

1. Per the recommendations in the IBM System Storage N series Data ONTAPUpgrade Guide , place the system files on the server you use for netbooting.You can copy the system files from the system boot directory, at/etc/boot/netapp-x86-64, or download the file <rlse>_netboot.q atwww.ibm.com/storage/support/nas/.

2. Turn on your system and press Ctrl-C to stop the boot process at the bootloader prompt.

3. Configure your network connection, if needed.v If you have DHCP running on your network, enter the following

command at the prompt:ifconfig e0a -auto

v If you do not have DHCP running, configure the connection by enteringthe following command at the prompt:ifconfig e0a -addr=filer_addr -mask=netmask -gw=gateway-dns=dns_addr -domain=dns_domain

filer_addr is the IP address of the system.netmask is the network mask of the system.gateway is the gateway for the system.dns_addr is the IP address of a name server on your network.dns_domain is the DNS domain name.

4. Enter the following command at the boot loader prompt:netboot URL

URL is the location of the remote system files. It can be either an HTTP or aTFTP network path.

5. Go to “Updating the CompactFlash card” on page 83.

Transferring the system files using a PC or laptop:

1. Download <rlse>_setup_q.exe to your PC.



rlse is the Data ONTAP release you are using.You can download the system files at www.ibm.com/storage/support/nas/. You can also copy the system files from the system boot directoryof another system at /etc/boot/netapp-x86-64. Contact IBM technicalsupport if you cannot get the system files from these sources.Attention: Make sure that you download the correct file, designated forPC administration, and that it is the same version of Data ONTAP aswhat is on your system.

2. Extract the contents of <rlse>_setup_q.exe to a temporary folder on yourPC.

3. Insert the CompactFlash card into the CompactFlash card reader.Attention: The CompactFlash card is pre-formatted. Do not format theCompactFlash card.

4. Create a folder called X86_64 in the root partition of the CompactFlashcard, and then create a subfolder called KERNEL in the X86_64 folder.

5. Copy netapp-x86-64 into the KERNEL folder in Windows Explorer.6. Rename the netapp-x86-64 image to Primary.KRN.7. Install the CompactFlash card with the kernel image into the system.8. Reinstall the controller module, recable it, and turn on the power.9. The controller will boot when power is turned on. If necessary, boot Data

ONTAP by entering the following command at the LOADER prompt:boot_ontap

10. Go to “Updating the CompactFlash card.”

Updating the CompactFlash card1. Download the system files to the CompactFlash card by entering the

following command:download

Attention: If the download fails with the following error message, youmust run setup to reinstall the proper files on the system that enable youto execute the download command on the CompactFlash card:

Failed to open download script file /etc/boot/x86-64/kernel_1024.cmds: No such file download.requestDoneError:error]:Operator requested download failed.

2. Check the version of the image by entering the following command:version -b

Make sure that the kernel version on the CompactFlash card is the sameversion was originally on the system.





4. Go to “Restoring environment variables.”

Restoring environment variables1. Check the version of the image by entering the following command:

version -b

Make sure that the BIOS and Diagnostic images are the correct version. Ifthey are not, go to www.ibm.com/storage/support/nas/ and follow theinstallation instructions to install the version you need.

2. Halt the controller by entering the following command:halt

3. Display the default environment variables by entering the followingcommand:printenv

4. Compare the default environment variables with the list you made in“Removing the CompactFlash card” on page 79.If the variable values are the same, go to step 5.If the variable values are different or need modification, complete thefollowing steps:a. Set the values of the individual variables by entering the following

command for each changed variable:setenv variable_name variable_value

b. Verify the values of the variables by entering the following commandfrom the boot loader prompt:printenv

5. Boot Data ONTAP after you modify all variables by entering the followingcommand:boot_ontap


Replacing a CompactFlash card in an active/active or high availabilityconfiguration

This procedure describes how to nondisruptively replace the CompactFlashcard in an active/active or high availability configuration.

If your system is a single-controller system, use the procedure in “Replacing aCompactFlash card in a single-controller system” on page 79.

Note: The following steps may be disruptive and are recommended to bepreformed only during a maintenance window.

This section describes how to perform the following tasks:v “Preparing for the CompactFlash card replacement” on page 85



v “Removing the CompactFlash card” on page 86v “Installing the replacement CompactFlash card” on page 86v “Updating the CompactFlash card” on page 88v “Restoring environment variables and onboard Fibre Channel port

configurations” on page 89v “Completing the replacement process” on page 90

Preparing for the CompactFlash card replacement1. Check the status of the active/active or high availability configuration and

take over the target node.v If you can connect to the target node through normal means, complete

the following substeps:a. Check that the active/active or high availability configuration is

enabled by entering the following command:cf status

If it is enabled, go to substep 1b.If it is not enabled, enable it by entering the following command:cf enable

b. Take over the target node by entering the following command fromthe partner console:cf takeover

c. Stop the target node from rebooting by pressing Ctrl-C when you seethe following message: Starting AUTOBOOT press Ctrl-C to abort

d. Go to step 2 on page 86.v If you cannot connect to the target node through normal means and the

node is receiving power, complete the following substeps:a. Connect a console directly to the target node through the marked

console port.Follow the manufacturer’s installation instructions for configuration.The boot loader prompt should be accessible after the consoleconnection is established. If it is not, contact technical support.

b. Boot the target node from the backup system files on theCompactFlash card.You might need to rename the backup system file so that it boots asthe primary file.

c. Return to the partner node and enable clustering by entering thefollowing command:cf enable

d. Take over the target node by entering the following command fromthe partner console:


cf takeover

e. Stop the target node from rebooting by pressing Ctrl-C when yousee the following message: Starting AUTOBOOT press Ctrl-C toabort

f. Go to step 2.2. At the boot loader prompt, display the environment variables for the

target node by entering the following command:printenv

3. Copy the values for the variables and save them for later use when yourestore the environment variables on the replacement CompactFlash card.

4. Go to the partner console and enter the following command:partner fcadmin config

5. Copy the values for the onboard Fibre Channel settings and save them forlater use when you restore the settings on the replacement CompactFlashcard.

6. Go to “Removing the CompactFlash card.”

Removing the CompactFlash card1. While grounded, shut down the controller module and remove it from the

chassis, as described in “Shutting down a controller module” on page 34and “Opening the system” on page 35.

2. Turn the controller module so that the cables are facing away from youand then locate the CompactFlash card inside and on the left of thecontroller module.

3. Grasp the CompactFlash card and lift it up and out of the socket.4. Go to “Installing the replacement CompactFlash card.”

Installing the replacement CompactFlash cardYou can transfer system files to the new CompactFlash card using netboot ora PC or laptop. The method you select depends on the following situations:v Use netboot when you cannot copy the system files to the CompactFlash

card because you do not have access to a card reader/writer but can accessa network server.

v Use a PC or laptop-when you can access a card reader/writer but you canonly take the CompactFlash card to the system; you cannot leave withanything you take to the system. For example, you are entering a securedlocation and must leave behind whatever you take into the location.

This section describes how to perform the following tasks:v “Transferring the system files using netboot” on page 87v “Transferring the system files using a PC or laptop” on page 88


Transferring the system files using netboot:

1. Make sure that you are properly grounded.2. Per the recommendations in the IBM System Storage N series Data ONTAP

Upgrade Guide, place the system files on the server you use fornetbooting.You can copy the system files from the system boot directory, at/etc/boot/netapp-x86-64, or download the file <rlse>_netboot.q atwww.ibm.com/storage/support/nas/.

3. Align the CompactFlash card with the edges of the CompactFlash cardslot. Seat the CompactFlash card by sliding it into the CompactFlashreader.The CompactFlash card should be squarely seated and should not move.Reseat the CompactFlash card, if necessary.

4. Reinstall the controller module into the chassis and recable it, asdescribed in “Closing the system” on page 37.

Note: The node starts to reboot as soon as you insert it fully back intothe chassis.

5. Press Ctrl-C to stop the boot process and go to the boot loader prompt.6. Configure your network connection, if needed.

If you have DHCP running on your network, enter the followingcommand at the prompt:ifconfig e0a -auto

If you do not have DHCP running, configure the connection by enteringthe following command at the prompt:ifconfig e0a -addr=filer_addr -mask=netmask -gw=gateway-dns=dns_addr -domain=dns_domain

filer_addr is the IP address of the system.netmask is the network mask of the system.gateway is the gateway for the system.dns_addr is the IP address of a name server on your network.dns_domain is the DNS domain name.

7. Enter the following command at the boot loader prompt:netboot URL

URL is the location of the remote system files from step 2. It can be eitheran HTTP or a TFTP network path.

8. On the failed node, at the Special Boot Menu, select Option 1 for normalboot. Wait until you receive the prompt: Waiting for Giveback (pressCtrl-C to abort wait).

9. On the partner node, enter the following command: cf giveback



10. After the target node completes booting, go to “Updating theCompactFlash card.”

Transferring the system files using a PC or laptop:

1. Download <rlse>_setup_q.exe to your PC.rlse is the Data ONTAP release you are using.You can download the system files at www.ibm.com/storage/support/nas/. You can also copy the system files from the system boot directoryof another storage system at /etc/boot/netapp-x86-64. Contact IBMtechnical support if you cannot get the system files from these sources.Attention: Make sure that you download the correct file, designated forPC administration, and that it is the same version of Data ONTAP aswhat is on your system.

2. Extract the contents of <rlse>_setup_q.exe to a temporary folder on yourPC.

3. Insert the CompactFlash card into the CompactFlash card reader.Attention: The CompactFlash card is pre-formatted. Do not format theCompactFlash card.

4. Create a folder called X86_64 in the root partition of the CompactFlashcard, and then create a subfolder called KERNEL in the X86_64 folder.

5. Copy netapp-x86-64 into the KERNEL folder in Windows Explorer.6. Rename the netapp-X86-64 image to Primary.KRN.7. While grounded, install the CompactFlash card into the controller

module.8. Reinstall the controller module into the chassis and recable it, as

described in “Closing the system” on page 37.

Note: The node starts to reboot as soon as you insert it back into thechassis.

Make sure that you give back the node when prompted to do so.9. The controller will boot when power is turned on. If necessary, boot Data

ONTAP by entering the following command at the LOADER prompt:boot_ontap

10. Go to “Updating the CompactFlash card.”

Updating the CompactFlash card1. Download the system files to the CompactFlash card by entering the

following commands:download




Attention: If the download fails with the following error message, youmust run setup to reinstall the proper files on the system that enable youto execute the download command on the CompactFlash card:

Failed to open download script file /etc/boot/x86-64/kernel_1024.cmds: No such file [download.requestDoneError:error]:Operator requested download failed.

2. Check the version of the image by entering the following command:version -b

Make sure that the kernel version on the CompactFlash card is the sameversion was originally on the system.


4. Press Ctrl-C to stop the system at the boot loader prompt, then go to“Restoring environment variables and onboard Fibre Channel portconfigurations””.

Restoring environment variables and onboard Fibre Channel portconfigurations1. Retrieve the environment variables you saved in “Preparing for the

CompactFlash card replacement” on page 85.2. Enter the following command for each variable you must reset:

setenv variable “value”

variable is the variable name.value is the setting you are assigning to the variable.

3. Boot Data ONTAP by entering the following command from the targetnode’s console:boot_ontap

4. When the following message is displayed on the target node’s console:Waiting for giveback....Press Ctrl-C to abort wait enter the followingcommand from the partner node’s console:cf giveback

5. After giveback completes, from the target node’s console, check theconfiguration of the onboard Fibre Channel ports by entering thefollowing command:fcadmin config

v If the displayed information is the same as what you captured for theonboard Fibre Channel ports in step 5 on page 52 of “Preparing for theCompactFlash card replacement” on page 85, then go to “Completingthe replacement process” on page 90.


v If the displayed information is different from what you captured for theonboard Fibre Channel ports, complete the following substeps:a. Reboot the node and press Ctrl-C when Press CTRL-C for special

boot menu appears.b. Press Ctrl-C again when Press CTRL-C for Maintenance menu to

release disks appears.c. Confirm disk release when prompted.d. Reset the Fibre Channel ports in one of three ways:

– To reset the target ports, enter the following command for eachport:fcadmin config -t target adapter_name

– To reset the initiator ports, enter the following command for eachport:fcadmin config -t initiator adapter_name

– To reset the ports to unconfigured, enter the following commandfor each port:fcadmin config -t unconfig adapter_name

e. On the failed node, verify the values of the variables by entering thefollowing command from the boot loader prompt:printenv

6. On the failed node, boot Data ONTAP by entering the followingcommand:boot_ontap




Appendix A. Recommended power line sizes

This appendix discusses how to determine the power line lengths runningfrom your N series system to the power source.

Recommended AC power line sizes

Longer AC power feeds need to be properly designed to preserve voltagelevels to the equipment. The wiring from the breaker panel to the power strip,which supplies power to your N6000 series system and storage expansionunits, can often exceed 50 feet.

Note: Total AC wire length = breaker to wall or ceiling outlet + extensioncable or ceiling drop.

The following table lists the recommended conductor size for 2% voltage dropfor a particular distance in feet (taken from the Radio Engineer’s Handbook).

Table 21. 110V, single phase recommended conductor sizes

110V, single-phase 20A circuit 30A circuit 40A circuit 50A circuit

25 feet 12 AWG 10 AWG 8 AWG 8 AWG



Table 22. 220V, single phase recommended conductor sizes

220V, single-phase 20A circuit 30A circuit 40A circuit 50A circuit




The following table list the approximate equivalent wire gauge (AmericanWire Gauge (AWG) to Harmonized Cordage).

Table 23. American Wire Gage to Harmonized Cordage equivalents

AWG 8 10 12

Harmonized, mm-mm 1 4.0 2.5 1.5

1 mm-mm = millimeter squared


Appendix B. FRU/CRU and power cord list for N seriesproducts

This appendix contains information about FRU/CRUs and power cords for Nseries products.

FRU/CRU list for N series products

For the most current FRU/CRU list for your N series product, see thefollowing web site:


Power cord list for N series products

The following list details the power cord feature codes (FCs) for N seriesproducts.

FC 9000 (All countries)Power cord, Rack PDUv 27 inchesv Rated 250 V/15 Av Product end uses C14; PDU end uses C13.

FC 9001 Europe and othersProvides power cords for Austria, Belgium, Bolivia, Bulgaria, Chile,Croatia, Czech Republic, Egypt, Estonia, European Union, Finland,France, Germany, Greece, Hungary, Iceland, Indonesia, Latvia,Lebanon, Lithuania, Luxemburg, Morocco, Netherlands, Norway,Peru, Poland, Portugal, Romania, Russia, Slovakia, Slovenia, Spain,Suriname, Sweden, Turkeyv 2.5 m (9 feet), unshielded, rated 250 V/10 A.v Attached plug EL 211 (CEE 7-VII) designed for 200-240 V ac input.

FC 9002 United Kingdom and othersProvides power cords for United Kingdom, Costa Rica, Cyprus,Guyana, Hong Kong, Ireland, Kuwait, Malta, Oman, Singapore, SriLankav 2.5 m (9 feet), unshielded, rated 250 V/10 A.v Attached plug EL 210 (13A fuse) designed for 200-240 V ac input.

FC 9003 JapanProvides power cords for Japan



v 1.83 m (6 feet), unshielded, rated 125 V/15 A.v Attached plug EL 302 (JIS C3306) designed for 100-110 V ac input.

FC 9004 U.S., Six Feet (2 m)Provides power cords for U.S., Canada, Mexico, Belize, Columbia,Ecuador, El Salvador, Guatemala, Honduras, Korea, Nicaragua,Panama, Philippines, Puerto Rico, Saudi Arabia, Thailand, Venezuelav 1.83 m (6 feet), unshielded, rated 125 V/15 A.v Attached plug EL 302 (Nema 5-15P) designed for 100-120 V ac

input.

FC 9005 Australia, New ZealandProvides power cords for Australia, New Zealand, Uruguayv 2.5 m (9 feet), unshielded, rated 250 V/10 A.v Attached plug EL 206 (AS 3112) designed for 200-240 V ac input.

FC 9006 Switzerland, LiechtensteinProvides power cords for Switzerland, Liechtensteinv 2.5 m (9 feet), unshielded, rated 250 V/10 A.v Attached plug EL 203 (SEV 1011) designed for 200-240 V ac input.

FC 9007 ArgentinaProvides power cords for Argentinav 2.5 m (9 feet), unshielded, rated 250 V/10 A.v Attached plug EL 219 (IRAM 2073) designed for 200-240 V ac input.

FC 9008 ChinaProvides power cords for Chinav 2.5 m (9 feet), unshielded, rated 250 V/10 A.v Attached plug EL 602 (GB 2099/GB 1002) designed for 200-240 V ac

input.

FC 9009 DenmarkProvides power cords for Denmarkv 2.5 m (9 feet), unshielded, rated 250 V/10 A.v Attached plug EL 213 (DHCR 107-2-D1) designed for 200-240 V ac

input.

FC 9010 India, Pakistan, South AfricaProvides power cords for India, Macau, Pakistan, South Africav 2.5 m (9 feet), unshielded, rated 250 V/10 A.v Attached plug EL 208 (BS 164-1, BS 546) designed for 200-240 V ac

input.

FC 9011 IsraelProvides power cords for Israel


v 2.5 m (9 feet), unshielded, rated 250 V/10 A.v Attached plug EL 212 (SI 32) designed for 200-240 V ac input.

FC 9012 ItalyProvides power cords for Italyv 2.5 m (9 feet), unshielded, rated 250 V/10 A.v Attached plug EL 502 (CEI 23-16) designed for 200-240 V ac input.

FC 9013 North America (250 V)Provides power cords for U.S.v 1.83 m (6 feet), unshielded, rated 250 V/15 A.v Attached plug EL 309 (NEMA 6-15P) designed for 200-240 V ac

input.

FC 9014 BrazilProvides power cords for Brazilv 2.5 m (9 feet), unshielded, rated 250 V/10 A.v Attached plug EL 211 (NBR 6147/2000) designed for 200-240 V ac

input

FC 9015 TaiwanProvides 125 V power cords for Taiwanv 2.5 m (9 feet), unshielded, rated 125 V/15 A.v Attached plug EL 302 (CNS 10917-3) designed for 100-120 V ac

input.

FC 9016 Taiwan (250 V)Provides 250 V power cords for Taiwanv 1.83 m (6 feet), unshielded, rated 250 V/10 A.v Attached plug EL 610 (CNS 10917, CNS 690) designed for 250 V ac

input.

Appendix B. FRU/CRU and power cord list for N series products 95

Appendix C. Optional adapter cards

IBM supports the following optional PCIe adapter cards in N6000 seriessystems.

Table 24. Optional adapter cards supported by N6000 series systems

FeatureCode Feature Code Description Supported systems

1012 Dual-port Gigabit Ethernet adapter (optical) N6040, N6060, N6070

1013 Dual-port 10/100/1000 Ethernet adapter(copper)

N6040, N6060, N6070

1014 Dual-port 4-Gbps Fibre Channel HBA for diskattachment

N6040, N6060, N6070

1015 Dual-port 4-Gbps Fibre Channel HBA for tapeattachment

N6040, N6060, N6070

1017 Dual-port 4-Gbps Fibre Channel target HBA N6040, N6060, N6070

1021 Dual-port GbE iSCSI adapter (optical) N6040, N6060, N6070

1022 Quad-port GbE Ethernet TOE adapter (copper) N6040, N6060, N6070

1023 Quad-port GbE Ethernet adapter (copper) N6040, N6060, N6070

1024 Dual-port Ultra320 SCSI HBA for tapeattachment

N6040, N6060, N6070

1026 Dual-port GbE iSCSI target adapter (copper) N6040, N6060, N6070

1029 Quad-port 4-Gbps Fibre Channel HBA for diskand tape attachment

N6040, N6060, N6070

1030 Quad-port 4-Gbps Fibre Channel target HBA N6040, N6060, N6070

1031 Dual-port 10 GbE Ethernet adapter N6040, N6060, N6070

1032 Dual-port MetroCluster VI HBA(A20/A21/A22 models only)

N6040, N6060, N6070

1033 SnapMirror over Fibre Channel HBA N6040, N6060, N6070

1035 Quad-port 4-Gbps Fibre Channel HBA for tapeand disk attachment

N6040, N6060, N6070

1036 Dual-port 8-Gbps Fibre Channel target HBA N6040, N6060, N6070

1056 16-GB Performance Acceleration Module (PAMI)

N6040, N6060, N6070

1057 512-GB Performance Acceleration Module(PAM II)

N6070


Table 24. Optional adapter cards supported by N6000 series systems (continued)

FeatureCode Feature Code Description Supported systems

1058 256-GB Performance Acceleration Module(PAM II)

N6040, N6060

1061 Quad-port 3-Gbps SAS adapter N6040, N6060, N6070

1063 Dual-port Fibre Channel over Ethernet (FCoE)Target Adapter (optical)

N6040, N6060, N6070

1064 Dual-port Fibre Channel over Ethernet (FCoE)Target Adapter (copper)

N6040, N6060, N6070

1065 Dual-port 10-Gbps NIC N6040, N6060, N6070

The following is the priority order for installing optional adapter cards intothe N6000 series system:1. Storage adapters for attaching disk storage expansion units (FC 1014, 1029,

1035, 1061)2. Storage adapters for mirroring or MetroCluster configurations (FC 1032,

1033)3. Performance Acceleration Modules I and II (PAMs) (FC 1056, 1057, 1058)4. Adapters for host block access (FC 1017, 1021, 1026, 1030, 1036, 1063, 1064,

1065)5. Network Interface cards (FC 1012, 1013, 1022, 1023, 1031)6. Storage adapters for tape attachment (FC 1015, 1024, 1029)

For the single-node models, the total number of PCIe adapters cannot exceedfour. For the dual-node (active/active or high availability) models, the totalnumber of PCIe adapters cannot exceed eight.

For information about monitoring the LEDs for your optional adapter cards,refer to the IBM System Storage N series Platform Monitoring Guide.

Dual-port Gigabit Ethernet (GbE) adapter (optical) (FC 1012)

Feature code 1012 is a dual-port Gigabit Ethernet (1000BASE-SX) adapter. Thisadapter has two LC duplex connectors and supports a maximum distance of275 meters using 62.5-micron MMF media and 550m using 50-micron MMFmedia.

For a single-node model, the maximum number of this adapter is four. For adual-node model, the maximum number of this adapter is eight.

The slot priority order for this adapter is 4, 3, 2, 1.


Dual-port 10/100/1000 Ethernet adapter (copper) (FC 1013)

Feature code 1013 is a dual-port 10/100/1000 Ethernet adapter. This adaptersupports 10BASE-T, 100BASE-TX and 1000BASE-T Ethernet standards. Thisadapter has two RJ-45 connectors and supports a maximum distance of 100meters using Category 5 or better unshielded twisted pair (UTP) four-pairmedia.



Dual-port 4-Gbps Fibre Channel HBA for disk attachment (FC 1014)

Feature code 1014 is a dual-port 4-Gbps Fibre Channel HBA. This adapterauto-negotiates to 4, 2 and 1 Gbps. This adapter may only be used forattaching supported N series disk storage expansion units (EXN1000,EXN2000, and EXN4000). The Fibre Channel ports on this adapter may not beused as FCP target ports.

This adapter has two small form factor (SFF) multi-mode optics with LC-styleconnectors. This adapter supports the following maximum cable lengths.

Table 25. Dual-port 4-Gbps Fibre Channel HBA for disk (FC 1014) - maximum cablelengths

Link operating speed50 micron multi-modefiber

62.5 micron multi-modefiber

1 Gbps 500 meters 300 meters





Dual-port 4-Gbps Fibre Channel HBA for tape attachment (FC 1015)

Feature code 1015 is a dual-port 4-Gbps Fibre Channel HBA for tapeattachment. This adapter auto-negotiates to 4, 2 and 1 Gbps.

This adapter has two SFF multi-mode optics with LC-style connectors. Thisadapter supports the following maximum cable lengths.

Appendix C. Optional adapter cards 99

Table 26. Dual-port 4-Gbps Fibre Channel HBA for tape (FC 1015) - maximum cablelengths








This feature code includes a 50-micron optical loopback cable with LCconnectors.

Dual-port 4-Gbps Fibre Channel target HBA (FC 1017)

Feature code 1017 is a dual-port 4-Gbps Fibre Channel HBA for FCP targetports. This adapter auto-negotiates to 4, 2 and 1 Gbps. This adapter is usedfor providing two additional 4-Gbps FCP target ports. It is not used forattaching N series storage expansion units.

This adapter has two SFF multi-mode optics with LC-style connectors. Thisadapter supports the following maximum cable lengths.

Table 27. Dual-port 4-Gbps Fibre Channel target HBA (FC 1017) - maximum cablelengths






For a single-node model, the maximum number of this adapter is two. For adual-node model, the maximum number of this adapter is four.


Dual-port GbE iSCSI adapter (optical) (FC 1021)

Feature code 1021 is a dual-port Ethernet iSCSI adapter.




Quad-port GbE Ethernet TOE adapter (copper) (FC 1022)

Feature code 1022 is a quad-port 10/100/1000 Ethernet TOE adapter.



Quad-port GbE Ethernet adapter (copper) (FC 1023)

Feature code 1023 is a quad-port 10/100/1000 Ethernet adapter. This adaptersupports 10BASE-T, 100BASE-TX and 1000BASE-T Ethernet standard. It hasfour RJ-45 connectors and supports a maximum distance of 100 meters usingCategory 5 or better unshielded twisted pair (UTP) four-pair media.



Dual-port Ultra320 SCSI HBA for tape attachment (FC 1024)

Feature code 1024 is a dual-port Ultra320 SCSI host bus adapter (HBA) fortape attachment.



Dual-port GbE iSCSI target adapter (copper) (FC 1026)

Feature code 1026 is a dual-port Ethernet iSCSI adapter.




Quad-port 4-Gbps Fibre Channel HBA for disk and tape attachment (FC 1029)

Feature code 1029 is a PCIe quad-port 4-Gbps HBA for attaching supported Nseries disk storage expansion units (EXN1000, EXN2000, and EXN4000) andtape devices to N series storage controllers. This adapter auto-negotiatesconnections of 1-Gbps, 2-Gbps, or 4-Gbps. Four small form factor (SFF)multimode optical ports with LC connectors support the following cablelengths:

Table 28. Quad-port 4-Gbps Fibre Channel HBA for disk and tape attachment (FC1029) - maximum cable lengths






The ports of this adapter may not be used as FCP target ports.



Quad-port 4-Gbps Fibre Channel Target adapter (FC 1030)

Feature code 1030 is a PCIe quad-port 4-Gbps HBA for FCP target ports. Thisadapter may only be used to provide additional target ports; it may not beused to attach storage expansion units. This adapter auto-negotiatesconnections of 1-Gbps, 2-Gbps, or 4-Gbps. Two SFP multimode optical portswith LC connectors support the following cable lengths:

Table 29. Quad-port 4-Gbps Fibre Channel Target adapter (PCIe) (FC 1030) -maximum cable lengths






For the single-node model the maximum number of this adapter is four. Forthe dual-node model the maximum number of this adapter is eight.


This adapter is a PCIe adapter. For a single-node configuration, the slotpriority order is 3, 4, 2. For a dual-node configuration, the slot priority orderis 1, 2, 4.

Note: Feature code 1030 requires Data ONTAP 7.3 or higher.

Dual-port 10 GbE Ethernet adapter (FC 1031)

Feature code 1031 is a 10-Gb Ethernet PCIe TOE adapter feature that providesdual LC duplex connectors. It supports a maximum distance of 300 metersusing 850-nanometer (nm) multimode fiber (MMF) media.



Dual-port MetroCluster VI HBA (Models A20/A21/A22 only) (FC 1032)

Feature code 1032 is used for fabric MetroCluster installations only. It isrequired by MetroCluster. In a fabric MetroCluster configuration, theMetroCluster Remote advanced function authorization and IBM 2005-16BFibre Channel switches are required. In a fabric MetroCluster configuration,the cluster interconnect traffic is carried across the Fibre Channel SAN via thisadapter instead of across the normal Infiniband (IB) cluster interconnectcables.

In a fabric MetroCluster configuration, two of these adapter cards must beordered (one for each node of a dual-node cluster).

This adapter must be installed in slot 1.

SnapMirror over Fibre Channel HBA (FC 1033)

Feature code 1033 is a 4-Gbps PCIe card used to support SnapMirror overFibre Channel.

For a single-node model, the maximum number of this adapter is one. For adual-node model, the maximum number of this adapter is two.

The slot priority order for this adapter is 3, 4.


Quad-port 4-Gbps Fibre Channel HBA for tape and disk attachment (FC 1035)

Feature code 1035 is a PCIe quad-port 4-Gbps HBA for attaching tape andsupported N series disk storage expansion units (EXN1000, EXN2000, andEXN4000) to N series storage controllers. This adapter auto-negotiatesconnections of 1-Gbps, 2-Gbps, or 4-Gbps. Four small form factor (SFF)multimode optical ports with LC connectors support the following cablelengths:

Table 30. Quad-port 4-Gbps Fibre Channel HBA for tape and disk attachment (FC1035) - maximum cable lengths






The ports of this adapter may not be used as FCP target ports.

Note: This adapter is not supported for N6000 series MetroClusterconfigurations or filers with gateway features.



Dual-port 8-Gbps Fibre Channel target HBA (FC 1036)

Feature code 1036 is a dual-port 8-Gbps Fibre Channel HBA for FCP targetports.

This adapter may only be used to provide additional target ports. It is notused for attaching N series storage expansion units. It auto-negotiatesconnections of 1-Gbps, 2-Gbps, or 4-Gbps.

This adapter has two SFP multimode optical ports with LC connectors. Thisadapter supports the following cable lengths:

Table 31. Dual-port 8-Gbps Fibre Channel target HBA (FC 1036) - maximum cablelengths





Table 31. Dual-port 8-Gbps Fibre Channel target HBA (FC 1036) - maximum cablelengths (continued)







16 GB Performance Acceleration Module (FC 1056)

Feature code 1056 is a PCIe adapter with 16 GB of onboard cache memorythat works as a performance acceleration module. It is designed to augmentthe system’s memory and improve performance with some applications whena configuration has a limited number of disks. This design allows the N seriesdisk configuration to be sized based on capacity, rather than performancerequirements. For more information about PAM cards, see Appendix D,“Installing or replacing a Performance Acceleration Module,” on page 109.

Use of the 16 GB Performance Acceleration Module I (FC 1056) requires theFlexScale software feature.

For the single-node model, the maximum number of this adapter is four forthe N6070 and two for the N6040 or N6060. For the dual-node model, themaximum number of this adapter is four.

This adapter is a PCIe adapter. For both single-node and dual-nodeconfigurations, the slot priority order is 1, 2. 3. 4.

Note: Feature code 1056 requires Data ONTAP 7.3 or higher.

512 GB Performance Acceleration Module II (FC 1057)

Feature code 1057 is a PCIe adapter with 512 GB of onboard cache memorythat works as a Performance Acceleration Module (PAM) II. The PerformanceAcceleration Module (PAM) II is the second generation of PCIe PAM adaptersfor N series systems. It is designed to augment the system’s onboard memory,improving performance with some configurations. The design allows the Nseries system to be sized based on required capacity instead of performance,reducing the need for excess spindles in some environments and helping to


improve capacity utilization. For more information about PAM cards, seeAppendix D, “Installing or replacing a Performance Acceleration Module,” onpage 109.

Use of the 512 GB Performance Acceleration Module II (FC 1057) requires thePerformance Acceleration Module II software feature.

For the single-node N6070, the maximum number of this adapter is two. Forthe dual-node N6070, the maximum number of this adapter is four.

This adapter is a PCIe adapter. For both single-node and dual-nodeconfigurations, the slot priority order is 1, 2, 3, 4.

Note: Feature code 1057 requires Data ONTAP 7.3.2 or higher.

256 GB Performance Acceleration Module II (FC 1058)

Feature code 1058 is a PCIe adapter with 256 GB of onboard cache memorythat works as a Performance Acceleration Module (PAM) II. The PerformanceAcceleration Module (PAM) II is the second generation of PCIe PAM adaptersfor N series systems. It is designed to augment the system’s onboard memory,improving performance with some configurations. The design allows the Nseries system to be sized based on required capacity instead of performance,reducing the need for excess spindles in some environments and helping toimprove capacity utilization. For more information about PAM cards, seeAppendix D, “Installing or replacing a Performance Acceleration Module,” onpage 109.

Use of the 256 GB Performance Acceleration Module II (FC 1058) requires thePerformance Acceleration Module II software feature.

For the single-node N6040, the maximum number of this adapter is one. Forthe dual-node N6040, the maximum number of this adapter is two.

For the single-node N6060, the maximum number of this adapter is two. Forthe dual-node N6060, the maximum number of this adapter is four.



Quad-port 3-Gbps SAS Adapter (FC 1061)

Feature code 1061 is a PCIe adapter with four SAS ports for connecting Nseries SAS-based storage (EXN3000) behind the N series controller. The SASadapter operates at 3 Gbps.





Dual-port Fibre Channel over Ethernet (FCoE) Target Adapter (optical) (FC 1063)

Feature code 1063 is a PCIe adapter with two Fibre Channel over Ethernet(FCoE) ports for connecting the N series controller to FCoE environments.This adapter utilizes optical connections to the FCoE networks.




Dual-port Fibre Channel over Ethernet (FCoE) Target Adapter (copper) (FC 1064)

Feature code 1064 is a PCIe adapter with two Fibre Channel over Ethernet(FCoE) ports for connecting the N series controller to FCoE environments.This adapter utilizes copper connections to the FCoE networks.




Dual-port 10-Gbps NIC (FC 1065)

Feature code 1065 is a 10-Gb Ethernet PCIe NIC adapter feature provides dualLC duplex connectors. It supports a maximum distance of 300 meters using850-nanometer (nm) multimode fiber (MMF) media.

Cable features 5m 50-micron MMF Cable (FC 1045), 30m 50-micron MMFCable (FC 1046), 10-GbE Fi cable 30m LC/SC (FC 1047), or 10-GbE Fi cable5m LC/SC (FC 1048) can optionally be ordered with this feature. FC 1045 andFC 1046 are LC/LC cables; FC 1047 and FC 1048 are LC/SC cables.



Appendix D. Installing or replacing a PerformanceAcceleration Module

This section contains information and processes for the following:v “System requirements”v “Before you begin”v “Installing or replacing a Performance Acceleration Module” on page 110v “Enabling the WAFL extended cache software license and functionality” on

page 111v “Enabling the WAFL extended cache configuration options” on page 112v “Completing the replacement process” on page 113

For information about the Performance Acceleration Module (PAM) LEDs,refer to the IBM System Storage N series Platform Monitoring Guide or to theflyer that shipped with your PAM.

System requirements

Your system must be running the minimum version of Data ONTAP requiredfor your module type. For the most up-to-date information about supportedData ONTAP versions for your module, see the IBM System Storage N seriesIntroduction and Planning Guide or the Hardware and Service Guide for your Nseries system, located at:

www.ibm.com/storage/support/nas

Before you begin

Depending on whether you are installing a Performance Acceleration Modulefor the first time, replacing an existing module, or installing an additionalmodule, your system must meet the criteria specified for your applicableinstallation type below.

First time installations:v Your system must be running the minimum version of Data ONTAP

required for the module type you are installing.v The platform on which you are installing the module must be supported.

The following platforms are supported; however, for the most up-to-datelist of supported platforms, see the IBM System Storage N series Introductionand Planning Guide or the Hardware and Service Guide for your N seriessystem, located at:



www.ibm.com/storage/support/nasv Your system must have an available PCI-e slot (one slot for each module),

and you must have checked the IBM System Storage N series Introduction andPlanning Guide or the Hardware and Service Guide for your N series system.

v You must have the software license key and download instructions thatcame with your order.

v If you are installing the module in an active/active or high availabilityconfiguration, you must install an equal number of modules in each system.

v All other components in the system must be functioning properly.

Replacement or additional module installationsv Your system must be running the minimum version of Data ONTAP

required for the module type you are installing.v If you are installing additional modules in an active/active or high

availability configuration, you must install an equal number of modules ineach system.

v If you are installing additional modules, your system must have anavailable PCI-e slot (one slot for each module), and you must have checkedthe IBM System Storage N series Introduction and Planning Guide or theHardware and Service Guide for your N series system for the assignedmodule slots for your system.

v If you are installing additional modules, they must be the same typemodule as you currently have installed.You cannot mix 16-GB, 256-GB, and 512-GB modules in the same system.

v If you are upgrading the 16-GB modules in your system with 256-GB or512-GB modules, you must have the correct software license for yourreplacement module type.There are two different WAFL® extended cache software licenses. One isused with the 16-GB module and one is used with the 256-GB and 512-GBmodules.

v All other components in the system must be functioning properly.

Installing or replacing a Performance Acceleration Module

Attention: This procedure is disruptive for single-controller configurations,and is recommended to be performed on single-controller configurations onlyduring a maintenance window. For active/active or high availabilityconfigurations, this is a nondisruptive procedure.

To install or replace a module, complete the following steps:1. Shut down the controller module.

See the Hardware and Service Guide for your applicable platform.2. Open your system.



See the Hardware and Service Guide for your applicable platform.3. Remove an existing module (if necessary).

See the Hardware and Service Guide for your applicable platform. Fordetailed information, see the section “Replacing PCI Cards and Risers” or“Replacing PCI adapters”.

4. Install the module.See the Hardware and Service Guide for your applicable platform. Fordetailed information, see the section “Replacing PCI Cards and Risers” or“Replacing PCI adapters”.

Note: For active/active or high availability configurations, if you areinstalling a module for the first time or adding an additionalmodule, you must install an equal number of modules in eachnode.

5. Close and boot your system.See the Hardware and Service Guide for your applicable platform.

6. Run diagnostics on the new module (for first time installations only).See the IBM System Storage N series Diagnostics Guide for informationabout specific diagnostics tests you can perform for PCI cards, located at:www.ibm.com/storage/support/nas

7. Complete the installation process:v If you are installing an additional module in a system with preexisting

modules, you have completed the installation process.v If you are replacing a failed module, go to step 10.v If you are installing a module for the first time in a system or

upgrading the 16-GB modules in your system with 256-GB or 512-GBmodules, complete steps 8 and 9.

8. Enable the WAFL extended cache software.See “Enabling the WAFL extended cache software license andfunctionality.”

9. Set the software configuration options.See “Enabling the WAFL extended cache configuration options” on page112.

10. Complete the replacement process.See “Completing the replacement process” on page 113.

Enabling the WAFL extended cache software license and functionality

For first-time installations of a module or upgrading the 16-GB modules inyour system with 256-GB or 512-GB modules, complete the following steps:

Appendix D. Installing or replacing a Performance Acceleration Module 111


Note: There are two different WAFL extended cache software licenses. One isused with the 16-GB module and one is used with the 256-GB and512-GB modules. You must have the correct software license for yourmodule type.

Note: See the software license key and download instructions that came withyour order.

1. From the console, enable the WAFL extended cache software license byentering the following command:license add license key

Result: WAFL extended cache functionality should be enabledautomatically.

2. Verify that WAFL extended cache functionality is enabled by entering thefollowing command:options flexscale.enable

Result: Should be on.3. Enable the WAFL extended cache configuration options.v If your system is in a single-controller module configuration, go to

“Enabling the WAFL extended cache configuration options.”v If your system is in an active/active or high availability configuration,

repeat Steps 1 and 2 of this procedure for each node, and then go to“Enabling the WAFL extended cache configuration options.”

Enabling the WAFL extended cache configuration options

WAFL extended cache configuration options enable you to optimizeperformance for your particular workload. Depending on your workload, thefollowing options can apply:v Caching normal user data blocksv Caching low-priority user data blocksv Caching only system metadatav Integrating FlexShare™ buffer cache policies with WAFL extended cache

options

Note: You can set the WAFL extended cache configuration options duringmodule installation or later. However, it is recommended that you setoptions at the time of installation to ensure optimal performance foryour workload.

To enable WAFL extended cache configuration options, complete the followingsteps:


1. Read about the WAFL extended cache configuration options in the DataONTAP System Administration Guide.You can access this document at:www.ibm.com/storage/support/nas

Note: Knowing your application and volume configuration helps youdecide what configuration options to choose.

2. Follow the applicable option enabling procedures in the Data ONTAPSystem Administration Guide.

Note: For active/active or high availability configurations, you mustconfigure options on each node.

Completing the replacement process

If you have replaced a failed module, return the failed part to IBM. ContactIBM Service and Support at 1-800-IBM-SERV (1-800-426-7378) for moreinformation on the return procedure.

Appendix D. Installing or replacing a Performance Acceleration Module 113


Appendix E. IBM System Storage N series documentation

The following lists present an overview of the IBM System Storage N serieshardware and Data ONTAP product libraries, as well as other relateddocuments.

You can access the documents listed in these tables at the following web site:


N7000 series systems library

v IBM System Storage N7000 Series Hardware and Service Guide, GC26-7953v IBM System Storage N7000 Series Filer Installation and Setup Instructions,

GC26-7954v IBM System Storage N7000 Series Gateway Installation and Setup Instructions,

GC26-7956


v IBM System Storage N6000 Series Hardware and Service Guide, GC53-1142-00v IBM System Storage N6000 Series Filer Installation and Setup Instructions,

GC53-1143-00v IBM System Storage N6000 Series Gateway Installation and Setup Instructions,

GC53-1144-00


v IBM System Storage N5000 Series Hardware and Service Guide, GC26-7785v IBM System Storage N5000 Series Filer Installation and Setup Instructions,

GC26-7784v IBM System Storage N5000 Series Gateway Installation and Setup Instructions,

GC26-7838

N3300 and N3600 storage systems library

v IBM System Storage N3300 and N3600 Hardware and Service Guide, GC27-2087v IBM System Storage N3300 Installation and Setup Instructions, GC27-2086v IBM System Storage N3600 Installation and Setup Instructions, GC27-2089



N3700 storage system library

v IBM System Storage N3700 Hardware and Service Guide, GA32-0515v IBM System Storage N3700 Installation and Setup Instructions, GA32-0517

EXN1000, EXN2000, EXN3000and EXN4000 storage expansion units library

v IBM System Storage EXN1000 Storage Expansion Unit Hardware and ServiceGuide, GC26-7802

v IBM System Storage EXN1000 Installation and Setup Instructions, GC26-7786v IBM System Storage EXN2000 Storage Expansion Unit Hardware and Service

Guide, GA32-0516v IBM System Storage EXN2000 Installation and Setup Instructions, GC27-2064v IBM System Storage EXN3000 Storage Expansion Unit Hardware and Service

Guide, GC52-1346v IBM System Storage EXN3000 Installation and Setup Instructions, GC52-1345v IBM System Storage EXN4000 Storage Expansion Unit Hardware and Service

Guide, GC27-2080v IBM System Storage EXN4000 Installation and Setup Instructions, GC27-2079

Data ONTAP 7.3 filer library

v IBM System Storage N series Data ONTAP 7.3.x Release Notes®, GC53-1175

Note: Beginning with Data ONTAP 7.3.1, a single Data ONTAP 7.3.xRelease Notes covers both filers and gateways.

v IBM System Storage N series Data ONTAP 7.3.Release Notes, GC27-2201v IBM System Storage N series Data ONTAP 7.3 Active/Active Configuration

Guide, GC27-2208v IBM System Storage N series Data ONTAP 7.3 File Access and Protocols

Management Guide, GC27-2207v IBM System Storage N series Data ONTAP 7.3 Storage Management Guide,

GC52-1277v IBM System Storage N series Data ONTAP 7.3 Data Protection Online Backup

and Recovery Guide, GC27-2204v IBM System Storage N series Data ONTAP 7.3 Data Protection Tape Backup and

Recovery Guide, GC27-2205v IBM System Storage N series Data ONTAP 7.3 MultiStore Management Guide,

GC52-1281v IBM System Storage N series Data ONTAP 7.3 Network Management Guide,

GC52-1280


v IBM System Storage N series Data ONTAP 7.3 Commands: Manual PageReference, Volume 1, GC27-2202

v IBM System Storage N series Data ONTAP 7.3 Commands: Manual PageReference, Volume 2, GC27-2203

v IBM System Storage N series Data ONTAP 7.3 Upgrade Guide, GC27-2200v IBM System Storage N series Data ONTAP 7.3 Block Access Management Guide

for iSCSI and FCP, GC52-1282v IBM System Storage N series Data ONTAP 7.3 System Administration Guide,

GC52-1279v IBM System Storage N series Data ONTAP 7.3 Software Setup Guide,

GC27-2206v IBM System Storage N series Data ONTAP 7.3 Core Commands Quick Reference,

GC52-1278v IBM System Storage N series Data ONTAP 7.3 Archive and Compliance

Management Guide, GC53-1168


v IBM System Storage N series Data ONTAP 7.2.x Release Notes, GC26-7963v IBM System Storage N series Data ONTAP 7.2 Active/Active Configuration

Guide, GC26-7964v IBM System Storage N series Data ONTAP 7.2 File Access and Protocols

Management Guide, GC26-7965v IBM System Storage N series Data ONTAP 7.2 Storage Management Guide,

GC26-7966v IBM System Storage N series Data ONTAP 7.2 Data Protection Online Backup

and Recovery Guide, GC26-7967v IBM System Storage N series Data ONTAP 7.2 Data Protection Tape Backup and

Recovery Guide, GC26-7968v IBM System Storage N series Data ONTAP 7.2 MultiStore Management Guide,

GC26-7969v IBM System Storage N series Data ONTAP 7.2 Network Management Guide,

GC26-7970v IBM System Storage N series Data ONTAP 7.2 Commands: Manual Page

Reference, Volume 1, GC26-7971v IBM System Storage N series Data ONTAP 7.2 Commands: Manual Page

Reference, Volume 2, GC26-7972v IBM System Storage N series Data ONTAP 7.2 Upgrade Guide, GC26-7976v IBM System Storage N series Data ONTAP 7.2 Block Access Management Guide

for iSCSI & FCP, GC26-7973

Appendix E. IBM System Storage N series documentation 117

v IBM System Storage N series Data ONTAP 7.2 System Administration Guide,GC26-7974

v IBM System Storage N series Data ONTAP 7.2 Software Setup Guide,GC26-7975

v IBM System Storage N series Data ONTAP 7.2 Core Commands Quick Reference,GC26-7977


v IBM System Storage N series Data ONTAP 7.1.x Release Notes, GC26-7862v IBM System Storage N series Data ONTAP 7.1 Cluster Installation and

Management Guide, GC26-7790v IBM System Storage N series Data ONTAP 7.1 File Access and Protocols

Management Guide, GA32-0520v IBM System Storage N series Data ONTAP 7.1 Storage Management Guide,

GA32-0521v IBM System Storage N series Data ONTAP 7.1 Data Protection Online Backup

and Recovery Guide, GA32-0522v IBM System Storage N series Data ONTAP 7.1 Data Protection Tape Backup and

Recovery Guide, GA32-0523v IBM System Storage N series Data ONTAP 7.1 MultiStore Management Guide,

GA32-0524v IBM System Storage N series Data ONTAP 7.1 Network Management Guide,

GA32-0525v IBM System Storage N series Data ONTAP 7.1 Commands: Manual Page

Reference, Volume 1, GA32-0526v IBM System Storage N series Data ONTAP 7.1 Commands: Manual Page

Reference, Volume 2, GA32-0527v IBM System Storage N series Data ONTAP 7.1 Upgrade Guide, GC26-7791v IBM System Storage N series Data ONTAP 7.1 Block Access Management Guide

for iSCSI and FCP, GA32-0528v IBM System Storage N series Data ONTAP 7.1 System Administration Guide,

GA32-0529v IBM System Storage N series Data ONTAP 7.1 Software Setup Guide,

GA32-0530v IBM System Storage N series Data ONTAP 7.1 Core Commands Quick Reference,

GA32-0531

Data ONTAP 7.2 and 7.3 gateway systems library

v IBM System Storage N series Data ONTAP 7.2.x Gateway Release Notes,GC26-7955


v IBM System Storage N series Data ONTAP 7.3 Gateway Release Notes,GC27-2189

v IBM System Storage N series Data ONTAP 7.3.x Release Notes, GC53-1175

Note: Beginning with Data ONTAP 7.3.1, a single Data ONTAP 7.3.xRelease Notes will cover both filers and gateways.

v IBM System Storage N series Gateway Planning Guide, GC53-1150v IBM System Storage N series Gateway Upgrade Guide, GC26-1166v IBM System Storage N series Gateway Software Setup, Installation, and

Management Guide, GC53-1147v IBM System Storage N series Gateway Installation Requirements and Reference

Guide, GC53-1148v IBM System Storage N series Gateway Metrocluster Guide, GC53-1149v IBM System Storage N series Gateway Implementation Guide for Native Disk

Shelves, GC27-2188 (for Data ONTAP 7.3 gateways only)v IBM System Storage N series Gateway Implementation Guide for EMC Symmetrix

Storage, GC27-2190v IBM System Storage N series Gateway Implementation Guide for HP EVA

Storage, GC27-2192v IBM System Storage N series Gateway Implementation Guide for HP XP Storage,

GC27-2193v IBM System Storage N series Gateway Implementation Guide for 3PAR InServ

Storage, GC27-2195v IBM System Storage N series Gateway Implementation Guide for EMC

CLARiiON Storage, GC27-2191v IBM System Storage N series Gateway Implementation Guide for IBM Storage,

GC27-2194v IBM System Storage N series Gateway Implementation Guide for IBM SAN

Volume Controller Storage, GC53-1151v IBM System Storage N series Gateway Implementation Guide for Hitachi Storage,

GC53-1164v IBM System Storage N series Gateway Implementation Guide for Fujitsu

ETERNUS Storage, GC53-1165v IBM System Storage N series Gateway Implementation Guide for RamSan Storage,

GC52-1342

Data ONTAP 7.1 gateway systems library

v IBM System Storage N series Gateway Planning Guide, GC26-7839v IBM System Storage N series Gateway Integration Guide for IBM Storage,

GC26-7840

Appendix E. IBM System Storage N series documentation 119

v IBM System Storage N series Gateway Integration Guide for Hitachi Storage,GC26-7841

v IBM System Storage N series Gateway Integration Guide for HP Storage,GC26-7858

v IBM System Storage N series Gateway Software Upgrade Guide, GC26-7859v IBM System Storage N series Gateway Software Setup, Installation, and

Management Guide, GC26-7886v IBM System Storage N series Gateway 7.1.x Release Notes, GC26-7837

Other N series and N series-related documents

v IBM System Storage N Series Platform Monitoring Guide, GC27-2088(previously called the IBM System Storage N series Error Messages andTroubleshooting Guide, GC26-7984)

v IBM System Storage N series Diagnostics Guide, GC26-7789v IBM System Storage N series Introduction and Planning Guide, GA32-0543v IBM System Storage N series AutoSupport Overview, GC26-7854v IBM System Storage N series: Changing the cluster cfmode Setting in Fibre

Channel SAN Configurations, GC26-7876v IBM System Storage N series iSCSI and Fibre Channel Configuration Guide,

GC53-1300v IBM System Storage N series Brocade 200E and Brocade 5000 Switch

Configuration Guide, GC52-1284v IBM System Storage N series Brocade 3000 Series Switch Configuration Guide,

GC52-1285v IBM System Storage N series Brocade 300 and Brocade 5100 Switch Configuration

Guide, GC53-1167v IBM System Storage N series MetroCluster Redbook, REDP-4243-00v IBM System Storage Systems Safety Notices, G229-9054v IBM Environmental Notices and User Guide Z125-5823v IBM Storage Solution Rack 2101 Rack Installation and Service Guide: Models 200

and N00, GC26-7993v IBM Storage Solution Rack 2101 Rack Installation and Service Guide: Model N42,

GC53-1174


Notices

This information was developed for products and services offered in theU.S.A.

IBM may not offer the products, services, or features discussed in thisdocument in other countries. Consult your local IBM representative forinformation on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state orimply that only that IBM product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe onany IBM intellectual property right may be used instead. However, it is theuser’s responsibility to evaluate and verify the operation of any non-IBMproduct, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not giveyou any license to these patents. You can send license inquiries, in writing to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, N.Y. 10504-1785U.S.A.

For additional information, visit the web at:http://www.ibm.com/ibm/licensing/contact/

The following paragraph does not apply to the United Kingdom or anyother country where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITYOR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allowdisclaimer of express or implied warranties in certain transactions, therefore,this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes willbe incorporated in new editions of the publication. IBM may makeimprovements and/or changes in the product(s) and/or the program(s)described in this publication at any time without notice.


http://www.ibm.com/ibm/licensing/contact/

Any references in this information to non-IBM web sites are provided forconvenience only and do not in any manner serve as an endorsement of thoseweb sites. The materials at those web sites are not part of the materials forthis IBM product and use of those web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environmentsmay vary significantly. Some measurements may have been made ondevelopment-level systems and there is no guarantee that these measurementswill be the same on generally available systems. Furthermore, somemeasurement may have been estimated through extrapolation. Actual resultsmay vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly availablesources. IBM has not tested those products and cannot confirm the accuracyof performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should beaddressed to the suppliers of those products.

If you are viewing this information in softcopy, the photographs and colorillustrations may not appear.

Trademarks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, othercountries, or both. A complete and current list of other IBM trademarks isavailable on the web at http://www.ibm.com/legal/copytrade.shtml

NetApp, the Network Appliance logo, the bolt design, NetApp–the NetworkAppliance Company, Data ONTAP, DataFabric, FAServer, FilerView,MultiStore, NearStore, NetCache, SecureShare, SnapManager, SnapMirror,SnapMover, SnapRestore, SnapVault, SyncMirror, and WAFL are registeredtrademarks of Network Appliance, Inc. in the United States, and/or othercountries. gFiler, Network Appliance, SnapCopy, Snapshot, and The Evolutionof Storage are trademarks of Network Appliance, Inc. in the United Statesand/or other countries and registered trademarks in some other countries.ApplianceWatch, BareMetal, Camera-to-Viewer, ComplianceClock,ComplianceJournal, ContentDirector, ContentFabric, EdgeFiler, FlexClone,FlexVol, FPolicy, HyperSAN, InfoFabric, LockVault, Manage ONTAP, NOW,NetApp on the web, ONTAPI, RAID-DP, RoboCache, RoboFiler, SecureAdmin,


http://www.ibm.com/legal/copytrade.shtml

Serving Data by Design, SharedStorage, Simulate ONTAP, Smart SAN,SnapCache, SnapDirector, SnapDrive, SnapFilter, SnapLock, SnapMigrator,SnapSuite, SnapValidator, SohoFiler, vFiler, VFM, Virtual File Manager,VPolicy, and Web Filer are trademarks of Network Appliance, Inc. in theUnited States and other countries. NetApp Availability Assurance andNetApp ProTech Expert are service marks of Network Appliance, Inc. in theUnited States. Spinnaker Networks, the Spinnaker Networks logo, SpinAccess,SpinCluster, SpinFS, SpinHA, SpinMove, and SpinServer are registeredtrademarks of Spinnaker Networks, LLC in the United States and/or othercountries. SpinAV, SpinManager, SpinMirror, SpinRestore, SpinShot, andSpinStor are trademarks of Spinnaker Networks, LLC in the United Statesand/or other countries.

Network Appliance is a licensee of the CompactFlash and CF Logotrademarks.

Network Appliance NetCache is certified RealSystem compatible.

Microsoft®, Windows, and Windows NT® are trademarks of MicrosoftCorporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States andother countries.

Other company, product, or service names may be trademarks or servicemarks of others.

Important notes

Processor speeds indicate the internal clock speed of the microprocessor; otherfactors also affect application performance.

CD-ROM drive speeds list the variable read rate. Actual speeds vary and areoften less than the maximum possible.

When referring to processor storage, real and virtual storage, or channelvolume, KB stands for approximately 1000 bytes, MB stands forapproximately 1 000 000 bytes, and GB stands for approximately 1 000 000 000bytes.

When referring to hard disk drive capacity or communications volume, MBstands for 1 000 000 bytes, and GB stands for 1 000 000 000 bytes. Totaluser-accessible capacity may vary depending on operating environments.

Notices 123

Maximum internal hard disk drive capacities assume the replacement of anystandard hard disk drives and population of all hard disk drive bays with thelargest currently supported drives available from IBM.

Maximum memory may require replacement of the standard memory with anoptional memory module.

IBM makes no representation or warranties regarding non-IBM products andservices that are ServerProven®, including but not limited to the impliedwarranties of merchantability and fitness for a particular purpose. Theseproducts are offered and warranted solely by third parties.

IBM makes no representations or warranties with respect to non-IBMproducts. Support (if any) for the non-IBM products is provided by the thirdparty, not IBM.

Some software may differ from its retail version (if available), and may notinclude user manuals or all program functionality.

Attention: In compliance with the GNU General Public License (GPL),Version 2, June 1991, a complete machine-readable copy of the source code forthe relevant source code portions of the Remote LAN Module (RLM)Firmware that are covered by the GPL, is available from http://now.netapp.com.

Electronic emission notices

The following statements apply to this product. The statements for otherproducts intended for use with this product will appear in theiraccompanying manuals.

Federal Communications Commission (FCC) Class A StatementNote: This equipment has been tested and found to comply with the limits fora Class A digital device, pursuant to Part 15 of the FCC Rules. These limitsare designed to provide reasonable protection against harmful interferencewhen the equipment is operated in a commercial environment. Thisequipment generates, uses, and can radiate radio frequency energy and, if notinstalled and used in accordance with the instruction manual, may causeharmful interference to radio communications. Operation of this equipment ina residential area is likely to cause harmful interference, in which case theuser will be required to correct the interference at his own expense.

Properly shielded and grounded cables and connectors must be used in orderto meet FCC emission limits. IBM is not responsible for any radio or televisioninterference caused by using other than recommended cables and connectors


or by unauthorized changes or modifications to this equipment. Unauthorizedchanges or modifications could void the user’s authority to operate theequipment.

This device complies with Part 15 of the FCC Rules. Operation is subject tothe following two conditions: (1) this device may not cause harmfulinterference, and (2) this device must accept any interference received,including interference that may cause undesired operation.

Industry Canada Class A Emission Compliance StatementThis Class A digital apparatus complies with Canadian ICES-003.

Avis de conformité à la réglementation d’Industrie CanadaCet appareil numérique de la classe A est conform à la norme NMB-003 duCanada.

European Union (EU) Electromagnetic Compatibility DirectiveThis product is in conformity with the protection requirements of EU CouncilDirective 2004/108/EC on the approximation of the laws of the MemberStates relating to electromagnetic compatibility. IBM cannot acceptresponsibility for any failure to satisfy the protection requirements resultingfrom a non-recommended modification of the product, including the fitting ofnon-IBM option cards.

This product has been tested and found to comply with the limits for Class AInformation Technology Equipment according to European Standard EN55022. The limits for Class A equipment were derived for commercial andindustrial environments to provide reasonable protection against interferencewith licensed communication equipment.

Attention: This is a Class A product. In a domestic environment this productmay cause radio interference in which case the user may be required to takeadequate measures.

European Community contact:IBM Technical RegulationsPascalstr. 100, Stuttgart, Germany 70569Tele: 0049 (0)711 785 1176Fax: 0049 (0)711 785 1283e-mail: [email protected]

Germany Electromagnetic Compatibility DirectiveDeutschsprachiger EU Hinweis:

Hinweis für Geräte der Klasse A EU-Richtlinie zur ElektromagnetischenVerträglichkeit

Notices 125

Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie2004/108/EG zur Angleichung der Rechtsvorschriften über dieelektromagnetische Verträglichkeit in den EU-Mitgliedsstaaten und hält dieGrenzwerte der EN 55022 Klasse A ein.

Um dieses sicherzustellen, sind die Geräte wie in den Handbüchernbeschrieben zu installieren und zu betreiben. Des Weiteren dürfen auch nurvon der IBM empfohlene Kabel angeschlossen werden. IBM übernimmt keineVerantwortung für die Einhaltung der Schutzanforderungen, wenn dasProdukt ohne Zustimmung der IBM verändert bzw. wennErweiterungskomponenten von Fremdherstellern ohne Empfehlung der IBMgesteckt/eingebaut werden.

EN 55022 Klasse A Geräte müssen mit folgendem Warnhinweis versehenwerden:“Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kannim Wohnbereich Funk-Störungen verursachen; in diesem Fall kann vomBetreiber verlangt werden, angemessene Maßnahmen zu ergreifen und dafüraufzukommen.“

Deutschland: Einhaltung des Gesetzes über die elektromagnetischeVerträglichkeit von Geräten

Dieses Produkt entspricht dem “Gesetz über die elektromagnetischeVerträglichkeit von Geräten (EMVG)“. Dies ist die Umsetzung derEU-Richtlinie 2004/108/EG in der Bundesrepublik Deutschland.

Zulassungsbescheinigung laut dem Deutschen Gesetz über dieelektromagnetische Verträglichkeit von Geräten (EMVG) (bzw. der EMC EGRichtlinie 2004/108/EG) für Geräte der Klasse A

Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVGdas EG-Konformitätszeichen - CE - zu führen. Verantwortlich für dieKonformitätserklärung des EMVG ist die IBM Deutschland GmbH, 70548Stuttgart.

Generelle Informationen:

Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022Klasse A.


People’s Republic of China Class A Electronic Emission Statement

Japan VCCI Class A ITE Electronic Emission Statement

Taiwan Class A warning statement

Korea Class A Electronic Emission Statement

Power cords

For your safety, IBM provides a power cord with a grounded attachment plugto use with this IBM product. To avoid electrical shock, always use the powercord and plug with a properly grounded outlet.

Notices 127

IBM power cords used in the United States and Canada are listed byUnderwriter’s Laboratories (UL) and certified by the Canadian StandardsAssociation (CSA).

For units intended to be operated at 115 volts: Use a UL-listed andCSA-certified cord set consisting of a minimum 18 AWG, Type SVT or SJT,three-conductor cord, a maximum of 15 feet in length and a parallel blade,grounding-type attachment plug rated 15 amperes, 125 volts.

For units intended to be operated at 230 volts (U.S. use): Use a UL-listed andCSA-certified cord set consisting of a minimum 18 AWG, Type SVT or SJT,three-conductor cord, a maximum of 15 feet in length and a tandem blade,grounding-type attachment plug rated 15 amperes, 250 volts.

For units intended to be operated at 230 volts (outside the U.S.): Use a cordset with a grounding-type attachment plug. The cord set should have theappropriate safety approvals for the country in which the equipment will beinstalled.

IBM power cords for a specific country or region are usually available only inthat country or region.


Index

Aabout this document xxiii

how to send your comments xxixAC power line sizes 91AC power supplies, connecting N6000 series system

to 15active/active or high availability configuration

tasks 25adapter, DB-9 to RJ-45 console 22adapters

cabling 16optional cards

N6000 series system 97ASCII terminal console connection 21, 22attention notice

definition viiexample vii

Bbooting your system 25

Ccaution notices vi

definition viclearance dimensions 3clustered configuration tasks 25comments

sending xxixCompactFlash card

replacing 78configuring for an active/active or high availability

configuration 25configuring the Fibre Channel port 27connections

ASCII terminal console 21, 22console 22filer to storage expansion unit 16gateway to external storage 20N6000 series system 13storage 15third-party devices 21to a power source 15to an IP network 13using a Fibre Channel expansion adapter 16using an optional adapter card 16

controller modulereplacing 38shutting down 34

conventionscommand xxviiformatting xxviikeyboard xxviii

Ddanger notices iii

definition iiiexample iii

Data ONTAP 7.1 filerdocumentation 118

Data ONTAP 7.1 gateway systems library 119Data ONTAP 7.2 and 7.3 gateway systems library 118Data ONTAP 7.2 filer

documentation 117Data ONTAP 7.3 filer

documentation 116DB-9 to RJ-45

console adapter 22pin connections 22

device carrier xxviiDIMMs

replacing 51documentation

Data ONTAP 7.1 filer 118Data ONTAP 7.1 gateway 119Data ONTAP 7.2 and 7.3 gateway 118Data ONTAP 7.2 filer 117Data ONTAP 7.3 filer 116EXN1000, EXN2000, EXN3000 and EXN4000 storage

expansion units 116IBM System Storage N series 113improvement xxixN series-related documents 120N3300 and N3600 storage system 115N3700 storage system 116N5000 series systems 115N6000 series systems 115N7000 series systems 115

dual-path Fibre Channel cabling 16

Ee0M interface 14electrical requirements

N6040 4, 5N6040 with PAM cards 5, 6N6060 6N6060 with PAM cards 7N6070 8N6070 with PAM cards 9


Electronic emission noticesTaiwanese Class A warning statement 127

environmental requirements 3EXN1000, EXN2000, EXN3000 and EXN4000 storage

expansion units library 116

Ffan module

replacing 48fiber-optic cable

handling 13Fibre Channel expansion adapters

cabling 16Fibre Channel port configuring 27filer, defined xxvifire suppression xiFRU/CRU list

feature codes 93

Ggateway

connecting to external storage 20gateway, defined xxvi

Hhandling static-sensitive devices 2hardware service and support xxvhardware specifications 3high availability configuration tasks 25how to send your comments xxix

IIBM safety information 120initiator mode 28installation

preparation for 1procedures for 11rack viiirules 10tools 1

intellectual property 121IP network 13

Llabels, safety vilaser safety viilicense, patents 121licensing

address 121Web address 121

NN series

related documents 120N series documentation 113

N series systemsetup worksheet 25

N3300 and N3600 storage system library 115N3700 storage system library 116N5000 series systems library 115N6000 series systems library 115N7000 series systems library 115notes, important 123notices

attention viicaution vidanger iiisafety iiitypes iii

NVRAM batteryreplacing 62

Ooptical port terminators viioptional adapter cards

cabling 16descriptions

N6000 series system 97

Ppatents 121PCIe card and riser

replacing 55physical characteristics 3power

separate circuit breakers for 15power cords 127

feature codes 93power line sizes 91power supplies 15power supply

replacing 60

Rrack installation viii

safety viiirack relocation

safety xrack safety viiireader feedback

sending xxixreal-time Clock (RTC) battery

replacing 67Remote LAN Module

replacing 71replacement

N6000 series system devices 33restrictions, usage viiRLM

configuring and using 29


Ssafety

labels iiilaser viinotices iiirack viiirack installation viiirack relocation x

safety labels vishipment package contents 9static-sensitive devices, handling 2system

closing 37opening 35

system setup worksheet 25

Ttasks by document title 113terminators

optical ports viiterminology xxvithird-party devices

rules for connecting 21trademarks 122

Uusage restrictions vii

Wweb sites, related xxvworksheets

system setup 25

Index 131

��

Printed in USA

GC53-1142-03

ibm n6k hardware and service guide

Documents