04-04-2024 02:29 AM - edited 04-04-2024 02:50 AM
Hi All
Got a strange problem. I setup a working IPN network between my DCs and have configured IP DHCP relay so that we can start discovering the remote POD spines.
The spines are being discovered, ie. Serial numbers and model details are shown as unregistered nodes.
When I try register them, that's when the fun starts. I have 3 pods, with 3 allocated pools. I have tried as per my LLD to setup the spines to POD 2 and POD 3 for the respective devices, and they are stuck in Discovery status.
Checking the APIC I see the Serial of one Spine and the message of
8371||2024-04-04T11:04:42.221675243+02:00||dhcp||DBG4||||ISC dhcpd: updateUid 19:SERIAL-eth1/36, ../common/external/dhcp/dhcp-4.1-ESV-R6/server/svcapi.c:410||../svc/dhcpd/src/gen/ifc/beh/imp/./DhcpdSvc.cc||75 bico 40.092
8371||2024-04-04T11:04:42.221717833+02:00||dhcp||INFO||||ISC dhcpd: svc_write_client: client uid = SERIAL-eth1/36 ||../svc/dhcpd/src/gen/ifc/beh/imp/./DhcpdSvc.cc||70
8371||2024-04-04T11:04:42.221729936+02:00||dhcp||INFO||||ISC dhcpd: svc_write_client: serial number = SERIAL ||../svc/dhcpd/src/gen/ifc/beh/imp/./DhcpdSvc.cc||70
8371||2024-04-04T11:04:42.221738682+02:00||dhcp||INFO||||ISC dhcpd: svc_write_client: interface name = eth1/36.8 ||../svc/dhcpd/src/gen/ifc/beh/imp/./DhcpdSvc.cc||70
8371||2024-04-04T11:04:42.221746306+02:00||dhcp||INFO||||ISC dhcpd: svc_write_client: client model = N9K-C93600CD-GX ||../svc/dhcpd/src/gen/ifc/beh/imp/./DhcpdSvc.cc||70
8371||2024-04-04T11:04:42.221853107+02:00||dhcp||DBG4||dn='"D"'||8371||2024-04-04T11:04:42.221928167+02:00||dhcp||ERROR||||ISC dhcpd: DHCPDISCOVER from e8:0a:b9:6a:0b:df via 172.18.28.66: network ifabric: no free leases||../svc/dhcpd/src/gen/ifc/beh/imp/./DhcpdSvc.cc||80
My IPN devices are N9K switches.
My POD Pools are not overlapping.
apic-01# moquery -c dhcpPool | grep startIp | sort | uniq -c
1 startIp : 100.64.0.64
1 startIp : 100.64.24.64
1 startIp : 100.64.56.64
# dhcp.Provider
id : 1
adminSt : enabled
childAction :
configIssues :
dn : prov-1
ip : 100.64.0.1
lcOwn : local
modTs : 2024-03-26T15:22:05.341+02:00
name :
operErr :
operSt : enabled
rn : prov-1
status :
Thanks
11-28-2024 11:48 PM
Hello @pkk666 It looks like you're encountering an issue with DHCP leases when trying to register your spines in different PODs. The error message "no free leases" indicates that the DHCP server is unable to allocate an IP address to the requesting device because there are no available IP addresses in the specified pool.
Let me know if you want steps to troubleshoot and resolve this issue.
HTH
AshSe
If this post was helpful, please rate it. Thank you!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide