Restore and verify the configuration - AFF A900

To complete the chassis replacement, you must complete specific tasks.

Step 1: Verifying and setting 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.

  2. If the displayed system state for the chassis does not match your system configuration:

    1. Set the HA state for the chassis: ha-config modify chassis ha-state

      The value for HA-state can be one of the following:

      • ha

      • non-ha

  3. Confirm that the setting has changed: ha-config show

  4. If you have not already done so, recable the rest of your system.

Step2: Bring up the system

  1. If you have not done so, plug the power cables back into the PSUs.

  2. Turn on the PSUs by toggling the rocker switched to ON, and wait for the controllers to power up completely.

  3. Check the front and the back of the chassis and controllers for any fault lights after power up.

  4. Connect to the SP or BMC IP address of the nodes via SSH. This will be the same address used to shut down the nodes.

  5. Perform additional health checks as described in How_to_perform_a_cluster_health_check_with_a_script_in_ONTAP

  6. Turn AutoSupport back on (end the maintenance window message): system node autosupport invoke -node * -type all -message MAINT=end

Note As a best practice, you should do the following:

Step 3: Run system-level diagnostics

After installing a new chassis, you should run interconnect diagnostics.

Before you begin

Your system must be at the LOADER prompt to start System Level Diagnostics.

All commands in the diagnostic procedures are issued from the controller where the component is being replaced.

  1. If the controller to be serviced is not at the LOADER prompt, perform the following steps:

    1. Select the Maintenance mode option from the displayed menu.

    2. After the controller boots to Maintenance mode, halt the controller: halt

      After you issue the command, you should wait until the system stops at the LOADER prompt.

      Note During the boot process, you can safely respond y to prompts:
  2. Repeat the previous step on the second controller if you are in an HA configuration.

    Note 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 y 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. Run the interconnect diagnostics test from the Maintenance mode prompt: sldiag device run -dev interconnect

    You only need to run the interconnect test from one controller.

  6. Verify that no hardware problems resulted from the replacement of the chassis: sldiag device status -dev interconnect -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.

  7. Proceed based on the result of the preceding step.

If the system-level diagnostics tests…​ Then…​

Were completed without any failures

  1. Clear the status logs: sldiag device clearstatus

  2. Verify that the log was cleared: sldiag device status

    The following default response is displayed:

    SLDIAG: No log messages are present.
  3. Exit Maintenance mode on both controllers: halt

    The system displays the LOADER prompt.

    Note You must exit Maintenance mode on both controllers before proceeding any further.
  4. Enter the following command on both controllers at the LOADER prompt: bye

  5. Return the controller to normal operation.

If your system is running ONTAP…​ Then…​

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 cluster

Issue this command:node::> storage failover modify -node node0 -enabled true

In a stand-alone configuration

You have no further steps in this particular task. You have completed system-level diagnostics.

Resulted in some test failures

Determine the cause of the problem.

  1. Exit Maintenance mode: halt

  2. Perform a clean shutdown, and then disconnect the power supplies.

  3. 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.

  4. Reconnect the power supplies, and then power on the storage system.

  5. Rerun the system-level diagnostics test. + If the system-level diagnostics test fails again, contact

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.