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).
Configuring Selective QinQ

Configuring Selective QinQ

Selective QinQ adds different outer VLAN tags to packets with different inner VLAN tags on an interface, and is more flexible than QinQ.

Configuring VLAN ID-based Selective QinQ

Context

Selective QinQ based on the VLAN ID enables the device to add different outer VLAN tags to received data frames according to VLAN IDs in the frames.

NOTE:
  • Selective QinQ based on the VLAN ID can be only enabled on hybrid or trunk interfaces in the inbound direction.
  • The outer VLAN ID must exist and the interface must be added to the outer VLAN in untagged mode.
  • The interface learns the MAC address in the VLAN specified by the outer VLAN tag of packets.
  • The MUX VLAN and selective QinQ based on the VLAN ID cannot be configured on the same interface.
  • The original VLAN specified in the port vlan-stacking command cannot be the same as the outer VLAN configured on a QinQ Layer 2 sub-interface.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Run port link-type { hybrid | trunk }

    The link type of the interface is configured as hybrid or trunk.

    By default, the link type of an interface is access.

  4. Add the interface to a VLAN.

    Run the following command as required.

    • Trunk interface

      Run the port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] }&<1-40> | all } command to add the trunk interface to the stacked VLAN.

    • Hybrid interface

      Run the port hybrid untagged vlan vlan-id command to add the hybrid interface to the stacked VLAN in untagged mode.

    The VLAN ID specified by vlan-id must already exist on the device. The original VLAN can be not created.

  5. Run port vlan-stacking vlan vlan-id1 [ to vlan-id2 ] stack-vlan vlan-id3 [ remark-8021p 8021p-value ]

    Selective QinQ based on the VLAN ID is configured.

    NOTE:

    If the port vlan-stacking command has been executed at least three times with specified VLAN ranges and VLAN ranges are combined twice at least, the configuration of each command must be committed. Otherwise, packets may be lost. For example, when port vlan-stacking vlan 31 to 60 stack-vlan 100, port vlan-stacking vlan 20 to 30 stack-vlan 100, and port vlan-stacking vlan 61 to 70 stack-vlan 100 commands are used, VLAN ranges 20 to 60 and 20 to 70 are combined twice. Therefore, commit the configuration of each command.

  6. Run commit

    The configuration is committed.

Verifying the Configuration
  • Run the display current-configuration interface interface-type interface-number command to check the configuration of selective QinQ based on the VLAN ID on the interface.

Configuring MQC-based Selective QinQ

Context

MQC-based selective QinQ uses a traffic classifier to classify packets based on VLAN IDs and associates the traffic classifier with a traffic behavior that defines the action of adding outer VLAN tags, so that the device can add outer VLAN tags to packets matching the traffic classifier.

NOTE:

The CE6870EI and CE6875EI do not support this function.

Procedure
  1. Configure a traffic classifier.
    1. Run system-view

      The system view is displayed.

    2. Run traffic classifier classifier-name [ type { and | or } ]

      A traffic classifier is created and the traffic classifier view is displayed, or the view of an existing traffic classifier is displayed.

      and is the logical operator between the rules in a traffic classifier, which means that:
      • If a traffic classifier contains ACL rules, packets match the traffic classifier only if they match one ACL rule and all the non-ACL rules.

      • If a traffic classifier does not contain any ACL rules, packets match the traffic classifier only if they match all the rules in the classifier.

      The logical operator or means that packets match a traffic classifier if they match one or more rules in the classifier.

      By default, the relationship between rules in a traffic classifier is or.

    3. Run if-match

      Matching rules are defined for the traffic classifier.

      For details about matching rules in a traffic classifier, see "Configuring a Traffic Classifier" in "MQC Configuration" of the CloudEngine 8800, 7800, 6800, and 5800 Series Switches Configuration Guide - QoS Configuration Guide.

    4. Run commit

      The configuration is committed.

    5. Run quit

      Exit from the traffic behavior view.

  2. Configure a traffic behavior.
    1. Run traffic behavior behavior-name

      A traffic behavior is created and the traffic behavior view is displayed, or the view of an existing traffic behavior is displayed.

    2. Run vlan-stacking vlan vlan-id

      An action of adding an outer VLAN tag is configured in the traffic behavior.

    3. Run commit

      The configuration is committed.

    4. Run quit

      Exit from the traffic behavior view.

    5. Run quit

      Exit from the system view.

  3. Configure a traffic policy.
    1. Run system-view

      The system view is displayed.

    2. Run traffic policy policy-name

      A traffic policy is created and the traffic policy view is displayed, or the view of an existing traffic policy is displayed.

    3. Run classifier classifier-name behavior behavior-name [ precedence precedence-value ]

      A traffic behavior is bound to a traffic classifier in the traffic policy.

    4. Run commit

      The configuration is committed.

    5. Run quit

      Exit from the traffic policy view.

    6. Run quit

      Exit from the system view.

  4. Apply the traffic policy.
    NOTE:
    • A traffic policy containing vlan-stacking cannot be applied to the outbound direction.

    • For details about the configuration guidelines of applying traffic policies in different views on the CE switches excluding CE6870EI and CE6875EI, see Licensing Requirements and Limitations for MQC (CE Switches Excluding CE6870EI and CE6875EI).

    • If a traffic policy needs to be applied to multiple VLANs and interfaces or multiple traffic classifiers for matching packets from different source IP addresses need to be bound to the same traffic policy, you are advised to add these VLANs, source IP addresses, and interfaces to the same QoS group and apply the traffic policy to the QoS group.

    • Applying a traffic policy to an interface
      1. Run system-view

        The system view is displayed.

      2. Run interface interface-type interface-number

        The interface view is displayed.

      3. Run traffic-policy policy-name inbound

        A traffic policy is applied to the interface in the inbound direction.

      4. Run commit

        The configuration is committed.

    • Applying a traffic policy to a VLAN
      1. Run system-view

        The system view is displayed.

      2. Run vlan vlan-id

        The VLAN view is displayed.

      3. Run traffic-policy policy-name inbound

        A traffic policy is applied to the VLAN in the inbound direction.

        After a traffic policy is applied to a VLAN, the system performs traffic policing for the packets that come from the VLAN and match traffic classification rules in the inbound direction.

      4. Run commit

        The configuration is committed.

    • Applying a traffic policy to the system
      1. Run system-view

        The system view is displayed.

      2. Run traffic-policy policy-name global [ slot slot-id ] inbound

        A traffic policy is applied to the system in the inbound direction.

      3. Run commit

        The configuration is committed.

    • Applying a traffic policy to a QoS group
      1. Run system-view

        The system view is displayed.

      2. Run qos group group-name

        The QoS group view is displayed.

      3. Run the following commands as required.
        • Run the group-member interface { interface-type interface-number1 [ to interface-type interface-number2 ] } &<1-8> command to add interfaces to the QoS group.

        • (For CE6870EI, CE6875EI and CE6880EI) Run the group-member vlan { vlan-id1 [ to vlan-id2 ] } &<1-8> command to add VLANs to the QoS group.

        • ( For CE Switches Excluding CE6870EI and CE6875EI) Run the group-member ip source ip-address { mask | mask-length } command to add source IP addresses to the QoS group.

      4. Run traffic-policy policy-name inbound

        A traffic policy is applied to a QoS group.

      5. Run commit

        The configuration is committed.

Verifying the Configuration
  • Run the display traffic classifier [ classifier-name ] command to check the traffic classifier configuration.
  • Run the display traffic behavior [ behavior-name ] command to check the traffic behavior configuration on the device.
  • Run the display traffic policy [ policy-name [ classifier classifier-name ] ] command to check the traffic policy configuration.

  • Run the display traffic-policy applied-record [ policy-name ] [ global [ slot slot-id ] | interface interface-type interface-number | vlan vlan-id | vpn-instance vpn-instance-name | qos group group-id | bridge-domain bd-id ] [ inbound | outbound ] command to check the application record of a specified traffic policy.

  • Run the display system tcam fail-record [ slot slot-id ] command to display TCAM delivery failures.
  • Run the display system tcam service brief [ slot slot-id ] command to display the group index and rule count occupied by different services.
  • Run the display system tcam service { cpcar slot slot-id | service-name slot slot-id [ chip chip-id ] } command to display IDs of entries that deliver services on the specified chip or in the specified slot.
  • Run one of the following commands to display data of a traffic policy that has been applied:
    • display system tcam service traffic-policy { global | vlan vlan-id | interface interface-type interface-number | vpn-instance vpn-instance-name | qos group group-id | bridge-domain bd-id } policy-name { inbound | outbound } [ slot slot-id [ chip chip-id ] ]
      NOTE:
      • The CE6810LI does not support the vpn-instance vpn-instance-name parameter.
      • The CE5810EI, CE5850EI, CE5850HI, CE5855EI, CE6810LI, CE6810EI, and CE6850EI do not support the bridge-domain bd-id parameter.
    • display system tcam service traffic-policy slot slot-id policy-name { inbound | outbound } [ chip chip-id ]
  • (For CE6870EI and CE6875EI) Run the display system tcam match-rules slot slot-id [ [ ingress | egress | group group-id ] | [ chip chip-id ] ] * command to display matched entries.
  • (For CE6880EI switches) Run the display system tcam match-rules slot slot-id chip chip-id index index-id command to display matched entries.
  • (Models excluding the CE6870EI, CE6875EI, and CE6880EI) Run the display system tcam match-rules slot slot-id [ [ ingress | egress | group group-id ] | [ delay-time time-value ] ] * command to display matched entries.
Translation
Download
Updated: 2019-05-08

Document ID: EDOC1100004351

Views: 128952

Downloads: 297

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