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

Configuration Guide - Device Management

S1720, S2700, S5700, and S6720 V200R011C10

This document describes the principles and configurations of the Device Management features, and provides configuration examples of these features.
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).
Stack Upgrade

Stack Upgrade

A stack supports three upgrade methods: intelligent upgrade, traditional upgrade, and smooth upgrade.

Intelligent Upgrade

When a stack is set up or new member switches join a stack, the standby and slave switches or new member switches check whether their software versions are the same as that of the master switch. If not, they download the system software from the master switch, restart with the new system software, and rejoin the stack.

Traditional Upgrade

You can specify the startup system software on the master switch and restart the entire stack to upgrade the software of member switches. This upgrade method causes service interruption for a relatively long time and can be used in scenarios insensitive to the service interruption time.

Smooth Upgrade

A smooth upgrade can be performed in a stack that has uplinks and downlinks working in redundancy mode. As shown in Figure 9-15, the stack is divided into an active area (with the master switch) and a backup area. Member switches in the two areas are upgraded in turn. When an area is being upgraded, traffic is transmitted through the other area, minimizing the impact of the upgrade on services. Use this upgrade method for the scenarios that are sensitive to the service interruption time.

In a network where uplinks and downlinks work in redundancy mode, both upstream traffic and downstream traffic are forwarded through the active and backup areas. When member switches in the backup area are upgrading, traffic is forwarded through the active area. When member switches in the active area are being upgraded, traffic is forwarded through the backup area.

NOTE:

To implement smooth upgrade for a stack, the stack must have uplinks and downlinks working in redundancy mode.To ensure a successful upgrade, you are advised to add at least one link on each member switch to an inter-device Eth-Trunk.

Figure 9-15  Networking for a smooth upgrade
Requirements for a Smooth Upgrade
  • The uplinks and downlinks work in redundancy mode.

  • The system software for the next startup supports the smooth upgrade function.

  • Member switches in the stack are running the same system software, with the same software package name, version, and path.

  • Member switches have the same system software specified for next startup, with the same software package name, version, and path.

Rules for Defining Active and Backup Areas
  • The active and backup areas cannot have the same member switch, and both areas must have at least one member switch.
  • The backup area cannot contain the master switch.
  • Member switches in each area must be directly connected.
  • Member switches in the active and backup areas constitute the entire stack.
Figure 9-16 shows an example. The switch with stack ID 1 is the master switch of the stack. If the stack ID range that you specify for the backup area is 4 to 3, the backup area contains member switches with stack IDs 4, 6, 5, and 3, and the active area contains member switches with stack IDs 1 and 2.
Figure 9-16  Defining active and backup areas

Smooth Upgrade Process

A smooth upgrade goes through three stages:
  1. The master switch issues the smooth upgrade command to the entire stack. Member switches in the backup area restart with the new system software.
  2. Member switches in the backup area set up an independent stack running the new system software and notify member switches in the active area. The master switch in the backup area starts to control the stack, and traffic is transmitted through the backup area. The active area then starts the upgrade.
  3. Member switches in the active area restart with the new system software and join the stack set up in the backup area. The master switch in the backup area displays the upgrade result depending on the stack setup result.
NOTE:

If errors or exceptions occur during a smooth upgrade, or the upgrade times out (the timeout interval is 70 minutes), member switches automatically roll back to the original system version and set up a stack again.

Translation
Download
Updated: 2019-09-23

Document ID: EDOC1000178167

Views: 206310

Downloads: 989

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