Does anyone know of any bugs in 6500 Sup720 code 12.2(33)SXH7 for stuck VTY sessions? We ended up having to reboot a dual supervisor Sup720 as we had a stuck VTY session.
A telnet session didn't disconnect cleanly and I couldn't clear it either with "clear line <line no>" or "clear tcp <tcb no>". I also tried changing the vty settings but that didn't do it either. The problem was that the session hung after issuing a "wr mem" so after that I couldn't view the running or startup config.
I got this error message .....
"Unable to get configuration. Try again later."
The logs were reporting this.....
Dec 15 21:24:29.108 gmt: %SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more
than (2000)msecs (46/40),process = RFSS_server_action.
-Traceback= 4142AE28 405D8BA4 405DA9DC 403B8C74 405DFC38 403B8C74 4092B150 40759
4A4 40759490
Dec 15 21:24:34.672 gmt: %SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more
than (2000)msecs (101/97),process = RFSS_server_action.
Also, some Mitel servers attached to the switches were reporting continuous spanning tree topology changes.
I switched to the secondary supervisor ok but then when the other supervisor reloaded it couldn't access the config from the active one so wouldn't sync up and kept rebooting itself!
Reloading both supervisors fixed it but it would be good to know if there's a workaround?
