No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Configuration Guide - Basic Configuration

S7700 and S9700 V200R011C10

This document describes methods to use command line interface and to log in to the device, file operations, and system startup configurations.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Overview of System Startup

Overview of System Startup

The system loads the system software, configuration file and certificate file during startup. If a patch file is specified for next startup, the system also loads the specified patch file.

System startup scenarios include:
  • Version upgrade

    Upgrade the system software to a later version. Upgrade the device to add new features, optimize existing features, or solve problems in the current version. To upgrade the device, load the upgrade system software and restart the device.

  • Version rollback

    Downgrade the system software to an earlier version. Perform version rollback to restore normal service operating if an error occurs after the upgrade. You need to load the earlier version system software and restart the device.

  • First startup

    When deploying a new device on a network, load an existing configuration file on the device to perform initial configuration quickly.

    A new device contains only default factory configurations. To connect a new device to the network and deploy services on it, you have to spend a lot of time on device configuration. To save time on device configuration, specify a configuration file that meets user needs for the device and restart the device.

  • Patch update

    Specify the patch file to be loaded after an upgrade. You can specify a new patch file when upgrading the device. The patch takes effect immediately when the upgrade is complete.

  • 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 and download the upgrade guide based on the product name and version.

  • For details about commands used for device upgrade, see Upgrade Commands in "Basic Configurations Commands" in the S7700 and S9700 V200R011C10 Command Reference.

System Software

The device software includes BootROM/BootLoad software and system software. After the device is powered on, it runs the BootROM/BootLoad 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 BootROM/BootLoad software and system software are prerequisites for device startup and operation, providing support, management, and services for the device.

A device upgrade includes BootROM/BootLoad software upgrade and system software upgrade.

The BootROM/BootLoad software is included in the system software package (.cc file) of the device. The BootROM/BootLoad software is automatically upgraded during system software upgrade.

Configuration File

A configuration file is a collection of command lines. The current configurations are saved in the configuration file, and continue to take effect after the device restarts. You can view configurations in the configuration file or upload the file to other devices to implement batch configuration.

A configuration file is in text format and meets the following requirements:

  • The configuration file saves configuration commands.

  • The configuration file stores only non-default parameters to save the space.

  • The commands used in the same command view form a section. Sections are separated by blank lines or comment lines beginning with comment signs (#). There can be one or multiple blank or comment lines.

  • Sections are arranged in the following order: global configurations, interface-based configurations, protocol configurations, and user interface configurations.

  • The configuration file name extension must be .cfg or .zip. In addition, the configuration file must be saved to the root directory of the storage device.
    • A configuration file with the file name extension .cfg is a text file, and you can view the file content in the text file. After the file is specified as the configuration file for next startup, the system restores all commands in the file one by one during a startup.
    • A .cfg file is compressed to a .zip file that occupies less space. After being specified as the configuration file, the .zip file is decompressed to the .cfg file and the system restores all commands in the .cfg file one by one during startup.
  • The commands in a configuration file must be expressed in their complete forms. Abbreviations are not allowed.
  • Each command in a configuration file is wrapped using \r\n. No other invisible characters can be used to wrap commands.
  • It is recommended that you transfer the configuration file to a device using FTP in binary mode.

The following table describes the factory configuration, configuration file, and current configuration.




Factory configuration

Factory configuration is the basic configuration on a new device, which enables the device to start and work properly when there is no configuration file or the configuration file is lost or damaged.


Configuration file

When the device is powered on, it reads the configuration file from the default directory to boot the system. The configuration in this file is called the initial configuration. If the default directory does not contain a configuration file, the device uses the default parameters for initialization.

  • Run the display startup command to check the current and next startup configuration files.
  • Run the display saved-configuration command to check the configuration file for next startup.

Current configuration

The configurations that are valid during the device running are called current configurations.

Run the display current-configuration command to check the current configuration.

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.

A configuration file can contain 30,000 command lines. If more than 30,000 commands are configured, some commands may be lost after an upgrade.

The maximum length of a command supported by the system is 510 characters. 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 exceed the maximum length of 510 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.

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 numbers for users to identify, manage, and operate the patches.

Patch Classification

Patches are classified into hot and cold patches based on their impact on services.
  • Hot patch (HP): does not interrupt services when being loaded and activated, which reduces upgrade costs and avoids upgrade risks.

  • Cold Patch (CP): takes effect only after a reboot of the device or reset of cards. Services are interrupted during the reboot.

Patches are also classified into incremental and non-incremental patches based on patch dependency.
  • An incremental patch is dependent on previous patches. A new patch file contains all the patch information in the previous patch file. You can install the patch file without uninstalling the original patch file.

  • A non-incremental patch is exclusive in the current system. To install another patch file when there is already one, uninstall the existing patch file, and then install and run the new patch file.

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.

Patch State

Each patch has its own state that can only be changed using commands.

Table 8-1 describes patch states.

Table 8-1  Patch states



Patch State Transition


The patch file is saved to the storage device but has not been loaded to the patch area.

When a patch in the storage device is loaded to the patch area, the patch is in the deactive state.


When a patch is loaded to the patch area, the patch is in the deactive state.

You can perform either of the following operations on a patch in the deactive state:
  • Uninstall the patch to delete it from the patch area.
  • Run the patch file temporarily to change the state to active.


When a patch is stored in the patch area and runs temporarily, the patch is in the active state.

If a card is reset, the active patch on the card remains active. The active patch changes to the deactive state only when the device is restarted.

You can perform either of the following operations on a patch in the active state:
  • Uninstall the patch to delete it from the patch area.
  • Run the patch permanently to change the patch to the running state.


When a patch is stored in the patch area and runs permanently, the patch is in the running state.

If a card is reset or the device is restarted, the running patch on the card or device remains in the running state.

You can unload a patch in the running state so that it can be deleted from the patch area.

Figure 8-1 shows the transitions between different patch states.

Figure 8-1  Patch state transition

Installing Patches

Installing patches is a way of upgrading a device. You can install patches in the following ways:

  • Install hot patches on a running device 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 Upgrade Commands in "Basic Configurations Commands" in the S7700 and S9700 V200R011C10 Command Reference.

  • Specify a patch file for next startup, which is described in this chapter. The patch file takes effect after the device restarts. The method is often used during a system upgrade.

Updated: 2020-02-04

Document ID: EDOC1000178308

Views: 100487

Downloads: 152

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next