cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Musayev, Ilya" <>
Subject RE: Router VM and Network Issue
Date Mon, 03 Dec 2012 20:36:47 GMT

It does ping the local gateways and I can see that happening when router VM boots up. 

But the fix is to ping either CS Core or CS gateway - that truly addresses the issue.

Any thoughts of how I can create this behavior in reproducible fashion for all new routers?


-----Original Message-----
From: Anthony Xu [] 
Sent: Monday, December 03, 2012 3:12 PM
Subject: RE: Router VM and Network Issue

I remember we have a fix for this, when route VM boots up, it tries to ping default gateway
to propagate its MAC to switch.

Might be this fix is not checked into CS 4.0


> -----Original Message-----
> From: Musayev, Ilya []
> Sent: Monday, December 03, 2012 10:59 AM
> To:
> Subject: Router VM and Network Issue
> So I hit a glitch where a router VM boots up but does not really pass 
> any traffic unless I ping the gateway of the CS host from within the 
> router VM.
> Once the gateway ping goes through, CS is able to SSH into a router VM 
> and everything is fine and dandy..
> But this behavior really puzzles me. Linux network stack is not fully 
> activated or routing is not fully functional until the initial CS GW 
> ping.
> Also I cant ping/ssh the router VM from CS unless a initiate a ping 
> from within the router VM.
> I'm on CS 4.0 and vSphere5. This seem to affect the Advanced Network 
> setup more than Basic because of routing complexity - as you add some 
> routes into linux routing table.
> Has anyone seen this before?

View raw message