cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

SNMP: Ports schecking anomaly on MX68

Comes here often

SNMP: Ports schecking anomaly on MX68

Hello everyone 🙂 !

 

I have a question about snmpwalk to meraki device MX68.

 

I would like to check interface traffic, through my ports, however, these information with snmpwalk are different from that I have in the Meraki dashboard.

 

In the Meraki dashboard, as you can see below, we  have the port 1 and 11 connected and up.

 

MX68.png

 

(Port 1 and 11 are connected and we traffic on these interfaces.)

 

 

However, the feedback on the snmpwalk show us the "OperStatus" 1 and 11 as down whereas they are up on the dashboard.

 

 

IF-MIB::ifOperStatus.1 = INTEGER: down(2)

 

 

According to cisco MIB, ifOperStatus is the current operational state of the interface. If ifAdminStatus is down(2) then ifOperStatus should be down(2).

 

 

 


OID
 
1.3.6.1.2.1.2.2.1.8
 

Module
 
IF-MIB (CISCO)
 

Nom
 
ifOperStatus
 

Acces
 
readonly
 

Status
 
current
 

Description
 
The current operational state of the interface. The testing(3) state indicates that no operational packets can be passed. If ifAdminStatus is down(2) then ifOperStatus should be down(2). If ifAdminStatus is changed to up(1) then ifOperStatus should change to up(1) if the interface is ready to transmit and receive network traffic; it should change to dormant(5) if the interface is waiting for external actions (such as a serial line waiting for an incoming connection); it should remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state; it should remain in the notPresent(6) state if the interface has missing (typically, hardware) components.
 

Syntaxe
 
Enumeration (1-up, 2-down, 3-testing, 4-unknown, 5-dormant, 6-notPresent, 7-lowerLayerDown)
 

 

 

 

However, in my snmpwalk my ifAdminStatus is up but my ifOperStatus is down.

 

 

 

snmpwalk -v 3 -u 'XXX' -x des -X 'XXX' -A 'XXX' -a sha -l authpriv  AA.BB.CC.DD

 

 

IF-MIB::ifAdminStatus.1 = INTEGER: up(1)

IF-MIB::ifAdminStatus.2 = INTEGER: up(1)

IF-MIB::ifAdminStatus.3 = INTEGER: up(1)

IF-MIB::ifAdminStatus.4 = INTEGER: up(1)

IF-MIB::ifAdminStatus.5 = INTEGER: up(1)

IF-MIB::ifAdminStatus.6 = INTEGER: up(1)

IF-MIB::ifAdminStatus.7 = INTEGER: up(1)

IF-MIB::ifAdminStatus.8 = INTEGER: up(1)

IF-MIB::ifAdminStatus.9 = INTEGER: up(1)

IF-MIB::ifAdminStatus.10 = INTEGER: up(1)

IF-MIB::ifAdminStatus.11 = INTEGER: up(1)

IF-MIB::ifAdminStatus.12 = INTEGER: up(1)

IF-MIB::ifOperStatus.1 = INTEGER: down(2)

IF-MIB::ifOperStatus.2 = INTEGER: down(2)

IF-MIB::ifOperStatus.3 = INTEGER: down(2)

IF-MIB::ifOperStatus.4 = INTEGER: down(2)

IF-MIB::ifOperStatus.5 = INTEGER: down(2)

IF-MIB::ifOperStatus.6 = INTEGER: down(2)

IF-MIB::ifOperStatus.7 = INTEGER: down(2)

IF-MIB::ifOperStatus.8 = INTEGER: down(2)

IF-MIB::ifOperStatus.9 = INTEGER: down(2)

IF-MIB::ifOperStatus.10 = INTEGER: up(1)

IF-MIB::ifOperStatus.11 = INTEGER: down(2)

IF-MIB::ifOperStatus.12 = INTEGER: down(2)

 

 

Moreover, we can some traffic through these interfaces:

.

.

IF-MIB::ifInOctets.1 = Counter32: 4267233788

IF-MIB::ifInOctets.2 = Counter32: 0

IF-MIB::ifInOctets.3 = Counter32: 0

IF-MIB::ifInOctets.4 = Counter32: 0

IF-MIB::ifInOctets.5 = Counter32: 0

IF-MIB::ifInOctets.6 = Counter32: 0

IF-MIB::ifInOctets.7 = Counter32: 0

IF-MIB::ifInOctets.8 = Counter32: 0

IF-MIB::ifInOctets.9 = Counter32: 952818

IF-MIB::ifInOctets.10 = Counter32: 0

IF-MIB::ifInOctets.11 = Counter32: 3309773612

IF-MIB::ifInOctets.12 = Counter32: 0

IF-MIB::ifInUcastPkts.1 = Counter32: 316592390

IF-MIB::ifInUcastPkts.2 = Counter32: 0

IF-MIB::ifInUcastPkts.3 = Counter32: 0

IF-MIB::ifInUcastPkts.4 = Counter32: 0

IF-MIB::ifInUcastPkts.5 = Counter32: 0

IF-MIB::ifInUcastPkts.6 = Counter32: 0

IF-MIB::ifInUcastPkts.7 = Counter32: 0

IF-MIB::ifInUcastPkts.8 = Counter32: 0

IF-MIB::ifInUcastPkts.9 = Counter32: 2829

IF-MIB::ifInUcastPkts.10 = Counter32: 0

IF-MIB::ifInUcastPkts.11 = Counter32: 390020574

IF-MIB::ifInUcastPkts.12 = Counter32: 0

IF-MIB::ifInNUcastPkts.1 = Counter32: 0

IF-MIB::ifInNUcastPkts.2 = Counter32: 0

IF-MIB::ifInNUcastPkts.3 = Counter32: 0

IF-MIB::ifInNUcastPkts.4 = Counter32: 0

IF-MIB::ifInNUcastPkts.5 = Counter32: 0

IF-MIB::ifInNUcastPkts.6 = Counter32: 0

IF-MIB::ifInNUcastPkts.7 = Counter32: 0

IF-MIB::ifInNUcastPkts.8 = Counter32: 0

IF-MIB::ifInNUcastPkts.9 = Counter32: 0

IF-MIB::ifInNUcastPkts.10 = Counter32: 0

IF-MIB::ifInNUcastPkts.11 = Counter32: 0

IF-MIB::ifInNUcastPkts.12 = Counter32:

 

 

Do you know why we have this please?

 

 

 Regards,

 

NicoSnmp

4 REPLIES 4
Kind of a big deal

Re: SNMP: Ports schecking anomaly on MX68

I don't have an MX68 to check on handy, but my MX64 on my desk reports correctly:

 

image.png

 

IF-MIB::ifAdminStatus.1 = INTEGER: up(1)
IF-MIB::ifAdminStatus.2 = INTEGER: up(1)
IF-MIB::ifAdminStatus.3 = INTEGER: up(1)
IF-MIB::ifAdminStatus.4 = INTEGER: up(1)
IF-MIB::ifAdminStatus.5 = INTEGER: up(1)
IF-MIB::ifOperStatus.1 = INTEGER: up(1)
IF-MIB::ifOperStatus.2 = INTEGER: up(1)
IF-MIB::ifOperStatus.3 = INTEGER: down(2)
IF-MIB::ifOperStatus.4 = INTEGER: down(2)
IF-MIB::ifOperStatus.5 = INTEGER: up(1)

...

IF-MIB::ifName.1 = STRING: wan1
IF-MIB::ifName.2 = STRING: lan1
IF-MIB::ifName.3 = STRING: lan2
IF-MIB::ifName.4 = STRING: lan3
IF-MIB::ifName.5 = STRING: lan4

 

I would call support and open a case. What you're describing sounds like a bug to me. 

Comes here often

Re: SNMP: Ports schecking anomaly on MX68

I have the same issue with all MX67C's, while all MX84's are responding correctly.

 

MX67C port 1 (WAN)
31/07/2019 14:11:14 (9 ms) : Custom OID 1.3.6.1.2.1.2.2.1.8.1
31/07/2019 14:11:14 (382 ms) : SNMP Datatype: ASN_INTEGER
31/07/2019 14:11:14 (386 ms) : Value: 1

 

MX67C port 2 (LAN, trunked)

31/07/2019 14:11:19 (9 ms) : Custom OID 1.3.6.1.2.1.2.2.1.8.2
31/07/2019 14:11:20 (382 ms) : SNMP Datatype: ASN_INTEGER
31/07/2019 14:11:20 (386 ms) : Value: 2

 

Is this a known issue?

Comes here often

Re: SNMP: Ports schecking anomaly on MX68

I contacted support and they said the following:

 


The issue for the SNMP ifOperstatus has been resolved in beta firmware version, 15.13 or higher.

 

"Corrected an issue that resulted in the ifOperStatus being reported incorrectly on MX67(C,W) and MX68(W,CW) appliance"

 

The following document may be helpful to you if you wish to upgrade to the latest beta:

https://documentation.meraki.com/zGeneral_Administration/Firmware_Upgrades/Managing_Firmware_Upgrade...


New here

Re: SNMP: Ports schecking anomaly on MX68


@Nick4 wrote:

I contacted support and they said the following:

 


The issue for the SNMP ifOperstatus has been resolved in beta firmware version, 15.13 or higher.

 

"Corrected an issue that resulted in the ifOperStatus being reported incorrectly on MX67(C,W) and MX68(W,CW) appliance"

 

The following document may be helpful to you if you wish to upgrade to the latest beta:

https://documentation.meraki.com/zGeneral_Administration/Firmware_Upgrades/google street view Managing_Firmware_Upgrade



I have the same problem, thank you so much! only this helped me

Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.