Download
Share
Print this page
NetApp AFF A400 Manual
  1. Manuals
  2. Brands
  3. NetApp Manuals
  4. Storage
  5. AFF A400
  6. Manual

NetApp AFF A400 Manual

Hide thumbs Also See for AFF A400:

Advertisement

Quick Links

Download this manual
AFF A400 systems
ONTAP Systems
NetApp
November 23, 2021
This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/a400/install-setup.html on
November 23, 2021. Always check docs.netapp.com for the latest.

Advertisement

loading
Need help?

Need help?

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

Questions and answers

Related Manuals for NetApp AFF A400

Summary of Contents for NetApp AFF A400

  • Page 1 AFF A400 systems ONTAP Systems NetApp November 23, 2021 This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/a400/install-setup.html on November 23, 2021. Always check docs.netapp.com for the latest.
  • Page 2 Table of Contents AFF A400 System Documentation ............

  • Page 3: Install And Setup

    Video one of two: Hardware installation and cabling The following video shows how to install and cable your new system. AFF A400 Installation and setup instructions AFF A400 Installation and setup instructions Video two of two: Perform end-to-end software configuration...
  • Page 4 NetApp video: Software configuration for vSphere NAS datastores for FAS/AFF systems running ONTAP 9.2 Detailed guide - AFF A400 This guide gives detailed step-by-step instructions for installing a typical NetApp system. Use this guide if you want more detailed installation instructions.
  • Page 5 Power cables Not applicable Powering up the system 4. Review the NetApp ONTAP Configuration 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 6 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 7 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 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 or illustration to complete the cabling between the controllers and to the switches: Switched cluster cabling 2.
  • Page 9 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 illustration to cable your controllers to a single drive shelf. Cabling the controllers to one NS224 drive shelf 2.
  • 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. Steps 1. Use the following animation or illustration to cable your controllers to two drive shelves. Cabling controllers to two NS224 drive shelves 2.
  • Page 11 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 illustration to cable your controllers to two drive shelves. Cabling the controllers to SAS drive shelves...
  • Page 12 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 13 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 14 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 4. Set up your account and download Active IQ Config Advisor: a.

  • Page 15: Boot Media

    ◦ If the impaired node is in a standalone configuration and at LOADER prompt, contact NetApp Support. mysupport.netapp.com 2. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message: system node autosupport invoke -node * -type all -message...
  • Page 16 Check NVE or NSE on systems running ONTAP 9.6 and later Before shutting down the impaired node, 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 17 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 18 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 19 Shut down the impaired controller - AFF A400 Option 1: Most configurations After completing the NVE or NSE tasks, you need to complete the shutdown of the impaired node. Steps 1. If the impaired node isn’t at the LOADER prompt: If the impaired node displays…...
  • Page 20 About this task • 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 Administration overview with the CLI.
  • Page 21 If the impaired node… 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 22 8. On the impaired controller module, disconnect the power supplies. Remove the controller module, replace the boot media and transfer the boot image to the boot media - AFF A400 To replace the boot media, you must remove the impaired controller module, install the replacement boot media, and transfer the boot image to a USB flash drive.
  • Page 23 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 boot media.
  • Page 24 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 25 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 26 Steps 1. Download and copy the appropriate service image from the NetApp Support Site to the USB flash drive. a. Download the service image to your work space on your laptop. b. Unzip the service image.
  • Page 27 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 28 The changes will be implemented when the system is booted. Booting the recovery image - AFF A400 The procedure for booting the impaired node from the recovery image depends on whether the system is in a two-node MetroCluster configuration.
  • Page 29 If your system has… Then… No network connection a. Press when prompted to restore the backup configuration. b. Reboot the system when prompted by the system. c. Select the Update flash from backup config (sync flash) option from the displayed menu. If you are prompted to continue with the update, press y.
  • Page 30 Reboot the node. Switch back aggregates in a two-node MetroCluster configuration - AFF A400 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 31 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 32 Restore OKM, NSE, and NVE as needed - AFF A400 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 33 --------------------------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 Waiting for giveback… prompt. 8. Move the console cable to the partner node and login as "admin". 9.
  • Page 34 c. Enter the security key-manager key query command to see a detailed view of all keys stored in the onboard key manager and verify that the column = for all authentication Restored yes/true keys. If the Restored column = anything other than yes/true, contact Customer Support. d.
  • Page 35 -auto-giveback true Return the failed part to NetApp - AFF A400 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 36 • 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. Shut down the controllers - AFF A400 Option 1: Shut down the controllers when replacing a chassis You must shut down the node or nodes in the chassis prior to moving them to the new chassis.
  • Page 37 About this task • 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 Administration overview with the CLI.
  • Page 38 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 -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation.
  • Page 39   Errors: - 8. On the impaired controller module, disconnect the power supplies. Move and replace hardware - AFF A400 Step 1: Remove the controller modules To replace the chassis, you must remove the controller modules from the old chassis.
  • Page 40 that it does not swing out of the chassis. 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. 5.
  • Page 41 If your system stops at the boot menu, select the option to boot to LOADER. 4. Repeat the preceding steps to install the second controller into the new chassis. Complete the restoration and replacement process - AFF A400 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 42 ▪ mccip ▪ non-ha 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. Reinstall the bezel on the front of the system. Step 2: Run diagnostics After you have replaced a component in your system, you should run diagnostic tests on that component.
  • Page 43 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 44: Controller Module

    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 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 45 necessary, take over the node so that the healthy node continues to serve data from the impaired node storage. 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 node shows false for eligibility and health, you must correct the issue before shutting down the impaired node;...
  • Page 46 About this task • 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 Administration overview with the CLI.
  • Page 47 If the impaired node… 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 48 Errors: - 8. On the impaired controller module, disconnect the power supplies. Move the controller module hardware - AFF A400 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.
  • Page 49 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. On the replacement controller module, open the air duct and remove the empty risers from the controller module using the animation, illustration, or the written steps: Removing the empty risers from the replacement controller module...
  • Page 50 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 51 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 52 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. Slide the air duct toward the back of the controller module, and then rotate it upward to its completely open position.
  • Page 53 You can use the following animation, illustration, or the written steps to move the boot media from the impaired controller module to the replacement controller module. Moving the boot media 1. Locate and remove the boot media from the controller module: a.
  • Page 54 Step 5: Move the PCIe risers and mezzanine card As part of the controller replacement process, you must move the PCIe risers and mezzanine card from the impaired controller module to the replacement controller module. 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.
  • Page 55 2. Remove riser number 3, remove the mezzanine card, and install both into 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 56 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. Verify that the NVDIMM battery is not plugged into the new controller module. 4.
  • Page 57 b. Locate the corresponding DIMM slot on the replacement controller module. c. Make sure that the DIMM ejector tabs on the DIMM socket are in the open position, and then insert the DIMM squarely into the socket. The DIMMs fit tightly in the socket, but should go in easily. If not, realign the DIMM with the socket and reinsert it.
  • Page 58 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 - AFF A400 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.
  • Page 59 1. If the replacement node is not at the LOADER prompt, halt the system to the LOADER prompt. 2. On the healthy node, check the system time: show date The date and time are given in GMT. 3. At the LOADER prompt, check the date and time on the replacement node: show date The date and time are given in GMT.
  • Page 60 ▪ A prompt warning that when entering Maintenance mode in an HA configuration you must ensure that the healthy node remains down. You can safely respond to these prompts. Recable the system and reassign disks - AFF A400 Continue the replacement procedure by recabling the storage and confirming disk reassignment. Step 1: Recable the system After running diagnostics, you must recable the controller module’s storage and network...
  • Page 61 This procedure applies only to systems running ONTAP in an HA pair. 1. If the replacement node is in Maintenance mode (showing the prompt, exit Maintenance mode and go *> to the LOADER prompt: halt 2. From the LOADER prompt on the replacement node, boot the node, entering if you are prompted to override the system ID due to a system ID mismatch:boot_ontap...
  • Page 62 If the giveback is vetoed, you can consider overriding the vetoes. Find the High-Availability Configuration Guide for your version of ONTAP 9 b. After the giveback has been completed, confirm that the HA pair is healthy and that takeover is possible: storage failover show The output from the storage failover show...
  • Page 63 11. If you disabled automatic takeover on reboot, enable it from the healthy node: storage failover modify -node replacement-node-name -onreboot true Complete system restoration - AFF A400 Step 1: Install licenses for the replacement node in ONTAP You must install new licenses for the replacement node if the impaired node was using ONTAP features that require a standard (node-locked) license.
  • Page 64 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 65 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 66 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 67 If the impaired node is Then… displaying… The LOADER prompt Go to the next step. Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired node: prompt (enter system password) •...
  • Page 68 About this task • 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 Administration overview with the CLI.
  • Page 69 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 70 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 71 4. Remove the cable management device from the controller module and set it aside. 5. Press down on both of the locking latches, and then rotate both latches downward at the same time. The controller module moves slightly out of the chassis. 6.
  • Page 72 The DIMMs are located in sockets 2, 4, 13, and 15. The NVDIMM is located in slot 11. 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 73 5. 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. 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.
  • Page 74 the following sections. 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 75 5. Select an option from the displayed sub-menu and run the test. 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 Reboot from the menu to reboot the system. Step 6: Restore the controller module to operation after running diagnostics After completing diagnostics, you must recable the system, give back the controller module, and then reenable automatic giveback.
  • Page 76 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 77 You can use the following animation, illustration, or the written steps to hot-swap a fan module. Replacing a fan 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.
  • Page 78 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 79 If the impaired node is Then… displaying… The LOADER prompt Go to the next step. Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired node: prompt (enter system password) •...
  • Page 80 About this task • 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 Administration overview with the CLI.
  • Page 81 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 82 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 83 4. Remove the cable management device from the controller module and set it aside. 5. Press down on both of the locking latches, and then rotate both latches downward at the same time. The controller module moves slightly out of the chassis. 6.
  • Page 84 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. Slide the air duct toward the back of the controller module, and then rotate it upward to its completely open position.
  • Page 85 3. Cable the management and console ports only, so that you can access the system to perform the tasks in the following sections. 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.
  • Page 86 5. Proceed based on the result of the preceding step: ◦ If the scan show problems, correct the issue, and then rerun the scan. ◦ If the scan reported no failures, select Reboot from the menu to reboot the system. Step 6: Restore the controller module to operation after running diagnostics After completing diagnostics, you must recable the system, give back the controller module, and then reenable automatic giveback.
  • Page 87 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 88 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. Option 1: Most configurations To shut down the impaired node, you must determine the status of the node and, if necessary, take over the node so that the healthy node continues to serve data from the impaired node storage.
  • Page 89 About this task • 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 Administration overview with the CLI.
  • Page 90 1. Check the MetroCluster status to determine whether the impaired node has automatically switched over to the healthy node: metrocluster show 2. Depending on whether an automatic switchover has occurred, proceed according to the following table: If the impaired node… Then…...
  • Page 91 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 92 LED turns off. • Although the contents of the NVDIMM is encrypted, it is a best practice to erase the contents of the NVDIMM before replacing it. For more information, see the Statement of Volatility on the NetApp Support...
  • Page 93 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. The animation shows empty slots for sockets without DIMMs. These empty sockets are populated with blanks.
  • Page 94 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. Carefully hold the NVDIMM by the edges to avoid pressure on the components on the NVDIMM circuit board.
  • Page 95 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 96 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 3. Select Scan System from the displayed menu to enable running the diagnostics tests. 4.
  • Page 97 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 98 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 99 If the impaired node is Then… displaying… Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired node: prompt (enter system password) • For an HA pair, take over the impaired node from the healthy node: storage failover takeover -ofnode impaired_node_name...
  • Page 100 About this task • 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 Administration overview with the CLI.
  • Page 101 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 102 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 103 4. Remove the cable management device from the controller module and set it aside. 5. Press down on both of the locking latches, and then rotate both latches downward at the same time. The controller module moves slightly out of the chassis. 6.
  • Page 104 The riser raises up slightly from the controller module. d. Lift the riser up straight up and set it aside on a stable flat surface, 2. Remove the PCIe card from the riser: a. Turn the riser so that you can access the PCIe card. b.
  • Page 105 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 106 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 re-install 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 107 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 108 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 109 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 110 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 111 necessary, take over the node so that the healthy node continues to serve data from the impaired node 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 node shows false for eligibility and health, you must correct the issue before shutting down the impaired node;...
  • Page 112 About this task • 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 Administration overview with the CLI.
  • Page 113 If the impaired node… Then… Has not automatically switched Perform a planned switchover operation from the healthy node: 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 114 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 115 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. 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 116 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 117 5. Close the air duct. Step 4: Reinstall the controller module and setting time/date after RTC battery replacement After you replace a component within the controller module, you must reinstall the controller module in the system chassis, reset the time and date on the controller, and then boot it.
  • Page 118 The controller module begins to boot as soon as it is fully seated in the chassis. Be prepared to interrupt the boot process. b. 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 119 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 120 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 121 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:

Aff a400 systems