Help was given bad advice and now device inst working

[aaronhill1]

Was told by another user on here to change the confreg to 0x800 so i tried it i entered

confreg 0x800

reset

After the device did that i started getting random jiberish like the baud rate is wrong on the console. and i cant read anything or do anything now. Help how do i fix this issue?

[Leo Laohoo]

I've never seen that config-registry value before.  Is this meant to speed up your baud rate to 115200?  If so, change your console baud rate to match it.

[Richard Burts · Accepted solution]

We do not know what platform this is on, but as you have discovered changing the config registry to 0x800 produced unexpected results. I believe that Leo is on the right track that part of the solution could be to change the speed specified by your terminal emulator to match what has been set on the device. If 115200 does not get it to work I would suggest starting with your emulator set to 1200, and try all of the speeds (2400, 4800, 9600 etc) till you find the one that works.

HTH

Rick

[John Blakley · Accepted solution]

I agree with Rick and Leo. According to this chart, if I'm reading it right, it looks like bit 11 is on which changes your console baud rate to 4800. Try that, but if that doesn't work try the others. Having garbage on the screen is usually an indication that it's a mismatched baud rate.

http://www.cisco.com/c/en/us/td/docs/routers/access/2600/hardware/installation/guide/2600hig/2600appC.html

HTH,

John

[aaronhill1]

Issue solved speed was 19200. 

[Richard Burts]

Thanks for posting back to the forum and letting us know that you solved the problem and confirming that the issue was a mismatch in speed between the console port and the terminal emulator. And thanks for using the rating system to mark this question as answered.

HTH

Rick