ARmy Rumour SErvice

**the_guru** · 11-09-2006, 09:57

Can anyone help? We have a couple of 1760 routers that have gone t*ts up. Someone (not me !) has changed the values in the config register and now on boot up they come up with a line of gash and then they just hang. We need to reload the IOS. Any help gratefully appreciated.

**TA_sig** · 11-09-2006, 12:12

Take a gander, should help: http://www.cisco.com/en/US/products/...html#wp1021650

**the_matelot** · 11-09-2006, 12:15

Try www.routergod.com

**no1cares** · 11-09-2006, 13:59

If you weren't such a t1t i'd help you.

**the_guru** · 11-09-2006, 16:45

Originally Posted by no1cares

If you weren't such a t1t i'd help you.

LOL.

Cisco Goddess? Go and do some ironing, troll.

Thanks to everyone else

**the_guru** · 12-09-2006, 08:17

Problem not cleared by the help already provided. Getting no CLI at all, so no MMI possible. Any clues?

**boney_m** · 12-09-2006, 08:35

Guru,

This link starts with an intro to the IOS, and links out to various articles on reloading/recovering the IOS.

Do you have a copy of your current config that can be used to tftp into the router via a console connection?

Boney

**Santa_Sunday** · 13-09-2006, 03:38

Originally Posted by the_guru

Problem not cleared by the help already provided. Getting no CLI at all, so no MMI possible. Any clues?

Sounds like your starter motor, mate.......

6 days

**scousemech** · 13-09-2006, 06:22

Originally Posted by the_guru

Can anyone help? We have a couple of 1760 routers that have gone t*ts up. Someone (not me !) has changed the values in the config register and now on boot up they come up with a line of gash and then they just hang. We need to reload the IOS. Any help gratefully appreciated.

What are the new values in the config reg this will determine our course of action

0x0000 Remains at bootstrap prompt
0x0001 Boot system image on EPROM
0x0040 ignores NVRAM contents
0x0100 Breaks disabled
0x2000 Sets defaulst ROM software if network boot fails
0x8000 Enables
diagnostic messages

We need to found out exactly were it fails when it boots attach a laptop to the console port using hyperterminal set the values to 9600 baud etc and capture the booting process to a text file.You can the read the file to pinpoint the start of the failure