NetApp FAS Manual

page of 704

/ 704
Bookmarks

Quick Links

FAS systems

ONTAP Systems

NetApp

April 04, 2022

This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/fas500f/install-setup.html on

April 04, 2022. Always check docs.netapp.com for the latest.

Need help?

Do you have a question about the FAS and is the answer not in the manual?

Questions and answers

Summary of Contents for NetApp FAS

Page 1 FAS systems ONTAP Systems NetApp April 04, 2022 This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/fas500f/install-setup.html on April 04, 2022. Always check docs.netapp.com for the latest.
Page 2: Table Of Contents
Table of Contents FAS systems ................
Page 3: Fas Systems
FAS systems FAS500f System Documentation Install and setup Start here: Choose your installation and setup experience For most configurations, you can choose from different content formats. • Quick steps A printable PDF of step-by-step instructions with live links to additional content.
Page 4 Video two of two: Performing end-to-end software configuration The following video shows end-to-end software configuration for systems running ONTAP 9.2 and later. NetApp video: Software configuration for vSphere NAS datastores for FAS/AFF systems running ONTAP 9.2 Detailed steps - FAS500f This section gives detailed step-by-step instructions for installing a FAS500f system.
Page 5 ONTAP Configuration Guide and collect the required information listed in that guide. Step 2: Install the hardware You need to install your system in a 4-post rack or NetApp system cabinet, as applicable. Steps 1. Install the rail kits, as needed.
Page 6 You need to be aware of the safety concerns associated with the weight of the system. 3. Identify and manage cables because this system does not have a cable management device. 4. Place the bezel on the front of the system. Step 3: Cable controllers There is required cabling for your platform’s cluster using the two-node switchless cluster method or the cluster interconnect network method.
Page 7 Step Perform on each controller Cable the cluster interconnect ports to each other with the 25GbE cluster interconnect cable • e0c to e0c • e0d to e0d Cable the wrench ports to the management network switches with the RJ45 cables. DO NOT plug in the power cords at this point.
Page 8 As you insert the connector, you should feel it click into place; if you do not feel it click, remove it, turn it around and try again. Steps 1. Use the animation (Cabling a switched cluster) or the step-by-step instructions to complete the cabling between the controllers and to the switches: Step Perform on each controller...
Page 9 Before you begin Contact your network administrator for information about connecting the system to the switches. Be sure to check the illustration arrow for the proper cable connector pull-tab orientation. As you insert the connector, you should feel it click into place; if you do not feel it click, remove it, turn it around and try again.
Page 10 As you insert the connector, you should feel it click into place; if you do not feel it click, remove it, turn it around and try again. Step Perform on each controller module Cable ports e4a through e4d to the 10GbE host network switches. To perform other optional cabling, choose from: •...
Page 11 1. Use the animation (Cabling the controllers to a single NS224) or the step-by-step instructions to cable your controller modules to a single shelf. Step Perform on each controller module Cable controller A to the shelf: Cable controller B to the shelf: 2.
Page 12 Steps 1. Plug the power cords into the controller power supplies, and then connect them to power sources on different circuits. 2. Make sure that your laptop has network discovery enabled. See your laptop’s online help for more information. 3. Use the animation (Connecting your laptop to the Management switch) to connect your laptop to the Management switch.
Page 13 a. Set the console port on the laptop or console to 115,200 baud with N-8-1. See your laptop or console’s online help for how to configure the console port. b. Connect the laptop or console to the switch on the management subnet. c.
Page 14 If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller; see the NetApp Encryption overview with the CLI. Steps 1.
Page 15 Check NVE or NSE on systems running ONTAP 9.6 and later Before shutting down the impaired controller, you need to verify whether the system has either NetApp Volume Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.
Page 16 Restored yes: a. Restore the external key management authentication keys to all nodes in the cluster: security key-manager external restore If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column equals for all authentication keys: Restored...
Page 17 Key Manager external Restored yes: a. Enter the onboard security key-manager sync command: security key-manager external sync If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the Restored column equals for all authentication keys: security key- manager key-query c.
Page 18 g. Return to admin mode: set -priv admin h. You can safely shut down the controller. Shut down the controller - FAS500f After completing the NVE or NSE tasks, you need to complete the shutdown of the impaired controller. Shut down or take over the impaired controller using the appropriate procedure for your configuration.
Page 19 1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message: system node autosupport invoke -node * -type all -message MAINT=number_of_hours_downh The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*> system node autosupport invoke -node * -type all -message MAINT=2h 2.
Page 20 Lever Latching mechanism 5. Using both hands, grasp the controller module sides and gently pull it out of the chassis and set it on a flat, stable surface. 6. Turn the thumbscrew on the front of the controller module anti-clockwise and open the controller module cover.
Page 21 Thumbscrew Controller module cover. 7. Lift out the air duct cover. Step 2: Replace the boot media You locate the failed boot media in the controller module by removing the air duct on the controller module before you can replace the boot media. You need a #1 magnetic Phillips head screwdriver to remove the screw that holds the boot media in place.
Page 22 • A copy of the same image version of ONTAP as what the impaired controller was running. You can download the appropriate image from the Downloads section on the NetApp Support Site ◦ If NVE is enabled, download the image with NetApp Volume Encryption, as indicated in the download...
Page 23 Steps 1. Download and copy the appropriate service image from the NetApp Support Site to the USB flash drive. 2. Download the service image to your work space on your laptop. 3. Unzip the service image.
Page 24 7. Close the controller module cover and tighten the thumbscrew.
Page 25 Controller module cover Thumbscrew 8. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system. 9. Plug the power cable into the power supply and reinstall the power cable retainer. 10.
Page 26 If your system has… Then… A network connection a. Press when prompted to restore the backup configuration. b. Set the healthy controller to advanced privilege level: -privilege advanced c. Run the restore backup command: system node restore- backup -node local -target-address impaired_node_IP_address d.
Page 27 If your system has… Then… No network connection and is in a a. Press when prompted to restore the backup configuration. MetroCluster IP configuration b. Reboot the system when prompted by the system. c. Wait for the iSCSI storage connections to connect. You can proceed after you see the following messages: date-and-time [node- name:iscsi.session.stateChanged:notice]:...
Page 28 Restore OKM, NSE, and NVE as needed - FAS500f Once environment variables are checked, you must complete steps specific to systems that have Onboard Key Manager (OKM), NetApp Storage Encryption (NSE) or NetApp Volume Encryption (NVE) enabled. 1. Determine which section you should use to restore your OKM, NSE, or NVE configurations: If NSE or NVE are enabled along with Onboard Key Manager you must restore settings you captured at the beginning of this procedure.
Page 29 If the console displays… Then… The LOADER prompt Boot the controller to the boot menu: boot_ontap menu Waiting for giveback…. a. Enter at the prompt Ctrl-C b. At the message: Do you wish to halt this node rather than wait [y/n]? , enter: c.
Page 30 9. Confirm the target controller is ready for giveback with the storage failover show command. 10. Giveback only the CFO aggregates with the storage failover giveback -fromnode local command. -only-cfo-aggregates true ◦ If the command fails because of a failed disk, physically disengage the failed disk, but leave the disk in the slot until a replacement is received.
Page 31 Restore NSE/NVE on systems running ONTAP 9.6 and later Steps 1. Connect the console cable to the target controller. 2. Use the command at the LOADER prompt to boot the controller. boot_ontap 3. Check the console output: If the console displays… Then…...
Page 32 -auto-giveback true Return the failed part to NetApp - FAS500f After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-...
Page 33 a healthy controller shows for eligibility and health, you must correct the issue before shutting down false the impaired controller; see the Administration overview with the CLI. • If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message: system node autosupport invoke -node * -type all -message MAINT=number_of_hours_downh The following AutoSupport message suppresses automatic case creation for two hours:...
Page 34 Move and replace hardware - FAS500f Move the power supplies, hard drives, and controller module or modules from the impaired chassis to the new chassis, and swap out the impaired chassis from the equipment rack or system cabinet with the new chassis of the same model as the impaired chassis.
Page 35 Step 2: Move drives to the new chassis You need to move the drives from each bay opening in the old chassis to the same bay opening in the new chassis. 1. Gently remove the bezel from the front of the system. 2.
Page 36 Complete the restoration and replacement process - FAS500f You must verify the HA state of the chassis, run diagnostics, and return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Step 1: Verify and set the HA state of the chassis You must verify the HA state of the chassis, and, if necessary, update the state to match your system configuration.
Page 37 ◦ If the test reported no failures, select Reboot from the menu to reboot the system. Step 3: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 38 • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the “Returning SEDs to unprotected mode” section of the ONTAP 9 NetApp Encryption Power Guide.
Page 39 The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*> system node autosupport invoke -node * -type all -message MAINT=2h 2. Disable automatic giveback from the console of the healthy controller: storage failover modify –node local -auto-giveback false 3.
Page 40 If the impaired controller is Then… displaying… The LOADER prompt Go to Remove controller module. Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name...
Page 41 Lever Latching mechanism 5. Using both hands, grasp the controller module sides and gently pull it out of the chassis and set it on a flat, stable surface. 6. Turn the thumbscrew on the front of the controller module anti-clockwise and open the controller module cover.
Page 42 Thumbscrew Controller module cover. 7. Lift out the air duct cover. Step 2: Move the power supply You must move the power supply from the impaired controller module to the replacement controller module when you replace a controller module. 1. Disconnect the power supply. 2.
Page 43 Blue power supply locking tab Power supply 5. Move the power supply to the new controller module, and then install it. 6. Using both hands, support and align the edges of the power supply with the opening in the controller module, and then gently push the power supply into the controller module until the locking tab clicks into place.
Page 44 Fan module 2. Move the fan module to the replacement controller module, and align the edges of the fan module with the opening in the controller module, and then slide the fan module in. 3. Repeat these steps for the remaining fan modules. Step 4: Move the boot media There is one boot media device in the AFF A250 under the air duct in the controller module.
Page 45 Remove the screw securing the boot media to the motherboard in the impaired controller module. Lift the boot media out of the impaired controller module. a. Using the #1 magnetic screwdriver, remove the screw from the boot media, and set it aside safely on the magnet.
Page 46 1. Slowly push apart the DIMM ejector tabs on either side of the DIMM, and slide the DIMM out of the slot. Hold the DIMM by the edges to avoid pressure on the components on the DIMM circuit board. 2. Locate the corresponding DIMM slot on the replacement controller module. 3.
Page 47 Loosen the screw in the controller module. Move the mezzanine card. 2. Unplug any cabling associated with the mezzanine card. Make sure that you label the cables so that you know where they came from. a. Remove any SFP or QSFP modules that might be in the mezzanine card and set it aside. b.
Page 48 Squeeze the clip on the face of the battery plug. Unplug the battery cable from the socket. Grasp the battery and press the blue locking tab marked PUSH. Lift the battery out of the holder and controller module. 2. Locate the battery plug and squeeze the clip on the face of the battery plug to release the plug from the socket.
Page 49 Step 8: Install the controller module After all of the components have been moved from the impaired controller module to the replacement controller module, you must install the replacement controller module into the chassis, and then boot it to Maintenance mode. You can use the following illustration or the written steps to install the replacement controller module in the chassis.
Page 50 Controller module cover Thumbscrew 3. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system. Do not completely insert the controller module in the chassis until instructed to do so. 4.
Page 51 mechanisms snap into place. The controller module begins to boot as soon as it is fully seated in the chassis. Be prepared to interrupt the boot process. The controller module should be fully inserted and flush with the edges of the chassis. Restore and verify the system configuration - FAS500f After completing the hardware replacement and booting to Maintenance mode, you verify the low-level system configuration of the replacement controller and reconfigure system...
Page 52 The HA state should be the same for all components. 2. If the displayed system state of the controller module does not match your system configuration, set the state for the controller module: ha-config modify controller ha-state The value for HA-state can be one of the following: ◦...
Page 53 Step 1: Recable the system After running diagnostics, you must recable the controller module’s storage and network connections. Steps 1. Recable the system. 2. Verify that the cabling is correct by using Active IQ Config Advisor. a. Download and install Config Advisor. b.
Page 54 You can respond when prompted to continue into advanced mode. The advanced mode prompt appears (*>). b. Save any coredumps: system node run -node local-node-name partner savecore c. Wait for the `savecore`command to complete before issuing the giveback. You can enter the following command to monitor the progress of the savecore command: system node run -node local-node-name partner savecore -s d.
Page 55 -node replacement-node-name -onreboot true Complete system restoration - FAS500f To restore your system to full operation, you must restore the NetApp Storage Encryption configuration (if necessary), and install licenses for the new controller, and return the failed part to NetApp, as described in the RMA instructions shipped with the kit.
Page 56 Steps 1. If you need new license keys, obtain replacement license keys on the NetApp Support Site in the My Support section under Software licenses. The new license keys that you require are automatically generated and sent to the email address on file.
Page 57 -node local -auto -giveback true Step 4: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp...
Page 58 If the impaired controller is Then… displaying… The LOADER prompt Go to Remove controller module. Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name...
Page 59 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 60 6. Turn the thumbscrew on the front of the controller module anti-clockwise and open the controller module cover. Thumbscrew Controller module cover. 7. Lift out the air duct cover.
Page 61 Step 3: Replace a DIMM To replace a DIMM, you must locate it in the controller module using the DIMM map label on top of the air duct or locating it using the LED next to the DIMM, and then replace it following the specific sequence of steps. You can use the following video or the tabulated steps to replace a DIMM: Replacing a DIMM 1.
Page 62 2. Note the orientation of the DIMM in the socket so that you can insert the replacement DIMM in the proper orientation. 3. Slowly push apart the DIMM ejector tabs on either side of the DIMM, and slide the DIMM out of the slot. 4.
Page 63 2. Close the controller module cover and tighten the thumbscrew.
Page 64 Controller module cover Thumbscrew 3. Insert the controller module into the chassis: a. Ensure the latching mechanism arms are locked in the fully extended position. b. Using both hands, align and gently slide the controller module into the latching mechanism arms until it stops.
Page 65 Step 6: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800-44- 638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 66 Option 1: Replace SSD 1. If you want to manually assign drive ownership for the replacement drive, you need to disable automatic drive assignment replacement drive, if it is enabled You manually assign drive ownership and then reenable automatic drive assignment later in this procedure.
Page 67 -node node_name -autoassign on You must reenable automatic drive assignment on both controller modules. 10. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp...
Page 68 Depending on the storage system, the disk drives have the release button located at the top or on the left of the disk drive face. For example, the following illustration shows a disk drive with the release button located on the top of the disk drive face: The cam handle on the disk drive springs open partially and the disk drive releases from the midplane.
Page 69 13. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 70 Option 2: Controller is in a MetroCluster Do not use this procedure if your system is in a two-node MetroCluster configuration. To shut down the impaired controller, you must determine the status of the controller and, if necessary, take over the controller so that the healthy controller continues to serve data from the impaired controller storage. •...
Page 71 with your thumb, and gently pull the controller a few inches out of the chassis. If you have difficulty removing the controller module, place your index fingers through the finger holes from the inside (by crossing your arms). Lever Latching mechanism 5.
Page 72 Thumbscrew Controller module cover Step 3: Replace a fan To replace a fan, remove the failed fan module and replace it with a new fan module. You can use the following video or the tabulated steps to replace a fan: Replacing a fan 1.
Page 73 Fan module 3. Align the edges of the replacement fan module with the opening in the controller module, and then slide the replacement fan module into the controller module. Step 4: Reinstall the controller module After you replace a component within the controller module, you must reinstall the controller module in the system chassis and boot it.
Page 74 Controller module cover Thumbscrew 2. Insert the controller module into the chassis: a. Ensure the latching mechanism arms are locked in the fully extended position. b. Using both hands, align and gently slide the controller module into the latching mechanism arms until it stops.
Page 75 -node local -auto -giveback true Step 5: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp...
Page 76 If the impaired controller is Then… displaying… Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 77 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 78 6. Turn the thumbscrew on the front of the controller module anti-clockwise and open the controller module cover. Thumbscrew Controller module cover. Step 3: Replace or install a mezzanine card To replace a mezzanine card, you must remove the impaired card and install the replacement card; to install a mezzanine card, you must remove the faceplate and install the new card.
Page 79 Remove screws on the face of the controller module. Loosen the screw in the controller module. Remove the mezzanine card. 2. Unplug any cabling associated with the impaired mezzanine card. Make sure that you label the cables so that you know where they came from. 3.
Page 80 Do not apply force when tightening the screw on the mezzanine card; you might crack it. 10. Insert any SFP or QSFP modules that were removed from the impaired mezzanine card to the replacement mezzanine card. Option 2: Install a mezzanine card: You install a new mezzanine card if your system does not have one.
Page 81 -node local -auto -giveback true Step 5: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp...
Page 82 About this task If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller;...
Page 83 The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*> system node autosupport invoke -node * -type all -message MAINT=2h 2. Disable automatic giveback from the console of the healthy controller: storage failover modify –node local -auto-giveback false 3.
Page 84 Lever Latching mechanism 5. Using both hands, grasp the controller module sides and gently pull it out of the chassis and set it on a flat, stable surface. 6. Turn the thumbscrew on the front of the controller module anti-clockwise and open the controller module cover.
Page 85 Thumbscrew Controller module cover. Step 3: Replace the NVMEM battery To replace the NVMEM battery, you must remove the failed battery from the controller module and install the replacement battery into the controller module. You can use the following video or the tabulated steps to replace the NVMEM battery: Replacing the NVMEM battery 1.
Page 86 Grasp the battery and press the blue locking tab marked PUSH. Lift the battery out of the holder and controller module. 2. Locate the battery plug and squeeze the clip on the face of the battery plug to release the plug from the socket.
Page 87 Controller module cover Thumbscrew 2. Insert the controller module into the chassis: a. Ensure the latching mechanism arms are locked in the fully extended position. b. Using both hands, align and gently slide the controller module into the latching mechanism arms until it stops.
Page 88 ◦ If the scan reported no failures, select Reboot from the menu to reboot the system. Step 6: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 89 1. If you are not already grounded, properly ground yourself. 2. Identify the power supply you want to replace, based on console error messages or through the red Fault LED on the power supply. 3. Disconnect the power supply: a. Open the power cable retainer, and then unplug the power cable from the power supply. b.
Page 90 Once power is restored to the power supply, the status LED should be green. 7. After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 91 If the impaired controller is Then… displaying… The LOADER prompt Go to Remove controller module. Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name...
Page 92 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 93 6. Turn the thumbscrew on the front of the controller module anti-clockwise and open the controller module cover. Thumbscrew Controller module cover. 7. Lift out the air duct cover.
Page 94 Step 3: Replace the RTC battery To replace the RTC battery, locate it inside the controller and follow the specific sequence of steps. You can use the following video or the tabulated steps to replace the RTC battery: Replacing the RTC battery 1.
Page 95 Gently pull tab away from the battery housing. NOTE: Pulling it away aggressively might displace the tab. Lift the battery up. Make a note of the polarity of the battery. The battery should eject out. The battery will be ejected out. 2.
Page 96 With positive polarity face up, slide the battery under the tab of the battery housing. Push the battery gently into place and make sure the tab secures it to the housing. CAUTION: Pushing it in aggressively might cause the battery to eject out again.
Page 97 -node local -auto -giveback true Step 5: Complete the replacement process After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp...
Page 98: Fas2600 System Documentation
FAS2600 System Documentation Install and setup Cluster configuration worksheet - FAS2600 You can use the worksheet to gather and record your site-specific IP addresses and other information required when configuring an ONTAP cluster. Cluster Configuration Worksheet Start here: Choose your installation and setup experience You can choose from different content formats to guide you through installing and setting up your new storage system.
Page 99 If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller; see the NetApp Encryption overview with the CLI. Steps 1.
Page 100 Option 1: Check NVE or NSE on systems running ONTAP 9.5 and earlier Before shutting down the impaired controller, you need to check whether the system has either NetApp Volume Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.
Page 101 Retrieve and restore all authentication keys and associated key IDs: security key-manager restore -address * If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column displays for all authentication keys and that all key managers...
Page 102 Option 2: Check NVE or NSE on systems running ONTAP 9.6 and later Before shutting down the impaired controller, you need to verify whether the system has either NetApp Volume Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.
Page 103 Restored yes: a. Restore the external key management authentication keys to all nodes in the cluster: security key-manager external restore If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column equals for all authentication keys: Restored...
Page 104 Enter the customer’s onboard key management passphrase at the prompt. If the passphrase cannot be provided, contact NetApp Support. mysupport.netapp.com b. Verify the column shows for all authentication keys: Restored security key-manager key-query c. Verify that the type shows onboard, and then manually back up the OKM Key Manager information.
Page 105 Restored column displays anything other than yes: a. Enter the onboard security key-manager sync command: security key-manager external sync If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column equals for all authentication keys: Restored security key- manager key-query c.
Page 106 If the impaired controller Then… displays… Press Ctrl-C, and then respond when prompted. Waiting for giveback… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 107 5. Turn the controller module over and place it on a flat, stable surface. 6. Open the cover by sliding in the blue tabs to release the cover, and then swing the cover up and open. Step 2: Replace the boot media 1.
Page 108 • A copy of the same image version of ONTAP as what the impaired controller was running. You can download the appropriate image from the Downloads section on the NetApp Support Site ◦ If NVE is enabled, download the image with NetApp Volume Encryption, as indicated in the download button.
Page 109 Steps 1. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system. 2. Reinstall the cable management device and recable the system, as needed. When recabling, remember to reinstall the media converters (SFPs) if they were removed. 3.
Page 110 Boot the recovery image - FAS2600 You must boot the ONTAP image from the USB drive, restore the file system, and verify the environmental variables. Steps 1. From the LOADER prompt, boot the recovery image from the USB flash drive: boot_recovery The image is downloaded from the USB flash drive.
Page 111 Restore OKM, NSE, and NVE as needed - FAS2600 Once environment variables are checked, you must complete steps specific to systems that have Onboard Key Manager (OKM), NetApp Storage Encryption (NSE) or NetApp Volume Encryption (NVE) enabled. Determine which section you should use to restore your OKM, NSE, or NVE configurations: If NSE or NVE are enabled along with Onboard Key Manager you must restore settings you captured at the beginning of this procedure.
Page 112 If the console Then… displays… The LOADER prompt Boot the controller to the boot menu: boot_ontap menu Waiting for giveback… a. Enter at the prompt Ctrl-C b. At the message: Do you wish to halt this controller rather than wait [y/n]? , enter: c.
Page 113 9. Confirm the target controller is ready for giveback with the storage failover show command. 10. Give back only the CFO aggregates with the storage failover giveback -fromnode local -only-cfo command. -aggregates true ◦ If the command fails because of a failed disk, physically disengage the failed disk, but leave the disk in the slot until a replacement is received.
Page 114 If giveback is not complete after 20 minutes, contact Customer Support. 18. At the clustershell prompt, enter the command to list the logical net int show -is-home false interfaces that are not on their home controller and port. If any interfaces are listed as false, revert those interfaces back to their home port using the net int command.
Page 115 This command does not work if NVE (NetApp Volume Encryption) is configured 10. Use the security key-manager query to display the key IDs of the authentication keys that are stored on the key management servers.
Page 116 If the console Then… displays… The login prompt Go to Step 7. Waiting for giveback… a. Log into the partner controller. b. Confirm the target controller is ready for giveback with the storage command. failover show 4. Move the console cable to the partner controller and give back the target controller storage using the storage failover giveback -fromnode local -only-cfo-aggregates true local command.
Page 117 -auto-giveback true Return the failed part to NetApp - FAS2600 After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-...
Page 118 The output should display the caching module status as erased. 2. If the impaired controller is part of an HA pair, disable automatic giveback from the console of the healthy controller: storage failover modify -node local -auto-giveback false 3. Take the impaired controller to the LOADER prompt: If the impaired controller is Then…...
Page 119 4. Squeeze the latch on the cam handle until it releases, open the cam handle fully to release the controller module from the midplane, and then, using two hands, pull the controller module out of the chassis. 5. Turn the controller module over and place it on a flat, stable surface. 6.
Page 120 Step 3: Replace a caching module To replace a caching module referred to as the M.2 PCIe card on the label on your controller, locate the slot inside the controller and follow the specific sequence of steps. Your storage system must meet certain criteria depending on your situation: •...
Page 121 4. Reseat and push the heatsink down to engage the locking button on the caching module housing. 5. Close the controller module cover, as needed. Step 4: Reinstall the controller module After you replace components in the controller module, reinstall it into the chassis. 1.
Page 122 If your system is in… Then perform these steps… An HA pair The controller module begins to boot as soon as it is fully seated in the chassis. Be prepared to interrupt the boot process. a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position.
Page 123 If your system is in… Then perform these steps… A stand-alone configuration a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position. Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.
Page 124 3. Run diagnostics on the caching module: sldiag device run -dev fcache 4. Verify that no hardware problems resulted from the replacement of the caching module: sldiag device status -dev fcache -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.
Page 125 Rerun the system-level diagnostic test. Step 6: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 126 • This procedure is written with the assumption that you are moving all drives and controller module or modules to the new chassis, and that the chassis is a new component from NetApp. • This procedure is disruptive. For a two-node cluster, you will have a complete service outage and a partial outage in a multi-node cluster.
Page 127 Warning: This operation will cause controller "node-name" to be marked as unhealthy. Unhealthy nodes do not participate in quorum voting. If the controller goes out of service and one more controller goes out of service there will be a data serving failure for the entire cluster. This will cause a client disruption.
Page 128 5. Repeat the preceding steps for any remaining power supplies. 6. Using both hands, support and align the edges of the power supply with the opening in the system chassis, and then gently push the power supply into the chassis using the cam handle. The power supplies are keyed and can only be installed one way.
Page 129 4. Set the controller module aside in a safe place, and repeat these steps if you have another controller module in the chassis. Step 3: Move drives to the new chassis Move the drives from each bay opening in the old chassis to the same bay opening in the new chassis. 1.
Page 130 Step 4: Replace a chassis from within the equipment rack or system cabinet Remove the existing chassis from the equipment rack or system cabinet before you can install the replacement chassis. 1. Remove the screws from the chassis mount points. 2.
Page 131 From the boot menu, select the option for Maintenance mode. Restore and verify the configuration - FAS2600 You must verify the HA state of the chassis, run diagnostics, and return the failed part to NetApp, as described in the RMA instructions shipped with the kit.
Page 132 Step 1: Verify and set the HA state of the chassis You must verify the HA state of the chassis, and, if necessary, update the state to match your system configuration. 1. In Maintenance mode, from either controller module, display the HA state of the local controller module and chassis: ha-config show The HA state should be the same for all components.
Page 133 Both controllers must be in Maintenance mode to run the interconnect test. 3. At the LOADER prompt, access the special drivers specifically designed for system-level diagnostics to function properly: boot_diags During the boot process, you can safely respond to the prompts until the Maintenance mode prompt (*>) appears.
Page 134 Rerun the system-level diagnostics test. Step 3: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 135 • You must replace the failed component with a replacement FRU component you received from your provider. • You must be replacing a controller module with a controller module of the same model type. You cannot upgrade your system by just replacing the controller module. •...
Page 136 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 137 6. Turn the controller module over and place it on a flat, stable surface. 7. Open the cover by sliding in the blue tabs to release the cover, and then swing the cover up and open. Step 2: Move the boot media You must locate the boot media and follow the directions to remove it from the old controller module and insert it in the new controller module.
Page 138 Steps 1. Locate the boot media using the following illustration or the FRU map on the controller module: 2. Press the blue button on the boot media housing to release the boot media from its housing, and then gently pull it straight out of the boot media socket. Do not twist or pull the boot media straight up, because this could damage the socket or the boot media.
Page 139 The NVRAM LED blinks while destaging contents to the flash memory when you halt the system. After the destage is complete, the LED turns off. ▪ If power is lost without a clean shutdown, the NVMEM LED flashes until the destage is complete, and then the LED turns off.
Page 140 Step 4: Move the DIMMs To move the DIMMs, you must follow the directions to locate and move them from the old controller module into the replacement controller module. You must have the new controller module ready so that you can move the DIMMs directly from the impaired controller module to the corresponding slots in the replacement controller module.
Page 141 Visually inspect the DIMM to verify that it is evenly aligned and fully inserted into the slot. 8. Repeat these steps for the remaining DIMMs. 9. Locate the NVMEM battery plug socket, and then squeeze the clip on the face of the battery cable plug to insert it into the socket.
Page 142 2. Gently pull the caching module straight out of the housing. 3. Move the caching module to the new controller module, and then align the edges of the caching module with the socket housing and gently push it into the socket. 4.
Page 143 If your system is in… Then perform these steps… An HA pair The controller module begins to boot as soon as it is fully seated in the chassis. Be prepared to interrupt the boot process. a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position.
Page 144 If your system is in… Then perform these steps… A stand-alone configuration a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position. Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.
Page 145 • The replacement node is the new node that replaced the impaired node as part of this procedure. • The healthy node is the HA partner of the replacement node. Steps 1. If the replacement node is not at the LOADER prompt, halt the system to the LOADER prompt. 2.
Page 146 After you issue the command, you should wait until the system stops at the LOADER prompt. 2. At the LOADER prompt, access the special drivers specifically designed for system-level diagnostics to function properly: boot_diags During the boot process, you can safely respond to the prompts until the Maintenance mode prompt (*>) appears.
Page 147 If you want to run diagnostic Then… tests on… Individual components a. Clear the status logs: sldiag device clearstatus b. Display the available tests for the selected devices: sldiag device show -dev dev_name dev_name can be any one of the ports and devices identified in the preceding step.
Page 148 If you want to run diagnostic Then… tests on… Multiple components at the same a. Review the enabled and disabled devices in the output from the time preceding procedure and determine which ones you want to run concurrently. b. List the individual tests for the device: sldiag device show -dev dev_name c.
Page 149 If the system-level diagnostics Then… tests… Were completed without any a. Clear the status logs: sldiag device clearstatus failures b. Verify that the log was cleared: sldiag device status The following default response is displayed: SLDIAG: No log messages are present. c.
Page 150 d. Check other cabling by clicking the appropriate tab, and then examining the output from Config Advisor. Step 2: Reassign disks If the storage system is in an HA pair, the system ID of the new controller module is automatically assigned to the disks when the giveback occurs at the end of the procedure.
Page 151 You can enter the following command to monitor the progress of the savecore command: system node run -node local-node-name partner savecore -s d. Return to the admin privilege level: set -privilege admin 5. Give back the controller: a. From the healthy controller, give back the replaced controller’s storage: storage failover giveback -ofnode replacement_node_name The replacement controller takes back its storage and completes booting.
Page 152 Option 2: Manually reassign the system ID on a stand-alone system in ONTAP In a stand-alone system, you must manually reassign disks to the new controller’s system ID before you return the system to normal operating condition. About this task This procedure applies only to systems that are in a stand-alone configuration.
Page 153 Complete system restoration - FAS2600 To restore your system to full operation, you must restore the NetApp Storage Encryption configuration (if necessary), and install licenses for the new controller, and return the failed part to NetApp, as described in the RMA instructions shipped with the kit.
Page 154 -node local -auto -giveback true Step 4: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp...
Page 155 system panic. All other components in the system must be functioning properly; if not, you must contact technical support. You must replace the failed component with a replacement FRU component you received from your provider. AFF FAS2600 DIMM replacement video Step 1: Shut down the impaired controller Shut down or take over the impaired controller using different procedures, depending on the storage system hardware configuration.
Page 156 Step 2: Remove controller module To access components inside the controller, you must first remove the controller module from the system and then remove the cover on the controller module. 1. If you are not already grounded, properly ground yourself. 2.
Page 157 Step 3: Replace the DIMMs To replace the DIMMs, locate them inside the controller and follow the specific sequence of steps. If you are replacing a DIMM, you need to remove it after you have unplugged the NVMEM battery from the controller module.
Page 158 b. Confirm that the NVMEM LED is no longer lit. c. Reconnect the battery connector. 4. Recheck the NVMEM LED. 5. Locate the DIMMs on your controller module. Each system memory DIMM has an LED located on the board next to each DIMM slot. The LED for the faulty blinks every two seconds.
Page 159 8. Remove the replacement DIMM from the antistatic shipping bag, hold the DIMM by the corners, and align it to the slot. The notch among the pins on the DIMM should line up with the tab in the socket. 9. Make sure that the DIMM ejector tabs on the connector are in the open position, and then insert the DIMM squarely into the slot.
Page 160 3. Recable the system, as needed. If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber optic cables. 4. Complete the reinstallation of the controller module: If your system is in… Then perform these steps… An HA pair The controller module begins to boot as soon as it is fully seated in the chassis.
Page 161 If your system is in… Then perform these steps… A stand-alone configuration a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position. Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.
Page 162 During the boot process, you can safely respond to the prompts until the Maintenance mode prompt (*>) appears. 3. Run diagnostics on the system memory: sldiag device run -dev mem 4. Verify that no hardware problems resulted from the replacement of the DIMMs: sldiag device status -dev mem -long -state failed System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of...
Page 163 Rerun the system-level diagnostic test. Step 6: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 164 How you replace the disk depends on how the disk drive is being used. If SED authentication is enabled, you must use the SED replacement instructions in the ONTAP 9 NetApp Encryption Power Guide. These Instructions describe additional steps you must perform before and after replacing an SED.
Page 165 Option 1: Replace SSD 1. If you want to manually assign drive ownership for the replacement drive, you need to disable automatic drive assignment replacement drive, if it is enabled You manually assign drive ownership and then reenable automatic drive assignment later in this procedure.
Page 166 -node node_name -autoassign on You must reenable automatic drive assignment on both controller modules. 10. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp...
Page 167 Depending on the storage system, the disk drives have the release button located at the top or on the left of the disk drive face. For example, the following illustration shows a disk drive with the release button located on the top of the disk drive face: The cam handle on the disk drive springs open partially and the disk drive releases from the midplane.
Page 168 13. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 169 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 170 5. Turn the controller module over and place it on a flat, stable surface. 6. Open the cover by sliding in the blue tabs to release the cover, and then swing the cover up and open. Step 3: Replace the NVMEM battery To replace the NVMEM battery in your system, you must remove the failed NVMEM battery from the system and replace it with a new NVMEM battery.
Page 171 1. Check the NVMEM LED: ◦ If your system is in an HA configuration, go to the next step. ◦ If your system is in a stand-alone configuration, cleanly shut down the controller module, and then check the NVRAM LED identified by the NV icon. The NVRAM LED blinks while destaging contents to the flash memory when you halt the system.
Page 172 8. Slide the battery pack down along the sheet metal side wall until the support tabs on the side wall hook into the slots on the battery pack, and the battery pack latch engages and clicks into the opening on the side wall.
Page 173 If your system is in… Then perform these steps… An HA pair The controller module begins to boot as soon as it is fully seated in the chassis. Be prepared to interrupt the boot process. a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position.
Page 174 If your system is in… Then perform these steps… A stand-alone configuration a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position. Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.
Page 175 During the boot process, you can safely respond to the prompts until the Maintenance mode prompt (*>) appears. 3. Run diagnostics on the NVMEM memory: sldiag device run -dev nvmem 4. Verify that no hardware problems resulted from the replacement of the NVMEM battery: sldiag device status -dev nvmem -long -state failed System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of...
Page 176 Rerun the system-level diagnostic test. Step 6: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 177 All other components in the system must be functioning properly; if not, you must contact technical support. • The power supplies are redundant and hot-swappable. • This procedure is written for replacing one power supply at a time. Cooling is integrated with the power supply, so you must replace the power supply within two minutes of removal to prevent overheating due to reduced airflow.
Page 178 5. Use the cam handle to slide the power supply out of the system. When removing a power supply, always use two hands to support its weight. 6. Make sure that the on/off switch of the new power supply is in the Off position. 7.
Page 179 11. After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800- 44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 180 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 181 5. Turn the controller module over and place it on a flat, stable surface. 6. Open the cover by sliding in the blue tabs to release the cover, and then swing the cover up and open. Step 3: Replace the RTC battery To replace the RTC battery, locate it inside the controller and follow the specific sequence of steps.
Page 182 1. Locate the RTC battery. 2. Gently push the battery away from the holder, rotate it away from the holder, and then lift it out of the holder. Note the polarity of the battery as you remove it from the holder. The battery is marked with a plus sign and must be positioned in the holder correctly.
Page 183: Fas2700 System Documentation
-node local -auto -giveback true Step 5: Complete the replacement process After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp...
Page 184 Video two of two: Performing end-to-end software configuration The following video shows end-to-end software configuration for systems running ONTAP 9.2 and later. NetApp video: Software configuration for vSphere NAS datastores for FAS/AFF systems running ONTAP 9.2 Detailed guide - AFF A220 and FAS2700 This guide gives detailed step-by-step instructions for installing a typical NetApp system.
Page 185 NetApp Product Registration 4. Download and install Config Advisor on your laptop. NetApp Downloads: Config Advisor 5. Inventory and make a note of the number and types of cables you received. The following table identifies the types of cables you might receive. If you receive a cable not listed in the table, see the Hardware Universe to locate the cable and identify its use.
Page 186 6. Download and complete the Cluster configuration worksheet. Cluster Configuration Worksheet Step 2: Install the hardware You need to install your system in a 4-post rack or NetApp system cabinet, as applicable. Steps 1. Install the rail kits, as needed.
Page 187 3. Attach cable management devices (as shown). 4. Place the bezel on the front of the system. Step 3: Cable controllers to your network You can cable the controllers to your network by using the two-node switchless cluster method or by using the cluster interconnect network. Option 1: Cable a two-node switchless cluster, unified network configuration Management network, UTA2 data network, and management ports on the controllers are connected to switches.
Page 188 Step Perform on each controller Cable the cluster interconnect ports to each other with the cluster interconnect cable: • e0a to e0a • e0b to e0b...
Page 189 Step Perform on each controller Use one of the following cable types to cable the UTA2 data ports to your host network: An FC host • 0c and 0d • or 0e and 0f A 10GbE • e0c and e0d •...
Page 190 2. To cable your storage, see Cabling controllers to drive shelves Option 2: Cable a switched cluster, unified network configuration Management network, UTA2 data network, and management ports on the controllers are connected to switches. The cluster interconnect ports are cabled to the cluster interconnect switches.
Page 191 Step Perform on each controller module Cable e0a and e0b to the cluster interconnect switches with the cluster interconnect cable: Use one of the following cable types to cable the UTA2 data ports to your host network: An FC host •...
Page 192 Step Perform on each controller module Cable the e0M ports to the management network switches with the RJ45 cables: DO NOT plug in the power cords at this point. 2. To cable your storage, see Cabling controllers to drive shelves Option 3: Cable a two-node switchless cluster, Ethernet network configuration Management network, Ethernet data network, and management ports on the controllers are connected to switches.
Page 193 Step Perform on each controller Cable the cluster interconnect ports to each other with the cluster interconnect cable: • e0a to e0a • e0b to e0b Use the Cat 6 RJ45 cable to cable the e0c through e0f ports to your host network:...
Page 194 Step Perform on each controller Cable the e0M ports to the management network switches with the RJ45 cables: DO NOT plug in the power cords at this point. 2. To cable your storage, see Cabling controllers to drive shelves Option 4: Cable a switched cluster, Ethernet network configuration Management network, Ethernet data network, and management ports on the controllers are connected to switches.
Page 195 Step Perform on each controller module Cable e0a and e0b to the cluster interconnect switches with the cluster interconnect cable: Use the Cat 6 RJ45 cable to cable the e0c through e0f ports to your host network:...
Page 196 Cabling controllers to drive shelves Step 4: Cable controllers to drive shelves You must cable the controllers to your shelves using the onboard storage ports. NetApp recommends MP-HA cabling for systems with external storage. If you have a SAS tape drive, you can use single-path cabling.
Page 197 Step Perform on each controller Cable the shelf-to-shelf ports. • Port 3 on IOM A to port 1 on the IOM A on the shelf directly below. • Port 3 on IOM B to port 1 on the IOM B on the shelf directly below. mini-SAS HD to mini-SAS HD cables Connect each node to IOM A in the stack.
Page 198 Step 5: Complete system setup and configuration You can complete the system setup and configuration using cluster discovery with only a connection to the switch and laptop, or by connecting directly to a controller in the system and then connecting to the management switch. Option 1: Complete system setup if network discovery is enabled If you have network discovery enabled on your laptop, you can complete system setup and configuration using automatic cluster discovery.
Page 199 Double-click either ONTAP icon and accept any certificates displayed on your screen. XXXXX is the system serial number for the target node. System Manager opens. 7. Use System Manager guided setup to configure your system using the data you collected in the NetApp ONTAP Configuration Guide. ONTAP Configuration Guide 8.
Page 200 c. Connect the laptop or console to the switch on the management subnet. d. Assign a TCP/IP address to the laptop or console, using one that is on the management subnet. 2. Use the following animation to set one or more drive shelf IDs: Setting drive shelf IDs 3.
Page 201 Point your browser to the node management IP address. The format for the address is https://x.x.x.x. b. Configure the system using the data you collected in the NetApp ONTAP Configuration guide. ONTAP Configuration Guide 7. Verify the health of your system by running Config Advisor.
Page 202 Option 1: Check NVE or NSE on systems running ONTAP 9.5 and earlier Before shutting down the impaired controller, you need to check whether the system has either NetApp Volume Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.
Page 203 Retrieve and restore all authentication keys and associated key IDs: security key-manager restore -address * If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column displays for all authentication keys and that all key managers...
Page 204 Retrieve and restore all authentication keys and associated key IDs: security key-manager restore -address * If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column displays for all authentication keys and that all key managers...
Page 205 Option 2: Check NVE or NSE on systems running ONTAP 9.6 and later Before shutting down the impaired controller, you need to verify whether the system has either NetApp Volume Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.
Page 206 Restore the external key management authentication keys to all nodes in the cluster: security key-manager external restore If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column equals for all authentication keys:...
Page 207 b. Verify the Restored column shows for all authentication keys: security key-manager key-query c. Verify that the type shows onboard, and then manually back up the OKM Key Manager information. d. Go to advanced privilege mode and enter when prompted to continue: set -priv advanced e.
Page 208 If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column equals for all authentication keys: Restored security key- manager key-query c. You can safely shut down the controller. 3. If the type displays and the column displays anything other than...
Page 209 If the impaired controller Then… displays… Press Ctrl-C, and then respond when prompted. Waiting for giveback… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 210 If the impaired controller is Then… displaying… The LOADER prompt Go to Remove controller module. Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name...
Page 211 5. Turn the controller module over and place it on a flat, stable surface. 6. Open the cover by sliding in the blue tabs to release the cover, and then swing the cover up and open. Step 2: Replace the boot media You must locate the boot media in the controller and follow the directions to replace it.
Page 212 • A copy of the same image version of ONTAP as what the impaired controller was running. You can download the appropriate image from the Downloads section on the NetApp Support Site ◦ If NVE is enabled, download the image with NetApp Volume Encryption, as indicated in the download button.
Page 213 ◦ If NVE is not enabled, download the image without NetApp Volume Encryption, as indicated in the download button. • If your system is an HA pair, you must have a network connection. • If your system is a stand-alone system you do not need a network connection, but you must perform an additional reboot when restoring the var file system.
Page 214 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. Other parameters might be necessary for your interface. You can enter help ifconfig the firmware prompt for details.
Page 215 Restore OKM, NSE, and NVE as needed - AFF A220 and FAS2700 Once environment variables are checked, you must complete steps specific to systems that have Onboard Key Manager (OKM), NetApp Storage Encryption (NSE) or NetApp Volume Encryption (NVE) enabled.
Page 216 Option 1: Restore NVE or NSE when Onboard Key Manager is enabled Steps 1. Connect the console cable to the target controller. 2. Use the command at the LOADER prompt to boot the controller. boot_ontap 3. Check the console output: If the console Then…...
Page 217 --------------------------BEGIN BACKUP-------------------------- TmV0QXBwIEtleSBCbG9iAAEAAAAEAAAAcAEAAAAAAADuD+byAAAAACEAAAAAAAAA QAAAAAAAAABvOlH0AAAAAMh7qDLRyH1DBz12piVdy9ATSFMT0C0TlYFss4PDjTaV dzRYkLd1PhQLxAWJwOIyqSr8qY1SEBgm1IWgE5DLRqkiAAAAAAAAACgAAAAAAAAA 3WTh7gAAAAAAAAAAAAAAAAIAAAAAAAgAZJEIWvdeHr5RCAvHGclo+wAAAAAAAAAA IgAAAAAAAAAoAAAAAAAAAEOTcR0AAAAAAAAAAAAAAAACAAAAAAAJAGr3tJA/ LRzUQRHwv+1aWvAAAAAAAAAAACQAAAAAAAAAgAAAAAAAAACdhTcvAAAAAJ1PXeBf ml4NBsSyV1B4jc4A7cvWEFY6lLG6hc6tbKLAHZuvfQ4rIbYAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA H4nPQM0nrDRYRa9SCv8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAA ---------------------------END BACKUP--------------------------- 7. At the Boot Menu select the option for Normal Boot. The system boots to prompt. Waiting for giveback… 8. Move the console cable to the partner controller and login as admin. 9.
Page 218 b. Enter the key-manager key show -detail command to see a detailed view of all keys stored in the onboard key manager and verify that the column = for all authentication keys. Restored If the column = anything other than yes, contact Customer Support. Restored c.
Page 219 This command does not work if NVE (NetApp Volume Encryption) is configured 10. Use the security key-manager query to display the key IDs of the authentication keys that are stored on the key management servers.
Page 220 11. If the Onboard Key Management is enabled: a. Use the to see a detailed view of all keys stored in security key-manager key show -detail the onboard key manager. b. Use the command and verify that the security key-manager key show -detail Restored column = for all authentication keys.
Page 221 -auto-giveback true Return the failed part to NetApp - AFF A220 and FAS2700 After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 222 • You must replace the failed component with a replacement FRU component you received from your provider. Step 1: Shut down the impaired controller Shut down or take over the impaired controller using the appropriate procedure for your configuration. Option 1: Most configurations To shut down the impaired controller, you must determine the status of the controller and, if necessary, take over the controller so that the healthy controller continues to serve data from the impaired controller storage.
Page 223 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller: prompt (enter system password) • For an HA pair, take over the impaired controller from the healthy controller: storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 224 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 225 5. Turn the controller module over and place it on a flat, stable surface. 6. Open the cover by sliding in the blue tabs to release the cover, and then swing the cover up and open. Step 3: Replace a caching module To replace a caching module referred to as the M.2 PCIe card on the label on your controller, locate the slot inside the controller and follow the specific sequence of steps.
Page 226 Your storage system must meet certain criteria depending on your situation: • It must have the appropriate operating system for the caching module you are installing. • It must support the caching capacity. • All other components in the storage system must be functioning properly; if not, you must contact technical support.
Page 227 7. Close the controller module cover, as needed. Step 4: Reinstall the controller module After you replace components in the controller module, reinstall it into the chassis. Steps 1. If you are not already grounded, properly ground yourself. 2. If you have not already done so, replace the cover on the controller module. 3.
Page 228 If your system is in… Then perform these steps… An HA pair The controller module begins to boot as soon as it is fully seated in the chassis. Be prepared to interrupt the boot process. a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position.
Page 229 If your system is in… Then perform these steps… A stand-alone configuration a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position. Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.
Page 230 appears. 3. Run diagnostics on the caching module: sldiag device run -dev fcache 4. Verify that no hardware problems resulted from the replacement of the caching module: sldiag device status -dev fcache -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.
Page 231 If the system-level Then… diagnostics tests… Resulted in some test Determine the cause of the problem: failures a. Exit Maintenance mode: halt After you issue the command, wait until the system stops at the LOADER prompt. b. Turn off or leave on the power supplies, depending on how many controller modules are in the chassis: ◦...
Page 232 cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B controller_B_1 configured enabled waiting for switchback recovery 2 entries were displayed. 2. Verify that resynchronization is complete on all SVMs: metrocluster vserver show 3.
Page 233 Step 7: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888- 463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 234 If your system is running Then… clustered ONTAP with… Two controllers in the cluster cluster ha modify -configured false storage failover modify -node node0 -enabled false More than two controllers in the storage failover modify -node node0 -enabled false cluster 2.
Page 235 • If you have a MetroCluster configuration, you must have confirmed that the MetroCluster Configuration State is configured and that the nodes are in an enabled and normal state (metrocluster node show). Steps 1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message: system node autosupport invoke -node * -type all -message MAINT=number_of_hours_downh The following AutoSupport message suppresses automatic case creation for two hours:...
Page 236 4. Use the cam handle to slide the power supply out of the system. When removing a power supply, always use two hands to support its weight. 5. Repeat the preceding steps for any remaining power supplies. 6. Using both hands, support and align the edges of the power supply with the opening in the system chassis, and then gently push the power supply into the chassis using the cam handle.
Page 237 4. Set the controller module aside in a safe place, and repeat these steps if you have another controller module in the chassis. Step 3: Move drives to the new chassis You need to move the drives from each bay opening in the old chassis to the same bay opening in the new chassis.
Page 238 Step 4: Replace a chassis from within the equipment rack or system cabinet You must remove the existing chassis from the equipment rack or system cabinet before you can install the replacement chassis. 1. Remove the screws from the chassis mount points. 2.
Page 239 Restore and verify the configuration - AFF A220 and FAS2700 You must verify the HA state of the chassis and run System-Level diagnostics, switch back aggregates, and return the failed part to NetApp, as described in the RMA instructions shipped with the kit.
Page 240 Step 1: Verify and set the HA state of the chassis You must verify the HA state of the chassis, and, if necessary, update the state to match your system configuration. 1. In Maintenance mode, from either controller module, display the HA state of the local controller module and chassis: ha-config show The HA state should be the same for all components.
Page 241 During the boot process, you can safely respond to prompts: 2. Repeat the previous step on the second controller if you are in an HA configuration. Both controllers must be in Maintenance mode to run the interconnect test. 3. At the LOADER prompt, access the special drivers specifically designed for system-level diagnostics to function properly: boot_diags During the boot process, you can safely respond...
Page 242 If the system-level diagnostics Then… tests… Were completed without any a. Clear the status logs: sldiag device clearstatus failures b. Verify that the log was cleared: sldiag device status The following default response is displayed: SLDIAG: No log messages are present. c.
Page 243 If your system is running Then… ONTAP… Resulted in some test failures Determine the cause of the problem. a. Exit Maintenance mode: halt b. Perform a clean shutdown, and then disconnect the power supplies. c. Verify that you have observed all of the considerations identified for running system-level diagnostics, that cables are securely connected, and that hardware components are properly installed in the storage system.
Page 244 6. Reestablish any SnapMirror or SnapVault configurations. Step 4: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 245 steps are required because the failure is restricted to an HA pair and storage failover commands can be used to provide nondisruptive operation during the replacement. • This procedure includes steps for automatically or manually reassigning drives to the replacement controller, depending on your system’s configuration.
Page 246 3. Take the impaired controller to the LOADER prompt: If the impaired controller is Then… displaying… The LOADER prompt Go to Remove controller module.. Waiting for giveback… Press Ctrl-C, and then respond y. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name...
Page 247 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 248 6. Turn the controller module over and place it on a flat, stable surface. 7. Open the cover by sliding in the blue tabs to release the cover, and then swing the cover up and open. Step 2: Move the NVMEM battery To move the NVMEM battery from the old controller module to the new controller module, you must perform a specific sequence of steps.
Page 249 1. Check the NVMEM LED: ◦ If your system is in an HA configuration, go to the next step. ◦ If your system is in a stand-alone configuration, cleanly shut down the controller module, and then check the NVRAM LED identified by the NV icon. The NVRAM LED blinks while destaging contents to the flash memory when you halt the system.
Page 250 7. Position the battery pack by aligning the battery holder key ribs to the “V” notches on the sheet metal side wall. 8. Slide the battery pack down along the sheet metal side wall until the support tabs on the side wall hook into the slots on the battery pack, and the battery pack latch engages and clicks into the opening on the side wall.
Page 251 controller module to the corresponding slots in the replacement controller module. 1. Locate the DIMMs on your controller module. 2. Note the orientation of the DIMM in the socket so that you can insert the DIMM in the replacement controller module in the proper orientation. 3.
Page 252 Make sure that the plug locks down onto the controller module. Step 5: Move a caching module, if present If your AFF A220 or FAS2700 system has a caching module, you need to move the caching module from the old controller module to the replacement controller module. The caching module is referred to as the “M.2 PCIe card”...
Page 253 5. Reseat and push the heatsink down to engage the locking button on the caching module housing. 6. Close the controller module cover, as needed. Step 6: Install the controller After you install the components from the old controller module into the new controller module, you must install the new controller module into the system chassis and boot the operating system.
Page 254 If your system is in… Then perform these steps… An HA pair The controller module begins to boot as soon as it is fully seated in the chassis. Be prepared to interrupt the boot process. a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position.
Page 255 If your system is in… Then perform these steps… A stand-alone configuration a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position. Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.
Page 256 Restore and verify the system configuration - AFF A220 and FAS2700 After completing the hardware replacement and booting to Maintenance mode, you verify the low-level system configuration of the replacement controller and reconfigure system settings as necessary. Step 1: Set and verify system time after replacing the controller You should check the time and date on the replacement controller module against the healthy controller module in an HA pair, or against a reliable time server in a stand-alone configuration.
Page 257 ▪ ▪ ▪ mcc-2n ▪ mccip ▪ non-ha b. Confirm that the setting has changed: ha-config show Step 3: Run system-level diagnostics You should run comprehensive or focused diagnostic tests for specific components and subsystems whenever you replace the controller. All commands in the diagnostic procedures are issued from the controller where the component is being replaced.
Page 258 If you want to run diagnostic Then… tests on… Individual components a. Clear the status logs: sldiag device clearstatus b. Display the available tests for the selected devices: sldiag device show -dev dev_name dev_name can be any one of the ports and devices identified in the preceding step.
Page 259 If you want to run diagnostic Then… tests on… Multiple components at the same a. Review the enabled and disabled devices in the output from the time preceding procedure and determine which ones you want to run concurrently. b. List the individual tests for the device: sldiag device show -dev dev_name c.
Page 260 Recable the system and reassign disks - AFF A220 and FAS2700 To complete the replacement procedure and restore your system to full operation, you must recable the storage, confirm disk reassignment, restore the NetApp Storage Encryption configuration (if necessary), and install licenses for the new controller. You must complete a series of tasks before restoring your system to full operation.
Page 261 c. Click the Cabling tab, and then examine the output. Make sure that all disk shelves are displayed and all disks appear in the output, correcting any cabling issues you find. d. Check other cabling by clicking the appropriate tab, and then examining the output from Config Advisor. Step 2: Reassign disks If the storage system is in an HA pair, the system ID of the new controller module is automatically assigned to the disks when the giveback occurs at the end of the procedure.
Page 262 node1> `storage failover show` Takeover Node Partner Possible State Description ------------ ------------ -------- ------------------------------------- node1 node2 false System ID changed on partner (Old: 151759755, New: 151759706), In takeover node2 node1 Waiting for giveback (HA mailboxes) 4. From the healthy controller, verify that any coredumps are saved: a.
Page 263 node1> `storage disk show -ownership` Disk Aggregate Home Owner DR Home Home ID Owner ID DR Home ID Reserver Pool ----- ------ ----- ------ -------- ------- ------- ------- --------- 1.0.0 aggr0_1 node1 node1 1873775277 1873775277 1873775277 Pool0 1.0.1 aggr0_1 node1 node1 1873775277 1873775277 1873775277 Pool0 Option 2: Manually reassign the system ID on a stand-alone system in ONTAP...
Page 264 5. Reassign disk ownership by using the system ID information obtained from the disk show command: disk reassign -s old system ID disk reassign -s 118073209 6. Verify that the disks were assigned correctly: disk show -a The disks belonging to the replacement node should show the new system ID. The following example now show the disks owned by system-1 the new system ID, 118065481: *>...
Page 265 Local System ID: 118065481 4. Reassign disk ownership (for FAS systems) or LUN ownership (for FlexArray systems), by using the system ID information obtained from the disk show command: disk reassign -s old system ID In the case of the preceding example, the command is:...
Page 266 Display the results of the MetroCluster check: metrocluster check show e. Run Config Advisor. Go to the Config Advisor page on the NetApp Support Site at support.netapp.com/NOW/download/tools/config_advisor/. After running Config Advisor, review the tool’s output and follow the recommendations in the output to address any issues discovered.
Page 267 -privilege admin Complete system restoration - AFF A220 and FAS2700 To restore your system to full operation, you must restore the NetApp Storage Encryption configuration (if necessary), and install licenses for the new controller, and return the failed part to NetApp, as described in the RMA instructions shipped with the kit.
Page 268 If any LIFs are listed as false, revert them to their home ports: network interface revert 2. Register the system serial number with NetApp Support. ◦ If AutoSupport is enabled, send an AutoSupport message to register the serial number. ◦ If AutoSupport is not enabled, call NetApp Support to register the serial number.
Page 269 cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B controller_B_1 configured enabled waiting for switchback recovery 2 entries were displayed. 2. Verify that resynchronization is complete on all SVMs: metrocluster vserver show 3.
Page 270 Step 5: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800-44- 638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 271 If the impaired controller is Then… displaying… Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 272 • If you have a MetroCluster configuration, you must have confirmed that the MetroCluster Configuration State is configured and that the nodes are in an enabled and normal state (metrocluster node show). Steps 1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message: system node autosupport invoke -node * -type all -message MAINT=number_of_hours_downh The following AutoSupport message suppresses automatic case creation for two hours:...
Page 273 4. Squeeze the latch on the cam handle until it releases, open the cam handle fully to release the controller module from the midplane, and then, using two hands, pull the controller module out of the chassis. 5. Turn the controller module over and place it on a flat, stable surface. 6.
Page 274 Step 3: Replace the DIMMs To replace the DIMMs, locate them inside the controller and follow the specific sequence of steps. If you are replacing a DIMM, you need to remove it after you have unplugged the NVMEM battery from the controller module.
Page 275 a. Locate the battery, press the clip on the face of the battery plug to release the lock clip from the plug socket, and then unplug the battery cable from the socket. b. Confirm that the NVMEM LED is no longer lit. c.
Page 276 9. Remove the replacement DIMM from the antistatic shipping bag, hold the DIMM by the corners, and align it to the slot. The notch among the pins on the DIMM should line up with the tab in the socket. 10. Make sure that the DIMM ejector tabs on the connector are in the open position, and then insert the DIMM squarely into the slot.
Page 277 Do not completely insert the controller module in the chassis until instructed to do so. 4. Recable the system, as needed. If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber optic cables. 5.
Page 278 If your system is in… Then perform these steps… A stand-alone configuration a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position. Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.
Page 279 function properly: boot_diags During the boot process, you can safely respond to the prompts until the Maintenance mode prompt (*>) appears. 3. Run diagnostics on the system memory: sldiag device run -dev mem 4. Verify that no hardware problems resulted from the replacement of the DIMMs: sldiag device status -dev mem -long -state failed System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of...
Page 280 If your controller is in… Then… Resulted in some test failures Determine the cause of the problem: a. Exit Maintenance mode: halt After you issue the command, wait until the system stops at the LOADER prompt. b. Turn off or leave on the power supplies, depending on how many controller modules are in the chassis: ◦...
Page 281 1. Verify that all nodes are in the enabled state: metrocluster node show cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B ...
Page 282 Step 7: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888- 463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 283 You may also choose to watch the Replace failed drive video that shows an overview of the embedded drive replacement procedure.
Page 284 Option 1: Replace SSD 1. If you want to manually assign drive ownership for the replacement drive, you need to disable automatic drive assignment replacement drive, if it is enabled You manually assign drive ownership and then reenable automatic drive assignment later in this procedure.
Page 285 -node node_name -autoassign on You must reenable automatic drive assignment on both controller modules. 10. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp...
Page 286 Depending on the storage system, the disk drives have the release button located at the top or on the left of the disk drive face. For example, the following illustration shows a disk drive with the release button located on the top of the disk drive face: The cam handle on the disk drive springs open partially and the disk drive releases from the midplane.
Page 287 13. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 288 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 289 1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message: system node autosupport invoke -node * -type all -message MAINT=number_of_hours_downh The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*> system node autosupport invoke -node * -type all -message MAINT=2h 2.
Page 290 module from the midplane, and then, using two hands, pull the controller module out of the chassis. 5. Turn the controller module over and place it on a flat, stable surface. 6. Open the cover by sliding in the blue tabs to release the cover, and then swing the cover up and open. Step 3: Replace the NVMEM battery To replace the NVMEM battery in your system, you must remove the failed NVMEM battery from the system and replace it with a new NVMEM battery.
Page 291 3. Locate the NVMEM battery in the controller module. 4. Locate the battery plug and squeeze the clip on the face of the battery plug to release the plug from the socket, and then unplug the battery cable from the socket. 5.
Page 292 If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber optic cables. 5. Complete the reinstallation of the controller module: If your system is in… Then perform these steps… An HA pair The controller module begins to boot as soon as it is fully seated in the chassis.
Page 293 If your system is in… Then perform these steps… A stand-alone configuration a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position. Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.
Page 294 function properly: boot_diags During the boot process, you can safely respond to the prompts until the Maintenance mode prompt (*>) appears. 3. Run diagnostics on the NVMEM memory: sldiag device run -dev nvmem 4. Verify that no hardware problems resulted from the replacement of the NVMEM battery: sldiag device status -dev nvmem -long -state failed System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of...
Page 295 If your controller is in… Then… Resulted in some test failures Determine the cause of the problem: a. Exit Maintenance mode: halt After you issue the command, wait until the system stops at the LOADER prompt. b. Turn off or leave on the power supplies, depending on how many controller modules are in the chassis: ◦...
Page 296 1. Verify that all nodes are in the enabled state: metrocluster node show cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B ...
Page 297 Step 7: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888- 463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 298 5. Use the cam handle to slide the power supply out of the system. When removing a power supply, always use two hands to support its weight. 6. Make sure that the on/off switch of the new power supply is in the Off position. 7.
Page 299 11. After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800- 44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 300 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 301 Step 2: Remove controller module To access components inside the controller, you must first remove the controller module from the system and then remove the cover on the controller module. 1. If you are not already grounded, properly ground yourself. 2.
Page 302 Step 3: Replace the RTC battery To replace the RTC battery, locate it inside the controller and follow the specific sequence of steps. 1. If you are not already grounded, properly ground yourself. 2. Locate the RTC battery.
Page 303 3. Gently push the battery away from the holder, rotate it away from the holder, and then lift it out of the holder. Note the polarity of the battery as you remove it from the holder. The battery is marked with a plus sign and must be positioned in the holder correctly.
Page 304 3. Recable the system, as needed. If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber optic cables. 4. If the power supplies were unplugged, plug them back in and reinstall the power cable retainers. 5.
Page 305 cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B controller_B_1 configured enabled waiting for switchback recovery 2 entries were displayed. 2. Verify that resynchronization is complete on all SVMs: metrocluster vserver show 3.
Page 306: Fas8200 System Documentation
Step 6: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888- 463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 307 If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller; see the NetApp Encryption overview with the CLI. Steps 1.
Page 308 Option 1: Check NVE or NSE on systems running ONTAP 9.5 and earlier Before shutting down the impaired controller, you need to check whether the system has either NetApp Volume Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.
Page 309 If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column displays for all authentication keys and that all key managers Restored display available: security key-manager query c. Shut down the impaired controller. 3. If you saw the message This command is not supported when onboard key management is enabled,...
Page 310 Retrieve and restore all authentication keys and associated key IDs: security key-manager restore -address * If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column displays for all authentication keys and that all key managers...
Page 311 Option 2: Check NVE or NSE on systems running ONTAP 9.6 and later Before shutting down the impaired controller, you need to verify whether the system has either NetApp Volume Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.
Page 312 If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the Restored column equals for all authentication keys: security key- manager key-query c. Shut down the impaired controller. 3. If the type displays and the column displays anything other than...
Page 313 Restored column displays anything other than yes: a. Enter the onboard security key-manager sync command: security key-manager external sync If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column equals for all authentication keys: Restored security key- manager key-query c.
Page 314 Shut down the impaired controller - FAS8200 Option 1: Most systems After completing the NVE or NSE tasks, you need to complete the shutdown of the impaired controller. After completing the NVE or NSE tasks, you need to complete the shutdown of the impaired controller.
Page 315 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 316 If the impaired controller… Then… Has not automatically switched Review the veto messages and, if possible, resolve the issue and try over, you attempted switchover again. If you are unable to resolve the issue, contact technical support. with the metrocluster command, and the switchover switchover was vetoed...
Page 317 If the healing is vetoed, you have the option of reissuing the command with the metrocluster heal -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation. 7. Verify that the heal operation is complete by using the command on metrocluster operation show the destination cluster:...
Page 318 Thumbscrew Cam handle 5. Pull the cam handle downward and begin to slide the controller module out of the chassis. Make sure that you support the bottom of the controller module as you slide it out of the chassis. Step 2: Replace the boot media You must locate the boot media in the controller and follow the directions to replace it.
Page 319 3. Press the blue button on the boot media housing to release the boot media from its housing, and then gently pull it straight out of the boot media socket. Do not twist or pull the boot media straight up, because this could damage the socket or the boot media.
Page 320 • A copy of the same image version of ONTAP as what the impaired controller was running. You can download the appropriate image from the Downloads section on the NetApp Support Site ◦ If NVE is enabled, download the image with NetApp Volume Encryption, as indicated in the download button.
Page 321 ▪ 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.
Page 322 If your system has… Then… A network connection a. Press when prompted to restore the backup configuration. b. Set the healthy controller to advanced privilege level: -privilege advanced c. Run the restore backup command: system node restore- backup -node local -target-address impaired_node_IP_address d.
Page 323 8. Give back the controller using the storage failover giveback -fromnode local command. 9. At the cluster prompt, check the logical interfaces with the command. net int -is-home false If any interfaces are listed as "false", revert those interfaces back to their home port using the net int command.
Page 324 This task only applies to two-node MetroCluster configurations. Steps 1. Verify that all nodes are in the enabled state: metrocluster node show cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A ...
Page 325 Restore OKM, NSE, and NVE as needed - FAS8200 Once environment variables are checked, you must complete steps specific to systems that have Onboard Key Manager (OKM), NetApp Storage Encryption (NSE) or NetApp Volume Encryption (NVE) enabled. Determine which section you should use to restore your OKM, NSE, or NVE configurations: If NSE or NVE are enabled along with Onboard Key Manager you must restore settings you captured at the beginning of this procedure.
Page 326 The data is output from either security key-manager backup show security command. key-manager onboard show-backup Example of backup data: --------------------------BEGIN BACKUP-------------------------- TmV0QXBwIEtleSBCbG9iAAEAAAAEAAAAcAEAAAAAAADuD+byAAAAACEAAAAAAAAA QAAAAAAAAABvOlH0AAAAAMh7qDLRyH1DBz12piVdy9ATSFMT0C0TlYFss4PDjTaV dzRYkLd1PhQLxAWJwOIyqSr8qY1SEBgm1IWgE5DLRqkiAAAAAAAAACgAAAAAAAAA 3WTh7gAAAAAAAAAAAAAAAAIAAAAAAAgAZJEIWvdeHr5RCAvHGclo+wAAAAAAAAAA IgAAAAAAAAAoAAAAAAAAAEOTcR0AAAAAAAAAAAAAAAACAAAAAAAJAGr3tJA/ LRzUQRHwv+1aWvAAAAAAAAAAACQAAAAAAAAAgAAAAAAAAACdhTcvAAAAAJ1PXeBf ml4NBsSyV1B4jc4A7cvWEFY6lLG6hc6tbKLAHZuvfQ4rIbYAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA H4nPQM0nrDRYRa9SCv8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAA ---------------------------END BACKUP--------------------------- 7. At the Boot Menu select the option for Normal Boot. The system boots to prompt.
Page 327 12. Move the console cable to the target controller. 13. If you are running ONTAP 9.5 and earlier, run the key-manager setup wizard: a. Start the wizard using the command, and then security key-manager setup -nodenodename enter the passphrase for onboard key management when prompted. b.
Page 328 This command does not work if NVE (NetApp Volume Encryption) is configured 10. Use the security key-manager query to display the key IDs of the authentication keys that are stored on the key management servers.
Page 329 Check the output of the security key-manager query again to ensure that the column = Restored and all key managers report in an available state 11. If the Onboard Key Management is enabled: a. Use the to see a detailed view of all keys stored in security key-manager key show -detail the onboard key manager.
Page 330 -auto-giveback true command. Return the failed part to NetApp - FAS8200 After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-...
Page 331 to do so results in performance degradation. You might want to erase the contents of your caching module before replacing it. . Although data on the caching module is encrypted, you might want to erase any data from the impaired caching module and verify that the caching module has no data: ..
Page 332 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 333 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 334 5. Check the state of the aggregates by using the storage aggregate show command. controller_A_1::> storage aggregate show Aggregate Size Available Used% State #Vols Nodes RAID Status --------- -------- --------- ----- ------- ------ ---------------- ------------ aggr_b2 227.1GB 227.1GB 0% online 0 mcc1-a2 raid_dp, mirrored, normal...
Page 335 4. Loosen the thumbscrew on the cam handle on the controller module. Thumbscrew Cam handle 5. Pull the cam handle downward and begin to slide the controller module out of the chassis. Make sure that you support the bottom of the controller module as you slide it out of the chassis. Step 3: Replace or add a caching module To replace or add a caching module referred to as the M.2 PCIe card on the label on your controller, locate the slots inside the controller and follow the specific sequence of steps.
Page 336 The storage system comes with two slots available for the caching module and only one slot is occupied, by default. 2. If you are adding a caching module, go to the next step; if you are replacing the caching module, gently pull it straight out of the housing.
Page 337 Do not completely insert the controller module in the chassis until instructed to do so. 2. Recable the system, as needed. If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber optic cables. 3.
Page 338 4. Verify that no hardware problems resulted from the replacement of the caching module: sldiag device status -dev fcache -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.
Page 339 If your controller is in… Then… Resulted in some test failures Determine the cause of the problem: a. Exit Maintenance mode: halt After you issue the command, wait until the system stops at the LOADER prompt. b. Turn off or leave on the power supplies, depending on how many controller modules are in the chassis: ◦...
Page 340 cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B controller_B_1 configured enabled waiting for switchback recovery 2 entries were displayed. 2. Verify that resynchronization is complete on all SVMs: metrocluster vserver show 3.
Page 341 Step 7: Complete the replacement process After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800-44- 638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 342 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 343 Steps 1. Check the MetroCluster status to determine whether the impaired controller has automatically switched over to the healthy controller: metrocluster show 2. Depending on whether an automatic switchover has occurred, proceed according to the following table: If the impaired controller… Then…...
Page 344 controller_A_1::> storage aggregate show Aggregate Size Available Used% State #Vols Nodes RAID Status --------- -------- --------- ----- ------- ------ ---------------- ------------ aggr_b2 227.1GB 227.1GB 0% online 0 mcc1-a2 raid_dp, mirrored, normal... 6. Heal the root aggregates by using the command. metrocluster heal -phase root-aggregates mcc1A::>...
Page 345 b. Open the power cable retainer, and then unplug the power cable from the power supply. c. Unplug the power cable from the power source. 3. Press down the release latch on the power supply cam handle, and then lower the cam handle to the fully open position to release the power supply from the mid plane.
Page 346 Power and Fault LEDs Cam handle Power cable locking mechanism 4. Use the cam handle to slide the power supply out of the system. When removing a power supply, always use two hands to support its weight. 5. Repeat the preceding steps for any remaining power supplies. 6.
Page 347 Cam handle Fan module Cam handle release latch Fan module Attention LED 3. 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. The fan modules are short.
Page 348 10. Align the bezel with the ball studs, and then gently push the bezel onto the ball studs. Step 3: Remove the controller module To replace the chassis, you must remove the controller module or modules from the old chassis. 1.
Page 349 Step 4: Replace a chassis from within the equipment rack or system cabinet You must remove the existing chassis from the equipment rack or system cabinet before you can install the replacement chassis. 1. Remove the screws from the chassis mount points. If the system is in a system cabinet, you might need to remove the rear tie-down bracket.
Page 350 From the boot menu, select the option for Maintenance mode. Restore and verify the configuration - FAS8200 You must verify the HA state of the chassis and run System-Level diagnostics, switch back aggregates, and return the failed part to NetApp, as described in the RMA...
Page 351 instructions shipped with the kit. Step 1: Verify and set the HA state of the chassis You must verify the HA state of the chassis, and, if necessary, update the state to match your system configuration. 1. In Maintenance mode, from either controller module, display the HA state of the local controller module and chassis: ha-config show The HA state should be the same for all components.
Page 352 During the boot process, you can safely respond to prompts: 2. Repeat the previous step on the second controller if you are in an HA configuration. Both controllers must be in Maintenance mode to run the interconnect test. 3. At the LOADER prompt, access the special drivers specifically designed for system-level diagnostics to function properly: boot_diags During the boot process, you can safely respond...
Page 353 If the system-level diagnostics Then… tests… Were completed without any a. Clear the status logs: sldiag device clearstatus failures b. Verify that the log was cleared: sldiag device status The following default response is displayed: SLDIAG: No log messages are present. c.
Page 354 If your system is running Then… ONTAP… Resulted in some test failures Determine the cause of the problem. a. Exit Maintenance mode: halt b. Perform a clean shutdown, and then disconnect the power supplies. c. Verify that you have observed all of the considerations identified for running system-level diagnostics, that cables are securely connected, and that hardware components are properly installed in the storage system.
Page 355 6. Reestablish any SnapMirror or SnapVault configurations. Step 4: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 356 • Any PCIe cards moved from the old controller module to the new controller module or added from existing customer site inventory must be supported by the replacement controller module. NetApp Hardware Universe • It is important that you apply the commands in these steps on the correct systems: ◦...
Page 357 MAINT=_number_of_hours_down_h The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*> system node autosupport invoke -node * -type all -message MAINT=2h 2. If the impaired controller is part of an HA pair, disable automatic giveback from the console of the healthy controller: storage failover modify -node local -auto-giveback false 3.
Page 358 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 359 controller_A_1::> metrocluster heal -phase aggregates [Job 130] Job succeeded: Heal Aggregates is successful. If the healing is vetoed, you have the option of reissuing the command with the metrocluster heal -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation.
Page 360 mcc1A::> metrocluster operation show Operation: heal-root-aggregates State: successful Start Time: 7/29/2016 20:54:41 End Time: 7/29/2016 20:54:42 Errors: - 8. On the impaired controller module, disconnect the power supplies. Replace the controller module hardware - FAS8200 To replace the controller module hardware, you must remove the impaired controller, move FRU components to the replacement controller module, install the replacement controller module in the chassis, and then boot the system to Maintenance mode.
Page 361 Thumbscrew Cam handle 6. Pull the cam handle downward and begin to slide the controller module out of the chassis. Make sure that you support the bottom of the controller module as you slide it out of the chassis. Step 2: Move the boot device You must locate the boot media and follow the directions to remove it from the old controller and insert it in the new controller.
Page 362 2. Press the blue button on the boot media housing to release the boot media from its housing, and then gently pull it straight out of the boot media socket. Do not twist or pull the boot media straight up, because this could damage the socket or the boot media.
Page 363 ◦ If your system is in a stand-alone configuration, cleanly shut down the controller module, and then check the NVRAM LED identified by the NV icon. The NVRAM LED blinks while destaging contents to the flash memory when you halt the system.
Page 364 Battery lock tab NVMEM battery pack 3. Grasp the battery and press the blue locking tab marked PUSH, and then lift the battery out of the holder and controller module. 4. Remove the battery from the controller module and set it aside. Step 4: Move the DIMMs To move the DIMMs, locate and move them from the old controller into the replacement controller and follow the specific sequence of steps.
Page 365 4. Locate the slot where you are installing the DIMM. 5. Make sure that the DIMM ejector tabs on the connector are in the open position, and then insert the DIMM squarely 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. Visually inspect the DIMM to verify that it is evenly aligned and fully inserted into the slot.
Page 366 1. Loosen the thumbscrew on the controller module side panel. 2. Swing the side panel off the controller module. Side panel PCIe card 3. Remove the PCIe card from the old controller module and set it aside. Make sure that you keep track of which slot the PCIe card was in. 4.
Page 367 7. Close the side panel and tighten the thumbscrew. Step 6: Move a caching module You must move the caching modules from the impaired controller modules to the replacement controller module when replacing a controller module. 1. Locate the caching module at the rear of the controller module and remove it: a.
Page 368 Step 7: Install the controller After you install the components from the old controller module into the new controller module, you must install the new controller module into the system chassis and boot the operating system. For HA pairs with two controller modules in the same chassis, the sequence in which you install the controller module is especially important because it attempts to reboot as soon as you completely seat it in the chassis.
Page 369 If your system is in… Then perform these steps… An HA pair The controller module begins to boot as soon as it is fully seated in the chassis. Be prepared to interrupt the boot process. a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position.
Page 370 If your system is in… Then perform these steps… A stand-alone configuration a. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position. Tighten the thumbscrew on the cam handle on back of the controller module.
Page 371 • The replacement node is the new node that replaced the impaired node as part of this procedure. • The healthy node is the HA partner of the replacement node. Steps 1. If the replacement node is not at the LOADER prompt, halt the system to the LOADER prompt. 2.
Page 372 All commands in the diagnostic procedures are issued from the controller where the component is being replaced. 1. If the controller to be serviced is not at the LOADER prompt, reboot the controller: halt After you issue the command, you should wait until the system stops at the LOADER prompt. 2.
Page 373 If you want to run diagnostic Then… tests on… Individual components a. Clear the status logs: sldiag device clearstatus b. Display the available tests for the selected devices: sldiag device show -dev dev_name dev_name can be any one of the ports and devices identified in the preceding step.
Page 374 If you want to run diagnostic Then… tests on… Multiple components at the same a. Review the enabled and disabled devices in the output from the time preceding procedure and determine which ones you want to run concurrently. b. List the individual tests for the device: sldiag device show -dev dev_name c.
Page 375 If the system-level diagnostics Then… tests… Were completed without any a. Clear the status logs: sldiag device clearstatus failures b. Verify that the log was cleared: sldiag device status The following default response is displayed: SLDIAG: No log messages are present. c.
Page 376 d. Check other cabling by clicking the appropriate tab, and then examining the output from Config Advisor. Step 2: Reassign disks If the storage system is in an HA pair, the system ID of the new controller module is automatically assigned to the disks when the giveback occurs at the end of the procedure.
Page 377 You can enter the following command to monitor the progress of the command: savecore system node run -node local-node-name partner savecore -s d. Return to the admin privilege level: set -privilege admin 5. Give back the controller: a. From the healthy controller, give back the replaced controller’s storage: storage failover giveback -ofnode replacement_node_name The replacement controller takes back its storage and completes booting.
Page 378 Local System ID: 118065481 4. Reassign disk ownership (for FAS systems) or LUN ownership (for FlexArray systems), by using the system ID information obtained from the disk show command: disk reassign -s old system ID In the case of the preceding example, the command is:...
Page 379 *> disk show -a Local System ID: 118065481 DISK OWNER POOL SERIAL NUMBER HOME ------- ------------- ----- ------------- ------------- disk_name system-1 (118065481) Pool0 J8Y0TDZC system-1 (118065481) disk_name system-1 (118065481) Pool0 J8Y09DXC system-1 (118065481) 6. From the healthy node, verify that any coredumps are saved: a.
Page 380 Display the results of the MetroCluster check: metrocluster check show e. Run Config Advisor. Go to the Config Advisor page on the NetApp Support Site at support.netapp.com/NOW/download/tools/config_advisor/. After running Config Advisor, review the tool’s output and follow the recommendations in the output to address any issues discovered.
Page 381 If any LIFs are listed as false, revert them to their home ports: network interface revert 2. Register the system serial number with NetApp Support. ◦ If AutoSupport is enabled, send an AutoSupport message to register the serial number. ◦ If AutoSupport is not enabled, call NetApp Support to register the serial number.
Page 382 This task only applies to two-node MetroCluster configurations. Steps 1. Verify that all nodes are in the enabled state: metrocluster node show cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A ...
Page 383 6. Reestablish any SnapMirror or SnapVault configurations. Step 5: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 384 If the impaired controller is Then… displaying… Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 385 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 386 that prevent the healing operation. 4. Verify that the operation has been completed by using the metrocluster operation show command. controller_A_1::> metrocluster operation show Operation: heal-aggregates State: successful Start Time: 7/25/2016 18:45:55 End Time: 7/25/2016 18:45:56 Errors: - 5.
Page 387 Step 2: Open the controller module To access components inside the controller, you must first remove the controller module from the system and then remove the cover on the controller module. 1. If you are not already grounded, properly ground yourself. 2.
Page 388 Step 3: Replace the DIMMs To replace the DIMMs, locate them inside the controller and follow the specific sequence of steps. 1. Check the NVMEM LED on the controller module. You must perform a clean system shutdown before replacing system components to avoid losing unwritten data in the nonvolatile memory (NVMEM).
Page 389 NVMEM battery lock tab NVMEM battery b. Locate the battery plug and squeeze the clip on the face of the battery plug to release the plug from the socket, and then unplug the battery cable from the socket. c. Wait a few seconds, and then plug the battery back into the socket. 4.
Page 390 Carefully hold the DIMM by the edges to avoid pressure on the components on the DIMM circuit board. The number and placement of system DIMMs depends on the model of your system. The following illustration shows the location of system DIMMs: 8.
Page 391 11. Locate the NVMEM battery plug socket, and then squeeze the clip on the face of the battery cable plug to insert it into the socket. Make sure that the plug locks down onto the controller module. 12. Close the controller module cover. Step 4: Reinstall the controller After you replace a component within the controller module, you must reinstall the controller module in the system chassis and boot it to a state where you can run diagnostic tests on the replaced component.
Page 392 b. After the controller boots to Maintenance mode, halt the controller: halt After you issue the command, you should wait until the system stops at the LOADER prompt. During the boot process, you can safely respond to prompts: ▪ A prompt warning that when entering Maintenance mode in an HA configuration, you must ensure that the healthy controller remains down.
Page 393 If your controller is in… Then… A two-node MetroCluster Proceed to the next step. The MetroCluster switchback procedure is configuration done in the next task in the replacement process. A stand-alone configuration Proceed to the next step. No action is required. You have completed system-level diagnostics.
Page 394 This task only applies to two-node MetroCluster configurations. Steps 1. Verify that all nodes are in the enabled state: metrocluster node show cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A ...
Page 395 6. Reestablish any SnapMirror or SnapVault configurations. Step 7: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 396 10. Align the bezel with the ball studs, and then gently push the bezel onto the ball studs. 11. After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 397 If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller;...
Page 398 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 399 3. Resynchronize the data aggregates by running the metrocluster heal -phase aggregates command from the surviving cluster. controller_A_1::> metrocluster heal -phase aggregates [Job 130] Job succeeded: Heal Aggregates is successful. If the healing is vetoed, you have the option of reissuing the command with the metrocluster heal parameter.
Page 400 mcc1A::> metrocluster operation show Operation: heal-root-aggregates State: successful Start Time: 7/29/2016 20:54:41 End Time: 7/29/2016 20:54:42 Errors: - 8. On the impaired controller module, disconnect the power supplies. Step 2: Open the controller module To access components inside the controller, you must first remove the controller module from the system and then remove the cover on the controller module.
Page 401 Thumbscrew Cam handle 5. Pull the cam handle downward and begin to slide the controller module out of the chassis. Make sure that you support the bottom of the controller module as you slide it out of the chassis. Step 3: Replace the NVMEM battery To replace the NVMEM battery in your system, you must remove the failed NVMEM battery from the system and replace it with a new NVMEM battery.
Page 402 Battery lock tab NVMEM battery pack 3. Grasp the battery and press the blue locking tab marked PUSH, and then lift the battery out of the holder and controller module. 4. Remove the replacement battery from its package. 5. Align the tab or tabs on the battery holder with the notches in the controller module side, and then gently push down on the battery housing until the battery housing clicks into place.
Page 403 1. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system. Do not completely insert the controller module in the chassis until instructed to do so. 2.
Page 404 During the boot process, you can safely respond to the prompts until the Maintenance mode prompt (*>) appears. 3. Run diagnostics on the NVMEM memory: sldiag device run -dev nvmem 4. Verify that no hardware problems resulted from the replacement of the NVMEM battery: sldiag device status -dev nvmem -long -state failed System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of...
Page 405 If your controller is in… Then… Resulted in some test failures Determine the cause of the problem: a. Exit Maintenance mode: halt After you issue the command, wait until the system stops at the LOADER prompt. b. Turn off or leave on the power supplies, depending on how many controller modules are in the chassis: ◦...
Page 406 cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B controller_B_1 configured enabled waiting for switchback recovery 2 entries were displayed. 2. Verify that resynchronization is complete on all SVMs: metrocluster vserver show 3.
Page 407 Step 7: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800-44- 638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 408 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 409 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 410 5. Check the state of the aggregates by using the storage aggregate show command. controller_A_1::> storage aggregate show Aggregate Size Available Used% State #Vols Nodes RAID Status --------- -------- --------- ----- ------- ------ ---------------- ------------ aggr_b2 227.1GB 227.1GB 0% online 0 mcc1-a2 raid_dp, mirrored, normal...
Page 411 4. Loosen the thumbscrew on the cam handle on the controller module. Thumbscrew Cam handle 5. Pull the cam handle downward and begin to slide the controller module out of the chassis. Make sure that you support the bottom of the controller module as you slide it out of the chassis. Step 3: Replace a PCIe card To replace a PCIe card, locate it within the controller and follow the specific sequence of steps.
Page 412 Side panel PCIe card 3. Remove the PCIe card from the controller module and set it aside. 4. Install the replacement 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.
Page 413 Do not completely insert the controller module in the chassis until instructed to do so. 2. Recable the system, as needed. If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber optic cables. 3.
Page 414 5. Return the controller to normal operation: If your system is in… Issue this command from the partner’s console… An HA pair storage failover giveback -ofnode impaired_node_name A two-node MetroCluster Proceed to the next step. The MetroCluster switchback procedure is done in configuration the next task in the replacement process.
Page 415 6. Reestablish any SnapMirror or SnapVault configurations. Step 6: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 416 3. Turn off the power supply and disconnect the power cables: a. Turn off the power switch on the power supply. b. Open the power cable retainer, and then unplug the power cable from the power supply. c. Unplug the power cable from the power source. 4.
Page 417 The power supply LEDs are lit when the power supply comes online. 2. After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 418 • All other components in the system must be functioning properly; if not, you must contact technical support. Step 1: Shut down the impaired controller You can shut down or take over the impaired controller using different procedures, depending on the storage system hardware configuration.
Page 419 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 420 If the impaired controller… Then… Has automatically switched over Proceed to the next step. Has not automatically switched Perform a planned switchover operation from the healthy controller: over metrocluster switchover Has not automatically switched Review the veto messages and, if possible, resolve the issue and try over, you attempted switchover again.
Page 421 mcc1A::> metrocluster heal -phase root-aggregates [Job 137] Job succeeded: Heal Root Aggregates is successful If the healing is vetoed, you have the option of reissuing the command with the metrocluster heal -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation.
Page 422 Thumbscrew Cam handle 5. Pull the cam handle downward and begin to slide the controller module out of the chassis. Make sure that you support the bottom of the controller module as you slide it out of the chassis. Step 3: Replace the RTC Battery To replace the RTC battery, locate them inside the controller and follow the specific sequence of steps.
Page 423 3. Gently push the battery away from the holder, rotate it away from the holder, and then lift it out of the holder. Note the polarity of the battery as you remove it from the holder. The battery is marked with a plus sign and must be positioned in the holder correctly.
Page 424 2. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system. Do not completely insert the controller module in the chassis until instructed to do so. 3.
Page 425 Steps 1. Verify that all nodes are in the state: enabled metrocluster node show cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B ...
Page 426: Fas8300 And Fas8700 System Documentation
6. Reestablish any SnapMirror or SnapVault configurations. Step 6: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 427 Video two of two: Performing end-to-end software configuration The following video shows end-to-end software configuration for systems running ONTAP 9.2 and later. NetApp video: Software configuration for vSphere NAS datastores for FAS/AFF systems running ONTAP 9.2 Detailed guide - FAS8300 and FAS8700 This guide gives detailed step-by-step instructions for installing a typical NetApp system.
Page 428 Power cables Not applicable Powering up the system 4. Review the NetApp ONTAP Confiuration Guide and collect the required information listed in that guide. ONTAP Configuration Guide Step 2: Install the hardware You need to install your system in a 4-post rack or NetApp system cabinet, as applicable.
Page 429 Steps 1. Install the rail kits, as needed. 2. Install and secure your system using the instructions included with the rail kit. You need to be aware of the safety concerns associated with the weight of the system. 3. Attach cable management devices (as shown). 4.
Page 430 As you insert the connector, you should feel it click into place; if you do not feel it click, remove it, turn it around and try again. Steps 1. Use the animation or illustration to complete the cabling between the controllers and to the switches: Two-node switchless cluster cabling 2.
Page 431 As you insert the connector, you should feel it click into place; if you do not feel it click, remove it, turn it around and try again. Steps 1. Use the animation or illustration to complete the cabling between the controllers and to the switches: Switched cluster cabling 2.
Page 432 Be sure to check the illustration arrow for the proper cable connector pull-tab orientation. The cable pull-tab for the DS224-C are down. As you insert the connector, you should feel it click into place; if you do not feel it click, remove it, turn it around and try again.
Page 433 2. Go to Step 5: Complete system setup and configuration to complete system setup and configuration. Step 5: Complete system setup and configuration You can complete the system setup and configuration using cluster discovery with only a connection to the switch and laptop, or by connecting directly to a controller in the system and then connecting to the management switch.
Page 434 Double-click either ONTAP icon and accept any certificates displayed on your screen. XXXXX is the system serial number for the target node. System Manager opens. 6. Use System Manager guided setup to configure your system using the data you collected in the NetApp ONTAP Configuration Guide. ONTAP Configuration Guide 7.
Page 435 Register your system. NetApp Product Registration c. Download Active IQ Config Advisor. NetApp Downloads: Config Advisor 8. Verify the health of your system by running Config Advisor. 9. After you have completed the initial configuration, go to the ONTAP & ONTAP System Manager Documentation Resources page for information about configuring additional features in ONTAP.
Page 436 Point your browser to the node management IP address. The format for the address is https://x.x.x.x. b. Configure the system using the data you collected in the NetApp ONTAP Configuration guide. ONTAP Configuration Guide 6. Set up your account and download Active IQ Config Advisor: a.
Page 437 If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller; see the NetApp Encryption overview with the CLI. Steps 1.
Page 438 Check NVE or NSE on systems running ONTAP 9.6 and later Before shutting down the impaired controller, you need to verify whether the system has either NetApp Volume Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.
Page 439 Restore the external key management authentication keys to all nodes in the cluster: security key-manager external restore If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column equals for all authentication keys: Restored security key- manager key-query c.
Page 440 Key Manager external Restored yes: a. Enter the onboard security key-manager sync command: security key-manager external sync If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column equals for all authentication keys: Restored security key- manager key-query c.
Page 441 Shut down the impaired controller - AFF FAS8300 and FAS8700 Option 1: Most systems After completing the NVE or NSE tasks, you need to complete the shutdown of the impaired controller. Steps a. Take the impaired controller to the LOADER prompt: If the impaired controller Then…...
Page 442 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 443 If the impaired controller… Then… Has not automatically switched Review the veto messages and, if possible, resolve the issue and try over, you attempted switchover again. If you are unable to resolve the issue, contact technical support. with the metrocluster command, and the switchover switchover was vetoed...
Page 444 If the healing is vetoed, you have the option of reissuing the command with the metrocluster heal -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation. 7. Verify that the heal operation is complete by using the command on metrocluster operation show the destination cluster:...
Page 445 NetApp Support Site. You must log into the NetApp Support Site to display the Statement of Volatility for your system. You can use the following animation, illustrations, or the written steps to replace the boot media.
Page 446 Locking tabs Slide air duct toward back of controller Rotate air duct up a. Press the locking tabs on the sides of the air duct in toward the middle of the controller module. b. Slide the air duct toward the back of the controller module, and then rotate it upward to its completely open position.
Page 447 Press blue button Rotate boot media up and remove from socket a. Press the blue button at the end of the boot media until the lip on the boot media clears the blue button. b. Rotate the boot media up and gently pull the boot media out of the socket. 3.
Page 448 • A copy of the same image version of ONTAP as what the impaired controller was running. You can download the appropriate image from the Downloads section on the NetApp Support Site ◦ If NVE is enabled, download the image with NetApp Volume Encryption, as indicated in the download button.
Page 449 7. Complete the installation of the controller module: a. Plug the power cord into the power supply, reinstall the power cable locking collar, and then connect the power supply to the power source. b. Firmly push the controller module into the chassis until it meets the midplane and is fully seated. The locking latches rise when the controller module is fully seated.
Page 450 3. Restore the file system: If your system has… Then… A network connection a. Press when prompted to restore the backup configuration. b. Set the healthy controller to advanced privilege level: -privilege advanced c. Run the restore backup command: system node restore- backup -node local -target-address impaired_node_IP_address d.
Page 451 7. Connect the console cable to the partner controller. 8. Give back the controller using the command. storage failover giveback -fromnode local 9. At the cluster prompt, check the logical interfaces with the command. net int -is-home false If any interfaces are listed as "false", revert those interfaces back to their home port using the net int command.
Page 452 configuration to its normal operating state, with the sync-source storage virtual machines (SVMs) on the formerly impaired site now active and serving data from the local disk pools. This task only applies to two-node MetroCluster configurations. Steps 1. Verify that all nodes are in the state: enabled metrocluster node show...
Page 453 Restore OKM, NSE, and NVE as needed - AFF fas8300 and FAS8700 Once environment variables are checked, you must complete steps specific to systems that have Onboard Key Manager (OKM), NetApp Storage Encryption (NSE) or NetApp Volume Encryption (NVE) enabled.
Page 454 6. When prompted to enter the backup data, paste the backup data you captured at the beginning of this procedure, when asked. Paste the output of security key-manager backup show security command key-manager onboard show-backup The data is output from either security key-manager backup show security command.
Page 455 show-giveback` commands. `storage failover Only the CFO aggregates (root aggregate and CFO style data aggregates) will be shown. 12. Move the console cable to the target controller. a. If you are running ONTAP 9.6 or later, run the security key-manager onboard sync: b.
Page 456 Waiting for giveback… a. Log into the partner controller. b. Confirm the target controller is ready for giveback with the storage failover show command. 4. Move the console cable to the partner controller and give back the target controller storage using the storage failover giveback -fromnode local -only-cfo-aggregates true local command.
Page 457 Return the failed part to NetApp - AFF fas8300 and FAS8700 After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp...
Page 458 The output should display the caching module status as erased. 2. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message: system node autosupport invoke -node * -type all -message MAINT=_number_of_hours_down_h The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*>...
Page 459 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 460 controller_A_1::> metrocluster heal -phase aggregates [Job 130] Job succeeded: Heal Aggregates is successful. If the healing is vetoed, you have the option of reissuing the command with the metrocluster heal -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation.
Page 461 mcc1A::> metrocluster operation show Operation: heal-root-aggregates State: successful Start Time: 7/29/2016 20:54:41 End Time: 7/29/2016 20:54:42 Errors: - 8. On the impaired controller module, disconnect the power supplies. Step 2: Remove the controller module To access components inside the controller module, you must remove the controller module from the chassis.
Page 462 NetApp Support Site. You must log into the NetApp Support Site to display the Statement of Volatility for your system. • All other components in the storage system must be functioning properly; if not, you must contact technical support.
Page 463 Steps 1. If you are not already grounded, properly ground yourself. 2. Open the air duct: a. Press the locking tabs on the sides of the air duct in toward the middle of the controller module. b. Slide the air duct toward the back of the controller module, and then rotate it upward to its completely open position.
Page 464 Step 4: Install the controller module After you have replaced the component in the controller module, you must reinstall the controller module into the chassis, and then boot it to Maintenance mode. You can use the following animation, illustration, or the written steps to install the controller module in the chassis.
Page 465 that they clear the locking pins, gently push the controller all the way in, and then lower the locking latches into the locked position. The controller module begins to boot as soon as it is fully seated in the chassis. Be prepared to interrupt the boot process.
Page 466 If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber optic cables. 2. Return the controller to normal operation by giving back its storage: storage failover giveback -ofnode impaired_node_name 3. If automatic giveback was disabled, reenable it: storage failover modify -node local -auto -giveback true Step 7: Switch back aggregates in a two-node MetroCluster configuration...
Page 467 6. Reestablish any SnapMirror or SnapVault configurations. Step 8: Complete the replacement process After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 468 • If you have a cluster with more than two controllers, it must be in quorum. If the cluster is not in quorum or a healthy controller shows for eligibility and health, you must correct the issue before shutting down false the impaired controller;...
Page 469 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 470 controller_A_1::> metrocluster operation show Operation: heal-aggregates State: successful Start Time: 7/25/2016 18:45:55 End Time: 7/25/2016 18:45:56 Errors: - 5. Check the state of the aggregates by using the command. storage aggregate show controller_A_1::> storage aggregate show Aggregate Size Available Used% State #Vols...
Page 471 system cabinet with the new chassis of the same model as the impaired chassis. Step 1: Remove the controller modules To replace the chassis, you must remove the controller modules from the old chassis. Steps 1. If you are not already grounded, properly ground yourself. 2.
Page 472 8. Push firmly on the fan module cam handle so that it is seated all the way into the chassis. The cam handle raises slightly when the fan module is completely seated. 9. Swing the cam handle up to its closed position, making sure that the cam handle release latch clicks into the locked position.
Page 473 Complete the restoration and replacement process - FAS8300 and FAS8700 You must verify the HA state of the chassis, run diagnostics, and return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Step 1: Verify and set the HA state of the chassis You must verify the HA state of the chassis, and, if necessary, update the state to match your system configuration.
Page 474 b. Confirm that the setting has changed: ha-config show 3. If you have not already done so, recable the rest of your system. Step 2: Run diagnostics After you have replaced a component in your system, you should run diagnostic tests on that component. Your system must be at the LOADER prompt to start diagnostics.
Page 475 cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B controller_B_1 configured enabled waiting for switchback recovery 2 entries were displayed. 2. Verify that resynchronization is complete on all SVMs: metrocluster vserver show 3.
Page 476 Step 4: Complete the replacement process After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800-44- 638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 477 If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller;...
Page 478 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 479 If the impaired controller… Then… Has not automatically switched Review the veto messages and, if possible, resolve the issue and try over, you attempted switchover again. If you are unable to resolve the issue, contact technical support. with the metrocluster command, and the switchover switchover was vetoed...
Page 480 If the healing is vetoed, you have the option of reissuing the command with the metrocluster heal -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation. 7. Verify that the heal operation is complete by using the command on metrocluster operation show the destination cluster:...
Page 481 The controller module moves slightly out of the chassis. 6. Slide the controller module out of the chassis. Make sure that you support the bottom of the controller module as you slide it out of the chassis. 7. Place the controller module on a stable, flat surface. 8.
Page 482 a. Press the locking tabs on the sides of the air duct in toward the middle of the controller module. b. Slide the air duct toward the back of the controller module, and then rotate it upward to its completely open position.
Page 483 1. Remove the power supply: a. Rotate the cam handle so that it can be used to pull the power supply out of the chassis. b. Press the blue locking tab to release the power supply from the chassis. c. Using both hands, pull the power supply out of the chassis, and then set it aside. 2.
Page 484 a. Press the locking tabs on the sides of the air duct in toward the middle of the controller module. b. Slide the air duct toward the back of the controller module, and then rotate it upward to its completely open position.
Page 485 controller module to the replacement controller module. Moving the boot media 1. Locate and remove the boot media from the controller module: a. Press the blue button at the end of the boot media until the lip on the boot media clears the blue button. b.
Page 486 You can use the following animations, illustrations. or the written steps to move the PCIe risers and mezzanine card from the impaired controller module to the replacement controller module. Moving PCIe riser 1 and 2 (left and middle risers): Moving PCI risers 1 and 2 Moving the mezzanine card and riser 3 (right riser): Moving the mezzanine card and riser 3...
Page 487 1. Move PCIe risers one and two from the impaired controller module to the replacement controller module: a. Remove any SFP or QSFP modules that might be in the PCIe cards. b. Rotate the riser locking latch on the left side of the riser up and toward air duct. The riser raises up slightly from the controller module.
Page 488 e. Install the mezzanine in the replacement controller and secure it with the thumbscrews. f. Install the third riser in the replacement controller module. Step 6: Move caching modules You must move the caching modules from the impaired controller modules to the replacement controller module when replacing a controller module.
Page 489 e. Placing your finger at the end of the caching module by the blue button, firmly push down on the caching module end, and then lift the locking button to lock the caching module in place. Step 7: Move the DIMMs You need to locate the DIMMs, and then move them from the impaired controller module to the replacement controller module.
Page 490 2. Note the orientation of the DIMM in the socket so that you can insert the DIMM in the replacement controller module in the proper orientation. 3. Verify that the NVDIMM battery is not plugged into the new controller module. 4.
Page 491 1. If you have not already done so, close the air duct. 2. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system. Do not completely insert the controller module in the chassis until instructed to do so. 3.
Page 492 f. At the LOADER prompt, enter to reinitialize the PCIe cards and other components. g. Interrupt the boot process and boot to the LOADER prompt by pressing Ctrl-C. If your system stops at the boot menu, select the option to boot to LOADER. Restore and verify the system configuration - FAS8300 and FAS8700 After completing the hardware replacement and booting to Maintenance mode, you verify the low-level system configuration of the replacement controller and reconfigure system...
Page 493 2. If the displayed system state of the controller module does not match your system configuration, set the state for the controller module: ha-config modify controller ha-state The value for can be one of the following: HA-state ◦ ◦ ◦ mcc-2n ◦...
Page 494 Recable the system and reassign disks - FAS8300 and FAS8700 You must complete a series of tasks before restoring your system to full operation. Step 1: Recable the system After running diagnostics, you must recable the controller module’s storage and network connections. Steps 1.
Page 495 node1> `storage failover show` Takeover Node Partner Possible State Description ------------ ------------ -------- ------------------------------------- node1 node2 false System ID changed on partner (Old: 151759755, New: 151759706), In takeover node2 node1 Waiting for giveback (HA mailboxes) 4. From the healthy controller, verify that any coredumps are saved: a.
Page 496 node1> `storage disk show -ownership` Disk Aggregate Home Owner DR Home Home ID Owner ID DR Home ID Reserver Pool ----- ------ ----- ------ -------- ------- ------- ------- --------- 1.0.0 aggr0_1 node1 node1 1873775277 1873775277 1873775277 Pool0 1.0.1 aggr0_1 node1 node1 1873775277 1873775277 1873775277 Pool0 Option 2: Manually reassign the system ID on systems in a two-node MetroCluster configuration...
Page 497 Local System ID: 118065481 4. Reassign disk ownership (for FAS systems) or LUN ownership (for FlexArray systems), by using the system ID information obtained from the disk show command: disk reassign -s old system ID In the case of the preceding example, the command is:...
Page 498 Display the results of the MetroCluster check: metrocluster check show e. Run Config Advisor. Go to the Config Advisor page on the NetApp Support Site at support.netapp.com/NOW/download/tools/config_advisor/. After running Config Advisor, review the tool’s output and follow the recommendations in the output to address any issues discovered.
Page 499 -privilege admin Complete system restoration - FAS8300 and FAS8700 To restore your system to full operation, you must restore the NetApp Storage Encryption configuration (if necessary), and install licenses for the new controller, and return the failed part to NetApp, as described in the RMA instructions shipped with the kit.
Page 500 If any LIFs are listed as false, revert them to their home ports: network interface revert 2. Register the system serial number with NetApp Support. ◦ If AutoSupport is enabled, send an AutoSupport message to register the serial number. ◦ If AutoSupport is not enabled, call NetApp Support to register the serial number.
Page 501 cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B controller_B_1 configured enabled waiting for switchback recovery 2 entries were displayed. 2. Verify that resynchronization is complete on all SVMs: metrocluster vserver show 3.
Page 502 Step 5: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800-44- 638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 503 If the impaired controller is Then… displaying… Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 504 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 505 parameter. If you use this optional parameter, the system overrides any soft vetoes -override-vetoes that prevent the healing operation. 4. Verify that the operation has been completed by using the metrocluster operation show command. controller_A_1::> metrocluster operation show Operation: heal-aggregates ...
Page 506 Step 2: Remove the controller module To access components inside the controller module, you must remove the controller module from the chassis. You can use the following animation, illustration, or the written steps to remove the controller module from the chassis.
Page 507 Step 3: Replace system DIMMs Replacing a system DIMM involves identifying the target DIMM through the associated error message, locating the target DIMM using the FRU map on the air duct or the lit LED on the motherboard, and then replacing the DIMM. You can use the following animation, illustration, or the written steps to replace a system DIMM.
Page 508 • If you have a FAS8700 system, the system DIMMs are located in slots 2, 4, 7, 9, 13, 15, 18, and 20. • The NVDIMM is located in slot 11. Steps 1. Open the air duct: a. Press the locking tabs on the sides of the air duct in toward the middle of the controller module. b.
Page 509 Steps 1. If you have not already done so, close the air duct. 2. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system. Do not completely insert the controller module in the chassis until instructed to do so. 3.
Page 510 If your system stops at the boot menu, select the option to boot to LOADER. f. At the LOADER prompt, enter to reinitialize the PCIe cards and other components. g. Interrupt the boot process and boot to the LOADER prompt by pressing Ctrl-C. If your system stops at the boot menu, select the option to boot to LOADER.
Page 511 Step 7: Switch back aggregates in a two-node MetroCluster configuration After you have completed the FRU replacement in a two-node MetroCluster configuration, you can perform the MetroCluster switchback operation. This returns the configuration to its normal operating state, with the sync-source storage virtual machines (SVMs) on the formerly impaired site now active and serving data from the local disk pools.
Page 512 6. Reestablish any SnapMirror or SnapVault configurations. Step 8: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 513 Steps 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 ball studs on the chassis frame. 3.
Page 514 10. Align the bezel with the ball studs, and then gently push the bezel onto the ball studs. 11. After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 515 If the impaired controller is Then… displaying… The LOADER prompt Go to Remove controller module. Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name...
Page 516 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 517 parameter. If you use this optional parameter, the system overrides any soft vetoes -override-vetoes that prevent the healing operation. 4. Verify that the operation has been completed by using the metrocluster operation show command. controller_A_1::> metrocluster operation show Operation: heal-aggregates ...
Page 518 Step 2: Remove the controller module To access components inside the controller module, you must remove the controller module from the chassis. You can use the following , illustration, or the written steps to remove the controller module from the chassis. Removing the controller module Steps 1.
Page 519 Statement of Volatility on the NetApp Support Site. You must log into the NetApp Support Site to display the Statement of Volatility for your system. You can use the following animation, illustration, or the written steps to replace the NVDIMM.
Page 520 Steps 1. Open the air duct and then locate the NVDIMM in slot 11 on your controller module. The NVDIMM looks significantly different than system DIMMs. 2. Eject the NVDIMM from its slot by slowly pushing apart the two NVDIMM ejector tabs on either side of the NVDIMM, and then slide the NVDIMM out of the socket and set it aside.
Page 521 4. Locate the slot where you are installing the NVDIMM. 5. Insert the NVDIMM squarely into the slot. The NVDIMM fits tightly in the slot, but should go in easily. If not, realign the NVDIMM with the slot and reinsert it. Visually inspect the NVDIMM to verify that it is evenly aligned and fully inserted into the slot.
Page 522 You will connect the rest of the cables to the controller module later in this procedure. 4. Complete the installation of the controller module: a. Plug the power cord into the power supply, reinstall the power cable locking collar, and then connect the power supply to the power source.
Page 523 5. Select NVDIMM Test from the displayed menu. 6. Proceed based on the result of the preceding step: ◦ If the test failed, correct the failure, and then rerun the test. ◦ If the test reported no failures, select from the menu to reboot the system. Reboot Step 6: Restore the controller module to operation after running diagnostics After completing diagnostics, you must recable the system, give back the controller...
Page 524 cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B controller_B_1 configured enabled waiting for switchback recovery 2 entries were displayed. 2. Verify that resynchronization is complete on all SVMs: metrocluster vserver show 3.
Page 525 Step 8: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888- 463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 526 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 527 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 528 controller_A_1::> metrocluster operation show Operation: heal-aggregates State: successful Start Time: 7/25/2016 18:45:55 End Time: 7/25/2016 18:45:56 Errors: - 5. Check the state of the aggregates by using the command. storage aggregate show controller_A_1::> storage aggregate show Aggregate Size Available Used% State #Vols...
Page 529 You can use the following animation, illustration, or the written steps to remove the controller module from the chassis. Removing the controller module Steps 1. If you are not already grounded, properly ground yourself. 2. Release the power cable retainers, and then unplug the cables from the power supplies. 3.
Page 530 inside the controller module to locate the NVDIMM battery. The NVDIMM LED blinks while destaging contents when you halt the system. After the destage is complete, the LED turns off. You can use the following animation, illustration, or the written steps to replace the NVDIMM battery. Replacing the NVDIMM battery Steps 1.
Page 531 locks into place. 7. Plug the battery plug back into the controller module, and then close the air duct. Step 4: Install the controller module After you have replaced the component in the controller module, you must reinstall the controller module into the chassis, and then boot it to Maintenance mode. You can use the following animation, illustration, or the written steps to install the controller module in the chassis.
Page 532 Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors. c. Fully seat the controller module in the chassis by rotating the locking latches upward, tilting them so that they clear the locking pins, gently push the controller all the way in, and then lower the locking latches into the locked position.
Page 533 Steps 1. Recable the system, as needed. If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber optic cables. 2. Return the controller to normal operation by giving back its storage: storage failover giveback -ofnode impaired_node_name 3.
Page 534 6. Reestablish any SnapMirror or SnapVault configurations. Step 8: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 535 About this task If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller;...
Page 536 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 537 If the impaired controller… Then… Has not automatically switched Review the veto messages and, if possible, resolve the issue and try over, you attempted switchover again. If you are unable to resolve the issue, contact technical support. with the metrocluster command, and the switchover switchover was vetoed...
Page 538 If the healing is vetoed, you have the option of reissuing the command with the metrocluster heal -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation. 7. Verify that the heal operation is complete by using the command on metrocluster operation show the destination cluster:...
Page 539 2. Release the power cable retainers, and then unplug the cables from the power supplies. 3. Loosen the hook and loop strap binding the cables to the cable management device, and then unplug the system cables and SFPs (if needed) from the controller module, keeping track of where the cables were connected.
Page 540 Steps 1. Remove the riser containing the card to be replaced: a. Open the air duct by pressing the locking tabs on the sides of the air duct, slide it toward the back of the controller module, and then rotate it to its completely open position. b.
Page 541 Steps 1. Remove riser number 3 (slots 4 and 5): a. Open the air duct by pressing the locking tabs on the sides of the air duct, slide it toward the back of the controller module, and then rotate it to its completely open position. b.
Page 542 b. Push the riser squarely into the socket on the motherboard. c. Rotate the latch down flush with the sheet metal on the riser. Step 5: Install the controller module After you have replaced the component in the controller module, you must reinstall the controller module into the chassis, and then boot it to Maintenance mode.
Page 543 Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors. The controller module begins to boot as soon as it is fully seated in the chassis. Be prepared to interrupt the boot process. c.
Page 544 cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B controller_B_1 configured enabled waiting for switchback recovery 2 entries were displayed. 2. Verify that resynchronization is complete on all SVMs: metrocluster vserver show 3.
Page 545 -node local -auto -giveback true Step 8: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp...
Page 546 Steps 1. If you are not already grounded, properly ground yourself. 2. Identify the power supply you want to replace, based on console error messages or through the LEDs on the power supplies. 3. Disconnect the power supply: a. Open the power cable retainer, and then unplug the power cable from the power supply. b.
Page 547 Once power is restored to the power supply, the status LED should be green. 8. After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 548 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 549 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 550 controller_A_1::> metrocluster operation show Operation: heal-aggregates State: successful Start Time: 7/25/2016 18:45:55 End Time: 7/25/2016 18:45:56 Errors: - 5. Check the state of the aggregates by using the command. storage aggregate show controller_A_1::> storage aggregate show Aggregate Size Available Used% State #Vols...
Page 551 You can use the following animation, illustration, or the written steps to remove the controller module from the chassis. Removing the controller module Steps 1. If you are not already grounded, properly ground yourself. 2. Release the power cable retainers, and then unplug the cables from the power supplies. 3.
Page 552 of the RTC battery. You can use the following animation, illustration, or the written steps to replace the RTC battery. Replacing the RTC battery Steps 1. If you are not already grounded, properly ground yourself. 2. Open the air duct: a.
Page 553 c. Remove the replacement battery from the antistatic shipping bag. d. Note the polarity of the RTC battery, and then insert it into the holder by tilting the battery at an angle and pushing down. 4. Visually inspect the battery to make sure that it is completely installed into the holder and that the polarity is correct.
Page 554 a. Using the locking latches, firmly push the controller module into the chassis until it meets the midplane and is fully seated. The locking latches rise when the controller module is fully seated. Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.
Page 555 cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B controller_B_1 configured enabled waiting for switchback recovery 2 entries were displayed. 2. Verify that resynchronization is complete on all SVMs: metrocluster vserver show 3.
Page 556: Aff A700 And Fas9000 System Documentation
Step 6: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888- 463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 557 Video two of two: Performing end-to-end software configuration The following video shows end-to-end software configuration for systems running ONTAP 9.2 and later. NetApp video: Software configuration for vSphere NAS datastores for FAS/AFF systems running ONTAP 9.2 Detailed guide - AFF A700 and FAS9000 This guide gives detailed step-by-step instructions for installing a typical NetApp system.
Page 558 Power cables Not applicable Powering up the system 4. Review the NetApp ONTAP Confiuration Guide and collect the required information listed in that guide. ONTAP Configuration Guide Step 2: Install the hardware You need to install your system in a 4-post rack or NetApp system cabinet, as applicable.
Page 559 Steps 1. Install the rail kits, as needed. 2. Install and secure your system using the instructions included with the rail kit. You need to be aware of the safety concerns associated with the weight of the system. The label on the left indicates an empty chassis, while the label on the right indicates a fully- populated system.
Page 560 As you insert the connector, you should feel it click into place; if you do not feel it click, remove it, turn it around and try again. Steps 1. Use the animation or illustration to complete the cabling between the controllers and to the switches: Cabling a two-node switchless cluster 1.
Page 561 Step 4: Cable controllers to drive shelves You can cable your new system to DS212C, DS224C, or NS224 shelves, depending on if it is an AFF or FAS system. Option 1: Cable the controllers to DS212C or DS224C drive shelves You must cable the shelf-to-shelf connections, and then cable both controllers to the DS212C or DS224C drive shelves.
Page 562 Steps 1. Use the following animations or illustrations to cable your drive shelves to your controllers. The examples use DS224C shelves. Cabling is similar with other supported SAS drive shelves. ◦ Cabling SAS shelves in FAS9000, AFF A700, and ASA AFF A700, ONTAP 9.7 and earlier: Cabling SAS storage - ONTAP 9.7 and earlier...
Page 563 ◦ Cabling SAS shelves in FAS9000, AFF A700, and ASA AFF A700, ONTAP 9.8 and later: Cabling SAS storage - ONTAP 9.8 and later...
Page 564 If you have more than one drive shelf stack, see the Installation and Cabling Guide for your drive shelf type. Install and cable shelves for a new system installation - shelves with IOM12 modules...
Page 565 2. Go to Step 5: Complete system setup and configuration to complete system setup and configuration. Option 2: Cable the controllers to a single NS224 drive shelf in AFF A700 and ASA AFF A700 systems running ONTAP 9.8 and later only You must cable each controller to the NSM modules on the NS224 drive shelf on an AFF A700 or ASA AFF A700 running system ONTAP 9.8 or later.
Page 566 • The systems must have at least one X91148A module installed in slots 3 and/or 7 for each controller. The animation or illustrations show this module installed in both slots 3 and 7. • Be sure to check the illustration arrow for the proper cable connector pull-tab orientation. The cable pull-tab for the storage modules are up, while the pull tabs on the shelves are down.
Page 567 2. Go to Step 5: Complete system setup and configuration to complete system setup and configuration. Option 3: Cable the controllers to two NS224 drive shelves in AFF A700 and ASA AFF A700 systems running ONTAP 9.8 and later only You must cable each controller to the NSM modules on the NS224 drive shelves on an AFF A700 or ASA AFF A700 running system ONTAP 9.8 or later.
Page 568 As you insert the connector, you should feel it click into place; if you do not feel it click, remove it, turn it around and try again. Steps 1. Use the following animation or illustrations to cable your controllers to two NS224 drive shelves. Cabling two NS224 shelves - ONTAP 9.8 and later...
Page 569 2. Go to Step 5: Complete system setup and configuration to complete system setup and configuration. Step 5: Complete system setup and configuration You can complete the system setup and configuration using cluster discovery with only a connection to the switch and laptop, or by connecting directly to a controller in the system and then connecting to the management switch.
Page 570 Double-click either ONTAP icon and accept any certificates displayed on your screen. XXXXX is the system serial number for the target node. System Manager opens. 7. Use System Manager guided setup to configure your system using the data you collected in the NetApp...
Page 571 Register your system. NetApp Product Registration c. Download Active IQ Config Advisor. NetApp Downloads: Config Advisor 9. Verify the health of your system by running Config Advisor. 10. After you have completed the initial configuration, go to the ONTAP & ONTAP System Manager Documentation Resources page for information about configuring additional features in ONTAP.
Page 572 Point your browser to the node management IP address. The format for the address is https://x.x.x.x. b. Configure the system using the data you collected in the NetApp ONTAP Configuration guide. ONTAP Configuration Guide 7. Set up your account and download Active IQ Config Advisor: a.
Page 573 If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller; see the NetApp Encryption overview with the CLI. Steps 1.
Page 574 Option 1: Check NVE or NSE on systems running ONTAP 9.5 and earlier Before shutting down the impaired controller, you need to check whether the system has either NetApp Volume Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.
Page 575 Restored unavailable: a. Retrieve and restore all authentication keys and associated key IDs: security key-manager restore -address * If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the Restored column displays for all authentication keys and that all key managers...
Page 576 Retrieve and restore all authentication keys and associated key IDs: security key-manager restore -address * If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column displays for all authentication keys and that all key managers...
Page 577 Option 2: Check NVE or NSE on systems running ONTAP 9.6 and later Before shutting down the impaired controller, you need to verify whether the system has either NetApp Volume Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.
Page 578 Restored yes: a. Restore the external key management authentication keys to all nodes in the cluster: security key-manager external restore If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column equals for all authentication keys: Restored...
Page 579 Key Manager external Restored yes: a. Enter the onboard security key-manager sync command: security key-manager external sync If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column equals for all authentication keys: Restored security key- manager key-query c.
Page 580 c. Verify that the Key Manager type shows onboard, and then manually back up the OKM information. d. Go to advanced privilege mode and enter when prompted to continue: set -priv advanced e. Enter the command to display the key management backup information: security key- manager onboard show-backup f.
Page 581 • If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller;...
Page 582 1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message: system node autosupport invoke -node * -type all -message MAINT=number_of_hours_downh The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*> system node autosupport invoke -node * -type all -message MAINT=2h 2.
Page 583 Cam handle release button Cam handle 4. Rotate the cam handle so that it completely disengages the controller module from the chassis, and then slide the controller module out of the chassis. Make sure that you support the bottom of the controller module as you slide it out of the chassis. 5.
Page 584 Controller module cover locking button Step 2: Replace the boot media Locate the boot media using the following illustration or the FRU map on the controller module:...
Page 585 • A copy of the same image version of ONTAP as what the impaired controller was running. You can download the appropriate image from the Downloads section on the NetApp Support Site ◦ If NVE is enabled, download the image with NetApp Volume Encryption, as indicated in the download button.
Page 586 handle to the closed position. The node begins to boot as soon as it is completely installed into the chassis. 5. Interrupt the boot process to stop at the LOADER prompt by pressing Ctrl-C when you see Starting AUTOBOOT press Ctrl-C to abort…. If you miss this message, press Ctrl-C, select the option to boot to Maintenance mode, and then halt the node to boot to LOADER.
Page 587 the environmental variables. This procedure applies to systems that are not in a two-node MetroCluster configuration. Steps 1. From the LOADER prompt, boot the recovery image from the USB flash drive: boot_recovery The image is downloaded from the USB flash drive. 2.
Page 588 If your system has… Then… No network connection and is in a a. Press when prompted to restore the backup configuration. MetroCluster IP configuration b. Reboot the system when prompted by the system. c. Wait for the iSCSI storage connections to connect. You can proceed after you see the following messages: date-and-time [node- name:iscsi.session.stateChanged:notice]:...
Page 589 ◦ If your system does not have onboard keymanager, NSE or NVE configured, complete the steps in this section. 6. From the LOADER prompt, enter the command. boot_ontap *If you see… Then…* The login prompt Go to the next Step. Waiting for giveback…...
Page 590 b. Check the environment variable settings with the printenv command. c. If an environment variable is not set as expected, modify it with the setenv environment- command. variable-name changed-value d. Save your changes using the command. savenv e. Reboot the node. Switch back aggregates in a two-node MetroCluster configuration - AFF A700 and FAS9000 After you have completed the FRU replacement in a two-node MetroCluster configuration, you can perform the MetroCluster switchback operation.
Page 591 Once environment variables are checked, you must complete steps specific to systems that have Onboard Key Manager (OKM), NetApp Storage Encryption (NSE) or NetApp Volume Encryption (NVE) enabled. Determine which section you should use to restore your OKM, NSE, or NVE configurations: If NSE or NVE are enabled along with Onboard Key Manager you must restore settings you captured at the beginning of this procedure.
Page 592 If the console Then… displays… The LOADER prompt Boot the controller to the boot menu: boot_ontap menu Waiting for giveback… a. Enter at the prompt Ctrl-C b. At the message: Do you wish to halt this controller rather than wait [y/n]? , enter: c.
Page 593 9. Confirm the target controller is ready for giveback with the storage failover show command. 10. Give back only the CFO aggregates with the storage failover giveback -fromnode local -only-cfo command. -aggregates true ◦ If the command fails because of a failed disk, physically disengage the failed disk, but leave the disk in the slot until a replacement is received.
Page 594 If giveback is not complete after 20 minutes, contact Customer Support. 18. At the clustershell prompt, enter the command to list the logical net int show -is-home false interfaces that are not on their home controller and port. If any interfaces are listed as false, revert those interfaces back to their home port using the net int command.
Page 595 This command does not work if NVE (NetApp Volume Encryption) is configured 10. Use the security key-manager query to display the key IDs of the authentication keys that are stored on the key management servers.
Page 596 If the console Then… displays… The login prompt Go to Step 7. Waiting for giveback… a. Log into the partner controller. b. Confirm the target controller is ready for giveback with the storage command. failover show 4. Move the console cable to the partner controller and give back the target controller storage using the storage failover giveback -fromnode local -only-cfo-aggregates true local command.
Page 597 -auto-giveback true Return the failed part to NetApp - AFF A700 and FAS9000 After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 598 About this task If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller;...
Page 599 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 600 If the impaired controller… Then… Has not automatically switched Review the veto messages and, if possible, resolve the issue and try over, you attempted switchover again. If you are unable to resolve the issue, contact technical support. with the metrocluster command, and the switchover switchover was vetoed...
Page 601 If the healing is vetoed, you have the option of reissuing the command with the metrocluster heal -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation. 7. Verify that the heal operation is complete by using the command on metrocluster operation show the destination cluster:...
Page 602 Orange release button. Caching module cam handle. a. Press the orange release button on the front of the caching module. Do not use the numbered and lettered I/O cam latch to eject the caching module. The numbered and lettered I/O cam latch ejects the entire NVRAM10 module and not the caching module.
Page 603 front of the NVRAM module in slot 6-1 in the rear of the system. To replace or add the core dump module, locate slot 6-1, and then follow the specific sequence of steps to add or replace it. Before you begin •...
Page 604 Do not use the numbered and lettered I/O cam latch to eject the core dump module. The numbered and lettered I/O cam latch ejects the entire NVRAM10 module and not the core dump module. c. Rotate the cam handle until the core dump module begins to slide out of the NVRAM10 module. d.
Page 605 cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B controller_B_1 configured enabled waiting for switchback recovery 2 entries were displayed. 2. Verify that resynchronization is complete on all SVMs: metrocluster vserver show 3.
Page 606 Step 6: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800-44- 638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Page 607 ::> system controller slot module replace -node node1 -slot 6-2 Warning: NVMe module in slot 6-2 of the node node1 will be powered off for replacement. Do you want to continue? (y|n): `y` The module has been successfully powered off. It can now be safely replaced.
Page 608 Orange release button. Caching module cam handle. a. Press the orange release button on the front of the caching module. Do not use the numbered and lettered I/O cam latch to eject the caching module. The numbered and lettered I/O cam latch ejects the entire NVRAM10 module and not the caching module.
Page 609 If you replace the caching module with a caching module from a different vendor, the new vendor name is displayed in the command output. 9. After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 610 • If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message: system node autosupport invoke -node * -type all -message MAINT=number_of_hours_downh The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*> system node autosupport invoke -node * -type all -message MAINT=2h Steps 1.
Page 611 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 612 5. Check the state of the aggregates by using the storage aggregate show command. controller_A_1::> storage aggregate show Aggregate Size Available Used% State #Vols Nodes RAID Status --------- -------- --------- ----- ------- ------ ---------------- ------------ aggr_b2 227.1GB 227.1GB 0% online 0 mcc1-a2 raid_dp, mirrored, normal...
Page 613 2. Turn off the power supply and disconnect the power cables: a. Turn off the power switch on the power supply. b. Open the power cable retainer, and then unplug the power cable from the power supply. c. Unplug the power cable from the power source. 3.
Page 614 The fan modules are short. Always support the bottom of the fan module with your free hand so that it does not suddenly drop free from the chassis and injure you. Orange release button 3. Set the fan module aside. 4.
Page 615 Cam handle release button Cam handle 3. Rotate the cam handle so that it completely disengages the controller module from the chassis, and then slide the controller module out of the chassis. Make sure that you support the bottom of the controller module as you slide it out of the chassis. 4.
Page 616 1. Unplug any cabling associated with the target I/O module. Make sure that you label the cables so that you know where they came from. 2. Remove the target I/O module from the chassis: a. Depress the lettered and numbered cam button. The cam button moves away from the chassis.
Page 617 Step 5: Remove the De-stage Controller Power Module Steps You must remove the de-stage controller power modules from the old chassis in preparation for installing the replacement chassis. 1. Press the orange locking button on the module handle, and then slide the DCPM module out of the chassis.
Page 618 5. Slide the chassis all the way into the equipment rack or system cabinet. 6. Secure the front of the chassis to the equipment rack or system cabinet, using the screws you removed from the old chassis. 7. Secure the rear of the chassis to the equipment rack or system cabinet. 8.
Page 619 Step 10: Install I/O modules Steps To install I/O modules, including the NVRAM/FlashCache modules from the old chassis, follow the specific sequence of steps. You must have the chassis installed so that you can install the I/O modules into the corresponding slots in the new chassis.
Page 620 Complete the restoration and replacement process - AFF A700 and FAS9000 You must verify the HA state of the chassis, run diagnostics, and return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Step 1: Verify and set the HA state of the chassis You must verify the HA state of the chassis, and, if necessary, update the state to match your system configuration.
Page 621 b. Confirm that the setting has changed: ha-config show 3. If you have not already done so, recable the rest of your system. 4. Exit Maintenance mode: halt The LOADER prompt appears. Step 2: Running system-level diagnostics After installing a new chassis, you should run interconnect diagnostics. Your system must be at the LOADER prompt to start System Level Diagnostics.
Page 622 If the system-level diagnostics Then… tests… Were completed without any a. Clear the status logs: sldiag device clearstatus failures b. Verify that the log was cleared: sldiag device status The following default response is displayed: SLDIAG: No log messages are present. c.
Page 623 If the system-level diagnostics Then… tests… Resulted in some test failures Determine the cause of the problem. a. Exit Maintenance mode: halt b. Perform a clean shutdown, and then disconnect the power supplies. c. Verify that you have observed all of the considerations identified for running system-level diagnostics, that cables are securely connected, and that hardware components are properly installed in the storage system.
Page 624 6. Reestablish any SnapMirror or SnapVault configurations. Step 4: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 625 If this is the procedure you should use, note that the controller replacement procedure for a node in a four or eight node MetroCluster configuration is the same as that in an HA pair. No MetroCluster-specific steps are required because the failure is restricted to an HA pair and storage failover commands can be used to provide nondisruptive operation during the replacement.
Page 626 If the impaired controller is Then… displaying… The LOADER prompt Go to Remove controller module. Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name...
Page 627 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 628 parameter. If you use this optional parameter, the system overrides any soft vetoes -override-vetoes that prevent the healing operation. 4. Verify that the operation has been completed by using the metrocluster operation show command. controller_A_1::> metrocluster operation show Operation: heal-aggregates ...
Page 629 Replace the controller module hardware - AFF A700 and FAS9000 To replace the controller module hardware, you must remove the impaired node, move FRU components to the replacement controller module, install the replacement controller module in the chassis, and then boot the system to Maintenance mode. Step 1: Remove the controller module To access components inside the controller, you must first remove the controller module from the system and then remove the cover on the controller module.
Page 630 Cam handle release button Cam handle 1. Rotate the cam handle so that it completely disengages the controller module from the chassis, and then slide the controller module out of the chassis. Make sure that you support the bottom of the controller module as you slide it out of the chassis. 2.
Page 631 Step 2: Move the boot media You must locate the boot media and follow the directions to remove it from the old controller and insert it in the new controller. Steps 1. Lift the black air duct at the back of the controller module and then locate the boot media using the following illustration or the FRU map on the controller module: Press release tab Boot media...
Page 632 5. Push the boot media down to engage the locking button on the boot media housing. Step 3: Move the system DIMMs To move the DIMMs, locate and move them from the old controller into the replacement controller and follow the specific sequence of steps. Steps 1.
Page 633 DIMM 5. Locate the slot where you are installing the DIMM. 6. Make sure that the DIMM ejector tabs on the connector are in the open position, and then insert the DIMM squarely 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. Visually inspect the DIMM to verify that it is evenly aligned and fully inserted into the slot.
Page 634 5. Complete the reinstallation of the controller module: a. If you have not already done so, reinstall the cable management device. b. Firmly push the controller module into the chassis until it meets the midplane and is fully seated. The locking latches rise when the controller module is fully seated. Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.
Page 635 The date and time are given in GMT. Step 2: Verify and set the HA state of the controller module You must verify the state of the controller module and, if necessary, update the state to match your system configuration. Steps 1.
Page 636 ◦ is a network interface card. ◦ is nonvolatile RAM. nvram ◦ is a hybrid of NVRAM and system memory. nvmem ◦ is a Serial Attached SCSI device not connected to a disk shelf. 4. Run diagnostics as desired. If you want to run diagnostic Then…...
Page 637 If you want to run diagnostic Then… tests on… Multiple components at the same a. Review the enabled and disabled devices in the output from the time preceding procedure and determine which ones you want to run concurrently. b. List the individual tests for the device: sldiag device show -dev dev_name c.
Page 638 If the system-level diagnostics Then… tests… Were completed without any a. Clear the status logs: sldiag device clearstatus failures b. Verify that the log was cleared: sldiag device status The following default response is displayed: SLDIAG: No log messages are present. c.
Page 639 If the system-level diagnostics Then… tests… Resulted in some test failures Determine the cause of the problem: a. Exit Maintenance mode: halt After you issue the command, wait until the system stops at the LOADER prompt. b. Turn off or leave on the power supplies, depending on how many controller modules are in the chassis: ◦...
Page 640 1. Recable the system. 2. Verify that the cabling is correct by using Active IQ Config Advisor. a. Download and install Config Advisor. b. Enter the information for the target system, and then click Collect Data. c. Click the Cabling tab, and then examine the output. Make sure that all disk shelves are displayed and all disks appear in the output, correcting any cabling issues you find.
Page 641 appears (*>). b. Save any coredumps: system node run -node local-node-name partner savecore c. Wait for the `savecore`command to complete before issuing the giveback. You can enter the following command to monitor the progress of the savecore command: system node run -node local-node-name partner savecore -s d.
Page 642 Complete system restoration - AFF A700 and FAS9000 To complete the replacement procedure and restore your system to full operation, you must recable the storage, restore the NetApp Storage Encryption configuration (if necessary), and install licenses for the new controller. You must complete a series of tasks before restoring your system to full operation.
Page 643 If the node is in a MetroCluster configuration and all nodes at a site have been replaced, license keys must be installed on the replacement node or nodes prior to switchback. 1. If you need new license keys, obtain replacement license keys on the NetApp Support Site in the My Support section under Software licenses.
Page 644 If any LIFs are listed as false, revert them to their home ports: network interface revert 2. Register the system serial number with NetApp Support. ◦ If AutoSupport is enabled, send an AutoSupport message to register the serial number. ◦ If AutoSupport is not enabled, call NetApp Support to register the serial number.
Page 645 6. Reestablish any SnapMirror or SnapVault configurations. Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 646 Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp...
Page 647 replacement procedure. Replace a DIMM - AFF A700 and FAS9000 You must replace a DIMM in the controller module when your system registers an increasing number of correctable error correction codes (ECC); failure to do so causes a system panic. All other components in the system must be functioning properly;...
Page 648 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 649 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 650 controller_A_1::> metrocluster operation show Operation: heal-aggregates State: successful Start Time: 7/25/2016 18:45:55 End Time: 7/25/2016 18:45:56 Errors: - 5. Check the state of the aggregates by using the command. storage aggregate show controller_A_1::> storage aggregate show Aggregate Size Available Used% State #Vols...
Page 651 Steps 1. If you are not already grounded, properly ground yourself. 2. Unplug the cables from the impaired controller module, and keep track of where the cables were connected. 3. Slide the orange button on the cam handle downward until it unlocks. Cam handle release button Cam handle 4.
Page 652 module. Controller module cover locking button Step 3: Replace the DIMMs To replace the DIMMs, locate them inside the controller and follow the specific sequence of steps. Steps 1. If you are not already grounded, properly ground yourself. 2. Locate the DIMMs on your controller module. Each system memory DIMM has an LED located on the board next to each DIMM slot.
Page 653 3. Eject the DIMM from its slot by slowly pushing apart the two DIMM ejector tabs on either side of the DIMM, and then slide the DIMM out of the slot. Carefully hold the DIMM by the edges to avoid pressure on the components on the DIMM circuit board.
Page 654 DIMM ejector tabs DIMM 4. Remove the replacement DIMM from the antistatic shipping bag, hold the DIMM by the corners, and align it to the slot. The notch among the pins on the DIMM should line up with the tab in the socket. 5.
Page 655 Step 4: Install the controller After you install the components into the controller module, you must install the controller module back into the system chassis and boot the operating system. For HA pairs with two controller modules in the same chassis, the sequence in which you install the controller module is especially important because it attempts to reboot as soon as you completely seat it in the chassis.
Page 656 b. After the node boots to Maintenance mode, halt the node: halt After you issue the command, you should wait until the system stops at the LOADER prompt. During the boot process, you can safely respond to prompts: ▪ A prompt warning that when entering Maintenance mode in an HA configuration, you must ensure that the healthy node remains down.
Page 657 If the system-level diagnostics Then… tests… A two-node MetroCluster Proceed to the next step. configuration The MetroCluster switchback procedure is done in the next task in the replacement process. A stand-alone configuration Proceed to the next step. No action is required. You have completed system-level diagnostics.
Page 658 Step 6: Switch back aggregates in a two-node MetroCluster configuration After you have completed the FRU replacement in a two-node MetroCluster configuration, you can perform the MetroCluster switchback operation. This returns the configuration to its normal operating state, with the sync-source storage virtual machines (SVMs) on the formerly impaired site now active and serving data from the local disk pools.
Page 659 6. Reestablish any SnapMirror or SnapVault configurations. Step 7: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 660 7. Align the bezel with the ball studs, and then gently push the bezel onto the ball studs. 8. After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 661 from the impaired controller storage. About this task If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller;...
Page 662 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
Page 663 If the impaired controller… Then… Has not automatically switched Review the veto messages and, if possible, resolve the issue and try over, you attempted switchover again. If you are unable to resolve the issue, contact technical support. with the metrocluster command, and the switchover switchover was vetoed...
Page 664 If the healing is vetoed, you have the option of reissuing the command with the metrocluster heal -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation. 7. Verify that the heal operation is complete by using the command on metrocluster operation show the destination cluster:...
Page 665 Lettered and numbered I/O cam latch I/O cam latch completely unlocked 4. Set the I/O module aside. 5. Install the replacement I/O module into the chassis by gently sliding the I/O module into the slot until the lettered and numbered I/O cam latch begins to engage with the I/O cam pin, and then push the I/O cam latch all the way up to lock the module in place.
Page 666 If your system is in… Issue this command from the partner’s console… An HA pair storage failover giveback -ofnode impaired_node_name A two-node MetroCluster Proceed to the next step. configuration The MetroCluster switchback procedure is done in the next task in the replacement process.
Page 667 6. Reestablish any SnapMirror or SnapVault configurations. Step 5: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 668 There is an audible click when the module is secure and connected to the midplane. Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 669 Before you begin • All disk shelves must be working properly. • If your system is in an HA pair, the partner node must be able to take over the node associated with the NVRAM module that is being replaced. •...
Page 670 Option 1: Most configs To shut down the impaired controller, you must determine the status of the controller and, if necessary, take over the controller so that the healthy controller continues to serve data from the impaired controller storage. About this task If you have a cluster with more than two nodes, it must be in quorum.
Page 671 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with CLI.
Page 672 If the impaired controller… Then… Has automatically switched over Proceed to the next step. Has not automatically switched Perform a planned switchover operation from the healthy over controller: metrocluster switchover Has not automatically switched Review the veto messages and, if possible, resolve the issue and over, you attempted switchover try again.
Page 673 mcc1A::> metrocluster heal -phase root-aggregates [Job 137] Job succeeded: Heal Root Aggregates is successful If the healing is vetoed, you have the option of reissuing the command with metrocluster heal the -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation.
Page 674 Orange release button (gray on empty FlashCache modules) FlashCache cam handle a. Press the orange button on the front of the FlashCache module. The release button on empty FlashCache modules is gray. b. Swing the cam handle out until the module begins to slide out of the old NVRAM module. c.
Page 675 Lettered and numbered I/O cam latch I/O latch completely unlocked 4. Set the NVRAM module on a stable surface and remove the cover from the NVRAM module by pushing down on the blue locking button on the cover, and then, while holding down the blue button, slide the lid off the NVRAM module.
Page 676 Cover locking button DIMM and DIMM ejector tabs 5. Remove the DIMMs, one at a time, from the old NVRAM module and install them in the replacement NVRAM module. 6. Close the cover on the module. 7. Install the replacement NVRAM module into the chassis: a.
Page 677 c. Remove the NVRAM module from the chassis by pulling on the pull tabs on the sides of the module face. Lettered and numbered I/O cam latch I/O latch completely unlocked 3. Set the NVRAM module on a stable surface and remove the cover from the NVRAM module by pushing down on the blue locking button on the cover, and then, while holding down the blue button, slide the lid off the NVRAM module.
Page 678 Cover locking button DIMM and DIMM ejector tabs 4. Locate the DIMM to be replaced inside the NVRAM module, and then remove it by pressing down on the DIMM locking tabs and lifting the DIMM out of the socket. Each DIMM has an LED next to it that flashes when the DIMM has failed. 5.
Page 679 Select one of the following options for instructions on how to reassign disks to the new controller.
Page 680 Option 1: Verify ID (HA pair) Verify the system ID change on an HA system You must confirm the system ID change when you boot the replacement node and then verify that the change was implemented. This procedure applies only to systems running ONTAP in an HA pair. Steps 1.
Page 681 node run -node local-node-name partner savecore -s d. Return to the admin privilege level: set -privilege admin 5. Give back the node: a. From the healthy node, give back the replaced node’s storage: storage failover giveback -ofnode replacement_node_name The replacement node takes back its storage and completes booting. If you are prompted to override the system ID due to a system ID mismatch, you should enter y.
Page 682 8. If the node is in a MetroCluster configuration, depending on the MetroCluster state, verify that the DR home ID field shows the original owner of the disk if the original owner is a node on the disaster site. This is required if both of the following are true: ◦...
Page 683 Local System ID: 118065481 4. Reassign disk ownership (for FAS systems) or LUN ownership (for FlexArray systems), by using the system ID information obtained from the disk show command: disk reassign -s old system In the case of the preceding example, the command is:...
Page 684 *> disk show -a Local System ID: 118065481 DISK OWNER POOL SERIAL NUMBER HOME ------- ------------- ----- ------------- ------------- disk_name system-1 (118065481) Pool0 J8Y0TDZC system-1 (118065481) disk_name system-1 (118065481) Pool0 J8Y09DXC system-1 (118065481) 6. From the healthy node, verify that any coredumps are saved: a.
Page 685 Display the results of the MetroCluster check: metrocluster check show e. Run Config Advisor. Go to the Config Advisor page on the NetApp Support Site at support.netapp.com/NOW/download/tools/config_advisor/. After running Config Advisor, review the tool’s output and follow the recommendations in the output to address any issues discovered.
Page 686 Restore external key management encryption keys ◦ Step 7: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp...
Page 687 The green power LED lights when the PSU is fully inserted into the chassis and the amber attention LED flashes initially, but turns off after a few moments. 9. After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 688 continue to function. • You can use this procedure with all versions of ONTAP supported by your system • All other components in the system must be functioning properly; if not, you must contact technical support. Step 1: Shut down the impaired controller You can shut down or take over the impaired controller using different procedures, depending on the storage system hardware configuration.
Page 689 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the...
Page 690 • You must leave the power supplies turned on at the end of this procedure to provide power to the healthy controller. Steps 1. Check the MetroCluster status to determine whether the impaired controller has automatically switched over to the healthy controller: metrocluster show 2.
Page 691 controller_A_1::> storage aggregate show Aggregate Size Available Used% State #Vols Nodes RAID Status --------- -------- --------- ----- ------- ------ ---------------- ------------ aggr_b2 227.1GB 227.1GB 0% online 0 mcc1-a2 raid_dp, mirrored, normal... 6. Heal the root aggregates by using the command. metrocluster heal -phase root-aggregates mcc1A::>...
Page 692 Cam handle release button Cam handle 4. Rotate the cam handle so that it completely disengages the controller module from the chassis, and then slide the controller module out of the chassis. Make sure that you support the bottom of the controller module as you slide it out of the chassis. 5.
Page 693 Controller module cover locking button Step 3: Replace the RTC battery To replace the RTC battery, you must locate the failed battery in the controller module, remove it from the holder, and then install the replacement battery in the holder. Steps 1.
Page 694 RTC battery RTC battery housing 3. Gently push the battery away from the holder, rotate it away from the holder, and then lift it out of the holder. Note the polarity of the battery as you remove it from the holder. The battery is marked with a plus sign and must be positioned in the holder correctly.
Page 695 Steps 1. If you have not already done so, close the air duct or controller module cover. 2. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system. Do not completely insert the controller module in the chassis until instructed to do so.
Page 696 Steps 1. Verify that all nodes are in the state: enabled metrocluster node show cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A controller_A_1 configured enabled heal roots completed cluster_B ...
Page 697 6. Reestablish any SnapMirror or SnapVault configurations. Step 6: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
Page 698 Option 1: Add an X91148A module as a NIC module in a system with open slots To add an X91148A module as a NIC module in a system with open slots, you must follow the specific sequence of steps. Steps 1.
Page 699 -port port name -mode network for other slots that can be used by the X91148A module for networking. NetApp Hardware Universe • All other components in the system must be functioning properly; if not, you must contact technical support.
Page 700 install one or more X91148A NIC modules into your fully-populated system. Steps 1. If you are adding an X91148A module into a slot that contains a NIC module with the same number of ports as the X91148A module, the LIFs will automatically migrate when its controller module is shut down. If the NIC module being replaced has more ports than the X91148A module, you must permanently reassign the affected LIFs to a different home port.
Page 701 Lettered and numbered I/O cam latch I/O cam latch completely unlocked 6. Install the X91148A module into the target slot: a. Align the X91148A module with the edges of the slot. b. Slide the X91148A module into the slot until the lettered and numbered I/O cam latch begins to engage with the I/O cam pin.
Page 702 Option 2: Adding an X91148A module as a storage module in a system with no open slots You must remove one or more existing NIC or storage modules in your system in order to install one or more X91148A storage modules into your fully-populated system. •...
Page 703 Lettered and numbered I/O cam latch I/O cam latch completely unlocked 6. Install the X91148A module into slot 3: a. Align the X91148A module with the edges of the slot. b. Slide the X91148A module into the slot until the lettered and numbered I/O cam latch begins to engage with the I/O cam pin.
Page 704 NetApp assumes no responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by NetApp. The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual property rights of NetApp.

This manual is also suitable for:

Fas500f Fas2600 Fas2700 Fas8200 Fas8300 Fas9000

NetApp FAS Manual

Quick Links

Need help?

Questions and answers

Related Manuals for NetApp FAS

Summary of Contents for NetApp FAS

Page 2: Table Of Contents

Page 3: Fas Systems

Page 98: Fas2600 System Documentation

Page 183: Fas2700 System Documentation

Page 306: Fas8200 System Documentation

Page 426: Fas8300 And Fas8700 System Documentation

Page 556: Aff A700 And Fas9000 System Documentation

This manual is also suitable for: