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 Memory
from the displayed menu.
5. Select an option from the displayed sub-menu and run the test.
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.
Step 6: Restore the controller module to operation after running diagnostics
After completing diagnostics, you must recable the system, give back the controller
module, and then reenable automatic giveback.
Steps
1. 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.
2. Return the node to normal operation by giving back its storage:
storage failover giveback
-ofnode
impaired_node_name
3. If automatic giveback was disabled, reenable it:
storage failover modify -node local -auto
-giveback true
Step 7: Switch back aggregates in a two-node MetroCluster configuration
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.
This task only applies to two-node MetroCluster configurations.
Steps
1. Verify that all nodes are in the
enabled
state:
metrocluster node show
85
