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 - Ethernet Switching

S7700 and S9700 V200R012C00

This document describes the configuration of Ethernet services, including configuring MAC address table, link aggregation, VLANs, VLAN aggregation, MUX VLAN, VLAN termination, Voice VLAN, VLAN mapping, QinQ, GVRP, VCMP, STP/RSTP/MSTP, VBST, SEP, RRPP, ERPS, LBDT, HVRP, and Layer 2 protocol transparent transmission.
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).
Licensing Requirements and Limitations for MUX VLANs

Licensing Requirements and Limitations for MUX VLANs

Involved Network Elements

Other network elements are not required.

Licensing Requirements

The MUX VLAN is a basic feature of a switch and is not under license control.

Version Requirements

Table 7-2  Products and versions supporting MUX VLAN

Product

Product Model

Software Version

S7700

S7703, S7706, S7712

V100R003C01, V100R006C00, V200R001(C00&C01), V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00, V200R013C00

S7703 PoE

V200R013C00

S7706 PoE

V200R013C00

S9700

S9703, S9706, S9712

V200R001(C00&C01), V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007(C00&C10), V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00, V200R013C00

NOTE:
For details about software mappings, visit Hardware Query Tool and search for the desired product model.

Feature Limitations

  • Table 7-3 describes the specifications of the MUX VLAN.
    Table 7-3  Specifications of the MUX VLAN
    Item Specification

    Maximum number of principal VLANs on the entire device

    128

    Maximum number of separate VLANs in each principal VLAN

    1

    Maximum number of group VLANs in each principal VLAN

    128

    NOTE:

    Each principal VLAN supports a total of 128 separate and group VLANs. That is, if one separate VLAN is configured, a maximum of 127 group VLANs can be configured.

  • The VLAN ID assigned to a principal VLAN cannot be used to configure VLAN mapping, VLAN stacking, super-VLAN, or sub-VLAN.
  • The VLAN ID assigned to a group or separate VLAN cannot be used to configure a VLANIF interface, VLAN mapping, VLAN stacking, super-VLAN, or sub-VLAN.
  • The VLAN ID assigned to a Layer 2 static multicast group and the MUX VLAN IDs (including the principal VLAN ID and subordinate VLAN IDs) cannot be the same.
  • Disabling MAC address learning or limiting the number of learned MAC addresses on an interface will compromise the performance of the MUX VLAN function.
  • The VLAN specified in the static MAC address entry cannot be the MUX VLAN.
  • MUX VLAN and port security cannot be configured on the same interface.
  • MUX VLAN and MAC address authentication cannot be configured on the same interface.
  • MUX VLAN and 802.1x authentication cannot be configured on the same interface.
  • When both DHCP snooping and MUX VLAN are configured, if DHCP snooping is configured in the subordinate VLAN and DHCP clients are configured in the principal VLAN, the DHCP clients may fail to obtain IP addresses. In this case, configure the DHCP server in the principal VLAN.

  • After the MUX VLAN function is enabled on an interface, VLAN mapping or VLAN stacking cannot be configured on the interface.
  • You cannot create a VLANIF interface for a subordinate group VLAN or separate VLAN. However, you can create a VLANIF interface for a principal VLAN. If a VLANIF interface is created for a principal VLAN, you cannot run the port mux-vlan enable command on an interface of the ES0D0G24SA00, ES0D0G24CA00, EH1D2G24SSA0, and EH1D2S24CSA0 cards of SA series to enable the MUX VLAN function including the principle and subordinate VLANs.
  • When the interface is enabled with MUX VLAN and configured with the PVID using the port trunk pvid vlan command, do not configure the PVID as the ID of the principal VLAN or subordinate VLAN of the MUX VLAN. For example, VLAN 10 is the principal VLAN, VLAN 11 is a subordinate group VLAN, and VLAN 12 is a subordinate separate VLAN. After the port mux-vlan enable vlan 10 command is used on the interface to enable MUX VLAN, do not run the port trunk pvid vlan command to set the PVID to VLAN 11 or VLAN 12.
  • In versions earlier than V200R012C00, the MUX VLAN cannot forward Layer 2 multicast traffic. Starting from V200R012C00, after the multicast-snooping mux-vlan enable command is run in the system view, the MUX VLAN can forward Layer 2 multicast traffic.
Translation
Download
Updated: 2019-01-18

Document ID: EDOC1100038843

Views: 107267

Downloads: 71

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