Build LLDP tree from SNMP information
- Net-SNMP with python bindings
- Be able to resolve device IP from name reported through LLDP
- Same SNMP community configured on all devices
- Currently this script only handles LLDP for HP ProCurve and Juniper JUNOS devices
- HP ProCurve firmware I.10.43 and perhaps the whole I-series seems to lack OIDs for model, firmware version, serial number.
- Juniper JUNOS older than version 11 seems to lack LLDP OIDs
- Script can only reach devices which report a resolvable hostname over LLDP and have the same SNMP community configured.
- SNMP version 1 and 2 only
- If a device is connected to another with several ports, only the first port gets registered in the tree.
- Network interface information
- VLAN information
Run the script with hostname of a SNMP and LLDP enabled device as argument. That device will become root of the generated lldp tree structure.
usage: lldp.py [options] COMMAND HOST
positional arguments:
COMMAND list or tree (default: list)
HOST hostname or IP address
optional arguments:
-h, --help show this help message and exit
-c COMMUNITY, --community COMMUNITY
SNMP community (default: public)
-q, --quiet Do not display or log errors
-l LOGFILE, --logfile LOGFILE
Log file (Default is logging to STDERR)
-o OIDFILE, --oidfile OIDFILE
JSON file containing SNMP OIDs (default: oid.json)
If COMMAND is list, the JSON output to STDOUT is a list of hostnames detected recursively through LLDP.
[ "switch001.example.net", "switch008.example.net", "switch036.example.net", # output truncated ]
If COMMAND is tree, output is JSON tree structure in following format:
{
"id": "switch001.example.net",
"children": [
{
"id": "switch008.example.net",
"children": [
{
"id": "switch036.example.net"
},
{
"id": "switch005.example.net"
},
{
"id": "switch001.example.net",
"children": [
{
"id": "switch028.example.net"
},
{
"id": "switch019.example.net"
},
{
"id": "switch014.example.net"
},
{
"id": "switch032.example.net"
},
{
"id": "switch045.example.net",
"children": [
{
"id": "switch056.example.net"
}
]
}
# output truncated
]
}
]
}
]
}
getinfo.py is designed to be run with lldp.py list output as input, either through stdin (pipe, for example) or by specifying a text file with the '-f' flag. Something like this:
export SNMPCOMMUNITY=secretcommunity lldp.py list switch001.example.net | getinfo.py > deviceinfo.json -or- lldp.py list switch001.example.net > list.json getinfo.py -f list.json -or- lldp.py list switch001.example.net > list.json cat list.json | getinfo.py
Other flags:
usage: getinfo.py [-h] [-f INPUTFILE] [-c COMMUNITY] [-q] [-l LOGFILE]
[-o OIDFILE]
optional arguments:
-h, --help show this help message and exit
-f INPUTFILE, --inputfile INPUTFILE
File to read list of devices from (defaults to reading
from stdin)
-c COMMUNITY, --community COMMUNITY
SNMP community (default: public)
-q, --quiet Do not display or log errors
-l LOGFILE, --logfile LOGFILE
Log file (Default is logging to STDERR)
-o OIDFILE, --oidfile OIDFILE
JSON file containing SNMP OIDs (default: oid.json)
Prerequisites:
- pydot library
graph.py is designed to be run with getinfo.py output as input, either through stdin (pipe, for example) or by specifying a text file with the '-f' flag. A device has to be specified to put in the root of the graph. Something like this:
export SNMPCOMMUNITY=secretcommunity lldp.py list switch001.example.net | getinfo.py > deviceinfo.json cat deviceinfo.json | graph.py -o graph.png switch001.example.net
Other flags:
usage: graph.py [-h] [-i INFOFILE] [-o OUTFILE] [-l LOGFILE] [-q] [-v] ROOT
positional arguments:
ROOT Device to put as root of the graph
optional arguments:
-h, --help show this help message and exit
-i INFOFILE, --infofile INFOFILE
File to read info about devices from (default:
info.json, failing that: stdin)
-o OUTFILE, --outfile OUTFILE
File to write to (default: graph.png)
-l LOGFILE, --logfile LOGFILE
Log file (default is logging to STDERR)
-q, --quiet Do not display or log errors
-v, --verbose Increase verbosity when using logfile.
Public domain. Please see LICENSE file.