How do I stop this?

[HermeszData]

I picked up a 1721 to be able to run SDM. the router works fine and I have no issues other than:
%Error opening tftp://255.255.255.255/network-confg (Timed out)
Nov 1 16:16:25.343: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/network-confg) failed
%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)
Nov 1 16:16:46.347: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/cisconet.cfg) failed
%Error opening tftp://255.255.255.255/hermeszlab_r8-confg (Timed out)
Nov 1 16:17:07.299: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/hermeszlab_r8-confg) failed
%Error opening tftp://255.255.255.255/hermeszl.cfg (Timed out)
Nov 1 16:17:28.311: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/hermeszl.cfg) failed
%Error opening tftp://255.255.255.255/network-confg (Timed out)
Nov 1 16:24:07.351: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/network-confg) failed
%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)
Nov 1 16:24:28.355: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/cisconet.cfg) failed
%Error opening tftp://255.255.255.255/hermeszlab_r8-confg (Timed out)
Nov 1 16:24:49.315: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/hermeszlab_r8-confg) failed
%Error opening tftp://255.255.255.255/hermeszl.cfg (Timed out)
Nov 1 16:25:10.319: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/hermeszl.cfg) failed

How do I kill the boot processes?

I have also been trying to find where I can view the directories where various config files are stored.

SH Flash does not display anything other than the IOS Image.

John

[lammle]

This "feature" happens because your router senses carrier detect on a serial interface and uses the Cisco proprietary protocol called SLARP (serial link ARP). Once it find the remote end IP, the interface on your router assigns itself the next IP address in the range, and enables itself.
Now remember, the router thinks it is doing you a favor here....but wait, it's not done trying to help you out.
After it finds the neighbors IP address and assigns your interface an IP address and enables it, the router then tried to do a reverse DNS lookup using that IP Address, that is the 255.255.255.255 you see over and over again. If by chance that it finds a DNS server and resolved the IP address to a name, it assigns that name as the hostname of your router. At this point the router will then broadcast looking for a DNS server looking for a configuration with the hostname that it found with an extension of hostname-confg. If it find this on the tftp server, if downloads it and puts it in running-config. Your router is supposedly up and running.
This "feature" was helpful about 15-19 years ago (early 1990's), but has outlived its usefulllness since more than one person in the world can now configure a Cisco router. At the time, there was maybe 100-150 Cisco techs in the world, so this could be useful if setup correctly.
To disable this use these two commands from global config:
no service config
no boot network

Now, I need to tell you, these commands works most of the time, but these commands don't work every time. If you reload your router a lot, it is possible that the autoinstall feature may pop up again. However, other than waiting 10-15 minutes for this to time out, it isn't hurting you or your router in any way. Go get a beer and/or shot of Crown Royal, come back and your router will be ready to be configured.

Good luck,
Cheers!
Todd Lammle

[Big Evil]

Go get a beer and/or shot of Crown Royal, come back and your router will be ready to be configured.

Hell yeah, thats what i'm thinking!!

[HermeszData]

Hell yeah, thats what i'm thinking!!

Unfortunately, economics have not allowed me the luxery of a drink in 10 weeks. I had to spend all my Scotch money on "Lab Hardware":(

And thanks to Todd. I have been looking for that info for the past 48 hours. those two commands resolved the issue completely.

When I set this router up initially, I did not use the auto config option. I manually entered the config. I did use the copy tftp mem option to bring in a running-config I had from another 1700 series. But, the router in question was doing this from the first bootup when I powered it on for the first time.

I have been working on the use of tftp (chapt 5, 6th Ed) I managed to get all the IOSs for my routers and switches backed up, except one 2600. Having "too much blood in my alcoholic system" caused me to load a newer IOS (the original was a 11.* version) before backing up the original. This router does not have enough memory to run the 12.3 version I loaded. Now I need to find an 11.* version or go without Scotch untils I can come up with enough money for the nevessary memory upgrades. I actually have 2 of these 2611s. One was missing the IOS to begin with!)

Maybe someone here could help with an older c2600 IOS?

Thanks again Todd. You book has been a great help in my studies. I am trying to do a FAST-TRACK to CCNP before June.

John

[lammle]

Hell yeah, thats what i'm thinking!!


Life's too short to watch a router try and auto-configure itself. :)

[Fuzz]

Depends on if you're paid by the hour or not ;)

[nsantana]

I picked up a 1721 to be able to run SDM. the router works fine and I have no issues other than:
%Error opening tftp://255.255.255.255/network-confg (Timed out)
Nov 1 16:16:25.343: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/network-confg) failed
%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)
Nov 1 16:16:46.347: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/cisconet.cfg) failed
%Error opening tftp://255.255.255.255/hermeszlab_r8-confg (Timed out)
Nov 1 16:17:07.299: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/hermeszlab_r8-confg) failed
%Error opening tftp://255.255.255.255/hermeszl.cfg (Timed out)
Nov 1 16:17:28.311: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/hermeszl.cfg) failed
%Error opening tftp://255.255.255.255/network-confg (Timed out)
Nov 1 16:24:07.351: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/network-confg) failed
%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)
Nov 1 16:24:28.355: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/cisconet.cfg) failed
%Error opening tftp://255.255.255.255/hermeszlab_r8-confg (Timed out)
Nov 1 16:24:49.315: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/hermeszlab_r8-confg) failed
%Error opening tftp://255.255.255.255/hermeszl.cfg (Timed out)
Nov 1 16:25:10.319: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tf
tp://255.255.255.255/hermeszl.cfg) failed

How do I kill the boot processes?

I have also been trying to find where I can view the directories where various config files are stored.

SH Flash does not display anything other than the IOS Image.

John




Check this

CSCeg04311

When you power on or restart a switch that does not have a config.text file in flash memory, the switch tries to get configuration files from a TFTP server. If the configuration files are not found, the switch automatically configures the service config global configuration command, which causes the switch to continue searching (in the background) for the expected configuration files.

If the service config command does not find the configuration files, these error messages appear:

%Error opening tftp://255.255.255.255/network-confg (Timed out)
%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)
%Error opening tftp://255.255.255.255/router-confg (Timed out)
%Error opening tftp://255.255.255.255/ciscortr.cfg (Timed out)

These system messages also appear:

00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from
(tftp://255.255.255.255/network-confg) failed
00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from
(tftp://255.255.255.255/cisconet.cfg) failed
00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from
(tftp://255.255.255.255/switch-confg) failed
00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from
(tftp://255.255.255.255/ciscortr.cfg) failed
These messages are for information only. There is no problem with the switch operation.

Because the switch automatically configures the service config global configuration command, it is in the switch startup-config file when you save the running-config file. This command runs every time the switch is restarted, even if a config.text configuration file is in the switch flash memory.

The workaround is to prevent these messages from being generated. To do this, enter the switch configuration mode, and issue the no service config command. Save the configuration to flash by using the copy running-config to startup-config command. The preceding error and system messages no longer appear and do not appear when the switch is restarted.

http://www.cisco.com/en/US/docs/switches/blades/cgesm/software/release/12.2_25_see1_2/release/notes/HP495516.html