The device supports the FIPS mode that complies with NIST FIPS 140-2 requirements. Support for features, commands, and parameters might differ in FIPS mode and non-FIPS mode. For more information about FIPS mode, see Security Configuration Guide.

archive configuration

Use archive configuration to manually archive the running configuration to the configuration archive directory.

Syntax

archive configuration

Views

User view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

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

Configuration archive facilitates configuration rollback. It provides manual and automatic methods for saving the running configuration. For more information about the archiving mechanism, see the section about configuration rollback in Fundamentals Configuration Guide.

H3C recommends that you not delete the configuration archives when the automatic configuration archiving is enabled. Otherwise, the rollback operation might fail.

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. The 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 manual and automatic methods for saving the running configuration.

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

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

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 the name of a configuration archive directory, a case-insensitive string of 1 to 63 characters. The directory name must take the format storage-medium-name:/folder-name. The directory must already exist on the active MPU in standalone mode or exist on the global active MPU in IRF mode.

filename-prefix: Specifies a file name prefix for configuration archives, a case-insensitive string of 1 to 30 characters. Valid characters are letters, digits, underscores (_), and hyphens (-).

Usage guidelines

Before archiving the running configuration, either manually or automatically, you must 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, all of the following occur:

· The old configuration archives are regarded as common configuration files.

· The configuration archive counter resets.

· 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. The command also performs the following operations:

· Disables the configuration archive function (both manual and automatic methods).

· Restores the default settings of the archive configuration interval and archive configuration max commands.

· 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: Specifies the maximum number of configuration archives that can be saved. The value range is 1 to 10. Adjust the setting depending on the amount of storage space available.

Usage guidelines

Before you can set a limit on configuration archives, use the archive configuration location command to specify a configuration archive directory and archive file name prefix.

After the maximum number of configuration archives is reached, the system deletes the oldest archive for the new archive.

Changing the limit setting to a lower value does not cause immediate deletion of excess archives. Instead, the configuration archive 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 case-insensitive string of 1 to 253 characters. Valid characters include letters, digits, hyphens (-), underscores (_), and dots (.).

dest-filename: Specifies the target file name used for saving the file on the server. The file name must use the .cfg extension. If you do not specify a target file name, the source file name is used.

Usage guidelines

This command is not supported in FIPS mode.

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. All H3C devices running Comware V7 software use the same private key.

public-key: Encrypts configuration with a public key. All H3C devices running Comware V7 software use the same public key.

Usage guidelines

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

Only H3C devices running Comware V7 software can decrypt the encrypted configuration file.

Examples

# Enable the public-key method for configuration encryption.

<Sysname> system-view

[Sysname] configuration encrypt public-key

configuration replace file

Use configuration replace file to perform configuration rollback.

Syntax

configuration replace file filename

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

filename: Specifies the name of the replacement configuration file 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 ensure a successful rollback:

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

· Use the following types of configuration files to roll back configuration:

¡ Configuration file that was created on the local device by using the archive function or the save command.

¡ Configuration file that was created on another device and transferred to the local device.

Make sure the command lines in the configuration file are fully compatible with the local device.

· Make sure the replacement configuration file only contains hardware-consistency configurations. For example, if the replacement configuration file contains the configuration for a card that has been removed, the rollback process fails.

· Make sure the replacement configuration file is not encrypted.

Examples

# Replace the running configuration with the configuration in the my_archive_1.cfg configuration file.

<Sysname> system-view

[Sysname] configuration replace file my_archive_1.cfg

Current configuration will be lost, save current configuration? [Y/N]:n

Now replacing the current configuration. Please wait...

Succeeded in replacing current configuration with the file my_archive_1.cfg.

display archive configuration

Use display archive configuration to display configuration archive information, 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 feature configuration. The module-name argument specifies a feature module. If no feature module is specified, this command displays all feature settings you have made.

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 configuration you have made.

If the system has automatically changed the setting you have made for a parameter, this command displays the effective setting instead of the configured one. An automatic change typically occurs because of system restrictions.

This command does not display parameters that are using the default settings.

Examples

# Display local user configuration.

<Sysname> display current-configuration configuration local-user

local-user ftp class manage

password hash $h$6$zU0a9CgxwksuYMjN$VNLCHr071isQ5RZ/qqAHnFCApc2rmSYFzgLBKMpoElN

y1tP14sKbkCRZ6H9Zyb68sOlGFDx09BA2+QaNZJ0cOQ==

service-type ftp

authorization-attribute user-role network-operator

return

# Display Ethernet interface configuration.

<Sysname> display current-configuration interface gigabitethernet 3/0/1

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 ensure that the device can start up and run correctly when it does not have any startup configuration file or the configuration file is corrupt.

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 contents of the configuration file for the next system startup.

Syntax

display saved-configuration

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Usage guidelines

Use this command to verify that important settings have been saved to the configuration file for the next system startup.

This command selects the configuration file to display in the following order:

1. If the main startup configuration file is available, this command displays the contents of the main startup configuration file.

2. If only the backup startup configuration file is available, this command displays the contents of the backup file.

3. If both the main and backup startup configuration files are not available, this command does not display anything.

Examples

# Display the contents of the configuration file for the next system startup.

<Sysname> display saved-configuration

version 7.1.041, Alpha 732004

mdc Admin id 1

sysname H3C

telnet server enable

lacp system-priority 33333

link-aggregation lacp traffic-redirect-notification enable

link-aggregation global load-sharing mode source-mac source-ip

system-working-mode bridgee

password-recovery enable

vlan 1

vlan 100

stp region-configuration

---- More ----

Related commands

· reset saved-configuration

· save

display startup

Use display startup to display the names of the current startup configuration file and the next-startup configuration files.

Syntax

display startup

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Usage guidelines

Current startup configuration file is the configuration file that has been loaded. Next-startup configuration file is the configuration file used at the next startup.

In standalone mode, the standby MPU always uses the same current startup configuration file as the active MPU. After an active/standby switchover, it is normal that the current startup configuration files on the MPUs are displayed as NULL. This is because the new active MPU continues to run with the running configuration rather than rebooting with a startup configuration file.

In IRF mode, the global standby MPUs always use the same current startup configuration file as the global active MPU. After an active/standby switchover, it is normal that the current startup configuration files on all MPUs are displayed as NULL. This is because the new global active MPU continues to run with the running configuration rather than rebooting with a startup configuration file.

Examples

# (In standalone mode.) Display names of the startup configuration files.

<Sysname> display startup

MainBoard:

Current startup saved-configuration file: 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	Primary startup configuration file to be used at the next startup.
Next backup startup saved-configuration file	Backup startup configuration file to be used at the next startup.
(This file does not exist.)	If the specified next-startup configuration file has been deleted, this comment appears next to the file name.
Slot n	Displays the startup configuration files on the MPU in slot n.

# (In IRF mode.) Display names of the startup configuration files.

<Sysname> display startup

MainBoard:

Current startup saved-configuration file: NULL

Next main startup saved-configuration file: 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	Primary configuration file to be used at the next startup.
Next backup startup saved-configuration file	Backup configuration file to be used at the next startup.
(This file does not exist.)	If the specified next-startup configuration file has been deleted, this comment appears next to the file name.
Chassis m Slot n	Displays the startup configuration files on the MPU in slot n of IRF member m.

Related commands

startup saved-configuration

display this

Use display this to display the running configuration in the current view.

Syntax

display this

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Usage guidelines

Use this command to verify the configuration you have made in a certain view.

This command does not display parameters that are set to their default settings.

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

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

Examples

# Display the running configuration on interface GigabitEthernet 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 lines.

<Sysname> system-view

[Sysname] line vty 0

[Sysname-line-vty0] display this

line aux 0 1

user-role network-operator

line con 0 1

user-role network-admin

line vty 0 63

user-role network-admin

user-role network-operator

idle-timeout 0 0

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

CAUTION:

Use this command with caution. This command permanently deletes the next-startup configuration file from each MPU.

Delete a next-startup configuration file if it is corrupt or does not match the software version.

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. Using only one of the commands removes the specific file attribute instead of deleting the file.

For example, if the reset saved-configuration backup command is executed, the backup next-startup configuration file setting is set to NULL. However, the file is still used as the main file. To delete the file, you must also execute the reset saved-configuration main command.

If 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 case-insensitive string of 1 to 253 characters. Valid characters include letters, digits, hyphens (-), underscores (_), and dots (.).

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

Usage guidelines

This command is not supported in FIPS mode.

Before restoring the configuration file for the next startup, make sure the following requirements are met:

· The server is reachable.

· The server is enabled with TFTP service.

· You have read and write permissions to the server.

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

The configuration file is automatically saved to the root directory of the default storage medium on each MPU.

If the CF card or USB disk is used and partitioned, the configuration file is saved on the first partition.

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, the standby MPU uses a CF card, but the active MPU uses a flash memory. In this situation, 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

Restoring the next startup-configuration file from 2.2.2.2. Please wait...finished.

Now restoring the next startup-configuration file from main board to backup 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

Restoring the next startup-configuration file from 2.2.2.2. Please wait...finished.

Now restoring the next startup-configuration file from main board to backup board. Please wait...finished.

Related commands

backup startup-configuration

save

In standalone mode:

Use save file-url [ all | slot slot-number ] to save the running configuration to a configuration file, without specifying the file as a next-startup configuration file.

Use save [ safely ] [ backup | main ] [ force ] [ mdc-all ] to save the running configuration to a file in the root directory of the default storage medium. This command applies to each MDC or the MDC where you are logged in. It automatically specifies the file as a next-startup configuration file.

In IRF mode:

Use save file-url [ all | chassis chassis-number slot slot-number ] to save the running configuration to a configuration file, without specifying the file as a next-startup configuration file.

Syntax

In standalone mode:

save file-url [ all | slot slot-number ]

save [ safely ] [ backup | main ] [ force ] [ mdc-all ]

In IRF mode:

save file-url [ all | chassis chassis-number slot slot-number ]

save [ safely ] [ backup | main ] [ force ] [ mdc-all ]

Views

Any view

Predefined user roles

network-admin

mdc-admin

Parameters

file-url: Saves the running configuration to the specified file, without specifying the file as a next-startup configuration file. The file name must use the extension .cfg and can include path information. If the keyword all or an MPU slot is specified, the file path cannot include a chassis number or slot number. If the file path includes a folder name, the folder must already exist.

all: Saves the running configuration to both MPUs. If you do not specify this keyword or the slot slot-number option, the command saves the running configuration only to the active MPU. (In standalone mode.)

all: Saves the running configuration to all MPUs. If you do not specify this keyword or the chassis chassis-number slot slot-number option, the command saves the running configuration only to the global active MPU in the IRF fabric. (In IRF mode.)

slot slot-number: Saves the running configuration to the standby MPU. If you do not specify this option or the all keyword, the command saves the running configuration only to the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Saves the running configuration to a standby MPU. If you do not specify this option or the all keyword, the command saves the running configuration only to the global active MPU in the IRF fabric. (In IRF mode.)

safely: Saves the configuration file in safe mode. If this keyword is not specified, the device saves the configuration file in fast mode. Safe mode is slower than fast mode, but more secure. H3C recommends that you specify the safely keyword for the command.

backup: Saves the running configuration to a configuration file, and specifies the file as the backup next-startup configuration file. If you do not specify this keyword or the main keyword, the command specifies the saved file as the main next-startup configuration file.

main: Saves the running configuration to a configuration file, and specifies the file as the main next-startup configuration file. If you do not specify this keyword or the backup keyword, the command specifies the saved file as the main next-startup configuration file.

force: Saves the running configuration without prompting for confirmation. Without this keyword, the system prompts you to confirm the operation. If you do not confirm the operation within 30 seconds, the system automatically aborts the operation. If you enter Y within the time limit, you can continue the save process and change the target file name during the process.

mdc-all: Saves the running configuration for each MDC. This keyword is available only on the default MDC. If this keyword is not available or you do not specify this keyword, the command saves the running configuration only for the MDC where you are logged in.

Usage guidelines

If the file specified for the 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 option for the command, the 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.

If you specify the file-url option for the command, the command only saves the running configuration to the specified .cfg file.

In safe mode, the system saves configuration in a temporary file and starts overwriting the target next-startup configuration file after the save operation is complete. If a reboot, power failure, or out of memory 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 event occurs during this process, the next-startup configuration file is lost.

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 flash successfully.

# Save the running configuration to the main next-startup configuration file without any confirmation required.

<Sysname> save force

Validating file. Please wait....

Configuration is saved to device successfully.

# (In standalone mode.) Save the running configuration to a file in the root directory of the default storage medium on each MPU, 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):

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 default storage medium on each MPU, 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):

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Chassis 1 Slot 1:

Save next configuration file successfully.

# Save the running configuration to a file in the root directory of the default storage medium for each MDC, and specify the file as the main next-startup configuration file.

<Sysname> save mdc-all

Save current configuration in MDC Admin? [Y/N]:y

Please input the file name(*.cfg)[flash:/1.cfg]

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

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

Save current configuration in MDC mdc1? [Y/N]:y

Please input the file name(*.cfg)[flash:/mdc1.cfg]

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

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

Default

No next-startup configuration file is specified.

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 the default 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. This is the primary configuration file that the device attempts to load at startup. If the loading attempt fails, the device tries the backup next-startup configuration file.

Usage guidelines

CAUTION:

In an IRF fabric, use the undo startup saved-configuration command with caution. This command can cause an IRF split after the IRF fabric or an IRF member reboots.

The startup saved-configuration command applies to all MPUs. To successfully configure the command, make sure the following requirements are met:

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

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

· All MPUs use the same type of storage medium as the default storage medium.

If the USB disk or CF card is used to store the next-startup configuration files, do not remove the USB disk or CF card during the startup process. If you remove the USB disk or CF card on a device, one of the following consequences occurs:

· In standalone mode, the device starts up with the factory defaults.

· In IRF mode, the device leaves the IRF fabric at the startup and runs the factory defaults.

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 only changes the file attribute of the main and backup next-startup configuration files to NULL. It 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