VLAN clients not following DHCP reservations

VLAN clients not following DHCP reservations
VLAN clients not following DHCP reservations
2022-08-10 08:51:29 - last edited 2022-08-22 02:06:47
Tags: #DHCP
Model: OC200  
Hardware Version: V20
Firmware Version: 1.17.7 Build 20220623 Rel.35367

Hi all !

I'm encountering some strange issues regarding DHCP reservations on my Omada hardware controller. The setup is as following: 

ER605 as the main router, one OC-200, two TL-SG2428P, another 11 AT-8000s switches connected to the Omada switches, and about 32 EAPs, mainly 235's Wall and 225 Ceiling mount.

 

On the topology, I have about 16 VLANs, and about 12 SSIDs VLAN tagged and profiled on the switches.

Everything's running smoothly, it's just one thing that puzzles me for about 6-8 months now - and this is where it starts.

I have one VLAN, called IoT, mainly for Smart devices. Sonoffs. A bunch of them. Like 160 throughout the entire building floors, all connected to the same SSID, IoT, set up on an virtual Interface 10.0.4.0/24 - running a DHCP server.

They do get IPs and all, first when the VLAN was set up, all of them consecutive in regards to their powering on. Of course, I've renamed them all and assign reservations out of the pool for all of them on the correct interface. Reconnected them one by one to the SSID from the clients list on the Omada, and they all got the correct IPs, excepting like 6 of them that just wouldn't want assign to the correct IPs (the ones that were previously reserved).

Trying to solve it, I've restarted the main router hoping that this would solve it, like releasing the leases which were already assigned on a 20 minute interval.

Surprise. After the GW restart they all lost the IPs assigned, and got consecutive IPs from the pool, despite me trying to assign them to the correct ones. Of course, consecutive from the same pool (10.0.4.0/24) - but not the exact ones that I was trying to assign by making reservations.

Tried reconnecting them, turning them down and then up, et cetera. They just wouldn't want to follow the reservations that are in place.

 

The Log feature on the Omada is useless for this matter, it's just saying that the clients were reconnected to the SSID which I already knew because they came back online.

So I've dug a bit deeper, on exporting the running log from the controller. I was looking for some Linux log file that would point me in the right direction. But the only thing I've got was something like this for a particular client MAC. The list is more extensive with more clients failing to get the correct IPs from the reservations (while the others are working fine on the same VLAN, same SSID, same device vendor, but I'm only show you this particular MAC for testing purposes and preventing flooding you with unwanted log contents: 

 

08-10-2022 00:58:44.055 INFO [proxy-handler-thread-63] [] c.t.s.o.c.d.m.d.h(92): Need override old client history for client C8-2B-96-59-A1-6C with lastSeen 1660093099080

08-10-2022 00:59:11.879 WARN [monitor-topology-pool-0] [] c.t.s.o.c.d.a.o(130): Client:C8-2B-96-59-A1-6C is not OswClientImage, Cannot modify TrafficRequireMark. omadac:dc5437d74aa33b48dcf4996650adf9cc, site:Default

08-10-2022 01:00:11.976 WARN [monitor-topology-pool-1] [] c.t.s.o.c.d.a.o(130): Client:C8-2B-96-59-A1-6C is not OswClientImage, Cannot modify TrafficRequireMark. omadac:dc5437d74aa33b48dcf4996650adf9cc, site:Default

08-10-2022 03:16:26.002 INFO [client-inform-work-group-1] [] c.t.s.o.c.d.a.t(193): Known wireless client C8-2B-96-59-A1-6C is informed by switch: E4-C3-2A-1A-D1-E3, omadac: dc5437d74aa33b48dcf4996650adf9cc, site: Default, handle as wired client now.

08-10-2022 03:20:15.580 INFO [client-inform-work-group-1] [] c.t.s.o.c.d.m.d.h(92): Need override old client history for client C8-2B-96-59-A1-6C with lastSeen 1660101609723
08-10-2022 03:20:15.580 WARN [client-inform-work-group-1] [] c.t.s.o.c.d.m.d.h(105): New connection may override the pre pre history
08-10-2022 03:20:15.581 WARN [client-inform-work-group-1] [] c.t.s.o.c.d.m.d.h(116): Not the same connection and has changed before, create new clientHistory

08-10-2022 03:21:11.856 WARN [monitor-topology-pool-0] [] c.t.s.o.c.d.a.o(130): Client:C8-2B-96-59-A1-6C is not OswClientImage, Cannot modify TrafficRequireMark. omadac:dc5437d74aa33b48dcf4996650adf9cc, site:Default

08-10-2022 03:46:11.750 WARN [monitor-topology-pool-0] [] c.t.s.o.c.d.a.o(130): Client:C8-2B-96-59-A1-6C is not OswClientImage, Cannot modify TrafficRequireMark. omadac:dc5437d74aa33b48dcf4996650adf9cc, site:Default

08-10-2022 03:46:44.567 WARN [client-inform-work-group-1] [] c.t.s.o.c.d.m.d.h(116): Not the same connection and has changed before, create new clientHistory
08-10-2022 03:46:44.598 INFO [client-inform-work-group-1] [] c.t.s.o.c.d.m.d.h(92): Need override old client history for client C8-2B-96-59-A1-6C with lastSeen 1660103200614
08-10-2022 03:46:44.599 WARN [client-inform-work-group-1] [] c.t.s.o.c.d.m.d.h(105): New connection may override the pre pre history

08-10-2022 07:46:05.213 INFO [client-inform-work-group-1] [] c.t.s.o.c.d.m.d.h(92): Need override old client history for client C8-2B-96-59-A1-6C with lastSeen 1660117544160

 

This basically tells me nothing. Maybe only for their developers. I'm open to any ideas, changes, verifications and so on. I do have a solid networking background and some knowledge on the Omada as I'm using it for about two years now on different clients, so hit me as hard as you can.

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:VLAN clients not following DHCP reservations-Solution
2022-08-10 11:47:16 - last edited 2022-08-10 12:22:02

  @laurentiu907 

 

Upgrade your ER605 to the beta sw 1.2.1 that fixes this.  See this thread

 

https://community.tp-link.com/en/business/forum/topic/542294 

Recommended Solution
  2  
  2  
#2
Options
3 Reply
Re:VLAN clients not following DHCP reservations-Solution
2022-08-10 11:47:16 - last edited 2022-08-10 12:22:02

  @laurentiu907 

 

Upgrade your ER605 to the beta sw 1.2.1 that fixes this.  See this thread

 

https://community.tp-link.com/en/business/forum/topic/542294 

Recommended Solution
  2  
  2  
#2
Options
Re:VLAN clients not following DHCP reservations
2022-08-10 12:24:28

  @d0ugmac1 - looks to be an exact match. Thank you so much. Yet I'll wait for an official update as this is a production network and I can't take it offline more than 5-10 minutes. I believe that after the firmware update it might need to be readopted and reconfigured. Am I mistaken?

  0  
  0  
#3
Options
Re:VLAN clients not following DHCP reservations
2022-08-10 12:34:23

  @laurentiu907 

 

Router goes offline for about 3min after upgrade and reboot, so WAN bounces and VPN drop.  I have been running it on two production systems since it was released.  No issues to date.

  2  
  2  
#4
Options

Information

Helpful: 0

Views: 70

Replies: 3

Tags

DHCP
Related Articles