Insight Cloud Portal - GC110 - Connected Neighbors

---

schumaku wrote:

---

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 

That then makes sense.

 

---

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.

Perhaps I'm not explaining myself well here. By propogation I mean the name assigned in 'Port Desc.' in the mobile app, which while visible in the mobile app, isn't visible in the Cloud Portal (Port Number>Summary>Neighbor Info). Well in my case that's how things are. I refer to the attached image. The 'Port Desc.' can only be modified and seen in the mobile app.

This doesn't seem correct as I thought this was not reliant on LLDP and you suggested in previous advice: 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)

By Web UI, do you mean Cloud Portal or

 

---

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?

Correct. I included that purely for painting a picture of the site.

 

---

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!).

 

I've learned today that a team of auditors has been on site over the last few week or two. They brought with them and plugged in small 5-port unmanaged switches of their own. These have been plugged into wherever they've thought convenient, unplugged client machine from wall and into their switches.

The email I've sent the client this morning has not been subtle.

 

---

Pristle wrote:

But then neither do the print servers.

---

What print servers are these? Make, model, firmware, ...? 

2 x TP-Link PS110U, which are due to be retired and then 2 x Ricoh Aficio devices.

 

---

Pristle wrote:

Interestingly, using the tool LDWin on the client machine, the 'Neighbor Port 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.

I've made a correction. In this case I've set the 'Port Desc.' in the mobile app and it's appeared in LDWin. I implemented this tool in my bid to get my head around LLDP. Something I've never concerned myself with. But like so many 'standards' in our industry, seems it is paid lip service by the entities we'd expect more from.

 

 

 

As you can probably gather, I'm not Netgear either.

What I had been hoping to do, was provide the directors of this client with a pictorial view of who's doing what with their limited bandwidth. As things are, I have to provide a separate legend chart explaining who belongs to which port on which switch.

 

I'm content to leave this here, unless you could provide any further comment on any other obvious things I might be missing. You've provided some good insight (excuse the pun) thus far.  

 

Thanks,

Paul

---