Apologies for the late response. None of the virtual routers I have spun up have ever been on the management network. I haven't dug into it too deeply but from what I can gather based on the vNICs assigned the management server has the host backdoor in through the link-local address and issues commands that way.
-----Original Message----- From: Deepak Garg [mailto:deepak.g...@citrix.com] Sent: Wednesday, June 06, 2012 8:35 PM To: cloudstack-dev@incubator.apache.org Subject: RE: Networking question Thanks, but in the pdf of System VMs, VR is not shown in the management network. Is this correct ? How is management server supposed to talk to VR in this case ? Deepak -----Original Message----- From: Clayton Weise [mailto:cwe...@iswest.net] Sent: Thursday, June 07, 2012 1:49 AM To: 'cloudstack-dev@incubator.apache.org' Subject: RE: Networking question Sort of like this? http://wiki.cloudstack.org/display/COMM/CloudStack+Example+Configurations Specifically the "Cloudstack System VMs" document(s). -----Original Message----- From: Deepak Garg [mailto:deepak.g...@citrix.com] Sent: Wednesday, June 06, 2012 12:56 PM To: cloudstack-dev@incubator.apache.org Subject: Networking question HI All, It gets confusing sometime but it will be nice if someone can give an exact table of which system vm ( Virtual Router, Console Proxy, Secondary Storage ) has vifs in which networks ( public, private, guest ) in the different zones (Basic and Advanced). Public Nw -> Traffic sent to this network will be sent to publicly routable network Private Nw -> Internal traffic between XS hosts, system vms Guest Nw -> Internal traffic between guest vms of an account Basic Zone: VR -> SS VM -> CP VM -> Basic Zone with EIP/ELB: VR -> SS VM -> CP VM -> Advanced Zone: VR -> SS VM -> CP VM -> e.g. in all the three cases VR has a vif in all the three networks. VR -> public, private, guest Please add or correct if I missed anything. Thanks, Deepak
