When one of the following situation occurs, your router "loses" its configuration
* power back on a router after power off for a while
* there is lightning strike around
* after configuring a router, you reload the router
* after installing new IOS image, you reload the router to let the new IOS image become active
You might want to check the config register value to verify if it is 0x2102 (the default) or else. When the config register value is not set as 0x2102, then the router might act differently than the default.
Following is an example. Let's say the router config register value is set to 0x2142. By having such value, the router will never load saved configuration every time the router boots up from either power up, power cycle, or reload command. The router ignores the saved configuration and instead boots up using default (blank) configuration.
Such abnormal behavior is typically unwanted at any time. To avoid the abnormal behavior, you need to set the value back to the 0x2102.
To find out what the current router config register value is, you can simply do a "show version" and look at the last line.
To set the value back to 0x2102 (default value), one way of doing it is via the CLI with following commands
configure terminal
config-register 0x2102
copy running-config startup-config
end
When the router has 0x2102 config register value, the router will act as factory recommended (Cisco recommended) including loading the current configuration after reload or power cycle.
Note:
When you are in luck, there is one possibility is that the router still has the configuration even though the router does not boot the configuration. This situation applies when the router configuration before reload or before power loss is saved (by issuing "copy running-config startup-config" or "write memory").
 feedback form
 feedback form
by aryoba 
last modified: 2009-08-13 08:56:52 |
