TL-SG3428XMP v2.0 on Omada controller shows each port twice
Hi guys,
all of a sudden, when I try accessing the SG3428XMP switch from within the Omada Web-Interface, the device is showing me the following picture:
Each of the ports is being listed twice, which doesn't allow for any modification since clicking on one port will address a different one (in a strange, random pattern).
The Ports list also shows them twice, although, the second "instance" has the default label "Port n" instead of my custom assigned label:
As far as I can tell, the device is still working and the network traffic doesn't seem to be messed up. Only thing not working is the traffic analysis / charts.
Strangely enough: We have a second SG3428XMP located in the same network, which also is a V2.0 with the same firmware and doesn't show this behaviour at all.
Could this be some configuration issue or is this a sign the device is slowly but surely dying?
Any advice on how to solve this?
Regards
Thanks for posting in our business forum.
Technik-Gegg wrote
Clive, thank you for the fast reply.
I suppose you mean the browser cache. Did that to no avail.
I even used a different browser, which never has connected to the Omada controller, just to be on the safe side.
What's even more strange, another switch (SG3210XHP-M2 v2.0) now shows the same behavior, even though it didn't do that yesterday.
And guess what: We also have two of those and the other one is not showing that kind of glitch.
I already suspected some sort of caching/display issues and downloaded and inspected the configuration JSON files for both switches.
The data looks fine at first glance. i.e. ports are all available and enumerated correctly.No wait... not sure where I was looking at: I inspected the JSON files once again, turned out, the ports appear duplicated in the JSON file as well... guess I was already a bit exhausted yesterday
Edit: Here are the screenshots from the Device-Info JSON files:
Switch 1: OK
Switch 2: Ports doubled
A bit more information on that topic, just to rule out any strange "side effects":
The very same network configuration has been up and running for the past 2 years, with no significant changes. Last week I had to set up a WAN fallback, and hence switched WAN/LAN1 to WAN. Not sure if this could have caused this.
Regards
TG
I am now consulting with the dev and see if we need additional information from you.
In the internal log, I found that this is known and estimated to be optimized in the future SDNC update.
Temporarily, you can forget the switch and readopt to fix the issues. Do not reset your Omada controller.
As for now, you may back up your config, device info, and running log for further diagnosis in case I am instructed to collect them.
Appreciate your cooperation.
Update:
This will be further optimized in the SDNC update. ETA in V5.15.X. Please kindly wait for the update.
Temporarily, if you experience the issue, please refer to this line: Temporarily, you can forget the switch and readopt to fix the issues. Do not reset your Omada controller.
Clive, thank you for the fast reply.
I suppose you mean the browser cache. Did that to no avail.
I even used a different browser, which never has connected to the Omada controller, just to be on the safe side.
What's even more strange, another switch (SG3210XHP-M2 v2.0) now shows the same behavior, even though it didn't do that yesterday.
And guess what: We also have two of those and the other one is not showing that kind of glitch.
I already suspected some sort of caching/display issues and downloaded and inspected the configuration JSON files for both switches. The data looks fine at first glance. i.e. ports are all available and enumerated correctly.
No wait... not sure where I was looking at: I inspected the JSON files once again, turned out, the ports appear duplicated in the JSON file as well... guess I was already a bit exhausted yesterday 
Edit: Here are the screenshots from the Device-Info JSON files:
Switch 1: OK
Switch 2: Ports doubled
A bit more information on that topic, just to rule out any strange "side effects":
The very same network configuration has been up and running for the past 2 years, with no significant changes. Last week I had to set up a WAN fallback, and hence switched WAN/LAN1 to WAN. Not sure if this could have caused this.
Regards
TG
Thanks for posting in our business forum.
Technik-Gegg wrote
Clive, thank you for the fast reply.
I suppose you mean the browser cache. Did that to no avail.
I even used a different browser, which never has connected to the Omada controller, just to be on the safe side.
What's even more strange, another switch (SG3210XHP-M2 v2.0) now shows the same behavior, even though it didn't do that yesterday.
And guess what: We also have two of those and the other one is not showing that kind of glitch.
I already suspected some sort of caching/display issues and downloaded and inspected the configuration JSON files for both switches.
The data looks fine at first glance. i.e. ports are all available and enumerated correctly.No wait... not sure where I was looking at: I inspected the JSON files once again, turned out, the ports appear duplicated in the JSON file as well... guess I was already a bit exhausted yesterday
Edit: Here are the screenshots from the Device-Info JSON files:
Switch 1: OK
Switch 2: Ports doubled
A bit more information on that topic, just to rule out any strange "side effects":
The very same network configuration has been up and running for the past 2 years, with no significant changes. Last week I had to set up a WAN fallback, and hence switched WAN/LAN1 to WAN. Not sure if this could have caused this.
Regards
TG
I am now consulting with the dev and see if we need additional information from you.
In the internal log, I found that this is known and estimated to be optimized in the future SDNC update.
Temporarily, you can forget the switch and readopt to fix the issues. Do not reset your Omada controller.
As for now, you may back up your config, device info, and running log for further diagnosis in case I am instructed to collect them.
Appreciate your cooperation.
Update:
This will be further optimized in the SDNC update. ETA in V5.15.X. Please kindly wait for the update.
Temporarily, if you experience the issue, please refer to this line: Temporarily, you can forget the switch and readopt to fix the issues. Do not reset your Omada controller.
