Thanks Alex, Your implementation is the same as I had thought so. But I want to ask you two questions regarding this implementation:- 1. If I use the Target keyword for monitoring the ifoperstatus then how would I be able to monitor the input & output octets through the same mrtg. 2. This implementation would plot the graphs but I want to only generate the mail whenever an interface is down. I don't want to use different mrtg for monitoring the Ifoperstatus. On Thu, 18 Apr 2002 Alex van den Bogaerdt wrote : > >tarik singh wrote: > > > I am trying to generate a mail whenever any interface on >any > > router is operatively down. By operatively down I mean when >the > > line protocol is down & not the serial interface. The OID >for > >RTFM and look for ifOperHack. > >It returns a number, this number can be monitored as a GAUGE. >I think in your case you should do something like > >Target[x]: ifOperStatus.1&ifOperHack.1:public@router > >-- > >__________________________________________________________________ > / alex@slot.hollandcasino.nl >alex@ergens.op.het.net \ >| work >private | >| My employer is capable of speaking therefore I speak only for >myself | >+----------------------------------------------------------------------+ >| Technical questions sent directly to me will be nuked. Use the >list. | >+----------------------------------------------------------------------+ >| http://faq.mrtg.org/ >| >| http://rrdtool.eu.org --> tutorial >| >+----------------------------------------------------------------------+ > >-- >Unsubscribe >mailto:mrtg-request@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 > -- Unsubscribe mailto:mrtg-request@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