Omada Software Controller Network topology not showing correctly
Hi All,
I'm running Omada Software Controller as a docker image[1] on a linux host. Recently I have noticed that network topology view is not showing any of my EAP615-wall or EAP655-wall devices and clients connected to them. However I can see my Omada compatiable devices under Devices section as well as all clients under clients section without any issue.
When inspecting controller logs, I have noticed Stack Overflow Exception in topology calculator occationaly. But there are successful calulation logs printed after those exceptions too.
Is there any known bug related to this controller version or this is something specific to my environment?
[1] mbentley/docker-omada-controller: Docker image to run TP-Link Omada Controller (github.com)
Thanks & Regards,
Charitha
Thanks for checking this out.
According to the Omada console, there is no any firmware upgrades available for both EAPs. Here is a screenshot of the firmware versions I have.
By the way, I was able to see the topology correctly up until a week ago without any issue under same software and firmware versions. I have tried restarting all the devices including the controller, but still I'm seeing above incorrect topology.
I have connected both EAPs via a TL-SG1008P, 8 Port Gigabit PoE Unmanaged Switch as follows.
ER605 ---> TL-SG1008P ---> EAP655 ---> ~10 wireless clients
|---> Controller
|---> Wired client (non PoE)
|--->EAP615 ---> 1 wired client (non PoE)
|---> ~ 5 wireless clients
Thanks,
Charitha
