Intermittent adoption loops
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I'm at the point where I'm almost giving up on Omada, and throwing all my gear in the dump.
I have a 3210xhp-m2, two EAP670's, an OC200.
ALL connected directly to each other, on the same VLAN, w/ the OC and EAPs powered by the 3210.
I'm getting these adoption loops where the 3210 and one of the EAPs get stuck. EAP comes offline, but switching continues to work.
The only way I've found out of it is power cycling the 3210, which gives me a ten minute downtime, and which (reliably) can't be done remote -- I've got a couple of wifi power switches, but of course, if the APs come offline I can't cycle the relevant power switch. Should also mention that power cycling an EAP through the 3210 doesn't work (PoE reclaim?)
This is a small setup, and even then I'm getting issues. I can't even imagine what it looks like on a large-scale system.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@ASGADFGWT until someone else answers, confirm latest firmware on all devices. I'm sure you have probably already done this.
When you say one EAP gets stuck in a loop, is it always the same EAP? If so, try moving cable one to cable two port and vise versa. See if the issue follows the EAP and cable, or stays with the port. If it follows the EAP and cable, then swap the EAPs out on each end and see if the issue stays with the cable.
Just some ideas. I know how frustrating it can be, particularly when the deployment is small.
- Copy Link
- Report Inappropriate Content
Hi @ASGADFGWT
Thanks for posting in our business forum.
First, the switch can be remotely rebooted if you can SSH into it. In controller mode, you can still use SSH with CLI. Refer to the CLI guide.
On the controller, you can modify the port of the switch and its PoE. Moreover, you got Reboot Schedule which can be sent to the EAP by Controller.
Second, your intermittent adoption issue, how long is the Ethernet cable? Can you verify it by a 3ft cable and test it for a day? With this, do you still experience the disconnection/readoption?
Firmware to the EAP, is that the latest? Or it's beta? Specify that.
Does the WIFI still provide Internet? Or it's completely cutting you from the Internet?
Have you checked the log? Is there a G1/0/X was blocked log?
- Copy Link
- Report Inappropriate Content
It's almost always the same EAP, but the second one has had it happen too.
All hw are on the latest updates. I think it actually only really started after the 2.0.6 update on the 3210, so maybe that's something.
Will try switching up the ports/cables!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @ASGADFGWT
Any update on this?
- Copy Link
- Report Inappropriate Content
I have changed out the cables to make sure they aren't the problem, using keystone jacks plus patch cables. I don't think they are the problem anymore, if they ever were.
It's all very intermittent, so not easy to trouble shoot.
When adopting, the switch doesn't reply to pings. And ssh doesn't work even when the switch is in a connected state, so that's a dead end.
Switching itself works, EAPs in adopting state don't.
Physically power cycling the switch is still the only working solution.
- Copy Link
- Report Inappropriate Content
Hi @ASGADFGWT
Thanks for posting in our business forum.
ASGADFGWT wrote
I have changed out the cables to make sure they aren't the problem, using keystone jacks plus patch cables. I don't think they are the problem anymore, if they ever were.
It's all very intermittent, so not easy to trouble shoot.
When adopting, the switch doesn't reply to pings. And ssh doesn't work even when the switch is in a connected state, so that's a dead end.
Switching itself works, EAPs in adopting state don't.
Physically power cycling the switch is still the only working solution.
I need a diagram of your network and I can escalate your case if I cannot find out the cause.
This is something I rarely see. And I am quite certain there is something special in your network.
The switch is not ping-able during the adoption, quite normal. Resetting and rebooting and back online and ready to be successfully adopted.
Do you have any other VLAN? Is the default network on 192.168.0.1/24?
Do you have another router/DHCP server?
Do you have EAP mesh previous to the reset? Does it still happen now?
How many devices are connected to the switch? To the router? Have you removed everything off the router and switch and adopt them in default VLAN1? Is it stable?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 560
Replies: 7
Voters 0
No one has voted for it yet.