Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Professional Edition
Description
Hi,
I have trouble with neighbours after r10477, seems to be mainly with lldp only (I am aware it said implementetd partally in commits node 
).
On every discovery I have this in the events logs for several devices:
2020-06-11 00:07:52 swi-dc1-core-1 swi-dc1-core-1 Neighbours: 37 deleted, 37 unchanged.
2020-06-11 00:07:43 hp3810-mf-1 hp3810-mf-1 Neighbours: 1 deleted.
2020-06-11 00:07:31 rtr-mpls01 rtr-mpls01 Neighbours: 5 deleted.
2020-06-11 00:03:36 rtr-mpls01 rtr-mpls01 Neighbours: 5 deleted.
2020-06-11 00:02:40 hp3810-mf-1 hp3810-mf-1 Neighbours: 1 deleted.
2020-06-11 00:02:17 swi-dc1-core-1 swi-dc1-core-1 Neighbours: 37 deleted, 37 unchanged.
I am attaching the output of "./poller.php -h device -m neighbours -d" for ostypes; cisco iosxe, arubaos, and hp/aruba provision if that can help for anything.
Attachments
Activity
Last Changed - is datetime when entry with neighbour changed (added/removed/etc).
Autodiscovery - this is an attempt to add new device and store if neighbour already exist.
This table required for reduce unnecessary attempts to auto-add devices.
Entries to this table will added anyway, also if xdp autodiscovery disabled - if remote device already in db as "ok" (your case), if not exist as "xdp disabled".
(Probably need improved popup message for this case).
Confirm everything is back to normal. I even think I have some more neighbours then before.
I just have a question about the popup under "Last Changed": "Remote host <host> (<ip>) successfully added to db. Autodiscovery checked: x ago"
What exactly is that supposed to be for? I see this only on LLDP and "neighbour" devices I already have added. Also I have "xdp" autodiscovery disabled, so it was not added by that feature.
Maybe I misunderstood something about it ?
Hrm, this is not formatting issue, something strange in lldp data.. please attach discovery
./discovery.php -d -m neighbours -h <device>
|
and better additionally attach your snmp dump from device:
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
|
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk
|
Hi,
Nice with the IP, but there is a formatting issue when the remote hostname is too long. I have attached a file
kentbjoh oh, I missed your text.. we not have poller module for neighbours, please make new debugs for discovery:
./discovery.php -h device -m neighbours -d
|
oh, in discovery really discovery.. ignore last comment 
yah..
currently not sure why on old code that trouble happen (really not should).
but anyway, lldp part will synched with lastest changes soon.
Please make and attach additional information about the device:
- full snmp dump from device:
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalksnmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalkIf device not support SNMP version 2c, replace -v2c with -v1.
- If you have problems with discovery or poller processes, please do and attach these debugs:
./discovery.php -d -h <device>./poller.php -d -h <device>
- additionally attach device and/or vendor specific MIB files
Note, this comment is added automatically.
Additionally there is escaping trouble, fixed in r10508.
But if you can, make snmp dump anyway.