We were hoping to have MAAS act as the DHCP server for our BMC interfaces, however, we are not able get this to work.
Our workflow is as follows:
- We have a fabric, let’s call it fabric0
- We have a tagged VLAN 20 within this fabric, call it “bmc-vlan”
- We have a single subnet within this vlan, call it “bmc-subnet”
- We have configured our MAAS rackd with a second interface and assigned it an IP on the “bmc-subnet”. Within the Ubuntu OS, this interface appears untagged. But the interface itself is connected to VLAN 20 on our switch.
- We enable DHCP on the “bmc-vlan” within MAAS and assigned it to the rackd from step 4
- We create a machine, call it “test-machine”, and configure the “power” option to the IPMI interface. We define the IP address, which is within the range of bmc-subnet, a BMC MAC.
- When we look at the “bmc-subnet” in MAAS, we see that the IP address of the BMC of test-machine shows up under “used IP address” of the subnet with a type of “Sticky”.
When the BMC is connected to the network, it receives an IP from the MAAS “Reserved Dynamic Range” range of bmc-subnet and not the IP that was defined under the “power” options of test-machine.
When I look at
/var/snap/maas/common/maas/dhcpd.conf on the rackd server from step 4, I do see the bmc-subnet defined. I do not see, however, a “host” (DHCP reservation) defined for the MAC address of the BMC of test-machine. I do see “host” entries for the non-BMC interfaces of other hosts.
If I true to use the “devices” option in MAAS to create a “device” for the BMC of test-machine, I get an error that the IP already exists.
I am wondering, is MAAS intended to provide IP addresses for BMCs. when configured in the way I described? If not, how can we manage the dissemination of BMC IP addresses via MAAS?
As a side question, if the workflow above is expected to not result in MAAS assigning an IP to the BMC via a DHCP reservation, then why is the BMC MAC one of the optional fields of the IPMI power type?
Thanks in advance for any help!