Before manually archiving the running configuration, you must use the archive configuration location command to specify a directory as the configuration archive directory and specify an archive name prefix.

Configuration archive facilitates configuration rollback. It provides manual and automatic approaches to saving the running configuration as checkpoint references. For more information about the archiving mechanism, see the section about configuration rollback in Fundamentals Configuration Guide.

To avoid decreasing system performance:

· If the device configuration does not change frequently, manually archive the running configuration as needed.

· If a low-speed storage medium (such as a Flash) is used, archive the running configuration manually, or configure automatic archiving with an interval longer than 1440 minutes (24 hours).

· If a high-speed storage medium (such as a CF card) is used and the device configuration changes frequently, set a shorter saving interval.

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 restore the default.

Syntax

archive configuration interval minutes

undo archive configuration interval

Default

The system does not automatically archive the running configuration.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

minutes: Specifies the interval (in minutes) for automatically saving the running configuration. Value range is 10 to 525600 (365 days).

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 function that facilitates configuration rollback. It provides the manual and automatic approaches to saving the running configuration as checkpoint references.

Automatic configuration archiving enables the system to automatically save the running configuration to the archive directory. For more information about the archiving mechanism, see the section about configuration rollback in Fundamentals Configuration Guide.

To avoid decreasing system performance, follow these guidelines:

· If the device configuration does not change frequently, manually archive the running configuration as needed.

· If a low-speed storage medium (such as a Flash) is used, archive the running configuration manually, or configure automatic archiving with an interval longer than 1440 minutes (24 hours).

· If a high-speed storage medium (such as a CF card) is used and the device configuration changes frequently, set a shorter saving interval.

· Change the archiving interval depending on the available storage space. The shorter the interval, the more free storage space is required.

· H3C recommends not deleting the configuration archives when the automatic configuration archiving is enabled.

Examples

# Configure 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 configure 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 has been set.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

directory: Specifies a configuration archive directory, a case-insensitive string of 1 to 63 characters. The directory must take the format storage-media-name:/folder-name. In standalone mode, this directory must already exist on the active MPU, and its directory name must not include slot information. In IRF mode, this directory must already exist on the active MPU of the master, and its directory name must not include member ID or slot information.

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 configure a directory and file name prefix for configuration archives.

In standalone mode, the configuration archive function saves the running configuration only on the active MPU. In IRF mode, the function saves the running configuration only on the active MPU in the master device. 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, the old configuration archives are regarded as common configuration files, the configuration archive counter resets, and the display archive configuration command no longer displays them. The serial number for new configuration archives starts at 1.

The undo archive configuration location command not only removes the configuration archive directory and file name prefix settings but also disables the configuration archive function (both manual and automatic approaches), restores the default settings of the archive configuration interval and archive configuration max commands, and clears all configuration archives.

Examples

# Configure 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

· 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

Up to five configuration archives can be saved.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

file-number: Sets 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 exceeding archives. Instead, the configuration archive function deletes the oldest n files when a new archive is manually or automatically saved, where n = current archive count – new archive limit + 1.

Suppose 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 tftp-server [ dest-filename ]

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

tftp-server: Specifies a TFTP server by its IPv4 address or host name. The host name is a string of 1 to 20 characters.

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.

Examples

# Back up the main next-startup configuration file to the TFTP server at 2.2.2.2, 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

Backup next startup-configuration file to 2.2.2.2, please wait…finished

Related commands

restore startup-configuration

configuration encrypt

Use configuration encrypt to enable configuration encryption.

Use undo configuration encrypt to restore the default.

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. Only the MPU where the configuration file is encrypted can decrypt the file.

public-key: Encrypts configuration with a public key. Any H3C device running the same software version as the encrypting device can decrypt the encrypted configuration file.

Usage guidelines

Configuration encryption enables the device to automatically encrypt a configuration file when saving the running configuration to the file.

Do not move or copy a private-key-encrypted configuration file between MPUs in the IRF fabric. Doing so can cause a decryption failure, because MPUs use different private keys.

Examples

# Enable the public-key approach to 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 for configuration rollback.

Usage guidelines

To replace the running configuration with the configuration in a configuration file without rebooting the device, use the configuration rollback function. This function helps you revert to a previous configuration state or adapt the running configuration to different network environments.

To avoid rollback failure:

· Do not remove or install a card while the system is executing the configuration replace file command.

· Make sure the replacement configuration file is created by using the configuration archive function or the save command on the device.

· If the configuration file is not created on the device, make sure the configuration file content format is 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.

convert configuration

Use convert configuration to convert a Comware V5 configuration file to a Comware V7 configuration file.

Syntax

convert configuration srcfile to desfile

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

srcfile: Specifies the source Comware V5 configuration file path.

desfile: Specifies the destination Comware V7 configuration file path.

Usage guidelines

Comware V7 is an operating system built to meet the demands of virtualized data centers. It optimizes performance of Comware V5 features, adds new features, and re-designs some commands for better user experience.

When you migrate from Comware V5 to Comware V7, you can convert the Comware V5-specific configuration file to a Comware V7 configuration file to reduce reconfiguration tasks.

Examples

# Convert the Comware V5 configuration file startupv5.cfg to the Comware V7 configuration file startupv7.cfg.

<Sysname> convert configuration startupv5.cfg to startupv7.cfg

display archive configuration

Use display archive configuration to display configuration archive information, including the archive directory, archive prefix, archive interval, maximum number of archives, and saved archives.

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: flash:/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

Table 1 Command output

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 ] | interface [ interface-type [ interface-number ] ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

configuration [ module-name ]: Displays non-interface configuration. The configuration argument specifies a type of configuration. If no configuration type is specified, this command displays all non-interface settings. If a type of configuration is specified, this command displays the specific 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.

Usage guidelines

Use this command to verify the running configuration you have made.

Typically, this command does not display parameters that are set to their default settings.

If the system has automatically changed the setting you have made for a parameter, for example, due to a system restriction, this command displays the effective setting rather than the configured one.

Examples

# Display local-user configuration.

<Sysname> display current-configuration configuration local-user

local-user ftp class manage

password simple 123

service-type ftp

authorization-attribute user-role network-operator

local-user root class manage

password simple admin

service-type ssh telnet terminal

authorization-attribute user-role network-admin

return

# Display Ethernet interface configuration.

<Sysname> display current-configuration interface GigabitEthernet

interface GigabitEthernet3/0/1

port link-mode route

return

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

mdc-admin

mdc-operator

Usage guidelines

The device is shipped with some basic settings called "factory defaults." These default settings make sure the device can start up and run normally when it has no configuration file or the configuration file is corrupted.

Factory defaults might differ from the default settings of commands.

Examples

# Display the factory defaults.

<Sysname> display default-configuration

display saved-configuration

Use display saved-configuration to display the configuration saved to the main next-startup configuration file.

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 main next-startup configuration file.

If no next-startup configuration file has been specified, or the specified next-startup configuration does not exist, this command displays nothing.

Examples

# Display the main next-startup configuration file.

<Sysname> display saved-configuration

version 7.1.026, Alpha 7122

mdc Admin id 1

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 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 used at this startup. Next-startup configuration file is the configuration file used at the next startup.

In standalone mode:

The standby MPU always maintains 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 them are displayed as NULL, because the new active MPU continues to run with the running configuration rather than rebooting with the previous current startup configuration file.

In IRF mode:

The MPUs in the IRF fabric always maintain 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 them are displayed as NULL, because the new global active MPU continues to run with the running configuration rather than rebooting with the previous current startup configuration file.

Examples

# In standalone mode, display 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

Slot 1:

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 2 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	Main 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 startup configuration files.

<Sysname> display startup

MainBoard:

Current startup saved-configuration file: NULL

Next main startup saved-configuration file: flash:/startup.cfg

Next backup startup saved-configuration file: flash:/startup2.cfg

Chassis 2 Slot 0:

Current startup saved-configuration file: NULL

Next main startup saved-configuration file: flash:/startup.cfg

Next backup startup saved-configuration file: flash:/startup2.cfg

Table 3 Command output

Field	Description
MainBoard	Displays the startup configuration files on the IRF master device.
Current Startup saved-configuration file	Configuration file that the global active MPU has started up with.
Next main startup saved-configuration file	Main 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.

Typically, this command does not display parameters that are set to their default settings.

For some parameters that can be successfully configured even if their dependent features are not enabled, this command displays their settings after the dependent features are enabled.

This command can be executed in any user interface view to display the running configuration of all user view interfaces.

Examples

# Display the running configuration on interface GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface gigabitethernet 3/0/1

[Sysname-GigabitEthernet3/0/1] display this

interface GigabitEthernet3/0/1

port link-mode route

return

# Display the running configuration on user interfaces.

<Sysname> system-view

[Sysname] user-interface vty 0

[Sysname-ui-vty0] display this

user-interface aux 0 1

user-role network-operator

user-interface con 0 1

user-role network-admin

user-interface vty 0 15

authentication-mode none

user-role network-admin

return

reset saved-configuration

Use reset saved-configuration to delete next-startup configuration files.

Syntax

reset saved-configuration [ backup | main ]

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

backup: Deletes the backup next-startup configuration file.

main: Deletes the main next-startup configuration file.

Usage guidelines

Delete a next-startup configuration file if it does not match the software version or has been corrupted.

Use this command with caution. In standalone mode, this command permanently deletes the next-startup configuration files from both MPUs. In IRF mode, this command permanently deletes the next-startup configuration files on all MPUs in the IRF fabric.

You can delete the main, the backup, 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. Whichever command is executed first, the system removes the specific file attribute instead of deleting the file. For example, if the reset saved-configuration backup command is executed first, the backup next-startup configuration file setting is set to NULL, but the file is still used as the main file. To delete the file, you must execute the reset saved-configuration main command.

If no configuration file attribute is specified, 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 flash: 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 flash: 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 tftp-server src-filename

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

tftp-server: Specifies a TFTP server's IPv4 address or host name. The host name is a string of 1 to 20 characters.

src-filename: Specifies the file name of the configuration file to be downloaded.

Usage guidelines

Before restoring the configuration file for the next startup, make sure the server is reachable, the server is enabled with TFTP service, and you have read and write permissions.

This command provides an easy approach to configuration file restoration by automatically performing all operations required for restoring the main next-startup configuration file.

It 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. (The default storage medium is user configurable. For more information, see "Managing the file system.")

This command assumes that all MPUs use the same type of storage medium. If a standby MPU uses a different type of storage medium than the active MPU, the command cannot propagate the configuration file to the standby MPU. For example, if the standby MPU uses a CF card, but the active MPU uses Flash, you must manually restore the next-startup configuration file on the standby MPU.

Examples

# In standalone mode, download the configuration file config.cfg from the TFTP server at 2.2.2.2, and specify the file as the main next-startup configuration file.

<Sysname> restore startup-configuration from 2.2.2.2 config.cfg

Restore next startup-configuration file from 2.2.2.2, please wait...

Finished.

Now restore next startup-configuration file from main to standby board, please wait...

Finished.

# In IRF mode, download the configuration file config.cfg from the TFTP server at 2.2.2.2 and specify the file as the main next-startup configuration file.

<Sysname> restore startup-configuration from 2.2.2.2 config.cfg

Restore next startup-configuration file from 2.2.2.2, please wait...

Finished.

Now restore next startup-configuration file from main to standby board, please wait...

Finished.

Related commands

backup startup-configuration

save

In standalone mode:

Use save file-url 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 ] to save the running configuration to the root directory of the storage media on both active MPU and standby MPU, and specify the file as a next-startup configuration file.

In IRF mode:

Use save file-url 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 ] to save the running configuration to the root directory of the storage media on each member device, and specify the file as a next-startup configuration file.

Syntax

save file-url

save [ safely ] [ backup | main ] [ force ]

Views

Any view

Predefined user roles

network-admin

mdc-admin

Parameters

file-url: Specifies a file path, where the file extension must be .cfg. If the file path includes a folder name, you must first create the folder on the specified MPU.

safely: Saves the configuration file in safe mode. If this keyword is not specified, the device saves the configuration file in fast mode. Safe mode is slower than fast mode, but more secure. 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 or power failure 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 or power failure occurs during this process, the next-startup configuration file is lost.

backup: Saves the running configuration to a configuration file, and specifies the file as the backup next-startup configuration file.

main: Saves the running configuration to a configuration file, and specifies the file as the main next-startup configuration file.

force: Saves the running configuration to the main next-startup configuration file that has been specified in the system. Without this keyword, the system asks 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 next-startup configuration file during this process.

Usage guidelines

If the base file name specified for the file-url argument does not exist, the system creates the file before saving the configuration. If the file already exists, the system asks you to confirm whether to overwrite the file. If you choose to not overwrite the file, the system cancels the save operation.

If neither the main keyword nor the backup keyword is specified, the save command saves configuration to the main next-startup configuration file.

Examples

# Save the running configuration to the configuration file backup.cfg, without specifying the file as the 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.

# 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)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

flash:/startup.cfg exists, overwrite? [Y/N]:y

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)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

flash:/startup.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Chassis 1 Slot 1:

Save next configuration file successfully.

Related commands

· display current-configuration

· display saved-configuration

startup saved-configuration

In standalone mode:

Use startup saved-configuration to specify a file as a next-startup configuration file for both active MPU and standby MPU.

Use undo startup saved-configuration to configure the active MPU and the standby MPU to start up with factory defaults at the next startup.

In IRF mode:

Use startup saved-configuration to specify a file as a next-startup configuration file for all MPUs in the IRF fabric.

Use undo startup saved-configuration to configure all MPUs to start up with the factory defaults at the next startup.

Syntax

startup saved-configuration cfgfile [ backup | main ]

undo startup saved-configuration

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

cfgfile: Specifies the name of a .cfg file. This .cfg file must already exist in the root directory of storage medium.

backup: Specifies the configuration file as the backup next-startup configuration file.

main: Specifies the configuration file as the main 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.

The startup saved-configuration command applies to all MPUs. To successfully configure the command, verify that:

· In standalone mode, the specified file already exists in the root directory of the storage medium on both active MPU and standby MPU.

· In IRF mode, the specified file already exists in the root directory of the storage medium on each MPU.

If neither backup nor main is specified, the startup saved-configuration command specifies the main next-startup configuration file.

Even though the main and backup next-startup configuration files can be the same one, specify them as separate files for high availability.

The undo startup saved-configuration command changes the file attribute of the main and backup next-startup configuration files to NULL but 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 to it.

Examples

# Specify the main next-startup configuration file.

<Sysname> startup saved-configuration testcfg.cfg

Please wait ....... Done.

Related commands

display startup

01-Fundamentals Command Reference

Configuration file management commands

reset saved-configuration

save

startup saved-configuration

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us