Download
Share
Print this page
NetApp AFF A300 Manual
  1. Manuals
  2. Brands
  3. NetApp Manuals
  4. Disk array system
  5. AFF A300
  6. Manual

NetApp AFF A300 Manual

Ontap systems
Hide thumbs Also See for AFF A300:

Advertisement

Quick Links

Download this manual
AFF A300 systems
ONTAP Systems
NetApp
January 28, 2022
This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/a300/install-worksheet-
linkout.html on January 28, 2022. Always check docs.netapp.com for the latest.

Advertisement

loading

Related Manuals for NetApp AFF A300

Summary of Contents for NetApp AFF A300

  • Page 1 AFF A300 systems ONTAP Systems NetApp January 28, 2022 This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/a300/install-worksheet- linkout.html on January 28, 2022. Always check docs.netapp.com for the latest.
  • Page 2 Table of Contents AFF A300 System Documentation ............

  • Page 3: Install And Setup

    Install MetroCluster IP configuration • Install MetroCluster Fabric-Attached configuration Installation and setup PDF poster - AFF A300 You can use the PDF poster to install and set up your new system. The PDF poster provides step-by-step instructions with live links to additional content.
  • Page 4 ◦ The impaired node is the node on which you are performing maintenance. ◦ The healthy node is the HA partner of the impaired node. Check onboard encryption keys as needed - AFF A300 Prior to shutting down the impaired node and checking the status of the onboard encryption keys, you must check the status of the impaired node, disable automatic giveback, and check what version of ONTAP the system is running.
  • Page 5 Option 1: Check NVE or NSE on systems running ONTAP 9.5 and earlier Before shutting down the impaired node, 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 6 2. If the column displayed anything other than yes, or if any key manager displayed 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.
  • Page 7 Option 2: Check NVE or NSE on systems running ONTAP 9.6 and later Before shutting down the impaired node, you need to verify whether the system has either NetApp Volume Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.
  • Page 8 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 9 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 information.
  • Page 10 Return to admin mode: set -priv admin h. You can safely shut down the node. Shut down the impaired controller - AFF A300 You can shut down or take over the impaired controller using different procedures, depending on the storage system hardware configuration.
  • Page 11 2. From the LOADER prompt, enter: printenv to capture all boot environmental variables. Save the 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 After completing the NVE or NSE tasks, you need to complete the shutdown of the impaired node.
  • Page 12 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 13 8. On the impaired controller module, disconnect the power supplies. Remove the controller module, replace the boot media and transfer the boot image to the boot media - AFF A300 To replace the boot media, you must remove the impaired controller module, install the...
  • Page 14 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, you must first remove the controller module from the system and then remove the cover on the controller module. 1.
  • Page 15 Step 2: Replace the boot media - AFF A300 You must locate the boot media in the controller and follow the directions to replace it. 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: 3.
  • Page 16 • 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 17 ▪ bootarg.init.flash_optimized ▪ bootarg.init.switchless_cluster.enable b. If External Key Manager is enabled, check the bootarg values, listed in the ASUP output: kenv ▪ bootarg.storageencryption.support <value> ▪ bootarg.keymanager.support <value> ▪ kmip.init.interface <value> ▪ kmip.init.ipaddr <value> ▪ kmip.init.netmask <value> ▪ kmip.init.gateway <value> c. If Onboard Key Manager is enabled, check the bootarg values, listed in the ASUP output: kenv ▪...
  • Page 18 The changes will be implemented when the system is booted. Boot the recovery image - AFF A300 The procedure for booting the impaired node from the recovery image depends on whether the system is in a two-node MetroCluster configuration.
  • Page 19 a. Take the node to the LOADER prompt. b. Check the environment variable settings with the command. printenv c. If an environment variable is not set as expected, modify it with the setenv environment- variable-name changed-value command. d. Save your changes using the command.
  • Page 20 Reboot the node. Switch back aggregates in a two-node MetroCluster configuration - AFF A300 After you have completed the FRU replacement in a two-node MetroCluster configuration, you can perform the MetroCluster switchback operation. This returns the configuration to its normal operating state, with the sync-source storage virtual machines (SVMs) on the formerly impaired site now active and serving data from the local disk pools.
  • Page 21 Restore OKM, NSE, and NVE as needed - AFF A300 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 22 Option 1: Restore NVE or NSE when Onboard Key Manager is enabled Steps 1. Connect the console cable to the target node. 2. Use the command at the LOADER prompt to boot the node. boot_ontap 3. Check the console output: If the console Then…...
  • Page 23 --------------------------BEGIN BACKUP-------------------------- TmV0QXBwIEtleSBCbG9iAAEAAAAEAAAAcAEAAAAAAADuD+byAAAAACEAAAAAAAAA QAAAAAAAAABvOlH0AAAAAMh7qDLRyH1DBz12piVdy9ATSFMT0C0TlYFss4PDjTaV dzRYkLd1PhQLxAWJwOIyqSr8qY1SEBgm1IWgE5DLRqkiAAAAAAAAACgAAAAAAAAA 3WTh7gAAAAAAAAAAAAAAAAIAAAAAAAgAZJEIWvdeHr5RCAvHGclo+wAAAAAAAAAA IgAAAAAAAAAoAAAAAAAAAEOTcR0AAAAAAAAAAAAAAAACAAAAAAAJAGr3tJA/ LRzUQRHwv+1aWvAAAAAAAAAAACQAAAAAAAAAgAAAAAAAAACdhTcvAAAAAJ1PXeBf ml4NBsSyV1B4jc4A7cvWEFY6lLG6hc6tbKLAHZuvfQ4rIbYAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA H4nPQM0nrDRYRa9SCv8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAA ---------------------------END BACKUP--------------------------- 7. At the Boot Menu select the option for Normal Boot. The system boots to prompt. Waiting for giveback… 8. Move the console cable to the partner node and login as admin. 9.
  • Page 24 b. Enter the key-manager key show -detail command to see a detailed view of all keys stored in the onboard key manager and verify that the column = for all authentication keys. Restored If the column = anything other than yes, contact Customer Support. Restored c.
  • Page 25 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 26 a. Use the security key-manager key show -detail to see a detailed view of all keys stored in the onboard key manager. b. Use the command and verify that the security key-manager key show -detail Restored column = for all authentication keys. If the Restored column = anything other than yes, use the...
  • Page 27 -auto-giveback true Return the failed part to NetApp - AFF A300 After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp...
  • Page 28 • This procedure is written with the assumption that you are moving the controller module or modules to the new chassis, and that the chassis is a new component from NetApp. • This procedure is disruptive. For a two-node cluster, you will have a complete service outage and a partial outage in a multi-node cluster.
  • Page 29 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 30 If the impaired node… Then… Has not automatically switched Review the veto messages and, if possible, resolve the issue and try over, you attempted switchover again. If you are unable to resolve the issue, contact technical support. with the metrocluster command, and the switchover switchover was vetoed...
  • Page 31 Errors: - 8. On the impaired controller module, disconnect the power supplies. Move and replace hardware - AFF A300 Move the power supplies, fans, and controller 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 32 Power supply Cam handle release latch Power and Fault LEDs Cam handle...
  • Page 33 Power cable locking mechanism 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 34 Cam handle Fan module Cam handle release latch Fan module Attention LED 3. Pull the fan module straight out from the chassis, making sure that you support it with your free hand so that it does not swing out of the chassis. The fan modules are short.
  • Page 35 10. Align the bezel with the ball studs, and then gently push the bezel onto the ball studs. Step 3: Remove the controller module To replace the chassis, you must remove the controller module or modules from the old chassis. 1.
  • Page 36 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. If the system is in a system cabinet, you might need to remove the rear tie-down bracket.
  • Page 37 From the boot menu, select the option for Maintenance mode. Restoring and verifying the configuration - AFF A300 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...
  • Page 38 Then… A stand-alone configuration a. Exit Maintenance mode: halt b. Go to Step 4: Return the failed part to NetApp. An HA pair with a second Exit Maintenance mode: The LOADER prompt appears. halt controller module Step 2: Run system-level diagnostics After installing a new chassis, you should run interconnect diagnostics.
  • Page 39 During the boot process, you can safely respond to prompts: 2. Repeat the previous step on the second node 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 40 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 41 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 42 6. Reestablish any SnapMirror or SnapVault configurations. Step 4: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
  • Page 43 This provides you a record of the procedure so that you can troubleshoot any issues that you might encounter during the replacement process. Shut down the impaired controller - AFF A300 You can shut down or take over the impaired controller using different procedures, depending on the storage system hardware configuration.
  • Page 44 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 45 controller_A_1::> metrocluster heal -phase aggregates [Job 130] Job succeeded: Heal Aggregates is successful. If the healing is vetoed, you have the option of reissuing the command with the metrocluster heal -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation.
  • Page 46 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 47 that prevent the healing operation. 4. Verify that the operation has been completed by using the metrocluster operation show command. 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.
  • Page 48 Replace controller module - AFF A300 To replace the controller module hardware, you must remove the impaired node, move FRU components to the replacement controller module, install the replacement controller module in the chassis, and then boot the system to Maintenance mode.
  • Page 49 6. Pull the cam handle downward and begin to 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. Step 2: Move the boot device 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 50 If necessary, remove the boot media and reseat it into the socket. 5. Push the boot media down to engage the locking button on the boot media housing. Step 3: 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 51 Battery lock tab NVMEM battery pack 3. Grasp the battery and press the blue locking tab marked PUSH, and then lift the battery out of the holder and controller module. 4. Remove the battery from the controller module and set it aside. Step 4: Move the 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 52 Carefully hold the DIMM by the edges to avoid pressure on the components on the DIMM circuit board. The number and placement of system DIMMs depends on the model of your system. The following illustration shows the location of system DIMMs: 4.
  • Page 53 Step 5: Move a PCIe card To move PCIe cards, locate and move them from the old controller into the replacement controller and follow the specific sequence of steps. You must have the new controller module ready so that you can move the PCIe cards directly from the old controller module to the corresponding slots in the new one.
  • Page 54 5. Open the new controller module side panel, if necessary, slide off the PCIe card filler plate, as needed, and carefully install the PCIe card. Be sure that you properly align the card in the slot and exert even pressure on the card when seating it in the socket.
  • Page 55 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 56 You can safely respond to these prompts. Restore and verify the system configuration - AFF A300 After completing the hardware replacement and booting to Maintenance mode, you verify the low-level system configuration of the replacement controller and reconfigure system settings as necessary.
  • Page 57 • The replacement node is the new node that replaced the impaired node as part of this procedure. • The healthy node is the HA partner of the replacement node. Steps 1. If the replacement node is not at the LOADER prompt, halt the system to the LOADER prompt. 2.
  • Page 58 All commands in the diagnostic procedures are issued from the node where the component is being replaced. 1. If the node to be serviced is not at the LOADER prompt, reboot the node: halt After you issue the command, you should wait until the system stops at the LOADER prompt. 2.
  • Page 59 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 60 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 61 Reconnect the power supplies, and then power on the storage system. e. Rerun the system-level diagnostics test. Recable the system and reassign disks - AFF A300 Continue the replacement procedure by recabling the storage and confirming disk reassignment. Step 1: Recable the system After running diagnostics, you must recable the controller module’s storage and network connections.
  • Page 62 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 63 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. Give back the node: a. From the healthy node, give back the replaced node’s storage: storage failover giveback -ofnode replacement_node_name The replacement node takes back its storage and completes booting.
  • Page 64 You must be sure to issue the commands in this procedure on the correct node: • The impaired node is the node on which you are performing maintenance. • The replacement node is the new node that replaced the impaired node as part of this procedure. •...
  • Page 65 *> disk show -a Local System ID: 118065481   DISK OWNER POOL SERIAL NUMBER HOME ------- ------------- ----- ------------- ------------- disk_name system-1 (118065481) Pool0 J8Y0TDZC system-1 (118065481) disk_name system-1 (118065481) Pool0 J8Y09DXC system-1 (118065481) 6. From the healthy node, verify that any coredumps are saved: a.
  • 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 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 68 local disk pools. This task only applies to two-node MetroCluster configurations. 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  ...
  • Page 69 6. Reestablish any SnapMirror or SnapVault configurations. Step 5: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
  • Page 70 If the impaired node 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 node from the healthy node: storage prompt (enter system password) failover takeover -ofnode impaired_node_name...
  • Page 71 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 72 If the healing is vetoed, you have the option of reissuing the metrocluster heal command with the parameter. If you use this optional parameter, the system overrides any soft vetoes -override-vetoes that prevent the healing operation. 4. Verify that the operation has been completed by using the metrocluster operation show command. controller_A_1::>...
  • Page 73 8. On the impaired controller module, disconnect the power supplies. Step 2: Open 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. 1.
  • Page 74 Step 3: Replace the DIMMs To replace the DIMMs, locate them inside the controller and follow the specific sequence of 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 75 NVMEM battery lock tab NVMEM battery b. 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. c. Wait a few seconds, and then plug the battery back into the socket. 5.
  • Page 76 Carefully hold the DIMM by the edges to avoid pressure on the components on the DIMM circuit board. The number and placement of system DIMMs depends on the model of your system. The following illustration shows the location of system DIMMs: 9.
  • Page 77 12. Locate the NVMEM battery plug socket, and then squeeze the clip on the face of the battery cable plug to insert it into the socket. Make sure that the plug locks down onto the controller module. 13. Close the controller module cover. Step 4: Reinstall the controller After you replace a component within the controller module, you must reinstall the controller module in the system chassis and boot it to a state where you can run...
  • Page 78 1. If the node to be serviced is not at the LOADER prompt, perform the following steps: a. Select the Maintenance mode option from the displayed menu. b. After the node boots to Maintenance mode, halt the node: halt After you issue the command, you should wait until the system stops at the LOADER prompt. During the boot process, you can safely respond to prompts: ▪...
  • Page 79 If your node is in… Then… An HA pair Perform a give back: storage failover giveback -ofnode replacement_node_name If you disabled automatic giveback, re-enable it with the storage failover modify command. A two-node MetroCluster Proceed to the next step. The MetroCluster switchback procedure is configuration done in the next task in the replacement process.
  • Page 80 Step 6 (Two-node MetroCluster only): Switch back aggregates After you have completed the FRU replacement in a two-node MetroCluster configuration, you can perform the MetroCluster switchback operation. This returns the configuration to its normal operating state, with the sync-source storage virtual machines (SVMs) on the formerly impaired site now active and serving data from the local disk pools.
  • Page 81 6. Reestablish any SnapMirror or SnapVault configurations. Step 7: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
  • Page 82 10. Align the bezel with the ball studs, and then gently push the bezel onto the ball studs. 11. After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
  • Page 83 44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure. Replace the NVMEM battery - AFF A300 To replace an NVMEM battery in the system, you must remove the controller module from the system, open it, replace the battery, and close and replace the controller module.
  • Page 84 If the impaired node is Then… displaying… System prompt or password Take over or halt the impaired node from the healthy node: storage prompt (enter system password) failover takeover -ofnode impaired_node_name When the impaired node shows Waiting for giveback…, press Ctrl-C, and then respond y.
  • Page 85 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 86 If the healing is vetoed, you have the option of reissuing the metrocluster heal command with the parameter. If you use this optional parameter, the system overrides any soft vetoes -override-vetoes that prevent the healing operation. 4. Verify that the operation has been completed by using the metrocluster operation show command. controller_A_1::>...
  • Page 87 8. On the impaired controller module, disconnect the power supplies. Step 2: Open 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. 1.
  • Page 88 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. 1. If you are not already grounded, properly ground yourself. 2.
  • Page 89 Battery lock tab NVMEM battery pack 4. Grasp the battery and press the blue locking tab marked PUSH, and then lift the battery out of the holder and controller module. 5. Remove the replacement battery from its package. 6. Align the tab or tabs on the battery holder with the notches in the controller module side, and then gently push down on the battery housing until the battery housing clicks into place.
  • Page 90 diagnostic tests on the replaced component. 1. If you are not already grounded, properly ground yourself. 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 91 2. 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 to the prompts until the Maintenance mode prompt (*>) appears. 3. Run diagnostics on the NVMEM memory: sldiag device run -dev nvmem 4.
  • Page 92 If your node 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 Step 8: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888- 463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
  • Page 95 If the impaired node is Then… displaying… System prompt or password Take over or halt the impaired node from the healthy node: storage prompt (enter system password) failover takeover -ofnode impaired_node_name When the impaired node shows Waiting for giveback…, press Ctrl-C, and then respond y.
  • Page 96 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 97 If the healing is vetoed, you have the option of reissuing the metrocluster heal command with the parameter. If you use this optional parameter, the system overrides any soft vetoes -override-vetoes that prevent the healing operation. 4. Verify that the operation has been completed by using the metrocluster operation show command. controller_A_1::>...
  • Page 98 8. On the impaired controller module, disconnect the power supplies. Step 2: Open 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. 1.
  • Page 99 Step 3: Replace a PCIe card To replace a PCIe card, locate it within the controller and follow the specific sequence of steps. 1. If you are not already grounded, properly ground yourself. 2. Loosen the thumbscrew on the controller module side panel. 3.
  • Page 100 6. Close the side panel and tighten the thumbscrew. Step 4: Reinstall the controller After you replace a component within the controller module, you must reinstall the controller module in the system chassis and boot it. 1. If you are not already grounded, properly ground yourself. 2.
  • Page 101 If your system is in… Then perform these steps… A two-node MetroCluster a. With the cam handle in the open position, firmly push the configuration controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position. Tighten the thumbscrew on the cam handle on back of the controller module.
  • Page 102 This task only applies to two-node MetroCluster configurations. 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  ...
  • Page 103 6. Reestablish any SnapMirror or SnapVault configurations. Step 6: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
  • Page 104 Power supply Cam handle release latch Power and Fault LEDs Cam handle...
  • Page 105 The power supply LEDs are lit when the power supply comes online. 2. After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
  • Page 106 Option 1: Most configurations To shut down the impaired node, you must determine the status of the node and, if necessary, take over the node so that the healthy node continues to serve data from the impaired node storage. About this task If you have a cluster with more than two nodes, it must be in quorum.
  • Page 107 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 108 If the impaired node… Then… Has automatically switched over Proceed to the next step. Has not automatically switched Perform a planned switchover operation from the healthy node: over metrocluster switchover Has not automatically switched Review the veto messages and, if possible, resolve the issue and try over, you attempted switchover again.
  • Page 109 mcc1A::> metrocluster heal -phase root-aggregates [Job 137] Job succeeded: Heal Root Aggregates is successful If the healing is vetoed, you have the option of reissuing the command with the metrocluster heal -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation.
  • Page 110 Thumbscrew Cam handle 5. Pull the cam handle downward and begin to 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. Step 3: Replace the RTC Battery To replace the RTC battery, locate them inside the controller and follow the specific sequence of steps.
  • Page 111 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 112 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 113 pools. This task only applies to two-node MetroCluster configurations. 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  ...
  • Page 114 6. Reestablish any SnapMirror or SnapVault configurations. Step 6: Return the failed part to NetApp After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at...
  • Page 115 NetApp assumes no responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by NetApp. The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual property rights of NetApp.

This manual is also suitable for:

Aff a300 systems