Monitoring ISDN channel usage over SNMP on ISR4321

[Tom Ribbens]

Hi,

We recently installed ISR4321 voice gateways. They have 2 ISDN PRI E1 interfaces provided by the NIM-2MFT-T1/E1 - T1/E1 Serial Module.

We have those devices included in our PRTG monitoring system. Now I wanted to add sensors that show the channel usage of the ISDN lines. Googling for the SNMP string, I found this one: http://snmp.cloudapps.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate=Translate&objectInput=1.3.6.1.4.1.9.10.19.1.1.4#oidContent

Unfortunately, that does not work. As does many others I have tried that might have seemed relevant. I now believe the feature is completely changed in this ISR family compared to previous ISR families.

In case it's important, we're running isr4300-universalk9.03.16.06.S.155-3.S6-ext.SPA.bin

Kind regards,

Tom

[Georgios Fotiadis]

What does

snmpwalk -v2c -c <community> <isr_ip> 1.3.6.1.4.1.9.10.19.1.1.9

return?

[Tom Ribbens]

I don't have that snmpwalk utility on a network that can directly access the device, but when I use the Paessler snmp tool, I simply get nothing.

----------------------- New Test -----------------------
Paessler SNMP Tester 5.1.3
9/01/2018 13:21:48 (4 ms) : Device: 10.25.0.19
9/01/2018 13:21:48 (5 ms) : SNMP V2c
9/01/2018 13:21:48 (7 ms) : Walk 1.3.6.1.4.1.9.10.19.1.1.9

When I try something else, I do get information back:

----------------------- New Test -----------------------
Paessler SNMP Tester 5.1.3
9/01/2018 13:23:28 (6 ms) : Device: 10.25.0.19
9/01/2018 13:23:28 (10 ms) : SNMP V2c
9/01/2018 13:23:28 (13 ms) : Walk 1.3.6.1.2.1.1.3
9/01/2018 13:23:28 (23 ms) : 1.3.6.1.2.1.1.3.0 = "187295866"

[Georgios Fotiadis]

I suppose the output you sent if when asking for a specific OID.

Can you have the whole tree (from root) returned to you? There, you should be able to see the required OIDs. Asking with root 1.3.6.1.4.1.9.10.19.1.1.9 should return you info regarding the PRI lines.

[Tom Ribbens]

The output should be that of a walk, so the whole tree:

----------------------- New Test -----------------------
Paessler SNMP Tester 5.1.3
9/01/2018 14:53:13 (6 ms) : Device: 10.25.0.19
9/01/2018 14:53:13 (10 ms) : SNMP V2c
9/01/2018 14:53:13 (13 ms) : Walk 1.3.6.1.4.1.9.10.19.1.1.9

----------------------- New Test -----------------------
Paessler SNMP Tester 5.1.3
9/01/2018 14:53:32 (8 ms) : Device: 10.25.0.19
9/01/2018 14:53:32 (11 ms) : SNMP V2c
9/01/2018 14:53:32 (15 ms) : Walk 1.3.6.1.2.1.1
9/01/2018 14:53:32 (26 ms) : 1.3.6.1.2.1.1.1.0 = "Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(3)S6, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2017 by Cisco Systems, Inc.
Compiled Mon 24-Jul-17 20:26 by mcpre"
9/01/2018 14:53:32 (38 ms) : 1.3.6.1.2.1.1.2.0 = "1.3.6.1.4.1.9.1.2093"
9/01/2018 14:53:32 (50 ms) : 1.3.6.1.2.1.1.3.0 = "187836263"
9/01/2018 14:53:32 (61 ms) : 1.3.6.1.2.1.1.4.0 = ""
9/01/2018 14:53:32 (71 ms) : 1.3.6.1.2.1.1.5.0 = "tel-cube03.mechelen.intra"
9/01/2018 14:53:32 (83 ms) : 1.3.6.1.2.1.1.6.0 = ""
9/01/2018 14:53:32 (93 ms) : 1.3.6.1.2.1.1.7.0 = "78"
9/01/2018 14:53:32 (104 ms) : 1.3.6.1.2.1.1.8.0 = "0"

As you can see from this output, it does actually produce a tree of answers when querying it. 1.3.6.1.4.1.9.10.19.1.1.9 however produces no results.

[Tom Ribbens]

The output should be that of a walk, so the whole tree:

----------------------- New Test -----------------------
Paessler SNMP Tester 5.1.3
9/01/2018 14:53:13 (6 ms) : Device: 10.25.0.19
9/01/2018 14:53:13 (10 ms) : SNMP V2c
9/01/2018 14:53:13 (13 ms) : Walk 1.3.6.1.4.1.9.10.19.1.1.9

----------------------- New Test -----------------------
Paessler SNMP Tester 5.1.3
9/01/2018 14:53:32 (8 ms) : Device: 10.25.0.19
9/01/2018 14:53:32 (11 ms) : SNMP V2c
9/01/2018 14:53:32 (15 ms) : Walk 1.3.6.1.2.1.1
9/01/2018 14:53:32 (26 ms) : 1.3.6.1.2.1.1.1.0 = "Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(3)S6, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2017 by Cisco Systems, Inc.
Compiled Mon 24-Jul-17 20:26 by mcpre"
9/01/2018 14:53:32 (38 ms) : 1.3.6.1.2.1.1.2.0 = "1.3.6.1.4.1.9.1.2093"
9/01/2018 14:53:32 (50 ms) : 1.3.6.1.2.1.1.3.0 = "187836263"
9/01/2018 14:53:32 (61 ms) : 1.3.6.1.2.1.1.4.0 = ""
9/01/2018 14:53:32 (71 ms) : 1.3.6.1.2.1.1.5.0 = "hostname redacted"
9/01/2018 14:53:32 (83 ms) : 1.3.6.1.2.1.1.6.0 = ""
9/01/2018 14:53:32 (93 ms) : 1.3.6.1.2.1.1.7.0 = "78"
9/01/2018 14:53:32 (104 ms) : 1.3.6.1.2.1.1.8.0 = "0"

As you can see from this output, it does actually produce a tree of answers when querying it. 1.3.6.1.4.1.9.10.19.1.1.9 however produces no results.

[Georgios Fotiadis]

Can you attach (as file) the complete OID tree?

[Tom Ribbens]

Attached should be the output of this command:

 snmpwalk.exe -v 2c -c REDACTED 10.25.0.19 1 > full-snmp.txt

[Georgios Fotiadis]

Indeed, the OID is not there. Alternatively, you can implement a script to login to the router and get the value that you want by executing "show voice call status" or sth.

[vincent.morton]

Tom,

Did you ever find the OID for this? I've got the same problem trying to monitor a 4321

Vincent