
Comms/Terminal Server Problem
Hi all,
I am not sure this is the right topic, so if not i am sorry for that.
Setting up a terminal server for my lab I use a 2811 with a NM-32A and 4 x octal cable set. The thing is when i extend the octal cable(s) with a straigth rj-45 cable as Cisco reommends the controller of the NM-32A almost crashed the box saying:
*Dec 9 11:35:12.927: %SYS-3-CPUHOG: Task is running for (2004)msecs, more than (2000)msecs (2/2),process = TTY Daemon.
-Traceback= 0x4035EBF4z 0x40377E8Cz 0x40F05898z 0x418E5644z 0x4202D6ECz 0x4202D6D0z
*Dec 9 11:35:13.923: %CIRRUS-3-HWNORESPONSE: The CD2430 Controller is not responding, power cycle the router
*Dec 9 11:35:14.927: %SYS-3-CPUHOG: Task is running for (4004)msecs, more than (2000)msecs (2/2),process = TTY Daemon.
-Traceback= 0x4035EBF4z 0x40376DF8z 0x40F058A8z 0x418E5644z 0x4202D6ECz 0x4202D6D0z
And after that I get a login prompt and let's me give in my username and password and than it hangs.....
If i connect a octal cable directly in a device it is working fine??? I tried several rj-45 cable flavors and different connector blocks as well..
Anybody has experienced something like this before?
Thanks, David
Comments
what version of IOS are you running, did you try another build? I've ran this setup before and didn't see the same errors but it seems like a bug in the IOS version you're using.
Thanks, some other people advised me that too... will do it when i am with the box,
David
I had the same issue with my access server 2600XM with (NM-32A)
Mar 1 00:01:54.035: %CIRRUS-3-HWNORESPONSE: The CD2430 Controller is not responding, power cycle the router
*Mar 1 00:01:57.035: %CIRRUS-3-HWNORESPONSE: The CD2430 Controller is not responding, power cycle the router
*Mar 1 00:02:00.035: %CIRRUS-3-HWNORESPONSE: The CD2430 Controller is not responding, power cycle the router
*Mar 1 00:02:00.035: %SYS-3-CPUHOG: Task ran for 8000 msec (0/0), process = TTY Daemon, PC = 80C025EC.
-Traceback= 80C025F0 8049E9BC 804A20BC
1 - changed the Octal cable = did not fix issue
2 - Tried different IOS to build = did not fix issue
**3 - installed different NM-32A module = Issue was fixed **