01-07 Configuring System Startup
01-07 Configuring System Startup
● The upgrade of a device is closely related to the released software versions. The
corresponding upgrade guide is released with each new version and you can upgrade
the device according to the guide. To obtain the upgrade guides, visit https://
support.huawei.com/enterprise and download the upgrade guide based on the
product name and version.
● For details about commands used for device upgrade, see "Basic Configurations
Commands - Upgrade Commands" in the CloudEngine 16800 Series SwitchesCommand
Reference.
System Software
The device software includes BIOS software and system software. After the device
is powered on, it runs the BIOS software to initialize the hardware and display the
hardware parameters. Then the device runs the system software. The system
software provides drivers and adaptation functions for hardware, and offers
services features. The BIOS software and system software are prerequisite for
device startup and operation, providing support, management, and services for the
device.
A device upgrade includes BIOS software upgrade and system software upgrade.
NOTE
The BIOS software is included in the system software package (.cc file) of the device. The
BIOS software is automatically upgraded in system software upgrade.
Configuration File
A configuration file is a collection of command lines. The current configurations
are saved in configuration files, and continue to take effect after the device
restarts. You can view configurations in configuration files or upload the files to
other devices to implement batch configuration.
A configuration file is in the text format and meets the following requirements:
● The extension of the configuration file name must be .zip, .cfg or .dat. The
system configuration file must be saved in the root directory of the storage
device.
– A .cfg file is a text file. You can directly view the content of a .cfg file.
After a .cfg file is specified as the configuration file, the system restores
the commands in the file one by one when startup.
– A .zip file is the compression of a .cfg file, occupying less space. After
a .zip file is specified as the configuration file, the system decompresses
the file into a .cfg file, and then restores the commands in the file one by
one when startup.
– A .dat file is a binary file. If the startup software version and the .dat file
version are the same, the system restores all configurations in the .dat
file in batches when the device starts. This speeds up the system startup.
The following table describes the configuration file, current configuration, and
offline configuration.
Configurati When the device is powered on, ● Run the display startup
on file the device reads the command to check the
configuration file from the current and next startup
default directory to boot the configuration files.
system. Therefore, the ● Run the display saved-
configuration in the file is configuration command to
called the initial configuration. check the configuration file
If no configuration file is stored for next startup.
in the default directory, the
device uses the default
parameters for initialization.
If you modify the current configuration and want to use the modified
configuration as the next startup configuration, run the save command to save
the new configuration to the default storage device.
NOTE
If a command in incomplete form is configured, the system saves the command to the
configuration file in its complete form, which may cause the command to have more than
1022 characters. (The maximum length of a command supported by the system is 1022
characters.) The incomplete command cannot be recovered after the system restarts.
Patch File
A patch is a kind of software compatible with the system software. It is used to
remove a few issues in the software that need to be solved immediately. Patches
can also fix errors or improve adaptation of the system software. For example,
patches can fix defects of the system and optimize some functions to meet service
requirements.
The patches are released in patch files. A patch file may contain one or more
patches with different functions. When patch files are loaded from the storage
device to the patch area in the memory, they are assigned unique sequence
number for users to identify, manage, and operate the patches.
Patch classification
According to impact on services, patches can be classified into hot patch and cold
patch.
● Hot patch (HP): The services are not interrupted when the HP is loaded and
activated, which reduces upgrade costs and eliminates upgrade risks.
● Cold Patch (CP): You must restart the device or reset boards on the device for
the CP to take effect. Services are interrupted during the restart.
The currently released patches are hot patches and incremental patches. All the patches
mentioned in the subsequent sections are hot patches and incremental patches unless
otherwise specified.
Status of Patches
Each patch has its own state that can only be changed with command line.
Idle The patch file is saved to the When a patch in the storage
storage device but has not device is loaded to the patch
been loaded to the patch area, the patch is in the
area. deactive state.
Active When a patch is stored in the You can perform one of the
patch area and runs following operations on the
temporarily, the patch is in patch that is in the active
the active state. state:
If a board is reset, the active ● Uninstall the patch to
patch on the board remains delete it from the patch
active. The active patch area.
changes to the deactive state ● Stop running the patch to
only when the device is change the patch to the
restarted. deactive state.
● Run the patch permanently
to change the patch to the
running state.
Running When a patch is stored in the You can unload the patch that
patch area and runs is in the running state so that
permanently, the patch is in it can be deleted from the
the running state. patch area.
If a board is reset or the
device is restarted, the
running patch on the board
remains in the running state.
Load a patch
Idle Deactive
Delete a patch
De
let
e Deactive a patch Activate a patch
a
Delete a patch pa
tch
Running Active
Run a patch
Installing Patches
● The hot patches are generally installed while the device is running without
interrupting services. This is an advantage of hot patches.
For details on how to install patches, see the corresponding patch installation
guide. For details about commands used for device upgrade, see "Basic
Configurations Commands - Upgrade Commands" in the CloudEngine 16800
Series Switches Command Reference.
● Another way is to specify a patch file for next startup, which is described in
this chapter. The patch file takes effect after the device reboots. The method
is often used during a system upgrade.
Pre-configuration Tasks
Before managing configuration files, complete the following task:
Configuration Process
Perform one or more of the following tasks:
Procedure
● Save the configurations automatically.
a. Run system-view
The system view is displayed.
b. Run configuration file auto-save [ interval interval | cpu-limit cpu-
usage | delay delay-interval ] *
The system is configured to periodically save the configurations.
By default, the system does not periodically save configurations.
The system cancels the automatic save operation when:
SFTP has higher security and is therefore recommended for saving the configuration
file in the file server.
The configuration file is saved on the server as a compressed package. The package is
named in the format of YY-MM-DD.HH-MM-SS.device name.zip, for example,
2012-10-25.15-13-37.HUAWEI.zip. After the package is decompressed, the file with
the file name extension of .cfg is the configuration file.
d. (Optional) Run configuration current backup-to-server monthly date
date-value [ time time-value ]
The function to upload a configuration file to the server on a specific
date and time every month is enabled.
By default, the function to upload a configuration file to the server on a
specific date and time every month is disabled.
e. Run commit
The configuration is committed.
● Save the configurations manually.
– Run save [ configuration-file ]
The current configuration is saved.
The configuration file name extension must be .zip, .dat, or .cfg. The
system startup file must be stored in the root directory of the storage
device.
▪ You can run the pwd command in the user view to check the current
storage directory.
▪ You can run the cd command in the user view to modify the current
storage directory.
----End
Context
You can compare the current configuration file with the specified configuration file
to check whether they are consistent and determine whether to set the specified
configuration file as the next startup configuration file.
NOTE
Procedure
● Run display configuration changes [ running file file-name | file file-name
running ]
The system starts to check whether the current running configurations are
identical with the specified configuration file.
● Run display configuration changes [ running label label | label label
running ]
The system starts to check whether the current running configurations are
identical with the configuration based on a specific user label.
● Run compare configuration [ configuration-file ]
The system starts to check whether the current configurations are identical
with the next startup configuration file or a specified configuration file.
After completing a series of operations, you can compare whether the current
configurations are the same as the configurations in the next startup
configuration file or a specified configuration file starting from the first line of
the current configurations. You can determine whether to save the current
configurations based on the comparison result and specify the current
configurations as the next startup configuration file.
After you run this command to compare the current configurations with the
next startup configuration file or a specified configuration file, the system
displays the different content starting from the first different line to the ninth
different line. If the different content contains fewer than nine lines, the
system displays only the content from the first different line to the end of the
file.
----End
Procedure
● Copying the content in the display on the screen
Run the display current-configuration command and copy all command
outputs to a .txt file. The configuration file is backed up in the hard disk of
the maintenance terminal.
NOTE
If a configuration is too long, it may be displayed in two lines on the terminal screen,
depending on the terminal software. When copying a two-line configuration from the
screen to a .txt file, ensure that the configuration is displayed in only one line.
Otherwise, configuration restoration may fail when the .txt file is used.
● Backing up the configuration file to the storage device
The current configuration file can be backed up immediately to the flash
memory of the device. After the device starts, run the following commands to
back up the configuration file to the flash memory of the device:
<HUAWEI> save config.cfg
<HUAWEI> copy config.cfg backup.cfg
● Backing up the configuration file using FTP, TFTP, SFTP, or SCP
The device supports configuration file backup through FTP, TFTP, SFTP, or SCP.
Configuration file backup through FTP or TFTP is simple, but there are
Procedure
● Recover the configuration file that is backed up in the flash.
– Method 1: Restore the backup configuration file that is stored in the flash
memory of the device to the configuration file that is currently running in
the system, and specifies the file as the configuration file for next startup.
i. Run copy source-filename destination-filename [ all ]
The configuration file is backed up.
ii. Run startup saved-configuration configuration-file
The configuration file for next startup is specified.
iii. Run reboot
The device is restarted to make the configuration file take effect.
– Method 2: Back up the configuration and specify the configuration file for
next startup simultaneously in one-click mode.
i. Run copy source-filename startup destination-filename
The configuration file is copied and the file copy is specified as the
configuration file for next startup.
ii. Run reboot
The device is restarted to make the configuration file take effect.
You can specify the configuration file for next startup using either of the
preceding methods, and the later configuration takes effect.
● Recovering the configuration file using FTP, TFTP, SFTP, or SCP
The device supports configuration file recovery through FTP, TFTP, SFTP, or
SCP. Configuration file recovery through FTP or TFTP is simple, but there are
security risks. In scenarios with high security requirements, configuration file
recovery through SFTP or SCP is recommended. The following describes how
to recover the configuration file that is backed up on a PC through FTP. For
details about TFTP, SFTP, and SCP, see "File Management" in CloudEngine
16800 Series Switches Configuration Guide - Basic Configurations.
a. Start the FTP service when the device works as the FTP server.
Enable the FTP server function on the device. Create an FTP user with the
name huawei and password Helloworld@6789. The user is authorized to
access the flash directory.
<HUAWEI> system-view
[~HUAWEI] ftp server enable
[~HUAWEI] ftp server source all-interface
Warning: FTP is not a secure protocol, and it is recommended to use SFTP.
[*HUAWEI] aaa
[*HUAWEI-aaa] local-user huawei password irreversible-cipher Helloworld@6789
[*HUAWEI-aaa] local-user huawei ftp-directory flash:
[*HUAWEI-aaa] local-user huawei service-type ftp
[*HUAWEI-aaa] local-user huawei level 3
[*HUAWEI-aaa] commit
On the PC, set up an FTP connection to the device through the FTP client.
Assume that the device IP address is 10.110.24.254.
C:\Documents and Setting\Administrator> ftp 10.110.24.254
Connected to 10.110.24.254.
220 FTP service ready.
User (10.110.24.254:(none)): huawei
331 Password required for huawei.
Password:
230 User logged in.
c. Configure transfer parameters.
If the FTP user is authenticated, the FTP client displays the prompt
character of ftp>. Enter binary following the prompt character, and
specify the path where the uploaded file is to be saved on the FTP client.
ftp> binary
200 Type set to I.
ftp> lcd c:\temp
Local directory now C:\temp.
d. Transfer the configuration file.
On the PC, run the put command to upload the configuration file to the
specified path and save the file as backup.cfg.
ftp> put config.cfg backup.cfg
e. Check whether the backup.cfg file is successfully uploaded. If the
backup.cfg file exists on the device and has the correct size, the
configuration file recovery is successful.
f. Run startup saved-configuration configuration-file, specify the next
startup configuration file.
g. Run reboot, restart the device to make the file take effect.
----End
NOTICE
Exercise caution when you run the reset saved-configuration command. You are
advised to run this command under the guide of technical support personnel.
Procedure
● Run the reset saved-configuration command to cancel the configuration file
used for next startup. The default device configurations are restored.
NOTE
If the next startup configuration file is empty, the device displays a message indicating
that the file does not exist.
● Delete configurations on an interface at a time to restore the default
configurations.
NOTE
● Clear the inactive configurations of the boards that have not been installed.
a. Run system-view
----End
Context
If faults are caused by incorrect configurations or an unexpected configuration
result occurs on the network after the configuration is submitted, you can roll
back the configuration.
Before you roll back the configuration, the device has used either of two modes to
submit the configuration and generated a configuration rollback point.
● Immediate mode: After you enter the command and press Enter, the system
checks whether the current configuration is the same as the historical
configuration. If they are different, the system submits the configuration and
generates the configuration rollback point. Therefore, multiple configuration
rollback points may be generated when one feature is deployed.
● Two-stage mode: When running a series of configuration commands, you
must use the commit [ trial [ time ] ] [ label label ] [ description
description ] command to enable the system to compare the current
configuration with the historical configuration and generate a configuration
rollback point. In this way, all configurations for a certain service using a
series of commands can take effect. To quickly find the required configuration
rollback point, specify description description to configure the point
description. You are advised to use this mode to edit and submit the
configuration.
Procedure
Step 1 Check the configuration rollback points and the latest configuration changes.
1. Run display configuration commit list [ verbose ] [ number-of-commits |
label ]
All configuration rollback points and their details are displayed.
To check one or more configuration rollback points, specify number-of-
commits.
2. Run display configuration commit changes [ at commit-id | since commit-id
| last number-of-commits ]
The configuration change for a specified configuration rollback point is
displayed.
Based on the configuration change, you can determine whether to roll back
the configuration and the possible effects on the system.
– To check the configuration changes at all configuration rollback points,
do not specify any parameters in the command.
– To check the configuration change at a specified configuration rollback
point, specify at commit-id.
– To check the configuration change from a specified configuration rollback
point to the current state, specify since commit-id.
– To check one or more of the latest configuration changes, specify last
number-of-commits.
Step 2 Roll back the configuration based on the required historical configuration state.
1. Run return
Return to the user view to ensure that all data has been submitted before
rollback.
2. Run rollback configuration { to { commit-id commit-id | label label | file
file-name } | last number-of-commits }
The system is rolled back to the historical configuration state based on the
specified configuration rollback point, a user label for a configuration rollback
point, a configuration file for configuration rollback, or the number of
configuration changes.
Based on the configured rollback rule, run this command to delete the
created configuration, re-create the deleted configuration, or recover the
quondam configuration.
– To roll back the system to the historical configuration state at a certain
configuration rollback point, specify commit-id commit-id.
– To roll back the system to the historical configuration state at a user
label for a configuration rollback point, specify label label.
– To roll back the system to the historical configuration state at a
configuration file for configuration rollback, specify file file-name.
– To roll back the system to the historical configuration state before one or
more latest configuration rollback points, specify last number-of-
commits.
NOTE
After the configuration rollback operation is complete, you can run the display
configuration rollback result command to view the result of the latest configuration
rollback operation.
Step 4 (Optional) Run clear configuration commit { commit-id label | oldest number-
of-commits }
The label of a configuration rollback point specified in the system or the earliest
configuration rollback point generated in the system is deleted.
----End
Pre-configuration Tasks
Before configuring the system startup files, complete the following tasks:
● Start the device and logging in to the device locally or remotely.
● Save the system startup files in the root directory of the device.
Context
Before specifying the files for next startup, you can run the display startup
command to view the specified files for next startup.
● If no system software is specified for next startup, the device will start with
current system software. To change the system software to be loaded for next
startup (during an upgrade for example), upload the new system software to
the device and specify it as the system file for next startup. The system
software package must use .cc as the file name extension and be saved to the
root directory of the storage device. If the device has dual MPUs, the system
software must be saved to both the master MPU and slave MPU.
● If no configuration file is specified for next startup, the device will start with
the default configuration file (vrpcfg.zip for example). If no configuration file
is stored in the default directory, the device uses the default parameters for
initialization. The configuration file name extension must be .cfg, .dat, or .zip.
In addition, the configuration file must be saved in the root directory of the
storage device.
● A patch file uses .pat as the file name extension. The specified patch file to be
loaded for next startup must also be saved to the root directory of the storage
device. If the device has double MPUs, the patch file must be manually copied
to the slave MPU using the copy source-filename destination-filename
command when being uploaded to the master MPU. This ensures that the
patch file is saved in both the master MPU and slave MPU.
Procedure
● Configure the system software to be loaded for next startup.
a. (Optional) Run check system-software system-file
The integrity of the system software package is checked.
If you use method 1 to specify the configuration file for next startup, and other
configurations are deployed after the startup saved-configuration command is run, a
message will be displayed, asking you whether to save configurations when you
restart the device. Enter Y, and the configurations deployed later are contained in the
configuration file after the restart. If you use method 2, the configuration file for next
startup is the current backup configuration file and is not affected by the later
configuration change.
– (Method 1) Run startup saved-configuration configuration-file
The configuration file for next startup is specified.
The device reads the configuration file from the root directory of the
storage device for initialization when powered on.
– (Method 2) Run copy source-filename startup destination-filename
The configuration file is copied and the file copy is specified as the
configuration file for next startup.
● Configure the patch file to be loaded for next startup.
a. (Optional) Run check patch { file-name | startup }
The integrity of the patch package is checked.
b. Run startup patch patch-name all
The patch file for next startup is specified.
To make the patch file take effect after the device restarts, run this
command to specify the patch file for next startup.
----End
Pre-configuration Tasks
Before loading a digital certificate CRL, upload the CRL file to the flash directory
of the device.
Procedure
Step 1 Run software crl load crl-name
----End
If a required module does not exist in the system, you can use dynamic module
loading to successfully load the required module file to the system, and use
functions corresponding to the module. You can also dynamically uninstall the
module if functions corresponding to the module are no longer required.
NOTE
Pre-configuration Tasks
Obtain the .mod or .MOD file and upload the file to the switch.
Procedure
● Check the integrity of the dynamic module.
----End
Pre-configuration Tasks
Before restarting the device, complete the following tasks:
● Configure system startup files.
Context
Use either of the following methods to restart the device:
● Restart the device immediately after configuration: The device restarts
immediately after the reboot command is run.
● Restart the device at scheduled time: The device can be restarted at a
specified time later. When the configuration is complete, you can configure
the device to restart at time when few services are running to minimize the
impact of device restart on services.
The device restarts with the specified startup software. If the specified startup
software is damaged, the device restarts with the startup software that works last
time. If the software for last startup does not exist, the device searches for a valid
startup software package on the storage devices.
NOTE
When the system startup configuration file is large, boards may register slowly during the
system startup.
NOTICE
● Do not restart the device unless necessary because device restart causes service
interruption in a short time.
● Save the current configuration so that it will take effect after the device
restarts.
Procedure
● Restart the device immediately.
– The fast parameter indicates quick restart of the device. The system does
not ask you whether to save the configuration file in fast startup.
– save diagnostic-information indicates that the system will save the
diagnostic information to root directory of the storage device before
restarting.
● Restart the device at scheduled time.
In the user view, run the schedule reboot { at time | delay interval [ force ] }
command to restart the device at scheduled time.
----End
Context
Before committing a set of configuration, you can view the difference between the
modified configuration and current running configuration. If the running
configuration is changed during the period from configuration modification to
configuration difference viewing, a configuration conflict occurs. In addition, an
error message is displayed when you view the configuration difference. In this
case, resolve the configuration conflict so that you can continue to view the
configuration difference.
NOTE
Procedure
Step 1 Run system-view
----End
Networking Requirements
As shown in Figure 7-2, a user logs in to the device and backs up the
configuration file to the TFTP server. So the configuration file can be recovered in
case that the device is damaged.
Network
Configuration Roadmap
The configuration roadmap is as follows:
NOTICE
Configuration file backup through TFTP is simple, but there are security risks.
In scenarios with high security requirements, configuration file backup
through SFTP or SCP is recommended. The following describes the
configuration file backup process using TFTP as an example.
Procedure
Step 1 Save configurations to the config.cfg file.
<HUAWEI> save config.cfg
Start the TFTP server program on the PC. Set the path for transmitting the
configuration file, and the IP address and port number of the TFTP server.
2. Transfer the configuration file.
# Run the tftp command in the user view to back up the specified
configuration file.
<HUAWEI> tftp 10.110.24.254 put flash:/config.cfg backup.cfg
----End
Networking Requirements
As shown in Figure 7-3, a user logs in to the device and finds that some incorrect
configurations cause errors in the system. To recover the original configuration,
the user downloads the configuration file saved in the TFTP server to the device
and specifies the configuration file for the next startup.
Network
Configuration Roadmap
The configuration roadmap is as follows:
NOTICE
Configuration file recovery through TFTP is simple, but there are security risks.
In scenarios with high security requirements, configuration file recovery
through SFTP or SCP is recommended. The following describes how to recover
the configuration file that is backed up on a PC through TFTP.
Procedure
Step 1 Recover the configuration file that is backed up on the PC through TFTP.
1. Start the TFTP server program.
Start the TFTP server program on the PC. Set the path for transmitting the
configuration file, and the IP address and port number of the TFTP server.
2. Transfer the configuration file.
Step 2 Specify the recovered configuration file for the next startup.
<HUAWEI> startup saved-configuration config.cfg
----End
Networking Requirements
As shown in Figure 7-4, a user logs in to the switch and configures an IP address
for each switch interface. Generally, after submitting the configuration, the user
cannot check the latest configurations and can only check the current
configuration file. When the configurations are incorrect or an unexpected
configuration result occurs on the network, the user can only manually delete or
modify the configurations one by one and cannot perform the batch recovery
operation.
Network0 Network2
Switch
10GE1/0/1 10GE1/0/3
10GE1/0/2 10GE1/0/4
Network1 Network3
To solve the preceding problem, the user can check the difference between the
historical and current configurations and roll back the system configuration to the
appropriate configuration point without restarting the system or interrupting
services.
In this example, the user finds that IP addresses are incorrectly configured for
interfaces and wants to reconfigure them. By using the traditional method, the
user must enter each interface view to delete the corresponding IP address and
reconfigure the IP address. By using the configuration rollback function, the user
can recover the configurations to the configuration state when the IP addresses
have not been configured, which greatly simplifies configuration recovery.
Configuration Roadmap
The configuration roadmap is as follows:
● Check the configuration rollback points and the latest configuration changes.
● Determine the configuration rollback point or the number of configuration
changes to roll back the configuration.
Procedure
Step 1 Configure IP addresses for 10GE1/0/1, 10GE1/0/2, 10GE1/0/3, and 10GE1/0/4 on
the switch.
<HUAWEI> system-view
[~HUAWEI] sysname Switch
[*HUAWEI] commit
[~Switch] vlan batch 77 to 80
[*Switch] interface vlanif 77
[*Switch-Vlanif77] ip address 10.0.1.1 24
[*Switch] quit
[*Switch] interface vlanif 78
[*Switch-Vlanif78] ip address 10.0.2.1 24
[*Switch] quit
[*Switch] interface vlanif 79
[*Switch-Vlanif79] ip address 10.0.3.1 24
[*Switch] quit
[*Switch] interface vlanif 80
[*Switch-Vlanif80] ip address 10.0.4.1 24
[*Switch] quit
[*Switch] interface 10ge 1/0/1
[*Switch-10GE1/0/1] port link-type trunk
[*Switch-10GE1/0/1] port trunk allow-pass vlan 77
[*Switch-10GE1/0/1] quit
[*Switch] interface 10ge 1/0/2
[*Switch-10GE1/0/2] port link-type trunk
[*Switch-10GE1/0/2] port trunk allow-pass vlan 78
[*Switch-10GE1/0/2] quit
[*Switch] interface 10ge 1/0/3
[*Switch-10GE1/0/3] port link-type trunk
[*Switch-10GE1/0/3] port trunk allow-pass vlan 79
[*Switch-10GE1/0/3] quit
[*Switch] interface 10ge 1/0/4
[*Switch-10GE1/0/4] port link-type trunk
[*Switch-10GE1/0/4] port trunk allow-pass vlan 80
[*Switch-10GE1/0/4] quit
[*Switch] commit
[~Switch] quit
Step 2 Check the configuration rollback points and the difference between the historical
and current configurations.
2) CommitId: 1000000005
Label: -
User: root
User-Intf: VTY 1
Type: CLI
TimeStamp: 2012-06-29 15:50:05
Description:
3) CommitId: 1000000004
Label: -
User: root
User-Intf: VTY 0
Type: CLI
TimeStamp: 2012-06-29 09:57:34
Description:
4) CommitId: 1000000003
Label: -
User: root
User-Intf: VTY 0
Type: CLI
TimeStamp: 2012-06-29 09:57:21
Description:
5) CommitId: 1000000002
Label: -
User: anonymous
User-Intf: CON 0
Type: CLI
TimeStamp: 2012-06-28 16:31:48
Description:
6) CommitId: 1000000001
Label: -
User: anonymous
User-Intf: CON 0
Type: CLI
TimeStamp: 2012-06-28 16:31:48
Description:
interface 10GE1/0/1
+ port link-type trunk
+ port trunk allow-pass vlan 77
#
interface 10GE1/0/2
+ port link-type trunk
+ port trunk allow-pass vlan 78
#
interface 10GE1/0/3
+ port link-type trunk
+ port trunk allow-pass vlan 79
#
interface 10GE1/0/4
+ port link-type trunk
+ port trunk allow-pass vlan 80
#
# Roll system configurations back to what they were before the most recent
configuration rollback point was created.
<Switch> rollback configuration last 1
Warning: This operation will revert configuration changes to the previous status. Continue? [Y/N]:y
Loading rollback changes
Committing
Check rollback result
Configuration rollback succeeded.
Please use 'display configuration commit changes last 1' to view the changes.
2) CommitId: 1000000006
Label: -
User: root
User-Intf: VTY 1
Type: CLI
TimeStamp: 2012-06-29 15:55:20
Description:
3) CommitId: 1000000005
Label: -
User: root
User-Intf: VTY 1
Type: CLI
TimeStamp: 2012-06-29 15:50:05
Description:
4) CommitId: 1000000004
Label: -
User: root
User-Intf: VTY 0
Type: CLI
TimeStamp: 2012-06-29 09:57:34
Description:
5) CommitId: 1000000003
Label: -
User: root
User-Intf: VTY 0
Type: CLI
TimeStamp: 2012-06-29 09:57:21
Description:
6) CommitId: 1000000002
Label: -
User: anonymous
User-Intf: CON 0
Type: CLI
TimeStamp: 2012-06-28 16:31:48
Description:
7) CommitId: 1000000001
Label: -
User: anonymous
User-Intf: CON 0
Type: CLI
TimeStamp: 2012-06-28 16:31:48
Description:
----End
Configuration Files
Switch configuration file
#
sysname Switch
#
interface 10GE1/0/1
#
interface 10GE1/0/2
#
interface 10GE1/0/3
#
interface 10GE1/0/4
#
return
Networking Requirements
As shown in Figure 7-5, the device has dual main processing units (MPUs), and
the current system software cannot meet user needs. The device must load new
software version with more features. Then the device software needs to be
upgraded remotely.
PC Device
Configuration Roadmap
The configuration roadmap is as follows:
1. Upload the new system software to the root directory of the device. When the
device has dual MPUs, save the system software to both the master MPU and
slave MPU.
2. Save the current configuration so that it remains active after upgrade.
3. Specify the system software for next startup.
4. Specify the configuration file for next startup of the device.
5. Restart the device to complete upgrade.
Procedure
Step 1 Upload the new system software to the root directory of the device.
Before configuration, run the display startup command to view the files for next
startup.
<HUAWEI> system-view
[HUAWEI] sysname Switch
[Switch] quit
<Switch> display startup
MainBoard:
Configured startup system software: flash:/basicsoft.cc
Startup system software: flash:/basicsoft.cc
Next startup system software: flash:/basicsoft.cc
Startup saved-configuration file: flash:/vrpcfg.zip
Next startup saved-configuration file: flash:/vrpcfg.zip
Startup paf file: default
Next startup paf file: default
Startup patch package: NULL
Next startup patch package: NULL
SlaveBoard:
Configured startup system software: flash:/basicsoft.cc
Startup system software: flash:/basicsoft.cc
Next startup system software: flash:/basicsoft.cc
Startup saved-configuration file: flash:/vrpcfg.zip
Next startup saved-configuration file: flash:/vrpcfg.zip
Startup paf file: default
Next startup paf file: default
Startup patch package: NULL
Next startup patch package: NULL
# Upload the new system software to the device. This example uses FTP to
transfer the system software. Configure the device as an FTP server and upload
the system software to the device from the FTP client. Make sure there is enough
space in the storage device before uploading files. If the space is insufficient,
delete unnecessary files to free up space in the storage device.
<Switch> system-view
[Switch] ftp server enable
# Run the ftp 10.1.1.1 command in the command line window of the PC to set up
an FTP connection with the device. Run the put command to upload new system
software newbasicsoft.cc. After the upload completes, run the dir command to
check the system software.
<Switch> dir
Directory of flash:/
Run dir slave#flash: to check whether the file has been copied to the slave MPU.
Step 2 Save the current configuration to both the master and slave MPUs.
<Switch> save
The current configuration will be written to the device.
Are you sure to continue? [Y/N]y
Now saving the current configuration to the slot 0 .
Info: Save the configuration successfully.
NOTE
When the device has double MPUs, save the system software to both master and slave
MPUs. Then configure the system software for next startup on both the master and slave
MPUs.
NOTE
● In step 1, you can run the display startup command to check the configuration file for
next startup. The message "Next startup saved-configuration file: flash:/vrpcfg.zip will
be displayed. This means that the vrpcfg.zip configuration file has been specified for
next startup, so skip this step. To specify another file for next startup, perform this step.
● If a configuration file is specified for next startup on the master MPU, the slave MPU
automatically updates the configuration for next startup.
----End
Configuration File
#
FTP server enable
#
vlan batch 10
#
aaa
local-user huawei password irreversible-cipher $1c$g8wLJ`LjL!$CyE(V{3qg5DdU:PM[6=6O
$UF-.fQ,Q}>^)OBzgoU$