ASR9910 IOS-XR 6.3.3 CPU/MEM snmp OID

Dragoljub Spasojevic · ‎09-03-2018

It seems that in 6.3.3 are new OID for CPU/MEM usage.

ghost n9000 # snmpbulkwalk -c XXXXX -v 2c -t 10 -r 3 XXXXX system SNMPv2-MIB::sysDescr.0 = STRING: Cisco IOS XR Software (Cisco ASR9K Series), Version 6.3.3[Default]
Copyright (c) 2018 by Cisco Systems, Inc.
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.2390
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (40290) 0:06:42.90
SNMPv2-MIB::sysContact.0 = STRING: XXXXX
SNMPv2-MIB::sysName.0 = STRING: XXXXX
SNMPv2-MIB::sysLocation.0 = STRING: XXXXX
SNMPv2-MIB::sysServices.0 = INTEGER: 78
ghost n9000 # snmpbulkwalk -c XXXXX-v 2c -t 10 -r 3 XXXXX 1.3.6.1.2.1.47.1.1.1.1.7 | grep "module 0/"
SNMPv2-SMI::mib-2.47.1.1.1.1.7.15176092 = STRING: "module 0/6/1"
SNMPv2-SMI::mib-2.47.1.1.1.1.7.28927172 = STRING: "module 0/0/CPU0"
SNMPv2-SMI::mib-2.47.1.1.1.1.7.29992163 = STRING: "module 0/7/1"
SNMPv2-SMI::mib-2.47.1.1.1.1.7.36731525 = STRING: "module 0/RSP1/CPU0"
SNMPv2-SMI::mib-2.47.1.1.1.1.7.37425837 = STRING: "module 0/7/CPU0"
SNMPv2-SMI::mib-2.47.1.1.1.1.7.38645760 = STRING: "module 0/RSP0/CPU0"
SNMPv2-SMI::mib-2.47.1.1.1.1.7.49175796 = STRING: "module 0/6/CPU0"
ghost # snmpbulkwalk -c XXXXX -v 2c -t 10 -r 3 XXXXX 1.3.6.1.4.1.9.9.109.1.1.1.1.2
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.2 = No Such Instance currently exists at this OID

Same OID on 6.2.3 these OID's works perfect.

Aleksandar Vidakovic · ‎09-04-2018

hi Dragoljub,

it may be that reading from sysdb failed. There were some similar issues in the past. It would be the best to investigate this further through a TAC SR.

In general we recommend moving to Model Based Telemetry as opposed to polling via SNMP. Streaming telemetry not only performs better but also allows for monitoring of more parameters than supported by SNMP. If you didn't have a chance to see this Cisco Live talk, please try to find some time for it:

BRKSPG-2333 - Model-Driven Telemetry: The Foundation of Big Data Analytics (2017 Berlin)

/Aleksandar

Dragoljub Spasojevic · ‎09-04-2018

Hi Aleksandar,

I have upgraded to 6.4.2 and everything works fine. There is a problem with 6.3.3 definitely.