NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Insight Cloud Portal - GC110 - Connected Neighbors
Hi, Re: Netgear Insight GC110 (Firmware 1.0.5.25) Am a at a bit of a loss here. I picked up a pair of these switches for a small site, who are hoping to better manage their internet traffic. I h...
There seems to be some confusion. The information under Device -> Switch -> [Click on the port] -> Connected Neighbors -> Status -> Neighbor Info is dynamically updated according the device plugged, it's provided by LLDP-MD. None of these fields is intended to be edited for the obvious reason. When you go the Device -> Switch -> [Click on the port] -> Settings you find the Port Description field, which is editable. Unfortunately, this information (and some more ineresting one) is not used elsewhere (e.g. on Devices -> Switch on the Port mouse-over or the Port information below.
Hi,
Thank you for your response, not that it was particularly helpful.
Your comment "None of these fields is intended to be edited for the obvious reason" doesn't really elaborate on the 'obvious reason'.
It would seem my site is not populating properly, with only the Netgear and Ubiquiti devices showing up. Of the 15 other available ports, despite all clients being LLDP enable, only 4 are offering up their MAC addresses. None of the ports have 'Neighbor Name' nor 'Neighbor Description' populated.
Even the one port which I have configured with a 'Neighbor Description' via the mobile app, doesn't propogate to the PC based cloud portal.
A very clunky piece of work to say the least.
Paul
Pristle wrote:Your comment "None of these fields is intended to be edited for the obvious reason" doesn't really elaborate on the 'obvious reason'.
All the information shown under Neigbour Info, including the Neigbour Description (App says just Description) is coming from the connected device by LLDP - and can't be edited. That's why it's obvious.
Pristle wrote:It would seem my site is not populating properly, with only the Netgear and Ubiquiti devices showing up. Of the 15 other available ports, despite all clients being LLDP enable, only 4 are offering up their MAC addresses. None of the ports have 'Neighbor Name' nor 'Neighbor Description' populated.
What are these other clients, what kind of lldpd is in place there?
Please note that a common Windows 10 client - with the Microsoft-LLDP-Driver enabled on the interface - does only provide Chassis ID: [MAC], Chassis ID Subtype: MAC Address, Port ID: [MAC], Port ID Subtype: MAC Address - neither a neighbor name or description.
Pristle wrote:Even the one port which I have configured with a 'Neighbor Description' via the mobile app, doesn't propogate to the PC based cloud portal.
Provide more information - "Neighbor Description" isn't editable or configureable. You might talk of the confusing "Port Description" label for two purposes:
a) the Port Description, an editable string on on the switch port (which deploys nicely to both the App as well as the Web UI for me), andb) the Port Description, in the Neigbor Information, LLDP based, showing the connected device port information, e.g. "Device Port 5" from the connected device.
Schumaku, you response this time has been a lot more concise. Thank you.
Point to note, I can only set and view 'Port Description' via the mobile app. This does not propogate to the Insight Portal. 'Neighbor Name', 'Neighbor Desc.' and 'Port Desc.' remain blank on the Insight Portal. If I select a port, I see a 'Summary' tab and a 'Settings' tab on the left. Under 'Summary' I see the Overview of the port, however 'Settings' is blank. It's in here that I expected to have the ability to assign things like 'Port Desc.'.
The other clients you queried are Hyper-V Servers, print servers and Windows 10 based PCs. The Hyper-V configuration poses it's own unique set of issues, but I can monitor throughput and traffic pattern with other tools there. As for the Windows 10 machines, not all present their MAC to the switch. But then neither do the print servers.
Interestingly, using the tool LDWin on the client machine, the 'Neighbor Desc.' appears in the app on the client PC.
These issues of non-propogation are why I began this quest for answers in the first place. Why, if these entries do not automatically propogate, for whatever reason, why is there no mechanism to make manual entries somewhere?
Paul
Pristle wrote:I can only set and view 'Port Description' via the mobile app.
...
If I select a port, I see a 'Summary' tab and a 'Settings' tab on the left. Under 'Summary' I see the Overview of the port, however 'Settings' is blank. It's in here that I expected to have the ability to assign things like 'Port Desc.'.Some peek-and-poke in my own and customer environments appears like the Settings are shown on PoE switch models (GC110P, GC510PP), but remains empty on non-PoE switches (GS110, GS728X) - must be a bug in the Web portal. YeZ
Pristle wrote:This does not propogate to the Insight Portal. 'Neighbor Name', 'Neighbor Desc.' and 'Port Desc.' remain blank on the Insight Portal.
This is only LLDP data (inlcuding the LLDP Port Name data) and has no relation to switch port configured Port Name.
There is no propagation issue: The Port Description from the other side can only show up if there is LLCP workable - as it is remote data.
Pristle wrote:The other clients you queried are Hyper-V Servers, .... The Hyper-V configuration poses it's own unique set of issues, but I can monitor throughput and traffic pattern with other tools there.
That's unrelated to LLDP, isn't it?
Pristle wrote:As for the Windows 10 machines, not all present their MAC to the switch.
Hm, the Win 10 systems with the Microsoft-LLDP-Driver in place on each interface stack seem to preset the MAC address information to all Insight managed switches for us. (And hey, I'm not Netgear!).
Pristle wrote:But then neither do the print servers.
What print servers are these? Make, model, firmware, ...?
Pristle wrote:Interestingly, using the tool LDWin on the client machine, the 'Neighbor Desc.' appears in the app on the client PC.
LDWin does make use of both the standardized LLDP _and_ the proprietary CDP - where the later is not supported on the Netgear switches.
Regards
-Kurt
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
