Must be something with my networking but I cannot get PXE boot to recognize any other machines.
I have external DHCP (Fortigate), with 2 interfaces on each of my 4 bare metals: 10.20.0.0/24 and 10.50.0.0/24.
I don’t want to use MAAS DHCP, but I just cant get it to work, PXE just wont kick in and find the MAAS deployment.
Hopefully this presentation Show and Tell: Using external DHCP with MAAS - #2 by r00ta will give you more context on what’s required to setup your external dhcp
Ok if I wanted to use MAAS Dhcp, I can get the machine to recognize PXE boot now, but I get this error and then the server shuts off (and I have to manually power it on via iDRAC)
Looks like you have some DNS issues. You have to make sure you don’t have 2 dhcp servers on your network (you can’t have MAAS DHCP + your external DHCP server).
You can also try to disable Allow DNS resolution on that subnet for troubleshooting
I do have two, that might be the problem.
I’m not sure how to set up a DHCP server with a different IP subnet in MAAS.
I have two nics, both of which get their IP from my external DHCP:
10.20.0.32 and 10.50.0.3
So if I want to set up a DHCP server in MAAS, the only options I have are those two subnets which have DHCP servers already.
How do I make a 10.60.0.0/24 subnet in MAAS?
BTW my 3 servers have made their way past that stage but I am now on the 5th reboot for each server (it keeps shutting down). I’m not sure whats going on here. They show up on MAAS as successfully comissioned and are in a “New State” but every time I turn them back on they go through the Ubuntu setup and then eventually shut down.
Ok I simplified it into a VM for the controller, and only one network:
10.20.0.42 - it gets this from my Fortigate DHCP server.
So now, how do I create a DHCP server in MAAS? I set one up on the same fabric (fabric-0) that the controller was using, and gave it 10.21.0.0/24, and PXE boot picked it up, gave it an IP (10.21.0.191) but then I got this:
If you keep 2 DHCP servers on the network this is not going to work. If you can’t get rid of your external DHCP server, I’d suggest you to configure it according to Having Trouble Deploying Maas Machine - #2 by r00ta and https://community.fortinet.com/t5/FortiGate/Technical-Tip-Configuring-FortiGate-for-PXE-Client-booting/ta-p/213404
I can configure it any way, but how do I go about giving the server an IP and then using that same subnet as the DHCP server?
Like why can’t I just add a new interface to my VM, and have it be the DHCP server? I can’t get that interface to have the checkmark on PXE.
could you elaborate wdym?
Ok:
I have a VM in HyperV, Ubuntu 24.04, with one network interface. It gets DHCP from my Fortigate and gets 10.20.0.42.
Now, I can do anything with the VM, interfaces, vlans, etc etc.
How do I create a DHCP server, on a different interface. I want to leave the 10.20.0.42 alone because its my “servers” DHCP subnet that is given out to all servers I set up.
But what if I want to just create a brand new subnet/interface in my VM to handle the DHCP server that MAAS provides.
If I set up a new interface with static IP 10.50.0.2, which is NOT a DHCP server in my Fortigate, I still can’t get PXE boot working because its only enable on interface 1 (10.20.0.42) and I can’t set up a DHCP server on that interface.
How did you setup the second interface? Do you have a virtual network? Is it accessible by the MAAS controller?
I set it up in Ubuntu netplan.
Could you run
ip a
on your MAAS controller?
Also, please share your netplan config and the screenshot of the subnets page on the MAAS UI
Idk I have seem to messed something up further and now my eth1 wont show up or be recognized, not sure how to proceed from here:
Does this controller have actually 2 physical interfaces?
New Update, I have 2 interfaces showing again:
My netplan:
My ip a:
My MAAS Subnets page:
But PXE Boot still not working.
This is my controller network page, why is my eth1 not checked off for PXE?
The PXE info on the controller page is not relevant, you can ignore it. Now if your network is properly setup and the machines are configured to pxe boot in the subnets managed by MAAS DHCP it should work
I switched my primary to a non-dhcp server, gave it a static IP and I can get PXE Booting recognized again but getting TFTP error from server
Why do you have 10.50.x now? In your MAAS only 10.20 and 10.25 are known subnets
