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 8800, 7800, 6800, and 5800 V200R005C10

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

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

A stack is set up after the following stages:
  1. Physical connection: Multiple switches are physically connected in a specific topology based on network requirements to set up a stack. For details about the stack connection modes, see Stack Connection Mode.

  2. Master election: Stack members exchange stack competition packets to elect the master switch based on master election rules.

  3. Topology collection: The master switch collects information about other member switches and calculates the topology. If some member switches use the same stack member ID, the master switch assigns new stack member IDs to these member switches to avoid conflicts.

  4. Stable running: The master switch synchronizes the stack topology to other member switches and selects the standby switch.

Master Election

During stack setup, member switches exchange stack competition packets to elect the master switch. The stack members 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 first becomes the master switch.

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

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

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

Topology Collection and Stable Running

After the master switch is elected, it collects information about other member switches and calculates the topology. If some member switches use the same stack member ID, the master switch assigns new stack member IDs to these member switches to avoid conflicts.

After the master switch calculates the topology, it synchronizes the stack topology to other member switches and elects the standby switch. The stack members compare the following items in the listed order to elect the standby switch (the election ends when a winning switch is found):
  1. Stack priority: The switch with the second highest stack priority becomes the standby switch.

  2. MAC address: The switch with the second smallest MAC address becomes the standby switch.

Software Version Synchronization

A stack supports software version synchronization among stack members. The stack members do not need to run the same software version as long as their software versions are compatible with each another. After stack master election is complete, if the software version or software name of other member switches is different from that of the master switch, other member switches download the system software from the master switch, restart with the new system software, and join the stack again.

Configuration Synchronization

A stack uses a strict configuration file synchronization mechanism to ensure that all stack members work like a single device on the network.

  • During stack setup, stack members use their own configuration files to start. After stack members complete their startup, the standby and slave switches combine their stack configurations into the configuration file of the master switch to form the stack configuration file.

  • When the stack is running properly, the master switch manages the entire stack, and synchronizes its configuration to other stack members to ensure consistent configuration on all stack members.

This synchronization mechanism ensures that all stack members use the same configuration file. Even if the master switch is faulty, other stack members can provide the same functions according to the same configuration file.

Configuration Combination and Conflict Detection

Configuration Combination

Stack configuration is saved in a configuration file. During stack setup, the standby and slave switches combine their stack configurations with that of the master switch according to the following rules:
  • The configurations of the standby and slave switches are combined 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 configurations of the standby and slave switches, the stack configuration of the master switch takes effect.

    In Figure 1-10, SwitchA and SwitchB in a stack combine their port configurations. 10GE2/0/5 of SwitchA has the common service configuration, which conflicts with the port configuration of SwitchB. Because SwitchA is the master switch, its port configuration takes effect.

  • After the stack is set up, the standby and slave switches synchronize their configuration files with that of the master switch to use the same configuration as the master switch.

    In Figure 1-10, SwitchB synchronizes its configuration file with that of SwitchA after the stack is set up.

Figure 1-10 Port configuration combination

Configuration Conflict Detection

A configuration conflict may occur if the master switch has the offline configurations of the standby and slave switches during stack setup. In this case, the stack cannot be set up. A configuration conflict often occurs in the following situations:
  • When port configurations are combined, the number of stack member ports in a stack port exceeds the upper limit.

  • All stack member ports of the standby and slave switches have the shutdown configuration on the master switch or have the configuration that conflicts with the stack.

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

  • Different types of stack member ports are added to the same stack port.

  • The same stack member ports on stack members are added to different stack ports.

If any of the preceding conflicts occurs, the standby and slave switches cannot set up a stack with the master switch. You need to modify the configuration of the master, standby, or slave switch to avoid configuration conflicts, and then restart the switch to make the modification take effect.
Translation
Download
Updated: 2020-01-07

Document ID: EDOC1100075367

Views: 12289

Downloads: 80

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next