Professional Documents
Culture Documents
GA32-0838-01
GA32-0838-01
Note: Before using this information and the product it supports, be sure to read the general information in Notices on page 87.
The following paragraph does not apply to any country (or region) where such provisions are inconsistent with local law. INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states (or regions) do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you. Order publications through your IBM representative or the IBM branch office serving your locality. Copyright IBM Corporation 2011. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Safety notices
This section contains information about: v Safety notices and labels v Laser safety on page vi v Rack safety on page vii v Fire suppression systems on page ix For information about environmental notices, see the IBM Environmental Notices and User Guide.
Danger notices
A danger notice calls attention to a situation that is potentially lethal or extremely hazardous to people. A lightning bolt symbol accompanies a danger notice to represent a dangerous electrical condition. A sample danger notice follows.
DANGER An electrical outlet that is not correctly wired could place hazardous voltage on metal parts of the system or the devices that attach to the system. It is the responsibility of the customer to ensure that the outlet is correctly wired and grounded to prevent an electrical shock. (D004)
iii
A general danger notice provides instructions on how to avoid shock hazards when servicing equipment. Unless instructed otherwise, follow the procedures in the following danger notice.
DANGER When working on or around the system, observe the following precautions: Electrical voltage and current from power, telephone, and communication cables are hazardous. To avoid a shock hazard: v Connect power to this unit only with the IBM provided power cord. Do not use the IBM provided power cord for any other product. v Do not open or service any power supply assembly. v Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm. v The product might be equipped with multiple power cords. To remove all hazardous voltages, disconnect all power cords. v Connect all power cords to a properly wired and grounded electrical outlet. Ensure outlet supplies proper voltage and phase rotation according to the system rating plate. v Connect any equipment that will be attached to this product to properly wired outlets. v When possible, use one hand only to connect or disconnect signal cables. v Never turn on any equipment when there is evidence of fire, water, or structural damage. v Disconnect the attached power cords, telecommunications systems, networks, and modems before you open the device covers, unless instructed otherwise in the installation and configuration procedures. v Connect and disconnect cables as described below when installing, moving, or opening covers on this product or attached 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)
iv
Labels
As an added precaution, safety labels are often installed directly on products or product components to warn of potential hazards. The actual product safety labels may differ from these sample safety labels:
DANGER Hazardous voltage, current, or energy levels are present inside any component that has this label attached. Do not open any cover or barrier that contains this label. (L001)
DANGER Multiple power cords. The product might be equipped with multiple power cords. To remove all hazardous voltages, disconnect all power cords. (L003)
Caution notices
A caution notice calls attention to a situation that is potentially hazardous to people because of some existing condition. A caution notice can be accompanied by different symbols, as in the examples below:
If the symbol is... It means.... A hazardous electrical condition with less severity than electrical danger.
A hazardous condition due to the use of a laser in the product. Laser symbols are always accompanied by the classification of the laser as defined by the U. S. Department of Health and Human Services (for example, Class I, Class II, and so forth).
Attention notices
An attention notice indicates the possibility of damage to a program, device, or system, or to data. An exclamation point symbol may accompany an attention notice, but is not required. A sample attention notice follows:
Attention: Do not bend a fiber cable to a radius less than 5 cm (2 in.); you can damage the cable. Tie wraps are not recommended for optical cables because they can be easily overtightened, causing damage to the cable.
Safety notices
Laser safety
CAUTION: This product contains a Class 1M laser. Do not view directly with optical instruments. (C028)
This equipment contains Class 1 laser products, and complies with FDA radiation Performance Standards, 21 CFR Subchapter J and the international laser safety standard IEC 825-2.
CAUTION: Data processing environments can contain equipment transmitting on system links with laser modules that operate at greater than Class 1 power levels. For this reason, never look into the end of an optical fiber cable or open receptacle. (C027)
Attention: In the United States, use only SFP or GBIC optical transceivers that comply with the FDA radiation performance standards, 21 CFR Subchapter J. Internationally, use only SFP or GBIC optical transceivers that comply with IEC standard 8251. Optical products that do not comply with these standards may produce light that is hazardous to the eyes.
Usage restrictions
The optical ports of the modules must be terminated with an optical connector or with a dust plug.
vi
v Each rack cabinet might have more than one power cord. Be sure to disconnect all power cords in the rack cabinet when directed to disconnect power during servicing. v Connect all devices installed in a rack cabinet to power devices installed in the same rack cabinet. Do not plug a power cord from a device installed in one rack cabinet into a power device installed in a different rack cabinet. v An electrical outlet that is not correctly wired could place hazardous voltage on the metal parts of the system or the devices that attach to the system. It is the responsibility of the customer to ensure that the outlet is correctly wired and grounded to prevent an electrical shock.
(R001 part 1 of 2
Safety notices
vii
CAUTION: v Do not install a unit in a rack where the internal rack ambient temperatures will exceed the manufacturer's recommended ambient temperature for all your rack-mounted devices. v Do not install a unit in a rack where the air flow is compromised. Ensure that air flow is not blocked or reduced on any side, front, or back of a unit used for air flow through the unit. v Consideration should be given to the connection of the equipment to the supply circuit so that overloading of the circuits does not compromise the supply wiring or overcurrent protection. To provide the correct power connection to a rack, refer to the rating labels located on the equipment in the rack to determine the total power requirement of the supply circuit. v (For sliding drawers.) Do not pull out or install any drawer or feature if the rack stabilizer brackets are not attached to the rack. Do not pull out more than one drawer at a time. The rack might become unstable if you pull out more than one drawer at a time. v (For fixed drawers) This drawer is a fixed drawer and should not be moved for servicing unless specified by manufacturer. Attempting to move the drawer partially or completely out of the rack may cause the rack to become unstable or cause the drawer to fall out of the rack. (R001 part 2 of 2)
viii
Safety notices
ix
Contents
Safety notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Safety notices and labels . . Danger notices . . . . Labels . . . . . . . Caution notices . . . . Attention notices . . . . Laser safety . . . . . . Usage restrictions . . . Rack safety . . . . . . Rack installation . . . Rack relocation (19" rack) . Fire suppression systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii . iii . v . v . v . vi . vi . vii . vii . ix . ix
. . . . . . . . . . . . . . Fibre
. . . . . . . . . . . . . . . . . . . . . Channel
. . . . . . . . . . . . . . . . . . . . . . . . . . . . expansion
. . . . . . . . . . . . . . . . . . . . . adapter
. . . . . . . .
. . . . . . . .
. . . . . . . .
13 13 14 15 16 16 16 17
xi
Connecting a gateway to external storage . . . Connecting to a third-party device. . . . . . Rules for connecting the third-party devices . Connecting your system to an ASCII terminal console
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
19 19 19 20
. . . . . . . . . . . . . . . . 23
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . later releases in the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 26 26 27 28 28 28 29 30 30 30 30 31 32 32 34 36 37 37 38 40 40 40 40 40 41 42 42 44 44 45 47 47 47 47 48 49 49 50 51 51 53 54 54 55 55 56
Using the IBM N series support website . . . . . . . . . . . . . . . Replacing a fan module in an N6200 series system . . . . . . . . . . . Removing a fan module . . . . . . . . . . . . . . . . . . . Installing a fan module . . . . . . . . . . . . . . . . . . . Completing the replacement process . . . . . . . . . . . . . . . Replacing a power supply on an N6200 series system . . . . . . . . . . Removing a power supply . . . . . . . . . . . . . . . . . . Installing a power supply . . . . . . . . . . . . . . . . . . Completing the replacement process . . . . . . . . . . . . . . . Replacing an NVMEM battery and NVMEM DIMMs in an N6200 series system . Shutting down the node . . . . . . . . . . . . . . . . . . . Shutting down a node in an HA pair . . . . . . . . . . . . . . Shutting down the node in a stand-alone system . . . . . . . . . . Opening the system . . . . . . . . . . . . . . . . . . . . Removing an NVMEM battery from an N6200 series system . . . . . . . Removing the NVMEM DIMM . . . . . . . . . . . . . . . . . Installing the system DIMMs . . . . . . . . . . . . . . . . . Installing an NVMEM battery . . . . . . . . . . . . . . . . . Reinstalling the controller module and booting the system. . . . . . . . Checking the status of the NVMEM battery and running diagnostics . . . . Completing the replacement process . . . . . . . . . . . . . . . Disposing of batteries . . . . . . . . . . . . . . . . . . . Replacing a system DIMM in an N6200 series system . . . . . . . . . . Shutting down the node . . . . . . . . . . . . . . . . . . . Shutting down a node in an HA pair . . . . . . . . . . . . . . Shutting down the node in a stand-alone system . . . . . . . . . . Opening the system . . . . . . . . . . . . . . . . . . . . Removing the system DIMMs . . . . . . . . . . . . . . . . . Installing the system DIMMs . . . . . . . . . . . . . . . . . Reinstalling the controller module and booting the system. . . . . . . . Running diagnostics on the system DIMM . . . . . . . . . . . . . Completing the replacement process . . . . . . . . . . . . . . . Replacing PCIe cards in an N6200 series system . . . . . . . . . . . . Shutting down the node . . . . . . . . . . . . . . . . . . . Shutting down a node in an HA pair . . . . . . . . . . . . . . Shutting down the node in a stand-alone system . . . . . . . . . . Opening the system . . . . . . . . . . . . . . . . . . . . Removing a PCIe card . . . . . . . . . . . . . . . . . . . . Installing a PCIe card . . . . . . . . . . . . . . . . . . . . Reinstalling the controller module and booting the system. . . . . . . . Running diagnostics on a PCIe card . . . . . . . . . . . . . . . Completing the replacement process . . . . . . . . . . . . . . . Replacing a boot device in an N6200 series system running Data ONTAP 7.3.5 and ONTAP 7.3 release family . . . . . . . . . . . . . . . . . . . Shutting down a node . . . . . . . . . . . . . . . . . . . . Opening the system . . . . . . . . . . . . . . . . . . . . Removing the boot device from the controller . . . . . . . . . . . . Installing the boot device and transferring system files to the boot device . .
xii
Completing the replacement process . . . . . . . . . . . . . . . . . . . . . . . . . Replacing a boot device in an N6200 series system running Data ONTAP 7-Mode . . . . . . . . . . . Replacing a boot device in a system running Data ONTAP 7-Mode. . . . . . . . . . . . . . . Shutting down a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the boot device from the controller . . . . . . . . . . . . . . . . . . . . . Installing the boot device and transferring system files disruptively using netboot in a 7-Mode system . . Installing the boot device and transferring system files nondisruptively using netboot in a 7-Mode system Completing the replacement process . . . . . . . . . . . . . . . . . . . . . . . . . Replacing the I/O expansion module in an N6200 series system. . . . . . . . . . . . . . . . . Shutting down the node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shutting down a node in an HA configuration . . . . . . . . . . . . . . . . . . . . Shutting down the node in a stand-alone system . . . . . . . . . . . . . . . . . . . . Removing the I/O expansion module . . . . . . . . . . . . . . . . . . . . . . . . Installing the I/O expansion module . . . . . . . . . . . . . . . . . . . . . . . . . Running diagnostics on the I/O expansion module . . . . . . . . . . . . . . . . . . . . Completing the replacement process . . . . . . . . . . . . . . . . . . . . . . . . . Disposing of batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing the Real-Time Clock (RTC) battery in an N6200 series system . . . . . . . . . . . . . . Shutting down the node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shutting down a node in an HA pair . . . . . . . . . . . . . . . . . . . . . . . . Shutting down the node in a stand-alone system . . . . . . . . . . . . . . . . . . . . Opening the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing an RTC battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing an RTC battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reinstalling the controller module and booting the system. . . . . . . . . . . . . . . . . . Running diagnostics on the RTC battery . . . . . . . . . . . . . . . . . . . . . . . . Resetting the date and time on the system . . . . . . . . . . . . . . . . . . . . . . . Completing the replacement process . . . . . . . . . . . . . . . . . . . . . . . . . Disposing of batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59 59 60 60 60 61 62 65 68 68 68 68 69 69 70 71 73 73 74 74 74 75 75 76 76 77 77 79 80 80
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Trademarks . . . . . . . . . . . . . . . . . . . . . . . Important notes . . . . . . . . . . . . . . . . . . . . . . Electronic emission notices . . . . . . . . . . . . . . . . . . Federal Communications Commission (FCC) Class A Statement . . . . . Industry Canada Class A Emission Compliance Statement . . . . . . . Avis de conformit la rglementation d'Industrie Canada . . . . . . European Union EMC Directive Conformance Statement . . . . . . . Germany Electromagnetic Compatibility Directive . . . . . . . . . People's Republic of China Class A Electronic Emission Statement . . . . Japan Voluntary Control Council for Interference (VCCI) Class A Statement . Japan Electronics and Information Technology Industries Association (JEITA) Korea Communications Commission (KCC) Class A Statement . . . . . Russia Electromagnetic Interference (EMI) Class A Statement . . . . . . Taiwan Class A Electronic Emission Statement . . . . . . . . . . . Taiwan Contact Information . . . . . . . . . . . . . . . . Australia and New Zealand Class A Statement . . . . . . . . . . Power cords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 89 89 89 90 90 90 90 91 92 92 92 92 93 93 93 93
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Contents
xiii
xiv
Figures
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. N6200 series system - Front view. . . . . . . . . . . . . . N6210 2858-C10 . . . . . . . . . . . . . . . . . . . N6240 2858-E11 and N6270 2858-E12 . . . . . . . . . . . . N6210 2858-C20, N6240 2858-C21 and N6270 2858-C22 . . . . . . N6240 2858-E21 and N6270 2858-E22 . . . . . . . . . . . . Rear view . . . . . . . . . . . . . . . . . . . . . Appliance ports and LEDs . . . . . . . . . . . . . . . Cabling the N6200 series system to Fibre Channel switches . . . . Cabling the N6200 series system expansion adapter to storage expansion Cabling the N6200 series system expansion adapter to storage expansion N6200 series system components - Front . . . . . . . . . . . N6200 series system components - Rear . . . . . . . . . . . N6200 series ports and LEDs. . . . . . . . . . . . . . . N6200 series system components - Exploded view . . . . . . . N6200 series system fans . . . . . . . . . . . . . . . . Removing the power supply . . . . . . . . . . . . . . . NVMEM LED. . . . . . . . . . . . . . . . . . . . NVMEM battery location . . . . . . . . . . . . . . . . Removing the NVMEM battery . . . . . . . . . . . . . . DIMM locations . . . . . . . . . . . . . . . . . . . Removing DIMMs . . . . . . . . . . . . . . . . . . Installing the NVMEM battery . . . . . . . . . . . . . . NVMEM LED. . . . . . . . . . . . . . . . . . . . DIMM locations . . . . . . . . . . . . . . . . . . . Removing DIMMs . . . . . . . . . . . . . . . . . . NVMEM LED. . . . . . . . . . . . . . . . . . . . Removing the PCI card . . . . . . . . . . . . . . . . Removing the boot device. . . . . . . . . . . . . . . . Removing the boot device. . . . . . . . . . . . . . . . NVMEM LED. . . . . . . . . . . . . . . . . . . . Remving the IOX module . . . . . . . . . . . . . . . . NVMEM LED. . . . . . . . . . . . . . . . . . . . Removing the RTC battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 . 2 . 2 . 2 . 3 . 14 . 15 . 17 . 18 . 19 . 23 . 24 . 24 . 25 . 27 . 29 . 31 . 33 . 34 . 35 . 36 . 37 . 41 . 43 . 44 . 49 . 50 . 56 . 61 . 69 . 70 . 75 . 76
. . . . . . units units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xv
xvi
Tables
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. N6200 series physical characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . 5 N6200 series clearance dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . 5 N6200 series environmental requirements . . . . . . . . . . . . . . . . . . . . . . . . 6 N6200 series systems maximum electrical power . . . . . . . . . . . . . . . . . . . . . 6 N6210 electrical requirementsone controller node, with one 256-Gb Flash Cache module . . . . . . . . 6 N6210 electrical requirementstwo controller nodes, with one 256-Gb Flash Cache module per node . . . . 7 N6240 electrical requirementstwo controller nodes, with one 256-Gb and one 512-Gb Flash Cache module per controller node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 N6240 electrical requirementsone controller node, with one 256-Gb and one 512-Gb Flash Cache module, and one I/O expansion module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 N6270 electrical requirementstwo controller nodes, with one 256-Gb and one 512-Gb Flash Cache module per controller node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 N6270 electrical requirementsone controller node, with one 256-Gb and one 512-Gb Flash Cache module, and one I/O expansion module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Filer installation process procedures . . . . . . . . . . . . . . . . . . . . . . . . . 11 Service Processor manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 110V, single phase recommended conductor sizes . . . . . . . . . . . . . . . . . . . . . 81 220V, single phase recommended conductor sizes . . . . . . . . . . . . . . . . . . . . . 81 American Wire Gage to Harmonized Cordage equivalents . . . . . . . . . . . . . . . . . . 81
xvii
xviii
Related documents
The following documents, as well as documentation for Data ONTAP and other software, are available on the IBM N series support website, which is accessed and navigated as described in Websites on page xx. For information about installation and setup for your N6200 series system, see the N6200 series Installation and Setup Instructions that came with your system. For information about error messages, troubleshooting, and monitoring the LEDs for your N6200 series system and optional adapter cards, see the IBM System Storage N series Platform Monitoring Guide. For diagnostic information about your N6200 series system, see the IBM System Storage N series System-Level Diagnostics Guide. For a list of N series hardware and hardware-related documents, as well as lists of Data ONTAP documentation by release family, refer to the "Bibliography" appendix in the IBM System Storage N series Introduction and Planning Guide.
xix
For a list of optional adapter cards supported by your N6200 series system, refer to the appropriate "Optional adapter cards" appendix in the IBM System Storage N series Introduction and Planning Guide. If you are replacing or installing a Performance Acceleration Module (PAM) or Flash Cache module, refer to the "Installing or replacing a Flash Cache module or PAM" appendix in the IBM System Storage N series Introduction and Planning Guide.
Supported features
IBM System Storage N series storage systems are driven by NetApp Data ONTAP software. Some features described in the product software documentation are neither offered nor supported by IBM. Please contact your local IBM representative or reseller for further details. Information about supported features can also be found on the N series support website, which is accessed and navigated as described in Websites.
Websites
IBM maintains pages on the World Wide Web where you can get the latest technical information and download device drivers and updates. The following web pages provide N series information: v A listing of currently available N series products and features can be found at the following web page: www.ibm.com/storage/nas/ v The IBM System Storage N series support website requires users to register in order to obtain access to N series support content on the web. To understand how the N series support web content is organized and navigated, and to access the N series support website, refer to the following publicly accessible web page: www.ibm.com/storage/support/nseries/ This web page also provides links to AutoSupport information as well as other important N series product resources. v IBM System Storage N series products attach to a variety of servers and operating systems. To determine the latest supported attachments, go to the IBM N series interoperability matrix at the following web page: www.ibm.com/systems/storage/network/interophome.html v For the latest N series hardware product documentation, including planning, installation and setup, and hardware monitoring, service and diagnostics, see the IBM N series Information Center at the following web page: http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp
xx
IBM Taiwan Product Service Contact Info: IBM Taiwan Corporation 3F, No 7, Song Ren Rd., Taipei Taiwan Tel: 0800-016-888
Firmware updates
IBM N series product firmware is embedded in Data ONTAP. As with all devices, it is recommended that you run the latest level of firmware. Any firmware updates are posted to the IBM N series support website, which is accessed and navigated as described in Websites on page xx. Note: If you do not see new firmware updates on the IBM N series support website, you are running the latest level of firmware.
xxi
Verify that the latest level of firmware is installed on your machine before contacting IBM for technical support.
Storage terms
ACP Alternate Control Path is a protocol that enables Data ONTAP to manage and control the storage expansion unit storage subsystem using a separate network from the data path, so management communication is not dependent on the data path being intact and available. The controller module of the EXN1000 serial advanced technology attachment (SATA) storage expansion unit.
AT-FCX
xxii
Disk
Disk shelf or shelf Any storage expansion unit containing hard disk drives. ESH IOM The controller module of Fibre Channel disk storage expansion units. The Input/Output module of SAS disk storage expansion units.
Loop or Fibre-Channel Arbitrated Loop One or more daisy-chained Fibre Channel storage expansion units connected to an N series storage system. Node The system controller module that executes the software on an N series system. There is one node in single-controller models; there are two nodes in active/active or high availability models.
Stack or SAS stack A stack of one or more SAS storage expansion units using IOM modules connected to the storage system. The maximum number of storage expansion units in a stack of storage expansion units and the number of storage expansion unit stacks in a configuration are dependent on the type of storage system.
Command conventions
You can enter commands on the system console or from any client that can obtain access to the storage system using a Telnet session. In examples that illustrate commands executed on a UNIX workstation, the command syntax and output might differ, depending on your version of UNIX.
Formatting conventions
The following table lists different character formats used in this guide to set off special information.
Formatting convention Italic type Type of information v Words or characters that require special attention. v Placeholders for information you must supply. For example, if the guide requires you to enter the fctest adaptername command, you enter the characters fctest followed by the actual name of the adapter. v Book titles in cross-references. Monospaced font v Command and daemon names. v Information displayed on the system console or other computer monitors. v The contents of files. Bold monospaced font Words or characters you type. What you type is always shown in lowercase letters, unless your program is case-sensitive and uppercase letters are necessary for it to work properly.
xxiii
Keyboard conventions
This guide uses capitalization and some abbreviations to refer to the keys on the keyboard. The keys on your keyboard might not be labeled exactly as they are in this guide.
What is in this guide... hyphen (-) What it means... Used to separate individual keys. For example, Ctrl-D means holding down the Ctrl key while pressing the D key. Used to refer to the key that generates a carriage return, although the key is named Return on some keyboards. Used to mean pressing one or more keys on the keyboard. Used to mean pressing one or more keys and then pressing the Enter key.
Enter
type enter
xxiv
xxv
xxvi
Figure 1. N6200 series system - Front view 1 2 3 4 Fan module System LEDs - power fault, controller A activity, controller B activity Fan CAM handle Fan LED
n62hw02
The following images show the available models of the N6200 series systems. The N6210 2858-C10 is single-enclosure, non-HA system with a single controller. It does not contain an Input/Output expansion module.
c0a
0a 0b
0c 0d
e0a e0b
PSU
c0b
IOIOI
PSU
n62hw08
The N6240 2858-E11 and N6270 2858-E12 are single-enclosure, non-HA systems with a single controller and one Input/Output expansion module (IOXM).
c0a
0a 0b
0c 0d
e0a e0b
PSU
c0b
IOIOI
IOXM
1 2 3 4
PSU
n62hw05
IOIOI
The N6210 2858-C20, N6240 2858-C21 and N6270 2858-C22 are single-enclosure HA systems with two controllers. They do not contain an Input/Output expansion module.
c0a
0a 0b
0c 0d FC
PSU
0a 0b
c0b
PSU
c0a c0b
0c 0d
e0a
e0b
IOIOI
The N6240 2858-E21 and N6270 2858-E22 are dual-enclosure HA systems. Each enclosure contains one controller and one Input/Output expansion module.
c0a
0c 0d
e0a e0b
0a
0b
c0b
IOIOI
PSU
IOXM
1 2 3 4
PSU
c0a
0c 0d
e0a e0b
0a
0b
c0b
IOIOI
PSU
IOXM
1 2 3 4
PSU
n62hw07
Attention: Static electricity can damage electronic devices and your system. To avoid damage, keep static-sensitive devices in their static-protective packages until you are ready to install them. To reduce the possibility of electrostatic discharge (ESD), observe the following 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. This drains static electricity from the package and from your body. v Remove the device from its package and install it directly into your system unit without setting it down. If it is necessary to set the device down, place it in its static-protective package. Do not place the device on your system unit cover or on a metal table. Take additional care when handling devices during cold weather because heating reduces indoor humidity and increases static electricity.
This product is not intended to be connected directly or indirectly by any means whatsoever to interfaces of public telecommunications networks.
Hardware specifications
The following tables list the characteristics and requirements for your hardware.
DANGER The weight of this part or unit is between 32 and 55 kg (70.5 and 121.2 lb). It takes three persons to safely lift this part or unit. (C010)
Note: Operating at the extremes of the environmental requirements might increase the risk of device failure.
Table 1. N6200 series physical characteristics Weight v 2858-C10 (single enclosure with one controller): 29.67.kg (65.41 lb) v 2858-C20 (single enclosure with two controllers): 34.52 kg (76.1 lb) v 2858-C21 (single enclosure with two controllers): 34.56 kg (76.19 lb) v 2858-C22 (single enclosure with two controllers): 36.06 kg (79.5 lb) v 2858-E11 (single enclosure with one controller and one IOXM): 32.94 kg (72.62 lb) v 2858-E12 (single enclosure with one controller and one IOXM): 33.69 kg (74.27 lb) v 2858-E21 (two enclosures, each with one controller and one IOXM): 65.88 kg (145.24 lb) v 2858-E22 (two enclosures, each with one controller and one IOXM): 67.38 kg (148.55 lb) Rack units v 3U for single enclosure models v 6U for dual enclosure models Height v 13 cm (5.12 in.) for single enclosure models v 26 cm (10.24 in.) for dual enclosure models Width Depth 44.7 cm (17.6 in.) 61 cm (24 in.) without bezel 64.5 cm (25.4 in.) with beze1
Table 2. N6200 series clearance dimensions Airflow Front Rear Service Front Rear 25.4 cm (10 in.) 30.5 cm (12 in.) 76.2 cm (30.5 in.) 76.2 cm (30.5 in.)
svc00168
Table 3. N6200 series environmental requirements Operating temperature maximum range Operating temperature recommended range Nonoperating temperature range Operating relative humidity Nonoperating relative humidity 50 F to 104 F (10 C to 40 C) 68 F to 77 F (20 C to 25 C) -40 F to 158 F (-40 C to 70 C) 20 to 80% noncondensing 10 to 95% noncondensing (in original container)
Recommended operating temperature relative humidity 40 to 55% range Maximum wet bulb temperature Maximum altitude Acoustic level 28 C (82 F) 3050 m (10,000 ft.) 55.5 dBA, 7.5 bels at 23 C
The following tables list the maximum electrical power for the N6200 series systems and the electrical requirements for different configurations of the N6200 series systems.
Table 4. N6200 series systems maximum electrical power System N6200 series systems Maximum electrical power 100-240 V ac, 12-8 A, 50-60 Hz.
In the following tables, Worst-case indicates a system running with one PSU and high fan speed. Typical Per PSU/System, two PSUs indicates a system running one PSU on one circuit and a system running two PSUs on two circuits.
Table 5. N6210 electrical requirementsone controller node, with one 256-Gb Flash Cache module 100 to 120V Worstcase, single PSU 4.22 421 1437 Typical Per PSU 1.52 150 511 System, two PSUs 3.03 299 1021 200 to 240V Worstcase, single PSU 2.11 411 1403 Typical Per PSU 0.83 147 500 System, two PSUs 1.66 293 1000
Input voltage Input current measured, A Input power measured, W Thermal dissipation, BTU/hr Input power frequency, Hz
50 to 60
Table 6. N6210 electrical requirementstwo controller nodes, with one 256-Gb Flash Cache module per node 100 to 120V Worstcase, single PSU 6.27 626 2137 Typical Per PSU 2.32 231 789 System, two PSUs 4.64 462 1577 200 to 240V Worstcase, single PSU 3.11 610 2082 Typical Per PSU 1.13 225 768 System, two PSUs 2.38 450 1536
Input voltage Input current measured, A Input power measured, W Thermal dissipation, BTU/hr Input power frequency, Hz
50 to 60
Table 7. N6240 electrical requirementstwo controller nodes, with one 256-Gb and one 512-Gb Flash Cache module per controller node 100 to 120V Worstcase, single PSU 6.37 635 2168 Typical Per PSU 2.35 233 796 System, two PSUs 4.70 466 1591 200 to 240V Worstcase, single PSU 3.15 620 2116 Typical Per PSU 1.21 228 779 System, two PSUs 2.41 456 1557
Input voltage Input current measured, A Input power measured, W Thermal dissipation, BTU/hr Input power frequency, Hz
50 to 60
Table 8. N6240 electrical requirementsone controller node, with one 256-Gb and one 512-Gb Flash Cache module, and one I/O expansion module 100 to 120V Worstcase, single PSU 5.01 500 1707 Typical Per PSU 1.86 184 628 System, two PSUs 3.71 368 1256 200 to 240V Worstcase, single PSU 2.50 478 1632 Typical Per PSU 0.98 180 615 System, two PSUs 1.96 360 1229
Input voltage Input current measured, A Input power measured, W Thermal dissipation, BTU/hr Input power frequency, Hz
50 to 60
Table 9. N6270 electrical requirementstwo controller nodes, with one 256-Gb and one 512-Gb Flash Cache module per controller node 100 to 120V Worstcase, single PSU 7.28 728 2485 Typical Per PSU 2.78 278 942 System, two PSUs 5.56 552 1884 200 to 240V Worstcase, single PSU 3.58 707 2413 Typical Per PSU 1.42 271 924 System, two PSUs 2.83 541 1847
Input voltage Input current measured, A Input power measured, W Thermal dissipation, BTU/hr Input power frequency, Hz
50 to 60
Table 10. N6270 electrical requirementsone controller node, with one 256-Gb and one 512-Gb Flash Cache module, and one I/O expansion module 100 to 120V Worstcase, single PSU 5.47 547 1867 Typical Per PSU 2.07 204 697 System, two PSUs 4.14 408 1393 200 to 240V Worstcase, single PSU 2.73 533 1820 Typical Per PSU 1.07 199 680 System, two PSUs 2.13 398 1359
Input voltage Input current measured, A Input power measured, W Thermal dissipation, BTU/hr Input power frequency, Hz
50 to 60
1 set of IBM publications v N6240 2858-E11 and N6270 2858-E12 1 single-enclosure, non-HA system with a single controller and one Input/Output expansion module (IOXM), containing any options you ordered 1 console adapter cable, RJ-45 to DB-9 4 cable management arms (two per controller node, and two per IOXM) 1 ESD wrist strap 2 power cords 1 serial null modem cable 1 IBM rail kit 1 set of IBM publications v N6210 2858-C20, N6240 2858-C21 and N6270 2858-C22 1 single-enclosure HA system with two controllers, containing any options you ordered 2 console adapter cables, RJ-45 to DB-9 4 cable management arms (two per controller node) 1 ESD wrist strap 2 power cords 2 serial null modem cables 1 IBM rail kit 1 set of IBM publications v N6240 2858-E21 and N6270 2858-E22: 1 dual-enclosure HA system, containing any options you ordered. Each enclosure ships in a separate container, and each enclosure contains one controller and one Input/Output expansion module. 2 console adapter cables, RJ-45 to DB-9 (1 per enclosure) 8 cable management arms (two per controller node, and two per IOXM, for a total of 4 per enclosure) 2 ESD wrist straps (1 per enclosure) 4 power cords (2 per enclosure) 2 serial null modem cables (1 per enclosure) 2 cluster connection cables (either SFP+ integrated copper cables or 10GbE SFP+ transceivers with fiber cables, depending on your order) 2 IBM rail kits (1 per enclosure) 1 set of IBM publications
You need to observe the following rules and restrictions when installing an N6200 series system in a standard IBM 19-inch (48.26 cm) equipment rack with mounting rails:
DANGER The weight of this part or unit is between 32 and 55 kg (70.5 and 121.2 lb). It takes three persons to safely lift this part or unit. (C010) v Install the system at the bottom of your configuration, so that stacks or loops extend above 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 of the rack cabinet. (R001 part 1 of 2) v When installing storage expansion units in a rack, do not exceed the maximum storage limit for your system. v Make sure that the ID on the back panel of each storage expansion unit matches the ID specified on its label. v Always install the storage expansion units fully loaded. Do not remove disk drives to reduce the weight.
10
svc00168
Table 11. Filer installation process procedures Procedure is performed by... Is the procedure required? Filer Gateway Yes Customer Customer
Stage 1
Procedure Print and complete a configuration worksheet for each system node of your storage system to gather the information that the software setup process requires. Install the system in a standard IBM 19-inch rack.
For instructions, see... The configuration worksheet is provided in the Data ONTAP Software Setup Guide for your version of Data ONTAP.
Yes
Customer
IBM
The Installation and Setup Instructions for your system Connecting your system to an IP network on page 14, or the Installation and Setup Instructions that came with your system Connecting a filer to storage expansion units on page 16, or the Installation and Setup Instructions that came with your system Refer to the documentation for your external storage for additional information. Connecting your system to a power source on page 13, or the Installation and Setup Instructions that came with your system The Data ONTAP Software Setup Guide for your version of Data ONTAP, or the Installation and Setup Instructions that came with your system Connecting your system to storage on page 15
Customer
Customer
Filer: Connect the storage system to storage expansion units. 4 Gateway: Connect the system to the back-end storage.
Yes
Customer
n/a
Yes
n/a
Customer
Customer
Customer
Yes
Customer
Customer
Customer
Customer
11
12
13
14
n62hw01
13
11
c0a
0c
e0a
LNK
LNK
!
c0b 0d e0b
12
10
Figure 7. Appliance ports and LEDs 1 2 3 4 5 6 7 8 9 10 11 12 13 NVMEM LED Controller fault LED USB (top) and serial console (bottom) ports Private management 10/100 Mb Ethernet port Management Ethernet 10/100 Mb port and LEDs 1-GbE ports (e0a and e0b) 1-GbE port LEDs Fibre Channel ports (0c and 0d) Fibre Channel port LEDs HA ports (c0a and c0b) HA port LEDs SAS ports SAS port LEDs
15
n62hw03
0a
0b
16
Cabling an N6200 series system to Fibre Channel switches using a Fibre Channel expansion adapter
This section describes how to cable an N6200 series system to Fibre Channel switches using a dual-port optical Fibre Channel expansion adapter for expansion unit storage. The example shown in this section illustrates the connections for a single-enclosure HA pair, such as the N6210 2858-C20, N6240 2858-C21, or N6270 2858-C22. For a list of optional adapter cards supported by your N6200 series system, refer to the appropriate "Optional adapter cards" appendix in the IBM System Storage N series Introduction and Planning Guide. This guide, as well as other N series and Data ONTAP documentation, is available on the IBM N series support website, which is accessed and navigated as described in Websites on page xx. Important: If you are not using the onboard Fibre Channel ports for storage, then you must set your onboard Fibre Channel ports to Target mode, as described in the IBM System Storage N series Data ONTAP Block Access Management Guide for your version of Data ONTAP. Note: The illustrations in the following sections show connections to EXN4000 storage expansion units. In EXN1000 storage expansion units, the positions of the In and Out ports are reversed from those of the EXN4000. 1. As shown in Figure 8, cable onboard ports 0c of both the top and bottom controller modules (CM-A and CM-B) to two ports on one Fibre Channel switch. 2. As shown in Figure 8, cable onboard ports 0d of both the top and bottom controller modules (CM-A and CM-B) to two ports on a second Fibre Channel switch.
OUT
IN
PSU
IN OUT
PSU
EXN
OUT
IN
PSU
IN OUT
PSU
EXN
CM-A
0a 0b
1b c0a 0c e0a
1a
PSU
c0b
0d
e0b 1b 1a
CM-B
0a 0b
PSU
N6200
n62hw023
c0a
0c
e0a
c0b
0d
e0b
FC Switch 1
FC Switch 2
3. As shown in Figure 9 on page 18, cable the dual-port expansion adapter Port 1a on the top controller module (CM-A) to the first storage expansion unit Channel A ESH4 or AT-FCX IN port.
17
4. As shown in Figure 9, cable the dual-port expansion adapter Port 1a on the bottom controller module (CM-B) to the first storage expansion unit Channel B ESH4 or AT-FCX IN port. 5. As shown in Figure 9, cable the first storage expansion unit Channel A ESH4 or AT-FCX OUT port to the next storage expansion unit Channel A ESH4 or AT-FCX IN port. Label this cable with a solid-colored label. 6. As shown in Figure 9, cable the first storage expansion unit Channel B ESH4 or AT-FCX OUT port to the storage expansion unit Channel B ESH4 or AT-FCX IN port. Label this cable with a solid-colored label. 7. Repeat Steps 5 and 6, connecting OUT port to IN port, for the remaining storage expansion units in the loop. Do not plug any cables in the ESH4 or AT-FCX OUT port of the last unit. The storage expansion units are self-terminating. Note: The ESH4 is self-terminating and does not have a terminate switch. The AT-FCX is self-terminating.
OUT
IN
PSU
IN OUT
PSU
EXN
OUT
IN
PSU
IN OUT
PSU
EXN
CM-A
0a 0b
1b c0a 0c e0a
1a
PSU
c0b
0d
e0b 1b 1a
CM-B
0a 0b
PSU
N6200
n62hw024
c0a
0c
e0a
c0b
0d
e0b
FC Switch 1
FC Switch 2
Figure 9. Cabling the N6200 series system expansion adapter to storage expansion units
8. As shown in Figure 10 on page 19, cable the dual-port expansion adapter Port 1b on the top controller module (CM-A) to the last storage expansion unit Channel B ESH4 or AT-FCX OUT port. 9. As shown in Figure 10 on page 19, cable the dual-port expansion adapter Port 1b on the bottom controller module (CM-B) to the last storage expansion unit Channel A ESH4 or AT-FCX OUT port.
18
OUT
IN
PSU
IN OUT
PSU
EXN
OUT
IN
PSU
IN OUT
PSU
EXN
CM-A
0a 0b
1b c0a 0c e0a
1a
PSU
c0b
0d
e0b 1b 1a
CM-B
0a 0b
PSU
N6200
n62hw025
c0a
0c
e0a
c0b
0d
e0b
FC Switch 1
FC Switch 2
Figure 10. Cabling the N6200 series system expansion adapter to storage expansion units
19
v An unsupported tape backup device might cause the system to halt. To verify support for your third-party device, check the Interoperability Matrix on the IBM N series support website, which is accessed and navigated as described in Websites on page xx. v For additional information about Fibre Channel cables, see the IBM N series support website.
20
where adapter is the port number. You can specify more than one port.
Copyright IBM Corp. 2011
21
Example: The following example sets onboard ports 0c and 0d to initiator mode.
fcadmin config -t initiator 0c 0d
3. Verify that the Fibre Channel ports are online and configured in the correct state for your configuration by entering the following command:
fcadmin config
Example: The following output example shows two ports configured as Fibre Channel targets and two ports configured as initiators.
n6000a> fcadmin config Local Adapter Type State Status --------------------------------------------------0a target CONFIGURED online 0b target CONFIGURED online 0c initiator CONFIGURED online 0d initiator CONFIGURED online
For information on converting the onboard ports to target mode and configuring your SAN, see the IBM System Storage N series Data ONTAP Block Access Management Guide for your version of Data ONTAP. This guide, as well as other Data ONTAP publications, is available on the IBM N series support website, which is accessed and navigated as described in Websites on page xx.
22
1 2 3 4
Fan module System LEDs - power fault, controller A activity, controller B activity Fan CAM handle Fan LED
23
n62hw02
Figure 12 shows the locations of components at the rear of your N6200 series system.
1 2 3
Figure 13 shows a view of the ports and LEDs of your N6200 series system.
13 11 9 7 5
c0a
0c
e0a
LNK
LNK
!
c0b 0d e0b
12
10
1 2 3 4 5 6
NVMEM LED Controller fault LED USB (top) and serial console (bottom) ports Private management 10/100 Mb Ethernet port Management Ethernet 10/100 Mb port and LEDs 1-GbE ports (e0a and e0b)
24
n62hw03
0a
0b
n62hw01
6 5 7
1-GbE port LEDs Fibre Channel ports (0c and 0d) Fibre Channel port LEDs HA ports (c0a and c0b) HA port LEDs SAS ports SAS port LEDs
56 8
86 5 9 86 5 10 86 5 11 86 5 12 86 5 13
Figure 14 shows an exploded view of the components of your N6200 series system.
1 2 3 4 1 2
10
8
n62hw04
5 4
1 2 3
NVMEM (1, 2) and system DIMMs (1, 2, 3, 4) DIMM and NVMEM DIMM slots CPU air ducts
25
4 5 6
6 5 7
PCIe card(s) PCIe side panel Boot device Boot device enclosure RTC battery holder and battery NVMEM battery NVMEM battery cable
56 8
86 5 9 86 5 10
Procedure
1. If you are not already grounded, properly ground yourself. 2. Remove the bezel (if necessary) with two hands, by grasping the openings on each side of the bezel, and then pulling it toward you until the bezel releases from the four ball studs on the chassis frame. 3. Identify the fan module that you must replace by checking the console error messages and looking at the Status LED on each fan module cam handle. A failed fan module LED is solid amber, indicating that the fan module failed. No LEDs are lit if the fan module is not receiving power.
26
4. Press down the release latch on the fan module cam handle and pull the cam handle downward. The fan module moves a little bit away from the chassis.
2 3 1 4
1 2 3 4
Cam handle Fan module Cam handle release latch Fan module status LED
5. Pull the fan module straight out from the chassis, making sure that you support it with your free hand, so that it does not swing out of the chassis. Attention: The fan modules are short. Always support the bottom of the module with your free hand so that it does not suddenly drop free from the chassis and injure you. 6. Set the fan module aside.
Procedure
1. If you are not already grounded, properly ground yourself. 2. Remove the bezel, if necessary. 3. Insert the replacement fan module into the chassis by aligning it with the opening and sliding it into the chassis. 4. Push firmly on the fan module cam handle to ensure that it is seated all the way into the chassis. The cam handle raises slightly when the fan module is completely seated. 5. Swing the cam handle up to its closed position, making sure that the cam handle release latch clicks into the locked position. 6. Reinstall the bezel.
Chapter 4. Replacing N6200 series system devices
27
7. Run diagnostics on the replacement fan module during the next scheduled system downtime. See the IBM System Storage N series System-Level Diagnostics Guide for more information.
Procedure
1. Identify the power supply you want to replace, based on console error messages or through the LEDs on the power supplies. See the IBM System Storage N series Platform Monitoring Guide for a description of LED behaviors. 2. If you are not already grounded, properly ground yourself. 3. Turn off the target power supply and remove the power cord by completing the following substeps, using the illustration for reference:
28
3 4
1 2 3 4 5
Power supply Cam handle release latch Power and Fault LEDs Cam handle Power cord locking mechanism
Note: If you are having difficulty unplugging the power supply, remove the cable management arm from the controller module. a. Pinch the tab on the locking mechanism of the cable retainer clip, and then open the retainer clip. b. Slide the retainer clip off the cord. c. Unplug the power cord from the power source, and then remove the power cord from the power supply. 4. 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 supply out of the chassis. Make sure that you support the power supply with your free hand.
Procedure
1. Make sure that the on/off switch of the new power supply is in the Off position. 2. If you are not already grounded, properly ground yourself.
Chapter 4. Replacing N6200 series system devices
29
3. Align the edges of the power supply with the opening in the system chassis and gently push the power supply into the chassis. 4. Push on the power supply cam handle to seat it all the way into the chassis, and then push the cam handle to the closed position, making sure that the cam handle release latch clicks into its locked position. 5. Reconnect the power cord and secure it to the power supply using the cable retaining clip. 6. Reconnect the power supply to the power source, and then turn it on. The power supply should run with no fault LEDs lit. Note: Reinstall the cable management arm, if you removed it when unplugging the power supply. 7. Run diagnostics on the power supply at the next reboot. See the IBM System Storage System-Level Diagnostics Guide for more information.
Procedure
1. Check the status of the target node (the node you want to perform maintenance on) by entering the cf status command at the system console of either node. 2. Take one of the following actions, depending on the result of the cf status command:
30
If... Neither node is in takeover mode The partner node took over the target node
Then... Go to the next step in this procedure. The target node is in a state where you can begin removing it from the system chassis. Continue with "Opening the System."
1. Correct the problem that caused the takeover. 2. Run the cf giveback command from the target node console. 3. Go back to the beginning of this procedure.
3. Take over the target node by entering the cf takeover command from the partner node's console. 4. Continue with "Opening the System."
Procedure
1. Enter the halt command from the system console. Attention: You must perform a clean system shutdown before replacing system components to avoid losing unwritten data in the nonvolatile memory (NVMEM). The NVMEM LED is located on the controller module to the right of the network ports, marked with a battery symbol. If the NVMEM LED is flashing, there is content in the NVMEM that has not been saved to disk. You need to reboot the controller module and proceed from the beginning of this procedure. 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.
c0a
0c
e0a
0a LNK
0b LNK
!
c0b 0d e0b
1
Figure 17. NVMEM LED
NVMEM LED
2. If you are not already grounded, properly ground yourself. 3. Turn off the power supplies, unplug the power cords from the power source, and remove the power cords.
Chapter 4. Replacing N6200 series system devices
31
Procedure
1. If you are not already grounded, properly ground yourself. 2. Unplug the system cables from the controller module, as needed, and keep track of where the cables were connected. Leave the cables in the cable management arm so that when you reinstall the cable management arm in the controller module, the cables will be organized. 3. Disconnect the right and left cable management arms from the controller module. To release the arms, press the silver button on the power supply side of each arm, and then remove the arm from the controller module. 4. Loosen the thumbscrew on the cam handle. 5. Pull the cam handle downward and slide the controller module out of the system.
Procedure
1. Open the CPU air duct. 2. Locate the battery, squeeze the clip on the face of the battery plug to release the plug from the socket, and then lift the battery cable from the socket. v If you are only replacing NVMEM DIMMs, and you are not replacing the NVMEM battery, go to Removing the NVMEM DIMM on page 34. v If you are replacing the NVMEM battery, continue with the next step in this procedure.
32
3 4
1 2 3 4
CPU air duct NVMEM battery NVMEM battery plug NVMEM battery locking tab
3. Gently pull the locking tab on the battery housing, near the plug, away from the controller module side. 4. Place your forefinger at the far end of the battery housing and gently push it toward the CPU air duct. You should see the tabs on the battery housing aligning with the notches in the controller module sheet metal.
33
1 2 3
5. Gently pull the battery housing toward the center of the controller module and then lift the battery out of the controller module. 6. Continue with one of the following tasks:
Option If you are also replacing the NVMEM DIMMS If you are replacing only the NVMEM battery, and not replacing the NVMEM DIMMS Description Continue with Removing the NVMEM DIMM Continue with Installing an NVMEM battery on page 37
34
Procedure
1. If you are not already grounded, properly ground yourself. 2. Open the CPU air duct, if necessary, and locate the DIMMs on the controller module. The NVMEM DIMMs are located in DIMM slots 1 and 2, and have white DIMM locking tabs. There is also a fault LED for these DIMMs. This illustration shows a system fully populated with DIMMs:
1
1 2 3 4 1 2
1 2
NVMEM DIMMs 1 and 2. System DIMMs 1 through 4. The number of DIMMs in your system will vary. DIMM sockets 1 and 2 are always populated in all N6200 series models, while DIMM sockets 3 and 4 are only populated in the N6270.
DIMM sockets. The NVMEM DIMM sockets have white DIMM locking tabs, while the system DIMM sockets have black locking tabs.
3. Note the orientation of the DIMM in the socket so that you can insert the replacement DIMM in the proper orientation.
35
4. 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.
CAUTION: The DIMMs are located very close to the CPU heat sync, which might still be hot. Avoid touching the CPU heat sync when removing the DIMM. Attention: Carefully hold the DIMM by the edges to avoid pressure on the components on the DIMM circuit board. 5. Repeat these steps to remove additional DIMMs as needed.
Procedure
1. If you are not already grounded, properly ground yourself. 2. Locate the slot where you are installing the new DIMM. 3. Remove the replacement DIMM from the antistatic shipping bag, hold the DIMM by the corners, and align it over the slot. The notch among the pins on the DIMM should line up with the tab in the socket. 4. Insert the DIMM straight into the slot. The DIMM fits tightly in the slot, but should go in easily. If not, realign the DIMM with the slot and reinsert it. Attention: Visually inspect the DIMM to verify that it is evenly aligned and fully inserted into the slot. 5. Push carefully, but firmly, on the top edge of the DIMM until the latches snap into place over the notches at the ends of the DIMM. 6. Repeat the preceding steps to install additional DIMMs as needed. v If you are only replacing the DIMM, plug in the battery, close the CPU air duct, and then go to Reinstalling the controller module and booting the system on page 37. v If you are replacing both the DIMMs and the NVMEM battery, continue with the next step and the following topics. 7. Close the CPU air duct.
36
Procedure
1. Align the tabs on the battery holder with the notches in the controller module side, and gently push the battery housing so that the notches are under the lip of the controller module side.
1 2 3
2. While gently pushing the battery against the sheet metal on the chassis to hold it in the battery guide, place the forefinger of your free hand against the battery housing behind the locking tab on the battery, and then gently push the battery housing away from the CPU air duct. If it is properly aligned, the battery snaps into place on the side of the controller module. If it does not, repeat these steps. 3. Seat the battery in the holder and plug it into the controller module. The plug should lock down onto the socket on the controller module. 4. Close the CPU air duct, if necessary.
37
Procedure
1. Align the end of the controller module with the opening in the chassis, if necessary, and then gently push the controller module halfway into the system. 2. Reinstall the cable management arms and recable the controller module, as needed. When recabling, remember to reinstall the media converters (SFPs) if you are using fiber cables. 3. Reinstall the controller module: a. Push the controller module all the way into the system. b. Push the cam handle to finish seating the controller module. c. Close the cam and tighten the thumbscrew on the cam handle. d. Halt the boot process: v For systems in an HA pair, press Ctrl-c to stop the boot process. v For stand-alone systems, reconnect the power cables to the power supplies and to the power sources, and then turn on the power. Press Ctrl-c to stop the boot process. The boot process is halted at either the Boot menu or the Loader prompt.
Procedure
1. Complete the applicable step, depending on where the node halted during the boot process: v If the node halted at the Loader prompt, continue with the next step in this procedure. v If the node halted at the Boot menu, then perform the following steps to reach the Loader prompt before continuing with this procedure. a. Select the Maintenance mode option from the displayed menu. b. Enter the following command at the prompt: halt 2. c. Continue with the next step in this procedure. Enter the following command at the Loader prompt: boot_diags Note: You must run this command from the Loader prompt for sldiag to function properly. The boot_diags command starts special drivers designed specifically for sldiag. The Maintenance mode prompt (*>) appears. 3. Enter the following command at the Maintenance mode prompt: sldiag
38
For details about the sldiag command, see the sldiag man page. 4. Clear the status logs by entering the following command: sldiag device clearstatus 5. Verify that the log is cleared by entering the following command: sldiag device status The following default response is displayed:
SLDIAG: No log messages are present.
6. Enter the following command at the prompt: sldiag device run -dev nvmem 7. View the status of the test by entering the following command: sldiag device status Your storage system provides the following output while the tests are still running:
There are still test(s) being processed.
After all the tests are complete, the following response appears by default:
*> <SLDIAG:_ALL_TESTS_COMPLETED>
8. Verify that no hardware problems resulted from the addition or replacement of hardware components on your system by entering the following command: sldiag device status [-dev devtype] [-name device] -long -state failed System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of failures resulting from testing the component. 9. Proceed based on the result of the preceding step.
If the system-level diagnostics tests... Were completed without any failures Then... 1. Clear the status logs by entering the following command: sldiag device clearstatus 2. Verify that the log is cleared by entering the following command: sldiag device status The following default response is displayed:
SLDIAG: No log messages are present.
3. Exit Maintenance mode by entering the following command: halt 4. Enter the following command at the firmware prompt to reboot the storage system: boot 5. If your system is in an HA pair , run the cf giveback command from the partner node console. You have completed system-level diagnostics.
39
Then... Determine the cause of the problem. 1. Exit Maintenance mode by entering the following command: halt 2. Perform a clean shutdown and disconnect the power supplies. 3. Verify that you have observed all the considerations identified for running system-level diagnostics, that cables are securely connected, and that hardware components are properly installed in the storage system. 4. Reconnect the power supplies and power on the storage system. 5. Rerun the system-level diagnostics tests.
Disposing of batteries
Dispose of batteries according to local regulations regarding battery recycling or disposal.
v All other components in the system must be functioning properly; if not, contact technical support.
40
Procedure
1. Check the status of the target node (the node you want to perform maintenance on) by entering the cf status command at the system console of either node. 2. Take one of the following actions, depending on the result of the cf status command:
If... Neither node is in takeover mode The partner node took over the target node Then... Go to the next step in this procedure. The target node is in a state where you can begin removing it from the system chassis. Continue with "Opening the System." The target node took over the partner node 1. Correct the problem that caused the takeover. 2. Run the cf giveback command from the target node console. 3. Go back to the beginning of this procedure.
3. Take over the target node by entering the cf takeover command from the partner node's console. 4. Continue with "Opening the System."
Procedure
1. Enter the halt command from the system console. Attention: You must perform a clean system shutdown before replacing system components to avoid losing unwritten data in the nonvolatile memory (NVMEM). The NVMEM LED is located on the controller module to the right of the network ports, marked with a battery symbol. If the NVMEM LED is flashing, there is content in the NVMEM that has not been saved to disk. You need to reboot the controller module and proceed from the beginning of this procedure. 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.
c0a
0c
e0a
0a LNK
0b LNK
!
c0b 0d e0b
1
Figure 23. NVMEM LED
41
NVMEM LED
2. If you are not already grounded, properly ground yourself. 3. Turn off the power supplies, unplug the power cords from the power source, and remove the power cords.
Procedure
1. If you are not already grounded, properly ground yourself. 2. Unplug the system cables from the controller module, as needed, and keep track of where the cables were connected. Leave the cables in the cable management arm so that when you reinstall the cable management arm in the controller module, the cables will be organized. 3. Disconnect the right and left cable management arms from the controller module. To release the arms, press the silver button on the power supply side of each arm, and then remove the arm from the controller module. 4. Loosen the thumbscrew on the cam handle. 5. Pull the cam handle downward and slide the controller module out of the system.
Procedure
1. If you are not already grounded, properly ground yourself. 2. Open the CPU air duct. 3. Locate the DIMMs. Note: Each system memory DIMM has an LED located on the board next to each DIMM slot. The LED is illuminated if the DIMM needs to be replaced. This illustration shows a system fully populated with DIMMs:
42
1
1 2 3 4 1 2
NVMEM DIMMs 1 and 2. Note: See Replacing an NVMEM battery and NVMEM DIMMs in an N6200 series system on page 30 for information about removing these two DIMMs. System DIMMs 1 through 4. The number of DIMMs in your system will vary. DIMM sockets 1 and 2 are populated in all models, while DIMM sockets 3 and 4 are only populated in the N6270.
DIMM sockets. The NVMEM DIMM sockets have white DIMM locking tabs, while the system DIMM sockets have black locking tabs.
4. Note the orientation of the DIMM in the socket so that you can insert the replacement DIMM in the proper orientation. 5. 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.
43
CAUTION: The DIMMs are located very close to the CPU heat sync, which might still be hot. Avoid touching the CPU heat sync when removing the DIMM. Attention: Carefully hold the DIMM by the edges to avoid pressure on the components on the DIMM circuit board. 6. Repeat these steps to remove additional DIMMs as needed.
Procedure
1. If you are not already grounded, properly ground yourself. 2. Locate the slot where you are installing the new DIMM. 3. Remove the replacement DIMM from the antistatic shipping bag, hold the DIMM by the corners, and align it over the slot. The notch among the pins on the DIMM should line up with the tab in the socket. 4. Insert the DIMM straight into the slot. The DIMM fits tightly in the slot, but should go in easily. If not, realign the DIMM with the slot and reinsert it. Attention: Visually inspect the DIMM to verify that it is evenly aligned and fully inserted into the slot. 5. Push carefully, but firmly, on the top edge of the DIMM until the latches snap into place over the notches at the ends of the DIMM. 6. Repeat the preceding steps to install additional DIMMs as needed. v If you are only replacing the DIMM, plug in the battery, close the CPU air duct, and then go to Reinstalling the controller module and booting the system on page 37. v If you are replacing both the DIMMs and the NVMEM battery, continue with the next step and the following topics. 7. Close the CPU air duct.
44
Procedure
1. Align the end of the controller module with the opening in the chassis, if necessary, and then gently push the controller module halfway into the system. 2. Reinstall the cable management arms and recable the controller module, as needed. When recabling, remember to reinstall the media converters (SFPs) if you are using fiber cables. 3. Reinstall the controller module: a. Push the controller module all the way into the system. b. Push the cam handle to finish seating the controller module. c. Close the cam and tighten the thumbscrew on the cam handle. d. Halt the boot process: v For systems in an HA pair, press Ctrl-c to stop the boot process. v For stand-alone systems, reconnect the power cables to the power supplies and to the power sources, and then turn on the power. Press Ctrl-c to stop the boot process. The boot process is halted at either the Boot menu or the Loader prompt.
Procedure
1. Complete the applicable step, depending on where the node halted during the boot process: v If the node halted at the Loader prompt, continue with the next step in this procedure. v If the node halted at the Boot menu, then perform the following steps to reach the Loader prompt before continuing with this procedure. a. Select the Maintenance mode option from the displayed menu. b. Enter the following command at the prompt: halt c. Continue with the next step in this procedure. 2. Enter the following command at the Loader prompt: boot_diags Note: You must run this command from the Loader prompt for sldiag to function properly. The boot_diags command starts special drivers designed specifically for sldiag. The Maintenance mode prompt (*>) appears. 3. Enter the following command at the Maintenance mode prompt: sldiag For details about the sldiag command, see the sldiag man page. 4. Clear the status logs by entering the following command:
Chapter 4. Replacing N6200 series system devices
45
sldiag device clearstatus 5. Verify that the log is cleared by entering the following command: sldiag device status The following default response is displayed:
SLDIAG: No log messages are present.
6. Check the status of the system memory by entering the following command at the prompt: sldiag device run -dev mem 7. View the status of the test by entering the following command: sldiag device status Your storage system provides the following output while the tests are still running:
There are still test(s) being processed.
After all the tests are complete, the following response appears by default:
*> <SLDIAG:_ALL_TESTS_COMPLETED>
8. Verify that no hardware problems resulted from the addition or replacement of hardware components on your system by entering the following command: sldiag device status [-dev devtype] [-name device] -long -state failed System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of failures resulting from testing the component. 9. Proceed based on the result of the preceding step.
If the system-level diagnostics tests... Were completed without any failures Then... 1. Clear the status logs by entering the following command: sldiag device clearstatus 2. Verify that the log is cleared by entering the following command: sldiag device status The following default response is displayed:
SLDIAG: No log messages are present.
3. Exit Maintenance mode by entering the following command: halt 4. Enter the following command at the firmware prompt to reboot the storage system: boot 5. If your system is in an HA pair , run the cf giveback command from the partner node console. You have completed system-level diagnostics.
46
Then... Determine the cause of the problem. 1. Exit Maintenance mode by entering the following command: halt 2. Perform a clean shutdown and disconnect the power supplies. 3. Verify that you have observed all the considerations identified for running system-level diagnostics, that cables are securely connected, and that hardware components are properly installed in the storage system. 4. Reconnect the power supplies and power on the storage system. 5. Rerun the system-level diagnostics tests.
What to do next
See the IBM System Storage N series System-Level Diagnostics Guide for more information on running diagnostics.
47
Procedure
1. Check the status of the target node (the node you want to perform maintenance on) by entering the cf status command at the system console of either node. 2. Take one of the following actions, depending on the result of the cf status command:
If... Neither node is in takeover mode The partner node took over the target node Then... Go to the next step in this procedure. The target node is in a state where you can begin removing it from the system chassis. Continue with "Opening the System." The target node took over the partner node 1. Correct the problem that caused the takeover. 2. Run the cf giveback command from the target node console. 3. Go back to the beginning of this procedure.
3. Take over the target node by entering the cf takeover command from the partner node's console. 4. Continue with "Opening the System."
Procedure
1. Enter the halt command from the system console. Attention: You must perform a clean system shutdown before replacing system components to avoid losing unwritten data in the nonvolatile memory (NVMEM). The NVMEM LED is located on the controller module to the right of the network ports, marked with a battery symbol. If the NVMEM LED is flashing, there is content in the NVMEM that has not been saved to disk. You need to reboot the controller module and proceed from the beginning of this procedure. 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.
48
c0a
0c
e0a
0a LNK
0b LNK
!
c0b 0d e0b
1
Figure 26. NVMEM LED
NVMEM LED
2. If you are not already grounded, properly ground yourself. 3. Turn off the power supplies, unplug the power cords from the power source, and remove the power cords.
Procedure
1. If you are not already grounded, properly ground yourself. 2. Unplug the system cables from the controller module, as needed, and keep track of where the cables were connected. Leave the cables in the cable management arm so that when you reinstall the cable management arm in the controller module, the cables will be organized. 3. Disconnect the right and left cable management arms from the controller module. To release the arms, press the silver button on the power supply side of each arm, and then remove the arm from the controller module. 4. Loosen the thumbscrew on the cam handle. 5. Pull the cam handle downward and slide the controller module out of the system.
Procedure
1. Loosen the thumbscrew on the controller module side panel. 2. Swing the side panel open until it comes off the controller module.
49
1 2
Figure 27. Removing the PCI card
1 2
Controller module side panel with thumbscrew Controller module PCIe card
3. Remove the PCIe card from the controller module and set it aside. 4. Repeat the preceding steps as needed.
Procedure
1. Open the controller module side panel, if necessary, slide off the PCIe card filler plate, as needed, and install the PCIe card. Be sure that you properly align the card in the slot and exert even pressure on the card when seating it in the socket. The adapter must be fully and evenly seated in the slot. Note: If you are installing a card in the bottom slot and cannot see the card socket well, remove the top card so that you can see the card socket, install the card, and the reinstall the card you removed from the top slot. 2. Repeat the preceding step as needed for additional cards. 3. Close the side panel and tighten the thumbscrew.
50
Procedure
1. Align the end of the controller module with the opening in the chassis, if necessary, and then gently push the controller module halfway into the system. 2. Reinstall the cable management arms and recable the controller module, as needed. When recabling, remember to reinstall the media converters (SFPs) if you are using fiber cables. 3. Reinstall the controller module: a. Push the controller module all the way into the system. b. Push the cam handle to finish seating the controller module. c. Close the cam and tighten the thumbscrew on the cam handle. d. Halt the boot process: v For systems in an HA pair, press Ctrl-c to stop the boot process. v For stand-alone systems, reconnect the power cables to the power supplies and to the power sources, and then turn on the power. Press Ctrl-c to stop the boot process. The boot process is halted at either the Boot menu or the Loader prompt.
51
Procedure
1. Complete the applicable step, depending on where the node halted during the boot process: v If the node halted at the Loader prompt, continue with the next step in this procedure. v If the node halted at the Boot menu, then perform the following steps to reach the Loader prompt before continuing with this procedure. a. Select the Maintenance mode option from the displayed menu. b. Enter the following command at the prompt: halt c. Continue with the next step in this procedure. 2. Enter the following command at the Loader prompt: boot_diags Note: You must run this command from the Loader prompt for sldiag to function properly. The boot_diags command starts special drivers designed specifically for sldiag. The Maintenance mode prompt (*>) appears. 3. Enter the following command at the Maintenance mode prompt: sldiag For details about the sldiag command, see the sldiag man page. 4. Clear the status logs by entering the following command: sldiag device clearstatus 5. Verify that the log is cleared by entering the following command: sldiag device status The following default response is displayed:
SLDIAG: No log messages are present.
6. View the types of devices available for checking by entering the following command: sldiag device show 7. Run the test for the type of PCIe card you installed by entering the following command at the Maintenance mode prompt: sldiag device run -dev fcal|sas|ata|nic|toe Note: See the IBM System Storage N series System-Level Diagnostics Guide for a description of other types of tests you can run. 8. View the status of the test by entering the following command: sldiag device status Your storage system provides the following output while the tests are still running:
There are still test(s) being processed.
After all the tests are complete, the following response appears by default:
*> <SLDIAG:_ALL_TESTS_COMPLETED>
9. Verify that no hardware problems resulted from the addition or replacement of hardware components on your system by entering the following command:
52
sldiag device status [-dev devtype] [-name device] -long -state failed System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of failures resulting from testing the component. 10. Proceed based on the result of the preceding step.
If the system-level diagnostics tests... Were completed without any failures Then... 1. Clear the status logs by entering the following command: sldiag device clearstatus 2. Verify that the log is cleared by entering the following command: sldiag device status The following default response is displayed:
SLDIAG: No log messages are present.
3. Exit Maintenance mode by entering the following command: halt 4. Enter the following command at the firmware prompt to reboot the storage system: boot 5. If your system is in an HA pair , run the cf giveback command from the partner node console. You have completed system-level diagnostics. Resulted in some test failures Determine the cause of the problem. 1. Exit Maintenance mode by entering the following command: halt 2. Perform a clean shutdown and disconnect the power supplies. 3. Verify that you have observed all the considerations identified for running system-level diagnostics, that cables are securely connected, and that hardware components are properly installed in the storage system. 4. Reconnect the power supplies and power on the storage system. 5. Rerun the system-level diagnostics tests.
53
Replacing a boot device in an N6200 series system running Data ONTAP 7.3.5 and later releases in the Data ONTAP 7.3 release family
The boot device stores a primary and secondary set of system files on it (also called the boot image) that the system uses when it boots. To replace the boot device, you must complete a specific sequence of tasks.
Procedure
1. Shut down the system or node.
If the system is in... A stand-alone configuration and is running Then... 1. Enter the following command at the console: halt -t 0 2. Go to the next step. A stand-alone configuration and is not running An HA pair Go to the next step. 1. Check the status of the target node by entering the following command at the console: cf status 2. Take one of the following actions, depending on the result of cf status command: v If the target node is not running or has been taken over by the partner node, go to the next step. v If the target node has not been taken over by the partner node and is running, enter the following command, and then go to the next step: cf takeover
54
2. If applicable, turn off the power supplies, unplug both power cords from the power source and then remove the power cords.
Procedure
1. If you are not already grounded, properly ground yourself. 2. Unplug the system cables from the controller module, as needed, and keep track of where the cables were connected. Leave the cables in the cable management arm so that when you reinstall the cable management arm in the controller module, the cables will be organized. 3. Disconnect the right and left cable management arms from the controller module. To release the arms, press the silver button on the power supply side of each arm, and then remove the arm from the controller module. 4. Loosen the thumbscrew on the cam handle. 5. Pull the cam handle downward and slide the controller module out of the system.
Procedure
1. If you are not already grounded, properly ground yourself. 2. Remove the controller module and turn it so that you can see where the boot device is located. Use the FRU map on the controller module or the following illustration to help you locate the boot device enclosure.
55
1 2
3. Open the boot device cover and gently lift the boot device out of the housing. 4. Set the boot device aside.
Installing the boot device and transferring system files to the boot device
You can transfer the system files and restore configuration information to your system by using netboot to boot the system and performing a software update to copy the system files to the replacement boot device.
56
v Access to the IBM N series support website, which is accessed and navigated as described in Using the IBM N series support website on page 26. This enables you to download the necessary system files for your platform and version of Data ONTAP running on it. v A copy of the Data ONTAP 7.3 Upgrade Guide, available on the IBM N series support website.
Procedure
1. If your system is in an active/active configuration, check the version of Data ONTAP you are running by entering the following command on the partner's console: version 2. Copy the boot image ( <release>_netboot.q) and software image ( <release>_setup_q.exe) from the IBM N series support website, which is accessed and navigated as described in Using the IBM N series support website on page 26, to a web-accessible directory. On the IBM N series support website, the Data ONTAP Matrix provides a current list and history of Data ONTAP releases available by release family and supported storage systems. 3. If you are not already grounded, properly ground yourself. 4. Turn the controller module so that you can locate the boot device enclosure. Use the FRU map on the controller module to help you locate the boot device enclosure. 5. Lift the boot device cover, if applicable. 6. Align the boot device with the boot device socket or connector, and then firmly push it into the socket or connector. 7. Check the boot device to make sure that it is seated squarely and completely in the socket or connector, and reseat the boot device, if necessary. 8. Close the boot device cover. 9. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system. 10. Reinstall the cable management arms and recable the system, as needed. When recabling, remember to reinstall the media converters (SFPs) if you are using fiber cables. 11. Push the controller module all the way into the system, firmly push the cam handle to finish seating it, push the cam handle to the closed position, and then tighten the thumbscrew.
If your system is in... A stand-alone configuration Then... Reconnect the power cables to the power supplies and to the power sources, and then turn on the power. The node reboots as soon as you seat the controller module completely into the system.
An HA configuration
12. Enter one of the following commands at the firmware prompt: v If you are configuring DHCP, enter the following command: ifconfig e0a -auto v If you are configuring manual connections, enter the following command: ifconfig e0a -addr=filer_addr -mask=netmask -gw=gateway -dns=dns_addr -domain=dns_domain
57
filer_addr is the IP address of the storage system. netmask is the network mask of the storage system. gateway is the gateway for the storage system. dns_addr is the IP address of a name server on your network. dns_domain is the Domain Name System (DNS) domain name. If you use this optional parameter, you do not need a fully qualified domain name in the netboot server URL; you need only the server's host name. Note: Other parameters might be necessary for your interface. Enter help ifconfig at the firmware prompt for details. 13. At the firmware prompt, enter the following command: netboot http://path_to_the_web-accessible_directory/ <release>_netboot.q The system begins to boot, but stops at the Boot menu. 14. Select the Normal Boot option from the displayed menu.
Please choose one of the following: 1) Normal Boot 2) Boot without /etc/rc 3) Change Password 4) Initialize all disks 4a) Same as option 4, but create a flexible root volume 5) Maintenance mode boot Selection (1-5)? 1
16. Copy and install the image from your HTTP server by entering the following command: software update http://path_to_the_web-accessible_directory/ <release>_setup_q.exe -r 17. Reapply any BIOS or firmware service images that were previously installed on the node by entering the following commands and noting the displayed information: version -b sysconfig 18. Verify that the correct BIOS or firmware service images are installed.
If your system is in... A stand-alone configuration Then... Use the most current versions available for your system.
58
Then... Compare the displayed versions from the target node with the versions installed on the partner node. If the versions are not the same, update that target node by installing the same version of files on the target node from any applicable service images available from the IBM N series support website, which is accessed and navigated as described in Using the IBM N series support website on page 26.
Replacing a boot device in an N6200 series system running Data ONTAP 7-Mode
The boot device stores a primary and secondary set of system files on it (also called the boot image) that the system uses when it boots. To replace the boot device, you must complete a specific sequence of tasks.
59
v You can use this procedure only with systems running Data ONTAP 7-Mode.
Procedure
1. Shut down the system or node.
If the system is in... A stand-alone configuration and is running Then... 1. Enter the following command at the console: halt -t 0 2. Go to the next step. A stand-alone configuration and is not running An HA pair Go to the next step. 1. Check the status of the target node by entering the following command at the console: cf status 2. Take one of the following actions, depending on the result of cf status command: v If the target node is not running or has been taken over by the partner node, go to the next step. v If the target node has not been taken over by the partner node and is running, enter the following command, and then go to the next step: cf takeover
2. If you are replacing a device in a stand-alone system, or if you are replacing a device in one enclosure of a dual-enclosure HA pair, turn off the power supplies in the enclosure, unplug the power cords from the power source, and then remove the power cords from the power supplies. If you are replacing a device in a single-enclosure HA pair, do not remove power from the enclosure.
Procedure
1. If you are not already grounded, properly ground yourself. 2. Unplug the system cables from the controller module, as needed, and keep track of where the cables were connected. Leave the cables in the cable management arm so that when you reinstall the cable management arm in the controller module, the cables will be organized.
60
3. Disconnect the right and left cable management arms from the controller module. To release the arms, press the silver button on the power supply side of each arm, and then remove the arm from the controller module. 4. Loosen the thumbscrew on the cam handle. 5. Pull the cam handle downward and slide the controller module out of the system.
Procedure
1. If you are not already grounded, properly ground yourself. 2. Remove the controller module and turn it so that you can see where the boot device is located. Use the FRU map on the controller module or the following illustration to help you locate the boot device enclosure.
1 2
3. Open the boot device cover and gently lift the boot device out of the housing.
Chapter 4. Replacing N6200 series system devices
61
Installing the boot device and transferring system files disruptively using netboot in a 7-Mode system
You can transfer the system files and restore configuration information to your system by using netboot to copy the system files to the replacement boot device.
Procedure
1. Download and extract the netboot.tgz file from the IBM N series support website, which is accessed and navigated as described in Using the IBM N series support website on page 26.. This file is used for performing a netboot of your system. Download the file contents to a web-accessible directory. To download the file, complete the following substeps: a. Download the netboot.tgz file from the IBM N series support website to the web-accessible directory. b. Change to the web-accessible directory. c. Extract the contents of the netboot.tgz file to the target directory by entering the following command: tar -zxvf netboot.tgz Your directory listing should contain the following directory:
netboot/
2. Download the image.tgz file from the IBM N series support website to the web-accessible directory. Your directory listing should contain the following file and directory:
image.tgz netboot/
3. If you are not already grounded, properly ground yourself. 4. Turn the controller module so that you can locate the boot device enclosure. Use the FRU map on the controller module to help you locate the boot device enclosure. 5. Lift the boot device cover, if applicable. 6. Align the boot device with the boot device socket or connector, and then firmly push it into the socket or connector.
62
7. Check the boot device to make sure that it is seated squarely and completely in the socket or connector, and reseat the boot device, if necessary. 8. Close the boot device cover. 9. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system. 10. Reinstall the cable management arms and recable the system, as needed. When recabling, remember to reinstall the media converters (SFPs) if you are using fiber cables. 11. Push the controller module all the way into the system, firmly push the cam handle to finish seating it, push the cam handle to the closed position, and then tighten the thumbscrew.
If your system is in... A stand-alone configuration Then... Reconnect the power cables to the power supplies and to the power sources, and then turn on the power. The node reboots as soon as you seat the controller module completely into the system.
An HA configuration
12. Enter one of the following commands at the firmware prompt: v If you are configuring DHCP, enter the following command: ifconfig e0a -auto v If you are configuring manual connections, enter the following command: ifconfig e0a -addr=filer_addr -mask=netmask -gw=gateway -dns=dns_addr -domain=dns_domain filer_addr is the IP address of the storage system. netmask is the network mask of the storage system. gateway is the gateway for the storage system. dns_addr is the IP address of a name server on your network. dns_domain is the Domain Name System (DNS) domain name. If you use this optional parameter, you do not need a fully qualified domain name in the netboot server URL; you need only the server's host name. Note: Other parameters might be necessary for your interface. Enter help ifconfig at the firmware prompt for details. 13. At the firmware prompt, enter the following command: netboot http://path_to_the_web-accessible_directory/netboot/kernel The system begins to boot, but stops at the Boot menu. 14. Select the Install new software first option from the displayed menu.
Please choose one of the following: (1) Normal Boot (2) Boot without etc/rc. (3) Change password. (4) Clean configuration and initialize all disks. (5) Maintenance mode boot. (6) Update flash from backup config. (7) Install new software first. (8) Reboot node. Selection (1-8)? 7
63
This menu option downloads and installs the new Data ONTAP image to the boot device. Note: During the software install process, you are prompted for the URL of the image.tgz file. Enter the path as follows: http://path_to_the_web-accessible_directory/image.tgz 15. Your next step depends on which version of Data ONTAP is installed on your system. If your system is running Data ONTAP 8.0: Reboot the node by entering y when you see the following prompt:
The node must be rebooted to start using the newly installed software. Do you want to reboot now? [y/n} y
The controller reboots, but stops at the Boot Menu because the boot device has been reformatted and the configuration data needs to be restored. If your system is running Data ONTAP 8.0.1 or later: Complete the following substeps: a. Enter n to skip the backup recovery when you see the following prompt:
************************************************************** * Restore Backup Configuration * * This procedure only applies to storage controllers that * * are configured as an HA pair. * * * * Choose Yes to restore the varfs backup configuration * * from a TFTP server. Refer to the Boot Device Replacement * * guide for more details. * * Choose No to skip the back up recovery and return to the * * boot menu. * ************************************************************** Do you want to restore the backup configuration now? {y|n} n
b. Reboot the node by entering y when you see the following prompt:
The node must be rebooted to start using the newly installed software. Do you want to reboot now? [y/n} y
The controller reboots, but stops at the boot environment prompt. c. Boot Data ONTAP by entering the following command at the boot environment prompt: boot_ontap The controller reboots, but stops at the Boot Menu because the boot device has reformatted and the configuration data needs to be restored. 16. Select the Update flash from backup config option from the displayed menu.
Please choose one of the following: (1) Normal Boot (2) Boot without etc/rc. (3) Change password. (4) Clean configuration and initialize all disks. (5) Maintenance mode boot. (6) Update flash from backup config. (7) Install new software first. (8) Reboot node. Selection (1-8)? 6
64
This will replace all flash-based configuration with the last backup to disk. Are you sure you want to continue?:y
The system automatically reboots when the syncflash process is complete. 18. Your next step depends on your system configuration.
If your system is... A stand-alone configuration An HA configuration Description You can begin using your system. Complete the following substeps: 1. Enter the following command at the boot environment prompt: boot_ontap 2. Give back the node after the boot process completes by entering the following command from the partner console: cf giveback
Installing the boot device and transferring system files nondisruptively using netboot in a 7-Mode system
You can nondisruptively transfer the system files and restore configuration information to your HA configuration by using netboot and a the partner node.
Procedure
1. Download and extract the netboot.tgz file from the IBM N series support website, which is accessed and navigated as described in Using the IBM N series support website on page 26.. This file is used for performing a netboot of your system. Download the file contents to a web-accessible directory. To download the file, complete the following substeps: a. Download the netboot.tgz file from the IBM N series support website to the web-accessible directory. b. Change to the web-accessible directory. c. Extract the contents of the netboot.tgz file to the target directory by entering the following command: tar -zxvf netboot.tgz Your directory listing should contain the following directory:
netboot/
65
2. Download the image.tgz file from the IBM N series support website to the web-accessible directory. Your directory listing should contain the following file and directory:
image.tgz netboot/
3. If you are not already grounded, properly ground yourself. 4. Turn the controller module so that you can locate the boot device enclosure. Use the FRU map on the controller module to help you locate the boot device enclosure. 5. Open the boot device cover, if applicable. 6. Align the boot device with the boot device socket or connector, and then firmly push it into the socket or connector. 7. Check the boot device to make sure that it is seated squarely and completely in the socket or connector, and reseat the boot device, if necessary. 8. Close the boot device cover. 9. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system. 10. Reinstall the cable management arms and recable the system, as needed. When recabling, remember to reinstall the media converters (SFPs) if you are using fiber cables. 11. Push the controller module all the way into the system, firmly pushing the cam handle to finish seating it, push the cam handle to the closed position and then tighten the thumbscrew. The node reboots and stops at the firmware prompt as soon as you seat the controller module completely into the system. 12. Set up the TFTP server on the partner node by entering the following commands on the partner node console: a. partner options tftpd.enable off b. partner options tftpd.rootdir /etc c. partner options tftpd.enable on 13. Enter one of the following commands at the firmware prompt: v If you are configuring DHCP, enter the following command: ifconfig e0a -auto v If you are configuring manual connections, enter the following command: ifconfig e0a -addr=filer_addr -mask=netmask -gw=gateway -dns=dns_addr -domain=dns_domain filer_addr is the IP address of the storage system. netmask is the network mask of the storage system. gateway is the gateway for the storage system. dns_addr is the IP address of a name server on your network. dns_domain is the Domain Name System (DNS) domain name. If you use this optional parameter, you do not need a fully qualified domain name in the netboot server URL; you need only the server's host name. Note: Other parameters might be necessary for your interface. Enter help ifconfig at the firmware prompt for details. 14. At the firmware prompt, enter the following command: netboot http://path_to_web-accessible_directory/netboot/kernel 15. Select the Install new software first option from the displayed menu.
66
Please choose one of the following: (1) Normal Boot (2) Boot without etc/rc. (3) Change password. (4) Clean configuration and initialize all disks. (5) Maintenance mode boot. (6) Update flash from backup config. (7) Install new software first. (8) Reboot node. Selection (1-8)? 7
This menu option downloads and installs the new Data ONTAP image to the boot device. 16. Enter y when you see the following prompt:
This procedure is not supported for Non-Disruptive Upgrade on an HA pair. Do you want to continue? [y|no]y
17. Enter the path to the image.tgz when you see the following prompt:
What is the URL for the package? http://path_to_web-accessible_directory/image.tgz
18. Restore the backup configuration by entering y and then entering the IP address of the server containing the varfs.tgz file when you see the following screen:
**************************************************************** * Restore Backup Configuration * * This procedure only applies to storage controllers that * * are configures as an HA pair. * * * * Choose Yes to restore the "varfs" backup configuration * * from the TFTP server. Refer to the Boot Device Replacement * * guide for more details. * * Choose No to skip the backup and recovery and return to the * * boot menu. * **************************************************************** Do you want to restore the backup configuration now? {y|n} y Enter the IP address of the server: target_node.management_IP.address Checking network link... success. Checking route to host "target_node.management_IP.address"... success. Attempting to reach "target_node.management_IP.address"... success. Checking boot device file system... success. Mounting boot device to /tmp/mnt... success. Checking boot device mount point... success. Restoring backup configuration... Received 82481 bytes in 0.1 seconds Backup Configuration successfully restored
19. Reboot the target node by entering y when you see the following prompt:
The node must be rebooted to start using the newly installed software. Do you want to reboot now? {y|n} y
20. While the target node is rebooting, restore the tftp settings on the partner node by entering the following commands from the partner node console: a. partner options tftpd.enable off b. partner options tftpd.rootdir /etc/tftpboot 21. Reboot the target node by entering the following command on the target node console: boot_ontap
Chapter 4. Replacing N6200 series system devices
67
22. Once the target node has rebooted, complete the procedure by entering the following command on the partner node's console: cf giveback
Procedure
1. Check the status of the target node (the node you want to perform maintenance on) by entering the cf status command at the system console of either node. 2. Take one of the following actions, depending on the result of the cf status command:
If... Neither node is in takeover mode The partner node took over the target node Then... Go to the next step in this procedure. The target node is in a state where you can begin removing it from the system chassis. Continue with "Opening the System." The target node took over the partner node 1. Correct the problem that caused the takeover. 2. Run the cf giveback command from the target node console. 3. Go back to the beginning of this procedure.
68
3. Take over the target node by entering the cf takeover command from the partner node's console. 4. If you are not already grounded, properly ground yourself. 5. Turn off the power supplies, unplug the power cords from the power source, and remove the power cords.
Procedure
1. Enter the halt command from the system console. Attention: You must perform a clean system shutdown before replacing system components to avoid losing unwritten data in the nonvolatile memory (NVMEM). The NVMEM LED is located on the controller module to the right of the network ports, marked with a battery symbol. If the NVMEM LED is flashing, there is content in the NVMEM that has not been saved to disk. You need to reboot the controller module and proceed from the beginning of this procedure. 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.
c0a
0c
e0a
0a LNK
0b LNK
!
c0b 0d e0b
1
Figure 30. NVMEM LED
NVMEM LED
2. If you are not already grounded, properly ground yourself. 3. Turn off the power supplies, unplug the power cords from the power source, and remove the power cords.
Procedure
1. If you are not already grounded, properly ground yourself. 2. Unplug the system cables from the I/O expansion module, as needed, and keep track of where the cables were connected. Leave the cables in the cable management arm so that when you install the cable management arm in the new I/O expansion module, the cables will be organized.
Chapter 4. Replacing N6200 series system devices
69
3. Remove the cable management arms for the left and right sides of the controller module and set them aside. 4. Loosen the thumbscrew on the cam handle. 5. Pull the cam handle down and slide the I/O expansion module out of the system, and then place it on an anti-static surface. 6. Remove the side panels from the I/O expansion module by loosening the side panel thumbscrew and swinging the side panel out of the way.
4 3
2 1
1 2
Left side panel, seen from the side farthest away from the cam handle, of the I/O expansion module. Left PCIe card or cards. There can be two PCIe cards per side of the I/O expansion module.
3 4
Right PCIe card or cards. Right side panel, side farthest away from the cam handle, of the I/O expansion module.
7. Remove the PCIe cards, noting their locations so that you can install them into the same slots in the new I/O expansion module.
Procedure
1. Open the new I/O expansion module side panels, as needed. 2. Remove the card filler plates for any slots where you will be installing PCIe cards. 3. Install the individual PCIe cards into the proper I/O expansion module slots by aligning each PCIe card with the target slot, and then gently seating it into the socket. Make sure that you install the PCIe cards in the same locations in the new I/O expansion module as where they were in the old I/O expansion module. 4. Close the side panels and tighten the side panel thumbscrews. 5. Align the I/O expansion module with the bottom opening of the bottom bay of the target chassis (labeled B on the bay), and gently slide the I/O expansion module all the way into the chassis using the cam handle. The I/O expansion
70
module cam handle begins to engage prior to fully seating into the chassis. Use the cam handle to fully seat the module into the chassis. 6. Push the cam handle all the way to the closed position, and then tighten the thumbscrew on the cam handle. 7. Reinstall the cable management arms, and recable your I/O expansion module.
Procedure
1. Reconnect the system to the power source and turn on the power. 2. As the system boots, interrupt the process during the memory test by pressing Ctrl-C. The boot process is halted at either the Boot menu or the Loader prompt. 3. Complete the applicable step, depending on where the node halted during the boot process: v If the node halted at the Loader prompt, continue with the next step in this procedure. v If the node halted at the Boot menu, then perform the following steps to reach the Loader prompt before continuing with this procedure. a. Select the Maintenance mode option from the displayed menu. b. Enter the following command at the prompt: halt c. Continue with the next step in this procedure. 4. Enter the following command at the Loader prompt: boot_diags Note: You must run this command from the Loader prompt for sldiag to function properly. The boot_diags command starts special drivers designed specifically for sldiag. The Maintenance mode prompt (*>) appears.
Chapter 4. Replacing N6200 series system devices
71
5. Enter the following command at the Maintenance mode prompt: sldiag For details about the sldiag command, see the sldiag man page. 6. Clear the status logs by entering the following command: sldiag device clearstatus 7. Verify that the log is cleared by entering the following command: sldiag device status The following default response is displayed:
SLDIAG: No log messages are present.
8. View the types of devices available for checking by entering the following command: sldiag device show 9. Run the test for the type of PCIe cards installed in the I/O expansion module by entering the following command at the Maintenance mode prompt: sldiag device run -dev fcal|sas|ata|nic|toe Note: See the IBM System Storage N series System-Level Diagnostics Guide for a description of other types of tests you can run. 10. View the status of the test by entering the following command: sldiag device status Your storage system provides the following output while the tests are still running:
There are still test(s) being processed.
After all the tests are complete, the following response appears by default:
*> <SLDIAG:_ALL_TESTS_COMPLETED>
11. Verify that no hardware problems resulted from the addition or replacement of hardware components on your system by entering the following command: sldiag device status [-dev devtype] [-name device] -long -state failed System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of failures resulting from testing the component. 12. Proceed based on the result of the preceding step.
72
Then... 1. Clear the status logs by entering the following command: sldiag device clearstatus 2. Verify that the log is cleared by entering the following command: sldiag device status The following default response is displayed:
SLDIAG: No log messages are present.
3. Exit Maintenance mode by entering the following command: halt 4. Enter the following command at the firmware prompt to reboot the storage system: boot 5. If your system is in an HA pair , run the cf giveback command from the partner node console. You have completed system-level diagnostics. Resulted in some test failures Determine the cause of the problem. 1. Exit Maintenance mode by entering the following command: halt 2. Perform a clean shutdown and disconnect the power supplies. 3. Verify that you have observed all the considerations identified for running system-level diagnostics, that cables are securely connected, and that hardware components are properly installed in the storage system. 4. Reconnect the power supplies and power on the storage system. 5. Rerun the system-level diagnostics tests.
Disposing of batteries
Dispose of batteries according to local regulations regarding battery recycling or disposal.
73
Procedure
1. Check the status of the target node (the node you want to perform maintenance on) by entering the cf status command at the system console of either node. 2. Take one of the following actions, depending on the result of the cf status command:
If... Neither node is in takeover mode The partner node took over the target node Then... Go to the next step in this procedure. The target node is in a state where you can begin removing it from the system chassis. Continue with "Opening the System." The target node took over the partner node 1. Correct the problem that caused the takeover. 2. Run the cf giveback command from the target node console. 3. Go back to the beginning of this procedure.
3. Take over the target node by entering the cf takeover command from the partner node's console. 4. Continue with "Opening the System."
74
Procedure
1. Enter the halt command from the system console. Attention: You must perform a clean system shutdown before replacing system components to avoid losing unwritten data in the nonvolatile memory (NVMEM). The NVMEM LED is located on the controller module to the right of the network ports, marked with a battery symbol. If the NVMEM LED is flashing, there is content in the NVMEM that has not been saved to disk. You need to reboot the controller module and proceed from the beginning of this procedure. 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.
c0a
0c
e0a
0a LNK
0b LNK
!
c0b 0d e0b
1
Figure 32. NVMEM LED
NVMEM LED
2. If you are not already grounded, properly ground yourself. 3. Turn off the power supplies, unplug the power cords from the power source, and remove the power cords.
Procedure
1. If you are not already grounded, properly ground yourself. 2. Unplug the system cables from the controller module, as needed, and keep track of where the cables were connected. Leave the cables in the cable management arm so that when you reinstall the cable management arm in the controller module, the cables will be organized. 3. Disconnect the right and left cable management arms from the controller module. To release the arms, press the silver button on the power supply side of each arm, and then remove the arm from the controller module. 4. Loosen the thumbscrew on the cam handle. 5. Pull the cam handle downward and slide the controller module out of the system.
Chapter 4. Replacing N6200 series system devices
75
Procedure
1. Locate the RTC battery on the right side of the controller module as you slide the controller module out of the chassis. It is the battery in the vertical holder near the boot device holder.
1
Figure 33. Removing the RTC battery
2. Grasp the battery with your thumb and forefinger, gently tip the battery toward the center of the controller module, and then gently lift the battery out of the holder and set it aside. Note: Note the polarity of the battery as you remove it from the holder.
76
Procedure
1. If you are not already grounded, properly ground yourself. 2. Remove the replacement battery from the antistatic shipping bag. 3. Locate the empty battery holder in the controller module and insert the battery into the holder. 4. Visually inspect the battery to make sure that it is completely installed into the holder and that the polarity is correct. There is a large + on the motherboard indicating battery polarity.
Procedure
1. Align the end of the controller module with the opening in the chassis, if necessary, and then gently push the controller module halfway into the system. 2. Reinstall the cable management arms and recable the controller module, as needed. When recabling, remember to reinstall the media converters (SFPs) if you are using fiber cables. 3. Reinstall the controller module: a. Push the controller module all the way into the system. b. Push the cam handle to finish seating the controller module. c. Close the cam and tighten the thumbscrew on the cam handle. d. Halt the boot process: v For systems in an HA pair, press Ctrl-c to stop the boot process. v For stand-alone systems, reconnect the power cables to the power supplies and to the power sources, and then turn on the power. Press Ctrl-c to stop the boot process. The boot process is halted at either the Boot menu or the Loader prompt.
Procedure
1. Complete the applicable step, depending on where the node halted during the boot process: v If the node halted at the Loader prompt, continue with the next step in this procedure. v If the node halted at the Boot menu, then perform the following steps to reach the Loader prompt before continuing with this procedure. a. Select the Maintenance mode option from the displayed menu. b. Enter the following command at the prompt: halt
Chapter 4. Replacing N6200 series system devices
77
2.
c. Continue with the next step in this procedure. Enter the following command at the Loader prompt: boot_diags
Note: You must run this command from the Loader prompt for sldiag to function properly. The boot_diags command starts special drivers designed specifically for sldiag. The Maintenance mode prompt (*>) appears. 3. Enter the following command at the Maintenance mode prompt: sldiag For details about the sldiag command, see the sldiag man page. 4. Clear the status logs by entering the following command: sldiag device clearstatus 5. Verify that the log is cleared by entering the following command: sldiag device status The following default response is displayed:
SLDIAG: No log messages are present.
6. Run the sensor-related environmental tests for the RTC battery by entering the following command from the Maintenance mode prompt: sldiag device run -dev env Note: See the IBM System Storage N series System-Level Diagnostics Guide for a description of the types of tests you can run. 7. View the status of the test by entering the following command: sldiag device status Your storage system provides the following output while the tests are still running:
There are still test(s) being processed.
After all the tests are complete, the following response appears by default:
*> <SLDIAG:_ALL_TESTS_COMPLETED>
8. Verify that no hardware problems resulted from the addition or replacement of hardware components on your system by entering the following command: sldiag device status [-dev devtype] [-name device] -long -state failed System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of failures resulting from testing the component. 9. Proceed based on the result of the preceding step.
78
Then... 1. Clear the status logs by entering the following command: sldiag device clearstatus 2. Verify that the log is cleared by entering the following command: sldiag device status The following default response is displayed:
SLDIAG: No log messages are present.
3. Exit Maintenance mode by entering the following command: halt 4. Enter the following command at the firmware prompt to reboot the storage system: boot 5. If your system is in an HA pair , run the cf giveback command from the partner node console. You have completed system-level diagnostics. Resulted in some test failures Determine the cause of the problem. 1. Exit Maintenance mode by entering the following command: halt 2. Perform a clean shutdown and disconnect the power supplies. 3. Verify that you have observed all the considerations identified for running system-level diagnostics, that cables are securely connected, and that hardware components are properly installed in the storage system. 4. Reconnect the power supplies and power on the storage system. 5. Rerun the system-level diagnostics tests.
Procedure
1. Display the current date on the node or nodes by entering the date command. Note: If your system is in an HA pair, make sure that you display the date and time on the partner node and set the target node to those values. 2. Set the date by entering the following command: date [-u] [[[CC]yy]mmddhhmm>[.<ss>]]
Chapter 4. Replacing N6200 series system devices
79
-u sets the date and time to Greenwich Mean Time instead of the local time. 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 the month is omitted, the default is the current month. dd is the current day. If the day is omitted, 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 the seconds are omitted, the default is 0. Note: For more information, see the Data ONTAP 7-Mode System Administration Guide. This guide, as well as other Data ONTAP documentation, is available on the IBM N series support website, which is accessed and navigated as described in Using the IBM N series support website on page 26.. The following command sets the date and time to 22 May 2009 at 9:25 a.m. on a 7-Mode system: date 200905220925
Disposing of batteries
Dispose of batteries according to local regulations regarding battery recycling or disposal.
80
Table 14. 220V, single phase recommended conductor sizes 220V, single-phase 25 feet 50 feet 75 feet 20A circuit 14 AWG 12 AWG 10 AWG 30A circuit 12 AWG 10 AWG 8 AWG 40A circuit 12 AWG 8 AWG 6 AWG 50A circuit 10 AWG 8 AWG 6 AWG
The following table list the approximate equivalent wire gauge (American Wire Gauge (AWG) to Harmonized Cordage).
Table 15. American Wire Gage to Harmonized Cordage equivalents AWG Harmonized, mm-mm
1
8 4.0
10 2.5
12 1.5
81
82
83
v Attached plug EL 206 (AS 3112) designed for 200-240 V ac input. FC 9006 Switzerland, Liechtenstein Provides power cords for Switzerland, Liechtenstein v 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 Argentina Provides power cords for Argentina v 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 China Provides power cords for China v 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 Denmark Provides power cords for Denmark v 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 Africa Provides power cords for India, Macau, Pakistan, South Africa v 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 Israel Provides 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 Italy Provides power cords for Italy v 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 Brazil Provides power cords for Brazil v 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 Taiwan Provides 125 V power cords for Taiwan v 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 Taiwan v 1.83 m (6 feet), unshielded, rated 250 V/10 A.
84
v Attached plug EL 610 (CNS 10917, CNS 690) designed for 250 V ac input.
85
86
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe on any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, N.Y. 10504-1785 U.S.A. For additional information, visit the web at: www.ibm.com/ibm/licensing/contact/ The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer 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 will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level
Copyright IBM Corp. 2011
87
systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. If you are viewing this information in softcopy, the photographs and color illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. A complete and current list of other IBM trademarks is available on the web at http://www.ibm.com/legal/copytrade.shtml NetApp, the Network Appliance logo, the bolt design, NetAppthe Network Appliance Company, Data ONTAP, DataFabric, FAServer, FilerView, MultiStore, NearStore, NetCache, SecureShare, SnapManager, SnapMirror, SnapMover, SnapRestore, SnapVault, SyncMirror, and WAFL are registered trademarks of Network Appliance, Inc. in the United States, and/or other countries. gFiler, Network Appliance, SnapCopy, Snapshot, and The Evolution of Storage are trademarks of Network Appliance, Inc. in the United States and/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, 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 the United States and other countries. NetApp Availability Assurance and NetApp ProTech Expert are service marks of Network Appliance, Inc. in the United States. Spinnaker Networks, the Spinnaker Networks logo, SpinAccess, SpinCluster, SpinFS, SpinHA, SpinMove, and SpinServer are registered trademarks of Spinnaker Networks, LLC in the United States and/or other countries. SpinAV, SpinManager, SpinMirror, SpinRestore, SpinShot, and SpinStor are trademarks of Spinnaker Networks, LLC in the United States and/or other countries. Network Appliance is a licensee of the CompactFlash and CF Logo trademarks. Network Appliance NetCache is certified RealSystem compatible. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries.
88
Other company, product, or service names may be trademarks or service marks of others.
Important notes
Processor speeds indicate the internal clock speed of the microprocessor; other factors also affect application performance. CD-ROM drive speeds list the variable read rate. Actual speeds vary and are often less than the maximum possible. When referring to processor storage, real and virtual storage, or channel volume, KB stands for approximately 1000 bytes, MB stands for approximately 1 000 000 bytes, and GB stands for approximately 1 000 000 000 bytes. When referring to hard disk drive capacity or communications volume, MB stands for 1 000 000 bytes, and GB stands for 1 000 000 000 bytes. Total user-accessible capacity may vary depending on operating environments. Maximum internal hard disk drive capacities assume the replacement of any standard hard disk drives and population of all hard disk drive bays with the largest currently supported drives available from IBM. Maximum memory may require replacement of the standard memory with an optional memory module. IBM makes no representation or warranties regarding non-IBM products and services that are ServerProven, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. These products are offered and warranted solely by third parties. IBM makes no representations or warranties with respect to non-IBM products. Support (if any) for the non-IBM products is provided by the third party, not IBM. Some software may differ from its retail version (if available), and may not include 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 for the relevant source code portions of the Service Processor (SP) Firmware that are covered by the GPL, is available from ftp://ftp.netapp.com/frm-ntap/opensource/.
89
Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense. Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits. IBM is not responsible for any radio or television interference caused by using other than recommended cables and connectors or by unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could void the user's authority to operate the equipment. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
90
Um dieses sicherzustellen, sind die Gerte wie in den Handbchern beschrieben zu installieren und zu betreiben. Des Weiteren drfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM bernimmt keine Verantwortung fr die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der IBM verndert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne Empfehlung der IBM gesteckt/eingebaut werden. EN 55022 Klasse A Gerte mssen mit folgendem Warnhinweis versehen werden: "Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im Wohnbereich Funk-Strungen verursachen; in diesem Fall kann vom Betreiber verlangt werden, angemessene Manahmen zu ergreifen und dafr aufzukommen." Deutschland: Einhaltung des Gesetzes ber die elektromagnetische Vertrglichkeit von Gerten Dieses Produkt entspricht dem "Gesetz ber die elektromagnetische Vertrglichkeit von Gerten (EMVG)". Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in der Bundesrepublik Deutschland. Zulassungsbescheinigung laut dem Deutschen Gesetz ber die elektromagnetische Vertrglichkeit von Gerten (EMVG) (bzw. der EMC EG Richtlinie 2004/108/EG) fr Gerte der Klasse A Dieses Gert ist berechtigt, in bereinstimmung mit dem Deutschen EMVG das EG-Konformittszeichen - CE - zu fhren. Verantwortlich fr die Einhaltung der EMV Vorschriften ist der Hersteller: International Business Machines Corp. New Orchard Road Armonk, New York 10504 Tel: 919-499-1900 Der verantwortliche Ansprechpartner des Herstellers in der EU ist: IBM Deutschland GmbH Technical Regulations, Abteilung M456 IBM-Allee 1, 71139 Ehningen, Germany Generelle Informationen: Das Gert erfllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse A.
Notices
91
Translation: This is a Class A product based on the standard of the VCCI Council. If this equipment is used in a domestic environment, radio interference may occur, in which case, the user may be required to take corrective actions.
jjieta1
92
rusemi
Power cords
For your safety, IBM provides a power cord with a grounded attachment plug to use with this IBM product. To avoid electrical shock, always use the power cord and plug with a properly grounded outlet. IBM power cords used in the United States and Canada are listed by Underwriter's Laboratories (UL) and certified by the Canadian Standards Association (CSA). For units intended to be operated at 115 volts: Use a UL-listed and CSA-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 and CSA-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 cord set with a grounding-type attachment plug. The cord set should have the appropriate safety approvals for the country in which the equipment will be installed. IBM power cords for a specific country or region are usually available only in that country or region.
Notices
93
94
Index A
about this document xix how to send your comments xxv AC power line sizes 81 AC power supplies, connecting N6200 series system to 13 active/active or high availability configuration tasks 21 adapters cabling 17 ASCII terminal console connection 20 attention notice definition v example v dual-path Fibre Channel cabling 17
E
electrical requirements N6210 6, 7 N6240 7 N6270 8 environmental requirements
F
fan module installing 27 removing a 26 fiber-optic cable handling 13 Fibre Channel expansion adapters cabling 17 Fibre Channel port configuring 21 filer, defined xxii fire suppression ix FRU/CRU list feature codes 83
B
boot device removing 55, 61 replacing in a 32xx system running Data ONTAP 7.3.5 and later releases in the Data ONTAP 7.3 release family 54 booting your system 21
C
caution notices v definition v clearance dimensions 5 comments sending xxv configuration worksheet 21 configuring for an active/active or high availability configuration 21 configuring the Fibre Channel port 21 connections ASCII terminal console 20 filer to storage expansion unit 16 gateway to external storage 19 N6200 series system 13 storage 15 third-party devices 19 to a power source 13 to an IP network 14 using a Fibre Channel expansion adapter 17 using an optional adapter card 17 controller module reinstalling 45, 51, 77 conventions command xxiii formatting xxiii keyboard xxiv
G
gateway connecting to external storage gateway, defined xxii 19
H
HA configuration shutdown a node 68 handling static-sensitive devices 4 hardware service and support xxi hardware specifications 5 high availability configuration tasks how to send your comments xxv
21
I
I/O expansion module installing 68 replacing 68 initiator mode 21 installation preparation for 1 procedures for 10 rack vii rules 9 tools 3 installing a fan module 27 a PCIe card 50 RTC battery 77 the I/O expansion module
D
danger notices iii definition iii example iii DIMM running SLDiag 45 documentation improvement xxv Copyright IBM Corp. 2011
68
95
Installing I/O expansion module installing 70 the I/O expansion module 70 the NVMEM battery 37 the NVRAM battery 37 intellectual property 87 IP network 14
R
rack installation vii safety vii rack relocation safety ix rack safety vii reader feedback sending xxv reinstalling 38 controller module 45, 51, 77 removing a fan module 26 NVMEM battery 32 PCIe cards 49 the boot device 55, 61 Removing I/O expansion module removing 69 the I/O expansion module 69 replacement N6200 series system devices 23 replacing a fan module 26 PIC cards 47 riser cards 47 the I/O expansion module 68 replacing a boot device in a 32xx system running Data ONTAP 7.3.5 and later releases in the Data ONTAP 7.3 release family 54 restrictions, usage vi riser cards installing or replacing 47 RTC battery removing 76
L
labels, safety v laser safety vi license, patents 87 licensing address 87 Web address 87
N
netboot in 7-Mode on Data ONTAP 8.0; disruptive 62 in 7-Mode on Data ONTAP 8.0; non-disruptive 65 in a 32xx system running Data ONTAP 7.3.5 or later in the 7.3 family; disruptive 56 node shutdown in an HA configuration 68 notes, important 89 notices attention v caution v danger iii safety iii types iii NVMEM checking the status 38 installing the battery 37 NVRAM checking the status 38 installing the battery 37
S
safety labels iii laser vi notices iii rack vii rack installation vii rack relocation ix safety labels v Service Processor (SP) configuring and using 22 shipment package contents 8 shutting down a node in 7-Mode 60 a node running Data ONTAP 7.3.5 or laterin the 7.3 release family 54 SLDiag running for DIMMs 45 static-sensitive devices, handling 4
O
optical port terminators optional adapter cards cabling 17 vi
P
patents 87 PCI cards installing or replacing 47 PCIe card installing 50 PCIe cards removing 49 physical characteristics 5 power separate circuit breakers for power cords 93 feature codes 83 power line sizes 81 power supplies 13
T
13 terminators optical ports vi terminology xxii the controller module with normal boot third-party devices rules for connecting 19 trademarks 88 38
96
U
usage restrictions vi
W
websites, related xx
Index
97
98
Printed in USA
GA32-0838-01