Skip to main content

Running system-level diagnostics

After installing a new DIMM, you should run 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. 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.
  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 failures resulting from testing the component.
  5. 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 by typing halt

      The controller displays the LOADER prompt.

    4. If the controller does not automatically start ONTAP, boot the controller from the LOADER prompt: boot_ontap
    5. Return the controller to normal operation by typing: storage failover giveback -ofnode replacement_node_name
    Resulted in some test failuresDetermine the cause of the problem:
    1. Exit Maintenance mode by typing halt

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

    3. Verify that you have observed all 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. Boot the controller module you are servicing, interrupting the boot by pressing Ctrl-C when prompted to get to the LOADER menu. If you removed the controller in the previous step, fully seat the controller module you are servicing in the chassis. The controller module boots up when fully seated.
    5. Select Boot to maintenance mode by typing boot_diags
    6. Repeat all the steps necessary to perform the system level diagnostics for the cache module.

    7. Exit Maintenance mode by entering the following command: halt

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

    8. Rerun the system-level diagnostic test.