Incorrect / Missing Topology after moving OC200 to alternate subnet.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Incorrect / Missing Topology after moving OC200 to alternate subnet.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Incorrect / Missing Topology after moving OC200 to alternate subnet.
Incorrect / Missing Topology after moving OC200 to alternate subnet.
2021-10-17 13:56:16 - last edited 2021-10-17 14:00:13
Model: OC200  
Hardware Version: V1
Firmware Version: 1.9.1 Build 20210721 Rel.39263

Controller Version: 4.4.4

Model: OC200 1.0

Firmware Version: 1.9.1 Build 20210721 Rel.39263

 

Since moving the controller to a separate subnet (using DNS option 138 for discovery), the network topology map for my network is screwed up, links are missing, and the overall topology layout is wrong.

 

1) SW1 Garage is the top level switch, not SW2 Master Bedroom, which should be on the right hand side of this topology.

2) AP 3 Patio is connected to SW2 Master Bedroom, a link which is just completely missing.

3) In the client lists there are 4 devices missing which are connected using TP-Link AV1000 PowerLine adapters

 

Previously, when the OC200 was on the same subnet as the Switches and AP's the topology map was correct, and all PowerLine connected clients were present.

 

I can't understand why this has changed just by moving the controller...., any ideas on why the topology has changed and/or the PowerLine connected clients are missing ?

 

  0      
  0      
#1
Options
1 Reply
Re:Incorrect / Missing Topology after moving OC200 to alternate subnet.
2021-10-19 08:59:26 - last edited 2021-10-19 09:37:17

The problem here is the controller has mis-labeled the uplink and downlink between SW3 and SW1, i.e. they are reversed., . Any way to manually change this ?, and then also mark the correct port on SW3 as the downlink port for AP4

  0  
  0  
#2
Options