Broken Mikrotik LLDP-MIB implementation causes ipdevpoll LLDP plugin to crash #2015
Comments
|
Sounds pretty strange. lldpRemEntry OBJECT-TYPE
SYNTAX LldpRemEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a particular physical network connection.
Entries may be created and deleted in this table by the agent,
if a physical topology discovery process is active."
INDEX {
lldpRemTimeMark,
lldpRemLocalPortNum,
lldpRemIndex
}
::= { lldpRemTable 1 }Which makes it sound like the MikroTik implementation is broken. It would be interesting to see what it actually replies. Do you have the MIB available (http://www.ieee802.org/1/files/public/MIBs/LLDP-MIB-200505060000Z.txt) and can you query a MikroTik device using the NET-SNMP command line utilities using the MIB definition? E.g.
|
|
@lunkwill42 Thank you for replying quickly! Here's the results from this specific MikroTik (I believe it's happening to ALL our MikroTiks I imported into NAV) |
|
In my previous output, I used a computer that had the MIB you linked, but was questioning the "Wrong Type (should be BITS)" results..... So, I downloaded the MIB specifically you suggested, and related modules on the pre-built NAV 5.0 VM appliance (using VirtualBox) and placed them into Lastly, as I was curious what Windows 10 shows (using iReasoning MIB browser), I grabbed the same MIB you referenced and queried the same MikroTik CCR1009-8G-1S device as above - using same OID query LLDP-MIB::lldpRemTable (numeric OID: .1.0.8802.1.1.2.1.4.1): |
|
That was a bit excessive :-D Your first output confirms that the From your first example, there's From a switch with a proper implementation, it looks like this: I wouldn't even begin to know how to interpret the single value from your Mikrotik; is it a lldpRemLocalPortNum or a lldpRemIndex? Who knows. The best we could do, IMHO, is to workaround this in NAV by ignoring the LLDP-MIB and continuing if there's an error parsing the results. |
lunkwill42
changed the title
|
Yessir, I will give it your patch a go and report back soon. Thank you for looking into this! |
So, did you test the patch, @xorr0 ? :-) |
|
Though there is no feedback from @xorr0 , I was able to test this on a customer's Mikrotik devices. |
|
Closed by #2020 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running the fresh pre-packaged Virtual Appliance NAV v5.0 released 11/7/2019. I did a simple Bulk Import with lines like this (showing this specifically as this is the device providing an error):
myroom:10.255.213.34:myorg:GSW:SNMP v1 read-only profile|public SNMP v1 read-only profile:The device is a MikroTik CCR1009-8G-1S
When reviewing the log
/var/log/nav/ipdevpoll.logI see this (among MANY others similar):Steps to reproduce the behavior:
Expected behavior
Hope to get the Topology job to properly run with MikroTik devices, and clear this error.
Environment (please complete the following information):
I can provide any additional information required, let me know. Thank you for any assistance.
The text was updated successfully, but these errors were encountered: