Hi  @ProSumerTester 

Thanks for the suggestion.

Did you try forget? did it help?

  @KocherJJ 

@ProSumerTester 

KocherJJ wrote

  @ProSumerTester 

I second this request. Being able to manually set the uplink port on any given switch should fix topology issues like these.

Request for omada developers: add a way to change uplink device manually (override dashboard topology)

 

 

You may start a thread to request this feature under Requests & Suggestions block to gather more voters. Thanks.

Hi  @daniel_hainich 

To understand the situation better, please start a new thread and share the following info:

1. A screenshot of the topology page;

2. What was the firmware version of the controller before this update?

3. A screenshot showing the model number and firmware version of the devices you are managing;

4. Do you have any non-tplink devices installed? if yes, please also list them.

daniel_hainich wrote

Hi,

 

after upgrading software controller from release 5 to 6, topology is totally wrong.

rebooting controller, switch and ap´s didnt help.

when i reboot an device, topology is changing and the uplinks of the switches are correct, but after the rebooted device is back nad full provisioned, the topology changes back.

my switches are connected with copper, but topology said the uplink port is one of the ap´s that is connected to the switch.

  @KocherJJ 

For your case, please include a detailed topology/map of the network.

Once sent, a ticket will be created in our support system, and a member of the team will follow up to gather more information or troubleshoot a cause.

KocherJJ wrote

I am having a similar issue. My network is a bit more complex, consisting of 4 network switches and 5 access points, all being handled by my Omada software controller.

 

Switch 1 is the 'primary' switch that has my router attached. The Router is NOT a TP-Link model. All three other switches are connected directly to trunk ports on switch 1, with switch 4 being both the smallest switch and the one physically furthest from the demarc, and in fact it is in a separate building.

 

The topology that Omada produces is absurdly inaccurate, showing switch 4 as the point switch, with switch 1 downstream and then switches 2 and 3 downstream from there.

  @ProSumerTester 

@daniel_hainich 

Thank you so much for taking the time to post the issue on the TP-Link community!
To better assist you, I've created a support ticket via your registered email address and escalated it to our support engineer to look into the issue. Please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, please update this topic thread with your solution to help others who may encounter the same problem as you did.
Many thanks for your excellent cooperation and patience!

  @GRL 

Thanks for joining the discussion. Is this issue still present? Any updates?

GRL wrote

There is definitely something wacky with the latest v6 topology map, here is one issue i have already logged with tech support.

 

ER8411 WAN/LAN 5 shows up as a client of its own gateway connected via LAN 9 (which is empty)  - no amount of provisioning, resetting, factory reset/readopt, LLDP settings etc makes it go away.  Its only present on one of my two ER8411 (both of which have WAN 5 enabled) and ony WAN5 is here, not WAN 4 or SFP WAN.... very odd indeed!

 

 

 

-ST