Bringing this back up, I’m on v3.4 at the moment and dealing with the same issue. I spent a period of time last night looking more into this, I think this is due to MAAS configuring items that are “in the same VLAN”, in what is called a shared-network. I said “in the same VLAN”, because when a network engineer says “untagged”, we usually think layer 3 interface (so no VLAN), or a native vlan. MAAS seems to assume VLAN1, which I feel like is erroneous.
Here are some docs on shared networks: https://support.microfocus.com/kb/doc.php?id=7004091
Shared networks are used for situations where you have vlan growth, so in Cisco CLI syntax:
int vlan 100
ip address 10.100.0.0 255.255.255.0
ip address 10.101.0.0 255.255.255.0 secondary
!! MAAS IP HELPER
ip helper-address 192.168.10.10
However when the MAAS rack controller, or whichever MAAS instance is serving DHCP is in a different VLAN, and you don’t have the ability to put the VLAN into the VM/etc, I would just traditionally just define my subnets and point a DHCP relay to them, not putting them in a shared network.
I read one post somewhere that brought me into suspecting the shared-network is the root cause of my issues being that they were able to remove the shared network line, and the closing bracket, and MAAS work as expected, I wasn’t able to figure out how to do that without MAAS overwriting my configuration, though.
I keep seeing posts and bug reports saying this issue has been fixed, but some lingering issues had been ongoing, is there just documentation I’m missing somewhere, I suppose?
Here are my subnets within MAAS. The goal is to have 1-2 rack controllers controlling 256 nodes, across about 16 subnets or so.
My network switch configuration (Juniper):
root@office-sw01> show configuration forwarding-options dhcp-relay
forward-snooped-clients all-interfaces;
overrides {
allow-snooped-clients;
no-bind-on-request;
delete-binding-on-renegotiation;
}
server-group {
dhcp {
192.168.88.10;
}
MAAS {
192.168.71.10;
}
}
active-server-group dhcp;
group MAAS {
active-server-group MAAS;
overrides;
interface vlan.200;
interface vlan.201;
interface vlan.202;
interface vlan.203;
interface vlan.204;
}
{master:0}
root@office-sw01>
root@office-sw01> show configuration interfaces vlan
(filtered)
unit 200 {
family inet {
address 192.168.200.254/24;
}
}
unit 201 {
family inet {
address 192.168.201.254/24;
}
}
unit 202 {
family inet {
address 192.168.202.254/24;
}
}
unit 203 {
family inet {
address 192.168.203.254/24;
}
}
unit 204 {
family inet {
address 192.168.204.254/24;
}
}
{master:0}
root@office-sw01>
If I were in a Cisco environment, I would do:
int vlan 200
ip address 192.168.200.1 255.255.255.0
ip helper-address 192.168.71.10
!
int vlan 201
ip address 192.168.201.1 255.255.255.0
ip helper-address 192.168.71.10
!
int vlan 202
ip address 192.168.202.1 255.255.255.0
ip helper-address 192.168.71.10
Again, let me know your thoughts on the matter…
