Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

PRI monitoring problem with SNMP

Hello

I'm having some problems with PRI monitoring.

I'm using cpmDS1ActiveDS0 MIB on a 3800 VoIP gateway with 4 PRI (2x2) (IOS 12.4(4)T1)

1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.0 - I can see PRI 0/0/0 total number of calls

1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.1 - I can see PRI 0/0/1 total number of calls

1.3.6.1.4.1.9.10.19.1.1.9.1.3.1.0 - Error

1.3.6.1.4.1.9.10.19.1.1.9.1.3.1.1 - Error

1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.0.x - Error

1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.1.x - Error

The PRIs that we want to see are 0/1/0 e 0/1/1...... (bad luck!)

Do I need to make some special configuration on the Router?

7 REPLIES
Cisco Employee

Re: PRI monitoring problem with SNMP

The errors are most likely due to the fact that the 3800 or other ISR's do not support the CISCO-POP-MGMT-MIB.

The CISCO-POP-MGMT-MIB was designed/intended for dial platform such as AS5xxx. It will have some support for the 26xx/36xx platforms as these

platforms have dial functions as well.

The ISRs (3825) have 3-tuple representation of interfaces (slot.subslot.port), which is different from the older slot.port indexing. The MIB does not support this 3-tuple numbering and hence you

will see that ISRs don't support CISCO-POP-MGMT-MIB.

you might want to look at the CISCO-VOICE-DIAL-CONTROL-MIB and the DIAL-CONTROL-MIB as alternatives

New Member

PRI monitoring problem with SNMP

Hi David, while your answer is correct, that the Cisco-POP-MGMT-MIB does not support slot.port.subslot. when is Cisco going to fix this in their ISR G1 and G2? the CISCO-VOICE-DIAL-CONTROL-MIB and the DIAL-CONTROL-MIB do not provide an slot.subslot.port to provide monitoring for Local/LD/other usage types. Even when using tying this to the expression-MID does not provide an "Standard" way to monitor PRI's in ISR's. Seems very short sided of Cisco considering the ISR are positioned highly for the Cisco UC infrastructure.

New Member

Re: PRI monitoring problem with SNMP

Were you able to get the results back from the CISCO-VOICE-DIAL-CONTROL-MIB and the DIAL-CONTROL-MIB MIBs?  I have a 3845 as well with 8 PRI and the POP-MGMT MIB is not working very well for us.

Thanks,

BC

New Member

Re: PRI monitoring problem with SNMP

I'm running into the same issue.  What's nice about the POP MIB is that it gives you DS0 utilization on an DS1 basis, so you can verify load distribution and perform proper capacity planning.  As others have found, though, it only works with VWIC's in slot 0/0.  The only similar information I can pull using the CISCO-VOICE-DIAL-CONTROL-MIB and the DIAL-CONTROL-MIB MIBs is total active DS0's (1.3.6.1.4.1.9.9.63.1.3.3.0).  Unfortunately this gives you an aggregate total across all the PRI's in the chassis as opposed to a breakdown per PRI.  This is the same data as the older 'cpmActiveDS0s' MIB; it's just under a new OID.

Anyone have any luck collecting DS0 utilization on a per PRI basis?

Thanks,

JT

New Member

Re: PRI monitoring problem with SNMP on ISR 38XX

Have you had any responses to this issue ?

I am running into exactly the same issue and have tried everything I can find to get these individual PRI (count of channels/lines in use) statistics.

Just for the record, here are some of the SNMP OIDs that I have tried (the ISRs do respond to them, only thing is, the data they send back is mostly rubbish...) the output below is from two separate routers, with different versions of IOS running (which is shown in the sysdescr response):

Note that the query in red in the second router was responded to with a valid response in the FIRST router...

All of these OIDs have been suggested at various sites online as useable SNMP OIDs for the ISR, but at other sites, they are suggested to be faulty.  I have found no definitive statement for ways to get these stats successfully on the ISR platform (which amazes me.)  Output below is using net-snmp to collect the stats.

I welcome any suggestions as to how this can be done reliably for the ISR, and what IOS versions WILL work.  (since I am getting way different reponses to the same OIDs on the two versions below).

You'll see that for the second (DC) router below, the values are always Zero.

Yet I can guarantee that the ACTUAL stats are NEVER zero during the time period queried.

Timestamp: 2010-12-27_13:56:31.73

C:\usr\share\snmp\mibs>snmptranslate -On CISCO-POP-MGMT-MIB::cpmActiveDS0s.0
.1.3.6.1.4.1.9.10.19.1.1.4.0

C:\usr\share\snmp\mibs>snmptranslate -On CISCO-POP-MGMT-MIB::cpmDS1ActiveDS0s.0.0
.1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.0

C:\usr\share\snmp\mibs>snmptranslate -On CISCO-POP-MGMT-MIB::cpmISDNCfgBChannelsInUse.0
.1.3.6.1.4.1.9.10.19.1.1.3.0

C:\usr\share\snmp\mibs>snmptranslate -On CISCO-VOICE-DIAL-CONTROL-MIB::cvCallActiveDS0s.0
.1.3.6.1.4.1.9.9.63.1.3.3.0

C:\usr\share\snmp\mibs>snmptranslate -On ISDN-MIB::isdnBearerOperStatus.32
.1.3.6.1.2.1.10.20.1.2.1.1.2.32

From ROUTER2 - HQ:
SNMPv2-MIB::sysDescr.0 = STRING: Cisco IOS Software,
3800 Software (C3825-ADVIPSERVICESK9-M),
Version 12.4(15)T8, RELEASE SOFTWARE (fc3)

CISCO-POP-MGMT-MIB::cpmActiveDS0s.0 = Gauge32: 14
CISCO-POP-MGMT-MIB::cpmDS1ActiveDS0s.0.0 = Gauge32: 14
CISCO-POP-MGMT-MIB::cpmISDNCfgBChannelsInUse.0 = Gauge32: 7
CISCO-VOICE-DIAL-CONTROL-MIB::cvCallActiveDS0s.0 = Gauge32: 7 interfaces
ISDN-MIB::isdnBearerOperStatus.32 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.33 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.34 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.35 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.36 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.37 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.38 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.39 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.40 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.41 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.42 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.43 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.44 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.45 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.46 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.47 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.48 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.49 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.50 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.51 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.52 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.53 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.54 = INTEGER: idle(1)

From ROUTER2 - DC:
SNMPv2-MIB::sysDescr.0 = STRING: Cisco IOS Software,
3800 Software (C3825-ADVIPSERVICESK9-M),
Version 12.4(18), RELEASE SOFTWARE (fc1)

CISCO-POP-MGMT-MIB::cpmActiveDS0s.0 = Gauge32: 0
CISCO-POP-MGMT-MIB::cpmDS1ActiveDS0s.0.0 = Gauge32: 0
CISCO-POP-MGMT-MIB::cpmISDNCfgBChannelsInUse.0 = Gauge32: 0
CISCO-VOICE-DIAL-CONTROL-MIB::cvCallActiveDS0s.0 = No Such Object available on this agent at this OID
ISDN-MIB::isdnBearerOperStatus.32 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.33 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.34 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.35 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.36 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.37 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.38 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.39 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.40 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.41 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.42 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.43 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.44 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.45 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.46 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.47 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.48 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.49 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.50 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.51 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.52 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.53 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.54 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.81 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.82 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.83 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.84 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.85 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.86 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.87 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.88 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.89 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.90 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.91 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.92 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.93 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.94 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.95 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.96 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.97 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.98 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.99 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.100 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.101 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.102 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.103 = INTEGER: idle(1)

Timestamp: 2010-12-27_13:56:35.02

New Member

Re: PRI monitoring problem with SNMP on ISR 38XX

This is probably a result of your VG registered as an MGCP endpoint instead of H323

Did you find a workaround?  I would be interested in the results via SNMP monitoring the CCM about your registered 38XX

New Member

Re: PRI monitoring problem with SNMP on ISR 38XX

Realize you were responding to another post, but in our case we dealing strictly with h.323 gateways.We still do not have a workaround for our gen 1 or gen 2 ISR's.

6540
Views
15
Helpful
7
Replies
CreatePlease login to create content