â–ª
ha
â–ª
mcc
â–ª
mcc-2n
â–ª
mccip
â–ª
non-ha
b.
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 node where the component is being replaced.
1.
If the node to be serviced is not at the LOADER prompt, reboot the node:
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:
â—¦
bootmedia is the system booting device..
â—¦ cna is a Converged Network Adapter or interface not connected to a network or storage device.
â—¦ fcal is a Fibre Channel-Arbitrated Loop device not connected to a Fibre Channel network.
â—¦
env is motherboard environmentals.
â—¦ mem is system memory.
â—¦ nic is a network interface card.
â—¦
nvram is nonvolatile RAM.
â—¦
nvmem is a hybrid of NVRAM and system memory.
â—¦
sas is a Serial Attached SCSI device not connected to a disk shelf.
4. Run diagnostics as desired.
146