1. If the node to be serviced is not at the LOADER prompt, reboot the node:
system node halt -node
node_name
After you issue the command, you should wait until the system stops at the LOADER prompt.
2. At the LOADER prompt, access the special drivers specifically designed for system-level diagnostics to
function properly:
boot_diags
3. Select
Scan System
from the displayed menu to enable running the diagnostics tests.
4. Select
Test system
from the displayed menu to run diagnostics tests.
5. Select the test or series of tests from the various sub-menus.
6. Proceed based on the result of the preceding step:
◦
If the test failed, correct the failure, and then rerun the test.
◦
If the test reported no failures, select Reboot from the menu to reboot the system.
During the boot process, you might see the following prompts:
▪
A prompt warning of a system ID mismatch and asking to override the system ID.
▪
A prompt warning that when entering Maintenance mode in an HA configuration you must ensure
that the healthy node remains down.
You can safely respond
y
to these prompts.
Recable the system and reassign disks - AFF A400
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.
Steps
1. Recable the system.
2. Verify that the cabling is correct by using
.
a. Download and install Config Advisor.
b. Enter the information for the target system, and then click Collect Data.
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
procedure. You must confirm the system ID change when you boot the
replacement
node
and then verify that the change was implemented.
58
