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 - Virtualization
CloudEngine 12800 and 12800E V200R002C50

This document describes the configurations of virtualization, including stack and VS.

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 Setup

Stack Setup

After two switches are connected using stack cables and configured with required stack parameters, they can set up a stack.

Role Election

After a stack is set up, member switches exchange stack competition packets to elect a master switch. The switch that wins the competition becomes the master switch and manages the entire stack. The other switch becomes the standby switch and works as a backup of the master switch.

The two switches compare the following items in the listed order to elect the master switch (the election ends when a winning switch is found):
  1. Running status: The switch that completes startup becomes the master switch.

  2. Stack priority: The switch with a higher stack priority becomes the master switch.

  3. Software version: The switch running a later software version becomes the master switch.

  4. Number of main processing units (MPUs): The switch with two MPUs is preferred over the switch with only one MPU.

  5. Bridge MAC address: The switch with the smallest bridge MAC address becomes the master switch.

If the master and standby switches have the same stack member ID, the master switch assigns a new stack member ID to the standby switch. Then the standby switch restarts and rejoins the stack.

After a stack is set up, the master MPU of the master switch works as the system master MPU to manage the entire stack. The master MPU of the standby switch works as the system standby MPU. The standby MPUs of the master and standby switches work as candidate system standby MPUs. Figure 1-10 shows the role election result after a stack is set up. In this example, SwitchA is elected as the master switch.

Figure 1-10 Role election in a stack

Software Version Synchronization

A stack supports software version synchronization between the member switches. The member switches do not have to run the same software version, and they can set up a stack as long as their software versions are compatible with each another. If the software version running on the standby switch is different from that on the master switch, the standby switch downloads the system software from the master switch, restarts with the new system software, and rejoins the stack.

Configuration File Synchronization

A stack uses a strict configuration file synchronization mechanism to ensure that the member switches work like one device.

  • When setting up a stack, member switches first start with their own configuration files. After they complete the startup process, the standby switch combines its stack configuration with the configuration file of the master switch. This configuration file is then used as the configuration file of the stack.

  • When the stack is running normally, the master switch manages the entire stack, and synchronizes configurations made by users to the standby switch in real time to maintain configuration consistency between them.

Real-time configuration file synchronization ensures that both member switches in a stack maintain the same configuration. When the master switch fails, the standby switch can provide the same functions using the same configuration.

Configuration Combination and Conflict Detection

Configuration Combination

Stack configuration on a switch is saved in the configuration file. When a stack is set up, the standby switch combines its own stack configuration with that of the master switch. The configuration combination rules are as follows:
  • The standby switch combines its stack configuration with that of the master switch, including the stack attribute configuration, stack port configuration, and port split configuration. If the master switch has the offline stack configuration of the standby switch, the stack configuration of the master switch takes effect.

    As shown in Figure 1-11, SwitchA and SwitchB in a stack combine their port configurations. Port 10GE2/1/0/2 on SwitchA has common service configuration, which conflicts with the configuration on SwitchB. SwitchA is the master switch, so the port configuration on SwitchA takes effect.

  • After a stack is set up, the standby switch synchronizes its configuration file with that of the master switch to maintain the same configuration with the master switch.

    As shown in Figure 1-11, SwitchB synchronizes its configuration file with that of SwitchA after the stack is set up.

Figure 1-11 Port configuration combination

Configuration Conflict Detection

A configuration conflict may occur if the master switch has offline configurations made for the standby switch, which may cause a stack setup failure. A configuration conflict occurs in the following situations:
  • In MPU connection mode:

    • All SIP ports on the standby switch are disabled using the shutdown command on the master switch.

  • In line processing unit (LPU) connection mode:

    • When member switches combine their stack member port configurations, the number of stack member ports in a stack port exceeds the limit.

    • All stack member ports configured on the standby switch are disabled using the shutdown command on the master switch or conflict with the configuration on the master switch.

    • Stack ports of the standby switch have the shutdown configuration or the configuration that conflicts with the stack on the master switch.

    • A stack contains stack member ports of different types.

When any of the preceding conflicts occurs, the standby switch cannot set up a stack with the master switch. In this case, modify the configuration of the master switch or the standby switch to avoid configuration conflicts, and then restart the switch.

Configuration File Backup

When the stacking function is enabled or disabled on a switch, the switch automatically backs up its configuration file. In this way, the switch can restore the original configuration after the stacking function is disabled or enabled. The backup configuration file is saved in flash:/, and the file name contains the original configuration file name and the time when the file is saved (in the yyyymmddhhmmss format). For example, if the original configuration file is vrpcfg.cfg and you enable the stacking function at 11:17:16 on 2012-12-11, the backup configuration file is named vrpcfg20121211111716.cfg.

Translation
Download
Updated: 2019-03-21

Document ID: EDOC1000166610

Views: 47167

Downloads: 136

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next