Login
- Table of Contents
-
- 01-Fundamentals Command Reference
- 00-Preface
- 01-CLI commands
- 02-RBAC commands
- 03-Login management commands
- 04-FTP and TFTP commands
- 05-File system management commands
- 06-Configuration file management commands
- 07-Software upgrade commands
- 08-ISSU commands
- 09-Emergency shell commands
- 10-Automatic configuration commands
- 11-Device management commands
- 12-Security zone commands
- 13-Tcl commands
- 14-Python commands
- 15-License management commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 06-Configuration file management commands | 106.42 KB |
Configuration file management commands
archive configuration interval
archive configuration location
display current-configuration diff
Configuration file management commands
archive configuration
Use archive configuration to manually archive the running configuration to the configuration archive directory.
Syntax
archive configuration
Views
User view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
Before executing this command, you must use the archive configuration location command to specify a directory and a name prefix for the configuration archives.
The archive configuration command saves the running configuration to the specified configuration archive directory with file names generated from the specified name prefix.
Configuration archive facilitates configuration rollback. It provides manual and automatic methods for saving the running configuration as checkpoint references. For more information about the archiving mechanism, see the section about configuration rollback in Fundamentals Configuration Guide.
Examples
# Archive the running configuration.
<Sysname> archive configuration
Save the running configuration to an archive file. Continue? [Y/N]: Y
The archive configuration file myarchive_1.cfg is saved.
Related commands
archive configuration interval
archive configuration location
archive configuration max
display archive configuration
archive configuration interval
Use archive configuration interval to enable automatic running-configuration archiving and set the archiving interval.
Use undo archive configuration interval to disable automatic running-configuration archiving.
Syntax
archive configuration interval interval
undo archive configuration interval
Default
The automatic running-configuration archiving feature is disabled.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
interval: Specifies the interval for automatically saving the running configuration. The value range is 10 to 525600, in minutes.
Usage guidelines
Before enabling automatic configuration archiving, use the archive configuration location command to specify the configuration archive directory and archive file name prefix.
Configuration archive is a feature that facilitates configuration rollback. It provides manual and automatic methods for saving the running configuration.
Automatic configuration archiving enables the system to periodically save the running configuration to the archive directory. After the system finishes an automatic archive, it resets the archiving interval timer. For more information about the archiving mechanism, see the section about configuration rollback in Fundamentals Configuration Guide.
Change the archiving interval depending on the available amount of storage space. The shorter the interval, the more amount of free storage space is required.
Examples
# Set the system to archive the running configuration every 60 minutes.
<Sysname> system-view
[Sysname] archive configuration interval 60
Archive files will be saved every 60 minutes.
Related commands
archive configuration
archive configuration location
archive configuration max
display archive configuration
archive configuration location
Use archive configuration location to set the directory and file name prefix for archiving the running configuration.
Use undo archive configuration location to restore the default.
Syntax
archive configuration location directory filename-prefix filename-prefix
undo archive configuration location
Default
No configuration archive directory or configuration archive file name prefix is set.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
directory: Specifies the name of a configuration archive directory, a case-insensitive string of 1 to 63 characters. The value for this argument must take the format storage-medium-name:/folder-name. The directory must already exist on the active MPU. (In standalone mode.)
directory: Specifies the name of a configuration archive directory, a case-insensitive string of 1 to 63 characters. The value for this argument must take the format storage-medium-name:/folder-name. The directory must already exist on the global active MPU. (In IRF mode.)
filename-prefix: Specifies a file name prefix for configuration archives, a case-insensitive string of 1 to 30 characters. Valid characters are letters, digits, underscores (_), and hyphens (-).
Usage guidelines
Before archiving the running configuration, either manually or automatically, you must set a directory and file name prefix for configuration archives.
(In standalone mode.) The configuration archive feature saves the running configuration only on the active MPU. To make sure the system can archive running configuration after an active/standby switchover, create the configuration archive directory on both MPUs.
(In IRF mode.) The configuration archive feature saves the running configuration only on the global active MPU. To make sure the system can archive running configuration after an active/standby or master/subordinate switchover, create the configuration archive directory on all MPUs.
Configuration archives take the file name format prefix_serial number.cfg, for example, 20080620archive_1.cfg and 20080620archive_2.cfg. The serial number is automatically assigned from 1 to 1000, increasing by 1. After the serial number reaches 1000, it restarts from 1.
After you change the file directory or file name prefix, or reboot the device, all of the following events occur:
· The old configuration archives are regarded as common configuration files.
· The configuration archive counter is reset.
· The display archive configuration command no longer displays the old configuration archives.
· The serial number for new configuration archives starts at 1.
The undo archive configuration location command removes the configuration archive directory and file name prefix settings. The command also performs the following operations:
· Disables the configuration archive feature (both manual and automatic methods).
· Restores the default settings of the archive configuration interval and archive configuration max commands.
· Clears the configuration archive information displayed by using the display archive configuration command.
Examples
# Set the configuration archive directory as cfa0:/archive and the archive file name prefix as my_archive.
<Sysname> mkdir cfa0:/archive
Creating directory cfa0:/archive... Done.
<Sysname> system-view
[Sysname] archive configuration location cfa0:/archive filename-prefix my_archive
Related commands
archive configuration
archive configuration location
archive configuration max
display archive configuration
archive configuration max
Use archive configuration max to set the maximum number of configuration archives.
Use undo archive configuration max to restore the default.
Syntax
archive configuration max file-number
undo archive configuration max
Default
The maximum number is 5.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
file-number: Specifies the maximum number of configuration archives that can be saved. The value range is 1 to 10. Adjust the setting depending on the amount of storage space available.
Usage guidelines
Before you can set a limit on configuration archives, use the archive configuration location command to specify a configuration archive directory and archive file name prefix.
After the maximum number of configuration archives is reached, the system deletes the oldest archive for the new archive.
Changing the limit setting to a lower value does not cause immediate deletion of excess archives. Instead, the configuration archive feature deletes the oldest n files when a new archive is manually or automatically saved, where n = current archive count – new archive limit + 1. For example, seven configuration archives have been saved before the archive limit is set to four. When saving a new configuration archive, the system first deletes the oldest four (7 – 4 + 1) archives.
If you execute the undo archive configuration location command, the default archive limit is restored.
Examples
# Set the maximum number of configuration archives to 10.
<Sysname> system-view
[Sysname] archive configuration max 10
Related commands
archive configuration
archive configuration location
archive configuration interval
display archive configuration
backup startup-configuration
Use backup startup-configuration to back up the main next-startup configuration file to a TFTP server.
Syntax
backup startup-configuration to { ipv4-server | ipv6 ipv6-server } [ dest-filename ] [ vpn-instance vpn-instance-name ]
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
ipv4-server: Specifies a TFTP server by its IPv4 address or host name. The host name is a case-insensitive string of 1 to 253 characters. Valid characters include letters, digits, hyphens (-), underscores (_), and dots (.).
ipv6 ipv6-server: Specifies a TFTP server by its IPv6 address or host name. The host name is a case-insensitive string of 1 to 253 characters. Valid characters include letters, digits, hyphens (-), underscores (_), and dots (.).
dest-filename: Specifies the target file name used for saving the file on the server. The file name must use the .cfg extension. If you do not specify a target file name, the source file name is used.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify an MPLS L3VPN instance, this command backs up the main next-startup configuration file to a TFTP server in the public network.
Usage guidelines
This command is not supported in FIPS mode.
Examples
# Back up the main next-startup configuration file to the IPv4 TFTP server at 2.2.2.2 in the public network, and set the target file name to 192-168-1-26.cfg.
<Sysname> backup startup-configuration to 2.2.2.2 192-168-1-26.cfg
Backing up the main startup configuration file to 2.2.2.2...
Done.
# Back up the main next-startup configuration file to the IPv4 TFTP server at 2.2.2.2 in MPLS L3VPN instance VPN1, and set the target file name to 192-168-1-26.cfg.
<Sysname> backup startup-configuration to 2.2.2.2 192-168-1-26.cfg vpn-instance VPN1
Backing up the main startup configuration file to 2.2.2.2 in VPN VPN1...
Done.
# Back up the main next-startup configuration file to the IPv6 TFTP server at 2001::2 in the public network, and set the target file name to 192-168-1-26.cfg.
<Sysname> backup startup-configuration to ipv6 2001::2 192-168-1-26.cfg
Backing up the main startup configuration file to 2001::2...
Done.
Related commands
restore startup-configuration
configuration encrypt
Use configuration encrypt to enable configuration encryption.
Use undo configuration encrypt to disable configuration encryption.
Syntax
configuration encrypt { private-key | public-key }
undo configuration encrypt
Default
Configuration encryption is disabled. The running configuration is saved to a configuration file without encryption.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
private-key: Encrypts configuration with a private key. All devices running Comware 7 software use the same private key.
public-key: Encrypts configuration with a public key. All devices running Comware 7 software use the same public key.
Usage guidelines
Configuration encryption enables the device to automatically encrypt a configuration file when saving the running configuration to the file.
Any devices running Comware 7 software can decrypt the encrypted configuration file. To prevent an encrypted file from being decoded by unauthorized users, make sure the file is accessible only to authorized users.
Examples
# Enable the public-key method for configuration encryption.
<Sysname> system-view
[Sysname] configuration encrypt public-key
configuration replace file
Use configuration replace file to perform configuration rollback.
Syntax
configuration replace file filename
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
filename: Specifies the name of the replacement configuration file suffixed with the .cfg extension for configuration rollback. Excluding the .cfg extension, the file name is a case-insensitive string of 1 to 255 characters and can include path information. Valid characters include letters, digits, hyphens (-), underscores (_), and dots (.). If the file path includes a folder name, the folder must already exist.
Usage guidelines
To replace the running configuration with the configuration in a configuration file without rebooting the device, use the configuration rollback feature. This feature helps you revert to a previous configuration state or adapt the running configuration to different network environments.
To ensure a successful rollback, follow these guidelines:
· Make sure the replacement configuration file is created by using the configuration archive feature or the save command on the device.
· If the configuration file is not created on the device, make sure the command lines in the configuration file are fully compatible with the device.
· Make sure the replacement configuration file is not encrypted.
Examples
# Replace the running configuration with the configuration in the my_archive_1.cfg configuration file.
<Sysname> system-view
[Sysname] configuration replace file my_archive_1.cfg
Current configuration will be lost, save current configuration? [Y/N]:n
Now replacing the current configuration. Please wait...
Succeeded in replacing current configuration with the file my_archive_1.cfg.
display archive configuration
Use display archive configuration to display configuration archive information.
Syntax
display archive configuration
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Examples
# Display configuration archive information.
<Sysname> display archive configuration
Location: cfa0:/archive
Filename prefix: my_archive
Archive interval in minutes: 120
Maximum number of archive files: 10
Saved archive files:
No. TimeStamp FileName
1 Wed Jan 15 14:20:18 2012 my_archive_1.cfg
2 Wed Jan 15 14:33:10 2012 my_archive_2.cfg
# 3 Wed Jan 15 14:49:37 2012 my_archive_3.cfg
'#' indicates the most recent archive file.
Next archive file to be saved: my_archive_4.cfg
|
Field |
Description |
|
Location |
Absolute path of the directory for saving running-configuration archives. |
|
Filename prefix |
File name prefix for configuration archives. |
|
Archive interval in minutes |
Interval (in minutes) for the system to automatically archive the running configuration. If automatic configuration saving is disabled, this field is not available. |
|
Maximum number of archive files |
Maximum number of configuration archives that can be saved. |
|
Saved archive files |
Configuration archives that have been saved. |
|
TimeStamp |
Time when the configuration archive was created. |
Related commands
archive configuration
archive configuration interval
archive configuration location
archive configuration max
display current-configuration
Use display current-configuration to display the running configuration.
Syntax
display current-configuration [ configuration [ module-name ] | controller | exclude-provision | interface [ interface-type [ interface-number ] ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
configuration [ module-name ]: Displays feature configuration. The module-name argument specifies a feature module. If you do not specify a feature module, the command displays all feature settings you have made.
controller: Displays OpenFlow port configuration.
exclude-provision: Excludes preprovisioned settings from the running configuration.
interface [ interface-type [ interface-number ] ]: Displays interface configuration, where the interface-type argument represents the interface type and the interface-number argument represents the interface number. If you do not specify the interface-type interface-number arguments, the command displays the running configuration for all interfaces. If you specify only the interface-type argument, the command displays the running configuration for all interfaces of this type.
Usage guidelines
Use this command to verify the configuration you have made.
If the system has automatically changed the setting you have made for a parameter, this command displays the effective setting instead of the configured one. An automatic change typically occurs because of system restrictions.
This command does not display parameters that are using the default settings.
Examples
# Display local user configuration.
<Sysname> display current-configuration configuration local-user
#
local-user ftp
password hash $h$6$Twd73mLrN8O2vvD5$Cz1vgdpR4KoTiRQNE9pg33gU14Br2p1VguczLSVyJLO2huV5Syx/LfDIf8ROLtVErJ/C31oq2rFtmNuyZf4STw==
service-type ftp
authorization-attribute user-role network-operator
#
local-user root
password hash $h$6$Twd73mLrN8O2vvD5$Cz1vgdpR4KoTiRQNE9pg33gU14Br2p1VguczLSVyJLO2huV5Syx/LfDIf8ROLtVErJ/C31oq2rFtmNuyZf4STw==
service-type ssh telnet terminal
authorization-attribute user-role network-admin
#
return
# Display GigabitEthernet interface configuration.
<Sysname> display current-configuration interface gigabitethernet
#
interface GigabitEthernet2/1/1
port link-mode route
#
return
display current-configuration diff
Use display current-configuration diff to display the differences that the running configuration has as compared with the next-startup configuration.
Syntax
display current-configuration diff
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Usage guidelines
This command searches for the next-startup configuration in the following order:
1. The main next-startup configuration file.
2. The backup next-startup configuration file if the main next-startup configuration file is unavailable.
If both the main and backup next-startup configuration files are unavailable, the system displays a message indicating that no next-startup configuration files exist.
Examples
# Display the differences that the running configuration has as compared with the next-startup configuration.
<Sysname> display current-configuration diff
--- Startup configuration
+++ Current configuration
@@ -17,7 +17,9 @@
#
vlan 200
#
-vlan 300
+vlan 400
+#
+vlan 500
#
interface GigabitEthernet2/1/1
#
<Sysname>
The output shows that the running configuration contains VLAN 400 and VLAN 500 while the next-startup configuration contains VLAN 300.
|
Field |
Description |
|
- - - A +++ B |
· A represents the source configuration for comparison, which can be Startup configuration, Current configuration, or the name of the source configuration file with its directory information. · B represents the target configuration for comparison, which can be Current configuration, Startup configuration, or the name of the target configuration file with its directory information. |
|
@@ -linenumber1,number1 +linenumber2,number2 @@ |
Location summary for sections that contain command line differences: · -linenumber1,number1—Source configuration section that contains differences. The linenumber1 argument represents the start line of the section. The number1 argument represents the number of lines between the start line and the end line of the section. · +linenumber2,number2—Target configuration section that contains differences. The linenumber2 argument represents the start line of the section. The number2 argument represents the number of lines between the start line and the end line of the section. |
|
cmd1 - cmd2 + cmd3 cmd4 |
Displays command differences. · cmd1 and cmd4—Command lines are contained in both source and target configurations if they are not prefixed with a minus (-) or plus (+) sign. They provide a context for locating command line differences. · - cmd2—Command lines are prefixed with a minus sign if they are contained in the source configuration but not in the target configuration. · + cmd3—Command lines are prefixed with a plus sign if they are contained in the target configuration but not in the source configuration. |
Related commands
display current-configuration
display diff
display saved-configuration
display diff
Use display diff to display differences between configurations.
Syntax
display diff current-configuration { configfile file-name-d | startup-configuration }
display diff startup-configuration { configfile file-name-d | current-configuration }
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
configfile file-name-s: Specifies the source configuration file for comparison.
configfile file-name-d: Specifies the target configuration file for comparison.
current-configuration: Specifies the running configuration. In the display diff current-configuration command, this keyword specifies the source configuration for comparison. In the display diff configfile file-name-s and display diff startup-configuration commands, this keyword specifies the target configuration.
startup-configuration: Specifies the next-startup configuration. In the display diff startup-configuration command, this keyword specifies the source configuration for comparison. In the display diff configfile file-name-s and display diff current-configuration commands, this keyword specifies the target configuration.
Usage guidelines
If you specify the startup-configuration keyword, the system searches for the next-startup configuration for comparison in the following order:
1. The main next-startup configuration file.
2. The backup next-startup configuration file if the main next-startup configuration file is unavailable.
If both the main and backup next-startup configuration files are unavailable, the system displays a message indicating that no next-startup configuration files exist.
Examples
# Display the differences between startup.cfg and test.cfg.
<Sysname> display diff configfile startup.cfg configfile test.cfg
--- cfa0:/startup.cfg
+++ cfa0:/test.cfg
@@ -17,7 +17,9 @@
#
vlan 200
#
-vlan 300
+vlan 400
+#
+vlan 500
#
interface GigabitEthernet2/1/1
#
<Sysname>
The output shows that test.cfg contains VLAN 400 and VLAN 500 while startup.cfg contains VLAN 300.
# Display the differences between the running configuration and the next-startup configuration.
<Sysname> display diff current-configuration startup-configuration
--- Current configuration
+++ Startup configuration
@@ -17,9 +17,7 @@
#
vlan 200
#
-vlan 400
-#
-vlan 500
+vlan 300
#
interface GigabitEthernet2/1/1
#
<Sysname>
The output shows that the running configuration contains VLAN 400 and VLAN 500 while the next-startup configuration contains VLAN 300.
For the command output description, see Table 2.
Related commands
display current-configuration diff
display saved-configuration
Use display saved-configuration to display the contents of the configuration file for the next system startup.
Syntax
display saved-configuration
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Usage guidelines
Use this command to verify that important settings have been saved to the configuration file for the next system startup.
This command selects the configuration file to display in the following order:
1. If the main startup configuration file is available, this command displays the contents of the main startup configuration file.
2. If only the backup startup configuration file is available, this command displays the contents of the backup file.
3. If both the main and backup startup configuration files are not available, this command does not display anything.
Examples
# Display the contents of the configuration file for the next system startup.
<Sysname> display saved-configuration
#
version 7.1.054, E7102P02
#
sysname Sysname
#
mdc Admin id 1
#
ftp server enable
#
telnet server enable
#
domain default enable system
#
vlan 1
#
domain system
#
---- More ----
Related commands
reset saved-configuration
save
display startup
Use display startup to display the names of the current startup configuration file and the next-startup configuration files.
Syntax
display startup
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Usage guidelines
Current startup configuration file is the configuration file that has been loaded. Next-startup configuration file is the configuration file used at the next startup.
(In standalone mode.) The standby MPU always uses the same current startup configuration file as the active MPU. After an active/standby switchover, it is normal that the current startup configuration files on the MPUs are displayed as NULL. This is because the new active MPU continues to run with the running configuration rather than rebooting with a startup configuration file.
(In IRF mode.) The global standby MPUs always use the same current startup configuration file as the global active MPU. After an active/standby switchover, it is normal that the current startup configuration files on all MPUs are displayed as NULL. This is because the new global active MPU continues to run with the running configuration rather than rebooting with a startup configuration file.
Examples
# (In standalone mode.) Display names of the startup configuration files.
<Sysname> display startup
MainBoard:
Current startup saved-configuration file: cfa0:/startup.cfg
Next main startup saved-configuration file: cfa0:/startup.cfg
Next backup startup saved-configuration file: NULL
Slot 1:
Current startup saved-configuration file: cfa0:/startup.cfg
Next main startup saved-configuration file: cfa0:/startup.cfg
Next backup startup saved-configuration file: NULL
Table 3 Command output
|
Field |
Description |
|
MainBoard |
Displays the startup configuration files on the active MPU. |
|
Current startup saved-configuration file |
Configuration file that the active MPU has started up with. |
|
Next main startup saved-configuration file |
Primary startup configuration file to be used at the next startup. |
|
Next backup startup saved-configuration file |
Backup startup configuration file to be used at the next startup. |
|
Slot n |
Displays the startup configuration files on the MPU in slot n. |
# (In IRF mode.) Display names of the startup configuration files.
<Sysname> display startup
MainBoard:
Current startup saved-configuration file: NULL
Next main startup saved-configuration file: cfa0:/startup.cfg
Next backup startup saved-configuration file: cfa0:/startup2.cfg
Chassis 2 Slot 0:
Current startup saved-configuration file: NULL
Next main startup saved-configuration file: cfa0:/startup.cfg
Next backup startup saved-configuration file: cfa0:/startup2.cfg
Table 4 Command output
|
Field |
Description |
|
MainBoard |
Displays the startup configuration files on the global active MPU. |
|
Current startup saved-configuration file |
Configuration file that the global active MPU has started up with. |
|
Next main startup saved-configuration file |
Primary configuration file to be used at the next startup. |
|
Next backup startup saved-configuration file |
Backup configuration file to be used at the next startup. |
|
(This file does not exist.) |
If the specified next-startup configuration file has been deleted, this comment appears next to the file name. |
|
Chassis x Slot n |
Displays the startup configuration files on the MPU in slot n of IRF member x. |
Related commands
startup saved-configuration
display this
Use display this to display the running configuration in the current view.
Syntax
display this
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Usage guidelines
Use this command to verify the configuration you have made in a certain view.
This command does not display parameters that are using the default settings.
Some parameters can be successfully set even if their dependent features are not enabled. For these parameters, this command displays their settings after the dependent features are enabled.
This command can be executed in any user line view to display the running configuration of all user lines.
Examples
# Display the running configuration on interface GigabitEthernet 2/1/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 2/1/1
[Sysname-GigabitEthernet2/1/1] display this
#
interface GigabitEthernet2/1/1
port link-mode route
#
return
# Display the running configuration on user lines.
<Sysname> system-view
[Sysname] line vty 0
[Sysname-line-vty0] display this
#
line aux 0
user-role network-operator
#
line con 0
user-role network-admin
#
line vty 0 4
authentication-mode none
user-role network-admin
#
return
reset saved-configuration
Use reset saved-configuration to delete a next-startup configuration file.
Syntax
reset saved-configuration [ backup | main ]
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
backup: Specifies the backup next-startup configuration file.
main: Specifies the main next-startup configuration file.
Usage guidelines
|
|
CAUTION: · (In standalone mode.) This command permanently deletes the specified next-startup configuration file from the device. · (In IRF mode.) This command permanently deletes the specified next-startup configuration file from all IRF member devices. |
You can delete the main file, the backup file, or both.
To delete a file that is set as both main and backup next-startup configuration files, you must execute both the reset saved-configuration backup command and the reset saved-configuration main command. Using only one of the commands removes the specified file attribute instead of deleting the file.
For example, if the reset saved-configuration backup command is executed, the backup next-startup configuration file setting is set to NULL. However, the file is still used as the main file. To delete the file, you must also execute the reset saved-configuration main command.
If you do not specify a configuration file attribute, the reset saved-configuration command deletes the main next-startup configuration file.
Examples
# (In standalone mode.) Delete the main next-startup configuration file.
<Sysname> reset saved-configuration
The saved configuration file will be erased. Are you sure? [Y/N]:y
Configuration file in cfa0: is being cleared.
Please wait ...
..
MainBoard:
Configuration file is cleared.
Slot 1:
Erase next configuration file successfully
# (In IRF mode.) Delete the backup next-startup configuration file.
<Sysname> reset saved-configuration backup
The saved configuration file will be erased. Are you sure? [Y/N]:y
Configuration file in cfa0: is being cleared.
Please wait ...
..
MainBoard:
Configuration file is cleared.
Chassis 2 Slot 2:
Erase next configuration file successfully
Related commands
display saved-configuration
restore startup-configuration
Use restore startup-configuration to download a configuration file from a TFTP server and specify it as the main next-startup configuration file.
Syntax
restore startup-configuration from { ipv4-server | ipv6 ipv6-server } src-filename [ vpn-instance vpn-instance-name ]
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
ipv4-server: Specifies a TFTP server by its IPv4 address or host name. The host name is a case-insensitive string of 1 to 253 characters. Valid characters include letters, digits, hyphens (-), underscores (_), and dots (.).
ipv6 ipv6-server: Specifies a TFTP server by its IPv6 address or host name. The host name is a case-insensitive string of 1 to 253 characters. Valid characters include letters, digits, hyphens (-), underscores (_), and dots (.).
src-filename: Specifies the file name of the configuration file to be downloaded suffixed with the .cfg extension. Excluding the .cfg extension, the file name is a case-insensitive string of 1 to 255 characters. Valid characters include letters, digits, hyphens (-), underscores (_), and dots (.).
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify an MPLS L3VPN instance, this command downloads a configuration file from a TFTP server in the public network.
Usage guidelines
This command is not supported in FIPS mode.
Before restoring the configuration file for the next startup, make sure the following requirements are met:
· The server is reachable.
· The server is enabled with TFTP service.
· You have read and write permissions to the server.
This command downloads the configuration file to the root directory of the default storage medium on each MPU and specifies the file as the main next-startup configuration file.
Make sure all MPUs use the same type of default storage medium. If a standby MPU uses a different type of default storage medium than the active MPU, the command cannot propagate the configuration file to the standby MPU. For example, the standby MPU uses a CF card, but the active MPU uses a USB disk. In this situation, you must manually restore the main next-startup configuration file on the standby MPU.
Examples
# (In standalone mode.) Download config.cfg from the IPv4 TFTP server at 2.2.2.2 in the public network, and specify the file as the main next-startup configuration file.
<Sysname> restore startup-configuration from 2.2.2.2 config.cfg
Restoring the main startup configuration file from 2.2.2.2. Please wait...finished.
Now restoring the next startup-configuration file from main board to backup board...
Done.
# (In standalone mode.) Download test.cfg from the IPv4 TFTP server at 2.2.2.2 in MPLS L3VPN instance VPN1, and specify the file as the main next-startup configuration file.
<Sysname> restore startup-configuration from 2.2.2.2 test.cfg vpn-instance VPN1
Restoring the main startup configuration file from 2.2.2.2 in VPN VPN1...
Now restoring the main startup configuration file from main board to backup board...
Done.
# (In standalone mode.) Download test.cfg from the IPv6 TFTP server at 2001::2 in the public network, and specify the file as the main next-startup configuration file.
<Sysname> restore startup-configuration from ipv6 2001::2 test.cfg
Restoring the main startup configuration file from 2001::2...
Now restoring the main startup configuration file from main board to backup board...
Done.
# (In IRF mode.) Download config.cfg from the IPv4 TFTP server at 2.2.2.2 in the public network, and specify the file as the main next-startup configuration file.
<Sysname> restore startup-configuration from 2.2.2.2 config.cfg
Restoring the main startup configuration file from 2.2.2.2...
Now restoring the main startup configuration file from main board to backup board...
Done.
# (In IRF mode.) Download test.cfg from the IPv4 TFTP server at 2.2.2.2 in MPLS L3VPN instance VPN1, and specify the file as the main next-startup configuration file.
<Sysname> restore startup-configuration from 2.2.2.2 test.cfg vpn-instance VPN1
Restoring the main startup configuration file from 2.2.2.2 in VPN VPN1...
Now restoring the main startup configuration file from main board to backup board...
Done.
# (In IRF mode.) Download test.cfg from the IPv6 TFTP server at 2001::2 in the public network, and specify the file as the main next-startup configuration file.
<Sysname> restore startup-configuration from ipv6 2001::2 test.cfg
Restoring the main startup configuration file from 2001::2...
Now restoring the main startup configuration file from main board to backup board...
Done.
Related commands
backup startup-configuration
save
In standalone mode:
Use save file-url [ all | slot slot-number ] to save the running configuration to a configuration file, without specifying the file as a next-startup configuration file.
Use save [ safely ] [ backup | main ] [ force ] [ mdc-all | changed ] to save the running configuration to a file in the root directory of the storage medium. This command automatically saves the file on each MPU and specifies the file as a next-startup configuration file.
In IRF mode:
Use save file-url [ all | chassis chassis-number slot slot-number ] to save the running configuration to a configuration file, without specifying the file as a next-startup configuration file.
Use save [ safely ] [ backup | main ] [ force ] [ mdc-all | changed ] to save the running configuration to a file in the root directory of the storage medium. This command automatically saves the file on each MPU in an IRF fabric and specifies the file as a next-startup configuration file.
Syntax
In standalone mode:
save file-url [ all | slot slot-number ]
save [ safely ] [ backup | main ] [ force ] [ mdc-all | changed ]
In IRF mode:
save file-url [ all | chassis chassis-number slot slot-number ]
save [ safely ] [ backup | main ] [ force ] [ mdc-all | changed ]
Views
Any view
Predefined user roles
network-admin
mdc-admin
Parameters
file-url: Specifies a file path for saving the running configuration. The file name must use the .cfg extension. Excluding the .cfg extension, the file name is a case-insensitive string of 1 to 255 characters. Valid characters include letters, digits, hyphens (-), underscores (_), and dots (.). If you specify the all keyword or the slot slot-number option, the file path cannot include a slot number. If the file path includes a folder name, the folder must already exist on both MPUs. (In standalone mode.)
file-url: Specifies a file path for saving the running configuration. The file name must use the .cfg extension. Excluding the .cfg extension, the file name is a case-insensitive string of 1 to 255 characters. Valid characters include letters, digits, hyphens (-), underscores (_), and dots (.). If you specify the all keyword or the chassis chassis-number slot slot-number option, the file path cannot include a chassis or slot number. If the file path includes a folder name, the folder must already exist on all MPUs. (In IRF mode.)
all: Specifies both the active and standby MPUs. If you do not specify this keyword or the slot slot-number option, the command saves the running configuration only to the active MPU. (In standalone mode.)
all: Specifies all MPUs. If you do not specify this keyword or the chassis chassis-number slot slot-number option, the command saves the running configuration only to the global active MPU in the IRF fabric. (In IRF mode.)
slot slot-number: Specifies the standby MPU by its slot number. If you do not specify the standby MPU or the all keyword, this command saves the running configuration only to the active MPU. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a standby MPU on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the standby MPU. If you do not specify a standby MPU or the all keyword, this command saves the running configuration only to the global active MPU in the IRF fabric. (In IRF mode.)
safely: Saves the configuration file in safe mode. If you do not specify this keyword, the device saves the configuration file in fast mode. Safe mode is slower than fast mode, but more secure. As a best practice, specify the safely keyword for the command.
backup: Saves the running configuration to a configuration file, and specifies the file as the backup next-startup configuration file. If you do not specify this keyword or the main keyword, the command specifies the saved file as the main next-startup configuration file.
main: Saves the running configuration to a configuration file, and specifies the file as the main next-startup configuration file. If you do not specify this keyword or the backup keyword, the command specifies the saved file as the main next-startup configuration file.
force: Saves the running configuration to the existing next-startup configuration file without prompting for confirmation. If you do not specify this keyword, the system prompts you to confirm the operation. If you do not confirm the operation within 30 seconds, the system automatically aborts the operation. If you enter Y within the time limit, you can continue the save process and change the target file name during the process.
mdc-all: Saves the running configuration for each MDC. This keyword is available only on the default MDC. If this keyword is not available or you do not specify this keyword, the save command saves the running configuration only for the MDC where you are logged in.
changed: Overwrites the target configuration file with the running configuration if an inconsistency is detected between the settings in the configuration file and the running configuration. The save command does not take effect if no inconsistency is detected. If you do not specify this keyword, the save command always overwrites the target configuration file with the running configuration.
Usage guidelines
If the file specified for this command does not exist, the system creates the file before saving the configuration. If the file already exists, the system prompts you to confirm whether to overwrite the file. If you choose to not overwrite the file, the system cancels the save operation.
This command saves the running configuration to an .mdb binary file as well as a .cfg text file. The two files use the same file name. An .mdb file takes less time to load than a .cfg file.
In safe mode, the system saves configuration in a temporary file and starts overwriting the target next-startup configuration file after the save operation is complete. If a reboot, power failure, or out of memory or storage space event occurs during the save operation, the next-startup configuration file is retained.
In fast mode, the device directly overwrites the target next-startup configuration file. If a reboot, power failure, or out of memory or storage space event occurs during this process, all settings in the next-startup configuration file are lost.
Examples
# Save the running configuration to backup.cfg, without specifying the file as the next-startup configuration file.
<Sysname> save backup.cfg
The current configuration will be saved to cfa0:/backup.cfg. Continue? [Y/N]:y
Now saving current configuration to the device.
Saving configuration
Saving configuration cfa0:/backup.cfg. Please wait...
Configuration is saved to device successfully.
# Save the running configuration to the main next-startup configuration file without any confirmation required.
<Sysname> save force
Validating file. Please wait....
Saved the current configuration to mainboard device successfully.
# (In standalone mode.) Save the running configuration to a file in the root directory of the storage medium, and specify the file as the main next-startup configuration file.
<Sysname> save
The current configuration will be written to the device. Are you sure? [Y/N]:y
Please input the file name(*.cfg)[cfa0:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
Slot 1:
Save next configuration file successfully.
# (In IRF mode.) Save the running configuration to a file in the root directory of the storage medium, and specify the file as the main next-startup configuration file.
<Sysname> save
The current configuration will be written to the device. Are you sure? [Y/N]:y
Please input the file name(*.cfg)[cfa0:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
Chassis 1 Slot 1:
Save next configuration file successfully.
# Save the running configuration to a file in the root directory of the storage medium for each MDC, and specify the file as the main next-startup configuration file.
<Sysname> save mdc-all
Save current configuration in MDC Admin? [Y/N]:y
Please input the file name(*.cfg)[cfa0:/1.cfg]
(To leave the existing filename unchanged, press the enter key):
cfa0:/1.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration of mdc Admin to mainboard device successfully.
Chassis 1 Slot 1:
Save next configuration file successfully.
Save current configuration in MDC mdc1? [Y/N]:y
Please input the file name(*.cfg)[cfa0:/mdc1.cfg]
(To leave the existing filename unchanged, press the enter key):
cfa0:/mdc1.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration of mdc mdc1 to mainboard device successfully.
Chassis 1 Slot 1:
Save next configuration file successfully.
Related commands
display current-configuration
display saved-configuration
startup saved-configuration
Use startup saved-configuration to specify a file as a next-startup configuration file.
Use undo startup saved-configuration to set the system to start up with factory defaults at the next startup.
Syntax
startup saved-configuration cfgfile [ backup | main ]
undo startup saved-configuration
No next-startup configuration file is specified.
Views
Predefined user roles
network-admin
mdc-admin
Parameters
cfgfile: Specifies the name of a .cfg configuration file suffixed with the .cfg extension. Excluding the .cfg extension, the file name is a case-insensitive string of 1 to 255 characters. Valid characters include letters, digits, hyphens (-), underscores (_), and dots (.). If the file is not on the default storage medium, you must specify the file name with storage medium information.
backup: Specifies the configuration file as the backup next-startup configuration file.
main: Specifies the configuration file as the main next-startup configuration file. This is the primary configuration file that the device attempts to load at startup. If the loading attempt fails, the device tries the backup next-startup configuration file.
Usage guidelines
|
|
CAUTION: In an IRF fabric, use the undo startup saved-configuration command with caution. This command can cause an IRF split after the IRF fabric or an IRF member reboots. |
(In standalone mode.) The startup saved-configuration command applies to both MPUs. To successfully execute this command, make sure the specified file has been saved in the root directory of the storage medium on both the active MPU and standby MPU.
(In IRF mode.) The startup saved-configuration command applies to all MPUs. To successfully execute this command, make sure the specified file has been saved in the root directory of the storage medium on each MPU in the IRF fabric.
If you do not specify the backup or main keyword, the startup saved-configuration command specifies the main next-startup configuration file.
As a best practice, specify different files as the main and backup next-startup configuration files.
The undo startup saved-configuration command changes the file attribute of the main and backup next-startup configuration files to NULL. However, the command does not delete the two configuration files.
You can also specify a configuration file as a next startup file when you use the save command to save the running configuration.
Examples
# Specify the main next-startup configuration file.
<Sysname> startup saved-configuration testcfg.cfg
Please wait ....... Done!
Related commands
display startup
