maas not detecting nodes

Yinon yinonby.hpe at
Thu Feb 9 09:06:08 UTC 2017

And When I click on the subnet, I can see the range ( as a dynamic range. Is that a problem? 

    On Thursday, February 9, 2017 2:03 AM, Yinon <yinonby.hpe at> wrote:

 Indeed the dhcpd, dhcpd6 and ntp services don't have a green indication.How can find out what is the cause?When I try to disable the dhcp and "provide" it again, I no longer get the range option that I initially had. Any idea? 

    On Thursday, February 9, 2017 1:47 AM, Lloyd Parkes <lloyd at> wrote:

 Then MAAS isn’t doing DHCP for you.
Following on from Mike, check that you have a reserved _dynamic_ range defined for your subnet. Auto discovery IP addresses are issued from the dynamic range, and no dynamic range means no auto discovery. 
Also, in the GUI, got to the Nodes screen, select the Controllers view, select your rack controller and ensure that all of the services listed have green ticks on them. A missing green tick should give you a clue about where in the logs to look for problems.

On 9/02/2017, at 9:27 PM, Yinon <yinonby.hpe at> wrote:
I don't have any /var/lib/maas/dhcpd.conf .The only dhcp conf file I can find is:
root at dl-360-143:~# grep -v "^#\|^$" /etc/dhcp/dhcpd.confddns-update-style none;option domain-name "";option domain-name-servers,;default-lease-time 600;max-lease-time 7200;log-facility local7;
no conf files in /var/lib/dhcp:root at dl-360-143:~# find /var/lib/dhcp/var/lib/dhcp/var/lib/dhcp/dhcpd.leases~/var/lib/dhcp/dhcpd.leases/var/lib/dhcp/dhclient.leases

Any other files I can share?

    On Thursday, February 9, 2017 1:12 AM, Lloyd Parkes <lloyd at> wrote:

 Hi Yinon,What is in /var/lib/maas/dhcpd.conf? The directory /var/lib/dhcp doesn’t contain MAAS related stuff, instead it’s all under /var/lib/maas, even for DHCP.

On 9/02/2017, at 8:04 PM, Yinon <yinonby.hpe at> wrote:
Hey and thank you for your reply,
(1) I am specifying the IP address of the BMC (HPE iLO4). The BMC IP is not on a subnet directly connected, but it is routable (I can ping it). There is only 1 MAAS server (region controller and rack controller on the same server).
(2) I enabled DHCP on the correct interface with untagged vlan (see snapshot, and specified a range. As I mentioned, I can see the incoming dhcp requests on the interface, on untagged packets.
(3) Version: 2.1.3+bzr5573-0ubuntu1~16.04.1 .
(4) syslog at: . I saw mostly messages from the MAAS server dhclient, which seems to send dhcp discover on all ports periodically, which I don't believe should conflict with anything.
In /var/lib/maas:---------------------------------------------------------------------------------------root at dl-360-143:~# cat /var/lib/maas/dhcpd-interfaces; echoeno49root at dl-360-143:~# cat /var/lib/maas/dhcp/dhcpd.leases# The format of this file is documented in the dhcpd.leases(5) manual page.# This lease file was written by isc-dhcp-4.3.3
server-duid "\000\001\000\001 .\312\375<\250*\374\347p";----------------------------------------------------------------------------------------

I also don't see any listener on port 67, but since it's udp, I'm not sure I'm supposed to see it:---------------------------------------------------------------------------------------root at dl-360-143:~# netstat -tulpn | grep -w 67 | wc -l
How can I get the status of MAAS dhcp server?

    On Wednesday, February 8, 2017 10:59 PM, Mike Pontillo <mike.pontillo at> wrote:

 On Wed, Feb 8, 2017 at 3:04 PM, Yinon <yinonby.hpe at> wrote:

Regarding the pxe boot - I can see the incoming dhcp discover to port 67, and there is no response from the pxe server (MAAS server).So no IP, and no pxe boot is successful.
Regarding BMC - I can ping the iLO address from the MAAS server.

   Thanks for your feedback, and for giving MAAS a try. I looked through the logs; I have a few comments/questions that might be relevant.
(1) MAAS works best when you use IP addresses rather than hostnames to address BMCs, /and/ those IP addresses are on subnets directly connected to the MAAS server. This is recommended both to help to ensure that network or DNS failures cannot impact MAAS management of servers, and for HA; if you run multiple rack controllers, MAAS will need to select which one to communicate with the BMC on, and can do that more reliably if it is on a directly-attached IP subnet, specified by an IP address. If MAAS cannot make that determination, if should attempt to fall back to trying to determine if the BMC is routable from a rack controller. (It sounds like that fallback might be happening in your case; if that's true, we could have a bug.) - Are you specifying a hostname or IP address for your BMC? - Is the BMC connected directly to a subnet configured on the MAAS server, or is it only available via routing? (You can use "ip route get <bmc-ip-address>" to determine that.)
(2) In order for DHCP (and, thus, PXE booting) to operate, the appropriate VLAN must be enabled for DHCP management in MAAS, and a dynamic IP range must be set up for [a] subnet(s) on that VLAN. If MAAS is nether responding to DHCP nor TFTP requests for PXE booting, check that DHCP is enabled on the appropriate VLAN. (Usually to do this, you browse to it under the Subnets tab and click on the 'untagged' VLAN that is displayed next to the subnet(s) you wish to manage.) If the network model in MAAS does not match your physical topology, MAAS might not enable DHCP on the correct interface. So it would be good to double-check that.
(3) What specific version of MAAS you're using. (We should really print that out in the logs, to be honest.) From the logs, it looks like at least 2.1. (Is it 2.1.3 -- the latest in xenial-updates -- I hope?)
(4) You might want to take a look at /var/log/syslog (check for messages from dhcp) and in /var/lib/maas (check for DHCP configuration files to see if they are correct).
   Hope that helps.

Maas-devel mailing list
Maas-devel at
Modify settings or unsubscribe at:



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Maas-devel mailing list