Send netdisco-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: Neighbors seen but remote port not populated
(Christian Ramseyer)
2. Re: Neighbors seen but remote port not populated
([email protected])
--- Begin Message ---
Hi Linwood
>> Is there a better debug to show what it is doing, why it is not
>> populating the remote columns?
Can you try to run a discover with full debug output, and then see if
you find your neighbor in there? If we're lucky, we can narrow it down
further from there.
netdisco-do -DISQ discover -d <ip>
Sorry that's all I've got for now, unfortunately we don't have any
Netgear nor Adtran devices for me to try.
Cheers
Christian
--- End Message ---
--- Begin Message ---
Sorry for delay had a firewall die and got distracted...
I ran the debug (I thought the prior one was, but this is much more verbose).
It was VERY long, but I think I pruned it down to the part relevant. It looks
like it is finding LLDP data but not the remote port address. That output is
second below.
But I think I see why, and I can't see that it is anything but a bug in the
SNMP implementation somewhere, probably the Adtran. Here's what a list of the
ports shows (see below). The only catch is that the device it's connected to
as an uplink is on giga-swx 0/2, which is not shown at all. It's like there's
a .26 that is not visible (doing a get for it gives "no such instance").
root@gc911-nms:~# snmpwalk -v2c -c redacted 192.168.1.209
1.0.8802.1.1.2.1.3.7.1.3
iso.0.8802.1.1.2.1.3.7.1.3.0 = STRING: "internal 0/0"
iso.0.8802.1.1.2.1.3.7.1.3.1 = STRING: "swx 0/1"
iso.0.8802.1.1.2.1.3.7.1.3.2 = STRING: "swx 0/2"
iso.0.8802.1.1.2.1.3.7.1.3.3 = STRING: "swx 0/3"
.... repetitive stuff removed
iso.0.8802.1.1.2.1.3.7.1.3.24 = STRING: "swx 0/24"
iso.0.8802.1.1.2.1.3.7.1.3.25 = STRING: "giga-swx 0/1"
Interestingly the remote device name appears in this device's LLDP section,
with all correct info, i.e:
iso.0.8802.1.1.2.1.4.1.1.4.1788.25.1 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.5.1788.25.1 = Hex-STRING: 10 DA 43 08 99 B8
iso.0.8802.1.1.2.1.4.1.1.6.1788.25.1 = INTEGER: 7
iso.0.8802.1.1.2.1.4.1.1.7.1788.25.1 = STRING: "0/25"
iso.0.8802.1.1.2.1.4.1.1.8.1788.25.1 = ""
iso.0.8802.1.1.2.1.4.1.1.9.1788.25.1 = STRING: "ETSBH1-SW"
iso.0.8802.1.1.2.1.4.1.1.10.1788.25.1 = STRING: "M4100-26G ProSafe 24-port
Gigabit L2+ Intelligent Edge Managed Switch, 10.0.2.26, B1.0.1.1"
iso.0.8802.1.1.2.1.4.1.1.11.1788.25.1 = STRING: "("
iso.0.8802.1.1.2.1.4.1.1.12.1788.25.1 = STRING: " "
The actual IF-MIB file shows the right names of the local interfaces by the
way:
root@gc911-nms:~# snmpwalk -v2c -c redacted 192.168.1.209 ifdesc
IF-MIB::ifDescr.1 = STRING: swx 0/1: Fast Ethernet (BCM56xx v228)
IF-MIB::ifDescr.2 = STRING: swx 0/2: Fast Ethernet (BCM56xx v228)
IF-MIB::ifDescr.3 = STRING: swx 0/3: Fast Ethernet (BCM56xx v228)
.... repetitive stuff removed
IF-MIB::ifDescr.23 = STRING: swx 0/23: Fast Ethernet (BCM56xx v228)
IF-MIB::ifDescr.24 = STRING: swx 0/24: Fast Ethernet (BCM56xx v228)
IF-MIB::ifDescr.25 = STRING: giga-swx 0/1: Gigabit Ethernet (BCM56xx v228)
IF-MIB::ifDescr.26 = STRING: giga-swx 0/2: Gigabit Ethernet (BCM56xx v228) <<<
This is the real interface
IF-MIB::ifDescr.27 = STRING: vlan 1: VLAN (BCM56xx)
IF-MIB::ifDescr.28 = STRING: vlan 172: VLAN (BCM56xx)
IF-MIB::ifDescr.29 = STRING: vlan 192: VLAN (BCM56xx)
So I think it's just broken. The if index is 26, but I guess if counting from
zero it could be 0/25, but in the LLDp section the index of 25 comes up one
short since it has an internal interface shown?
Anyone think there's a fix for this other than "complain to adtran"? Or am I
misinterpreting?
Sigh.
Thanks.
Linwood
PS. Here's the debug sections I think relevant:
SNMP::Info::_global lldp_sys_cap : LLDP-MIB::lldpLocSysCapEnabled.0 :
.1.0.8802.1.1.2.1.3.6.0
...removed other protocols that all said "unable to resolve method...
SNMP::Info::_load_attr lldp_rem_pid : LLDP-MIB::lldpRemPortId :
.1.0.8802.1.1.2.1.4.1.1.7
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(1) :
.1.0.8802.1.1.2.1.3.7.1.4.1
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(14) :
.1.0.8802.1.1.2.1.3.7.1.4.14
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(8) :
.1.0.8802.1.1.2.1.3.7.1.4.8
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(22) :
.1.0.8802.1.1.2.1.3.7.1.4.22
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(25) :
.1.0.8802.1.1.2.1.3.7.1.4.25
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(11) :
.1.0.8802.1.1.2.1.3.7.1.4.11
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(15) :
.1.0.8802.1.1.2.1.3.7.1.4.15
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(13) :
.1.0.8802.1.1.2.1.3.7.1.4.13
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(17) :
.1.0.8802.1.1.2.1.3.7.1.4.17
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(24) :
.1.0.8802.1.1.2.1.3.7.1.4.24
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(20) :
.1.0.8802.1.1.2.1.3.7.1.4.20
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(21) :
.1.0.8802.1.1.2.1.3.7.1.4.21
...removed other protocols...
SNMP::Info::_load_attr lldp_rem_desc : LLDP-MIB::lldpRemPortDesc :
.1.0.8802.1.1.2.1.4.1.1.8
SNMP::Info::_load_attr lldp_rem_pid_type : LLDP-MIB::lldpRemPortIdSubtype :
.1.0.8802.1.1.2.1.4.1.1.6
SNMP::Info::_load_attr lldp_rem_sysdesc : LLDP-MIB::lldpRemSysDesc :
.1.0.8802.1.1.2.1.4.1.1.10
...removed other protocols...
SNMP::Info::_load_attr lldp_rem_id_type : LLDP-MIB::lldpRemChassisIdSubtype :
.1.0.8802.1.1.2.1.4.1.1.4
SNMP::Info::_load_attr lldp_rem_id : LLDP-MIB::lldpRemChassisId :
.1.0.8802.1.1.2.1.4.1.1.5
...removed other protocols...
SNMP::Info::_load_attr lldp_rem_sysname : LLDP-MIB::lldpRemSysName :
.1.0.8802.1.1.2.1.4.1.1.9
...removed other protocols...
SNMP::Info::_load_attr lldp_rem_cap_spt : LLDP-MIB::lldpRemSysCapSupported :
.1.0.8802.1.1.2.1.4.1.1.11
SELECT me.ip, me.port, me.creation, me.descr, me.up, me.up_admin, me.type,
me.duplex, me.duplex_admin, me.speed, me.name, me.mac, me.mtu, me.stp,
me.remote_ip, me.remote_port, me.remote_type, me.remote_id, me.is_master,
me.slave_of, me.manual_topo, me.is_uplink, me.vlan, me.pvid, me.lastchange
FROM device_port me
WHERE me.ip = '192.168.1.209'
...removed other protocols...
SNMP::Info::_load_attr lldp_rman_addr : LLDP-MIB::lldpRemManAddrIfSubtype :
.1.0.8802.1.1.2.1.4.2.1.3
SNMP::Info::_load_attr lldp_rman_addr : LLDP-MIB::lldpRemManAddrIfSubtype :
.1.0.8802.1.1.2.1.4.2.1.3
[78433] 2019-09-22 21:51:16 debug [192.168.1.209] neigh - processed 0 neighbors
[78433] 2019-09-22 21:51:16 debug -> run worker main/neighbors/100
SNMP::Info::_load_attr ospf_peers : OSPF-MIB::ospfNbrIpAddr :
.1.3.6.1.2.1.14.10.1.1
SNMP::Info::_load_attr ospf_peer_id : OSPF-MIB::ospfNbrRtrId :
.1.3.6.1.2.1.14.10.1.3
...removed other protocols, power supplies etc...
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(1) :
.1.0.8802.1.1.2.1.3.7.1.4.1
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(14) :
.1.0.8802.1.1.2.1.3.7.1.4.14
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(8) :
.1.0.8802.1.1.2.1.3.7.1.4.8
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(22) :
.1.0.8802.1.1.2.1.3.7.1.4.22
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(25) :
.1.0.8802.1.1.2.1.3.7.1.4.25
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(11) :
.1.0.8802.1.1.2.1.3.7.1.4.11
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(15) :
.1.0.8802.1.1.2.1.3.7.1.4.15
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(13) :
.1.0.8802.1.1.2.1.3.7.1.4.13
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(17) :
.1.0.8802.1.1.2.1.3.7.1.4.17
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(24) :
.1.0.8802.1.1.2.1.3.7.1.4.24
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(20) :
.1.0.8802.1.1.2.1.3.7.1.4.20
SNMP::Info::_load_attr lldpLocPortDesc : LLDP-MIB::lldpLocPortDesc(21) :
.1.0.8802.1.1.2.1.3.7.1.4.21
...removed other protocols...
SNMP::Info::_load_attr lldp_rem_media_cap_spt :
LLDP-EXT-MED-MIB::lldpXMedRemCapSupported : .1.0.8802.1.1.2.1.5.4795.1.3.1.1.1
SNMP::Info::_load_attr lldp_rem_vendor : LLDP-EXT-MED-MIB::lldpXMedRemMfgName :
.1.0.8802.1.1.2.1.5.4795.1.3.3.1.5
SNMP::Info::_load_attr lldp_rem_model : LLDP-EXT-MED-MIB::lldpXMedRemModelName
: .1.0.8802.1.1.2.1.5.4795.1.3.3.1.6
SNMP::Info::_load_attr lldp_rem_sw_rev :
LLDP-EXT-MED-MIB::lldpXMedRemSoftwareRev : .1.0.8802.1.1.2.1.5.4795.1.3.3.1.3
SNMP::Info::_load_attr lldp_rem_serial : LLDP-EXT-MED-MIB::lldpXMedRemSerialNum
: .1.0.8802.1.1.2.1.5.4795.1.3.3.1.4
BEGIN WORK
DELETE FROM device_port_properties
WHERE ip = '192.168.1.209'
[78433] 2019-09-22 21:51:17 debug [192.168.1.209] properties - removed 0 ports
with properties
SAVEPOINT savepoint_0
INSERT INTO device_port_properties( ifindex, ip, port, raw_speed,
remote_is_phone )
VALUES( ?, ?, ?, ?, ? ) : '__BULK_INSERT__'
RELEASE SAVEPOINT savepoint_0
COMMIT
[78433] 2019-09-22 21:51:17 debug [192.168.1.209] properties - added 29 new
port properties
[78433] 2019-09-22 21:51:17 debug -> run worker main/vlans/100
-----Original Message-----
From: Christian Ramseyer [mailto:[email protected]]
Sent: Sunday, September 22, 2019 8:52 AM
To: [email protected]; [email protected]
Subject: Re: [Netdisco] Neighbors seen but remote port not populated
Hi Linwood
>> Is there a better debug to show what it is doing, why it is not
>> populating the remote columns?
Can you try to run a discover with full debug output, and then see if you find
your neighbor in there? If we're lucky, we can narrow it down further from
there.
netdisco-do -DISQ discover -d <ip>
Sorry that's all I've got for now, unfortunately we don't have any Netgear nor
Adtran devices for me to try.
Cheers
Christian
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
