[mrtg] Re: Monitoring Cisco ISDN Lines

Steven Koutstaal coldsteel at zonnet.nl
Thu Jun 22 07:59:45 MEST 2000

Hi Barry,

you can achieve this in two ways:

1.    Make a config file with cfgmaker, and just graph the routers
interfaces. It will be obvious when these lines come up.

2.    Look at the oid for the link state. I don't really know the OID for
it, and can't check from the location I am in right now, but if you do a
'snmpwalk router community | grep state' on a unix/linux box you'll be able
to find it.

Good luck,

right now,
----- Original Message -----
From: "Barry Young" <byoung at europe.chep.com>
To: <mrtg at list.ee.ethz.ch>
Sent: Wednesday, June 21, 2000 14:09
Subject: [mrtg] Monitoring Cisco ISDN Lines

> Having been caught out by some incorrect configuration in our ISDN
> routers and hence some major call charges, I would like to get MRTG
> to monitor the line usage.
> We have a Cisco 1603 with an ISDN connection to a single site in
> Greece.  Therefore the call can start on one channel (ie. BRI0:1) and
> then bring in a second channel (ie. BRI0:2) if the traffic volume exceeds
> the given threshold.  Calls should then be dropped after a pre-determined
> period of inactivity. So fairly standard practise...
> I guess a suitable approach would be to graph when the lines are up?
> Does anyone know how to achieve this and the appropriate OIDs to use?
> Or is there a better method?
> Thanks in advance,
> --------------------------------------------------------------------------
> This E-mail is strictly confidential and intended solely for the
> It may contain information that is covered by legal, professional or other
> privilege. If you are not the intended addressee you must not use,
disclose or
> copy this transmission.
> This E-mail is not intended to impose nor shall it be construed as
imposing any
> legally binding obligation upon CHEP and/or any of its subsidiaries or
> associated companies.
> Neither CHEP nor any of its subsidiaries or associated companies gives any
> representation or warranty as to the accuracy or completeness of the
contents of
> this E-mail.
> CHEP shall not be held liable to any person resulting from the use of any
> information contained in this E-mail and shall not be liable to any person
> acts or omits to do anything in reliance upon it.
> --
> 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

More information about the mrtg mailing list