Alternatively, perform the following task in user view to specify the next-startup configuration file:
Specify the next-startup
Backing up the next-startup configuration file to a
Before performing this task, make sure the following requirements are met:
The server is reachable and enabled with TFTP service.
You have read and write permissions.
This task backs up only the main next-startup configuration file.
To back up the next-startup configuration file to a TFTP server:
Verify that a next-startup
configuration file has been
specified in user view.
Back up the next-startup
configuration file to a TFTP
server in user view.
Deleting the next-startup configuration file
This task permanently deletes the next-startup configuration file from all member devices. Before
performing this task, back up the file as needed.
You can delete the main, the backup, or both. If the main and backup next-startup configuration files are
the same file, the system sets the attribute of the configuration file to NULL instead of deleting the file. You
can permanently delete the file after its attribute changes to NULL.
You may need to delete the next-startup configuration file for one of the following reasons:
After you upgrade system software, the file does not match the new system software.
The file is corrupted or is not fully compatible with the device.
Perform the following task in user view:
startup saved-configuration cfgfile
[ backup | main ]
backup startup-configuration to
dest-addr [dest-filename ]
The setting applies to all member
The configuration file must use
the .cfg extension and be saved in
the root directory of the flash.
If no next-startup configuration file
has been specified, the backup
operation will fail.
This command is not supported in