Hello!
I installed a new MAAS server and I think I made all the settings the same as the old one. However, I think there is a point I forgot in the “External DHCP” section, I can’t find where I set the external dhcp setting. I am sharing the screenshots of the old server (configured external dhcp) and the new server (no dhcp) below.
Thanks.
POC Server with external DHCP config.
New one that i would like to configure “external dhcp”.
There has been no change for about two days. Is there a setting I need to do on the DHCP server side?
in fact, MAAS automatically finds the machines on the subnet…I’m just digging if the other issue may be related to this external dhcp setting.
do you have network discovery enabled?
Yes I have. It has the same settings as the old one.
Network Discovery > Enabled (Every 10 min)
Old server : 780 discoveries
New one : 178 discoveries
every rack should check every 10 minutes for external dhcp servers and report the info back to the regions. If you definitely have an external dhcp server on a subnet of a rack it should work. If not, I’d check the rackd logs
How can I see the rackd logs ?
Thanks. I did not see an error, the last line has the following message : " External DHCP probe complete."
2024-03-06 14:04:07 Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type='TCP', host='::ffff:192.168.36.26', port=55928, flowInfo=0, scopeID=0) PEER:IPv6Address(type='TCP', host='::ffff:192.168.36.26', port=5253, flowInfo=0, scopeID=0))
2024-03-06 14:04:07 Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type='TCP', host='::ffff:192.168.36.26', port=55932, flowInfo=0, scopeID=0) PEER:IPv6Address(type='TCP', host='::ffff:192.168.36.26', port=5253, flowInfo=0, scopeID=0))
2024-03-06 14:04:07 Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type='TCP', host='::ffff:192.168.36.26', port=55942, flowInfo=0, scopeID=0) PEER:IPv6Address(type='TCP', host='::ffff:192.168.36.26', port=5253, flowInfo=0, scopeID=0))
2024-03-06 14:04:07 provisioningserver.rpc.clusterservice: [info] Event-loop 'srvmaas:pid=1242' authenticated.
2024-03-06 14:04:07 provisioningserver.rpc.clusterservice: [info] Event-loop 'srvmaas:pid=1242' authenticated.
2024-03-06 14:04:07 provisioningserver.rpc.clusterservice: [info] Event-loop 'srvmaas:pid=1242' authenticated.
2024-03-06 14:04:07 provisioningserver.rpc.clusterservice: [info] Rack controller 'r6c37t' registered (via srvmaas:pid=1242) with MAAS version 3.4.0-14321-g.1027c7664.
2024-03-06 14:04:07 provisioningserver.rpc.clusterservice: [info] Rack controller 'r6c37t' registered (via srvmaas:pid=1242) with MAAS version 3.4.0-14321-g.1027c7664.
2024-03-06 14:04:07 provisioningserver.rpc.clusterservice: [info] Rack controller 'r6c37t' registered (via srvmaas:pid=1242) with MAAS version 3.4.0-14321-g.1027c7664.
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:custom:amd64:generic:ubuntu2204-DESKTOP: to_add=['20240305'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:grub-efi-signed:amd64:generic:uefi: to_add=['20231004.0'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:grub-efi:arm64:generic:uefi: to_add=['20231004.0'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:grub-ieee1275:ppc64el:generic:open-firmware: to_add=['20210509.0'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:pxelinux:i386:generic:pxe: to_add=['20210203.0'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:rhel:amd64:generic:8-custom: to_add=['20240305'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:ga-18.04-lowlatency:bionic: to_add=['20230607'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:ga-18.04:bionic: to_add=['20230607'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:ga-22.04-lowlatency:jammy: to_add=['20240301'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:ga-22.04:jammy: to_add=['20240301'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04-edge:bionic: to_add=['20230607'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04-lowlatency-edge:bionic: to_add=['20230607'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04-lowlatency:bionic: to_add=['20230607'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04:bionic: to_add=['20230607'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-22.04-edge:jammy: to_add=['20240301'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-22.04-lowlatency-edge:jammy: to_add=['20240301'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-22.04-lowlatency:jammy: to_add=['20240301'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-22.04:jammy: to_add=['20240301'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:armhf:ga-22.04:jammy: to_add=['20240301'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:armhf:generic-lpae:jammy: to_add=['20240301'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:armhf:hwe-22.04-edge:jammy: to_add=['20240301'] to_remove=[]
2024-03-06 14:07:07 sstreams: [info] maas:v2:download/maas:boot:ubuntu:armhf:hwe-22.04:jammy: to_add=['20240301'] to_remove=[]
2024-03-06 14:12:07 provisioningserver.rackdservices.dhcp_probe_service: [info] Probe for external DHCP servers started on interfaces: ens160.
2024-03-06 14:12:17 provisioningserver.rackdservices.dhcp_probe_service: [info] External DHCP probe complete.
are you 100% the external dhcp server is properly working on the subnet where the rack interface
ens160 is listening to? Do you see the host of the external dhcp server in the network discovery?
I solved it.
I configured the server’s network settings to static and the problem was solved. I think this is an “openVswitch” problem, I have not encountered such a problem on a physical machine.
Thanks.
I’m leaving the working configs below
BEFORE:
AFTER
network:
ethernets:
ens16:
addresses:
- 192.168.30.20/23
nameservers:
addresses:
- 192.168.30.1
- 192.168.30.2
search: […]
routes:
- to: default
via: 192.168.30.10
version: 2
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.