| 2017-03-31 13:08:01 |
Krzysztof Klimonda |
description |
MAAS Version 2.1.4+bzr5591-0ubuntu1 (16.04.1)
I've three ranges defined in MAAS for 198.18.6.0/24 network:
198.18.6.1-198.18.6.9 as "Reserved"
198.18.6.10-198.18.6.30 as "Dynamic"
198.18.6.230-198.18.6.254 as "Reserved"
MAAS is correctly using 10-30 range for DHCP clients, seem to be ignoring 1-9 range, but assigns IPs from 198.18.6.254 which is unfortunate as 252-254 are routers + gateway.
From maas.log:
-----8<-----
Mar 31 13:50:47 maas-regiond maas.api: [info] juju-0ee668-0-lxd-7: Added new device (parent: ample-orca)
Mar 31 13:50:47 maas-regiond maas.subnet: [warn] Next IP address to allocate from '198.18.6.0/24' has been observed previously: 198.18.6.254 was last claimed by 44:d9:e7:51:a4:d6 via ens160 (physical) on maas-rackd-vlan1206 at 2017-03-31 00:19:07.225315.
-----8<-----
44:d9:e7:51:a4:d6 is MAC address of the gateway, and is pingable from both maas-regiond and maas-rackd. the "last claimed" date seems bogus - as a gateway, it should be constantly on the network talking with other hosts.
After the last time, I've reenabled discovery in hopes that maas would discover the IP as taken, but that didn't seem to have helped. |
MAAS Version 2.1.4+bzr5591-0ubuntu1 (16.04.1)
I've three ranges defined in MAAS for 198.18.6.0/24 network:
198.18.6.1-198.18.6.9 as "Reserved"
198.18.6.10-198.18.6.30 as "Dynamic"
198.18.6.230-198.18.6.254 as "Reserved"
MAAS is correctly using 10-30 range for DHCP clients, seem to be ignoring 1-9 range, but assigns IPs from 198.18.6.230-254 which is unfortunate as 252-254 are routers + gateway.
From maas.log:
-----8<-----
Mar 31 13:50:47 maas-regiond maas.api: [info] juju-0ee668-0-lxd-7: Added new device (parent: ample-orca)
Mar 31 13:50:47 maas-regiond maas.subnet: [warn] Next IP address to allocate from '198.18.6.0/24' has been observed previously: 198.18.6.254 was last claimed by 44:d9:e7:51:a4:d6 via ens160 (physical) on maas-rackd-vlan1206 at 2017-03-31 00:19:07.225315.
-----8<-----
44:d9:e7:51:a4:d6 is MAC address of the gateway, and is pingable from both maas-regiond and maas-rackd. the "last claimed" date seems bogus - as a gateway, it should be constantly on the network talking with other hosts.
After the last time, I've reenabled discovery in hopes that maas would discover the IP as taken, but that didn't seem to have helped. |
|
