NetApp FAS2700 Manual
  1. Manuals
  2. Brands
  3. NetApp Manuals
  4. Storage
  5. FAS2700 Series
  6. Manual

NetApp FAS2700 Manual

Maintain ontap systems
Hide thumbs Also See for FAS2700:
Table of Contents

Advertisement

Quick Links

Maintain
ONTAP Systems
NetApp
June 27, 2022
This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/fas2700/bootmedia-replace-
overview.html on June 27, 2022. Always check docs.netapp.com for the latest.

Advertisement

Table of Contents
loading

Related Manuals for NetApp FAS2700

Summary of Contents for NetApp FAS2700

  • Page 1 Maintain ONTAP Systems NetApp June 27, 2022 This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/fas2700/bootmedia-replace- overview.html on June 27, 2022. Always check docs.netapp.com for the latest.

  • Page 2: Table Of Contents

    FAS2700.........

  • Page 3: Maintain

    Maintain Boot media Overview of boot media replacement - AFF A220 and FAS2700 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 4 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 5 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 6 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 7 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 8 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 9 Key Manager external Restored yes: a. Enter the onboard security key-manager sync command: security key-manager external sync If the command fails, contact NetApp Support. mysupport.netapp.com b. Verify that the column equals for all authentication keys: Restored security key- manager key-query c.
  • Page 10 Return to admin mode: set -priv admin h. You can safely shut down the controller. Shut down the impaired controller - AFF A220 and FAS2700 Shut down or take over the impaired controller using the appropriate procedure for your configuration.
  • Page 11 When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y. Replace the boot media - AFF A220 and FAS2700 To replace the boot media, you must remove the impaired controller module, install the replacement boot media, and transfer the boot image to a USB flash drive.
  • Page 12 3. Remove and set aside the cable management devices from the left and right sides of the controller module. 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.
  • Page 13 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 14 • 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 15 • 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. 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.
  • Page 16 Other parameters might be necessary for your interface. You can enter help ifconfig the firmware prompt for details. Boot the recovery image - AFF A220 and FAS2700 You must boot the ONTAP image from the USB drive, restore the file system, and verify the environmental variables.
  • Page 17 -node local command. -auto-giveback true Restore OKM, NSE, and NVE as needed - AFF A220 and FAS2700 Once environment variables are checked, you must complete steps specific to systems that have Onboard Key Manager (OKM), NetApp Storage Encryption (NSE) or NetApp Volume Encryption (NVE) enabled.
  • Page 18 Option 1: Restore NVE or NSE when Onboard Key Manager is enabled Steps 1. Connect the console cable to the target controller. 2. Use the command at the LOADER prompt to boot the controller. boot_ontap 3. Check the console output: If the console Then…...
  • Page 19 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. Give back only the CFO aggregates with the storage failover giveback -fromnode local -only-cfo command.
  • Page 20 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. 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.
  • Page 21 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 22 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 23: Replace The Caching Module - Aff A220 And Fas2700

    -auto-giveback true Return the failed part to NetApp - AFF A220 and FAS2700 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 24 2. If the impaired controller is part of an HA pair, disable automatic giveback from the console of the healthy controller: storage failover modify -node local -auto-giveback false 3. Take the impaired controller to the LOADER prompt: If the impaired controller is Then…...
  • Page 25 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 26 Step 3: Replace a caching module To replace a caching module referred to as the M.2 PCIe card on the label on your controller, locate the slot inside the controller and follow the specific sequence of steps. Your storage system must meet certain criteria depending on your situation: •...
  • Page 27 5. Verify that the caching module is seated squarely and completely in the socket. If necessary, remove the caching module and reseat it into the socket. 6. Reseat and push the heatsink down to engage the locking button on the caching module housing. 7.
  • Page 28 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 29 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 30 During the boot process, you can safely respond to the prompts until the Maintenance mode prompt (*>) appears. 3. Run diagnostics on the caching module: sldiag device run -dev fcache 4. Verify that no hardware problems resulted from the replacement of the caching module: sldiag device status -dev fcache -long -state failed System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of...
  • Page 31 If the system-level Then… diagnostics tests… Resulted in some test Determine the cause of the problem: failures a. Exit Maintenance mode: halt After you issue the command, wait until the system stops at the LOADER prompt. b. Turn off or leave on the power supplies, depending on how many controller modules are in the chassis: ◦...
  • Page 32 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 33: Chassis

    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. Chassis Overview of chassis replacement - AFF A220 and FAS2700...
  • Page 34 If your system is running Then… clustered ONTAP with… Two controllers in the cluster cluster ha modify -configured false storage failover modify -node node0 -enabled false More than two controllers in the storage failover modify -node node0 -enabled false cluster 2.
  • Page 35 When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y. Move and replace hardware - AFF A220 and FAS2700 Move the power supplies, hard drives, and controller module or modules from the impaired chassis to the new chassis, and swap out the impaired chassis from the equipment rack or system cabinet with the new chassis of the same model as the impaired chassis.
  • Page 36 power supply from the mid plane. 4. Use the cam handle to slide the power supply out of the system. When removing a power supply, always use two hands to support its weight. 5. Repeat the preceding steps for any remaining power supplies. 6.
  • Page 37 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 38 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 39 Restore and verify the configuration - AFF A220 and FAS2700 You must verify the HA state of the chassis and run System-Level diagnostics, switch back aggregates, and return the failed part to NetApp, as described in the RMA instructions shipped with the kit.
  • Page 40 Step 1: Verify and set the HA state of the chassis You must verify the HA state of the chassis, and, if necessary, update the state to match your system configuration. 1. In Maintenance mode, from either controller module, display the HA state of the local controller module and chassis: ha-config show The HA state should be the same for all components.
  • Page 41 During the boot process, you can safely respond to prompts: 2. Repeat the previous step on the second controller if you are in an HA configuration. Both controllers must be in Maintenance mode to run the interconnect test. 3. At the LOADER prompt, access the special drivers specifically designed for system-level diagnostics to function properly: boot_diags During the boot process, you can safely respond...
  • Page 42 If the system-level diagnostics Then… tests… Were completed without any a. Clear the status logs: sldiag device clearstatus failures b. Verify that the log was cleared: sldiag device status The following default response is displayed: SLDIAG: No log messages are present. c.
  • Page 43 If your system is running Then… ONTAP… Resulted in some test failures Determine the cause of the problem. a. Exit Maintenance mode: halt b. Perform a clean shutdown, and then disconnect the power supplies. c. Verify that you have observed all of the considerations identified for running system-level diagnostics, that cables are securely connected, and that hardware components are properly installed in the storage system.

  • Page 44: Controller

    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 45 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the “Returning SEDs to unprotected mode” section of the ONTAP 9 NetApp Encryption Power Guide.
  • Page 46 When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond y. Replace the controller module hardware - AFF A220 and FAS2700 To replace the controller module hardware, you must remove the impaired controller, move FRU components to the replacement controller module, install the replacement controller module in the chassis, and then boot the system to Maintenance mode.
  • Page 47 4. If you left the SFP modules in the system after removing the cables, move them to the new controller module. 5. 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.
  • Page 48 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. 1. Check the NVMEM LED: ◦ If your system is in an HA configuration, go to the next step. ◦...
  • Page 49 3. 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. 4. Grasp the battery and press the blue locking tab marked PUSH, and then lift the battery out of the holder and controller module.
  • Page 50 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 51 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 52 a. Press the release tab. b. Remove the heatsink. 2. Gently pull the caching module straight out of the housing. 3. Move the caching module to the new controller module, and then align the edges of the caching module with the socket housing and gently push it into the socket. 4.
  • Page 53 The system might update system firmware when it boots. Do not abort this process. The procedure requires you to interrupt the boot process, which you can typically do at any time after prompted to do so. However, if the system updates the system firmware when it boots, you must wait until after the update is complete before interrupting the boot process.
  • Page 54 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 55 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 56 Restore and verify the system configuration - AFF A220 and FAS2700 After completing the hardware replacement and booting to Maintenance mode, you verify the low-level system configuration of the replacement controller and reconfigure system settings as necessary. Step 1: Set and verify system time after replacing the controller You should check the time and date on the replacement controller module against the healthy controller module in an HA pair, or against a reliable time server in a stand-alone configuration.
  • Page 57 ▪ ▪ ▪ mcc-2n ▪ mccip ▪ non-ha b. Confirm that the setting has changed: ha-config show Step 3: Run system-level diagnostics You should run comprehensive or focused diagnostic tests for specific components and subsystems whenever you replace the controller. All commands in the diagnostic procedures are issued from the controller where the component is being replaced.
  • Page 58 If you want to run diagnostic Then… tests on… Individual components a. Clear the status logs: sldiag device clearstatus b. Display the available tests for the selected devices: sldiag device show -dev dev_name dev_name can be any one of the ports and devices identified in the preceding step.
  • Page 59 If you want to run diagnostic Then… tests on… Multiple components at the same a. Review the enabled and disabled devices in the output from the time preceding procedure and determine which ones you want to run concurrently. b. List the individual tests for the device: sldiag device show -dev dev_name c.
  • Page 60 Rerun the system-level diagnostics test. Recable the system and reassign disks - AFF A220 and FAS2700 To complete the replacement procedure and restore your system to full operation, you must recable the storage, confirm disk reassignment, restore the NetApp Storage Encryption configuration (if necessary), and install licenses for the new controller.
  • Page 61 c. Click the Cabling tab, and then examine the output. Make sure that all disk shelves are displayed and all disks appear in the output, correcting any cabling issues you find. d. Check other cabling by clicking the appropriate tab, and then examining the output from Config Advisor. Step 2: Reassign disks If the storage system is in an HA pair, the system ID of the new controller module is automatically assigned to the disks when the giveback occurs at the end of the procedure.
  • Page 62 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 63 node1> `storage disk show -ownership` Disk Aggregate Home Owner DR Home Home ID Owner ID DR Home ID Reserver Pool ----- ------ ----- ------ -------- ------- ------- ------- --------- 1.0.0 aggr0_1 node1 node1 1873775277 1873775277 1873775277 Pool0 1.0.1 aggr0_1 node1 node1 1873775277 1873775277 1873775277 Pool0 Option 2: Manually reassign the system ID on a stand-alone system in ONTAP...
  • Page 64 5. Reassign disk ownership by using the system ID information obtained from the disk show command: disk reassign -s old system ID disk reassign -s 118073209 6. Verify that the disks were assigned correctly: disk show -a The disks belonging to the replacement node should show the new system ID. The following example now show the disks owned by system-1 the new system ID, 118065481: *>...
  • Page 65 dr-group-id cluster node node-systemid dr- partner-systemid  ----------- --------------------- -------------------- ------------- -------------------  1 Cluster_A Node_A_1 536872914 118073209  1 Cluster_B Node_B_1 118073209 536872914  2 entries were displayed. 3. View the new system ID at the Maintenance mode prompt on the impaired node: disk show In this example, the new system ID is 118065481: Local System ID: 118065481...
  • Page 66 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 67 -privilege admin Complete system restoration - AFF A220 and FAS2700 To restore your system to full operation, you must restore the NetApp Storage Encryption configuration (if necessary), and install licenses for the new controller, and return the failed part to NetApp, as described in the RMA instructions shipped with the kit.
  • Page 68 If any LIFs are listed as false, revert them to their home ports: network interface revert 2. Register the system serial number with NetApp Support. ◦ If AutoSupport is enabled, send an AutoSupport message to register the serial number. ◦ If AutoSupport is not enabled, call NetApp Support to register the serial number.
  • Page 69 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 70: Replace A Dimm - Aff A220 And Fas2700

    About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the “Returning SEDs to unprotected mode” section of the ONTAP 9 NetApp Encryption Power Guide.
  • Page 71 If the impaired controller is Then… displaying… The LOADER prompt Go to Remove controller module. Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name...
  • Page 72 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 DIMMs To replace the DIMMs, locate them inside the controller and follow the specific sequence of steps.
  • Page 73 If you are replacing a DIMM, you need to remove it after you have unplugged the NVMEM battery from the controller module. Steps 1. If you are not already grounded, properly ground yourself. 2. Check the NVMEM LED on the controller module. You must perform a clean system shutdown before replacing system components to avoid losing unwritten data in the nonvolatile memory (NVMEM).
  • Page 74 Each system memory DIMM has an LED located on the board next to each DIMM slot. The LED for the faulty blinks every two seconds. 7. Note the orientation of the DIMM in the socket so that you can insert the replacement DIMM in the proper orientation.
  • Page 75 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 76 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 77 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 78 function properly: boot_diags During the boot process, you can safely respond to the prompts until the Maintenance mode prompt (*>) appears. 3. Run diagnostics on the system memory: sldiag device run -dev mem 4. Verify that no hardware problems resulted from the replacement of the DIMMs: sldiag device status -dev mem -long -state failed System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of...
  • Page 79 If your controller is in… Then… Resulted in some test failures Determine the cause of the problem: a. Exit Maintenance mode: halt After you issue the command, wait until the system stops at the LOADER prompt. b. Turn off or leave on the power supplies, depending on how many controller modules are in the chassis: ◦...
  • Page 80 1. Verify that all nodes are in the enabled state: metrocluster node show cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A   controller_A_1 configured enabled heal roots completed   cluster_B  ...

  • Page 81: Replace Ssd Drive Or Hdd Drive - Aff A220 And Fas2700

    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. Replace SSD Drive or HDD Drive - AFF A220 and FAS2700 You can replace a failed drive nondisruptively while I/O is in progress.
  • Page 82 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 83 -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 84 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 85: Replace The Nvmem Battery - Aff A220 And Fas2700

    About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the “Returning SEDs to unprotected mode” section of the ONTAP 9 NetApp Encryption Power Guide.
  • Page 86 If the impaired controller is Then… displaying… The LOADER prompt Go to Remove controller module. Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name...
  • Page 87 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 88 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 89 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. Be prepared to interrupt the boot process. a.
  • Page 90 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 91 function properly: boot_diags During the boot process, you can safely respond to the prompts until the Maintenance mode prompt (*>) appears. 3. Run diagnostics on the NVMEM memory: sldiag device run -dev nvmem 4. Verify that no hardware problems resulted from the replacement of the NVMEM battery: sldiag device status -dev nvmem -long -state failed System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of...
  • Page 92 If your controller is in… Then… Resulted in some test failures Determine the cause of the problem: a. Exit Maintenance mode: halt After you issue the command, wait until the system stops at the LOADER prompt. b. Turn off or leave on the power supplies, depending on how many controller modules are in the chassis: ◦...
  • Page 93 1. Verify that all nodes are in the enabled state: metrocluster node show cluster_B::> metrocluster node show Configuration Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- cluster_A   controller_A_1 configured enabled heal roots completed   cluster_B  ...

  • Page 94: Swap Out A Power Supply - Aff A220 And Fas2700

    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. Swap out a power supply - AFF A220 and FAS2700 Swapping out a power supply involves turning off, disconnecting, and removing the old power supply and installing, connecting, and turning on the replacement power supply.
  • Page 95 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 96: Replace The Real-Time Clock Battery

    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 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 97 If the impaired controller is Then… displaying… The LOADER prompt Go to Remove controller module. Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired controller from the healthy controller: prompt (enter system password) storage failover takeover -ofnode impaired_node_name...
  • Page 98 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 99 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 100 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 101 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 102 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 103 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 a220

Table of Contents