Yes it would be preferable not to have dodgy hardware! But we have to
put up with it for a little while longer.

Thanks for those suggestions guys. Since I already have a telnet perl
script I will mod that to do the ping beforehand.

Thanks,


Aaron.


-----Original Message-----
From: Pete S. [mailto:[email protected]] 
Sent: Friday, 21 August 2009 12:52 PM
To: Aaron Riemer
Cc: [email protected]
Subject: Re: [c-nsp] IP SLA / EEM Scripting

A perl script with Net:Ping, and Net:Telnet might be easier,
especially if you have a server dedicated to device management.  Both
are fairly trivial modules with many examples on line.  Have cron run
the script every 5(whatever) min.  If ping fails, part of the scripts
logic is to telnet and reload.

Part of the script's output can be the ping data, which cacti can
graph as a datasource.  You may even see a trend when its about to
die.

Wouldn't you rather solve the problem with the vendor, as to why the
device needs the reset so often, or find new hardware that doesn't
need the reset? :)

--Pete

On Thu, Aug 20, 2009 at 9:26 PM, Aaron Riemer<[email protected]>
wrote:
> Hey Guys,
>
> I am hoping to use a combination of IP SLA and EEM to run a script
when
> a certain event occurs. For example we have a cellular router that
> sometimes requires a reset. We have a backup link so I would like to
> automate this reset process. What I would like to do is to monitor the
> cellular device with IP SLA icmp probes and after a certain number of
> failures run a script that can telnet to the device via the back door
> and issue commands to reset.
>
> I have done some digging but I am unable to see if EEM supports the
> ability for a router to actually telnet to another device and issue
> commands. I may have to use our network monitoring app to run the
> script. Could Cacti do this?
>
> Thanks for any suggestions.
>
> Aaron.

LEGAL DISCLAIMER: This message contains confidential information and is 
intended only for the individual named. If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail. Please notify the 
sender immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system. If you are not the intended recipient you 
are notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to