Router 2610XM Self decompressing the image

[Zoorben123]

Hi,

I`m having problem with booting Cisco router 2610 and I`m having this messenge :

C2600 platform with 131072 Kbytes of main memory

Program load complete, entry point: 0x80008000, size 0x439138

Self decompressing the image :
##################################################
###################################################################
###############################################
[OK]

After that, I can't type any thing, is there someone who can help me please?

Tks

[Peter Paluch · Accepted solution]

Nuno,

While improbable, it is still possible that the console speed changes from the default value after the IOS started. Have you tried other COM port speeds to see whether you get access? Try all available speed settings ranging from 1200 bps up to 115200 bps.

If that does not help please perform another test: break the IOS bootup process and enter the ROMMON mode. Then use the cookie command to display the value of the configuration cookie (an array holding vital information about the router's hardware configuration) and post it here please. I have seen a number of routers with corrupted cookie value, resulting in its inability to boot.

Best regards,

Peter

[Richard Burts · Accepted solution]

I agree with Peter that the symptoms suggest the possibility that the console speed has been changed. I especially notice that there is no console output after the image is decompressed and loaded. Some routers (and I believe that the 2610 is among them) support a speed command under the console interface, which interacts with the speed as set in the config register but only becomes effective after the router has accessed the startup config.

The symptom described by Nuno are that he cannot enter any commands after the router boots. I have seen another problem that produces this symptom. If the console is configured with the command no exec, then the console will not accept any input. When I was teaching Cisco classes I had some students who would configure "no exec" assuming that it was an abbreviation for "no exec-timeout".  But whereas the no exec-timeout will not use the inactivity timeout, the command "no exec" will prevent any input on the console. If this is perhaps the issue, then performing the password recovery process, specifying the config register as 0x2142 will allow the router to boot and to accept input on the console.

HTH

Rick

[Zoorben123]

Hi,

Thanks for your help, I change the speed of the COM port and gained access again. Not sure how this happened, but this is my new lab, that I'm setting so maybe I made a rookie mistake.

Regards,

Nuno