Meraki Cloud Controller MIBs for Orion NPM

EDITED: 2012-10-01

I have been having a heck of a time trying to find out what MIBs to use in creating a custom poller for the Meraki Cloud Controller. The real issue is due to the severe limitations of having to go through the Meraki Cloud Controller to poll for data instead of being able to SNMP walk the access points themselves on a local network. Thankfully, I did find the root OID in the Universal Device Poller utility.

Here is some information about Meraki and SNMP -

1. This post is all about polling MR series access points. I am not including info for polling MX routers or MS switches in this post.
2. You can now monitor Meraki MR series access points directly using SNMP, but not OD2 (Outdoor) or wall plug APs. Notes about that are in the comments below.
3. Meraki now has their own MIB database which is included in NPM v10.3 at the very least.
4. You will have to create a custom universal device poller to gather data from Meraki access points.
5. **2012-10-01 - You can still poll the Meraki Cloud Controller if you do not want to poll each MR series access point individually.
6. **2012-10-01 - The Meraki KB database is getting cleaned up. It definitely looks like Meraki has acknowledged that there are discrepancies in their KB and they are working on cleaning it up.

Root OID in the MIB database for the Meraki Cloud Controller.

1.3.6.1.4.1.2967.

Under this tree, here are the supported OIDs:

• cloudController(1)
  • organization(1)
    • organizationName(1) = Only use this if you are an MSP. If you are a singular entity, this info won't matter.
    • networkTable(2) = Networks table.
      • networkEntry(1) = Describes each network.
        • networkID(1) = Network id , consists of 8 octets. Remains the same even if the name of the network changes.
        • networkName(2) = Network name.
    • ssidTable(3) = SSID table.
      • ssidEntry(1) = Desribes each SSID
        • ssidNetworkName(1) = The name of the network that the SSID is a part of. [The same name that is the root network name in the drop down at the top of the Meraki Dashboard.]
        • ssidNumber(2) = SSID number. [Most MR16s and MR24s support up to 15 different SSIDs, each with their own number.]
        • ssidName(3) = The SSID name.
    • apTable(4) =
      • apEntry(1) =
        • apMac(1) = The MAC address of the access point.
        • apName(2) = The administrative name of the access point as defined in the Meraki dashboard.
        • apStatus(3) = The status of the AP's connection to the Meraki Cloud Controller.
        • apConnectedAt(4) = The last time the AP contacted the Meraki Cloud Controller.
        • apClientCount(5) = Current count of connected clients of the access point.
        • apMeshStatus(6) = Whether the AP is currently acting as a gateway or a repeater.
        • apPublicIp(7) = Whether the AP is currently acting as a gateway (as opposed to a repeater).
        • apSerial(8) = The serial number of the access point.
        • apProductCode(9) = The product code of the access point.
        • apProductDescription(10) = AP product description.
        • apNetworkName(11) = The name of the network this AP is in. Useful in tables.
    • apInterfaceTable(5) = AP Interfaces table
      • apInterfaceEntry(1) = Describes each AP.
        • All of the mibs under this table are probably the most interesting as it has apInterfaceSentPkts and apInterfaceRecvPkts and so forth.

Root OIDs for Meraki MR series access points:

See Meraki's official KB for info

I am working on building a view with the supported MIBs for Meraki in Orion NPM now. I will post a UnDP after I have checked out everything.

Is there anyone else out there that is trying to do the same thing?

Message was edited by: Joe Dissmeyer on 2012-10-01 - Updated Meraki SNMP info - Removed false claim about Meraki's official KB documentation - Added link to Meraki's KB for supported OIDs