[c-nsp] Something like MTR, but forced path

[Masood Ahmad Shah]

You can't do this by using pooling or interval based monitoring system. You
need to work on syslog or event based traps. I believe that your equipment
at both end is Cisco. 

You must track reachable IPs and generate syslog or event traps if the next
hope or whatever IP is unreachable. Here is an example

Here what you want to monitor: 

ip sla monitor 1
 type echo protocol ipIcmpEcho 192.168.75.3 source-ipaddr 192.168.3.254
 timeout 2000
 threshold 2500
 frequency 3

Here I'm defining time domain:

ip sla monitor schedule 1 life forever start-time now


Here I'm starting track:

track 123 rtr 1 reachability


You will find logs as show below on every event.

*Dec 19 12:53:19.204 PKT: %TRACKING-5-STATE: 123 rtr 1 reachability Up->Down
*Dec 19 12:53:24.204 PKT: %TRACKING-5-STATE: 123 rtr 1 reachability Down->Up

For same you can also use Cisco Embedded Event Manager 

http://www.cisco.com/en/US/products/ps6815/products_ios_protocol_group_home.
html

Regards,
Masood Ahmad Shah
BLOG: http://www.weblogs.com.pk/jahil/



-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Tuc at T-B-O-H.NET
Sent: Wednesday, December 19, 2007 6:38 PM
To: Ed Ravin
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Something like MTR, but forced path

> 
> On Tue, Dec 18, 2007 at 09:01:50PM -0500, Tuc at T-B-O-H.NET wrote:
> > I'm basically looking for something I can run on Unix and
> > give me a curses view of IPs I give it to ping at the same time.
> 
> You could use Mon:
> 
>   http://mon.wiki.kernel.org/index.php/Main_Page
>
	(Info deleted for brevity) 
> 
> > Curses MTR bolds the lettering when it has a ping loss which I want
> > to catch my eye.
> 
> In my shop, we have Mon set to write to our terminals when it has
> something important to tell us.
> 
> > As an FYI, the problem I have is I'm having connection losses between my
> > site and the wireless WISP's gateway. I think the packet is getting to
the
> > backhaul link at the site here, but not to the other end of the backhaul
here.
> > I want to run a set of pings [...]
> 
> That sounds like a job for Smokeping:
> 
>   http://oss.oetiker.ch/smokeping/
>
	(Info deleted for brevity)
> 
> > I want something formalized since sending pings that just show
> > a loss somewhere in the middle don't mean anything.
> 
> I've done that with Smokeping - tell Smokeping to ping everything in
> a particular path.  Lining up the resulting graphs with records of
> service outages is usually very informative.
> 
	I appreciate your reply.

	I actually have smokeping running on both ends, but I'm looking
for something that can run in an xterm while I'm writing email and I
can see it actually pinging live. The others are snapshots of the
network, not real time. If it pings every 5 minutes, for 20 seconds,
and the next 270 seconds the network is down, then comes back, the
utilities are going to show 100% up. Unless the intermittent
issue happens during the polling cycle, we won't see it. I'm running
into the problem of the WISP seeing the graphing show 100% up, while
I'm sitting here with 64 second chunks of network disappearing. I
also can't prove its ONLY my site happening, since I am only at this
one site. I wanted something that I could leave running in a "screen"
on one of his DD-WRT installed Buffalo (SIGH... That lawsuit sucks)
routers.

		Thanks, Tuc
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/