Skip to main content

Running 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 get to the maintenance menu to start System Level Diagnostics.

About this task

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

      Attention
      You must exit Maintenance mode on both controllers before proceeding any further.
    4. Enter the following command on both controllers at the LOADER prompt: boot_ontap
    5. Return the controller to normal operation:
      If your system is running ONTAP...Then...
      With two controllers in the clusterIssue these commands:

      node::> cluster ha modify -configured true

      node::> storage failover modify -node node0 -enabled true

      With more than two controllers in the clusterIssue this command:

      node::> storage failover modify -node node0 -enabled true

    You have completed system-level diagnostics.

    Resulted in some test failuresDetermine 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.