[Netdot-users] Netdot and device topology via LLDP

Matej Vadnjal

2016-10-18 11:34:47 UTC

Hi Stefano

It is possible that the LLDP neigbour interface info these devices
return via SNMP makes it impossible to determine the correct neighbours.

Some devices report the local interface name to their neighbour. Some
others report ifIndex or a short or long interface name.

I don't have any HP or 3com gear in my network, so I can't be certain
this is the issue in your case as well.

You'll need do do an snmpwalk for ifTable and lldpRemTable on two
adjacent devices and compare interface values returned.

Also take a look at the code of SNMP::Info Perl module (this is what
netdot uses for snmp discovery). You might be able to hack together a
patch for your device types. If you do, make sure to submit it to
SNMP::Info developers.

Best regards
Matej Vadnjal

Post by Stefano Martini
Hi people,
I am using Netdot 1.6 in a network with 150 switches (HP and 3Com).
The configuration parameters of these switches (IP, SNMP community,
SNMP version, ) are stored into the Netdot database. For each switch
Netdot correctly collects information such as: device name, system
description, interfaces list,
All the switches are configured to have LLDP enabled. Some switches have CDP enabled too.

TOPO_USE_DP => 1,
TOPO_WEIGHT_DP => 8,

ADD_UNKNOWN_DP_DEVS => 1,

The updatedevice.pl (run with T D A I ) gets uplinks only for
devices with CDP enabled. All devices with LLDP only have no uplinks.
Does Netdot support LLDP enabled devices ?
If yes, how can I solve the missing of uplinks for devices with LLDP ?
Thanks in advance
Stefano
_______________________________________________
Netdot-users mailing list
https://osl.uoregon.edu/mailman/listinfo/netdot-users