Pulling my hair out...

[mpicher]

Please see attached picture.



My VM Hosts (ESX 3.5) can ping each other, the network switch, the other SAN device but not the DSS server.

The network switch can ping all devices. A little more detail in the diagram...

What the heck!?!?!?

[symm]

looks as it should work

have you tried to ping from the dss to the vmware box ?
console ctrl alt t
ping

let us know if it works

[jmo]

Please see attached picture.



My VM Hosts (ESX 3.5) can ping each other, the network switch, the other SAN device but not the DSS server.

The network switch can ping all devices. A little more detail in the diagram...

What the heck!?!?!?

Apart from the typo with the IP of vmnic1 of vmwarer2 (I assume that's supposed to be 172.29.1.12) the diagram looks fine.

Which address(es) have you been pinging specifically? Can the VMserver reach both routing interfaces of the switch? Can it reach none of the three interfaces of the DSS?

After (unsuccessfully) pinging the DSS from the VMserver - what's in the arp table of the VMserver?

With regards

Jens

[mpicher]

I think I found the source of the problem... for some reason traffic will not leave the VMKernel adapter. Very odd... If I add another service console on to the network adapter that has vmnic2 i can then get to the DSS box.

We did a tcpdump to watch the traffic and the traffic is coming from the service console IP and not the vmkernel IP. Really messed up.

We're ripping exp 3.5 off of that vmhost and loading up 4 now to see how it behaves.

Thanks. Sorry for wasting time...

Mike

[1parkplace]

I had a similar problem with the VMKernel on 3.5

A reboot of the ESX server fixed it for me.

[1parkplace]

ESX 4.0 does not require a service console for the VMKernel to function. Keep that in mind during configuration.