Client info not updated after reassigning switch port to a different VLAN
The switch model is SG2008.
I've had a client connected to a port assigned to a VLAN. I've changed configuration of the port and assigned it to the default VLAN (VID 1). After that the client got a correct IP address from configured subnet, everything works properly. But in Omada Controller I can still see the client assigned to previous VLAN and it does not show IP address at all. Restarting switch nor the client did not help.
What else should I do to get a proper information about the client in Omada Controler?
Thanks!
P.S.
Rourter: ER7212PC v1.0
Switch is connected to router's LAN port 4 with PoE.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @aDamDr
Thanks for posting in our business forum.
The DHCP will remember its lease time. Set the DHCP renewal time to a smaller one. And keep the device disconnected from the network until the DHCP lease is over.
Connect it back to the network and make sure it is in the correct VLAN. It will display as the correct form.
Rebooting the whole system may be helpful. You can also try it. I don't recommend this as you will experience the down time.
- Copy Link
- Report Inappropriate Content
DHCP is properly providing an IP address from the new VLAN. It is just that it is not displayed properly in the Omada Controller view. And it's been now a week since this change and the update is not getting reflected in the controller views. Also I have some devices that show up as connected to a gatway where in fact they are connected to the switch or EAP ethernet port. Even if I have set them up like that from the first connection. This is not critical obviously but a bit annoying so the question is if it is a known limitation / bug?
In some spare time I'll try to disconnect the impacted devices for longer than the DHCP lease time (which I have set to default value of 120 minutes).
- Copy Link
- Report Inappropriate Content
Hi @aDamDr
Thanks for posting in our business forum.
aDamDr wrote
DHCP is properly providing an IP address from the new VLAN. It is just that it is not displayed properly in the Omada Controller view. And it's been now a week since this change and the update is not getting reflected in the controller views. Also I have some devices that show up as connected to a gatway where in fact they are connected to the switch or EAP ethernet port. Even if I have set them up like that from the first connection. This is not critical obviously but a bit annoying so the question is if it is a known limitation / bug?
In some spare time I'll try to disconnect the impacted devices for longer than the DHCP lease time (which I have set to default value of 120 minutes).
Did you reboot or try what I suggested?
It seems to be a cache on the system.
We have received some reports similar to this and have plans to optimize the sync between the router and controller in the firmware iterations.
- Copy Link
- Report Inappropriate Content
@Clive_A
I have rebooted the router. Now those clients with wrong VLAN are shown properly. Interesting thing has happened though: all of the clients previously correclty shown as connected to router are now shown as connected to an uplink port of the switch. It seems like the controller is up and running before the router is fully restarted and it is picking up the info from the switch. Similarly some of the wifi clients are also shown as connected to the uplink switch port whereas they are connected to an EAP connected to a router.
I'll still try to reboot all of the networking gear to see if it will get more accurate view. But it is a bit a pitty that this info is not getting updated properly, even hours after reboot of the router.
- Copy Link
- Report Inappropriate Content
@Clive_A I have now also restarted all the network devices: the router, SG2008 switch and 5 EAPs (2 653s and 3 615-WALLs).
And it is even worse than it was. No client is shown as connected to the router directly, despite the fact that some of them are. Also some of the wifi clients are shown as connected to port 8 of the switch, which is the uplink port. So I don't know now to which EAP they are connected.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 63
Replies: 5
Voters 0
No one has voted for it yet.