Omada Controller (OC200) and TL-SG2218v1.0 Smart Switch MAP Client Group Error
Hi,
I have just installed a new TL-SG2218v1.0 Smart Switch managed by an OC200 Omada controller. Everything seems to be working fine and managing the vLAN and LAGs has been straight forward to do. However, I have noticed that when accessing the CLIENT group within the MAP Topology section you get an error and the client devices are not displayed. Please see the screen grab bellow.
I guess there will be a firmware upgrade reqired to resolve this?
Thanks
Richard
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Dear @RichardHilton,
I have noticed that when accessing the CLIENT group within the MAP Topology section you get an error and the client devices are not displayed.
Are you able to reproduce the problem steadily? Is the Clients page showing the connected clients properly?
Does the issue start to happen after you add the new switch and configure VLAN/LAG in the network?
To wipe the influence of the configuration, perhaps you may backup the current config and then try to disable the VLAN/LAGs to have a check.
If you have any additional information, please do not hesitate to give a reply.
- Copy Link
- Report Inappropriate Content
Hi @Fae
Thanks for getting back to me.
Yes the problem is repeatable. Every time you click on the TL-SG2218 switch CLIENT GROUP you get the General Error message. All Client Groups for all other devices all work OK.
I fully configured the switch before checking the Topology MAP.
It will take some time to re-install the switch.
I will report back once completed.
Thanks
Richard
- Copy Link
- Report Inappropriate Content
Hi @Fae
I've managed to isolate the problem with the device MAP not showing client group members. When I remove the LAG configuration the clients are visible. When I configure it again I get the error.
Unfortunately, I need to have the LAG configuration as it connected to a server with bonded NIC's
Will there be a fix to enable client Group display when a LAG group is configured in a future firmware release?
Thanks
Richard
- Copy Link
- Report Inappropriate Content
Dear @RichardHilton,
I've managed to isolate the problem with the device MAP not showing client group members. When I remove the LAG configuration the clients are visible. When I configure it again I get the error.
Unfortunately, I need to have the LAG configuration as it connected to a server with bonded NIC's
Will there be a fix to enable client Group display when a LAG group is configured in a future firmware release?
Thank you for your valued feedback. I've reported this to the R&D team who will check the problem and add a plan to fix it.
- Copy Link
- Report Inappropriate Content
Fae wrote
Dear @RichardHilton,
I've managed to isolate the problem with the device MAP not showing client group members. When I remove the LAG configuration the clients are visible. When I configure it again I get the error.
Unfortunately, I need to have the LAG configuration as it connected to a server with bonded NIC's
Will there be a fix to enable client Group display when a LAG group is configured in a future firmware release?
Thank you for your valued feedback. I've reported this to the R&D team who will check the problem and add a plan to fix it.
An update: the R&D team has addressed the problem, it's planned to fix it in the subsequent firmware update.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Dear @RichardHilton,
RichardHilton wrote
Hi @Fae Just to let you know the TL-SG2218 firmware release 1.0.1 Build 20210407 Rel.65593 & the Omada OC firmware release 1.8.0 Build 20210406 Rel.58757 have fixed this issue. Many thanks for all your help Richard
Thank you for your valued feedback. Glad to hear that your concern was resolved finally.
Hope you enjoy the Internet and have a great day!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2328
Replies: 8
Voters 0
No one has voted for it yet.