cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1273
Views
0
Helpful
1
Replies

Incorrect number formatting on Cisco Nexus 9396 SNMP

support
Level 1
Level 1

I have two different issues here.

1) The switch returning **bleep** information.
2) The NMS formatting it incorrectly (which may be at the direction of the MIB)

I have done the snmpget request in the same order as the screenshot from the NMS.

The snmpget isn't returning all of the information one would care about (not enough digits for precision) and the NMS is introducing a few extra decimal points.

[redacted]:~$ /usr/bin/snmpget -v3 -l authPriv -u [redacted] -a SHA -A [redacted] -x AES -X [redacted] [redacted] .1.3.6.1.4.1.9.9.91.1.1.1.1.4.300003522 .1.3.6.1.4.1.9.9.91.1.1.1.1.4.300003524 .1.3.6.1.4.1.9.9.91.1.1.1.1.4.300003527 .1.3.6.1.4.1.9.9.91.1.1.1.1.4.300003533 .1.3.6.1.4.1.9.9.91.1.1.1.1.4.300003534
iso.3.6.1.4.1.9.9.91.1.1.1.1.4.300003522 = INTEGER: 3
iso.3.6.1.4.1.9.9.91.1.1.1.1.4.300003524 = INTEGER: 15
iso.3.6.1.4.1.9.9.91.1.1.1.1.4.300003527 = INTEGER: 39
iso.3.6.1.4.1.9.9.91.1.1.1.1.4.300003533 = INTEGER: -6
iso.3.6.1.4.1.9.9.91.1.1.1.1.4.300003534 = INTEGER: -6



           SFP Detail Diagnostics Information (internal calibration)
  ----------------------------------------------------------------------------
                Current              Alarms                  Warnings
                Measurement     High        Low         High          Low
  ----------------------------------------------------------------------------
  Temperature   39.67 C       100.00 C    -50.00 C     85.00 C      -40.00 C
  Voltage        3.35 V         3.79 V      2.80 V      3.46 V        3.13 V
  Current       15.75 mA       90.00 mA     0.00 mA    85.00 mA       0.00 mA
  Tx Power      -6.10 dBm      -1.50 dBm  -10.50 dBm   -3.00 dBm     -9.03 dBm
  Rx Power      -6.12 dBm      -3.00 dBm  -26.98 dBm   -5.00 dBm    -23.97 dBm
  Transmit Fault Count = 0
  ----------------------------------------------------------------------------
  Note: ++  high-alarm; +  high-warning; --  low-alarm; -  low-warning


It's a rather simple SNMP config, so I don't see messing it up.


 
!Command: show running-config snmp
!Time: Mon Apr  1 10:09:48 2019

version 7.0(3)I2(3)
snmp-server contact FD-IX <support@fd-ix.com>
snmp-server location 01.201.b03 733 W. Henry St., Indianapolis, IN, 46225, USA [39.759731, -86.172487]
snmp-server user Admin network-operator auth sha [redacted] priv aes-128 [redacted] localizedkey
rmon event 1 log trap public description FATAL(1) owner PMON@FATAL
rmon event 2 log trap public description CRITICAL(2) owner PMON@CRITICAL
rmon event 3 log trap public description ERROR(3) owner PMON@ERROR
rmon event 4 log trap public description WARNING(4) owner PMON@WARNING
rmon event 5 log trap public description INFORMATION(5) owner PMON@INFO
snmp-server community [redacted] group network-operator
 
1 Reply 1

support
Level 1
Level 1

A 3064 I poll for the same interface has no issue at all.

[redacted]$ /usr/bin/snmpget -v2c -c [redacted] [redacted] .1.3.6.1.4.1.9.9.91.1.1.1.1.4.300003523 .1.3.6.1.4.1.9.9.91.1.1.1.1.4.300003524 .1.3.6.1.4.1.9.9.91.1.1.1.1.4.300003527 .1.3.6.1.4.1.9.9.91.1.1.1.1.4.300003533 .1.3.6.1.4.1.9.9.91.1.1.1.1.4.300003534
iso.3.6.1.4.1.9.9.91.1.1.1.1.4.300003523 = INTEGER: 3340
iso.3.6.1.4.1.9.9.91.1.1.1.1.4.300003524 = INTEGER: 22950
iso.3.6.1.4.1.9.9.91.1.1.1.1.4.300003527 = INTEGER: 35132
iso.3.6.1.4.1.9.9.91.1.1.1.1.4.300003533 = INTEGER: -10506
iso.3.6.1.4.1.9.9.91.1.1.1.1.4.300003534 = INTEGER: -6003