Can See EQL Array from ESX but not from VM

[MPCDI]

I'm not sure it what I have is setup correctly. I have a feeling that it isn't. The ESX host can see the EQL Array and boot the VM's from the Array, but the VM machines can NOT see it (ping or iSCSI initiator). The VM's boot with the IP of 10.10.10.* / 24 and all run Windows Server 2003 R2.

I was planning on using the Auto Snap-Shotmanger / Microsoft Edition so I need the VM's to see the EQL Array.

Setup:

Windows 2003 Server R2 SP2 - with vShere v4.0 Client

(3) ESX 4.0 Hosts with dual hardware HBA iSCSI Initators

On Switch #1

EQLogic Group: 10.10.10.170 with NICS 10.10.10.171, 10.10.10.172 &10.10.10.173 - VLAN100. All Volumes are restricted by IP of 10.10.10.*. CHAP is not used nor is the restirct by iSCSI initiator.

HOST1: HBA: 10.10.10.174 / 24 and 10.10.10.175 / 24 - VLAN100

HOST2: HBA: 10.10.10.176 / 24 and 10.10.10.177 / 24 - VLAN100

HOST3: HBA: 10.10.10.178 / 24 and 10.10.10.179 / 24 - VLAN100

On Switch #2

HOST1: NIC1,2,3 - 10.10.10.181 - VLAN1

HOST1: NIC1,2,3 - 10.10.10.182 - VLAN1

HOST1: NIC1,2,3 - 10.10.10.183 - VLAN1

I have attached some screen shots and a Visio diagram to help.

Thank You

[AndreTheGiant]

As you see in your diagram your iSCSI network (VLAN100) is isolated from your VM network (VLAN1).

You need to configure another VM portgroup on a vSwitch connected to the iSCSI switch and on VLAN100.

Then your VM must have 2 vNIC (if you also need to reach the EQL).

Note that your are using the same logical network both for VLAN1 and VLAN100... you will have routing problem with this configuration... change it with 2 different logical network.

Andre

[MPCDI]

Thank you VERY much.

Originally I had 10.10.10.* on the VLAN1 and then 192.168.10.* but when I called EQL they told me that I needed to put them on the same subnet but separate out the switch with VLAN's. At the time it didn't make that much sense, but I figured they knew what they were doing. The tech told me that the ESX Host actually routes the information between the LAN NIC and the iSCSI so when the VM needs access the the iSCSI it will route it to it's appropriate location.

[AndreTheGiant]

The tech told me that the ESX Host actually routes the information between the LAN NIC and the iSCSI so when the VM needs access the the iSCSI it will route it to it's appropriate location.

ESX does not perform routing operations.

You need an external router or a dual NIC configuration.

Andre