NetApp ASA A Series Manual

Install and maintain

page of 539

/ 539
Bookmarks

Quick Links

Download this manual

ASA A-series systems

Install and maintain

NetApp

August 11, 2023

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

August 11, 2023. Always check docs.netapp.com for the latest.

Summary of Contents for NetApp ASA A Series

Page 1 ASA A-series systems Install and maintain NetApp August 11, 2023 This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/asa150/install-setup.html on August 11, 2023. Always check docs.netapp.com for the latest.
Page 2 Table of Contents All SAN Array (ASA) A-series Systems ............ ...
Page 3 Learn how to install your system from racking and cabling, through initial system bring-up. AFF A150 System Installation and Setup Instructions if you are familiar with installing NetApp systems. The ASA A150 uses the same installation procedure as the AFF A150 system. Videos - ASA A150 Use the following videos to learn how to rack and cable your system and perform initial system configuration.
Page 4 Step 1: Prepare for installation To install your system, create an account on the NetApp Support Site, register your system, and obtain your license keys. You also need to inventory the appropriate number and type of cables for your system and collect specific network information.
Page 5 Download and complete the Cluster Configuration Worksheet. Step 2: Install the hardware Install your system in a 4-post rack or NetApp system cabinet, as applicable. Steps 1. Install the rail kits, as needed. 2. Install and secure your system using the instructions included with the rail kit.
Page 6 3. Attach cable management devices (as shown). 4. Place the bezel on the front of the system. Step 3: Cable controllers to network Cable the controllers to your network by using either the two-node switchless cluster method or the cluster interconnect network method. Management network, UTA2 data network, Ethernet data network, and management ports on the controllers are connected to switches.
Page 7 Option 1: Two-node switchless cluster Learn how to cable a two-node switchless cluster. Before you begin 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 8 2. Do one of the following: UTA2 data network configurations Use one of the following cable types to cable the UTA2 data ports to your host network. ◦ For an FC host, use 0c and 0d or 0e and 0f. ◦...
Page 9 3. Cable the e0M ports to the management network switches with the RJ45 cables. DO NOT plug in the power cords at this point. Option 2: Switched cluster Learn how to cable a switched cluster. Before you begin 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;...
Page 10 Ethernet network cabling Perform the following steps on each controller module. Steps 1. For each controller module, cable e0a and e0b to the cluster interconnect switches with the cluster interconnect cable. 2. Do one of the following:...
Page 11 UTA2 data network configurations Use one of the following cable types to cable the UTA2 data ports to your host network. ◦ For an FC host, use 0c and 0d or 0e and 0f. ◦ For an 10GbE system, use e0c and e0d or e0e and e0f.
Page 12 DO NOT plug in the power cords at this point. Step 4: Cable controllers to drive shelves Cable the controllers to your shelves using the onboard storage ports. NetApp recommends MP-HA cabling for systems with external storage. About this task If you have a SAS tape drive, you can use single-path cabling.
Page 13 3. Connect each node to IOM A in the stack. ◦ Controller 1 port 0b to IOM A port 3 on last drive shelf in the stack. ◦ Controller 2 port 0a to IOM A port 1 on the first drive shelf in the stack. mini-SAS HD to mini-SAS HD cables 4.
Page 14 Option 1: 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. Steps 1. Use the following animation to set one or more drive shelf IDs Animation - Set drive shelf IDs 2.
Page 15 b. Click network in the left pane. c. Right click and select refresh. d. 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. Configure the system using the data you collected in the ONTAP Configuration Guide.
Page 16 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: Animation - Set drive shelf IDs 3. Plug the power cords into the controller power supplies, and then connect them to power sources on different circuits.
Page 17 The format for the address is https://x.x.x.x. b. Configure the system using the data you collected in the ONTAP Configuration Guide. 7. Set up your account and download Active IQ Config Advisor: a. Log in to your existing account or create and account.
Page 18 Power supply A power supply provides a redundant power source in a controller shelf. Real time clock battery A real time clock battery preserves system date and time information if the power is off. Boot media Overview of boot media replacement - ASA A150 The boot media stores a primary and secondary set of system (boot image) files that the system uses when it boots.
Page 19 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 20 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 21 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 22 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 23 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 24 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 25 f. Copy the contents of the backup information to a separate file or your log file. You’ll need it in disaster scenarios where you might need to manually recover OKM. g. Return to admin mode: set -priv admin h. You can safely shut down the controller. Shut down the impaired controller - ASA A150 Shut down or take over the impaired controller using the appropriate procedure for your configuration.
Page 26 • 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 27 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 28 Step 2: Replace the boot media You must locate the boot media in the controller and follow the directions to replace it. Steps 1. If you are not already grounded, properly ground yourself. 2. Locate the boot media using the following illustration or the FRU map on the controller module:...
Page 29 • 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 30 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 31 Boot the recovery image - ASA A150 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 32 Restore OKM, NSE, and NVE - ASA A150 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 33 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 34 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 35 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 36 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 37 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 38 -node * -type all -message MAINT=END Return the failed part to NetApp - ASA A150 Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 39 controller: storage failover modify -node local -auto-giveback false 3. Take the impaired controller to the LOADER prompt: If the impaired controller is Then… displaying… The LOADER prompt Go to the next step. Waiting for giveback… Press Ctrl-C, and then respond when prompted.
Page 40 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 41 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 42 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 43 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 44 6. Reestablish any SnapMirror or SnapVault configurations. Step 6: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 45 • Suspend external backup jobs. • Necessary tools and equipment for the replacement. If the system is a NetApp StorageGRID or ONTAP S3 used as FabricPool cloud tier, refer to the Gracefully shutdown and power up your storage system Resolution Guide after performing this procedure.
Page 46 3. Identify the SP/BMC address of all nodes: system service-processor show -node * -fields address 4. Exit the cluster shell: exit 5. Log into SP/BMC over SSH using the IP address of any of the nodes listed in the output from the previous step.
Page 47 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. Take the impaired controller to the LOADER prompt: If the impaired controller is Then…...
Page 48 The power supplies are keyed and can only be installed one way. Do not use excessive force when sliding the power supply into the system. You can damage the connector. 7. Close the cam handle so that the latch clicks into the locked position and the power supply is fully seated. 8.
Page 49 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 50 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 51 You must verify the HA state of the chassis, switch back aggregates, 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 52 ▪ mcc-2n ▪ 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. Reboot the system. Step 2: 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 53 6. Reestablish any SnapMirror or SnapVault configurations. Step 3: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 54 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.
Page 55 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 when prompted. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt storage failover takeover -ofnode impaired_node_name...
Page 56 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 57 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 58 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 59 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 60 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 61 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 62 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 63 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 64 Restore and verify the system configuration - ASA A150 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 65 Recable the system and reassign disks - ASA A150 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 66 Option 1: Verify the system ID change on an HA system You must confirm the system ID change when you boot the replacement controller and then verify that the change was implemented. This procedure applies only to systems running ONTAP in an HA pair. 1.
Page 67 Restore onboard key management encryption keys ◦ Restore external key management encryption keys ◦ 6. 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. If you are prompted to override the system ID due to a system ID mismatch, you should enter y.
Page 68 Steps 1. If you have not already done so, reboot the replacement node, interrupt the boot process by pressing Ctrl- C, and then select the option to boot to Maintenance mode from the displayed menu. 2. You must enter when prompted to override the system ID due to a system ID mismatch. 3.
Page 69 Restore onboard key management encryption keys ◦ Restore external key management encryption keys ◦ 8. Boot the node: boot_ontap Option 3: Manually reassign the system ID on systems in a two-node MetroCluster configuration In a two-node MetroCluster configuration running ONTAP, you must manually reassign disks to the new controller’s system ID before you return the system to normal operating condition.
Page 70 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: disk reassign -s 118073209 You can respond when prompted to continue.
Page 71 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 72 If any LIFs are listed as false, revert them to their home ports: network interface revert -vserver * -lif * 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 73 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. This task only applies to two-node MetroCluster configurations. Steps 1.
Page 74 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.
Page 75 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 When you see Do you want to disable auto-giveback?, enter y.
Page 76 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 77 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 78 5. Return to Replace the DIMMs of this procedure to recheck the NVMEM LED. 6. Locate the DIMMs on your controller module. 7. Note the orientation of the DIMM in the socket so that you can insert the replacement DIMM in the proper orientation.
Page 79 Make sure that the plug locks down onto the controller module. 13. Close the controller module cover. 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.
Page 80 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 81 6. Reestablish any SnapMirror or SnapVault configurations. Step 6: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 82 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 83 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 84 -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 85 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 86 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.
Page 87 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 storage failover takeover -ofnode impaired_node_name...
Page 88 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 89 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. Remove the battery from the controller module and set it aside. 6.
Page 90 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. 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 91 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 92 6. Reestablish any SnapMirror or SnapVault configurations. Step 6: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 93 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 94 11. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information. Replace the real-time clock battery - ASA A150 You replace the real-time clock (RTC) battery in the controller module so that your system’s services and applications that depend on accurate time synchronization...
Page 95 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 storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y.
Page 96 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 97 1. If you are not already grounded, properly ground yourself. 2. Locate the RTC battery. 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 98 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. 4.
Page 99 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 100 Step 6: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information. ASA A250 systems Install and setup Start here: Choose your installation and setup experience For most configurations, you can choose from different content formats.
Page 101 Register your system. 4. Download and install NetApp Downloads: Config Advisor on your laptop. 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...
Page 102 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 103 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 to cluster Cable the controllers to a cluster by using the two-node switchless cluster method or by using the cluster interconnect network method.
Page 104 Option 1: Two-node switchless cluster The management, Fibre Channel, and data or host network ports on the controller modules are connected to switches. The cluster interconnect ports are cabled on both controller modules. Before you begin • Contact your network administrator for information about connecting the system to the switches. •...
Page 105 DO NOT plug in the power cords at this point. Option 2: Switched cluster All ports on the controllers are connected to switches; cluster interconnect, management, Fibre Channel, and data or host network switches. Before you begin • Contact your network administrator for information about connecting the system to the switches. •...
Page 106 Step 4: Cable to host network or storage (Optional) You have configuration-dependent optional cabling to the Fibre Channel or iSCSI host networks or direct- attached storage. This cabling is not exclusive; you can have cabling to a host network and storage.
Page 107 Option 1: Cable to Fibre Channel host network Fibre Channel ports on the controllers are connected to Fibre Channel host network switches. 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;...
Page 108 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. About this task Perform the following step on each controller module. Steps 1. Cable ports e4a through e4d to the 10GbE host network switches. Option 3: Cable controllers to single drive shelf Cable each controller to the NSM modules on the NS224 drive shelf.
Page 109 2. Cable controller B to the shelf. Step 5: Complete system setup 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 110 Option 1: 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. Steps 1. Plug the power cords into the controller power supplies, and then connect them to power sources on different circuits.
Page 111 Documentation Resources page for information about configuring additional features in ONTAP. Option 2: If network discovery is not enabled If network discovery is not enabled on your laptop, you must complete the configuration and setup using this task. Steps 1. Cable and configure your laptop or console: a.
Page 112 b. Configure the system using the data you collected in the ONTAP Configuration Guide. 5. Verify the health of your system by running Config Advisor. 6. 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 113 ◦ If the impaired controller is at the LOADER prompt and is part of HA configuration, log in as admin the healthy controller. ◦ If the impaired controller is in a standalone configuration and at LOADER prompt, contact mysupport.netapp.com. 2. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message:...
Page 114 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 115 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 116 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 117 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 118 over the controller so that the healthy controller continues to serve data from the impaired controller 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 controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller;...
Page 119 4. Insert your forefinger into the latching mechanism on either side of the controller module, press the lever 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).
Page 120 Thumbscrew Controller module cover. 7. Lift out the air duct cover.
Page 121 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. Due to the space constraints within the controller module, you should also have a magnet to transfer the screw on to so that you do not lose it.
Page 122 • 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 123 ◦ 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 124 7. Close the controller module cover and tighten the thumbscrew.
Page 125 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 126 ▪ dns_addr is the IP address of a name server on your network. ▪ is the Domain Name System (DNS) domain name. dns_domain If you use this optional parameter, you do not need a fully qualified domain name in the netboot server URL.
Page 127 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 128 ◦ 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 129 You must boot the ONTAP image from the USB drive, restore the file system, and verify the environmental variables. 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 130 If your system has… Then… No network connection and is in a. Press when prompted to restore the backup configuration. a 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 131 :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ 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 132 2. Use the boot_ontap command at the LOADER prompt to boot the controller. 3. Check the console output: 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.
Page 133 The system boots to Waiting for giveback… prompt. 8. Move the console cable to the partner controller and login as "admin". 9. Confirm the target controller is ready for giveback with the command. storage failover show 10. Giveback only the CFO aggregates with the storage failover giveback -fromnode local command.
Page 134 17. Move the console cable to the target controller and run the version -v command to check the ONTAP versions. 18. Restore automatic giveback if you disabled it by using the storage failover modify -node command. local -auto-giveback true == Restore NSE/NVE on systems running ONTAP 9.6 and later Steps 1.
Page 135 = Return the failed part to NetApp - ASA A250 :icons: font :relative_path: ./asa250/ :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 136 • Suspend external backup jobs. • Necessary tools and equipment for the replacement. If the system is a NetApp StorageGRID or ONTAP S3 used as FabricPool cloud tier, refer to the Gracefully shutdown and power up your storage system Resolution Guide after performing this procedure.
Page 137 3. Identify the SP/BMC address of all nodes: system service-processor show -node * -fields address 4. Exit the cluster shell: exit 5. Log into SP/BMC over SSH using the IP address of any of the nodes listed in the output from the previous step.
Page 138 2. Unplug the controller module power supplies from the source. 3. Release the power cable retainers, and then unplug the cables from the power supplies. 4. Insert your forefinger into the latching mechanism on either side of the controller module, press the lever with your thumb, and gently pull the controller a few inches out of the chassis.
Page 139 Drives are fragile. Handle them as little as possible to prevent damage to them. 3. Align the drive from the old chassis with the same bay opening in the new chassis. 4. Gently push the drive into the chassis as far as it will go. The cam handle engages and begins to rotate upward.
Page 140 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: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part...
Page 141 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in Returning SEDs to unprotected mode.
Page 142 Each SCSI-blade process should be in quorum with the other nodes in the cluster. Any issues must be resolved before you proceed with the replacement. • 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 143 Make sure that you label the cables so that you know where they came from. Use the following video or the tabulated steps to replace a controller module: Animation - Replace a controller module 1. If you are not already grounded, properly ground yourself. 2.
Page 144 Thumbscrew Controller module cover. 7. Lift out the air duct cover.
Page 145 == 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. Open the power cable retainer, and then unplug the power cable from the power supply. 3.
Page 146 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 147 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 You must move the boot media device from the impaired controller module to the replacement controller module.
Page 148 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. 2. Using the #1 magnetic screwdriver, remove the screw from the boot media, and set it aside safely on the magnet.
Page 149 Install each DIMM into the same slot it occupied in the impaired controller module. 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.
Page 150 Remove screws on the face of the controller module. 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.
Page 151 3. Repeat these steps if there is another mezzanine card in the impaired controller module. 4. Insert the SFP or QSFP modules that were removed onto the mezzanine card. == Step 7: Move the NV battery When replacing the controller module, you must move the NV battery from the impaired controller module to the replacement controller module.
Page 152 4. Locate the corresponding NV battery holder on the replacement controller module and align the NV battery to the battery holder. 5. Insert the NV battery plug into the socket. 6. 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 153 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 154 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 - ASA A250 :icons: font :relative_path: ./asa250/...
Page 155 1. In Maintenance mode from the new controller module, verify that all components display the same state: ha-config show 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 state for the controller module: ha-config modify controller ha-state The value for HA-state can be one of the following:...
Page 156 and go to the LOADER prompt: halt 2. From the LOADER prompt on the replacement controller, boot the controller, entering if you are prompted to override the system ID due to a system ID mismatch: 3. Wait until the message is displayed on the replacement controller Waiting for giveback…...
Page 157 If you are prompted to override the system ID due to a system ID mismatch, you should enter y. If the giveback is vetoed, you can consider overriding the vetoes. Find the High-Availability Configuration content for your version of ONTAP 9 b.
Page 158 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 159 -node local -auto-giveback true == Step 3: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 160 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in Returning SEDs to unprotected mode.
Page 161 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy prompt controller: storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y. == Step 2: Remove the controller module You must remove the controller module from the chassis when you replace a component inside the controller module.
Page 162 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 163 == 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 and then replace it following the specific sequence of steps. Use the following video or the tabulated steps to replace a DIMM: Animation - Replace a DIMM 1.
Page 164 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.
Page 165 2. Close the controller module cover and tighten the thumbscrew.
Page 166 You will connect the rest of the cables to the controller module later in this procedure. == Step 5: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return &...
Page 167 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 168 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 169 -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 170 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 171 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in Returning SEDs to unprotected mode.
Page 172 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 prompt controller: storage failover takeover -ofnode impaired_node_name...
Page 173 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 174 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 175 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 176 -node local -auto-giveback true == Step 5: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 177 2. Disable automatic giveback from the console of the healthy controller: storage failover modify –node local -auto-giveback false When you see Do you want to disable auto-giveback?, enter y. 3. Take the impaired controller to the LOADER prompt: If the impaired controller is Then…...
Page 178 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 179 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. Use the following video or the tabulated steps to replace a mezzanine card: Animation - Replace a mezzanine card 1.
Page 180 a. Unplug any cabling associated with the impaired mezzanine card. Make sure that you label the cables so that you know where they came from. b. Remove any SFP or QSFP modules that might be in the impaired mezzanine card and set it aside.
Page 181 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 182 -node local -auto-giveback true == Step 5: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 183 When you see Do you want to disable auto-giveback?, enter y. 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 when prompted.
Page 184 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 185 1. Locate and replace the impaired NVMEM battery on your controller module. It is recommended that you follow the illustrated instructions in the order listed. 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.
Page 186 on the side wall. 7. Press firmly down on the battery pack to make sure that it is locked into place. == 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.
Page 187 You will connect the rest of the cables to the controller module later in this procedure. == Step 5: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return &...
Page 188 Option 1: Replace an AC PSU Use the following video or the tabulated steps to replace the PSU: Animation - Replace the AC PSU 1. If you are not already grounded, properly ground yourself. 2. Identify the PSU you want to replace, based on console error messages or through the red Fault LED on the PSU.
Page 189 Secure the power cable to the PSU using the power cable retainer. Once power is restored to the PSU, the status LED should be green. 7. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See Part Return & Replacements page for further information.
Page 190 Secure the power cable to the PSU with the thumbscrews. Once power is restored to the PSU, the status LED should be green. 7. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See Part Return & Replacements page for further information.
Page 191 • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in Returning SEDs to unprotected mode. • If you have a SAN system, you must have checked event messages (cluster kernel-service show) for impaired controller SCSI blade. The...
Page 192 1. If you are not already grounded, properly ground yourself. 2. Unplug the controller module power supplies from the source. 3. Release the power cable retainers, and then unplug the cables from the power supplies. 4. Insert your forefinger into the latching mechanism on either side of the controller module, press the lever with your thumb, and gently pull the controller a few inches out of the chassis.
Page 193 Thumbscrew Controller module cover. 7. Lift out the air duct cover.
Page 194 == Step 3: Replace the RTC battery To replace the RTC battery, locate it inside the controller and follow the specific sequence of steps. Use the following video or the tabulated steps to replace the RTC battery: Animation - Replace the RTC battery 1.
Page 195 Gently pull tab away from the battery housing. Attention: Pulling it away aggressively might displace the tab. Lift the battery up. Note: Make a note of the polarity of the battery. The battery should eject out. The battery will be ejected out. 2.
Page 196 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. Pushing it in aggressively might cause the battery to eject out again.
Page 197 -node local -auto-giveback true == Step 5: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 198 This page gives graphic instructions for a typical installation of your system from racking and cabling, through initial system bring-up. Use this guide if you are familiar with installing NetApp systems. Access the Installation and Setup Instructions PDF poster: AFF A400 Installation and Setup Instructions The ASA A400 uses the same installation procedure as the AFF A400 system.
Page 199 :icons: font :relative_path: ./asa400/ :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ This page provides detailed step-by-step instructions for installing a typical NetApp system. Use this guide if you want more detailed installation instructions. == Step 1: Prepare for installation To install your system, you need to create an account, register the system, and get license keys. You also need to inventory the appropriate number and type of cables for your system and collect specific network information.
Page 200 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...
Page 201 You need to install your system in a 4-post rack or NetApp system cabinet, as applicable. 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.
Page 202 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: Animation - Two-node switchless cluster cabling 2.
Page 203 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: Animation - Switched cluster cabling 2.
Page 204 Be sure to check the illustration arrow for the proper cable connector pull-tab orientation. The cable pull- tab for the NS224 are up. 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 205 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. Animation - Cable the controllers to one NS224 drive shelf 2.
Page 206 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. Steps 1. Use the following illustration to cable your controllers to two drive shelves. Animation - Cable the controllers to SAS drive shelves...
Page 207 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 208 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. Set up your account and download Active IQ Config Advisor: a.
Page 209 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 210 :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ For the ASA A400 storage system, you can perform maintenance procedures on the following components. == Boot media The boot media stores a primary and secondary set of boot image files that the system uses when it boots. == Chassis The chassis is the physical enclosure housing all the controller components such as the controller/CPU unit, power supply, and I/O.
Page 211 ◦ If the impaired controller is at the LOADER prompt and is part of HA configuration, log in as on the healthy controller. admin ◦ If the impaired controller is in a standalone configuration and at LOADER prompt, contact mysupport.netapp.com.
Page 212 == 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 213 Restored than 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 Restored column equals for all authentication keys:...
Page 214 Restored than 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 Restored column equals for all authentication keys:...
Page 215 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 216 output to your log file. This command may not work if the boot device is corrupted or non-functional. == Option 2: Controller is in a MetroCluster configuration 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 217 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 218 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 219 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. == Step 1: Remove the controller module To access components inside the controller module, you must remove the controller module from the chassis.
Page 220 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 221 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 222 ◦ If NVE is enabled, download the image with NetApp Volume Encryption, as indicated in the download button. ◦ 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.
Page 223 6. Insert the USB flash drive into the USB slot on the controller module. Make sure that you install the USB flash drive in the slot labeled for USB devices, and not in the USB console port. 7. Complete the installation of the controller module: a.
Page 224 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. When prompted, either enter the name of the image or accept the default image displayed inside the brackets on your screen.
Page 225 *If you see… Then…* The login prompt Go to the next Step. Waiting for giveback… a. Log into the partner controller. b. Confirm the target controller is ready for giveback with the command. storage failover show 7. Connect the console cable to the partner controller. 8.
Page 226 d. Save your changes using the savenv command. e. Reboot the node. = Switch back aggregates in a two-node MetroCluster configuration - ASA A400 :icons: font :relative_path: ./asa400/ :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ After you have completed the FRU replacement in a two-node MetroCluster configuration, you can perform the MetroCluster switchback operation.
Page 227 :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ 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 228 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 229 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 230 18. Restore automatic giveback if you disabled it by using the storage failover modify -node command. local -auto-giveback true == 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.
Page 231 = Return the failed part to NetApp - ASA A400 :icons: font :relative_path: ./asa400/ :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 232 • Suspend external backup jobs. • Necessary tools and equipment for the replacement. If the system is a NetApp StorageGRID or ONTAP S3 used as FabricPool cloud tier, refer to the Gracefully shutdown and power up your storage system Resolution Guide after performing this procedure.
Page 233 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 234 If the impaired controller… Then… 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 235 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 236 Make sure that you support the bottom of the controller module as you slide it out of the chassis. 7. Set the controller module aside in a safe place, and repeat these steps for the other controller module in the chassis. == Step 2: Move the fans To move the fan modules to the replacement chassis when replacing the chassis, you must perform a specific sequence of tasks.
Page 237 4. Repeat the preceding steps to install the second controller into the new chassis. = Complete chassis replacement - ASA A400 :icons: font :relative_path: ./asa400/ :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ You must verify the HA state of the chassis and return the failed part to NetApp, as...
Page 238 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 239 If a switchback is taking a long time to finish, you can check on the status of in-progress baselines by using the command. metrocluster config-replication resync-status show 6. Reestablish any SnapMirror or SnapVault configurations. == Step 3: Return the failed part to NetApp...
Page 240 Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information. = Controller = Overview of controller replacement - ASA A400 :icons: font :relative_path: ./asa400/ :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/...
Page 241 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.
Page 242 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 243 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 244 :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ 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. == Step 1: Remove the controller module To access components inside the controller module, you must remove the controller module from the chassis.
Page 245 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: Animation - Remove the empty risers from the replacement controller module a.
Page 246 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 247 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 248 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. Rotate the boot media up and gently pull the boot media out of the socket. 2.
Page 249 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 250 You can use the following animation, illustration, or the written steps to move the DIMMs from the impaired controller module to the replacement controller module. Animation - Move the DIMMs 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.
Page 251 d. Visually inspect the DIMM to verify that it is evenly aligned and fully inserted into the socket. e. Repeat these substeps for the remaining DIMMs. 5. Plug the NVDIMM battery into the motherboard. Make sure that the plug locks down onto the controller module. == Step 7: 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...
Page 252 b. Using the locking latches, firmly push the controller module into the chassis until the locking latches begin to rise. 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 253 3. At the LOADER prompt, check the date and time on the replacement node: show date The date and time are given in GMT. 4. If necessary, set the date in GMT on the replacement node: set date mm/dd/yyyy 5. If necessary, set the time in GMT on the replacement node: set time hh:mm:ss 6.
Page 254 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 255 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. Return to the admin privilege level: set -privilege admin 5.
Page 256 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 257 If any LIFs are listed as false, revert them to their home ports: network interface revert -vserver * -lif * 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 258 3. If an AutoSupport maintenance window was triggered, end it by using the system node command. autosupport invoke -node * -type all -message MAINT=END 4. If automatic giveback was disabled, reenable it: storage failover modify -node local -auto-giveback true == Step 3: 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 259 6. Reestablish any SnapMirror or SnapVault configurations. == Step 4: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 260 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.
Page 261 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 262 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 263 chassis. You can use the following animation, illustration, or the written steps to remove the controller module from the chassis. Animation - Remove the controller module 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 264 The animation and illustration show empty slots for sockets without DIMMs. These empty sockets are populated with blanks. Animation - Replace a system DIMM The DIMMs are located in sockets 2, 4, 13, and 15. The NVDIMM is located in slot 11. 1.
Page 265 Carefully hold the DIMM by the edges to avoid pressure on the components on the DIMM circuit board. 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.
Page 266 Do not completely insert the controller module in the chassis until instructed to do so. 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.
Page 267 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 268 6. Reestablish any SnapMirror or SnapVault configurations. == Step 7: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 269 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 270 10. Align the bezel with the ball studs, and then gently push the bezel onto the ball studs. 11. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 271 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.
Page 272 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 273 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 274 chassis. You can use the following animations, illustration, or the written steps to remove the controller module from the chassis. Animation - Remove the controller module 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 275 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. Animation - Replace the NVDIMM battery 1.
Page 276 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 277 f. At the LOADER prompt, enter to reinitialize the PCIe cards and other components. == Step 5: Restore the controller module to operation You must recable the system, give back the controller module, and then reenable automatic giveback. 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.
Page 278 6. Reestablish any SnapMirror or SnapVault configurations. == Step 7: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 279 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.
Page 280 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 281 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 282 chassis. You can use the following animations, illustration, or the written steps to remove the controller module from the chassis. Animation - Remove the controller module 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 283 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 284 and then align it to the slot. The notch among the pins on the NVDIMM should line up with the tab in the socket. 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.
Page 285 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 286 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 287 6. Reestablish any SnapMirror or SnapVault configurations. == Step 7: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 288 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.
Page 289 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 290 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 291 chassis. You can use the following animations, illustration, or the written steps to remove the controller module from the chassis. Animation - Remove the controller module 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 292 Animation - Replace a PCIe card 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 293 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). You must remove that riser to access the mezzanine card, replace the mezzanine card, and then reinstall riser number 3.
Page 294 == 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. You can use the following animation, illustration, or the written steps to install the controller module in the chassis.
Page 295 interrupt the boot process. 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 296 If a switchback is taking a long time to finish, you can check on the status of in-progress baselines by using the command. metrocluster config-replication resync-status show 6. Reestablish any SnapMirror or SnapVault configurations. == Step 8: Return the failed part to NetApp...
Page 297 Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information. = Replacing a power supply - ASA A400 :icons: font :relative_path: ./asa400/ :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/...
Page 298 Secure the power cable to the power supply using the power cable retainer. Once power is restored to the power supply, the status LED should be green. 8. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 299 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.
Page 300 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 301 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 302 chassis. You can use the following animations, illustration, or the written steps to remove the controller module from the chassis. Animation - Remove the controller module 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 303 Animation - Replace the RTC battery 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.
Page 304 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 305 6. Reset the time and date on the controller: a. Check the date and time on the healthy controller with the command. show date b. At the LOADER prompt on the target controller, check the time and date. c. If necessary, modify the date with the command.
Page 306 6. Reestablish any SnapMirror or SnapVault configurations. == Step 6: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 307 Use the AFF A800 Installation and Setup Instructions if you are familiar with installing NetApp systems. The ASA A800 uses the same installation procedure as the AFF A800 system. = Videos - ASA A800 :icons: font :relative_path: ./asa800/...
Page 308 (NetApp Product Registration) your system. 2. Download and install NetApp Downloads: Config Advisor on your laptop. 3. 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...
Page 309 4. Download and complete the 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. Installing SuperRail into a four-post rack 2.
Page 310 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. There is optional cabling to the Fibre Channel or iSCSI host networks or direct-attached storage.
Page 311 Step Perform on each controller module Cable the HA interconnect ports: • e0b to e0b • e1b to e1b Cable the cluster interconnect ports: • e0a to e0a • e1a to e1a...
Page 312 Step Perform on each controller module Cable the management ports to the management network switches DO NOT plug in the power cords at this point. 2. To perform optional cabling, see: [Option 1: Connect to a Fibre Channel host] ◦ [Option 2: Connect to a 10GbE host] ◦...
Page 313 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 the tabulated steps to complete the cabling between the controllers and the switches: Animation - Cable a switched cluster Step...
Page 314 Step Perform on each controller module Cable the cluster interconnect ports to the 100 GbE cluster interconnect switches. Cable the management ports to the management network switches DO NOT plug in the power cords at this point. 2. To perform optional cabling, see:...
Page 315 [Option 1: Connect to a Fibre Channel host] ◦ [Option 2: Connect to a 10GbE host] ◦ [Option 3: Connect to a single direct-attached NS224 drive shelf] ◦ [Option 4: Connect to two direct-attached NS224 drive shelves] ◦ 3. To complete setting up your system, see Step 4: Complete system setup and configuration.
Page 316 Step Perform on each controller module Cable ports 2a through 2d to the FC host switches. To perform other optional cabling, choose from: • [Option 3: Connect to a single direct-attached NS224 drive shelf] • [Option 4: Connect to two direct-attached NS224 drive shelves] To complete setting up your system, see Step 4: Complete system setup and configuration.
Page 317 Step Perform on each controller module Cable ports e4a through e4d to the 10GbE host network switches. To perform other optional cabling, choose from: • [Option 3: Connect to a single direct-attached NS224 drive shelf] • [Option 4: Connect to two direct-attached NS224 drive shelves] To complete setting up your system, see Step 4: Complete system setup and configuration.
Page 318 Step Perform on each controller module Cable controller A to the shelf: Cable controller B to the shelf: To complete setting up your system, see Step 4: Complete system setup and configuration. ==== Option 4: Cable the controllers to two drive shelves...
Page 319 You must cable each controller to the NSM modules on both NS224 drive shelves. Before you begin 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 320 Step Perform on each controller module Cable controller B to the shelves: To complete setting up your system, see Step 4: Complete system setup and configuration. == Step 4: Complete system setup and configuration 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 321 3. Use the animation to connect your laptop to the Management switch: Animation - Connect your laptop to the Management switch 4. Select an ONTAP icon listed to discover: a. Open File Explorer. b. Click Network in the left pane. c.
Page 322 using the console cable that came with your system. 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.
Page 323 If the management network Then… has DHCP… Not configured a. Open a console session using PuTTY, a terminal server, or the equivalent for your environment. Check your laptop or console’s online help if you do not know how to configure PuTTY. b.
Page 324 ◦ If the impaired controller is at the LOADER prompt and is part of HA configuration, log in as on the healthy controller. admin ◦ If the impaired controller is in a standalone configuration and at LOADER prompt, contact mysupport.netapp.com.
Page 325 == 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 326 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 column displays for all authentication keys and that all key...
Page 327 .. 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 a. Verify that the column displays for all authentication keys and that all key managers...
Page 328 == 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 329 Restored than 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 330 Restored than 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 331 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 332 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 333 You must remove the controller module from the chassis when you replace the controller module or replace a component inside the controller module. 1. If you are not already grounded, properly ground yourself. 2. Unplug the controller module power supplies from the source. 3.
Page 334 a. Press in the locking tabs on the sides of the air duct toward the middle of the controller module. b. Slide the air duct toward the fan modules, and then rotate it upward to its completely open position. Air duct locking tabs Slide air duct towards fan modules Rotate air duct towards fan modules == Step 2: Replace the boot media...
Page 335 Air duct Riser 3 Phillips #1 screwdriver Boot media screw Boot media 2. Remove the boot media from the controller module: a. Using a #1 Phillips head screwdriver, remove the screw holding down the boot media and set the screw aside in a safe place. b.
Page 336 ◦ If NVE is enabled, download the image with NetApp Volume Encryption, as indicated in the download button. ◦ 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.
Page 337 Air duct Risers 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. 4. Reinstall the cable management device and recable the system, as needed. When recabling, remember to reinstall the media converters (SFPs or QSFPs) if they were removed.
Page 338 == 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 339 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 column displays for all authentication keys and that all key...
Page 340 .. 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 a. Verify that the column displays for all authentication keys and that all key managers...
Page 341 == 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 342 Restored than 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 343 Key Manager external Restored than 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...
Page 344 :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ 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 345 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… displays… The LOADER prompt Boot the controller to the boot menu: boot_ontap menu Waiting for giveback…...
Page 346 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. Confirm the target controller is ready for giveback with the command.
Page 347 15. Move the console cable to the partner controller. 16. Give back the target controller using the storage failover giveback -fromnode local command. 17. Check the giveback status, 3 minutes after it reports complete, using the storage failover show command. If giveback is not complete after 20 minutes, contact Customer Support.
Page 348 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 349 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… displays… The login prompt Go to Step 7. Waiting for giveback… a.
Page 350 = Return the failed part to NetApp - ASA A800 :icons: font :relative_path: ./asa800/ :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 351 • Suspend external backup jobs. • Necessary tools and equipment for the replacement. If the system is a NetApp StorageGRID or ONTAP S3 used as FabricPool cloud tier, refer to the Gracefully shutdown and power up your storage system Resolution Guide after performing this procedure.
Page 352 5. Log into SP/BMC over SSH using the IP address of any of the nodes listed in the output from the previous step. If your’re using a console/laptop, log into the controller using the same cluster administrator credentials. Open an SSH session to every SP/BMC connection so that you can monitor progress. 6.
Page 353 The controller module moves slightly out of the chassis. Locking latch Locking pin 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.
Page 354 Drives are fragile. Handle them as little as possible to prevent damage to them. 3. Align the drive from the old chassis with the same bay opening in the new chassis. 4. Gently push the drive into the chassis as far as it will go. The cam handle engages and begins to rotate upward.
Page 355 4. Reinstall the bezel on the front of the system. == Step 2: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements...
Page 356 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in Returning SEDs to unprotected mode.
Page 357 • If you have a SAN system, you must have checked event messages (cluster kernel-service show) for impaired controller SCSI blade. The command cluster kernel-service show displays the node name, quorum status of that node, availability status of that node, and operational status of that node.
Page 358 == Step 1: Remove the controller module You must remove the controller module from the chassis when you replace the controller module or replace a component inside the controller module. 1. On the front of the chassis, use your thumbs to firmly push each drive in until you feel a positive stop. This ensures that the drives are firmly seated against the chassis midplane.
Page 359 Locking latch Locking pin 8. Slide the controller module out of the chassis and place it on a stable, flat surface. Make sure that you support the bottom of the controller module as you slide it out of the chassis. 9.
Page 360 Air duct locking tabs Slide air duct towards fan modules Rotate air duct towards fan modules == Step 2: Move the power supplies You must move the power supplies from the impaired controller module to the replacement controller module when you replace a controller module. 1.
Page 361 Blue power supply locking tab Power supply 2. Move the power supply to the new controller module, and then install it. 3. 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 362 Fan locking tabs Fan module 2. Move the fan module to the replacement controller module, and then install the fan module by aligning its edges with the opening in the controller module, and then sliding the fan module into the controller module until the locking latches click into place.
Page 363 Air duct riser NVDIMM battery plug NVDIMM battery pack Attention: The NVDIMM battery control board LED blinks while destaging contents to the flash memory when you halt the system. After the destage is complete, the LED turns off. 2. 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.
Page 364 == Step 5: Remove the PCIe risers As part of the controller replacement process, you must remove the PCIe modules from the impaired controller module. You must install them into the same location in the replacement controller module once the NVDIMMS and DIMMs have moved to the replacement controller module. 1.
Page 365 controller module in the proper orientation. 2. 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 366 Air duct NVDIMMs 2. Note the orientation of the NVDIMM in the socket so that you can insert the NVDIMM in the replacement controller module in the proper orientation. 3. 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 367 Air duct Riser 3 Phillips #1 screwdriver Boot media screw Boot media 2. Remove the boot media from the controller module: a. Using a #1 Phillips head screwdriver, remove the screw holding down the boot media and set the screw aside in a safe place. b.
Page 368 You install the PCIe risers in the replacement controller module after moving the DIMMs, NVDIMMs, and boot media. 1. Install the riser into the replacement controller module: a. Align the lip of the riser with the underside of the controller module sheet metal. b.
Page 369 Locking tabs Slide plunger 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 370 module in an HA pair, or against a reliable time server in a stand-alone configuration. If the time and date do not match, you must reset them on the replacement controller module to prevent possible outages on clients due to time differences. About this task It is important that you apply the commands in the steps on the correct systems: •...
Page 371 = Recable the system and reassign disks - ASA A800 :icons: font :relative_path: ./asa800/ :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ Continue the replacement procedure by recabling the storage and confirming disk reassignment. == Step 1: Recable the system Recable the controller module’s storage and network connections. Steps 1.
Page 372 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 373 changed on partner message. 7. Verify that the disks were assigned correctly: storage disk show -ownership The disks belonging to the replacement controller should show the new system ID. In the following example, the disks owned by node1 now show the new system ID, 1873775277: node1>...
Page 374 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 375 -node local -auto-giveback true == Step 3: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 376 provider. == Step 1: Shut down the impaired controller 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 377 Locking latch Locking pin 7. 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. 8. Place the controller module on a stable, flat surface, and then open the air duct: a.
Page 378 Air duct locking tabs Slide air duct towards fan modules Rotate air duct towards fan modules == 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 and then replace it following the specific sequence of steps.
Page 379 Air duct cover Riser 1 and DIMM bank 1, and 3-6 Riser 2 and DIMM Riser 3 and DIMM 19 -22 and 24 bank 7-10, 12-13, and 15-18 Note: Slot 2 and 14 are left empty. Do not attempt to install DIMMs into these slots. 2.
Page 380 Carefully hold the DIMM by the edges to avoid pressure on the components on the DIMM circuit board. 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.
Page 381 Locking tabs Slide plunger 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 382 If you have not already done so, reinstall the cable management device. == Step 5: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return &...
Page 383 Procedure Replace the failed drive by selecting the option appropriate to the drives that your platform supports.
Page 384 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 385 -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 386 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 387 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in Returning SEDs to unprotected mode.
Page 388 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 prompt controller: storage failover takeover -ofnode impaired_node_name...
Page 389 Locking latch Locking pin 7. 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. 8. Set the controller module aside in a safe place. == Step 3: Replace a fan To replace a fan, remove the failed fan module and replace it with a new fan module.
Page 390 Fan locking tabs 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 until the locking latches click into place. == 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 391 -controller local -auto-giveback true == Step 5: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 392 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. Disable automatic giveback from the console of the healthy controller: storage failover modify –node local -auto-giveback false When you see Do you want to disable auto-giveback?, enter y.
Page 393 Locking latch Locking pin 7. 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. 8. Place the controller module on a stable, flat surface, and then open the air duct: a.
Page 394 Air duct locking tabs Slide air duct towards fan modules Rotate air duct towards fan modules == Step 3: Replace the NVDIMM To replace the NVDIMM, you must locate it in the controller module using the NVDIMM map label on top of the air duct, and then replace it following the specific sequence of steps.
Page 395 Air duct cover Riser 2 and NVDIMM 11 2. Note the orientation of the NVDIMM in the socket so that you can insert the NVDIMM in the replacement controller module in the proper orientation. 3. 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 396 5. Locate the slot where you are installing the NVDIMM. 6. 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 397 If you have not already done so, reinstall the cable management device. == Step 4: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return &...
Page 398 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in Returning SEDs to unprotected mode. • If you have a SAN system, you must have checked event messages (cluster kernel-service show) for impaired controller SCSI blade.
Page 399 2. Unplug the controller module power supplies from the source. 3. Release the power cable retainers, and then unplug the cables from the power supplies. 4. Loosen the hook and loop strap binding the cables to the cable management device, and then unplug the system cables and SFP and QSFP modules (if needed) from the controller module, keeping track of where the cables were connected.
Page 400 the replacement battery into the controller module. 1. Open the air duct cover and locate the NVDIMM battery in the riser. Air duct riser NVDIMM battery plug NVDIMM battery pack Attention: The NVDIMM battery control board LED blinks while destaging contents to the flash memory when you halt the system.
Page 401 If you have not already done so, reinstall the cable management device. == Step 5: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return &...
Page 402 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in Returning SEDs to unprotected mode.
Page 403 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy prompt controller: storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y. == Step 2: Remove the controller module You must remove the controller module from the chassis when you replace the controller module or replace a component inside the controller module.
Page 404 Locking latch Locking pin 7. 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. 8. Place the controller module on a stable, flat surface, and then open the air duct: a.
Page 405 ◦ If you are replacing the 100GbE PCIe card in Riser 1, use Steps 2 - 3 and Steps 6 - 7. ◦ If you are replacing a PCIe card from Riser 2 or 3, use Steps 4 through 7. 2.
Page 406 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 the fan modules. The riser raises up slightly from the controller module. c.
Page 407 b. For Riser 2 or 3, close the side panel. c. Swing the locking latch into place until it clicks into the locked position. 7. Install the riser into the controller module: a. Align the lip of the riser with the underside of the controller module sheet metal. b.
Page 408 -node local -auto-giveback true == Step 5: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 409 Do not mix PSUs with different efficiency ratings or different input types. Always replace like for like. Use the appropriate procedure for your type of PSU: AC or DC.
Page 410 Option 1: Replace an AC PSU To replace an AC PSU, complete the following steps. 1. If you are not already grounded, properly ground yourself. 2. Identify the PSU you want to replace, based on console error messages or through the red Fault LED on the PSU.
Page 411 Secure the power cable to the PSU using the power cable retainer. Once power is restored to the PSU, the status LED should be green. 7. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See Part Return & Replacements page for further information.
Page 412 Secure the power cable to the PSU with the thumbscrews. Once power is restored to the PSU, the status LED should be green. 7. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See Part Return & Replacements page for further information.
Page 413 displays the node name, quorum status of that node, availability status of that node, and operational status of that node. Each SCSI-blade process should be in quorum with the other nodes in the cluster. Any issues must be resolved before you proceed with the replacement. •...
Page 414 Leave the cables in the cable management device so that when you reinstall the cable management device, the cables are organized. 5. Remove the cable management device from the controller module and set it aside. 6. 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.
Page 415 Air duct locking tabs Slide air duct towards fan modules Rotate air duct towards fan modules == Step 3: Remove the PCIe risers You must remove one or more PCIe risers when replacing specific hardware components in the controller module. 1.
Page 416 Air duct Riser 2 (middle riser) locking latch == Step 4: Replace the RTC battery To replace the RTC battery, locate it inside the controller and follow the specific sequence of steps. 1. Locate the RTC battery under Riser 2.
Page 417 Air duct Riser 2 RTC battery and housing 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 418 -node local -auto-giveback true == Step 7: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 419 This page provides graphic instructions for a typical installation of your system from racking and cabling, through initial system bring-up. Use this content if you are familiar with installing NetApp systems. Access the Installation and Setup Instructions PDF poster: AFF A900 Installation and Setup Instructions The ASA A900 uses the same installation procedure as the AFF A900 system.
Page 420 == Step 1: Prepare for installation To install your system, you need to create an account on the NetApp Support Site, register your system, and get license keys. You also need to inventory the appropriate number and type of cables for your system and collect specific network information.
Page 421 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. 1. Install the rail kits, as needed.
Page 422 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. Place the bezel on the front of the system. The following diagram shows a representation of what a typical system looks like and where the major components are located at the rear of the system:...
Page 423 == 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.
Page 424 Option 1: Two-node switchless cluster Management network, data network, and management ports on the controllers are connected to switches. The cluster interconnect ports are cabled on both controllers. Before you begin You must have contacted your network administrator for information about connecting the system to the switches.
Page 425 Step Perform on each controller Cable controller management (wrench) ports. Cable 25 GbE network switches: Ports in slot A3 and B3 (e3a and e3c) and slot A9 and B9 (e9a and e9c) to the 25 GbE network switches. 40GbE host network switches: Cable host‐side b ports in slot A4 and B4 (e4b) and slot A8 and B8 (e8b) to the host switch.
Page 426 As you insert the connector, you should feel it click into place; if you do not feel it click, remove it, turn it over and try again. 1. Use the animation or illustration to complete the cabling between the controllers and to the switches: Animation - Cable a switched cluster To cluster switches...
Page 427 Step Perform on each controller Cable 25GbE network switches: Ports in slot A3 and B3 (e3a and e3c) and slot A9 and B9 (e9a and e9c) to the 25 GbE network switches. 40GbE host network switches: Cable host‐side b ports in slot A4 and B4 (e4b) and slot A8 and B8 (e8b) to the host switch.
Page 428 Option 1: Cable the controllers to a single NS224 drive shelf You must cable each controller to the NSM modules on the NS224 drive shelf. Before you begin • 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 429 Step Perform on each controller • Connect controller A port e2a to port e0a on NSM A on the shelf. • Connect controller A port e10b to port e0b on NSM B on the shelf. 100 GbE cable • Connect controller B port e2a to port e0a on NSM B on the shelf.
Page 431 Step Perform on each controller • Connect controller A port e2a to NSM A e0a on shelf 1. • Connect controller A port e10b to NSM B e0b on shelf 1. • Connect controller A port e2b to NSM B e0b on shelf 2.
Page 432 Option 1: 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. 1. Use the following animation or drawing to set one or more drive shelf IDs: The NS224 shelves are pre-set to shelf ID 00 and 01.
Page 433 Initial booting may take up to eight minutes. 3. Make sure that your laptop has network discovery enabled. See your laptop’s online help for more information. 4. Use the following animation to connect your laptop to the Management switch. Animation - Connect your laptop to the Management switch 5.
Page 434 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 435 The NS224 shelves are pre-set to shelf ID 00 and 01. If you want to change the shelf IDs, you must create a tool to insert into the hole where button is located. see Change a shelf ID - NS224 shelves for detailed instructions.
Page 436 Log in to your existing account or create an account. NetApp Support Registration b. Register your system. NetApp Product Registration c. Download Active IQ Config Advisor. NetApp Downloads: Config Advisor 7. Verify the health of your system by running Config Advisor.
Page 437 8. 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. = Maintain = Maintain ASA A900 hardware :icons: font :relative_path: ./asa900/ :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ For the ASA A900 storage system, you can perform maintenance procedures on the following components.
Page 438 The NVRAM module (Non-Volatile Random Access Memory) allows the controller to retain data across power cycles or system reboots. == Power supply A power supply provides a redundant power source in a controller shelf. == Real-time clock battery A real time clock battery preserves system date and time information if the power is off. = Boot media = Replace the boot media - ASA A900 :icons: font...
Page 439 NVE, proceed to shut down the controller. == 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 440 Restored than 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 441 Restored than 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 442 Enter the onboard security key-manager sync command: security key-manager onboard sync 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:...
Page 443 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.
Page 444 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy prompt controller: storage failover takeover -ofnode impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y. Controller is in a MetroCluster After completing the NVE or NSE tasks, you need to complete the shutdown of the impaired controller.
Page 445 If the impaired controller is Then… displaying… System prompt or password Take over or halt the impaired controller from the healthy prompt (enter system controller: storage failover takeover -ofnode password) impaired_node_name When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y. = Replace the boot media - ASA A900 You must remove and open the controller module, locate and replace the boot media in the controller, and then transfer the image to the replacement boot media.
Page 446 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 447 slide the cover to the back of the controller module, and then swing the cover up and lift it off of the controller module. Controller module cover locking button == Step 2: Replace the boot media :icons: font :relative_path: ./_include/ :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ You must locate the boot media in the controller and follow the directions to replace it.
Page 448 Press release tab Boot media 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 449 ◦ If NVE is enabled, download the image with NetApp Volume Encryption, as indicated in the download button. ◦ If NVE is not enabled, download the image without NetApp Volume Encryption, as indicated in the download button. • 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 450 The target port you configure is the target port you use to communicate with the impaired controller from the healthy controller during var file system restore with a network connection. You can also use the e0M port in this command. ◦...
Page 451 If your system has… Then… A network connection a. Press when prompted to restore the backup configuration. b. Press when prompted to overwrite /etc/ssh/ssh_host_ecdsa_key. c. Press when prompted to confirm if the restore backup was successful. d. Press when prompted to the restored configuration copy. e.
Page 452 If your system has… Then… No network connection and is in a. Press when prompted to restore the backup configuration. a 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 453 :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ After environment variables are checked, you must complete steps specific to restore Onboard Key Manager (OKM), NetApp Storage Encryption (NSE) and NetApp Volume Encryption (NVE). 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 454 3. Check the console output: 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 455 The system boots to Waiting for giveback… prompt. 8. Move the console cable to the partner controller and log in as admin. 9. Confirm the target controller is ready for giveback with the command. storage failover show 10. Give back only the CFO aggregates with the storage failover giveback -fromnode local command.
Page 456 17. Move the console cable to the target controller and run the version -v command to check the ONTAP versions. 18. Restore automatic giveback if you disabled it by using the storage failover modify -node command. local -auto-giveback true == Restore NSE/NVE on systems running ONTAP 9.6 and later 1.
Page 457 = Return the failed part to NetApp - ASA A900 :icons: font :relative_path: ./asa900/ :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 458 • Suspend external backup jobs. • Necessary tools and equipment for the replacement. If the system is a NetApp StorageGRID or ONTAP S3 used as FabricPool cloud tier, refer to the Gracefully shutdown and power up your storage system Resolution Guide after performing this procedure.
Page 459 credentials. Open an SSH session to every SP/BMC connection so that you can monitor progress. 6. Halt all nodes in the cluster: system node halt -node * -skip-lif-migration-before-shutdown true -ignore -quorum-warnings true -inhibit-takeover true. For clusters using SnapMirror synchronous operating in StrictSync mode: system node halt -node * -skip-lif-migration-before-shutdown true -ignore-quorum-warnings true -inhibit-takeover true -ignore...
Page 460 Locking button 4. Repeat the preceding steps for any remaining power supplies. == Step 2: Remove the fans You must remove the six fan modules, located on in the front of the chassis, when replacing the chassis. 1. If you are not already grounded, properly ground yourself. 2.
Page 461 Terra cotta locking button Slide fan in/out of chassis 4. Set the fan module aside. 5. Repeat the preceding steps for any remaining fan modules. == Step 3: Remove the controller module To replace the chassis, you must remove the controller module or modules from the impaired chassis. 1.
Page 462 Cam handle locking 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 463 that it can be installed into the same slot in the replacement chassis.. 6. Repeat these steps if you have another controller module in the chassis. == Step 4: Remove the I/O modules To remove I/O modules from the impaired chassis, including the NVRAM modules, follow the specific sequence of steps.
Page 464 Lettered and numbered I/O cam latch I/O cam latch completely unlocked 4. Set the I/O module aside. 5. Repeat the preceding step for the remaining I/O modules in the impaired chassis. == Step 5: Remove the de-stage controller power module Remove the two de-stage controller power modules from the front of the impaired chassis.
Page 465 DCPM terra cotta locking button 3. Set the DCPM aside in a safe place and repeat this step for the remaining DCPM. == Step 6: Remove the USB LED module Remove the USB LED modules. Animation - Remove/install USB...
Page 466 Eject the module. Slide out of chassis. 1. Locate the USB LED module on the front of the impaired chassis, directly under the DCPM bays. 2. Press the black locking button on the right side of the module to release the module from the chassis, and then slide it out of the impaired chassis.
Page 467 by guiding the chassis onto the rack rails in a system cabinet or L brackets in an equipment rack. 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 impaired chassis.
Page 468 4. Repeat the preceding step for the remaining I/O modules that you set aside. If the impaired chassis has blank I/O panels, move them to the replacement chassis at this time. == Step 11: Install the power supplies Installing the power supplies when replacing a chassis involves installing the power supplies into the replacement chassis, and connecting to the power source.
Page 469 the controller module in until it meets the midplane and is fully seated, and then close the cam handle until it clicks into the locked position. Do not use excessive force when sliding the controller module into the chassis; you might damage the connectors.
Page 470 • Check system health using How_to_perform_a_cluster_health_check_with_a_script_in_ONTAP == Step 3: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 471 so that the replacement controller will boot up in the same version of ONTAP as the old controller module. • It is important that you apply the commands in these steps on the correct systems: ◦ The impaired controller is the controller that is being replaced. ◦...
Page 472 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.
Page 473 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 474 controller module in the chassis, and then boot the system to Maintenance mode. The following animation shows the whole process of moving components from the impaired to the replacement controller. Animation - Move components to replacement controller == 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 475 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 476 slide the cover to the back of the controller module, and then swing the cover up and lift it off of the controller module. Controller module cover locking button == 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.
Page 477 Press release tab Boot media 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 478 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.
Page 479 DIMM ejector tabs 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.
Page 480 reinsert it. Visually inspect the DIMM to verify that it is evenly aligned and fully inserted into the slot. 8. Push carefully, but firmly, on the top edge of the DIMM until the ejector tabs snap into place over the notches at the ends of the DIMM.
Page 481 Cam handle release button Cam handle Do not completely insert the controller module in the chassis until instructed to do so. 4. Cable the management and console ports only, so that you can access the system to perform the tasks in the following sections.
Page 482 You will connect the rest of the cables to the controller module later in this procedure. 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. Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.
Page 483 5. If necessary, set the time in GMT on the replacement node: set time hh:mm:ss 6. At the LOADER prompt, confirm the date and time on the replacement node: date The date and time are given in GMT. == Step 2: Verify and set the controller’s HA state You must verify the state of the controller module and, if necessary, update the state to match your system configuration.
Page 484 The system ID and disk assignment information reside in the NVRAM module, which is in a module separate from the controller module and not impacted by the controller module replacement. == 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 485 d. Return to the admin privilege level: set -privilege admin 5. If your storage system has Storage or Volume Encryption configured, you must restore Storage or Volume Encryption functionality by using one of the following procedures, depending on whether you are using onboard or external key management: Restore onboard key management encryption keys ◦...
Page 486 :imagesdir: /tmp/d20230811-13274-9xzqyw/source/./asa250/../media/ 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 487 If any LIFs are listed as false, revert them to their home ports: network interface revert -vserver * -lif * 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 488 -node local -auto-giveback true == Step 3: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 489 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.
Page 490 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 491 connected. 3. Slide the terra cotta button on the cam handle downward until it unlocks. Animation - Remove the controller Cam handle release button Cam handle 4. Rotate the cam handle so that it completely disengages the controller module from the chassis, and...
Page 492 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. Place the controller module lid-side up on a stable, flat surface, press the blue button on the cover, slide the cover to the back of the controller module, and then swing the cover up and lift it off of the controller module.
Page 493 2. Locate the DIMMs on your controller module. 1. 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 494 DIMM ejector tabs DIMM 2. 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. 3.
Page 495 4. Push carefully, but firmly, on the top edge of the DIMM until the ejector tabs snap into place over the notches at the ends of the DIMM. 5. Close the controller module cover. == 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.
Page 496 Animation - Install controller Cam handle release button Cam handle Do not completely insert the controller module in the chassis until instructed to do so. 4. Cable the management and console ports only, so that you can access the system to perform the tasks in the following sections.
Page 497 You will connect the rest of the cables to the controller module later in this procedure. 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.
Page 498 failures resulting from testing the component. 5. Proceed based on the result of the preceding step: 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.
Page 499 LOADER prompt. f. Rerun the system-level diagnostic test. == Step 6: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 500 You must dispose of batteries according to the local regulations regarding battery recycling or disposal. If you cannot properly dispose of batteries, you must return the batteries to NetApp, as described in the RMA instructions that are shipped with the kit.
Page 501 Safety Information and Regulatory Notices == Step 3: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 502 7. Align the bezel with the ball studs, and then gently push the bezel onto the ball studs. 8. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 503 Option 1: Most systems 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 504 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: cluster1:*>...
Page 505 face. Make sure that you keep track of which slot the I/O module was in. Animation - Remove/install I/O module 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 506 -node local -auto-giveback true == Step 4: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 507 Shut down or take over the impaired controller using one of the following options.
Page 508 Option 1: Most systems 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 509 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: cluster1:*>...
Page 510 Make sure that any unused I/O slots have blanks installed to prevent possible thermal issues. 5. Reboot the controller from the LOADER prompt: bye This reinitializes the PCIe cards and other components and reboots the node. 6. Give back the controller from the partner controller. storage failover giveback -ofnode target_node_name 7.
Page 511 Option 1: Most systems 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 512 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: cluster1:*>...
Page 513 Lettered and numbered I/O cam latch I/O cam latch completely unlocked 1. Install the I/O module into the target slot: a. Align the I/O module with the edges of the slot. b. Slide 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.
Page 514 c. Reboot the node: This reinitializes the PCIe cards and other components and reboots the node. If you encounter an issue during reboot, see BURT 1494308 - Environment shutdown might be triggered during I/O module replacement 5. Give back the controller from the partner controller. storage failover giveback -ofnode target_node_name 6.
Page 515 There is an audible click when the module is secure and connected to the midplane. == Step 2: Return the failed component 1. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 516 The NVRAM module consists of the NVRAM11 and DIMMs. You can replace a failed NVRAM module or the DIMMs inside the NVRAM module. To replace a failed NVRAM module, you must remove it from the chassis, move the DIMMs to the replacement module, and install the replacement NVRAM module into the chassis.
Page 517 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.
Page 518 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 519 a. Depress the lettered and numbered cam button. The cam button moves away from the chassis. b. Rotate the cam latch down until it is in a horizontal position. The NVRAM module disengages from the chassis and moves out a few inches. c.
Page 520 Cover locking button DIMM and DIMM ejector tabs 4. Remove the DIMMs, one at a time, from the old NVRAM module and install them in the replacement NVRAM module. 5. Close the cover on the module. 6. Install the replacement NVRAM module into the chassis: a.
Page 521 b. Rotate the cam latch down until it is in a horizontal position. The NVRAM module disengages from the chassis and moves out a few inches. c. Remove the NVRAM module from the chassis by pulling on the pull tabs on the sides of the module face.
Page 522 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. 5. Install the replacement DIMM by aligning the DIMM with the socket and gently pushing the DIMM into the socket until the locking tabs lock in place.
Page 523 This procedure applies only to systems running ONTAP in an HA pair. Disk reassignment is only needed when replacing the NVRAM module. Steps 1. If the replacement controller is in Maintenance mode (showing the prompt), exit Maintenance *> mode and go to the LOADER prompt: halt 2.
Page 524 5. Verify that the disks were assigned correctly: storage disk show -ownership The disks belonging to the replacement controller should show the new system ID. In the following example, the disks owned by node1 now show the new system ID, 151759706: node1:>...
Page 525 node1_siteA::> metrocluster node show -fields configuration-state dr-group-id cluster node configuration-state ----------- ---------------------- -------------- ------------------- 1 node1_siteA node1mcc-001 configured 1 node1_siteA node1mcc-002 configured 1 node1_siteB node1mcc-003 configured 1 node1_siteB node1mcc-004 configured 4 entries were displayed. 9. Verify that the expected volumes are present for each controller: vol show -node node-name 10.
Page 526 Option 1: Using Onboard Key Manager Steps 1. Boot the node to the boot menu. 2. Select option 10, Set onboard key management recovery secrets. 3. Enter the passphrase for the onboard key manager you obtained from the customer. 4. At the prompt, paste the backup key data from the output of security key-manager backup command.
Page 527 7. Once the giveback completes, check the failover and giveback status with the storage commands. failover show storage failover show-giveback Only the CFO aggregates (root aggregate and CFO style data aggregates) will be shown. 8. Run the security key-manager onboard sync: a.
Page 528 3. Enter the management certificate information at the prompts. The controller returns to the boot menu after the management certificate information is completed. 4. Select option 1, Normal Boot 5. 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 529 == Step 7: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 530 2. If you are not already grounded, properly ground yourself. 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. 4.
Page 531 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. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 532 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.
Page 533 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 534 connected. 3. Slide the terra cotta button on the cam handle downward until it unlocks. Animation - Remove the controller Cam handle release button Cam handle 4. Rotate the cam handle so that it completely disengages the controller module from the chassis, and...
Page 535 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. Place the controller module lid-side up on a stable, flat surface, press the blue button on the cover, slide the cover to the back of the controller module, and then swing the cover up and lift it off of the controller module.
Page 536 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 537 7. Visually inspect the battery to make sure that it is completely installed into the holder and that the polarity is correct. 8. Reinstall the controller module cover. == Step 4: Reinstall the controller module and set time/date After you replace the RTC battery, you must reinstall the controller module. If the RTC battery has been left out of the controller module for more than 10 minutes, you may have to reset the time and date.
Page 538 -node local -auto-giveback true == Step 5: Return the failed part to NetApp Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return & Replacements page for further information.
Page 539 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:

Asa a150 Asa a250

NetApp ASA A Series Manual

Quick Links

Related Manuals for NetApp ASA A Series

Summary of Contents for NetApp ASA A Series

This manual is also suitable for: