Minor Topology Map Issues
I am starting to see some minor issues when viewing the topology map. They are:
1. Sometimes when viewing the map in site view, I can not expand the Client Group belonging to a switch. There are four SG2008 switches in my map and one in particular is more problematic then the others. The more troublesome switch is connected directly to the ER7406 gateway.
2. When expanding the Client Groups, the individual clients are not always highlighted when selecting a network filter to view a particular VLAN. Initially, I thought this was a Chrome issue as MS Edge was highlighting the clients but now Edge is behaving just like Chrome.
LLDP is enabled for all devices in the site settings on the controller. The switches have been rebooted several times with no success. For me, this is not a major concern but it is something that is not quite right.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @jra11500
This is fixed in the latest pre-release firmware OC300 1.33.8.
Would you please update it and let us know the performance?
- Copy Link
- Report Inappropriate Content
Hi @jra11500
Thanks for the feedback.
Did you update to the latest pre-release version? How is the performance?
- Copy Link
- Report Inappropriate Content
Yesterday I upgraded the controller to the latest pre-release version. Today I tested the topology map to see if the issue persists. I have no trouble now with expanding the client groups. When filtering however, not all the VLAN clients are highlighted when selecting an individual VLAN. I tested this with Chrome, MS Edge, and Firefox so it is not a browser issue.
- Copy Link
- Report Inappropriate Content
Hi @jra11500
Thanks for the reply.
What kind of clients are not highlighted? Do they belong to specific VLANs?
Could you please list some examples? Thanks.
- Copy Link
- Report Inappropriate Content
Vincent-TP wrote
Hi @jra11500
Thanks for the reply.
What kind of clients are not highlighted? Do they belong to specific VLANs?
Could you please list some examples? Thanks.
When the issue occurs, it affects both wired and wireless clients. For example, on my Servers VLAN, a Synology NAS fails to highlight. On the IoT VLAN, the Amazon Echo devices are not highlighted. On the Cams VLAN, the Reolink IP cameras are not highlighted but another Synology NAS is hightlighted correctly.
Oddly enough, after expanding and minimizing the Client Group several times in rapid succession, the clients sometimes begin to highlight correctly. I have noticed that if I minimize a Client Group, then click Reset (Network Filter), then select the VLAN again, then expand the Client Group, the clients will usually highlight correctly.
- Copy Link
- Report Inappropriate Content
I can confirm a similar behaviour
For me, all devices are properly highlighted on the correct VLAN the first time i select that vlan in the list. After that, if i reselect the same VLANs again, its hit or miss if the devices will be highlighted or not
Edit : 2 more bugs found
- Cannot move map sometimes, only zoom
- Cannot expand switch client groups
All three bugs can be fixed by, and weirdly, also triggered, by a manual page refresh
-ST
- Copy Link
- Report Inappropriate Content
Hi @jra11500
This is fixed in the latest pre-release firmware OC300 1.33.8.
Would you please update it and let us know the performance?
- Copy Link
- Report Inappropriate Content
With the latest pre-release firmware OC300 1.33.8, the issue is still not fixed but is much better than before with less errors. I just finished some testing and the results are:
1. My VLAN 20 (Private) is highlighting clients that are not members of that VLAN (HP Salon, Echo 1, Fire TV 1). The topology map for VLAN 20 is in the attached file.
2. My VLAN 50 (Public) has two member clients (HP Salon, iPhone Concha) that are not highlighted. The topology map for VLAN 50 is in the attached file.
3. My VLAN 60 (Amazon) has one client (iPhone Concha) incorrectly highlighted and two member clients (Echo 1, Fire TV 1) not highlighted. The topology map for VLAN 60 is in the attached file.
4. All other VLANs appear to be OK.
As you can see, the issue is only affecting a small number of wireless clients which are incorrectly identified. I don’t know if this might be related to using PPSK profiles and a single SSID and I have not tested this with individual VLAN SSIDs.
On a side note, when selecting the management (default) VLAN my EAP610 and EAP772-Outdoor devices are not highlighted even though they are members of that VLAN. From previous posts, I understand that this may be due to design because they are not transmitting an SSID related to the management VLAN. The EAP650-Desktop devices are highlighted correctly. In my view, every device should be highlighted if it has an interface on the selected VLAN.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 394
Replies: 7
Voters 0
No one has voted for it yet.
