Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Combine Poller Data to form a LLDP Neighbour Table?

Hi,

I'm looking to create an LLDP table based on information polled from HPE Procurve switches using UDP, to show local port, remote system name and remote port side by side.

I created the following pollers;

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

Each of the pollers work great individually, however how do I combine the data?

I tried using the 'Node Tabular Universal Device Poller' widget, however it displays the data from the 3 pollers under each other, ideally I would like it side by side.

I also tried to write up a query for this but being pretty new to SWQL I can't seem to figure it out....

Any advise would be appreciated!

Thanks,

Sug7

Find more posts tagged with

Accepted answers

All comments

rschroeder

This looks good. I'm watching to see what solution is provided by others.

mesverrum

Ok so the reason that the data would be stacked up when you tried to assign it as a custom table is because the tables use a different scheme for their rowid's. I tested those values against some HP switches I had in my lab and it looks like youd be able to join them in theory using 1.0.8802.1.1.2.1.3.7.1.2 since thats listed as the local port number, but my HP device said that was not available

Without something to correlate the remote system to a local port all we have is two lists of data with nothing in common between them.
With that said, Solarwinds natively polls LLDP data from devices that actually give us all the required info to make it useful. Have you taken a look at the NodeLldpEntry table in your database? What you are looking for probably already exists there with no need to muck around with UNDP's at all.

sug7

@mesverrumI 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 its of any use to anyone...

SELECT i.InterfaceName as [Interface], l.RemoteSystemName, l.RemotePortDescription as [Remote Port], l.RemoteIpAddress
FROM Orion.NodeLldpEntry l, Orion.npm.Interfaces i
WHERE l.nodeID = ${NodeID} and l.nodeID like i.NodeID and LocalPortNumber like i.Index

2020_04_10_22_03_13_Node_Details_Summary_LHBSWC0001.png

mesverrum

That's a legit point, the undp gets you away from the dependency on monitoring the interface. On your switches are you able to get the local port Id column then you could join across the two tables with those.

sug7

@mesverrumyes 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

rschroeder

@sug7 or @mesverrum , supposing a person was monitoring all ports on all switches. The SWQL provided above shows useful information, but is missing the name of the switches whose ports see LLDP neighbors. I'm imagining the SWQL query needs new columns or lines that add something like NodeName or NodeCaption or something similar . . .

Would either of you be willing to share with me the SWQL lines that would add the node name to the output of the query?

Many thanks,

Rick Schroeder

sug7

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

SELECT i.node.Caption, i.InterfaceName as [Interface], l.RemoteSystemName, l.RemotePortDescription as [Remote Port], l.RemoteIpAddress
FROM Orion.NodeLldpEntry l, Orion.npm.Interfaces i
WHERE l.nodeID = ${NodeID} and l.nodeID like i.NodeID and LocalPortNumber like i.Index

alex.schoneveld

Looks similar to a CDP entry that others have provided,

We might be able to convert the LLDP table to be similar to the CDP query below:

(note the below removes cisco phones - ie excludes SEP in the second paragraph)

SELECT I.InterfaceName AS [Local Interface], CDP.IPAddress AS [IP Address], DeviceId AS Device, DevicePort AS [Remote Interface], (SELECT N2.DetailsURL from Orion.Nodes N2 JOIN Orion.NodeIPAddresses **bleep** ON (N2.NodeID = **bleep**.NodeID) WHERE **bleep**.IPAddress = CDP.IPAddress) AS [_LinkFor_Device]
FROM Orion.NodeCdpEntry CDP
JOIN Orion.Nodes N ON (N.NodeID = CDP.NodeID)
LEFT OUTER JOIN Orion.NPM.Interfaces I ON ((CDP.NodeID = I.NodeID) AND (CDP.IfIndex = I.Index))
WHERE (CDP.NodeID = ${NodeID}) AND (N.IPAddress <> CDP.IPAddress)