Cisco – How to read optical transmit power via SNMP on Cisco ASR9k

ciscocisco-asrcisco-ios-xrsnmp

I am looking to read optical transmit and recieve power of XFPs in our ASR9k. The MIB used should be "CISCO-ENTITY-SENSOR-MIB" which is 1.3.6.1.4.1.9.9.91 and occording the ASR9000 documentation, this is available on ASR9k's:
http://www.cisco.com/en/US/docs/routers/asr9000/mib/guide/asr9kmib3.html#wp2293135
If you scroll up, you will see that the MIB is in the supported list.

So, my question: am I missing something and should this information be available to SNMP, or is the Cisco documentation wrong here?
And if it is available, how can I get to this information?

However show snmp mib object-name | i 1.3.6.1.4.1.9.9.91 gives me nothing
neither does show snmp mib object-name | i Sensor

RP/0/RSP0/CPU0:router#show snmp mib object-name | i 1.3.6.1.4.1.9.9.91
Thu May 16 09:08:01.679 CET
RP/0/RSP0/CPU0:router#show snmp mib
object-name | i [sS]ensor Thu May 16 09:08:19.017 CET

The version:

RP/0/RSP0/CPU0:router#show version Thu May 16 09:07:14.437 CET

Cisco IOS XR Software, Version 4.2.3[Default] Copyright (c) 2012 by
Cisco Systems, Inc.

ROM: System Bootstrap, Version 1.06(20120210:003513) [ASR9K ROMMON],

cn-asd-kl-cr15 uptime is 23 weeks, 3 days, 1 hour, 12 minutes System
image file is
"bootflash:disk0/asr9k-os-mbi-4.2.3/0x100000/mbiasr9k-rp.vm"

cisco ASR9K Series (MPC8641D) processor with 4194304K bytes of memory.
MPC8641D processor at 1333MHz, Revision 2.2 ASR 9006 AC Chassis with
PEM Version 2

And the XFP I am trying to read:

RP/0/RSP0/CPU0:router#show inventory NAME: "module 0/0/CPU0", DESCR:
"8-Port 10GE Low Queue Line Card, Requires XFPs" PID: A9K-8T-L, VID:
V04, SN: FOC1641N6EH

NAME: "module mau TenGigE0/0/CPU0/0", DESCR: "Multirate 10GBASE-LR and
OC-192/STM-64 SR-1 XFP, SMF" PID: XFP-10GLR-OC192SR , VID: V04 , SN:
SPC1623090S

To compare, this is the output from our 7606:

7606#show ver Cisco IOS Software, c7600s72033_rp Software
(c7600s72033_rp-ADVIPSERVICESK9-M), Version 15.1(3)S4, RELEASE
SOFTWARE (fc2)

7606#show snmp mib | i Sensor entPhySensorType entPhySensorScale
entPhySensorPrecision entPhySensorValue entPhySensorOperStatus
entPhySensorUnitsDisplay entPhySensorValueTimeStamp
entPhySensorValueUpdateRate entSensorType entSensorScale
entSensorPrecision entSensorValue entSensorStatus
entSensorValueTimeStamp entSensorValueUpdateRate
entSensorMeasuredEntity entSensorThresholdSeverity
entSensorThresholdRelation entSensorThresholdValue
entSensorThresholdEvaluation entSensorThresholdNotificationEnable

Best Answer

Have you tried walking the MIB/OIDs in question from a management station? After having spent a lot of time w/firmware QA, I've noticed things like show commands are likely to not display correct info, even when the OIDs are poll-able. I recommend using and knowing Net-SNMP tools and utils as debug before trying to poll the information in cacti, observium, etc.

e.g. snmpwalk -v2c -c <community> <routername> 1.3.6.1.4.1.9.9.91 will say "No Such Object available on this agent at this OID" if it's not there

Walking 1.3.6.1.4.1.9 on my IOS-XE box gives a lot (I just need to add the MIBs for description). Then I have something to work with (including other gems that might benefit me for monitoring)

snmpwalk -v2c -c <community> <routername> 1.3.6.1.4.1.9

Check out the MIBs available for 4.2.x on the ASR 9000 @:

ftp://ftp.cisco.com/pub/mibs/supportlists/asr9000/asr9000-supportlist.html#Supported_and_Verified_MIBs_XE_4_2_X

That link says that the CISCO-ENTITY-SENSOR-MIB is available, and hasn't been updated since 2007. Edit: it appears that the asr9k-mgbl-p.pie package was not available on the router, as mapped in the ASR9000 MIB list above.

Supplemental info:

Cisco's MIB Locator tool is IOS-only, so check out the directories above above the asr9000 on the FTP link for more info.

Tool: http://tools.cisco.com/ITDIT/MIBS/MainServlet

SNMP ftp dir: ftp://ftp.cisco.com/pub/mibs/supportlists/

For more information on loading MIBs: http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00800b4cee.shtml

A really good Cisco SNMP links page: http://www.cisco.com/en/US/tech/tk648/tk362/tk605/tsd_technology_support_sub-protocol_home.html

SSH Key Generation

ssh-keygen -b 1024 -t rsa -f myrouter_sshkey

This will generate myrouter_sshkey and myrouter_sshkey.pub. When you look into the public key file, it looks like followings:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgQDR/ggtknqBZ50pIAyzw0E93wfu2EsGLnft/uF6N4ov6Dsp1H7yoC5ssE+yOcrWHeDEQnD0BsNCLZPW+ye7jjYeE+CUrOINpi04PtD+zx95knpAFnREMV7w8fJ9c7/SMb2L4Jk6KlmTcqtM+lUgrxEnCD7Z1kpCUzkP+0D0N/RG2Q== foo@bar.com

We only need the second part of the public key file separated by space for base64 decoding.

'de'code SSH public key with base64.

cut -d" " -f2 myrouter_sshkey.pub | base64 -d > myrouter_sshkey.pub.b64

This generated file is binary format and can be imported to ASR router.
Note that if you're using MAC, use -D option instead.

Upload 'de'coded public key to the router.

RP/0/RSP0/CPU0:ASR9K#copy ftp:myrouter_sshkey.pub.b64 harddisk:/

I used ftp but you can use tftp or else.

import public key to a router user.

RP/0/RSP0/CPU0:ASR9K#admin
RP/0/RSP0/CPU0:ASR9K(admin)#crypto key import authentication rsa username admin

Verify key import

RP/0/RSP0/CPU0:ASR9K(admin)#sh crypto key authentication rsa all    
Key label: admin
Type     : RSA public key authentication
Size     : 1024
Imported : 18:39:54 UTC Thu Jul 03 2014
Data     :
 {{intentionally removed}}

Login test

ssh -oIdentitiesOnly=yes -i myrouter_sshkey ${myrouter}

Note that if you have more than one ssh keys, -oIdentitiesOnly=yes must be given or your connection will fail. SSH tries every keys sequentially until one of the keys is accepted or finally falls back to password authentication if applicable. SSH server may allow this multiple key trials even if the first key trial fails. Unfortunately ASR router seems not to allow this. If the first tried key fails, it disconnect the session. To explicitly specify the key you use, give -oIdentitiesOnly=yes option to ssh.

Cisco – SNMP MIBs for IPSLA ICMP Echo

I found out the MIBs. For the IPSLA types, udp jitter, icmp echo and icmp path-echo, the RTT and connection status are stored in the rttMonLatestRttOperEntry table

rttMonLatestRttOperCompletionTime has the average RTT
rttMonLatestRttOperSense has the connection status (ok/disconected etc.)
- List of values for RttResponseSense