VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
3 Replies Last post: Nov 4, 2009 8:49 AM by jschlach  

Cannot ping GW from VM's in fenced mode posted: Aug 28, 2007 3:51 PM

Click to view khai's profile Enthusiast 29 posts since
May 23, 2007
Hi All,

I'm having a problem getting to the gateway from the VM's deployed in fenced mode in lab manager. Here's the info, hopefully someone has ran into this before.

- GW - IP 10.59.70.1

When I deploy VM1 & VM2 in fenced mode (allow traffic in and out), I was able to ping VM1 from VM2 and vice versa. From either VM1 or VM2, I was able to ping the physical server .70.55 addresss, which means I was able to get out of the vRouter. But I cannot ping the GW (gateway) from VM1 or VM2. What's going on?

Btw, if I deploy in un-fenced mode, everything works fine.

I'm including the traceroute output for more info.
======
C:\Documents and Settings\Administrator.PS.000>tracert 10.59.70.55

Tracing route to w2k3 [10.59.70.55]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.59.70.148
2 <1 ms <1 ms <1 ms FEDWEST960 [10.59.70.55]

Trace complete.

C:\Documents and Settings\Administrator.PS.000>tracert 10.59.70.1

Tracing route to 10.59.70.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.59.70.148
2 * 10.59.70.146 reports: Destination host unreachable.

Trace complete.

Re: Cannot ping GW from VM's in fenced mode

1. Aug 28, 2007 4:26 PM in response to: khai
Click to view anupam0's profile Enthusiast 24 posts since
Jul 26, 2006
Do other fenced configurations have network connectivity?

This could be related to http://www.vmware.com/community/message.jspa?messageID=716889#716889

You will need to refer to your Lab router's manual to find out how to change the ARP cache timeout.

Re: Cannot ping GW from VM's in fenced mode

3. Nov 4, 2009 8:49 AM in response to: khai
Click to view jschlach's profile Enthusiast 124 posts since
Dec 11, 2006
i've just come across this, but strangely in just one of my configurations. looking into it, i saw that my VM had a cached arp entry for its default gateway ip address which didn't match that of the virtual router. my solution was to deploy the config, suspend the VR, delete all arp table entries in the guest VM, then capture back to library. when that's then checked out, it has to build a fresh arp cache and picks up the correct mac address of its gateway.

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities