So it's expected that it uses an IP address from the management network on the domain router? I typically only set aside 10 or so IP addresses from the management network for CloudStack usage for things like SSVM and console proxy. Am I going to have to allocate a lot more of my management IP addresses now? Also, I believe I did use the 5.1 SDK. Thanks for the replies guys!
----- Original Message ----- From: "Kirk Kosinski" <kirkkosin...@gmail.com> To: users@cloudstack.apache.org Cc: "Jayapal Reddy Uradi" <jayapalreddy.ur...@citrix.com> Sent: Friday, September 6, 2013 2:37:37 AM Subject: Re: VMware DomainRouter Right, since on KVM and XS hosts we can run scripts directly on the host to communicate with system VMs, whereas on ESXi this is discouraged and not even possible by default. Best regards, Kirk On 09/05/2013 10:07 PM, Jayapal Reddy Uradi wrote: > This is expected in vmware. In Xen and KVM we have link local IP address. > > Thanks, > Jayapal > > On 06-Sep-2013, at 3:46 AM, John Skinner <john.skin...@appcore.com> wrote: > >> Hello list, >> >> I just setup a CloudStack 4.1 environment with vSphere 5.1. Everything seems >> to be working ok for the most part. However, I have noticed that my domain >> routers are getting created with a management IP address for the control >> network instead of a control network IP address (the link local IP >> addresses). Is this expected behavior? >> >
