H3C Technologies H3C SecPath F1000-E - Manual (Page 64)

53
• Startup configuration files are corrupted, which is often caused by loading an incorrect
configuration file.
With startup configuration files deleted, the devices uses factory defaults at the next startup.
To delete a startup configuration file to be used at the next startup:
Task Command Remarks
Delete a startup configuration file
to be used at the next startup from
the storage medium.
reset saved-configuration Available in user view
CAUTION:
This command permanently deletes startup configuration files to be used at the next startup from the
device. Use it with caution.
Restoring a startup configuration file
The restore function allows you to copy a configuration file from a TFTP server to the device and specify
the file as the startup configuration file to be used at the next startup.
To restore a startup configuration file to be used at the next startup:
Task Command Remarks
Restore a startup configuration file
to be used at the next startup. restore startup-configuration from
src-addr src-filename
Available in user view
NOTE:
•
On a device that supports main and backup startup configuration files, the restore operation restores the
main startup configuration file.
• Before restoring a configuration file, ensure that the server is reachable, the server is enabled with TFTP
service, and the client has read and write permission.
• After execution of the command, use the display startup command (in user view) to verify that the
filename of the configuration file to be used at the next system startup is the same with that specified by
the
filename argument.
Displaying and maintaining a configuration file
Task Command Remarks
Display the information about
configuration rollback.
display archive configuration [ |
{ begin | exclude | include }
regular-expression ]
Available in any view