I viewed a sapwalk from a Meraki MX400 and Meraki MX64. Both do not have the OID
.1.3.6.1.2.1.17.4.3.1.1 in the sapwalk for bridge-mib unfortunately.
The Meraki doc states below. Curiously, the sapwalk of the two devices do not include any serial number reference.
"The Meraki dashboard and Meraki SNMP capable devices support the following standard MIBs:
SNMPv2-MIB .1.3.6.1.2.1.1
IF-MIB .1.3.6.1.2.1 "
There is a Meraki-Cloud-Controller-MIB for snmp polling to the Meraki Dashboard only. It has an interface table section where it has an interfaceMAC.
The Meraki dashboard snmp.meraki.com would have to be polled for that specific device so not sure how to make Spectrum do that or if that could help.
We don't have snmp open to snmp.meraki.com at this time.
Original Message:
Sent: 11-20-2019 04:27 PM
From: Joseph Ackley
Subject: Meraki MX to Cisco Switch connection modeling
The only other thing I can think of to look at is do either of these devices also support the dot1dTpFDB (forwarding) table.
Original Message:
Sent: 11-20-2019 03:00 PM
From: Jon Velazquez
Subject: Meraki MX to Cisco Switch connection modeling
I cannot get Spectrum to create a link between a Cisco switch and a Meraki MX device when doing Discover Connections from either device. Cisco is talking CDP and Meraki MX would be talking LLDP I believe. So in this scenario would there be another method Spectrum would use to make the connection? Cisco Device and Meraki MX device have different snmp profiles but I do not think that would matter.