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

Reminder

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

upgrade

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function 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).
System Startup Overview

System Startup Overview

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

System startup scenarios are as follows:
  • Version upgrade: Upgrade the system software to a later version.

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

  • Version rollback: Degrade the software to an earlier version.

    If an error occurs after the upgrade, perform version rollback to restore normal service operating. You need to load earlier version system software and restart the device.

  • First startup: When a new device is deployed on a network, you can load an existing configuration file on the device to meet user needs.

    A new device contains only 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.

NOTE:
  • 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 http://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 CX11x&CX31x&CX91x Series Switch Modules Command 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 configuration file saves configuration commands.

  • Only non-default parameters are stored in the configuration file, which saves 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 order of global configurations, interface-based configurations, protocol configurations, and user interface configurations.

  • The configuration file name extension must be .cfg,.dat, or .zip. In addition, the configuration file must be saved to the root directory of the storage device.

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

Concept

Description

Command

Configuration file

When the device is powered on, the device reads the configuration file from the default directory to boot the system. Therefore, the configuration in the file is called the initial configuration. If no configuration file is stored in the default directory, 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.

Offline Configuration

The system supports offline configuration. Specifically, after a device quits a stack system, the configurations on the device are not affected and you can continue to configure its interfaces in the stack system. If another device of the same type joins the stack system, the configurations are restored on the new device.

If another device joins the stack system, the impacts on the previous configurations are as follows:
  • The new device has the same type and stack ID as the previous device.

    The system automatically restores the configurations of all interfaces on the new device. Then, users can view interface configurations and configure the interfaces on the new device.

  • The new device has interfaces of a different type by the same stack ID as the previous device.

    The system deletes the configurations of all interfaces on the previous device. The deleted configurations cannot be restored.

    For example, device A has interfaces of type P and configuration information on its interfaces.
    1. Remove device A and then add device C with interfaces of type E to the stack system.
    2. Remove device C from the stack system without configuring its interfaces. If you run the display this command in the interface view on device C, the command output does not contain original configurations on device A.
    3. Add device A or another device with interfaces of type P. If you run the display this command in the interface view on device A or the device with interfaces of type P, the command does not contain original configurations on device A, either.
  • The new device has a different number of interfaces of the same type as those on the previous device.

    • If the new device has more interfaces than the previous device does, the system performs the following operations:

      • Restores the configuration information on the interfaces that are the same as those on the previous device.
      • Keeps default configuration information on the other interfaces of the new device.
    • If the new device has fewer interfaces than the previous device does, the system performs the following operations:

      • Restores the configuration information on the interfaces that are the same as those on the previous device.
      • Delete the other interfaces of the previous device and their configuration information.

Offline configuration is marked with *. To view the offline configuration, run the display current-configuration inactive or display current-configuration all command.

NOTE:
The symbol * has two meanings:
  1. When * is displayed in an interactive operation, it indicates the configurations that have not been submitted.
  2. When * is displayed in configuration information, it indicates the offline configurations.

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 for the CP to take effect. Services are interrupted during the restart.

According to patch dependency, patches can be classified into incremental and non-incremental patches.
  • 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.

NOTE:

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.

Table 1-94 describes the patch status.

Table 1-94 Status of patches

Status

Description

Patch Status Transition

Idle

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.

Deactive

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

You can perform either of the following operations on the patch that is 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.

Active

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

The active patch changes to the deactive state when the device is restarted.

You can perform one of the following operations on the patch that is in the active state:
  • Uninstall the patch to delete it from the patch area.
  • Stop running the patch to change the patch to the deactive state.
  • Run the patch permanently to change the patch to the running state.

Running

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

The running patch remains in the running state when the device is restarted.

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

Figure 1-33 shows patch status transition.

Figure 1-33 Patch status transition

Installing Patches

Installing patches is a way of upgrading a device. Patches can be installed in the following ways:

  • The hot patches are generally installed while the device is running without interrupting services. This is an advantage of hot patches.

    NOTE:

    For details on how to install patches, see the corresponding release notes. For details about commands used for device upgrade, see "Basic Configurations Commands - Upgrade Commands" in the CX11x&CX31x&CX91x Series Switch Modules 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.

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 57854

Downloads: 3621

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next