[mrtg] Re: Cisco 3810

Daniel J McDonald dmcdonald at digicontech.com
Fri Jul 27 21:33:56 MEST 2001


>Does anyone have a clue what I might be able to monitor on a 3810 with 2
FXO cards >an Ethernet Port and a Frame Relay WAN Port?

>I figured out the ETH port and the Frame ports but really want to know
about the
>FXO cards. Is there any way to monitor calls or throughput on these cards?

Calls, yes.  Throughput?  well, it's not really an interface, it's a net
consumer of traffic, but that's hard to measure due to the way it is
recorded.

You can pull stats from the DIAL-CONTROL-MIB.  Note that this mib will only
give you information per dial-peer, not per port (so if you have multiple
dial-peers associated with a single port, they each have their own
individual counters.

You might want to measure:
dialCtlPeerStatsConnectTime - seconds off hook
dialCtlPeerStatsSucessCalls - calls received
dialCtlPeerStatsAcceptCalls - calls made

These are a little kludgy when it comes to instance numbers.  Let's say you
have your POTS dial-peers listed as something like:

dial-peer voice 511 pots
 destination-pattern 511
 port 1
!
dial-peer voice 5112 pots
 destination-pattern 511
 port 2

Then you need to determine the ifIndex for these items:
[dmcdonald at netmon dmcdonald]$ snmpwalk 172.16.7.2 public ifName
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifName.16 = VoiceEncapPeer511
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifName.17 = VoiceEncapPeer5112

You could then determine calls made/received with:

loadmibs: DIAL-CONTROL-MIB-V1SMI.my

target[calls.511]: dialCtlPeerStatsAcceptCalls.511#VoiceEncapPeer511&
			dialCtlPeerStatsSuccessCalls.511#VoiceEncapPeer511:
			public at 172.16.7.2
options[calls.511]: perhour

I use perhour here since you are not likely to get 1 call per second, which
would be the minimum for it to show up on rateup without either the
perminute or perhour statement.  That's why I usually just monitor seconds
via the mib and monitor the calls using radius accounting.

Seconds would be something like:
target[seconds.511]: dialCtlPeerStatsConnectTime.511#VoiceEncapPeer511&
			  dialCtlPeerStatsChargedUnits.511#VoiceEncapPeer511:
			  public at 172.16.7.2
maxbytes[seconds.511]: 1
legend0[seconds.511]:
legendI[seconds.511]: off-hook seconds

Charged units should be zero on an FXO port, so it makes a handy zero so
that you only get one line on the graph.  For this to work, you must use
RRDTOOL as the backend.  it will then report the percentage of time on
hook - so if in 5 minutes 3 calls were made at 45 seconds each, it would
read as 135/300 = .45, or 45% utilization.  To do this with rateup you would
need to multiply by 100.

Note that the peer number and the ifIndex number are both required - when
you figure out why and tell me we will both know ;-)

Daniel J McDonald, CCIE 2495, CNX
Principal Network Specialist
Digicon Technologies
http://www.digicontech.com

Digicon, a Cisco Partner, Silver Certified.


--
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