Thanks guys. In the end I just set the Global Settings host variable and
that worked great rather than messing around with the host files as there
are other services currently running on the box that depend on hostname
--fqdn coming back with the hostname that resolves to 10.1.1.2.
Responses much
Hi Tejas,
Good to know agent is running now.
What you have fixed to run the agent?
Thanks
Rajesh Battala
-Original Message-
From: Tejas Gadaria [mailto:refond.g...@gmail.com]
Sent: Thursday, January 30, 2014 8:57 PM
To: Anshul Gangwar; users@cloudstack.apache.org
Subject: Re: hyper-v ag
Hi, the IP host connect to can be configured with the "host" parameter
in Global Settings. The initial setup probably detected the 10.1.1.2 IP
and configured the host parameter with it, but you should change it to
the desired IP.
Best regards,
Kirk
On 02/02/2014 12:48 AM, Zack Payton wrote:
> Hi
Hi Zack,
Thanks for using Cloudstack! I assume you are adding the host on the
management webUI when you are encountering this error?
The most probable cause is your DNS records are pointing the name of the
management server, say "man1" -> 10.1.1.2.
I manually override this in my setups to use a d
Hi there,
I have multiple IP addresses assigned to the CS Management server on
different VLANs. When I go add the host to the Infrastructure it tries to
connect back the wrong IP address and is thusly blocked by our inter-vlan
access policy. What's recommended mechanism for specifying the server
