Step 2: Verify and set the HA state of the controller module
You must verify the
HA state of the controller module and, if necessary, update the state to match your system
configuration.
1.
In Maintenance mode from the new controller module, verify that all components display the same
HA
state: ha-config show
The HA state should be the same for all components.
2.
If the displayed system state of the controller module does not match your system configuration, set the
HA
state for the controller module: ha-config modify controller ha-state
The value for HA-state can be one of the following:
◦ ha
◦ mcc
◦ mcc-2n
◦ mccip
◦ non-ha
3.
If the displayed system state of the controller module does not match your system configuration, set the
HA
state for the controller module: ha-config modify controller ha-state
4.
Confirm that the setting has changed:
ha-config show
Step 3: Run system-level diagnostics
You should run comprehensive or focused diagnostic tests for specific components and subsystems whenever
you replace the controller.
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, reboot the controller:
halt
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
During the boot process, you can safely respond y to the prompts until the Maintenance mode prompt (*>)
appears.
3. Display and note the available devices on the controller module:
sldiag device show -dev mb
The controller module devices and ports displayed can be any one or more of the following:
47
To Next Page
Loading...
