76dragon
Enthusiast
Enthusiast

ESX server cant see iSCSI target

Hi All.

Ive been using iSCSI for a long time now with an unmanaged switched so all interfaces are have been on the same network segment.

Ive now purchased a Managed switch and Im having trouble getting my ESX server to see the iSCSI target.

Ive got the following setup

Service Console vswif0 with 2x physical adapters on 192.168.0.x

Virtual Machine Network with 2 pysical adapters on the same network above (isolating the SC is another project)

VMotion with single pysical nic using 192.168.10.x

iSCSI Storage with 2x physical nics with a second service console vswif1 using 192.168.20.10 and a VMkernel port configured using 192.168.20.11

Both nics with vswif1 and VMkernel are patched into switch using VLAN 5 and ive configured the VLAN ID in the properties of both SC and VMKernel but im still unable to see the iscsi target which is also patched into the same VLAN with appropriate VLAN configuration.

Im wondering how i should set the default GW settings for both of these and if anyone can spot why this is not working

thanks

0 Kudos
2 Replies
JeffDrury
Hot Shot
Hot Shot

It's likely that your physical switch isn't passing VLAN information on to your ESX box. A quick fix would be to remove the VLAN tag on your iSCSI port group. The best opiton would be to configure the ports on your physical switch that are connected to your ESX server as trunk ports. This will cause the physical ports to pass VLAN tags onto the ESX box and the port groups will then do their thing by recognizing traffic with VLAN tags.

76dragon
Enthusiast
Enthusiast

Thanks Jeff, Im looking at it now and the problem Im sure is a link aggregation problem with the Procurve switches.

As ESX does not support Dynamic LACP it seem Im going to have to configure the trunk as type TRUNK rather than LACP.

Thanks for the response.

0 Kudos