LLDP acting screwy on latest omada switch firmwares

LLDP acting screwy on latest omada switch firmwares

LLDP acting screwy on latest omada switch firmwares
LLDP acting screwy on latest omada switch firmwares
13 hours ago - last edited 13 hours ago
Model: TL-SG3452  
Hardware Version: V1
Firmware Version: 1.20.3

Switches

 

SG3452 v1.2 firmware 1.20.3. (released today, dated november)

SG3210 v3 firmware 3.20.3 (released today dated november)

SG2218P v2 firmware 2.0.0 (factory firmware, no new releases yet)

 

Issues:

 

SG3452 no longer identifies is 4 port LAG uplink to my aggregation switch (draytek G2280) as an uplink, so floats by itself on network topology map (red arrow)

SG2218P (green arrow) now thinks is directly connected to gateway, its actually got its own 4 port LAG from the Draytek aggregation switch

 

This used to be correctly identified

 

 

 

Issue 2:

A device connected to my SG3210 is identified in two places on the topology map which is nonsensical

Red arrow indicated the erronoeus entry (listing just the IP and no device name as configured in known devices, green arrow indicates its actual location properly in the switch client group

 

 

 

However, everything in the wired client list is correctly identified on the correct ports of each switch.

 

The Draytek G2280 switch I am using as my aggregation switch is broadcasting full LLDP packets on all ports.

 

My Topology from Gateway to SG3452 and SG2218P switches:

 

 

 

 

 

  0      
  0      
#1
Options