Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 06-Configuration file management commands | 272.16 KB |
Contents
Configuration file management commands
archive configuration location
configuration exclusive by-user-name
configuration replace server file
configuration replace server password
configuration replace server user
display configuration exclusive by-user-name
display configuration replace server
display current-configuration diff
save current-configuration interval
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
Usage guidelines
Operating mechanism
This command saves the running configuration to the specified configuration archive directory with file names generated from the specified name prefix.
Restrictions and guidelines
Before executing this command, you must use one of the following methods to specify a directory and a name prefix for the configuration archives:
· For local archiving, use the archive configuration location command to specify a local configuration archive directory and a name prefix.
· For remote archiving, use the archive configuration server command to specify a configuration archive directory and a name prefix on a remote SCP server.
If you execute the archive configuration location command to specify a local configuration archive directory, manual configuration archiving saves the running configuration only on the master device.
Examples
# Archive the running configuration.
<Sysname> archive configuration
Save the running configuration to an archive file. Continue? [Y/N]: Y
The running configuration was saved to myarchive_1.cfg.
Related commands
archive configuration interval
archive configuration location
archive configuration max
archive configuration server
archive configuration server password
archive configuration server user
display archive configuration
archive configuration location
Use archive configuration location to configure the parameters for archiving the running configuration to a local directory.
Use undo archive configuration location to restore the default.
Syntax
archive configuration location directory filename-prefix filename-prefix [ max file-number ] [ interval interval ]
undo archive configuration location
Default
No local directory or file name prefix is specified on the device for archiving the running configuration.
Views
System view
Predefined user roles
network-admin
Parameters
directory: Specifies the archive directory, a string of 1 to 63 characters. The value for this argument must take the format of storage-medium-name:/folder-name. If you do not specify this argument, the system will automatically complete the archive directory and its length will be calculated. If the directory length exceeds 63 characters, the command execution will fail. The directory must already exist on the master device and the option cannot contain any member ID.
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 (-).
interval interval: Enables automatic running-configuration archiving and sets the archiving interval. The value range for the interval argument is 10 to 525600, in minutes. By default, automatic running-configuration archiving is disabled.
max file-number: Specifies the maximum number of configuration archives that can be saved on the device in the range of 1 to 10. Adjust the setting depending on the amount of storage space available. For devices with limited storage space, set a smaller value for the file-number argument. The default value for the file-number argument is 5.
Usage guidelines
Operating mechanism
You can use the following methods to archive the running configuration to a local directory:
· Manual configuration archiving: After you execute this command to specify the parameters for archiving the running configuration to a local directory, execute the archive configuration command for manual configuration archiving.
· Automatic configuration archiving: Specify the interval keyword to enable automatic running-configuration archiving. After you execute this command, the system saves the running configuration to the local archive directory at the interval specified by the interval argument. After the system finishes an automatic archive, it resets the archiving interval timer.
The local configuration archives on the device are named in the format of prefix_serial number.cfg, for example, archive_1.cfg and archive_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 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.
Restrictions and guidelines
The system saves the running configuration only on the master device.
After you execute the undo archive configuration location command, the output from the display archive configuration command will be cleared.
The archive configuration server and archive configuration location commands are mutually exclusive. To execute the archive configuration server command, you must restore the default for the archive configuration location command, and vice versa.
Examples
# Set the configuration archive directory as flash:/archive and the archive file name prefix as my_archive.
<Sysname> mkdir flash:/archive
Creating directory flash:/archive... Done.
<Sysname> system-view
[Sysname] archive configuration location flash:/archive filename-prefix my_archive
Related commands
archive configuration
display archive configuration
archive configuration server
Use archive configuration server to configure the parameters for archiving the running configuration to a remote server.
Use undo archive configuration server to restore the default.
Syntax
To archive the running configuration to a remote FTP server:
archive configuration server ftp [ user user-name password { cipher | simple } string ] { ipv4-address | ipv6 ipv6-address } [ port port-number ] [ vpn-instance vpn-instance-name ] [ directory directory ] filename-prefix filename-prefix [ interval interval ]
To archive the running configuration to a remote TFTP server:
archive configuration server tftp { ipv4-address | ipv6 ipv6-address } [ port port-number ] [ vpn-instance vpn-instance-name ] [ directory directory ] filename-prefix filename-prefix [ interval interval ]
To archive the running configuration to a remote SCP server:
archive configuration server scp user user-name password { cipher | simple } string { ipv4-address | ipv6 ipv6-address } [ port port-number ] [ vpn-instance vpn-instance-name ] [ directory directory ] filename-prefix filename-prefix [ interval interval ]
undo archive configuration server
Default
No parameters are set for archiving the running configuration to a remote server.
Views
System view
Predefined user roles
network-admin
Parameters
ftp: Specifies a remote FTP server.
tftp: Specifies a remote TFTP server.
scp: Specifies a remote SCP server.
ipv4-address: Specifies a remote server by its IPv4 address.
ipv6 ipv6-address: Specifies a remote server by its IPv6 address.
port port-number: Specifies the TCP port number of the remote server. The value range for the port-number argument is 1 to 65535. The default port number is 22 for a remote SCP server, 21 for a remote FTP server, and 69 for a remote TFTP server.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If the remote server is on the public network, do not specify this option.
directory directory: Specifies the archive directory, a case-insensitive string. The specified archive directory must have been created on the remote server.
· For a Linux SCP server, this option is required and the specified archive directory must be an absolute path.
· For a Windows SCP server, this option is optional and the specified archive directory must be a relative path. The default archive directory is the root directory of the SCP server.
filename-prefix 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 (-).
interval interval: Enables automatic running-configuration remote archiving and sets the archiving interval. The value range for the interval argument is 10 to 525600, in minutes. By default, automatic running-configuration remote archiving is disabled.
user user-name: Specifies the username for accessing the FTP or SCP server that stores the configuration archives, a case-sensitive string of 1 to 63 characters.
password: Configures the password for accessing the FTP or SCP server that stores the configuration archives.
cipher: Specifies a password in encrypted form.
simple: Specifies a password in plaintext form. For security purposes, the password specified in plaintext form will be stored in encrypted form.
string: Specifies the password. Its plaintext form is a case-sensitive string of 1 to 63 characters. Its encrypted form is a case-sensitive string of 33 to 117 characters.
Usage guidelines
Operating mechanism
You can use the following methods to archive the running configuration to a remote server:
· Manual configuration archiving: After you execute this command to specify the parameters for archiving the running configuration to a remote server, execute the archive configuration command for manual configuration archiving.
· Automatic configuration archiving: Specify the interval keyword to enable automatic running-configuration remote archiving. After you execute this command, the system saves the running configuration to the archive directory on the remote server at the interval specified by the interval argument. After the system finishes an automatic archive, it resets the archiving interval timer.
If you archive the running configuration to a remote server, configuration archives are named in the format of prefix_YYYYMMDD_HHMMSS.cfg (for example, archive_20170526_203430.cfg).
Restrictions and guidelines
If you use a remote TFTP, FTP, or SCP server, make sure the device is consistent with that server in, TFTP. FTP, or SCP settings. If a login username and password is configured on the server, you must specify that login username and password on the device.
The archive configuration server and archive configuration location commands are mutually exclusive. To execute the archive configuration server command, you must restore the default for the archive configuration location command, and vice versa.
If you execute this command multiple times, the most recent configuration takes effect.
After you execute the undo archive configuration server command, the output from the display archive configuration command will be cleared.
Examples
# Set the configuration archive directory as archive/ on the SCP server at 192.168.1.1 and set the archive file name prefix as my_archive.
<Sysname> system-view
[Sysname] archive configuration server scp user aaa password simple 123 192.168.1.1 port 22 directory /archive/ filename-prefix my_archive
# Set the configuration archive directory as archive/ on the FTP server at 192.168.1.1 and set the archive file name prefix as my_archive.
<Sysname> system-view
[Sysname] archive configuration server ftp user aaa password simple 123 192.168.1.1 port 22 directory /archive/ filename-prefix my_archive
Related commands
archive configuration
archive configuration location
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
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 name of the target file used for saving the file on the server. The file must be a .cfg file. The file name is a case-insensitive string of up to 255 characters. 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 the TFTP server is on the public network, do not specify this option.
Usage guidelines
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
undo configuration encrypt
Default
Configuration encryption is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
Operating mechanism
Configuration encryption enables the device to automatically encrypt a configuration file by using the master key when saving the running configuration to the file. For more information about the master key, see public key management in Security Configuration Guide.
Restrictions and guidelines
After a configuration file is encrypted by using this feature on the device, only devices that use the same master key as the device can decrypt the encrypted configuration file.
Examples
# Enable configuration encryption.
<Sysname> system-view
[Sysname] configuration encrypt
configuration exclusive by-user-name
Use configuration exclusive by-user-name to assign a user exclusive write access to the configuration.
Use undo configuration exclusive by-user-name to restore the default.
Syntax
configuration exclusive by-user-name user-name
undo configuration exclusive by-user-name user-name
Default
The configuration is not locked. No users have exclusive write access to the configuration.
Views
System view
Predefined user roles
network-admin
Parameters
user-name: Specifies a username, a case-sensitive string of 1 to 80 characters.
Usage guidelines
Application scenarios
In a multiuser environment, configuration conflicts or service exceptions might occur if multiple users are configuring the device.
To make sure only one user can change the running configuration, assign that user exclusive write access to the configuration. This setting locks the configuration. Then, all other users will have only read access to the configuration until the configuration is unlocked.
This command is available only for users that log in to the device through scheme authentication. Scheme authentication requires a username and password.
Restrictions and guidelines
Only one user can lock the configuration at a time.
To unlock the configuration, use the undo configuration exclusive by-user-name user-name command. The user-name argument must be the username that locked the configuration. To obtain this username, use the display configuration exclusive by-user-name command.
The configuration exclusive by-user-name command no longer takes effect after the device reboots. To use this command, you must reconfigure it.
Examples
# Assign user aaa exclusive write access to the configuration.
<Sysname> system-view
[Sysname] configuration exclusive by-user-name aaa
Related commands
display configuration exclusive by-user-name
configuration replace file
Use configuration replace file to perform configuration rollback.
Syntax
configuration replace file filename
Views
System view
Predefined user roles
network-admin
Parameters
filename: Specifies the path of the replacement configuration file, a string of up to 255 characters. The file must be a .cfg file. The file and file path must be valid and on the local system.
Usage guidelines
Prerequisites
Prepare the replacement configuration file. 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.
Operating mechanism
The configuration replace file command helps you revert to a previous configuration state or adapt the running configuration to different network environments without rebooting the device. Settings not in the replacement configuration file will be lost.
Restrictions and guidelines
This operation might cause service interruption. When you perform configuration rollback, make sure you fully understand its impact on your network.
If the replacement configuration file is encrypted, make sure the device can decrypt it.
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.
configuration replace server
Use configuration replace server to roll the running configuration back by using a configuration file on a remote server.
Use undo configuration replace server to restore the default.
Syntax
configuration replace server { ftp | tftp } { ipv4-address | ipv6 ipv6-address } [ port port-number ] [ vpn-instance vpn-instance-name ] [ directory directory ] file filename
undo configuration replace server
Default
No parameters are configured for remote configuration rollback.
Views
System view
Predefined user roles
network-admin
Parameters
ftp: Specifies a remote FTP server.
tftp: Specifies a remote TFTP server.
ipv4-address: Specifies the IPv4 address of the remote server.
ipv6 ipv6-address: Specifies the IPv6 address of the remote server.
port port-number: Specifies the TCP port number of the remote server, in the range of 1 to 65535. By default, the FTP port number is 21 and the TFTP port number is 69.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If the remote server is on the public network, do not specify this option.
directory directory: Specifies the remote rollback directory. The directory argument is a case-insensitive string. If you do not specify this option, the rollback directory is the root directory of the remote server.
file filename: Specifies the default replacement configuration file for running-configuration remote rollback. The filename argument is a case-insensitive string. The file must be a .cfg file.
Usage guidelines
If you use a remote FTP server, make sure the device is consistent with that FTP server in FTP settings. If a login username and password is configured on the FTP server, you must use the configuration replace server user and configuration replace server password commands to specify that login username and password on the device.
Examples
# Replace the running configuration with the configuration in the archive/ directory of the FTP server at 192.168.1.1.
<Sysname> system-view
[Sysname] configuration replace server ftp 192.168.1.1 port 22 directory /archive/ file my_archive_2017-05-09.cfg
Related commands
configuration replace server file
configuration replace server password
configuration replace server user
display configuration replace server
configuration replace server file
Use configuration replace server file to enable remote configuration rollback.
Use undo configuration replace server file to disable remote configuration rollback.
Syntax
configuration replace server file [ filename ] [ at time [ date ] ]
undo configuration replace server file
Default
Remote configuration rollback is disabled.
Views
System view
Predefined user roles
network-admin
Parameters
filename: Specifies a replacement configuration file by its name, a string of up to 255 characters. The file must be a .cfg file. If you do not specify a replacement configuration file, this command uses the default replacement configuration file specified by using the configuration replace server command for a rollback.
at time: Specifies the time at which the system downloads the replacement configuration file and performs configuration rollback. The time argument is in the format of HH:MM. HH represents the hours, in the range of 0 to 23. MM represents the minutes, in the range of 0 to 59.
date: Specifies the date on which the system downloads the replacement configuration file and performs configuration rollback. This argument is in the format of MM/DD/YYYY or YYYY/MM/DD. YYYY represents the year, in the range of 2000 to 2035. MM represents the month, in the range of 1 to 12. DD represents the day, in the range of 1 to N. The value for N depends on the month.
Usage guidelines
Operating mechanism
This command enables the device to perform the following operations:
1. Downloads the replacement configuration file from the remote rollback server.
2. Saves the downloaded file as a temporary file.
3. Replaces the running configuration with the configuration in the temporary file.
4. Deletes the temporary file after the configuration rollback finishes.
To perform an immediate configuration rollback, do not specify a rollback time or date. An immediate configuration rollback cannot be canceled.
To schedule a configuration rollback, specify a rollback time and optionally a date. A configuration rollback schedule can be canceled before the specified rollback time.
Restrictions and guidelines
The configuration rollback operation might cause service interruption. When you perform configuration rollback, make sure you fully understand its impact on your network.
When you schedule a rollback, follow these restrictions and guidelines:
· If you specify a rollback date with the rollback time, the specified date must be the same or later than the current system date. If the specified date is the same as the current system date, the specified time must be later than the current system time. After you create the rollback schedule, be careful with changing the system clock backward. The rollback schedule will be canceled automatically if it expires before it could be executed because the system date or time is changed backward.
· If you do not specify a rollback date with the rollback time, the device compares the specified rollback time with the current system time.
¡ If the specified rollback time is later than the current system time, the device performs a rollback at the specified time on the current day.
¡ If the specified rollback time is earlier than the current system time, the device performs a rollback at the specified time on the next day.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Roll back the running configuration immediately with the specified replacement configuration file on the remote server for configuration rollback.
<Sysname> system-view
[Sysname] configuration replace server file my_archive_2017-05-09.cfg
The running configuration will be lost. Do you want to save the running configuration? [Y/N]: N
Now replacing the running configuration...
Successfully replaced running configuration with file my_archive_2017-05-09.cfg.
Related commands
configuration replace server
configuration replace server password
configuration replace server user
configuration replace server password
Use configuration replace server password to configure the password for accessing the remote FTP server for configuration rollback.
Use undo configuration replace server password to restore the default.
Syntax
configuration replace server password { cipher | simple } string
undo configuration replace server password
Default
No password is configured for accessing the remote FTP server for remote configuration rollback.
Views
System view
Predefined user roles
network-admin
Parameters
cipher: Specifies a password in encrypted form.
simple: Specifies a password in plaintext form. For security purposes, the password specified in plaintext form will be stored in encrypted form.
string: Specifies the password. Its plaintext form is a case-sensitive string of 1 to 63 characters. Its encrypted form is a case-sensitive string of 33 to 117 characters.
Usage guidelines
Examples
# Set the password to admin in plaintext form for accessing the remote FTP server for configuration rollback.
<Sysname> system-view
[Sysname] configuration replace server password simple admin
Related commands
configuration replace server
configuration replace server file
configuration replace server user
configuration replace server user
Use configuration replace server user to specify the username for accessing the remote FTP server for configuration rollback.
Use undo configuration replace server user to restore the default.
Syntax
configuration replace server user user-name
undo configuration replace server user
Default
No username is configured for accessing the remote FTP server for configuration rollback.
Views
System view
Predefined user roles
network-admin
Parameters
user-name: Specifies the username, a case-sensitive string of 1 to 63 characters.
Usage guidelines
If no username is configured, the username will be anonymous.
Examples
# Set the username to admin for accessing the remote FTP server for configuration rollback.
<Sysname> system-view
[Sysname] configuration replace server user admin
Related commands
configuration replace server
configuration replace server file
configuration replace server password
display configuration replace server
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
Examples
# Display information about the configuration archives saved on the device.
<Sysname> display archive configuration
Location: flash:/archive
Filename prefix: my_archive
Archive interval in minutes: 120
Maximum number of archive files: 10
Archive history:
No. TimeStamp FileName
1 Jan 05 2020 20:24:54 my_archive_1.cfg
2 Jan 05 2020 20:34:54 my_archive_2.cfg
# 3 Jan 05 2020 20:44:54 my_archive_3.cfg
The pound sign (#) indicates the most recent archive file.
Next archive file to be saved: my_archive_4.cfg
# Display information about the configuration archives saved on a remote SCP server.
<Sysname> display archive configuration
Username: test
Location: scp://192.168.21.21:22/archive
Filename prefix: my_archive
Archive interval in minutes: 120
Archive history:
No. TimeStamp FileName
1 Wed Jan 15 14:20:18 2020 my_archive_20170509_142018.cfg
!2 Wed Jan 15 14:33:10 2020 my_archive_20170509_143018.cfg
#!3 Wed Jan 15 14:49:37 2020 my_archive_20170509_144018.cfg
The exclamation mark (!) indicates that the remote archiving attempt failed.
The pound sign (#) indicates the most recent archive file.
Table 1 Command output
|
Field |
Description |
|
Username |
Username for accessing the remote FTP or SCP server that stores the configuration archives. If the remote server is a TFTP server, this field is not available. |
|
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 on the device. |
|
Archive history |
History configuration archive information. |
|
No. |
Number of a configuration archive. |
|
TimeStamp |
Time when the configuration archive was created. |
Related commands
archive configuration
archive configuration location
archive configuration server
display configuration exclusive by-user-name
Use display configuration exclusive by-user-name to display information about user-based configuration locking.
Syntax
display configuration exclusive by-user-name
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display information about configuration locking after the system configuration was locked.
<Sysname> display configuration exclusive by-user-name
User-name: aaa
Locked at: 2018-03-07T20:13:31
# Display information about configuration locking after the configuration was unlocked.
<Sysname> display configuration exclusive by-user-name
User-name: aaa
Unlocked at: 2018-03-07T20:14:09
display configuration replace server
Use display configuration replace server to display information about remote configuration rollback.
Syntax
display configuration replace server
Views
Any view
Predefined user roles
network-admin
network-operator
Usage guidelines
The device stores only the most recent 10 remote rollback records.
Examples
# Display information about remote configuration rollback.
<Sysname> display configuration replace server
Username: test
Location: ftp://192.168.21.21:22/test/
VPN instance: VPN1
Next replacement file: my_archive_20180509_143018.cfg
Next replacement time: 22:00 2018/6/12
Replacement history:
No. Time FileName
! 1 20:21:09 2018/10/18 my_archive_20180509_142018.cfg
! 2 20:25:00 2018/10/18 my_archive_20180509_143018.cfg
#! 3 22:52:23 2018/10/20 my_archive_20180509_144018.cfg
The exclamation mark (!) indicates that the remote replacing attempt failed.
The pound sign (#) indicates the most recent replacement file.
Table 2 Command output
|
Field |
Description |
|
Username |
Username for accessing the remote server to download a configuration file for configuration rollback. |
|
Location |
Absolute path of the replacement configuration file. |
|
VPN instance |
VPN instance to which the remote server belongs. |
|
Next replacement file |
Configuration file for the next remote configuration rollback. If no remote configuration rollback schedule is waiting for execution, this field is not available. |
|
Next replacement time |
Time and date for the next remote configuration rollback. If no remote configuration rollback schedule is waiting for execution, this field is not available. |
|
Replacement history |
Remote configuration rollback history. |
|
No. |
Number of a configuration rollback. |
|
Time |
Time and date when the configuration rollback was performed. |
|
Filename |
Name of the replacement configuration file. |
Related commands
configuration replace server
configuration replace server file
configuration replace server password
configuration replace server user
display current-configuration
Use display current-configuration to display the running configuration.
Syntax
display current-configuration [ [ configuration [ module-name ] | exclude-provision | interface [ interface-type [ interface-number ] ] ] [ all ] | slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
configuration [ module-name ]: Displays the 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.
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.
all: Displays all settings in the running configuration, including the default settings. If you do not specify this keyword, the command displays only non-default settings in the running configuration.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify an IRF member device, this command displays the running configuration for all IRF member devices.
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 if you do not specify the all keyword.
Examples
# Display local user configuration.
<Sysname> display current-configuration configuration local-user
#
local-user ftp class manage
password hash $h$6$D5A6pqcGpnZXxFUO$OJqnqffG7m1wTH3C6v+FBCjZZBzqgJjTZlbATl1dnKNlYwFMJcWDMbDn8HD1j4XzuKggDp2LrP40kGIOvQGYhQ==
service-type ftp
authorization-attribute user-role network-operator
#
local-user root class manage
password hash $h$6$GcTZyXO04qmom21z$GjeAeDMjP/xtknMLf9NHUNIvebNYR3tkd5aWS6sKbkFh/ECFJZOjh2FVUI0GW7u44fNK6Ke7ANE7dhhAFcytUQ==
service-type ssh telnet terminal
authorization-attribute user-role network-admin
#
return
# Display VLAN interface configuration.
<Sysname> display current-configuration interface Vlan-interface
#
interface Vlan-interface1
ip address 192.168.1.84 255.255.255
#
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
Usage guidelines
This command searches for the next-startup configuration in the following order:
5. The .cfg main next-startup configuration file.
6. The .cfg backup next-startup configuration file if the .cfg main next-startup configuration file is unavailable.
If both 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
@@ -5,7 +5,7 @@
#
sysname Sysname
#
-alias dhc display history-command
+alias dh display hotkey
<Sysname>
|
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. In this example, the startup configuration and the current configuration are the source and target, respectively. |
|
@@ -linenumber1,number1 +linenumber2,number2 @@ |
Location information for identifying the 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. In this example, the sample output shows that the alias dhc display history-command command is contained only in the source configuration, and the alias dh display hotkey command is contained only in the target configuration. |
Related commands
display current-configuration
display diff
display saved-configuration
display default-configuration
Use display default-configuration to display the factory defaults.
Syntax
display default-configuration
Views
Any view
Predefined user roles
network-admin
network-operator
Usage guidelines
Factory defaults are custom basic settings that came with the device. Factory defaults vary by device models and might differ from the initial default settings for the commands.
If no factory defaults came with the device, the output of the display default-configuration command is empty.
The device starts up with the factory defaults if no next-startup configuration files are available.
Examples
# Display the factory defaults.
<Sysname> display default-configuration
display diff
Use display diff to display differences between configurations.
Syntax
display diff configfile file-name-s { configfile file-name-d | current-configuration | startup-configuration }
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
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 in the following order:
7. The .cfg main next-startup configuration file.
8. The .cfg backup next-startup configuration file if the .cfg main next-startup configuration file is unavailable.
If both 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
--- flash:/startup.cfg
+++ flash:/test.cfg
@@ -5,7 +5,7 @@
#
sysname Sysname
#
-alias dhc display history-command
+alias dh display hotkey
<Sysname>
The output shows that the alias dhc display history-command command is contained only in startup.cfg, and the alias dh display hotkey command is contained only in test.cfg.
# Display the differences between the running configuration and the next-startup configuration.
<Sysname> display diff current-configuration startup-configuration
--- Current configuration
+++ Startup configuration
@@ -5,7 +5,7 @@
#
sysname Sysname
#
-alias dhc display history-command
+alias dh display hotkey
<Sysname>
The output shows that the alias dhc display history-command command is contained only in the running configuration, and the alias dh display hotkey command is contained only in the next-startup configuration.
For the command output description, see Table 3.
Related commands
display current-configuration
display current-configuration diff
display saved-configuration
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
Usage guidelines
Application scenarios
Use this command to verify that important settings have been saved to the configuration file for the next system startup.
Operating mechanism
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 content of the main startup configuration file.
2. If only the backup startup configuration file is available, this command displays the content 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.070, Release 1201
#
sysname Sysname
#
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 all startup configuration files, including the file that the device started up with and the files for next startup.
Syntax
display startup
Views
Any view
Predefined user roles
network-admin
network-operator
Restrictions and guidelines
All IRF members use the same current startup configuration file as the master.
After a master/subordinate switchover, it is normal that the current startup configuration files on all IRF members are displayed as NULL. This is because the new master continues to run with the running configuration rather than rebooting with a startup configuration file.
Examples
# Display names of the startup configuration files.
<Sysname> display startup
MainBoard:
Current startup saved-configuration file: flash:/startup.cfg
Next main startup saved-configuration file: flash:/startup.cfg
Next backup startup saved-configuration file: NULL
Table 4 Command output
|
Field |
Description |
|
MainBoard |
Displays the startup configuration files on the master device. |
|
Current startup saved-configuration file |
Configuration file that the device has started up with. If the field is suffixed with an asterisk (*), the startup configuration file is a binary file. |
|
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. |
Related commands
startup saved-configuration
display this
Use display this to display the running configuration in the current view.
Syntax
display this [ all ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
all: Displays all settings in the running configuration in the current view, including the default settings. If you do not specify this keyword, the command displays only non-default settings in the running configuration.
Usage guidelines
Application scenarios
Use this command to verify the configuration you have made in a certain view.
Restrictions and guidelines
This command does not display parameters that are using the default settings if you do not specify the all keyword.
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 VLAN-interface 1.
<Sysname> system-view
[Sysname] interface vlan-interface 1
[Sysname-Vlan-interface1] display this
#
interface Vlan-interface1
#
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
Parameters
backup: Specifies the backup next-startup configuration file.
main: Specifies the main next-startup configuration file.
Usage guidelines
Application scenarios
If a next-startup configuration file is no longer in use, you can delete it.
Parameter description
If you do not specify a configuration file attribute, the reset saved-configuration command deletes the main next-startup configuration file.
Restrictions and guidelines
By default, this command permanently deletes the specified next-startup configuration file from all IRF member devices. To delete the configuration file only from the master device, disable automatic system-wide next-startup configuration file operations. For more information about disabling these operations, see configuration file management in Fundamentals Configuration Guide.
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 sets the target file attribute to NULL instead of deleting the file.
Examples
# 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 flash: is being cleared.
Please wait ...........
Configuration file is cleared.
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
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 name of the configuration file to be downloaded. The file must be a .cfg file. The file name is a case-insensitive string of up to 255 characters.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If the TFTP server is on the public network, do not specify this option.
Usage guidelines
Prerequisites
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.
Operating mechanism
Restrictions and guidelines
Examples
# Download test.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 test.cfg
Restoring the next startup-configuration file from 2.2.2.2. Please wait...finished.
# 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 next startup-configuration file from 2.2.2.2. Please wait...finished.
# 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 next startup-configuration file from 2001::2. Please wait...finished.
Related commands
backup startup-configuration
save
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 ] [ changed ] to save the running configuration as a next-startup configuration file in the root directory of the storage medium.
Syntax
save file-url [ all | slot slot-number ]
save [ safely ] [ backup | main ] [ force ] [ changed ]
Views
Any view
Predefined user roles
network-admin
Parameters
file-url: Specifies a file path, a string of up to 255 characters, which must end with .cfg. If you specify the all keyword or the slot slot-number option, the file path cannot include a member ID. If the file path includes a folder name, the folder must already exist on the specified IRF member devices.
all: Saves the running configuration to all member devices. If you do not specify a subordinate device or the all keyword, this command saves the running configuration only to the master device.
slot slot-number: Specifies a subordinate device by its member ID. If you do not specify a subordinate device or the all keyword, this command saves the running configuration only to the master device.
safely: Saves the configuration file in safe mode. If you do not specify this keyword, the device saves the configuration file in fast mode.
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.
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
Operating mechanism
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.
Restrictions and guidelines
Use the save command with caution. This command will overwrite the settings in the target configuration file. When you execute this command, carefully read the messages displayed by the system and make sure you fully understand the impact of this command on services.
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.
If you do not specify the file-url argument, the device saves the running configuration to the root directory of the storage media and specifies the configuration file as the next-startup configuration file. If you specify the file-url argument, the device only saves the running configuration file to the specified path.
When you use the save [ safely ] [ backup | main ] [ force ] [ changed ] command, follow these guidelines:
· 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.
Safe mode is slower than fast mode, but more secure. As a best practice, specify the safely keyword for reliable configuration saving.
By default, the save [ safely ] [ backup | main ] [ force ] command saves the configuration to all IRF member devices. To save the configuration only to the master device, disable automatic system-wide next-startup configuration file operations. For more information about disabling these operations, see configuration file management in Fundamentals Configuration Guide.
If containers have been created on the device, follow these guidelines when you use the save command to save the running configuration:
· If you do not specify the force keyword, the system prompts you to confirm whether to save the settings of the containers.
¡ If you enter Y at the prompt, the system saves the settings of the containers for the settings to survive a reboot. Saving the container settings will take some time.
¡ If you enter N at the prompt or do not confirm the prompt in 30 seconds, the system continues the saving process without saving the container settings.
· If you specify the force keyword, the system saves the container settings without any confirmation required.
Examples
# Save the running configuration to backup.cfg, without specifying the file as a next-startup configuration file.
<Sysname> save backup.cfg
The current configuration will be saved to flash:/backup.cfg. Continue? [Y/N]:y
Now saving current configuration to the device.
Saving configuration flash:/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.
# When containers exist on the device, save the running configuration to the main next-startup configuration file without any confirmation required.
<Sysname> save force
Validating file. Please wait....
Saving docker files need some time.
Saving docker files............
Done.
Saved the current configuration to mainboard device successfully.
# Save the running configuration to a file in the root directory of the default 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)[flash:/backup.cfg]
(To leave the existing filename unchanged, press the enter key):test.cfg
Validating file. Please wait............
Saved the current configuration to mainboard device successfully.
# When containers exist on the device, save the running configuration to a file in the root directory of the default 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)[flash:/backup.cfg]
(To leave the existing filename unchanged, press the enter key):test.cfg
Validating file. Please wait............
Saving docker files need some time. Do you want to save docker files in this process? [Y/N]:y
Saving docker files............
Done.
Saved the current configuration to mainboard device successfully.
Related commands
display current-configuration
display saved-configuration
save current-configuration interval
Use save current-configuration interval to enable the automatic configuration saving feature and set the automatic saving interval.
Use undo save current-configuration interval to restore the default.
Syntax
save current-configuration interval { interval | sec seconds-interval }
undo save current-configuration interval
Default
The automatic configuration saving feature is disabled.
Views
System view
Predefined user roles
network-admin
Parameters
interval: Sets the automatic saving interval, in minutes. The value range is 10 to 525600.
sec seconds-interval: Sets the automatic saving interval, in seconds. The value range is 1 to 31536000.
Usage guidelines
Operating mechanism
This feature enables the device to automatically save the running configuration to both the .cfg and .mdb main next-startup configuration files at intervals. At each interval, the device performs an automatic saving operation only if the running configuration contains different settings than the main next-startup configuration files.
If no main next-startup configuration files exist, this feature automatically creates configuration files startup.cfg and startup.mdb to save the running configuration and specifies the files as the main next-startup configuration files.
This feature saves the running configuration to all member devices.
Examples
# Enable the device to automatically save the running configuration to the .cfg and .mdb main next-startup configuration files every 60 minutes.
<Sysname> system-view
[Sysname] save current-configuration interval 60
standby auto-update config
Use standby auto-update config to enable automatic system-wide next-startup configuration file operations.
Use undo standby auto-update config to disable automatic system-wide next-startup configuration file operations.
Syntax
standby auto-update config
undo standby auto-update config
Default
Next-startup configuration file operations are automatically synchronized across the entire system.
Views
System view
Predefined user roles
network-admin
Usage guidelines
By default, automatic system-wide next-startup configuration file operations are enabled. The system performs the following operations on all IRF subordinate devices in addition to the master device:
· Saves the running configuration to the next-startup configuration file on each member device when you execute the save save [ safely ] [ backup | main ] [ force ] [changed ] command.
· Deletes the next-startup configuration file on each member device when you execute the reset saved-configuration command.
If you disable automatic system-wide next-startup configuration file operations, the system saves the running configuration or deletes the next-startup configuration file only on the master device.
If you are disabling automatic system-wide operations for faster configuration saving, be aware that the next-startup configuration files will be inconsistent between the master device and the subordinate devices.
Examples
# Enable automatic system-wide next-startup configuration file operations.
<Sysname> system-view
[Sysname] standby auto-update config
Related commands
reset saved-configuration
save
startup saved-configuration
Use startup saved-configuration to specify a file as a next-startup configuration file.
Use undo startup saved-configuration to configure the system to start up with the factory defaults at the next startup.
Syntax
startup saved-configuration cfgfile [ backup | main ]
undo startup saved-configuration
No next-startup configuration files are specified.
Views
Predefined user roles
network-admin
Parameters
cfgfile: Specifies the path of a configuration file, a string of up to 255 characters. The file must be a .cfg file. The file path can include only the file name, or the storage medium information and file name. 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
Prerequisites
Make sure the same file is specified as the next-startup configuration file on all member devices in an IRF fabric. Therefore, before executing this command, make sure the specified configuration file is saved in the root directory on the same type of storage medium for all member devices. If you fail to do so, the configuration will fail.
Recommended configuration
As a best practice, specify different files as the main and backup next-startup configuration files.
Parameter description
If you do not specify the backup or main keyword, the startup saved-configuration command specifies the main next-startup configuration file.
Restrictions and guidelines
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.
In an IRF fabric, the undo startup saved-configuration command can cause an IRF split after the IRF fabric or an IRF member reboots.
Examples
# Specify the main next-startup configuration file.
<Sysname> startup saved-configuration testcfg.cfg
Please wait ....... Done.
Related commands
display startup
