Table of Contents
Advertisement
Step 2.
If the displayed system state of the controller module does not match your system configuration,
set the
state for the controller module:
HA
Step 3.
If the displayed system state of the chassis does not match your system configuration, set the
state for the chassis:
Running 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.
Step 1.
If the controller to be serviced is not at the LOADER prompt, reboot the controller:
After you issue the command, you should wait until the system stops at the LOADER prompt.
Step 2.
Run diagnostics on the caching module:
Step 3.
Display and note the available devices on the controller module:
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.
Step 4.
Run diagnostics for each component from the maintenance menu. For example:
-dev nvmem -long -state failed
ha-config modify controller ha-state
ha-config modify chassis ha-state
sldiag device run -dev fcache
sldiag device show -dev mb
.
Chapter 4
Hardware replacement procedures
HA
halt
The
sldiag device status
47
Advertisement
Table of Contents
