Bug: The Map topology function is always incorrect

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

Bug: The Map topology function is always incorrect

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Bug: The Map topology function is always incorrect
Bug: The Map topology function is always incorrect
2020-10-16 03:49:12 - last edited 2020-10-16 05:30:18
Model: OC200  
Hardware Version: V1
Firmware Version: 1.7.0 Build 20200703 Rel.59609

In the Map Topology view, it shows each Omada Switch and Access Point but the devices on them is always wrong.

 

I noticed this when I added three T1500G-8T switches. Each switch randomly shows the wrong MAC addresses and devices.

 

Instead each switch shows a random and changing set of clients that are not even physically plugged in to it.

 

For example in this screenshot where the CenterSwitch shows 6 clients (number 6) but only 3 devices, and none of those devices are actually connected to that switch. That Desktop device is connected elsewhere. In other cases I do have a device connected to switch A and it shows up connected to switch B, and so on.

 

This list changes every time you reload the page.

 

Is this a known bug?

 

 

15 minutes later the BRSwitch now shows 10 devices on it and the DESKTOP has moved from CenterSwitch to BRSwitch.

 

 

And then changed again to just 3 clients only a few minutes later:

 

  0      
  0      
#1
Options
2 Reply
Re:Bug: The Map topology function is always incorrect
2020-10-19 09:04:56

Dear @Will_M,

 

Thank you for posting the problem on the community.

 

In the Map Topology view, it shows each Omada Switch and Access Point but the devices on them is always wrong.

 

I noticed this when I added three T1500G-8T switches. Each switch randomly shows the wrong MAC addresses and devices.

Instead each switch shows a random and changing set of clients that are not even physically plugged in to it.

 

For example in this screenshot where the CenterSwitch shows 6 clients (number 6) but only 3 devices, and none of those devices are actually connected to that switch. That Desktop device is connected elsewhere. In other cases I do have a device connected to switch A and it shows up connected to switch B, and so on.

 

We didn't receive such feedback before, I'll forward it to the senior engineers for further test.

 

May I ask for the actual network topology of your network? What's the model and firmware version of your Omada EAPs?

Best Regards!
  0  
  0  
#2
Options
Re:Bug: The Map topology function is always incorrect
2020-10-20 03:36:41

@Fae Thank you for the reply!

 

Here is some more information for the network configuration.

 

Equipment In Central Rack:
Firewall: Ubiquiti Edge RouterX
DHCP/DNS: NanoPi NEO
Wireless Access Points: EAP225-Wall, EAP235-Wall, EAP245
Eth. Switch 1: Aruba S2500 24-port + 4 SFP+
Eth. Switch 2: Netgear MS510TX Multi-Gig
Controller: TP-Link OC200

3 Remote Locations elsewhere in house:
3 Eth. Switches: TP-Link T1500G-8T powered by POE port 8
Each switch has Multiple devices connected (2-4 devices per switch plus uplink/POE port)

 

Topology

The Aruba S2500 POE switch is the center of the network.

Aruba -> 10G SFP+ -> Netgear MS510TX -> Multi-Gig Ethernet Ports -> clients
Aruba -> 1G Eth -> DNS/DHCP
Aruba -> 1G Eth -> Firewall -> 1G Eth -> Modem -> ISP
Aruba -> 1G Eth(POE) -> OC200
Aruba -> 1G Eth(POE) -> T1500G-8T #1 -> 1G Eth -> clients
Aruba -> 1G Eth(POE) -> T1500G-8T #2 -> 1G Eth -> clients
Aruba -> 1G Eth(POE) -> T1500G-8T #3 -> 1G Eth -> clients
Aruba -> 1G Eth(POE) -> EAP225
Aruba -> 1G Eth(POE) -> EAP235
Aruba -> 1G Eth(POE) -> EAP245

 

Hardware and Firmware Versions

Controller: Model: OC200 1.0  Firmware Version: 1.7.0 Build 20200703 Rel.59609
Switch 1: Model: T1500G-8T v2.0,  Firmware Version: 2.0.6 Build 20200805 Rel.56922
Switch 2: Model: T1500G-8T v2.0,  Firmware Version: 2.0.6 Build 20200805 Rel.56922
Switch 2: Model: T1500G-8T v2.0,  Firmware Version: 2.0.6 Build 20200805 Rel.56922
EAP 1: Model: EAP225-Wall(US) v2.0  Firmware Version: 1.20.0 Build 20200422 Rel. 70504
EAP 2: Model: EAP235-Wall(US) v1.0  Firmware Version: 1.0.1 Build 20200618 Rel. 39307
EAP 3: Model: EAP245(US) v3.0  Firmware Version: 2.21.0 Build 20200522 Rel. 49688

 

  0  
  0  
#3
Options