1 |
If... |
Then... |
The controller was NOT manually changed to the passive mode |
Go to step 2. |
The controller was manually changed to the passive mode |
Change the controller mode to active by highlighting the controller in the Physical View of the Subsystem Management
Window and selecting Controller>>Change Mode>>Active.
Then, go to step 9. |
|
2 |
If... |
Then... |
The controller was NOT manually taken offline |
Go to step 3. |
The controller was manually taken offline |
- Place the controller back online by highlighting the controller in the Physical View of the Subsystem Management
Window and selecting Controller>>Place Online.
- Change the controller mode to active by highlighting the controller and selecting Controller>>Change
Mode>>Active.
Then, go to step 9.
|
|
3 |
If you are running host-based, multi-path driver software other than RDAC, verify the software is configured correctly.
If you are not running any multi-path software or you are running RDAC, go to step 4.
Consult your multi-path driver software documentation to determine the preferred and alternate path configuration
settings.
If... |
Then... |
Your multi-path driver software is configured correctly |
Go to step 4. |
Your multi-path driver software is not configured correctly |
Correct the problem. Then, go to step 8. |
|
4 |
Check the following components on both ends of the connection for loose connections or visible damage:
Caution
If multiple Storage Subsystems share the same cabling path, removing cables can cause I/O failures to occur on all
Storage Subsystems on the path. Therefore, visibly check the cable connections first and then, if you still suspect
a cable problem, make sure you are aware of any I/O activity occurring on the other Storage Subsystems.
- External cables
- Terminators (SCSI connection only)
- Hubs and switches (Fibre connection only)
If... |
Then... |
The connection components are OK |
Go to step 5. |
There is a problem with the connection |
Fix the connection problem. Then, go to step 8. |
|
5 |
Use the information in the following table to determine the action to take.
If the host connected to this Storage Subsystem... |
Then... |
is NOT connected to any other Storage Subsystems. |
Verify that its host adapter is operational.
- If the host adapter is operational, the controller in the Storage Subsystem is probably defective. Go to step 6.
- If the host adapter is defective, correct the problem, then go to step 8.
|
is connected to other Storage Subsystems. |
Check the Enterprise Management Window for Storage Subsystems showing a Needs Attention status.
- If all of the Storage Subsystems connected to the same host/host adapter are not reporting a Needs Attention status,
then the controller in the Storage Subsystem is probably defective. Go to step 6.
- If all of the Storage Subsystems connected to the same host/host adapter are showing a Needs Attention status,
then the associated host adapter is probably defective. Fix the host adapter problem, then go to step 8.
|
|
6 |
Remove the defective controller indicated in the Details area.
Note: If the Storage Subsystem is Directly Managed (refer to the Network Management Type column in the Enterprise
Management Window), you must update the DHCP/BOOTP server so that it will associate the new controller's hardware
Ethernet address with the host name and IP address previously assigned to the failed controller before you go to
step 7. To update the DHCP/BOOTP server, find the entry associated with the removed controller and replace its
Ethernet address with the new controller's Ethernet address. The controller's Ethernet address is located on an
Ethernet ID label near the back of the controller canister. If you need more details, consult the installation
guide. |
|
7 |
Make sure at least 1 minute has elapsed; then, insert the new controller firmly into place. |
8 |
Note the controller slot of the affected controller listed in the Details area above. Highlight this controller
slot in the Physical View of the Subsystem Management Window and select Controller>>Change Mode.
If... |
Then... |
The controller's Mode is Active |
Go to step 9. |
The controller's Mode is Passive |
Change the controller to Active. Then, go to step 9. |
|
9 |
Redistribute the logical drives to their preferred controllers by selecting Storage Subsystem>>Redistribute Logical Drive
Groups from the Subsystem Management Window. |
10 |
Select Recheck to rerun the Recovery Guru to ensure that the failure has been fixed.
If... |
Then... |
Another type of failure is reported |
Follow the recovery procedures given for that failure. |
No failures are reported |
You are finished with the Recovery procedure.
Note: If you replaced the controller and the file systems/logical drives do not respond, reboot your host system. |
|