Helpful Script for Putty for monitoring

I'm looking for some advice for a helpful script that will help prevent from being kicked out of routers when monitoring certain circuits/running extended ping tests to loops. I currently use SuperPutty for the tab features and really, that's the only thing we are allowed to have within my group. I know I could change the timeout for my session, but I would like to try other options first.

What I would like is something that would attach to a certain window of SuperPutty that I would drag out and then attach to that process and for this example, hit enter or any key to prevent being kicked out while running the extended ping test to a loop or even a neighbor IP for stability testing. Maybe this could be edited then for my other needs that I would like to have, maybe doing show int <int> | inc <modifers wanted> every 5 minutes to check for any degradation on the circuit.

If you work in the ISP world and or even monitoring circuits manually and found something that works well for you, I would love to hear about it! Thanks!

Posted Jun 18, 2015, 7:18 AM UTC

811
magionCCNA•

In butty click on Connection, then check Enable TCP keepalives, then set the number of seconds between each keepalive sent. Change this for each of the sessions you want to have that feature enabled for.

9
ZeroAssassinOPCCNA•

I have tried this in the past, but didn't work. I will give it another shot though. Thanks!

0
EtherealMind2etherealmind.com &amp; CCIE•

Why use Putty ? Everyone else uses Linux which provides superior capabilities in every way for this. You can find untold resources to help you and get a good solution.

No one runs this type of solution on Windows so why would you bother ?

1
tmtl•

I know I could change the timeout for my session, but I would like to try other options first.

So, you have a solution, but you want.... another solution?

0
ZeroAssassinOPCCNA•

I mean, if I'm not "allowed" to change the timeouts, then it's obviously not a solution.

0
tmtl•

In which case, maybe the timeouts are there for a reason? I'd ask for an official answer from whoever you report to. You don't want to willfully circumvent policy

1
ZeroAssassinOPCCNA•

Of course there are timeouts for a reason.. It's for people to get kicked out for inactivity where they have forgot to exit out to free lines to allow people to ssh in.

0
tmtl•

Also, unattended sessions are a security issue

As I said before, talk to your superior to find out if the settings can/cannot be changed. There's no point going it alone to then find out you've breached some protocol or policy

1
ZeroAssassinOPCCNA•

Of course there are timeouts for a reason.. It's for people to get kicked out for inactivity where they have forgot to exit out to free lines to allow people to ssh in.

0