Highlighted
Contributor
Contributor

HP P2000 G3 SAS Multipath Configuration with Vmware HOSTS

Hi , we are having a weird problem with out HP SAN Setup with our VMware hosts , we have our san connected via 2 controllers ( A and B ) into each VMWare host.

Controller A port 1 goes to vmware hostA

Controller B port 1 goes to vmware hostA

Controller A port 2 goes to vmware hostB

Controller B port 2 goes to vmware hostB

Controller A port 3 goes to vmware hostC

Controller B port 3 goes to vmware hostC

when we fail over 1 controller on the SAN ( by rebooting the controller ) , it causes the vmware host to completely lose connection to our storage instead of failing over to the connection on the other controller on the SAN and we can only get it back by rebooting the vmware host causing downtime.

Our vmware configuration is shown in the attached screenshots.

thanks in advance and kind regards

output of ( esxcfg-mpath --list )

~ # esxcfg-mpath --list

  1. usb.vmhba32-usb.0:0-mpx.vmhba32:C0:T0:L0

   Runtime Name: vmhba32:C0:T0:L0

   Device: mpx.vmhba32:C0:T0:L0

   Device Display Name: Local USB Direct-Access (mpx.vmhba32:C0:T0:L0)

   Adapter: vmhba32 Channel: 0 Target: 0 LUN: 0

   Adapter Identifier: usb.vmhba32

   Target Identifier: usb.0:0

   Plugin: NMP

   State: active

   Transport: usb

  1. sata.vmhba0-sata.0:0-mpx.vmhba0:C0:T0:L0

   Runtime Name: vmhba0:C0:T0:L0

   Device: mpx.vmhba0:C0:T0:L0

   Device Display Name: Local hp CD-ROM (mpx.vmhba0:C0:T0:L0)

   Adapter: vmhba0 Channel: 0 Target: 0 LUN: 0

   Adapter Identifier: sata.vmhba0

   Target Identifier: sata.0:0

   Plugin: NMP

   State: active

   Transport: sata

  1. sas.500605b0045cce00-sas.500c0ff135bcc000-naa.600c0ff00013989d0000000000000000

   Runtime Name: vmhba2:C0:T1:L0

   Device: naa.600c0ff00013989d0000000000000000

   Device Display Name: HP Serial Attached SCSI Enclosure Svc Dev (naa.600c0ff00013989d0000000000000000)

   Adapter: vmhba2 Channel: 0 Target: 1 LUN: 0

   Adapter Identifier: sas.500605b0045cce00

   Target Identifier: sas.500c0ff135bcc000

   Plugin: NMP

   State: active

   Transport: sas

   Adapter Transport Details: 500605b0045cce00

   Target Transport Details: 500c0ff135bcc000

  1. sas.500605b0045cce00-sas.500c0ff135bcc000-naa.600c0ff00013989dc2164e4f01000000

   Runtime Name: vmhba2:C0:T1:L1

   Device: naa.600c0ff00013989dc2164e4f01000000

   Device Display Name: HP Serial Attached SCSI Disk (naa.600c0ff00013989dc2164e4f01000000)

   Adapter: vmhba2 Channel: 0 Target: 1 LUN: 1

   Adapter Identifier: sas.500605b0045cce00

   Target Identifier: sas.500c0ff135bcc000

   Plugin: NMP

   State: active

   Transport: sas

   Adapter Transport Details: 500605b0045cce00

   Target Transport Details: 500c0ff135bcc000

  1. sas.500605b0045cce00-sas.500c0ff135bcc400-naa.600c0ff0001395430000000000000000

   Runtime Name: vmhba2:C0:T0:L0

   Device: naa.600c0ff0001395430000000000000000

   Device Display Name: HP Serial Attached SCSI Enclosure Svc Dev (naa.600c0ff0001395430000000000000000)

   Adapter: vmhba2 Channel: 0 Target: 0 LUN: 0

   Adapter Identifier: sas.500605b0045cce00

   Target Identifier: sas.500c0ff135bcc400

  Plugin: NMP

   State: active

   Transport: sas

   Adapter Transport Details: 500605b0045cce00

   Target Transport Details: 500c0ff135bcc400

  1. sas.500605b0045cce00-sas.500c0ff135bcc400-naa.600c0ff00013989dc2164e4f01000000

   Runtime Name: vmhba2:C0:T0:L1

  Device: naa.600c0ff00013989dc2164e4f01000000

   Device Display Name: HP Serial Attached SCSI Disk (naa.600c0ff00013989dc2164e4f01000000)

   Adapter: vmhba2 Channel: 0 Target: 0 LUN: 1

   Adapter Identifier: sas.500605b0045cce00

   Target Identifier: sas.500c0ff135bcc400

   Plugin: NMP

   State: active

   Transport: sas

   Adapter Transport Details: 500605b0045cce00

   Target Transport Details: 500c0ff135bcc400

~ #

0 Kudos
2 Replies
Highlighted
VMware Employee
VMware Employee

Moderator: Moved to vSphere Storage


Forum Usage Guidelines: https://communities.vmware.com/docs/DOC-12286
VMware Training & Certification blog: http://vmwaretraining.blogspot.com
0 Kudos
Highlighted
Commander
Commander

Hi

Is this happened on all of your 3 ESXi hosts? (losing connectivity on failover operation between SAN storage controllers)

When everything is ok (before required to failover) did you check the 2nd controller is operating normally?! Did you check the P2000 event logs especially in time of failover!?

Please run the following command before and after failover between the SAN controllers:

esxcli storage core device list

Please mark my comment as the Correct Answer if this solution resolved your problem
0 Kudos