sug7

@"mesverrum"unfortunately that OID doesn't work on the HP switches we have.

The table I put together above was on node details, so unique output per switch. If you wanted more of a generic output across all switches you would have to also query node table since the LLDP table only contains node ID not name.

@"mesverrum"yes with the OIDs below I have all the data I need, its just I'm unsure on the SWQL query to join this together... lldpLocalPortID - 1.0.8802.1.1.2.1.3.7.1.3 lldpLocPortDesc - 1.0.8802.1.1.2.1.3.7.1.4 lldpRemSysName - 1.0.8802.1.1.2.1.4.1.1.9 lldpRemPortDesc - 1.0.8802.1.1.2.1.4.1.1.8

@"mesverrum"I was able to use your suggestion of the NodeLldpEntry table to pull together a SWQL query that builds a pretty nice looking LLDP table, however, this only works if the interfaces are added to monitoring, which we generally don't do.... I guess its back to the drawing board... Here's the SWQL query and table if…

@"jason.carrier"very interested in this but cant seem to access the links? 'The page you are trying to access was not found. Please check your URL for typos and try again.'

Does anyone know if this will work with HP Procurve switches?

I was able to get this working but creating a simple service in Clearpass that matches on the SAM 'Connection:NAD-IP-Address' then checks day of week (mon, tue, wed, thur, fri, sat, sun) and has a default allow access profile.