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

NetApp FAS8200 Manual

Hide thumbs Also See for FAS8200:
Table of Contents

Advertisement

Quick Links

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

Advertisement

Table of Contents
loading

Related Manuals for NetApp FAS8200

Summary of Contents for NetApp FAS8200

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

  • Page 2: Table Of Contents

      Swap out a power supply - FAS8200 ............

  • Page 3: Maintain

    ◦ If the impaired node is in a standalone configuration and at LOADER prompt, contact NetApp Support. mysupport.netapp.com 2. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message: system node autosupport invoke -node * -type all -message...
  • Page 4 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 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 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: Restored security key-manager key query c.
  • 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 If the impaired node displays… Then… Press Ctrl-C, and then respond when prompted. Waiting for giveback... System prompt or password Take over or halt the impaired node: prompt (enter system password) • For an HA pair, take over the impaired node from the healthy node: storage failover takeover -ofnode `impaired_node_name`...
  • Page 11 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Returning SEDs to unprotected mode" section of Administration overview with the CLI.
  • Page 12 3. Resynchronize the data aggregates by running the metrocluster heal -phase aggregates command from the surviving cluster. 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.
  • 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 - FAS8200 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 14 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 2: Replace the boot media You must locate the boot media in the controller and follow the directions to replace it.
  • Page 15 3. 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 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.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 kenv ASUP output: ▪ bootarg.storageencryption.support <value> ▪ bootarg.keymanager.support <value> ▪ bootarg.onboard_keymanager <value> d.
  • Page 18 Boot the recovery image - FAS8200 The procedure for booting the impaired node from the recovery image depends on whether the system is in a two-node MetroCluster configuration. Option 1: Most systems You must boot the ONTAP image from the USB drive, restore the file system, and verify the environmental variables.
  • Page 19 d. Save your changes using the savenev command. 5. The next depends on your system configuration: ◦ If your system has onboard keymanager, NSE or NVE configured, go to Restore OKM, NSE, and NVE as needed ◦ If your system does not have onboard keymanager, NSE or NVE configured, complete the steps in this section.
  • Page 20 Reboot the node. Switch back aggregates in a two-node MetroCluster configuration - FAS8200 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 - FAS8200 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 3. Check the console output: If the console Then… displays… The LOADER prompt Boot the node to the boot menu: boot_ontap menu Waiting for giveback… a. Enter at the prompt Ctrl-C b. At the message: Do you wish to halt this node rather than wait [y/n]? , enter: c.
  • Page 23 10. Giveback only the CFO aggregates with the storage failover giveback -fromnode local -only-cfo command. -aggregates true ◦ If the command fails because of a failed disk, physically dis-engage the failed disk, but leave the disk in the slot until a replacement is received. ◦...
  • Page 24 If any interfaces are listed as false, revert those interfaces back to their home port using the net int command. revert 19. Move the console cable to the target node and run the command to check the ONTAP version -v versions.
  • 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 4. Move the console cable to the partner node and give back the target node storage using the storage command. failover giveback -fromnode local -only-cfo-aggregates true local ◦ If the command fails because of a failed disk, physically dis-engage the failed disk, but leave the disk in the slot until a replacement is received.

  • Page 27: Replace The Caching Module - Fas8200

    Return the failed part to NetApp - FAS8200 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 28 local -auto-giveback false 3. Take the impaired node to the LOADER prompt: If the impaired node is Then… displaying… The LOADER prompt Go to the next step. Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired node: prompt (enter system password) •...
  • Page 29 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Returning SEDs to unprotected mode" section of Administration overview with the CLI.
  • Page 30 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 31 mcc1A::> metrocluster operation show   Operation: heal-root-aggregates   State: successful  Start Time: 7/29/2016 20:54:41   End Time: 7/29/2016 20:54:42   Errors: - 8. On the impaired controller module, disconnect the power supplies. Step 2: 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.
  • Page 32 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 or add a caching module To replace or add a caching module referred to as the M.2 PCIe card on the label on your controller, locate the slots inside the controller and follow the specific sequence of steps.
  • Page 33 2. If you are adding a caching module, go to the next step; if you are replacing the caching module, gently pull it straight out of the housing. 3. Align the edges of the caching module with the socket in the housing, and then gently push it into the socket.
  • Page 34 Do not completely insert the controller module in the chassis until instructed to do so. 2. Recable the system, as needed. If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber optic cables. 3.
  • Page 35 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 failures resulting from testing the component. 5. Proceed based on the result of the preceding step: If the system-level diagnostics Then…...
  • Page 36 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 37 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 38: Chassis

    Step 7: Complete the replacement process After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at 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 39 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Returning SEDs to unprotected mode" section of Administration overview with the CLI.
  • Page 40 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 41   Errors: - 8. On the impaired controller module, disconnect the power supplies. Move and replace hardware - FAS8200 Step 1: Move a power supply Moving out a power supply when replacing a chassis involves turning off, disconnecting, and removing the power supply from the old chassis and installing and connecting it on the replacement chassis.
  • Page 42 Power supply Cam handle release latch Power and Fault LEDs Cam handle...
  • Page 43 Power cable locking mechanism 4. Use the cam handle to slide the power supply out of the system. CAUTION: 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 44 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. CAUTION: The fan modules are short.
  • Page 45 Step 3: Remove the controller module To replace the chassis, you must remove the controller module or modules from the old chassis. 1. Loosen the hook and loop strap binding the cables to the cable management device, and then unplug the system cables and SFPs (if needed) from the controller module, keeping track of where the cables were connected.
  • Page 46 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 47 If you miss the prompt and the controller modules boot to ONTAP, enter halt, and then at the LOADER prompt enter boot_ontap, press when prompted, and then Ctrl-C repeat this step. b. From the boot menu, select the option for Maintenance mode. Restoring and verifying the configuration - FAS8200...
  • Page 48 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 49 function properly: boot_diags During the boot process, you can safely respond to the prompts until the Maintenance mode prompt (*>) appears. 4. Enable the interconnect diagnostics tests from the Maintenance mode prompt: sldiag device modify -dev interconnect -sel enable The interconnect tests are disabled by default and must be enabled to run separately. 5.
  • Page 50 If your system is running Then… ONTAP… With two nodes in the cluster Issue these commands: node::> cluster ha modify -configured true``node::> storage failover modify -node node0 -enabled true With more than two nodes in the Issue this command:node::> storage failover modify cluster -node node0 -enabled true In a two-node MetroCluster...
  • Page 51 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 52: Controller

    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 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 53 This provides you a record of the procedure so that you can troubleshoot any issues that you might encounter during the replacement process. Shut down the impaired controller - FAS8200 You can shut down or take over the impaired controller using different procedures, depending on the storage system hardware configuration.
  • Page 54 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Returning SEDs to unprotected mode" section of Administration overview with the CLI.
  • Page 55 Steps 1. Check the MetroCluster status to determine whether the impaired node has automatically switched over to the healthy node: metrocluster show 2. Depending on whether an automatic switchover has occurred, proceed according to the following table: If the impaired node… Then…...
  • Page 56 Errors: - 8. On the impaired controller module, disconnect the power supplies. Move the controller module hardware - FAS8200 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 57 Leave the cables in the cable management device so that when you reinstall the cable management device, the cables are organized. 3. Remove and set aside the cable management devices from the left and right sides of the controller module. 4.
  • Page 58 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 59 ◦ If your system is in an HA configuration, go to the next step. ◦ If your system is in a stand-alone configuration, cleanly shut down the controller module, and then check the NVRAM LED identified by the NV icon. The NVRAM LED blinks while destaging contents to the flash memory when you halt the system.
  • Page 60 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 61 4. Locate the slot where you are installing the DIMM. 5. Make sure that the DIMM ejector tabs on the connector are in the open position, and then insert the DIMM squarely into the slot. The DIMM fits tightly in the slot, but should go in easily. If not, realign the DIMM with the slot and reinsert it. Visually inspect the DIMM to verify that it is evenly aligned and fully inserted into the slot.
  • Page 62 1. Loosen the thumbscrew on the controller module side panel. 2. Swing the side panel off the controller module. Side panel PCIe card 3. Remove the PCIe card from the old controller module and set it aside. Make sure that you keep track of which slot the PCIe card was in. 4.
  • Page 63 7. Close the side panel and tighten the thumbscrew. Step 6: Move a caching module You must move the caching modules from the impaired controller modules to the replacement controller module when replacing a controller module. 1. Locate the caching module at the rear of the controller module and remove it: a.
  • Page 64 5. Repeat the steps if you have a second caching module. Close the controller module cover. Step 7: Install the controller After you install the components from the old controller module into the new controller module, you must install the new controller module into the system chassis and boot the operating system.
  • Page 65 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 66 You can safely respond to these prompts. Restore and verify the system configuration - FAS8200 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 67 • 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 68 subsystems whenever you replace the controller. 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.
  • Page 69 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 70 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 71 Reconnect the power supplies, and then power on the storage system. e. Rerun the system-level diagnostics test. Recable the system and reassign disks - FAS8200 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...
  • Page 72 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...
  • Page 73 b. Save any coredumps: system node run -node local-node-name partner savecore c. Wait for command to complete before issuing the giveback. savecore You can enter the following command to monitor the progress of the command: savecore system node run -node local-node-name partner savecore -s d.
  • Page 74 disks to the new controller’s system ID before you return the system to normal operating condition. About this task This procedure applies only to systems in a two-node MetroCluster configuration running ONTAP. You must be sure to issue the commands in this procedure on the correct node: •...
  • Page 75 5. Verify that the disks (or FlexArray LUNs) were assigned correctly: disk show -a Verify that the disks belonging to the replacement node show the new system ID for the replacement node. In the following example, the disks owned by system-1 now show the new system ID, 118065481: *>...
  • Page 76 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 77 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 78 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. 3. If automatic giveback was disabled, reenable it:...

  • Page 79: Replace A Dimm - Fas8200

    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 80 impaired node storage. About this task If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy node shows false for eligibility and health, you must correct the issue before shutting down the impaired node; see the Administration overview with the CLI.
  • Page 81 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Returning SEDs to unprotected mode" section of Administration overview with the CLI.
  • Page 82 If the impaired node… Then… Has not automatically switched Perform a planned switchover operation from the healthy node: over metrocluster switchover Has not automatically switched Review the veto messages and, if possible, resolve the issue and try over, you attempted switchover again.
  • Page 83 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 84 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 DIMMs To replace the DIMMs, locate them inside the controller and follow the specific sequence of steps.
  • Page 85 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. 4.
  • Page 86 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: 8.
  • Page 87 11. 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. 12. 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 88 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 89 If your node is in… Then… A two-node MetroCluster Proceed to the next step. The MetroCluster switchback procedure is configuration done in the next task in the replacement process. A stand-alone configuration Proceed to the next step. No action is required. You have completed system-level diagnostics.
  • Page 90 (SVMs) on the formerly impaired site now active and serving data from the local disk pools. This task only applies to two-node MetroCluster configurations. Steps 1. Verify that all nodes are in the state: enabled metrocluster node show cluster_B::> metrocluster node show Configuration Group Cluster Node State...

  • Page 91: Swap Out A Fan - Fas8200

    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 92 Cam handle Fan module Cam handle release latch Fan module Attention LED 5. 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. CAUTION: The fan modules are short.

  • Page 93: Replace The Nvmem Battery - Fas8200

    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 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 94 If the impaired node is Then… displaying… System prompt or password Take over or halt the impaired node: prompt (enter system password) • For an HA pair, take over the impaired node from the healthy node: storage failover takeover -ofnode impaired_node_name When the impaired node shows Waiting for giveback…, press Ctrl-C, and then respond y.
  • Page 95 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Returning SEDs to unprotected mode" section of Administration overview with the CLI.
  • Page 96 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 97 mcc1A::> metrocluster operation show   Operation: heal-root-aggregates   State: successful  Start Time: 7/29/2016 20:54:41   End Time: 7/29/2016 20:54:42   Errors: - 8. On the impaired controller module, disconnect the power supplies. Step 2: 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.
  • Page 98 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 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 99 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 replacement battery from its package. 5. 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 100 diagnostic tests on the replaced component. 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. Do not completely insert the controller module in the chassis until instructed to do so. 2.
  • Page 101 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 102 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 103 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 104: Replace A Pcie Card - Fas8200

    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 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 105 If the impaired node is Then… displaying… Waiting for giveback… Press Ctrl-C, and then respond when prompted. System prompt or password Take over or halt the impaired node: prompt (enter system password) • For an HA pair, take over the impaired node from the healthy node: storage failover takeover -ofnode impaired_node_name...
  • Page 106 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Returning SEDs to unprotected mode" section of Administration overview with the CLI.
  • Page 107 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 108 mcc1A::> metrocluster operation show   Operation: heal-root-aggregates   State: successful  Start Time: 7/29/2016 20:54:41   End Time: 7/29/2016 20:54:42   Errors: - 8. On the impaired controller module, disconnect the power supplies. Step 2: 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.
  • Page 109 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 a PCIe card To replace a PCIe card, locate it within the controller and follow the specific sequence of steps.
  • Page 110 3. Remove the PCIe card from the controller module and set it aside. 4. Install the replacement 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 111 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 controller module configuration in until it meets the midplane and is fully seated, and then close the cam handle to the locked position.
  • Page 112 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 113: Swap Out A Power Supply - Fas8200

    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 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 114 Power supply Cam handle release latch Power and Fault LEDs Cam handle...

  • Page 115: Replace The Real-Time Clock Battery - Fas8200

    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 116 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 117 About this task • If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Returning SEDs to unprotected mode" section of Administration overview with the CLI.
  • Page 118 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 119 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 120 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 121 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 122 then boot it. 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 123 configuration to its normal operating state, with the sync-source storage virtual machines (SVMs) on the formerly impaired site now active and serving data from the local disk pools. This task only applies to two-node MetroCluster configurations. Steps 1. Verify that all nodes are in the state: enabled metrocluster node show...
  • Page 124 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 125 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:

Fas8200 systemsFas8200 system

Table of Contents