[mrtg] Re: monitoring the "Unavailable Secs" of Serial Interface that has E3 card on Cisco ROuter

[Zeeshan Ahmed]

Thanks this transmission OID is working for me very well.

#############transmission.30.8.1.5.1&transmission.30.8.1.5.1


Regards
Zeeshan Ahmed
----- Original Message ----- 
From: "Pete Templin" <pete.templin at texlink.com>
To: "Zeeshan Ahmed" <zeeshan at worldcall.net.pk>; "MRTG Mailinglist"
<mrtg at list.ee.ethz.ch>
Sent: Friday, September 19, 2003 6:12 AM
Subject: [mrtg] Re: monitoring the "Unavailable Secs" of Serial Interface
that has E3 card on Cisco ROuter


> YMMV, but
".iso.org.dod.internet.mgmt.mib-2.transmission.ds3.dsx3TotalTable.dsx3TotalE
ntry", aka .1.3.6.1.2.1.10.30.8.1, is probably a good part of the SNMP
transmission MIB to go through.  I monitor
"Target[$router.$cardcode.$userslot.$port.11]:
1.3.6.1.2.1.10.30.6.1.2.$ifIndex&1.3.6.1.2.1.10.30.7.1.3.$ifIndex.$interval:
$snmpcomm\@$rtraddr" (and other related OIDs) on DS3s coming into my various
Riverstone routers, with great results.  This shows me the number of blips
(errored seconds in this case) in the "current" five-minute period and
previous fifteen-minute period.  It's not the world's most accurate, because
I can't synchronize MRTG to the DS1/DS3 fifteen minute interval.  The
"current" five-minute period is semi-cumulative in this scenario, so in a
succession of four polling intervals I might miss the tail end of an
interval but catch less than the first five minutes, then catch another five
minutes adding in, then catch another five minutes adding in, then miss the
t
>  ail end of the interval while catching a portion of the next interval.
By polling the previous interval (I set $interval to 1) three times, I at
least get a history of full fifteen minutes' worth of counters at that
point.
>
> Pete Templin
> Senior Staff Engineer
> TexLink Communications
> (210) 892-4183
> pete.templin at texlink.com
>
>
> -----Original Message-----
> From: Zeeshan Ahmed [mailto:zeeshan at worldcall.net.pk]
> Sent: Friday, September 19, 2003 3:58 PM
> To: MRTG Mailinglist
> Subject: [mrtg] monitoring the "Unavailable Secs" of Serial Interface that
has E3 card on Cisco ROuter
>
> I want to monitor the "Unavailable Secs" of my Serial Interface that has
E3 card on Cisco ROuter 7204 VXR.
> I can see the Unavailable Secs of my interface by the command sh
controllers serial 4/0
> and I get following out put
> Total Data (last 78 15 minute intervals):
>      0 Line Code Violations, 0 P-bit Coding Violation,
>      0 C-bit Coding Violation,
>      0 P-bit Err Secs, 0 P-bit Sev Err Secs,
>      0 Sev Err Framing Secs, 44 Unavailable Secs,
>      0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Sev Err Secs
>
> how can i graph the parameters given in the out put,especially I am
concerned with Unavailable Secs.
>
> Regards
> Zeeshan Ahmed
> --
> 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
>
> --
> 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
>
>
>


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