Thanks Erik, Its RESOLVED. it turnedout to be an network switch issue. Blade switch was configured with vlans so vms were pining in single blade chassie but* cloud vlans were not configured in Lan switches* so traffic was not able to go outside. my virtual router was in different blade chassie therefore it was not able to take dhcp address.
I am started facing another issue in shared network: when i added additional *shared network* to VM it was *not able take DHCP address from shared network ip pool*. Do we have to assign ip mannualy or any settings required? Thanks, Tejas On Fri, Dec 12, 2014 at 2:21 PM, Erik Weber <terbol...@gmail.com> wrote: > > On Fri, Dec 12, 2014 at 9:30 AM, Tejas Sheth <tshet...@gmail.com> wrote: > > > > Hello, > > > > I have deployed advanced zone and deployed windows 2008 VM instance. > The > > VM instance is connected to isolated network. > > > > The issue is none of the VMs are getting dhcp address from virtual > router. > > I tried to restart virtual router but still no DHCP address from vRouter. > > > > Any suggestion? > > > > > 1) Has it previously worked or is this a new network? > 2) Log on to the VR, and verify that dnsmasq is running, and that there is > free space on all partitions > 3) On the VR, start tcpdump and see if it receives and/or sends traffic > (command: tcpdump -nn -v -X -A port 68) > 4) If you cannot see the traffic in point three, try setting a static ip on > the guest and check if you can ping the VR > 5) What is your cloudstack version, hypervisor type, hypervisor version, > network isolation type? > > If point 3 or 4 fails it might be a network configuration issue, missing > trunk ports or similar, depending on isolation type. > > -- > Erik >
