Highlighted
atorres1
1 Nickel

Connecting Clariion AX4 and ESXi 4

Could help me with a question, I have the following scenario;

I have a storage AX4 iSCSI and 2 servers host ESXi 4.1 which has 2 HBA 1 port iSCSI c/u. configuring storage ports and servers is as follows.

AX4-i

SPA-0: 10.10.5.101 SPA-1: 10.10.5.102

SPB-0: 10.10.6.101 SPB-0: 10.10.6.102

ESXi1 (connected to the SPA-0 and SPB-0)

vSwitch

iSCSI1: 10.10.5.103 iSCSI1: 10.10.6.103

NIC Teaming

NIC2: ACTIVE NIC3: ACTIVE

NIC3: UNUSED NIC2: UNUSED

ESXi2 (connected to the SPA-1 and SPB-1)

vSwitch

iSCSI1: 10.10.5.104 iSCSI1: 10.10.6.104

NIC Teaming

NIC2: ACTIVE NIC3: ACTIVE

NIC3: UNUSED NIC2: UNUSED

Navisphere Express connections option appears for a moment the two ports active, but when recognizes the luns presented to a single esx maintains an active port and other inactive, the luns path refers to an ip address, and now Navisphere Express looks that only activates a port by controller and not the two connected.

ESXi1

A0 - INACTIVE

A1 - INACTIVE

B0 - ACTIVE

B1 - INACTIVE

ESXi2

A0 - INACTIVE

A1 - INACTIVE

B0 - INACTIVE

B1 - Active

If you have any information to help me fix this would be much appreciated.

atc

0 Kudos
1 Reply
JoeLawson
1 Copper

Re: Connecting Clariion AX4 and ESXi 4

Hi Buddy,

You need to read this: http://www.vmware.com/pdf/vsphere4/r40/vsp_40_iscsi_san_cfg.pdf

Page 23 explains: Path Selection Plugins

Path Selection Plugins (PSPs) run in conjunction with the VMware NMP and are responsible for choosing a

physical path for I/O requests.

The VMware NMP assigns a default PSP for every logical device based on the SATP associated with the physical

paths for that device. You can override the default PSP.

By default, the VMware NMP supports the following PSPs:

Most Recently Used

(MRU)

Selects the path the ESX/ESXi host used most recently to access the given device.

If this path becomes unavailable, the host switches to an alternative path and

continues to use the new path while it is available.

Basically by default ESX only uses one path. Switching it to round robin might help.  Make sure you test all your hosts connectivity and check switches for errors when you do this.

This link is old but still informative:

http://blogs.netapp.com/virtualstorageguy/2009/01/a-multivendor-p.html

Hope this helps.

-Joe

0 Kudos