01-06-2005 08:19 AM
When we attempt to telnet to our 4506 switches (running IOS 12.2.18 EW) it says "Conection refused....". I did an SNMPWALK and found that all VTY ports were in use. I did an SNMPSET to clear the ports and can get back in. I'm pretty sure it has something to do with CiscoWorks and it polling of this switch. Here's what I can config'd on the VTY 0 4:
session-timeout 10
exec-timeout 5 0
password 7 XXXXXXXXXX
logging synchronous
Has anyone else had this problem and if so, what did you change to free the VTY lines?
I can force the 5 VTY lines to hang busy by doing a Check Device Attributes inside CiscoWorks. Then I do the SNMPSET (etc.) and clear the lines.
01-12-2005 06:52 AM
Try upgrading your IOS to 12.2.20-EWA. It seems to fix the issue.
01-23-2007 01:32 PM
This is probably related to CSCee62455
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee62455&Submit=Search
01-17-2005 05:38 AM
Did you fix your problem yet, and how di you fix it. I have more than eightly 4500 switch in our network that all running version 12.2.18 EW. I am planning to install Ciscoworks 2000 in the next two weeks. And I hope I do not need to upgrade all our switch ios first.
Thanks
01-17-2005 05:58 AM
Whe have the same problem, will a UPDATE to the trick?
01-18-2005 07:26 AM
Well we wanted to do the IOS update as a last resort and I took several suggestions from other threads as well as a suggestion earlier in this post and it looks like this (and is working now):
BEFORE
line vty 0 4
session-timeout 10
exec-timeout 5 0
password 7 XXXXXXXXXXXXXXXXX
logging synchronous
AFTER
line vty 0 4
no session-timeout
exec-timeout 1 0
password 7 XXXXXXXXXXXXXXXXXXXXX
logging sychronous
transport input telnet
Thanks for all of your suggestions!
02-01-2005 12:43 PM
joharman, thanks for you reply. I also want to know in case all vty lines are hung in our 45xx, what step or program I need to free those line up. You have mentioned snmp clear. How to do that exactly?
Thanks
02-02-2005 06:16 AM
To see which VTY lines are busy (1's indicate busy)
C:\>snmpwalk {-v 2c} -c (write comm string) X.X.X.X .1.3.6.1.4.1.9.2.9.2.1.1
cisco.local.9.2.1.1.0 : INTEGER: 0 <----- these 0's will be 1's if VTY lines are in use
cisco.local.9.2.1.1.1 : INTEGER: 0
cisco.local.9.2.1.1.2 : INTEGER: 1
cisco.local.9.2.1.1.3 : INTEGER: 0
cisco.local.9.2.1.1.4 : INTEGER: 0
cisco.local.9.2.1.1.5 : INTEGER: 0
** depending on which snmp pkg you are using, you may need include the {-v 2c} in this string
C:\>
To clear busy lines issue:
C:\>snmpset {-v 2c} -c (write comm string) X.X.X.X .1.3.6.1.4.1.9.2.9.10.0 integer 0
C:\>snmpset {-v 2c} -c (write comm string) X.X.X.X .1.3.6.1.4.1.9.2.9.10.0 integer 1
C:\>snmpset {-v 2c} -c (write comm string) X.X.X.X .1.3.6.1.4.1.9.2.9.10.0 integer 2
C:\>snmpset {-v 2c} -c (write comm string) X.X.X.X .1.3.6.1.4.1.9.2.9.10.0 integer 3
C:\>snmpset {-v 2c} -c (write comm string) X.X.X.X .1.3.6.1.4.1.9.2.9.10.0 integer 4
C:\>snmpset {-v 2c} -c (write comm string) X.X.X.X .1.3.6.1.4.1.9.2.9.10.0 integer 5
Where integer 1, 2 thru 5 etc.
01-20-2005 03:10 AM
Well i some way it's not working
line vty 0 4
session-timeout 5 <= i have try this
exec-timeout 1 0
password 7
logging synchronous
transport input telnet
version 12.2.18
Any other idea
02-02-2005 08:33 AM
We are going to upgrade to 12.2.20EW but CiscoWorks won't allow me to distribute any image to the 4506. I've got another thread asking how to fix that. Agagin, it looks like the only fix is to upgrade the IOS. Please let me know if someone can use the distribute image to a 4506 inside CiscoWorks.
02-22-2005 10:13 AM
I had to manually (TFTP) the image to the switch and add the boot statement in the startup config and now it's working. The VTY ports do not get hung up on IOS 12.2.20 EW.
02-23-2005 06:03 AM
I have a lot of 45xx in our network. two weeks ago, I installed the latest Ciscoworks 2000 with latest patch. 99% of our 45xx are running IOS 12.2.18 EW. However, I have never experiencing any telnet problem so far. (I cross my finger).
02-23-2005 06:39 AM
The problem appears when a few consecutive check device attributes are done....you may not see it right away, but after time is when we saw the VTY ports hang. Do a few check device attributes then check the status of the VTY ports on your 45XX's using the procedure I have a few relpies ago in this thread. Good luck!
01-23-2007 12:21 PM
What CiscoWorks version are you using ? LMS 2.2? LMS 2.5? LMS 2.6 ?
01-23-2007 01:33 PM
This is probably related to CSCee62455
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee62455&Submit=Search
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide