Support of Meraki Switches

[ageldenberg]

Hello, NeDi community.

Has anyone been successful in recognizing nodes connected to Meraki switches?  I can see that the switches are being polled via SNMP properly.  However, nothing connected to those switches end up in the database.  Any help will be highly appreciated.

[rickli]

It should be possible, if they support bridge-fwd tables in SNMP. You can use Defed to test (tutorial on YT).
If it's only possible via CLI or REST, it could be addressed with a feature request...

[ageldenberg]

Rickli,

Would you, kindly, provide a link to Youtube video you mentioned?  I did not find it.  I will greatly appreciate that.

Thank you very much for your reply.

[rickli]

I admit it's used to be called Defgen and that's probably why you didn't find it. It's fairly long and all you need is the part where to check the bridge-fwd table (3:20). So, go to Devices-Status and click the triangle icon. Click on the walking-guys next to the "MAC Address" selectbox. If the 1st or 2nd one reveals a list, you're good...

https://youtu.be/bunFHB-RoUQ

[ageldenberg]

Rickli,

Is there a way to generate .def file from MIB file? Information: https://mibs.observium.org/mib/MERAKI-CLOUD-CONTROLLER-MIB/,  https://circitor.fr/Mibs/Html/M/MERAKI-CLOUD-CONTROLLER-MIB.php.  Could not upload the actual .mib file.

[ageldenberg]

NeDi Gurus,

Could any of yo help me creating the .def file from the attached snmpwalk outputs (snmpwalk_meraki.txt - with translated OIDs and snmpwalk_meraki2.txt - with non-translated OIDs)?

I tried to do it via defgen screen, but it did not work.  I am trying to build it by comparing the structure of existing .def files with the outputs of snmpwalk. 

However, in the structure of .def file I did not find how to define OIDs to look for MAC addresses of connected devices. 

In the attached files the connected devices can be found by polling following OIDs:

.1.3.6.1.2.1.17.4.3.1.1.0.4.242.242.11.1 = STRING: 0:4:f2:f2:b:1
.1.3.6.1.2.1.17.4.3.1.1.0.27.23.0.35.16 = STRING: 0:1b:17:0:23:10
.1.3.6.1.2.1.17.4.3.1.1.0.27.23.0.35.18 = STRING: 0:1b:17:0:23:12
.1.3.6.1.2.1.17.4.3.1.1.0.114.120.223.10.115 = STRING: 0:72:78:df:a:73
.1.3.6.1.2.1.17.4.3.1.1.0.114.120.223.60.140 = STRING: 0:72:78:df:3c:8c
.1.3.6.1.2.1.17.4.3.1.1.40.41.134.10.198.6 = STRING: 28:29:86:a:c6:6
.1.3.6.1.2.1.17.4.3.1.1.52.86.254.28.105.112 = STRING: 34:56:fe:1c:69:70
.1.3.6.1.2.1.17.4.3.1.1.52.86.254.28.105.163 = STRING: 34:56:fe:1c:69:a3
.1.3.6.1.2.1.17.4.3.1.1.100.22.127.73.71.71 = STRING: 64:16:7f:49:47:47
.1.3.6.1.2.1.17.4.3.1.1.100.22.127.73.72.112 = STRING: 64:16:7f:49:48:70
.1.3.6.1.2.1.17.4.3.1.1.100.22.127.73.77.89 = STRING: 64:16:7f:49:4d:59
.1.3.6.1.2.1.17.4.3.1.1.112.11.79.122.5.16 = STRING: 70:b:4f:7a:5:10
.1.3.6.1.2.1.17.4.3.1.1.224.203.188.52.14.153 = STRING: e0:cb:bc:34:e:99
.1.3.6.1.2.1.17.4.3.1.1.232.152.109.3.22.0 = STRING: e8:98:6d:3:16:0
.1.3.6.1.2.1.17.4.3.1.1.232.152.109.25.3.0 = STRING: e8:98:6d:19:3:0
.1.3.6.1.2.1.17.4.3.1.1.232.152.109.25.3.16 = STRING: e8:98:6d:19:3:10
.1.3.6.1.2.1.17.4.3.1.1.232.152.109.25.3.18 = STRING: e8:98:6d:19:3:12

As you can see the OIDs are constructed by converting MAC address of the device into decimal representation, starting from:  .1.3.6.1.2.1.17.4.3.1.1.

.1.3.6.1.2.1.17.4.3.1.1.0.114.120.223.10.115 = STRING: 0:72:78:df:a:73    (0=0.114=72.120=78.223=df.10=a.115=73)


In translated format it looks like this:

BRIDGE-MIB::dot1dTpFdbAddress.'......' = STRING: 0:4:f2:f2:b:1
BRIDGE-MIB::dot1dTpFdbAddress.'....#.' = STRING: 0:1b:17:0:23:10
BRIDGE-MIB::dot1dTpFdbAddress.'....#.' = STRING: 0:1b:17:0:23:12
BRIDGE-MIB::dot1dTpFdbAddress.'.rx..s' = STRING: 0:72:78:df:a:73
BRIDGE-MIB::dot1dTpFdbAddress.'.rx.<.' = STRING: 0:72:78:df:3c:8c
BRIDGE-MIB::dot1dTpFdbAddress.'()....' = STRING: 28:29:86:a:c6:6
BRIDGE-MIB::dot1dTpFdbAddress.'4V..ip' = STRING: 34:56:fe:1c:69:70
BRIDGE-MIB::dot1dTpFdbAddress.'4V..i.' = STRING: 34:56:fe:1c:69:a3
BRIDGE-MIB::dot1dTpFdbAddress.'d..IGG' = STRING: 64:16:7f:49:47:47
BRIDGE-MIB::dot1dTpFdbAddress.'d..IHp' = STRING: 64:16:7f:49:48:70
BRIDGE-MIB::dot1dTpFdbAddress.'d..IMY' = STRING: 64:16:7f:49:4d:59
BRIDGE-MIB::dot1dTpFdbAddress.'p.Oz..' = STRING: 70:b:4f:7a:5:10
BRIDGE-MIB::dot1dTpFdbAddress.'...4..' = STRING: e0:cb:bc:34:e:99
BRIDGE-MIB::dot1dTpFdbAddress.'..m...' = STRING: e8:98:6d:3:16:0
BRIDGE-MIB::dot1dTpFdbAddress.'..m...' = STRING: e8:98:6d:19:3:0
BRIDGE-MIB::dot1dTpFdbAddress.'..m...' = STRING: e8:98:6d:19:3:10
BRIDGE-MIB::dot1dTpFdbAddress.'..m...' = STRING: e8:98:6d:19:3:12

Going back to non-translated variant, the interfaces the devices are connected to are specified like this:

.1.3.6.1.2.1.17.4.3.1.2.0.114.120.223.10.115 = INTEGER: 14
.1.3.6.1.2.1.17.4.3.1.2.0.114.120.223.60.140 = INTEGER: 13
.1.3.6.1.2.1.17.4.3.1.2.40.41.134.10.198.6 = INTEGER: 38
.1.3.6.1.2.1.17.4.3.1.2.52.86.254.28.105.112 = INTEGER: 51
.1.3.6.1.2.1.17.4.3.1.2.52.86.254.28.105.163 = INTEGER: 51
.1.3.6.1.2.1.17.4.3.1.2.100.22.127.73.71.71 = INTEGER: 21
.1.3.6.1.2.1.17.4.3.1.2.100.22.127.73.72.112 = INTEGER: 17
.1.3.6.1.2.1.17.4.3.1.2.100.22.127.73.77.89 = INTEGER: 19
.1.3.6.1.2.1.17.4.3.1.2.112.11.79.122.5.16 = INTEGER: 1
.1.3.6.1.2.1.17.4.3.1.2.224.203.188.52.14.153 = INTEGER: 31
.1.3.6.1.2.1.17.4.3.1.2.232.152.109.3.22.0 = INTEGER: 42
.1.3.6.1.2.1.17.4.3.1.2.232.152.109.25.3.0 = INTEGER: 41
.1.3.6.1.2.1.17.4.3.1.2.232.152.109.25.3.16 = INTEGER: 43
.1.3.6.1.2.1.17.4.3.1.2.232.152.109.25.3.18 = INTEGER: 39


INTEGER:42 means Port 42.

Please, advice if .def file can even be created in such a way that connected devices can be then consumed into the database.

Thanks a lot for help.

[ageldenberg]

Posted .def files here:  https://forum.nedi.ch/index.php?topic=2205.0