Advertisement

Quick Links

Maintain
Install and maintain
NetApp
July 05, 2024
This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/a70-90/maintain-
overview.html on July 05, 2024. Always check docs.netapp.com for the latest.

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for NetApp AFF A70

  • Page 1 Maintain Install and maintain NetApp July 05, 2024 This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/a70-90/maintain- overview.html on July 05, 2024. Always check docs.netapp.com for the latest.
  • Page 2: Table Of Contents

      Replace the real-time clock battery - AFF A70, AFF A90 ........
  • Page 3: Maintain

    Maintain Maintain AFF A70, AFF A90 hardware For the AFF A70, AFF A90 storage systems, 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.
  • Page 4: Boot Media

    (SSN). Boot media Overview of boot media replacement - AFF A70, AFF A90 The boot media stores a primary and secondary set of system (boot image) files that the system uses when it boots. Depending on your network configuration, you can perform either a nondisruptive or disruptive replacement.
  • Page 5 Enter the onboard security key-manager sync command: security key-manager onboard sync Enter the 32 character, alphanumeric onboard key management passphrase at the prompt. If the passphrase cannot be provided, contact NetApp Support. mysupport.netapp.com b. Verify the column displays...
  • Page 6 You can safely shut down the impaired controller. Shut down the controller - AFF A70, AFF A90 After completing the NVE or NSE tasks, you need to complete the shutdown of the impaired controller. Shut down or take over the impaired controller using the appropriate...
  • Page 7 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 •...
  • Page 8 When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y. Replace the boot media - AFF A70, AFF A90 To replace the boot media, you must remove the System Management module from the back of the system, remove the impaired boot media, install the replacement boot media in the System Management module, and transfer the boot image to a USB flash drive.
  • Page 9 System Management module cam latch Boot media locking button Boot media 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. 2.
  • Page 10 Downloads section on the NetApp Support Site ◦ If NVE is supported, download the image with NetApp Volume Encryption, as indicated in the download button. ◦ If NVE is not supported, download the image without NetApp Volume Encryption, as indicated in the download button.
  • Page 11 Other parameters might be necessary for your interface. You can enter help ifconfig at the firmware prompt for details. Boot the recovery image - AFF A70, AFF A90 You must boot the ONTAP image from the USB drive, restore the file system, and verify the environmental variables.
  • Page 12 -node local -target -address impaired_node_IP_address. If you see any message other than a successful restore, contact NetApp Support. e. On the healthy partner controller, return the impaired controller to admin level: set -privilege admin. f. On the impaired controller, press y when you see...
  • Page 13 Encryption restore - AFF A70, AFF A90 You must complete steps specific to systems that have Onboard Key Manager (OKM), NetApp Storage Encryption (NSE) or NetApp Volume Encryption (NVE) enabled using settings you captured at the beginning of this procedure.
  • Page 14 Option 1: Systems with onboard key manager server configuration Restore the onboard key manager configuration from the ONATP boot menu. Before you begin You need the following information while restoring the OKM configuration: • Cluster-wide passphrase entered while enabling onboard key management.
  • Page 15 Enter the backup data: --------------------------BEGIN BACKUP-------------------------- 0123456789012345678901234567890123456789012345678901234567890123 1234567890123456789012345678901234567890123456789012345678901234 2345678901234567890123456789012345678901234567890123456789012345 3456789012345678901234567890123456789012345678901234567890123456 4567890123456789012345678901234567890123456789012345678901234567 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA 0123456789012345678901234567890123456789012345678901234567890123 1234567890123456789012345678901234567890123456789012345678901234 2345678901234567890123456789012345678901234567890123456789012345 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ---------------------------END BACKUP--------------------------- 5. The recovery process will be completed.
  • Page 16 Trying to recover keymanager secrets..Setting recovery material for the onboard key manager Recovery secrets set successfully Trying to delete any existing km_onboard.wkeydb file. Successfully recovered keymanager secrets. ******************************************************************** *************** * Select option "(1) Normal Boot." to complete recovery process. * Run the "security key-manager onboard sync"...
  • Page 17 8. From the partner node, giveback the partner controller: storage failover giveback -fromnode local -only-cfo-aggregates true 9. Once booted only with CFO aggregate run the security key-manager onboard sync command: 10. Enter the cluster-wide passphrase for the Onboard Key Manager: Enter the cluster-wide passphrase for the Onboard Key Manager: All offline encrypted volumes will be brought online and the corresponding volume encryption keys (VEKs) will be restored...
  • Page 18 Normal Boot. Boot without /etc/rc. Change password. Clean configuration and initialize all disks. Maintenance mode boot. Update flash from backup config. Install new software first. Reboot node. Configure Advanced Drive Partitioning. (10) Set Onboard Key Manager recovery secrets. (11) Configure node for external key management. Selection (1-11)? 11 2.
  • Page 19 Example Enter the client certificate (client.crt) file contents: -----BEGIN CERTIFICATE----- MIIDvjCCAqagAwIBAgICN3gwDQYJKoZIhvcNAQELBQAwgY8xCzAJBgNVBAYTAlVT MRMwEQYDVQQIEwpDYWxpZm9ybmlhMQwwCgYDVQQHEwNTVkwxDzANBgNVBAoTBk5l MSUbQusvzAFs8G3P54GG32iIRvaCFnj2gQpCxciLJ0qB2foiBGx5XVQ/Mtk+rlap Pk4ECW/wqSOUXDYtJs1+RB+w0+SHx8mzxpbz3mXF/X/1PC3YOzVNCq5eieek62si Fp8= -----END CERTIFICATE----- Enter the client key (client.key) file contents: -----BEGIN RSA PRIVATE KEY----- MIIEpQIBAAKCAQEAoU1eajEG6QC2h2Zih0jEaGVtQUexNeoCFwKPoMSePmjDNtrU MSB1SlX3VgCuElHk57XPdq6xSbYlbkIb4bAgLztHEmUDOkGmXYAkblQ= -----END RSA PRIVATE KEY----- Enter the KMIP server CA(s) (CA.pem) file contents: -----BEGIN CERTIFICATE----- MIIEizCCA3OgAwIBAgIBADANBgkqhkiG9w0BAQsFADCBjzELMAkGA1UEBhMCVVMx 7yaumMQETNrpMfP+nQMd34y4AmseWYGM6qG0z37BRnYU0Wf2qDL61cQ3/jkm7Y94...
  • Page 20 5. Select option 1 from the boot menu to continue booting into ONTAP. ******************************************************************** *************** * Select option "(1) Normal Boot." to complete the recovery process. ******************************************************************** *************** Normal Boot. Boot without /etc/rc. Change password. Clean configuration and initialize all disks. Maintenance mode boot.
  • Page 21: Chassis

    -node * -type all -message MAINT=END command. Return the failed part to NetApp - AFF A70, AFF A90 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 22 • 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 23 "cluster <node-name> number"? {y|n}: 8. Wait for each controller to halt and display the LOADER prompt. Move and replace hardware - AFF A70, AFF A90 Move the power supplies, hard drives, and controller module from the impaired chassis to the new chassis, and swap out the impaired chassis with the new chassis of the same model as the impaired chassis.
  • Page 24 If the NVRAM status LED is flashing, it could mean the controller module was not taken over or halted properly (uncommitted data). If the impaired controller module was not successfully taken over by the partner controller module, contact NetApp Support before continuing with this procedure.
  • Page 25 ◦ The NVRAM status LED flashes when the controller module is removed from the chassis and could mean the controller module is not taken over or halted properly (uncommitted data). Confirm that the controller module has been cleanly takeover by the partner controller module or the impaired controller module shows waiting for giveback.
  • Page 26 chassis. 1. Gently remove the bezel from the front of the system. 2. Remove the drives: a. Press the release button at the top of the carrier face below the LEDs. b. Pull the cam handle to its fully open position to unseat the drive from the midplane, and then gently slide the drive out of the chassis.
  • Page 27 8. Repeat the preceding steps to install the second controller into the new chassis. Complete the restoration and replacement process - AFF A70, AFF A90 You must verify the HA state of the chassis and return the failed part to NetApp, as described in the RMA instructions shipped with the kit.
  • Page 28: Controller

    3. If you have not already done so, recable the rest of your 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 &...
  • Page 29 Shut down the impaired controller - AFF A70, AFF A90...
  • Page 30 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 •...
  • Page 31 When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y. Replace the controller module hardware - AFF A70, AFF A90 To replace the controller, you must remove the impaired controller, move FRU components from the impaired controller module to the replacement controller module, install the replacement controller module in the chassis, and then boot the system to Maintenance mode.
  • Page 32 If the NVRAM status LED is flashing, it could mean the controller module was not taken over or halted properly (uncommitted data). If the impaired controller module was not successfully taken over by the partner controller module, contact NetApp Support before continuing with this procedure.
  • Page 33 ◦ The NVRAM status LED flashes when power is removed from the controller module and the storage system is in the "waiting for giveback" state, or the controller module is not taken over or halted properly (uncommitted data). ◦ The NVRAM status LED flashes when the controller module is removed from the chassis and could mean the controller module is not taken over or halted properly (uncommitted data).
  • Page 34 Step 2: Move the power supplies Move the power supplies to the replacement controller. 1. Rotate the cam handle such that it can be used to pull power supply out of the controller module while pressing the locking tab. The power supply is short. Always use two hands to support it when removing it from the controller module so that it does not suddenly swing free from the controller module and injure you.
  • Page 35 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 36 NV battery pack plug Attention: The NV module LED blinks while destaging contents to the flash memory when you halt the system. After the destage is complete, the LED turns off. 2. Lift the battery up to access the battery plug. 3.
  • Page 37 System DIMM 3. 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. 4. 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.
  • Page 38 2. Rotate the cable management arm down by pulling the buttons on the inside of the cable management arm and rotating it down. 3. Remove the I/O modules from the controller module: a. Depress the target I/O module cam latch button. The cam lever moves away from the controller module.
  • Page 39 System Management module cam latch Boot media locking button Replacement System Management module 1. Remove the System Management module from the impaired controller module: a. Depress the system management cam button. The cam lever moves away from the chassis. b. Rotate the cam lever all the way down. c.
  • Page 40 DIMM locking tab 1. Remove the NVRAM module from the impaired controller module: a. Depress the cam latch button. The cam button moves away from the chassis. b. Rotate the cam latch as far as it will go. c. Remove the NVRAM module from the enclosure by hooking your finger into the cam lever opening and pulling the module out of the enclosure.
  • Page 41 -node * -type all -message MAINT=END 8. If you have not already done so, reinstall the cable management device and recable the controller. Restore and verify the system configuration - AFF A70, AFF A90 After completing the hardware replacement, you verify the low-level system configuration of the replacement controller and reconfigure system settings as necessary.
  • Page 42 4. Confirm that the setting has changed: ha-config show Recable and give back the controller - AFF A70, AFF A90 Continue the replacement procedure by recabling the storage, network connections and giving back the controller. Step 1: Recable the system Recable the controller module’s storage and network connections.
  • Page 43 e. Giveback SFO, (no force) 2. If your system does not have Encryption configured, complete the following procedure to reboot the system: a. Boot to Menu and run Option 1. b. Give back the controller: c. From the healthy controller, give back the replaced controller’s storage: storage failover giveback -ofnode replacement_node_name The replacement controller takes back its storage and completes booting.
  • Page 44: Replace A Dimm - Aff A70, Aff A90

    -node local -auto -giveback true 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 for further information.
  • Page 45 system panic. Before you begin All other components in the system must be functioning properly; if not, you must contact technical support. You must replace the failed component with a replacement FRU component you received from your provider. Step 1: Shut down the impaired controller Shut down or take over the impaired controller using one of the following options.
  • Page 46 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 •...
  • Page 47 take 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 48 If the NVRAM status LED is flashing, it could mean the controller module was not taken over or halted properly (uncommitted data). If the impaired controller module was not successfully taken over by the partner controller module, contact NetApp Support before continuing with this procedure.
  • Page 49 ◦ The NVRAM status LED flashes when the controller module is removed from the chassis and could mean the controller module is not taken over or halted properly (uncommitted data). Confirm that the controller module has been cleanly takeover by the partner controller module or the impaired controller module shows waiting for giveback.
  • Page 50 FRU map on your controller module for exact DIMM locations for the AFF A70 or AFF A90. 4. 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.
  • Page 51 -node * -type all -message MAINT=END 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 52: Replace Ssd Drive - Aff A70, Aff A90

    Replace SSD Drive - AFF A70, AFF A90 You can replace a failed SSD drive nondisruptively while I/O is in progress. When a drive fails, the platform logs a warning message to the system console indicating which drive has failed. In addition, both the fault LED on the operator display panel and the fault LED on the failed drive are illuminated.
  • Page 53 You must disable automatic drive assignment on both controller modules. 2. Properly ground yourself. 3. Physically identify the failed drive. When a drive fails, the system logs a warning message to the system console indicating which drive failed. Additionally, the attention (amber) LED on the drive shelf operator display panel and the failed drive illuminate.
  • Page 54: Replace A Fan Module - Aff A70, Aff A90

    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 Support, 888-463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
  • Page 55 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 •...
  • Page 56 take 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 57 If the NVRAM status LED is flashing, it could mean the controller module was not taken over or halted properly (uncommitted data). If the impaired controller module was not successfully taken over by the partner controller module, contact NetApp Support before continuing with this procedure.
  • Page 58 ◦ The NVRAM status LED flashes when the controller module is removed from the chassis and could mean the controller module is not taken over or halted properly (uncommitted data). Confirm that the controller module has been cleanly takeover by the partner controller module or the impaired controller module shows waiting for giveback.
  • Page 59 1. Identify the fan module that you must replace by checking the console error messages or by locating the lit LED for the fan module on the motherboard. 2. Remove the fan module by pinching the locking tabs on the side of the fan module, and then lifting the fan module straight out of the controller module.
  • Page 60: Replace Nvram - Aff A70, Aff A90

    -node * -type all -message MAINT=END 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 61 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 •...
  • Page 62 take 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 63 2. Go to the rear of the chassis. If you are not already grounded, properly ground yourself. 3. Unplug the power cord from both PSUs. If your system has DC power supplies, disconnect the power cable block from the PSU. 4.
  • Page 64 Cam locking button DIMM locking tabs 6. Set the NVRAM module on a stable surface. 7. Remove the DIMMs, one at a time, from the impaired NVRAM module and install them in the replacement NVRAM module. 8. Install the replacement NVRAM module into the chassis: a.
  • Page 65 3. Rotate the cable management tray down by gently pulling the pins on the ends of the tray and rotating the tray down. 4. Remove the target NVRAM module from the chassis: a. Depress the cam button. The cam button moves away from the chassis. b.
  • Page 66 rotate the cam latch all the way up to lock the module in place. 10. Recable the PSU. If your system has DC power supplies, reconnect the power cable block to the PSU. 11. Rotate the cable management tray up to the closed position. Step 4: Reboot the controller After you replace the FRU, you must reboot the controller module.
  • Page 67 a. From the healthy controller, give back the replaced controller’s storage: storage failover giveback -ofnode replacement_node_name The 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. If the giveback is vetoed, you can consider overriding the vetoes.
  • Page 68: Replace The Nv Battery - Aff A70, Aff A90

    -node * -type all -message MAINT=END 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 69 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 •...
  • Page 70 take 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 71 If the NVRAM status LED is flashing, it could mean the controller module was not taken over or halted properly (uncommitted data). If the impaired controller module was not successfully taken over by the partner controller module, contact NetApp Support before continuing with this procedure.
  • Page 72 ◦ The NVRAM status LED flashes when the controller module is removed from the chassis and could mean the controller module is not taken over or halted properly (uncommitted data). Confirm that the controller module has been cleanly takeover by the partner controller module or the impaired controller module shows waiting for giveback.
  • Page 73 1. Open the air duct cover and locate the NV battery. NV battery air duct cover NV battery plug 2. Lift the battery up to access the battery plug. 3. 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 74: I/O Module

    -node * -type all -message MAINT=END 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 75 Before you begin • Check the NetApp Hardware Universe to make sure that the new I/O module is compatible with your storage system and version of ONTAP you’re running. • If multiple slots are available, check the slot priorities in...
  • Page 76 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 77 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 command: system node autosupport invoke -node * -type all -message MAINT=number_of_hours_downh The following AutoSupport command suppresses automatic case creation for two hours: cluster1:*>...
  • Page 78 2. Go to the rear of the chassis. If you are not already grounded, properly ground yourself. 3. Disconnect power by pulling the controller module out about three inches: a. Press down on both of the locking latches, and then rotate both latches downward at the same time. b.
  • Page 79 b. Rotate the cam latch down as far as it will go. For horizontal modules, rotate the cam away from the module as far as it will go. c. Remove the blanking module. 6. Install the I/O module: a. Align the I/O module with the edges of the controller module slot opening. b.
  • Page 80 Replacing a… Then… NIC I/O module with fewer ports Permanently reassign the ASAected LIFs to a different home port. Migrating a LIF for information about using System Manager to permanently move the LIFs. NIC I/O module with a storage I/O Use System Manager to permanently migrate the LIFs to different module home ports, as described in...
  • Page 81 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 82 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 command: system node autosupport invoke -node * -type all -message MAINT=number_of_hours_downh The following AutoSupport command suppresses automatic case creation for two hours: cluster1:*>...
  • Page 83 2. Go to the rear of the chassis. If you are not already grounded, properly ground yourself. 3. Disconnect power by pulling the controller module out about three inches: If your storage system has DC power supplies, disconnect the power cable block from the PSU.
  • Page 84 Cam locking button a. Depress the cam latch button. The cam latch moves away from the chassis. b. Rotate the cam latch down as far as it will go. For horizontal modules, rotate the cam away from the module as far as it will go. c.
  • Page 85 16. Repeat these steps for controller B. Replace I/O module - AFF A70, AFF A90 Use this procedure to replace a failed I/O module. • You can use this procedure with all versions of ONTAP supported by your storage system.
  • Page 86 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 •...
  • Page 87 take 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 88 2. Go to the rear of the chassis. If you are not already grounded, properly ground yourself. 3. Disconnect power by pulling the controller module out about three inches: If your storage system has DC power supplies units (PSUs), disconnect the power cable block from the PSUs.
  • Page 89 Cam locking button a. Depress the cam latch button. The cam latch moves away from the controller module. b. Rotate the cam latch down as far as it will go. For horizontal modules, rotate the cam away from the module as far as it will go. c.
  • Page 90: Replace A Power Supply - Aff A70, Aff A90

    4. If automatic giveback was disabled, reenable it: storage failover modify -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 &...
  • Page 91 Option 1: Replace an AC PSU To replace an AC PSU, complete the following steps. 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 92 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 the Part Return & Replacements page for further information.
  • Page 93: Replace The Real-Time Clock Battery - Aff A70, Aff A90

    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 the Part Return & Replacements page for further information.
  • Page 94 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 •...
  • Page 95 take 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 96 If the NVRAM status LED is flashing, it could mean the controller module was not taken over or halted properly (uncommitted data). If the impaired controller module was not successfully taken over by the partner controller module, contact NetApp Support before continuing with this procedure.
  • Page 97 ◦ The NVRAM status LED flashes when the controller module is removed from the chassis and could mean the controller module is not taken over or halted properly (uncommitted data). Confirm that the controller module has been cleanly takeover by the partner controller module or the impaired controller module shows waiting for giveback.
  • Page 98 1. Open the controller air duct on the top of the controller. a. Insert your fingers in the recesses at the far ends of the air duct. b. Lift the air duct and rotate it upward as far as it will go. 2.
  • Page 99 3. Recable the system, as needed. If you removed the transceivers (QSFPs or SFPs), remember to reinstall them if you are using fiber optic cables. 4. Complete the reinstallation of the controller module: a. 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 100: Replace System Management Module - Aff A70, Aff A90

    4. If automatic giveback was disabled, reenable it: storage failover modify -node local -auto-giveback true 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 &...
  • Page 101 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 •...
  • Page 102 take 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 103 2. Go to the rear of the chassis. If you are not already grounded, properly ground yourself. 3. Disconnect power by pulling the controller module out about three inches: If your system has DC power supplies, disconnect the power cable block from the PSU. a.
  • Page 104 6. Remove the System Management module: a. Depress the system management cam button. The cam lever moves away from the chassis. b. Rotate the cam lever all the way down. c. Loop your finger into the cam lever and pull the module straight out of the system. d.
  • Page 105 Steps 1. If you need new license keys, obtain replacement license keys on the NetApp Support Site in the My Support section under Software licenses. The new license keys that you require are automatically generated and sent to the email address on file.
  • Page 106 NetApp Support to register the serial number. 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 107 NetApp. The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual property rights of NetApp.

This manual is also suitable for:

Aff a90

Table of Contents

Save PDF