Rob,

Is there a way to make it work on Win2K system that is already running
MRTG?

Thanks,

-C�sar Artiga
http://www.calcom.us
(408) 499-8389

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob Martinson
Sent: Monday, August 25, 2003 4:36 PM
To: [EMAIL PROTECTED]
Subject: RE: Paging / Latency / Pinging WAS RE: [smartBridges] 100%
Failure Rate

It's not all that difficult actually. If you're interested and need a
hand, let me know.

Rob Martinson
http://www.limelyte.com
509-241-0138

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Summers
> Sent: Monday, August 25, 2003 4:25 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Paging / Latency / Pinging WAS RE: 
> [smartBridges] 100% Failure Rate
> 
> 
> 
> That's pretty sweet. Wish I had that kind of detail
> going on my monitoring. Then again if I would just hire
> someone so I would have time to learn Perl I could have
> some monitoring going on like that... :-)
> 
> Kevin Summers 
> KISTech Internet Services Inc.
> www.kistech.com
>  
> 
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED] Behalf Of Rob Martinson
> > Sent: Monday, August 25, 2003 4:13 PM
> > To: [EMAIL PROTECTED]
> > Subject: Paging / Latency / Pinging WAS RE: [smartBridges] 100% 
> > Failure Rate
> > 
> > 
> > 
> > You guys and girls looking for something to monitor latency 
> and send 
> > you a page when the link is out of a specific range might 
> also want to 
> > take a look at SmokePing from Tobias Oetiker (MRTG, RRDTool).
> > 
> > We use it to graph latency on internal as well as to remote 
> networks 
> > (to keep an eye on our provider and our routing). Additionally we 
> > monitor a couple of our smartBridges devices and some other 
> internal 
> > devices with alarms.
> > 
> > I just set up a new Mikrotik last week and rebuilt the graphing 
> > machine. Haven't yet restored our past history so graphs 
> are new, but 
> > you can take a peek at: http://www.limelyte.com/network.php?id=13 
> > (more on the left nav).
> > 
> > URL for smokeping is here: 
> > http://people.ee.ethz.ch/~oetiker/webtools/smokeping/
> > 
> > This may also help some of you who mentioned that constant pings to 
> > your failing smartBridges equipment is preventing disassociation.
> > 
> > Rob Martinson
> > http://www.limelyte.com
> > 509-241-0138
> > 
> > -----Original Message-----
> > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED] On Behalf Of Blazen Wireless
> > Sent: Monday, August 25, 2003 3:23 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [smartBridges] 100% Failure Rate
> > 
> > 
> > I have been using this software called SERVERS ALIVE its 
> free and lets 
> > you ping up to 10 servers and if you want to ping more up 
> to 1000 IP's 
> > then you buy the license key for $100 it has tons of cool 
> things you 
> > can set up with it, remote reboots of servers etc etc..
> > 
> > http://www.woodstone.nu/salive/
> > 
> > 
> > ----- Original Message -----
> > From: Kevin Summers 
> > To: [EMAIL PROTECTED] 
> > Sent: Monday, August 25, 2003 3:20 PM
> > Subject: RE: [smartBridges] 100% Failure Rate
> > 
> > 
> > What are you using for paging? I've been looking for a good 
> solution 
> > for that... Kevin Summers
> > KISTech Internet Services Inc.
> > www.kistech.com
> >  
> > -----Original Message-----
> > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED] Behalf Of Blazen Wireless
> > Sent: Monday, August 25, 2003 2:54 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [smartBridges] 100% Failure Rate
> > 
> > 
> > Mine pages me too I got tired of all the pages so I shut that off!
> > 
> > 
> > ----- Original Message -----
> > From: The Wirefree Network 
> > To: [EMAIL PROTECTED] 
> > Cc: [EMAIL PROTECTED] 
> > Sent: Monday, August 25, 2003 2:06 PM
> > Subject: RE: [smartBridges] 100% Failure Rate
> > 
> > 
> > Now isn't this a bit TOOOOOO coincidental?!?!? I mentioned 
> 10:20 am on 
> > mine.  However, that is when IPCheck paged me to tell me.  When I 
> > checked my log, it actually went down at 10:15.30 Pacific Standard 
> > Time.
> >  
> > Anyone else go down at the same time???
> >  
> > Sully
> >  
> > -----Original Message-----
> > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED] On Behalf Of Blazen Wireless
> > Sent: Monday, August 25, 2003 12:41 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [smartBridges] 100% Failure Rate
> >  
> > I mentioned at around 9-10:30am that a few went offline I 
> can check my 
> > logs from today I think they both crapped out at about 
> 10:15 today.. 
> > Here ar my logs sorry it was soo long but you can see the 
> times quite 
> > clearly when the 10.0.0.98 unit went down and it is still down no 
> > moatter how many times I try to ping it or reboot the APPO it is 
> > supposed to associate to.. it was good all night then at around 
> > 10:14PT 10.0.0.98 it went down
> >  
> > 
> > Monday, August 25, 2003 10:09:07 AM Ping 10.0.0.12
> > Monday, August 25, 2003 10:09:07 AM Ping 10.0.0.12 OK with a 
> > successrate of 100% and an average roundtriptime of 26ms Monday, 
> > August 25, 2003 10:09:07 AM Ping 10.0.0.14 Monday, August 25, 2003 
> > 10:09:08 AM Ping 10.0.0.14 OK with a successrate of 100% and an 
> > average roundtriptime of 52.2ms Monday, August 25, 2003 10:09:08 AM 
> > Ping 66.80.227.107 Monday, August 25, 2003 10:09:08 AM Ping 
> > 66.80.227.107 OK with a successrate of 100% and an average 
> > roundtriptime of 44ms Monday, August 25, 2003 10:09:08 AM Ping 
> > 66.80.227.98 Monday, August 25, 2003 10:09:08 AM Ping 
> 66.80.227.98 OK 
> > with a successrate of 100% and an average roundtriptime of 34ms
> > Monday, August 25, 2003 10:09:09 AM Ping 66.80.227.99
> > Monday, August 25, 2003 10:09:09 AM Ping 66.80.227.99 OK with a
> > successrate of 100% and an average roundtriptime of 64.2ms
> > Monday, August 25, 2003 10:09:09 AM Ping 66.80.227.90
> > Monday, August 25, 2003 10:09:09 AM Ping 66.80.227.90 OK with a
> > successrate of 100% and an average roundtriptime of 26ms
> > Monday, August 25, 2003 10:09:10 AM Ping 10.0.0.8
> > Monday, August 25, 2003 10:09:10 AM Ping 10.0.0.8 OK with a 
> successrate
> > of 100% and an average roundtriptime of 32ms
> > Monday, August 25, 2003 10:09:10 AM Ping 10.0.0.76
> > Monday, August 25, 2003 10:09:10 AM Ping 10.0.0.76 OK with 
> a successrate
> > of 100% and an average roundtriptime of 42.2ms
> > Monday, August 25, 2003 10:09:11 AM Ping 10.0.0.60
> > Monday, August 25, 2003 10:09:12 AM Ping 10.0.0.60 OK with 
> a successrate
> > of 80% and an average roundtriptime of 27.5ms
> > Monday, August 25, 2003 10:09:12 AM Ping 10.0.0.98
> > Monday, August 25, 2003 10:09:13 AM Ping 10.0.0.98 OK with 
> a successrate
> > of 100% and an average roundtriptime of 34ms
> > 
> > Monday, August 25, 2003 10:14:04 AM Check cycle starts ( 0- 
> 1) Monday, 
> > August 25, 2003 10:14:05 AM Ping 10.0.0.12 Monday, August 25, 2003 
> > 10:14:05 AM Ping 10.0.0.12 OK with a successrate of 100% and an 
> > average roundtriptime of 46ms Monday, August 25, 2003 
> 10:14:05 AM Ping 
> > 10.0.0.14 Monday, August 25, 2003 10:14:05 AM Ping 
> 10.0.0.14 OK with a 
> > successrate of 100% and an average roundtriptime of 40ms
> > Monday, August 25, 2003 10:14:06 AM Ping 66.80.227.107
> > Monday, August 25, 2003 10:14:06 AM Ping 66.80.227.107 OK with a
> > successrate of 100% and an average roundtriptime of 44.2ms
> > Monday, August 25, 2003 10:14:06 AM Ping 66.80.227.98
> > Monday, August 25, 2003 10:14:12 AM Ping 66.80.227.98 
> failed due to a
> > successrate of only 0%
> > Monday, August 25, 2003 10:14:12 AM Ping 66.80.227.99
> > Monday, August 25, 2003 10:14:12 AM Ping 66.80.227.99 OK with a
> > successrate of 100% and an average roundtriptime of 36ms
> > Monday, August 25, 2003 10:14:13 AM Ping 66.80.227.90
> > Monday, August 25, 2003 10:14:13 AM Ping 66.80.227.90 OK with a
> > successrate of 100% and an average roundtriptime of 36.2ms
> > Monday, August 25, 2003 10:14:13 AM Ping 10.0.0.8
> > Monday, August 25, 2003 10:14:13 AM Ping 10.0.0.8 OK with a 
> successrate
> > of 100% and an average roundtriptime of 36ms
> > Monday, August 25, 2003 10:14:14 AM Ping 10.0.0.76
> > Monday, August 25, 2003 10:14:14 AM Ping 10.0.0.76 OK with 
> a successrate
> > of 100% and an average roundtriptime of 48ms
> > Monday, August 25, 2003 10:14:14 AM Ping 10.0.0.60
> > Monday, August 25, 2003 10:14:14 AM Ping 10.0.0.60 OK with 
> a successrate
> > of 100% and an average roundtriptime of 42.2ms
> > Monday, August 25, 2003 10:14:14 AM Ping 10.0.0.98
> > Monday, August 25, 2003 10:14:20 AM Ping 10.0.0.98 failed due to a
> > successrate of only 0%
> > Monday, August 25, 2003 10:14:20 AM Ping 66.80.227.98
> > Monday, August 25, 2003 10:14:25 AM Ping 66.80.227.98 
> failed due to a
> > successrate of only 0%
> > 
> > Monday, August 25, 2003 10:15:20 AM Check cycle starts ( 1- 
> 2) Monday, 
> > August 25, 2003 10:15:20 AM Ping 10.0.0.12 Monday, August 25, 2003 
> > 10:15:20 AM Ping 10.0.0.12 OK with a successrate of 100% and an 
> > average roundtriptime of 26ms Monday, August 25, 2003 
> 10:15:20 AM Ping 
> > 10.0.0.14 Monday, August 25, 2003 10:15:21 AM Ping 
> 10.0.0.14 OK with a 
> > successrate of 100% and an average roundtriptime of 26ms
> > Monday, August 25, 2003 10:15:21 AM Ping 66.80.227.107
> > Monday, August 25, 2003 10:15:21 AM Ping 66.80.227.107 OK with a
> > successrate of 100% and an average roundtriptime of 46.2ms
> > Monday, August 25, 2003 10:15:21 AM Ping 66.80.227.98
> > Monday, August 25, 2003 10:15:27 AM Ping 66.80.227.98 
> failed due to a
> > successrate of only 0%
> > Monday, August 25, 2003 10:15:30 AM Ping 66.80.227.99
> > Monday, August 25, 2003 10:15:30 AM Ping 66.80.227.99 OK with a
> > successrate of 100% and an average roundtriptime of 42.2ms
> > Monday, August 25, 2003 10:15:30 AM Ping 66.80.227.90
> > Monday, August 25, 2003 10:15:31 AM Ping 66.80.227.90 OK with a
> > successrate of 100% and an average roundtriptime of 36ms
> > Monday, August 25, 2003 10:15:31 AM Ping 10.0.0.8
> > Monday, August 25, 2003 10:15:31 AM Ping 10.0.0.8 OK with a 
> successrate
> > of 100% and an average roundtriptime of 28ms
> > Monday, August 25, 2003 10:15:31 AM Ping 10.0.0.76
> > Monday, August 25, 2003 10:15:31 AM Ping 10.0.0.76 OK with 
> a successrate
> > of 100% and an average roundtriptime of 36.2ms
> > Monday, August 25, 2003 10:15:32 AM Ping 10.0.0.60
> > Monday, August 25, 2003 10:15:33 AM Ping 10.0.0.60 OK with 
> a successrate
> > of 80% and an average roundtriptime of 30ms
> > Monday, August 25, 2003 10:15:33 AM Ping 10.0.0.98
> > Monday, August 25, 2003 10:15:39 AM Ping 10.0.0.98 failed due to a
> > successrate of only 0%
> > 
> > Monday, August 25, 2003 10:17:39 AM Check cycle starts ( 2- 
> 3) Monday, 
> > August 25, 2003 10:17:39 AM Ping 10.0.0.12 Monday, August 25, 2003 
> > 10:17:39 AM Ping 10.0.0.12 OK with a success of 100% and an average 
> > roundtriptime of 42ms Monday, August 25, 2003 10:17:39 AM Ping 
> > 10.0.0.14 Monday, August 25, 2003 10:17:40 AM Ping 
> 10.0.0.14 OK with a 
> > successrate of 100% and an average roundtriptime of 48.2ms
> > Monday, August 25, 2003 10:17:40 AM Ping 66.80.227.107
> > Monday, August 25, 2003 10:17:40 AM Ping 66.80.227.107 OK with a
> > successrate of 100% and an average roundtriptime of 52.2ms
> > Monday, August 25, 2003 10:17:40 AM Ping 66.80.227.98
> > Monday, August 25, 2003 10:17:46 AM Ping 66.80.227.98 
> failed due to a
> > successrate of only 0%
> > Monday, August 25, 2003 10:17:49 AM Ping 66.80.227.99
> > Monday, August 25, 2003 10:17:50 AM Ping 66.80.227.99 OK with a
> > successrate of 80% and an average roundtriptime of 60.3ms
> > Monday, August 25, 2003 10:17:51 AM Ping 66.80.227.90
> > Monday, August 25, 2003 10:17:51 AM Ping 66.80.227.90 OK with a
> > successrate of 100% and an average roundtriptime of 34ms
> > Monday, August 25, 2003 10:17:51 AM Ping 10.0.0.8
> > Monday, August 25, 2003 10:17:51 AM Ping 10.0.0.8 OK with a 
> successrate
> > of 100% and an average roundtriptime of 26ms
> > Monday, August 25, 2003 10:17:52 AM Ping 10.0.0.76
> > Monday, August 25, 2003 10:17:52 AM Ping 10.0.0.76 OK with 
> a successrate
> > of 100% and an average roundtriptime of 32ms
> > Monday, August 25, 2003 10:17:52 AM Ping 10.0.0.60
> > Monday, August 25, 2003 10:17:52 AM Ping 10.0.0.60 OK with 
> a successrate
> > of 100% and an average roundtriptime of 24ms
> > Monday, August 25, 2003 10:17:52 AM Ping 10.0.0.98
> > Monday, August 25, 2003 10:17:58 AM Ping 10.0.0.98 failed due to a
> > successrate of only 0%
> > ----- Original Message ----- 
> > From: The Wirefree Network 
> > To: [EMAIL PROTECTED] 
> > Sent: Monday, August 25, 2003 12:20 PM
> > Subject: RE: [smartBridges] 100% Failure Rate
> >  
> > A common factor keeps coming up here..the 1000 hr.  Hmmm..mine went 
> > down this morning at 10:20 am.  Yesterday it went down at 9:45 am.  
> > The day before at 10:05 am.
> >  
> > Hmmmmm...I seem to remember other folks mentioning the same time 
> > frame.
> >  
> > Like I said earlier.this may not be an overall temperature 
> exceeding a 
> > certain threshold thing.it may be a temperature SWING 
> thing.  In other 
> > words, maybe when the unit goes from 70 degrees to 80 
> degrees in just 
> > 15 minutes, it craps??  I don't know.but this is very odd.
> >  
> > I can say this though..my network has very little traffic 
> at 10:00 am.
> >  
> > Sully
> >  
> > P.S.  I powered it down for 10 minutes and it has been working fine 
> > since.  So.if it was an overall temperature thing.then why does it 
> > stay up for the rest of the day, with it getting even 
> hotter???  This 
> > is where I would focus, if I were an sB engineer!!
> >  
> > -----Original Message-----
> > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED] On Behalf Of Bobby Bounds
> > Sent: Monday, August 25, 2003 12:10 PM
> > To: [EMAIL PROTECTED]
> > Subject: [smartBridges] 100% Failure Rate
> >  
> > I replaced a 2 week old APPO last night that was exhibiting 
> the "lost 
> > association" problem. The new APPO I used as the 
> replacement came from 
> > the same order I got from Electro-Comm. This new unit worked 
> > sporadically last night but this morning around 10 am lost 
> all signs 
> > of life.
> >  
> > Also we purchased 3 ABO's during the same time frame. One died 
> > completely and the other two are disassociating every evening about 
> > the same time.
> >  
> > So, were ohhh for five on those 'June' units.
> >  
> > Bobby Bounds
> > Airwave Internet, LLC
> >  
> >  
> >  
> > 
> > The PART-15.ORG smartBridges Discussion List
> > To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe
> > smartBridges <yournickname>
> > To Remove: mailto:[EMAIL PROTECTED] (in the body type 
> > unsubscribe smartBridges)
> > Archives: http://archives.part-15.org  
> The PART-15.ORG smartBridges Discussion List
> To Join: mailto:[EMAIL PROTECTED] (in the body type 
> subscribe smartBridges <yournickname> To Remove: 
> mailto:[EMAIL PROTECTED] (in the body type unsubscribe 
> smartBridges)
> Archives: http://archives.part-15.org  
> 

The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe
smartBridges <yournickname>
To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe
smartBridges)
Archives: http://archives.part-15.org  


The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges 
<yournickname>
To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges)
Archives: http://archives.part-15.org

Reply via email to