23
Troubleshooting configuration loss
This section provides troubleshooting information for common configuration management problems.
Startup configuration file failure
Symptom
The device starts up with factory defaults because both the main and backup startup configuration
files are not available or do not exist.
Solution
CAUTION:
Do not execute the
save
command before you complete the tasks in this section. The save
operation overwrites the restored startup configuration file with the running configuration.
To resolve the issue:
1.
Transfer a backup copy of the startup configuration file to the root directory of the default
storage medium on each MPU:
IMPORTANT:
The device loads startup configuration files from the default storage medium.
•
Make sure all MPUs use the same type of storage medium as the default storage medium. In this
section, the flash memory is used on each MPU.
•
If a partitioned USB disk is used, make sure the configuration file is transferred to the root directory of
the first partition on the USB disk.
a.
Download configuration file
config.cfg
from the FTP server to the root directory of the flash
memory on the active MPU.
<Sysname> ftp 192.168.29.1
Press CTRL+C to abort.
Connected to 192.168.29.1 (192.168.29.1).
220 WFTPD 2.0 service (by Texas Imperial Software) ready for new user
User (192.168.29.1:(none)): 1
331 Give me your password, please
Password:
230 Logged in successfully
Remote system type is MSDOS.
ftp> binary
200 Type is Image (Binary)
ftp> get config.cfg flash:/config.cfg
227 Entering Passive Mode (192,168,29,1,209,24)
150 "F:\config.cfg" file ready to send (18494 bytes) in IMAGE / Binary mode
226 Transfer finished successfully.
18494 bytes received in 0.0383 seconds (471.1 kbyte/s)
ftp> quit
