NetApp FAS8300 Manual

Hide thumbs Also See for FAS8300:

Manual (24 pages)

Installation and setup instructions (4 pages)

Install (314 pages)

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

page of 133

/ 133
Bookmarks

Quick Links

Download this manual

FAS8300 and FAS8700 systems

ONTAP Systems

NetApp

November 23, 2021

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

on November 23, 2021. Always check docs.netapp.com for the latest.

Need help?

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

Questions and answers

Summary of Contents for NetApp FAS8300

Page 1 FAS8300 and FAS8700 systems ONTAP Systems NetApp November 23, 2021 This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/fas8300/install-setup.html on November 23, 2021. Always check docs.netapp.com for the latest.
Page 2 Table of Contents FAS8300 and FAS8700 System Documentation ..........
Page 3: Install And Setup
Use this guide if you are familiar with installing NetApp systems. Access the Installation and Setup Instructions PDF poster: FAS8300 and FAS8700 Installation and Setup Instructions Videos - FAS8300 and FAS8700 There are two videos; one showing how to rack and cable your system and one showing an example of using the System Manager Guided Setup to perform initial system configuration.
Page 4 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. 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 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 6 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 The optional data ports, optional NIC cards, and management ports on the controller modules are connected to switches.
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 Steps 1. Use the following animation or illustration to cable your controllers to two drive shelves. Cabling the controllers to SAS drive shelves 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 10 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...
Page 11 Setting drive shelf IDs 3. Plug the power cords into the controller power supplies, and then connect them to power sources on different circuits. FAS8300 and FAS8700 shown. Power on the controllers Initial booting may take up to eight minutes.
Page 12 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 13 ◦ 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 14 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 15 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. Shut down the impaired node. 4. If the type displays and the column displays anything other than yes:...
Page 16 -priv admin h. You can safely shutdown the node. 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 node.
Page 17 If the impaired node displays… Then… 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` When the impaired node shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 18 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 19 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 20 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 - FAS8300 and FAS8700 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 21 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 22 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 23 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 24 • 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 25 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 26 The changes will be implemented when the system is booted. Booting the recovery image - AFF FAS8300 and FAS8700 The procedure for booting the impaired node from the recovery image depends on whether the system is in a two-node MetroCluster configuration.
Page 27 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 28 Reboot the node. Switch back aggregates in a two-node MetroCluster configuration - AFF fas8300 and FAS8700 After you have completed the FRU replacement in a two-node MetroCluster configuration, you can perform the MetroCluster switchback operation. This returns the...
Page 29 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 30 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 31 --------------------------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 32 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 33 -auto-giveback true 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...
Page 34 Replace the caching module - FAS8300 and FAS8700 You must replace the caching module in the controller module when your system registers a single AutoSupport (ASUP) message that the module has gone offline; failure to do so results in performance degradation.
Page 35 If the impaired node is Then… displaying… The LOADER prompt Go to the next step. Waiting for giveback… Press Ctrl-C, and then respond y. System prompt or password Take over or halt the impaired node: storage failover prompt (enter system password) When the impaired takeover -ofnode impaired_node_name node shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 36 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 37 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 38 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 39 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 40 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 41 Step 4: 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 42 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 43 If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber optic cables. 2. Return the node 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 44 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 45 • 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 for eligibility and health, you must correct the issue before shutting down the false 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. • You must leave the power supplies turned on at the end of this procedure to provide power to the healthy node.
Page 47 Errors: - 8. On the impaired controller module, disconnect the power supplies. Move and replace hardware - FAS8300 and FAS8700 Step 1: Remove the controller modules To replace the chassis, you must remove the controller modules from the old chassis.
Page 48 4. Remove and set aside the cable management devices from the left and right sides of the controller module. 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 49 1. Remove the screws from the chassis mount points. 2. With two people, slide the old chassis off the rack rails in a system cabinet or equipment rack, and then set it aside. 3. If you are not already grounded, properly ground yourself. 4.
Page 50 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 - FAS8300 and FAS8700 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 51 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. Select Test system from the displayed menu to run diagnostics tests. 5.
Page 52 6. Reestablish any SnapMirror or SnapVault configurations. 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...
Page 53 This provides you a record of the procedure so that you can troubleshoot any issues that you might encounter during the replacement process. Shut down the impaired controller - FAS8300 and FAS8700 You can shut down or take over the impaired controller using different procedures, depending on the storage system hardware configuration.
Page 54 If the impaired node is Then… displaying… System prompt or password Take over or halt the impaired node: storage failover prompt (enter system password) When the impaired takeover -ofnode impaired_node_name node shows Waiting for giveback…, press Ctrl-C, and then respond y. Option 2: Controller is in a MetroCluster Do not use this procedure if your system is in a two-node MetroCluster configuration.
Page 55 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 56 Errors: - 8. On the impaired controller module, disconnect the power supplies. Move the controller module hardware - FAS8300 and FAS8700 To replace the controller module hardware, you must remove the impaired node, move FRU components to the replacement controller module, install the replacement controller...
Page 57 module in the chassis, and then boot the system to Maintenance mode. Step 1: 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 58 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 a. Press the locking tabs on the sides of the air duct in toward the middle of the controller module. b.
Page 59 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 60 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 61 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 62 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. 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):...
Page 63 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 64 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 65 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 66 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 67 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 68 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 settings as necessary.
Page 69 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 70 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.
Page 71 In the command output, you should see a message that the system ID has changed on the impaired node, showing the correct old and new IDs. In the following example, node2 has undergone replacement and has a new system ID of 151759706. node1>...
Page 72 The disks belonging to the replacement node should show the new system ID. In the following example, the disks owned by node1 now show the new system ID, 1873775277: node1> storage disk show -ownership Disk Aggregate Home Owner DR Home Home ID Owner ID DR Home ID...
Page 73 dr-group-id cluster node node-systemid dr- partner-systemid ----------- --------------------- -------------------- ------------- ------------------- 1 Cluster_A Node_A_1 536872914 118073209 1 Cluster_B Node_B_1 118073209 536872914 2 entries were displayed. 3. View the new system ID at the Maintenance mode prompt on the impaired node: disk show In this example, the new system ID is 118065481: Local System ID: 118065481...
Page 74 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 75 Return to the admin privilege level: set -privilege admin Complete system restoration - FAS8300 and FAS8700 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 76 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 77 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 78 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 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 • If you have a FAS8300 system, the system DIMMs are located in sockets 2, 4, 13, and 15. • If you have a FAS8700 system, the system DIMMs are located in slots 2, 4, 7, 9, 13, 15, 18, and 20.
Page 85 4. Eject the DIMM from its socket by slowly pushing apart the two DIMM ejector tabs on either side of the DIMM, and then slide the DIMM out of the socket. Carefully hold the DIMM by the edges to avoid pressure on the components on the DIMM circuit board.
Page 86 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 87 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 88 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 89 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 90 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 91 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. About this task If you have a cluster with more than two nodes, it must be in quorum.
Page 92 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 93 If the impaired node… Then… Has automatically switched over Proceed to the next step. 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 94 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 95 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 96 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 97 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 98 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 99 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 module, and then reenable automatic giveback.
Page 100 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 101 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 102 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 103 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 104 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 105 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. 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 106 You can use the following animation, illustration, or the written steps to replace the NVDIMM battery. Replacing the NVDIMM battery 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 107 Step 4: 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 108 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 109 2. Return the node 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 After you have completed the FRU replacement in a two-node MetroCluster configuration, you can perform the MetroCluster switchback operation.
Page 110 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 111 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; see the Administration overview with the CLI.
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 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. 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 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 117 4. Reinstall the riser: a. Align the riser with the pins to the side of the riser socket, lower the riser down on the pins. 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 4: Replace the mezzanine card The mezzanine card is located under riser number 3 (slots 4 and 5).
Page 118 c. 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. d. Lift the riser up, and then set it aside on a stable, flat surface. 2.
Page 119 module halfway into the system. Do not completely insert the controller module in the chassis until instructed to do so. 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.
Page 120 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 121 -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 122 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 123 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 124 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 125 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 126 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 127 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 128 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 129 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 130 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 131 Step 5: 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 132 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 133 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:

Fas8700Aff fas8300Aff fas8700