[mrtg] Re: Monitoring Cisco H.323 VOIP gateways

Jerry Heidtke jheidtke at fmlh.edu
Thu Jan 23 00:29:01 MET 2003


Thanks Bob, but I'm not the one looking for the information on how to track
number of channels on the 26xx. I'm already tracking this successfully on a
5350 using the OID I listed.

However, my application is a little different than Dave's. I am tracking
B-channel usage on a remote access dial-in server fed by multiple PRI lines.
Dave wants to track B-channel usage on a VOIP gateway. The principle is the
same however; if the device supports CISCO-POP-MGMT-MIB the OID I use should
also work for Dave. This is not a table entry, just a regular gauge.

A couple other OIDs in this MIB that might work are:

cpmISDNCfgBChanInUseForAnalog
.1.3.6.1.4.1.9.10.19.1.1.2.0
The number of configured ISDN B-Channels that are
 currently occupied by analog calls.

cpmISDNCfgBChannelsInUse
.1.3.6.1.4.1.9.10.19.1.1.3.0
The number of configured ISDN B-Channels that are
 currently occupied by both Digital and Analog calls.

cpmPPPCalls
.1.3.6.1.4.1.9.10.19.1.1.5.0
The current number of active PPP calls received 
 by the managed device

cpmV120Calls
.1.3.6.1.4.1.9.10.19.1.1.6.0
The current number of active V.120 calls received 
 by the managed device

cpmV110Calls
.1.3.6.1.4.1.9.10.19.1.1.7.0
The current number of active V.110 calls received 
 by the managed device

There's also a table called cpmDS1DS0UsageTable, which has values broken
down by individual DS1 interfaces. For example, cpmDS1ActiveDS0s
(.1.3.6.1.4.1.9.10.19.1.1.9.1.3.3.x, where x is the DS1 number starting at
0) shows the number of B-Channels in use on each PRI. I just noticed that
cpmDS1ActiveDS0sHighWaterMark (.1.3.6.1.4.1.9.10.19.1.1.9.1.4.3.x) actually
gives the maximum number of channels that have ever (since last reset) been
used on each DS1, while cpmActiveDS0sHighWaterMark
(.1.3.6.1.4.1.9.10.19.1.1.8.0), which should be the aggregate of all DS1's,
doesn't work. Probably some bug in the agent.

Here's a section of my config. Note that the Max. Users number I have in
there doesn't work; but no one ever asked to have it fixed...

Unscaled[_]: 
WithPeak[_]: ymw
Suppress[_]: 
Options[_]: gauge, growright, nopercent, integer
MaxBytes[_]: 100
ShortLegend[_]: Users
YLegend[_]: Users
LegendI[_]: Act. Users:
LegendO[_]: Max. Users:
Legend1[_]: Active and Maximum Users
Legend2[_]: Active and Maximum Users
Legend3[_]: Maximum Act. Users
Legend4[_]: Maximum Max. Users

Target[ras1-as5350_Users]:
.1.3.6.1.4.1.9.10.19.1.1.4.0&.1.3.6.1.4.1.9.10.19.1.1.8.0:xx at x.x.x.x
Title[ras1-as5350_Users]: ras1-as5350 Users
PageTop[ras1-as5350_Users]: <H1>ras1-as5350 Users</H1>

-----Original Message-----
From: Robert Holley [mailto:rholley at cisco.com] 
Sent: Wednesday, January 22, 2003 4:16 PM
To: Jerry Heidtke; 'Grabowski, David'; mrtg at list.ee.ethz.ch
Subject: RE: [mrtg] Re: Monitoring Cisco H.323 VOIP gateways


Jerry,

The CISCO-POP-MGMT-MIB is supported in V1 and V2 format for certain IOS
releases on the 26xx platform.

However, in order to access the information, you would have to look into a
table using three indexes (cpmDS1SlotIndex, cpmDS1PortIndex,
cpmChannelIndex);

The below information looks like it might give you utilization information
for a single ds0.

As far as summing them up with MRTG, I'd be interested in seeing the cfg
file (assuming this works). It may require some pre processing before
sending it to MRTG.


-- cpmDS0Usage

cpmDS0UsageTable OBJECT-TYPE
    SYNTAX SEQUENCE OF CpmDS0UsageEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
        "The DS0 usage table is for hardware and software
         objects not used as interfaces, and not covered in
         rfc1213.  These objects include analog calls coming
         over ISDN, Channelized T1, and Channelized E1.  This
         table is created for every DS1 line in the device."
    ::= { cpmDS0Usage 1 }

cpmDS0UsageEntry OBJECT-TYPE
    SYNTAX CpmDS0UsageEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
        "An entry in the DS0 Usage table."
    INDEX {cpmDS1SlotIndex, cpmDS1PortIndex, cpmChannelIndex }
    ::= { cpmDS0UsageTable 1 }

CpmDS0UsageEntry ::= SEQUENCE {
    cpmDS1SlotIndex Integer32,
    cpmDS1PortIndex Integer32,
    cpmChannelIndex Integer32,
    cpmConfiguredType INTEGER,
    cpmDS0CallType INTEGER,
    cpmL2Encapsulation INTEGER,
    cpmCallCount Counter32,
    cpmTimeInUse TimeTicks,
    cpmInOctets Counter32,
    cpmOutOctets Counter32,
    cpmInPackets Counter32,
    cpmOutPackets Counter32,
    cpmAssociatedInterface InterfaceIndexOrZero
    }

cpmDS1SlotIndex OBJECT-TYPE
    SYNTAX  Integer32
    MAX-ACCESS  not-accessible
    STATUS current
    DESCRIPTION
        "The slot index indicates the slot number on the
         device where the DS1 card resides."
    ::= { cpmDS0UsageEntry 1 }

cpmDS1PortIndex OBJECT-TYPE
    SYNTAX  Integer32
    MAX-ACCESS  not-accessible
    STATUS current
    DESCRIPTION
        "The port index indicates the port number of a
         specific DS1 on the DS1 card in the slot"
    ::= { cpmDS0UsageEntry 2 }

cpmChannelIndex OBJECT-TYPE
    SYNTAX  Integer32
    MAX-ACCESS  not-accessible
    STATUS current
    DESCRIPTION
        "The channel index that distinguishes the DS0 timeslot
         of the DS1 port.  The range of the channel index is based
         on the number of T1/E1 channels: 1-24(T1) and 1-31(E1)."
    ::= { cpmDS0UsageEntry 3 }

***************
***************
Is this what your looking for....
***************
***************

cpmTimeInUse OBJECT-TYPE
    SYNTAX TimeTicks
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "The amount of time that this DS0 has been in use.
         This is computed by summing up the call durations
         of all past calls that have occupied this DS0."
    ::= { cpmDS0UsageEntry 8 }


regards
Bob


Confidentiality Notice: This e-mail message, including any attachments, is 
for the sole use of the intended recipient(s) and may contain confidential 
and privileged information.  Any unauthorized review, use, disclosure or 
distribution is prohibited.  If you are not the intended recipient, please 
contact the sender by reply e-mail and destroy all copies of the original 
message.


--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi



More information about the mrtg mailing list