Home

Forums

Stories

Knowledge Base

Business Community > Switches > LLDP acting screwy on latest omada switch firmwares

< Switches

LLDP acting screwy on latest omada switch firmwares

GRL

Yesterday - last edited Yesterday

Posts: 167

Helpful: 88

Solutions: 11

Stories: 0

Registered: 2022-01-02

LLDP acting screwy on latest omada switch firmwares

Yesterday - last edited Yesterday

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:

2 Reply

Clive_A

13 hours ago

Posts: 5628

Helpful: 2696

Solutions: 1268

Stories: 0

Registered: 2023-06-09

Re:LLDP acting screwy on latest omada switch firmwares

13 hours ago

Hi @GRL

Thanks for posting in our business forum.
Reboot the whole system after the update to let them discover again and see if the topology can show correctly.

If it does not work, start the Wireshark and be ready, and boot up the switch, and see how it works. I might need a Wireshark result for the test and dev team.

What's the controller verison?

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.

GRL

LV3

13 hours ago - last edited 13 hours ago

Posts: 167

Helpful: 88

Solutions: 11

Stories: 0

Registered: 2022-01-02

Re:LLDP acting screwy on latest omada switch firmwares

13 hours ago - last edited 13 hours ago

@Clive_A

I waited for the network to be unused tonight and rebooted the whole system, no changes. Topology remains the same.

I tested disabling LLDP on the Draytek switch - Which resolved the SG3452 not recognising its LAG uplink as an actual uplink, but instead the topology map then showed it as linked to the SG2218P instead, which is arguably even more wrong.

I can wireshark over the weekend, what do you want me to test? Im not sure if its even possible to mirror a LAG to a single port ?

Controller firmware is the 5.14.32 prerelease from a couple weeks ago - the re-released version that fixed the WAN settings issues, running on OC200 v1

To be a bit more clear, the Draytek Switch is filtering the VLANs from 4 ports on the ER8411 as we cannot have tagged-only port profiles on omada - which the draytek can do

WAN/LAN7 carries VLAN 0 (management), 6 (tagged), 10 (tagged

WAN/LAN8 carries VLAN 7 (tagged)

WAN.LAN9 carries VLAN 11 (tagged)

WAN/LAN10 carries VLAN 100,1000,1010,1011 and 1020 (tagged)

The dreytek then aggregated all these vlans into a 4gbit wide path to each of my main TP link core switches (one for EAPs, one for all LAN type stuff) for efficient bandwidth.

This all works flawlessly, and network performance is excellent - just the LLDP reporting is now wrong with the new switch firmwares.

I have no idea whats going on with the SG3210 reporting the same device twice, inside and outside the switch client group. Multiple reboots of the switch, and the device in question have not resolved this. The Sg3210 has a single uplink port to my SG3452 so the draytek switch isnt in that path at all.

LLDP acting screwy on latest omada switch firmwares

LLDP acting screwy on latest omada switch firmwares

Information

Voters 0

Tags