Topic
3 replies Latest Post - ‏2013-08-21T10:35:55Z by Novikov_Alexander
IT System Admin
IT System Admin
2 Posts
ACCEPTED ANSWER

Pinned topic Logical Drive not on preferred path

‏2013-08-20T16:14:50Z |

Hello,

We currently have setup an expansion unit to our IBM DS3512 and have setup the following:

1. 6 Logical drives at 2 TB each

2. We have mapped the drives to 6 LUNs.

Every time we set any of these drives as a data store within Vsphere on any of the ESX hosts we start receiving the below error messages that relate to both A and B controllers.

I have run the Advanced, Recovery and Redistribute Logical drives with the same results.

Has anyone had this same issue and if so how was it resolved.

Any help will be appreciated.

Summary

Node ID: DS3500_SAN

Host IP Address:

Host ID: Out-of-Band

Event Error Code: 4011

Event occurred: Aug 16, 2013 4:24:32 PM

Event Message: Logical Drive not on preferred path due to ADT/RDAC failover Event Priority: Critical Component Type: Controller Component Location: Enclosure 0, Slot A

Summary

Node ID: DS3500_SAN

Host IP Address:

Host ID: Out-of-Band

Event Error Code: 4011

Event occurred: Aug 16, 2013 3:58:54 PM

Event Message: Logical Drive not on preferred path due to ADT/RDAC failover Event Priority: Critical Component Type: Controller Component Location: Enclosure 0, Slot B

  • AndersLorensen
    AndersLorensen
    139 Posts
    ACCEPTED ANSWER

    Re: Logical Drive not on preferred path

    ‏2013-08-20T19:42:11Z  in response to IT System Admin

    This error Means that there is an error on the multipathing. This can happen if the Storage system is cabled wrong. You dont give any detail whenever you connect with SAS, iSCSI or FC, so its hard to give concrete help with that, except read the redbook on how to attached the hosts to the DS3512, or reply with your setup.

     

    What happens is that a LUN is owned by a preferred controller, and when it fails over to the other controller, you get the error. Often the LUN will failover between the controllers only when there is a hardware error on a switch or one of the controllers.

    I've seen it happen because people cable the system wrong. (for example, cable one controller to one switch, and the other to another switch. All HBA's on all servers using the SAN needs to be able to connect to both controllers. (Except when using Direct SAS connectivity though)

    You also need to make sure your host type is chosen correctly for each and every host object. If you use vSphere 5.0U1 or later, you should use VMWareALUA, if 5.0RTM and below, use VMWare as hosttype.

     

    --

    Anders

    • IT System Admin
      IT System Admin
      2 Posts
      ACCEPTED ANSWER

      Re: Logical Drive not on preferred path

      ‏2013-08-20T20:51:57Z  in response to AndersLorensen

      Anders

      Thank you for your response.

      Just to confirm we already had an existing SAN controller (FC) that has been working fine with no issues for quite some time.

      The hosts are all running VSphere 4.1U2 (4.1.0,260247) there is no switch between the controller, the expansion unit and all the ESX hosts.

      The SAS Cables are connected as shown in the attached manual. Out to the in ports.

      JP

       

      Attachments