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

CloudEngine 8800, 7800, 6800, and 5800 V200R003C00

This document describes the configuration of Ethernet services, including configuring MAC address table, link aggregation, VLANs, MUX VLAN, Voice VLAN, VLAN mapping, QinQ, GVRP, VCMP, STP/RSTP/MSTP, VBST, SEP, RRPP, ERPS, LBDT, 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 VLANs

Licensing Requirements and Limitations for VLANs

Involved Network Elements

Other network elements are not required.

Licensing Requirements

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

Version Requirements

Table 5-8 Products and minimum version supporting VLAN technology

Product

Minimum Version Required

CE8860EI

V100R006C00

CE8861EI/CE8868EI

V200R005C10

CE8850-32CQ-EI

V200R002C50

CE8850-64CQ-EI

V200R005C00

CE7850EI

V100R003C00

CE7855EI

V200R001C00

CE6810EI

V100R003C00

CE6810-48S4Q-LI/CE6810-48S-LI

V100R003C10

CE6810-32T16S4Q-LI/CE6810-24S2Q-LI

V100R005C10

CE6850EI

V100R001C00

CE6850-48S6Q-HI

V100R005C00

CE6850-48T6Q-HI/CE6850U-HI/CE6851HI

V100R005C10

CE6855HI

V200R001C00

CE6856HI

V200R002C50

CE6857EI

V200R005C10

CE6860EI

V200R002C50

CE6865EI

V200R005C00

CE6870-24S6CQ-EI/CE6870-48S6CQ-EI

V200R001C00

CE6870-48T6CQ-EI

V200R002C50

CE6875-48S4CQ-EI

V200R003C00

CE6880EI

V200R002C50

CE5810EI

V100R002C00

CE5850EI

V100R001C00

CE5850HI

V100R003C00

CE5855EI

V100R005C10

CE5880EI

V200R005C10

Feature Limitations

  • Plan service and management VLANs separately so that any broadcast storms in service VLANs do not affect switch management.
  • In practice, specify VLANs from which packets need to be transparently transmitted by a trunk interface. Avoid using the port trunk allow-pass vlan all command to configure the trunk interface to allow all VLANs.
  • The CE6810LI does not support IPv4 or IPv6 Layer 3 forwarding. After the IPv4 or IPv6 function is enabled on an interface of the CE6810LI, the configured IPv4 or IPv6 address can only be used to manage the switch.

  • VLAN 1 is the default VLAN, which cannot be deleted and does not need to be created. VLAN 1 cannot be configured as an mVLAN or a super-VLAN. On the backbone network device, to prevent broadcast storms, do not add interfaces to VLAN 1.
  • For the CE6870EI and CE6875EI, MAC address-based VLAN assignment cannot be used with port security or MAC address limiting.
  • The models excluding the CE5880EI, CE6870EI, CE6875EI, and CE6880EI do not support VLAN-based mirroring when being configured with MAC address-based VLAN assignment.
  • When MAC address-based assignment is configured on the CE6870EI and CE6875EI, running the mac-vlan enable or undo mac-vlan enable command may cause few packets to be discarded. Exercise caution when you run this command.
  • When the IP subnet-based VLAN is used for Layer 3 forwarding on the CE6870EI and CE6875EI, the PVID of the interface must be the same as the IP subnet-based VLAN ID.

  • When the PVID is configured on an interface and the encapsulation untag command is used to configure the Layer 2 sub-interface to receive untagged packets, if the Layer 2 sub-interface is Up, untagged packets are forwarded to the VXLAN network through the Layer 2 sub-interface. If the Layer 2 sub-interface is Down, untagged packets are forwarded based on the PVID.

  • If a hybrid interface is configured with a PVID and port hybrid tagged vlan and runs protocols such as STP, LACP, LLDP, GVRP, HGMP, and 802.3AH, BPDU packets forwarded by this interface contain the specified PVID. Consequently, interconnection with the remote end will fail. To prevent this, configure hybrid interfaces running these protocols to work in untagged mode.

  • The outer VLAN encapsulated for a Layer 2 QinQ sub-interface cannot be the same as the default VLAN and allowed VLAN of the corresponding Layer 2 main interface.

  • The VLAN used in OpenFlow in the development system cannot be the same as the VLAN created on the switch. Plan VLANs in advance.
  • The VLAN, VXLAN, carrier VLAN, main interface, and Eth-Trunk where card interoperability mode is set to enhanced share system resources. If system resources are insufficient, the configuration may fail.

  • Reserved VLAN
    • The configured reserved VLAN cannot be used as the common VLAN.
    • The VLAN in use cannot be configured as a reserved VLAN. The created reserved VLAN takes effect only after the switch restarts.
    • Configure reserved VLAN for a Layer 3 main interface on the CE6855HI, CE6856HI, CE6865EI, CE6857EI, CE8861EI, CE8868EI, and CE7855EI:
      • The vlan reserved for main-interface startvlanid to endvlanid command will take effect after the configuration is submitted. You do not need to restart the switch.

      • You can configure a maximum of eight reserved VLAN ranges for a Layer 3 main interface, and reserved VLAN ranges of different main interfaces cannot overlap.

      • The undo vlan reserved for main-interface startvlanid to endvlanid command cancels the reserved VLAN range but not some reserved VLANs in the reserved VLAN range. If a main interface joins a reserved VLAN in the specified reserved VLAN range, the undo vlan reserved for main-interface command cannot be executed.

      • The reserved VLANs of a main interface and the Layer 2 reserved VLAN configured by the vlan reserved command cannot overlap.

      • If a dynamic VLAN learned by GVRP is in the reserved VLAN range of a main interface, the dynamic VLAN cannot be learned.

      • In the SVF system, the VLAN ID of a Layer 2 sub-interface configured by the encapsulation dot1q vid vid command cannot be the ID of a reserved VLAN in the reserved VLAN range of a main interface.

  • VLAN aggregation
    • After a VLAN is configured as a super-VLAN, no physical interface can be added to the VLAN.
    • A VLAN can be added to only one super-VLAN.
    • The super-VLAN must be different from all its sub-VLANs.
    • An IP address must have been assigned to the VLANIF interface corresponding to the super-VLAN. Otherwise, proxy ARP cannot take effect.
  • MUX VLAN
    • The interface enabled with the MUX VLAN function cannot be added to other VLANs of the MUX VLAN.
    • Access interfaces can be added to only one MUX VLAN. Trunk and hybrid interfaces can be added to multiple MUX VLANs. An interface can be added to a maximum of 32 MUX VLANs.
    • Disabling MAC address learning or limiting the number of learned MAC addresses on an interface affects the MUX VLAN function on the interface.
    • All member VLANs in a MUX VLAN must belong to the same STP instance; otherwise, traffic forwarding may fail or loops may occur. The VLANs in QinQ and VLAN mapping must belong to the same STP instance.
    • The VLAN ID assigned to a principal VLAN cannot be used to configure VLAN mapping, VLAN stacking, a super-VLAN, or a sub-VLAN.
    • The VLAN ID assigned to a group or separate VLAN cannot be used to configure any VLANIF interface, VLAN mapping, VLAN stacking, super-VLAN, or sub-VLAN.
    • MUX VLAN cannot be used with port security, VLAN ID-based selective QinQ simultaneously.
    • MUX VLAN cannot be used together with TRILL, MPLS, EVN, or VBST.
    • In MUX VLAN cascading scenario, for other models excluding the CE6810LI, the VLANIF interface corresponding to the principal VLAN can be created, but the VLANIF interface cannot forward traffic from sub-VLANs.
    • The CE6810LI does not support VLANIF interfaces corresponding to the principal VLAN and sub-VLAN.
  • Traffic statistics collection in a VLAN

    • Traffic statistics collection in a VLAN and traffic statistics collection on a Layer 2 sub-interface are mutually exclusive on the CE6870EI and CE6875EI.

    • For the CE6870EI and CE6875EI, traffic statistics collection does not take effect for the MUX VLAN.

    • Traffic statistics are accumulative and cannot be cleared by the system. To clear traffic statistics in a VLAN, run the reset vlan statistics command in the VLAN.

    • The traffic statistics function occupies system resources. If system resources are insufficient, the configuration may fail. Disable this function when traffic statistics do not need to be collected.

    • For all models running earlier versions of V100R006C00, the following traffic statistics collection functions are in descending order of priority: traffic statistics collection in a VLAN, MQC-based traffic statistics collection, and traffic statistics collection on a VLANIF interface. When all of the three traffic statistics collection functions are configured, only the traffic statistics collection function with the highest priority takes effect. The following table lists the priorities of the traffic statistics collection functions in V100R006C00 and later versions.
      Table 5-9 Priorities of the traffic statistics collection functions

      Model

      Priority

      CE5880EI, CE6880EI

      Traffic statistics collection in a VLAN > Traffic statistics collection on a VLANIF interface

      Traffic statistics collection on 5-tuple information of IP packets and MQC-based traffic statistics collection are compatible with the statistics collection functions.

      CE6850EI, CE6810EI, CE6810LI, CE5855EI, and CE5810EI

      CE12800E equipped with FD-X series cards

      Traffic statistics collection on 5-tuple information of IP packets > Traffic statistics collection in a VLAN > Traffic statistics collection on a VLANIF interface

      MQC-based traffic statistics collection is compatible with the statistics collection functions.

      CE6870EI, CE6875EI

      Traffic statistics collection on 5-tuple information of IP packets > MQC-based traffic statistics collection > Traffic statistics collection on a VLANIF interface

      Traffic statistics collection in a VLAN is compatible with the statistics collection functions.

      Other models

      Traffic statistics collection on 5-tuple information of IP packets > Traffic statistics collection in a VLANIF interface

      Traffic statistics collection in a VLAN and MQC-based traffic statistics collection are compatible with the statistics collection functions.

    • For the CE6870EI and CE6875EI, the outbound traffic statistics do not contain packets forwarded at Layer 3.

    • For the CE6870EI and CE6875EI, the outbound traffic statistics in a VLAN bound to an EVN instance are inaccurate.
    • When the forwarding mode is set to cut-through on the CE5880EI and CE6880EI, the switch does not support VLAN traffic statistics collection.
    • If an interface is configured with port mirroring and is added to a VLAN on the CE6870EI and CE6875EI, doubled traffic is counted for inbound traffic statistics in a VLAN.

  • Traffic statistics on a VLANIF interface

    After you run the undo statistics enable command on a VLANIF interface, the switch stops collecting traffic statistics on the VLANIF interface, and the collected traffic statistics will be deleted. In V200R003C00 and later versions, the switch can collect statistics on IPv4 and IPv6 packets, respectively. The undo statistics enable command clears statistics on the corresponding type of packets. For details, see statistics enable (VLANIF interface view).

    Enabling traffic statistics collection on a VLANIF interface may affect the forwarding performance, for example, some interfaces may fail to forward packets at line rate when all interfaces are configured to forward packets at line rate.

    For the CE5880EI and CE6880EI:
    • If traffic statistics collection is enabled in a VLAN corresponding to the VLANIF interface, Layer 2 and Layer 3 traffic statistics are collected as traffic statistics in the VLAN.

    • The switch cannot collect statistics on unicast and multicast packets respectively, or collect statistics on IPv4 and IPv6 packets respectively.

    • The switch cannot collect statistics on error packets or packets generated and sent by the switch itself (for example, ping packets).

    For the CE6870EI and CE6875EI:

    • The switch uses ACL resources when collecting traffic statistics. If traffic statistics collection is enabled on too many VLANIF interfaces, other services may fail to obtain ACL resources. The switch can collect traffic statistics on a maximum of 100 VLANIF interfaces.

    • The switch cannot collect statistics on error packets, MPLS packets, or packets encapsulated with the VXLAN header, and cannot collect statistics on unicast and multicast packets, respectively.

    • In versions earlier than V200R003C00, the switch can only collect statistics on IPv4 unicast packets. In V200R003C00 and later versions, the switch can collect statistics on IPv4 and IPv6 unicast packets, and the IPv4 unicast packets do not include GRE packets encapsulated with the IPv4 header, IPv6 over IPv4 packets, and EVN packets encapsulated with the VXLAN header.

    • The switch cannot collect statistics on packets generated and sent by the switch itself (for example, ping packets).

    • The following services are in descending order of priority: M-LAG unidirectional isolation, MQC (traffic policing, traffic statistics collection, and packet filtering), querying the outbound interface of packets with specified 5-tuple information, source MAC address, and destination MAC address, local VLAN mirroring, sFlow, NetStream, and VLANIF interface statistics collection. When the services are configured on an interface in the outbound direction, only the service with the highest priority takes effect. For example, when both packet filtering and VLANIF interface statistics collection are configured on a VLANIF interface, packet filtering takes effect.

      For sFlow and NetStream, the preceding limitations apply only to Layer 2 sub-interfaces and Layer 3 sub-interfaces.

    • On the switch that decapsulates VXLAN packets, the switch cannot collect statistics on incoming packets encapsulated with the VXLAN header on a VLANIF interface. On the switch that encapsulates VXLAN packets, when the switch is not configured with VXLAN traffic statistics collection and the VXLAN NVO3 gateway uses the non-loopback mode, the switch can collect statistics on packets encapsulated with the VXLAN header in the outbound direction of a VLANIF interface. Otherwise, statistics cannot be collected on packets in the outbound direction of a VLANIF interface.
    For switches excluding the CE5880EI, CE6870EI, CE6875EI, and CE6880EI:
    • The switch uses ACL resources when collecting traffic statistics. If traffic statistics collection is enabled on too many VLANIF interfaces, other services may fail to obtain ACL resources. The switch can collect traffic statistics on a maximum of 100 VLANIF interfaces.

    • The VLANIF interface corresponding to the super-VLAN or MUX VLAN does not support traffic statistics collection.

    • The switch cannot collect statistics on error packets, MPLS packets, or VXLAN packets.

    • The switch cannot collect statistics on unicast and multicast packets, respectively.

    • The switch cannot collect statistics on packets generated and sent by the switch itself (for example, ping packets).

Translation
Download
Updated: 2019-05-08

Document ID: EDOC1100004351

Views: 118066

Downloads: 292

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