Hi Jay, i would suggest the following approach:
- set IPs manually for the all hosts you wont't to use OR use a different
dhcp server (not the Cloudstack Managementserver) and work with static
leases for the hosts
- only the system vm's (instances of systemvm's, console proxys and later
on virtural routers) using dhcp
- while creating the zone, you then double check that you didn't use the
whole managametn ip range in dhcp. You can specify parts of your management
network for ip leaese - not the whole network.
For example when using the wizzard and enter the informations for your
"Pod Network"
Name: Pod 1
Reserved System Gateway: Address of your Gateway
Reserved System Netmask: Subnetmask of the whole Pod-Network
Start / End IP Reserved System IP: IP Range used for leases to the
system vms's - not the whole pod / management network
Am Di., 28. Sept. 2021 um 08:16 Uhr schrieb jay hs <
jhahn-steic...@whatcom.edu>:
> Hi all:
> I must be doing something wrong.
> I am installing 4.15 from the apt repositories on ubuntu 16.04
> deb http://download.cloudstack.org/ubuntu xenial 4.15
>
> Everything goes grandly, except that when cloudstack-agent starts up, it
> puts a seemingly random IP address (from the correct subnet) in host= at
> agent.properties.
>
> It should be
> host=172.16.10.2
> but it picks up
> host=172.16.10.246@static
>
> Evidently, it passes this *.246 value on to the ssvm -- which makes it
> very mad.
>
> I've redone my management server and first kvm host a second time, and it
> got *.234 instead of *.246.
>
> I am doing these on a test network that is NATed off from the main
> network. That NAT network did have its own DHCP active. I've switched
> that off -- and will do another try (tomorrow).
>
> But does this sound like I've got a configuration missing -- or am I
> picking up a bum copy of the cloudstack-agent from the repo? or... ideas?
>
> thanks.
> --jay
>
