Insight Cloud Portal - GC110 - Connected Neighbors

Question

Hi,Re: Netgear Insight GC110 (Firmware&nbsp;1.0.5.25)&nbsp;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 have also signed onto the Premium subscription for "mobile app + cloud".&nbsp;My question is: Where can I edit the name of the connected devices? Other than MAC addresses, the fields are blank under 'Summary'. Inutitively I headed for 'Settings', but that presents a blank screen (regardless of browser).&nbsp;I then thought perhaps if I use the 'Direct Connect Web-browser', I may have better fortune. Nada, the interface must be among the worst I've seen in a long time.&nbsp;Is there a CLI type interface on these devices? It seems counterintuitive when the hype for these is 'cloud'.&nbsp;Any guidance would be appreciated.&nbsp;&nbsp;&nbsp;Paul

schumaku · Answer

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.

Pristle · Answer

Hi,&nbsp;Thank you for your response, not that it was particularly helpful.&nbsp;Your comment "None of these fields is intended to be edited for the obvious reason" doesn't really elaborate on the 'obvious reason'.&nbsp;&nbsp;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.&nbsp;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.&nbsp;&nbsp;A very clunky piece of work to say the least.&nbsp;Paul

schumaku · Answer

Pristle&nbsp;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.&nbsp;Pristle&nbsp;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&nbsp;there?Please note that a common Windows 10 client - with the Microsoft-LLDP-Driver enabled&nbsp;on the interface - does only provide&nbsp;Chassis ID: [MAC],&nbsp;Chassis ID Subtype:&nbsp;MAC Address,&nbsp;Port ID: [MAC],&nbsp;Port ID Subtype:&nbsp;MAC Address - neither&nbsp;a neighbor&nbsp;name or description.&nbsp;Pristle&nbsp;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&nbsp;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.&nbsp;&nbsp;

Pristle · Answer

Schumaku, you response this time has been a lot more concise. Thank you.&nbsp;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.'.&nbsp;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.&nbsp;Interestingly, using the tool LDWin on the client machine, the 'Neighbor Desc.' appears in the app on the client PC.&nbsp;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?&nbsp;Paul&nbsp;&nbsp;

schumaku · Answer

Pristle&nbsp;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.&nbsp;YeZ&nbsp;&nbsp;Pristle&nbsp;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.&nbsp;There is no propagation&nbsp;issue: The Port Description from the other side can only show up if there is LLCP workable - as it is remote data.&nbsp;Pristle&nbsp;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?&nbsp;Pristle&nbsp;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!).&nbsp;Pristle&nbsp;wrote:But then neither do the print servers.What print servers are these? Make, model, firmware, ...?&nbsp;&nbsp;Pristle&nbsp;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

Forum Discussion

Insight Cloud Portal - GC110 - Connected Neighbors

7 Replies

Related Content

Neighbor AP feature and Mesh

WAC540 not connecting to Insight Cloud

Activate Insight Premium Subscription

Insight no longer connects to devices

Insight VPN connection to BR500 questions

NETGEAR Academy

ProSupport for Business