One of the things that I hate is the processor to be cycling on 100% while I'm trying to configure something. Most of the time the reason for it is console timeout. I'm using this script on each router to get rid of console timeout, and some other things:
en
conf t
no ip domain-lookup
no cdp log mismatch duplex
line console 0
exec-timeout 33333
end
wr
That will setup the timeout to 3 weeks and 2 days, and your processor can breath a bit ;-)
Enjoy!
2 comments:
Why not do "exec-timeout 0 0"? You don't have to worry about timeouts if you do that.
Dear Sir, I've found your useful weblog while i was searching about "slow connection with FWSM" and I appreciate if u can halp me regrding to this issue..
I've recently setup FWSM Multiple context running in routed mode all the ping tests were successfully done between servers but when I start to setup database connection ...I saw that database application is very slow...and I should mention that all the security rule that I have, is one ACL with permit any any which is applied to all interfaces...the version of FWSM Sw is 3.2(2)
would u please help me?
Regards,
Post a Comment