Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

If you use NPM to monitor Meraki MX68's, do you have problems getting ports to display?

Beginning with Meraki MX68's, it seems NPM isn't discovering / monitoring the correct ports. Port 1 (a.k.a.: Internet 1) is not being discovered by NPM (we're using NAM Platform 2019.4 and HF 3). And when we select Port 12 for monitoring, NPM displays Port 11. Port 12 is not displayed at all.

My guess is that Meraki has updated the MIB to include one or more new OID's that are specific to the MX68's.

If you believe you have a fix or a workaround for this issue, please let me know.

Swift packets!

Rick Schroeder

Find more posts tagged with

Accepted answers

mesverrum

I had this same problem this week as well. I ran a mibwalk on the device and saw similar issues. Seems like the developers at meraki intended for .0 to be interface 1, but that's not how snmp oids work so it's all screwed up.

All comments

mesverrum

markh_au

Hi @rschroeder

If you update the firmware of the MX68 to version MX15.13 or later and the issue should be resolved.

Mark

rschroeder

Thanks, Mark!

mathvigs

Hello @rschroeder

the upgrade of your meraki MX68 corrected your issue ?

rschroeder

Resolving that issue has become the responsibility of one of my friends, so I'm no longer worrying about it. Sorry. Not the answer you were hoping for, I know.

Swift Packets!

Rick Schroeder

tmn_m

I'm seeing this issue with MX67c models too. I updated the mib database on SW but that didn't fix the issue. So far Meraki has only stated the obvious that different models have different strings for the ports. It's irritating that I cant monitor wan interfaces at the moment. this does not occur with other model mx devices just the newer ones.

mesverrum

Have you tried updating to their latest RC firmware? I know that its fixed there for the models I run. It's just been a slow March toward getting everything upgraded past the bug