Non-Concurrent Repair Procedures; Replacing A Single Controller Using The Cli - IBM BladeCenter S SAS RAID Controller Module Installation And User Manual

Sas raid controller module
Table of Contents

Advertisement

password. The FTDC Utility forces either or both controllers to restart if necessary
to collect the diagnostic information ftdc –ip 172.31.19.181 –allowoffline –log
mylog.
Development and Support Option
If you encounter a situation that makes it necessary to force the controller
firmware to restart and create the controller dump (CDUMP), you can enter the
parameter –forceoffline at the command line.
Note: Do not enter the –allowoffline parameter when using the -forceoffline
parameter. Example:
ftdc –ip 172.31.19.241 –forceoffline
CAUTION:
This option causes both controllers to reboot unconditionally and disrupts any
host I/O traffic . Users should only enter this option when directed to do so by
support personnel.

Non-concurrent repair procedures

Non-concurrent repair procedures must be performed only after all the application
I/O processes are stopped. This section contains the non-concurrent repair
procedures for the IBM BladeCenter S SAS RAID Controller Module.

Replacing a single controller using the CLI

Perform the following steps to non-concurrently replace a single RAID Controller
using the RAID Controller command line interface (CLI).
Procedure
154
IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module
1. Log into the chassis using the Advanced Management Module and illuminate
the blue chassis identification LED to ensure the repair action is conducted on
the correct chassis.
a. Log into the Advanced Management Module.
b. Click Monitors > LEDs > Media Tray and Rear Panel LEDs.
c. Click On or Blink next to Location. Depending on the selection, the blue
chassis identification LED will be in the SOLID or BLINKING state.
2. Stop all host I/O application processes.
3. Remove any externally attached devices that are connected to any of the four
SAS ports on the RAID Controller that is being replaced.
4. Log into the CLI of the RAID Controller.
5. At the <CLI> prompt, enter list controller and press Enter to verify the
controllers are operating in a dual primary-secondary state.
<CLI> list controller
_______________________________________________________________________
|
Ctlr#
|
Controller
|_____________|________________|____________________|_________|_________|
|
0 |
|
1 |
|_____________|________________|____________________|_________|_________|
6. At the <CLI> prompt, enter shutdown –ctlr <CONTROLLER 0 OR 1> –state
servicemode –readytoremove and press Enter to prepare the controller for
|
Status
Ctlr0|
PRIMARY|
Ctlr1|
SECONDARY|
| Ports | LUNs
|
1|
0|
1|
0|

Advertisement

Table of Contents
loading

Table of Contents