Logical Drive Not On Preferred Path

What Caused the Problem?
The host is unable to access its logical drives on the preferred path. These logical drives are now assigned to the Storage Subsystem's alternate controller. Possible causes include:

The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Caution
Do not replace the controller until you are instructed to do so. This procedure will instruct you to check the components along the connection, check the host adapters, and eventually instruct you to replace the controller, if necessary.

Caution
Electrostatic discharge can damage sensitive components. Use a grounding wrist strap or other anti-static precautions before removing or handling components.

Important Notes

When Auto Logical Drive Transfer (ADT) is enabled, it can take up to 10 minutes for the host based, multi-path driver to recognize a restored or modified preferred path. A Logical Drive Not On Preferred Path error will be reported during this time. If you have recently modified the preferred path using the Array>>Change Ownership or Logical Drive>>Change Ownership menu options or performed a recovery procedure that has restored a preferred path, wait at least 10 minutes and run the Recovery Guru again using the Recheck button. If this error is reported again, perform the recovery procedures listed below. Use the Storage Subsystem Profile to determine whether you have ADT enabled by selecting the Storage Subsystem>>Profile menu option from the Subsystem Management Window and locating the ADT entry.

Recovery Steps
1
If... Then...
The controller was NOT manually changed to Passive mode Go to Step 2.
The controller was manually changed to 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 10.
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.
Then, go to Step 10.
3 Check the following components on both ends of the connection for loose connections or visible damage:
  • External cables
  • Hubs and switches

If... Then...
The connection components are OK Go to Step 4.
There is a problem with the connection Fix the connection problem. Then, go to Step 8.

4 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 5.
  • 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 one or more Storage Subsystems connected to this host/host adapter does not have a Needs Attention status, then the controller in the Storage Subsystem is probably defective. Go to Step 5.
  • If every Storage Subsystem connected to this host/host adapter has a Needs Attention status, then the associated host adapter is probably defective. Fix the host adapter problem, then go to Step 8.
5 Remove the defective controller. The defective controller is listed in the Details area.

Note: Before you insert a new controller canister into a Directly Managed Storage Subsystem (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 removed controller.
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 on the controller canister in the form xx.xx.xx.xx. If you need more details, consult the Storage System Planning Guide.
6 Make sure at least 1 minute has elapsed; then, insert the new controller canister firmly into place.
7
If... Then...
The controllers for this Storage Subsystem are located in an enclosure containing only controllers Go to Step 8.
The controllers for this Storage Subsystem are located in an enclosure containing both controllers and drives The new controller's cache battery age must be reset. To reset the battery age, select the Components button on the enclosure containing the controllers in the Physical View of the Subsystem Management Window. Highlight the Batteries option and select the Reset button associated with the new controller canister. Go to Step 8.
8
If... Then...
The controller is NOT Offline Go to Step 9.
The controller is Offline. Place the controller Online by highlighting the controller in the Physical View of the Subsystem Management Window and selecting Controller>>Place Online.
Then, go to Step 10.
9 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, then select Controller>>Change Mode.
If... Then...
The controller's Mode is Active Go to Step 10.
The controller's Mode is Passive Change the controller to Active. Then, go to Step 10.
10 Locate the Automatic Logical Drive Transfer (ADT) entry in the Storage Subsystem Profile. To open the profile select the Storage Subsystem>>Profile menu option from the Subsystem Management Window.

If... Then...
The Auto Logical Drive Transfer (ADT) entry is set to Disabled

OR

You ARE NOT running a host based, multi-path driver

Redistribute the logical drives to their preferred controller by selecting Storage Subsystem>>Redistribute Logical Drives from the Subsystem Management Window.
The Auto Logical Drive Transfer (ADT) entry is set to Enabled

AND

You ARE running a host based, multi-path driver

The host based, multi-path driver will automatically initiate a transfer of logical drives to their preferred controller.

11 Note: When Auto Logical Drive Transfer (ADT) is enabled, it can take up to 10 minutes for the host based, multi-path driver to recognize a restored preferred path. Wait at least 10 minutes before selecting Recheck to ensure the failure has been fixed. Use the Storage Subsystem Profile to determine whether you have ADT enabled by selecting the Storage Subsystem>>Profile menu option from the Subsystem Management Window and locating the ADT entry.

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.