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 appreciated. Z On Sun, Feb 2, 2014 at 5:54 PM, Kirk Kosinski <kirkkosin...@gmail.com>wrote: > 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 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 IP > > address? > > > > cloudstack-setup-agent -m *10.1.1.2* -z 1 -p 1 -c 1 -g > > 03408e21-366b-3d94-8fe0-23aa00416bfd -a --pubNic=cloudbr1 > --prvNic=cloudbr1 > > --guestNic=cloudbr1 > > > > Here, the setup-agent script is passed 10.1.1.2 when it really should be > > passed 10.1.2.2. > > > > Any assistance on this matter would be appreciated. > > Thanks, > > Z > > >
