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

ME60 V800R010C10SPC500 Configuration Guide - LAN Access and MAN Access 01

This is ME60 V800R010C10SPC500 Configuration Guide - LAN Access and MAN Access
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 QinQ-based BPDU Tunneling Function

Configuring QinQ-based BPDU Tunneling Function

If each user-side interface on a provider edge (PE) is connected to multiple customer edges (CEs), bridge protocol data units (BPDUs) sent from user networks must carry virtual local area network (VLAN) tags to identify these user networks. To transparently transmit BPDUs from user networks over the carrier network and save VLAN ID resources for the carrier network, deploy QinQ-based BPDU tunneling (QinQ is short for 802.1Q in 802.1Q).

Usage Scenario

If each user-side interface on a PE is connected to multiple CEs, BPDUs sent from user networks must carry VLAN tags to identify these user networks. To transparently transmit BPDUs from user networks over the carrier network and save VLAN ID resources for the carrier network, you can configure QinQ-based BPDU tunneling. With QinQ-based BPDU tunneling configured, the PEs choose different BPDU tunnels to transmit BPDUs based on their outer VLAN IDs over the carrier network.

Pre-configuration Tasks

Before configuring QinQ-based BPDU tunneling, complete the following tasks:

  • Check that the interfaces through which BPDUs are transmitted are connected correctly.

  • Check that the interfaces through which BPDUs are transmitted are Layer 2 interfaces.

Configuration Procedures

Figure 16-5 Flowchart for configuring QinQ-based BPDU tunneling

Enabling the Spanning Tree Calculation

Bridge protocol data units (BPDUs) from user networks are transparently transmitted through different BPDU tunnels over the Layer 2 network of a carrier network to perform the spanning tree calculation.

Context

Perform the following steps on provider edges (PEs) and customer edges (CEs).

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run stp enable

    Spanning tree calculation is enabled.

  3. Run commit

    The configuration is committed.

Configuring an Interface to Add a Specified VLAN ID to BPDUs

If multiple user networks are connected to the same interface of a provider edge (PE), configure the interfaces of customer edges (CEs) to add specified virtual local area network (VLAN) IDs to bridge protocol data units (BPDUs) before sending them to the PE. The VLAN IDs identify the user networks to which the BPDUs belong.

Context

Perform the following steps on CEs.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run vlan vlan-id

    A VLAN is created, and the VLAN view is displayed.

    The VLAN ID ranges from 1 to 4094. To create multiple VLANs, repeat this step.

  3. Run quit

    The system view is displayed.

  4. Run interface interface-type interface-number

    The view of the interface connected to a PE is displayed.

  5. Run port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] } &<1-10> | all }

    The VLAN ID that the CE allows to pass is configured.

  6. Run stp bpdu vlan vlan-id

    The interface is configured to add the specified VLAN ID to BPDUs that will be sent to the PE.

    NOTE:

    Ensure that the specified VLAN ID is the same as that carried in BPDUs received by the interface.

  7. Run commit

    The configuration is committed.

Configuring QinQ-based BPDU Tunneling

You can configure QinQ-based bridge protocol data unit (BPDU) tunneling based on the different roles of provider edges (PEs) and customer edges (CEs) or on the same role of PEs and CEs (QinQ is short for 802.1Q in 802.1Q). After QinQ-based BPDU tunneling is configured, the PEs do not send BPDUs to their CPUs for processing. Instead, they transparently transmit the BPDUs through BPDU tunnels over the Layer 2 network of the carrier network to user networks. This configuration also saves virtual local area network (VLAN) ID resources for the carrier network.

Context

You can configure QinQ-based BPDU tunneling based on the different roles of PEs and CEs or on the same role of PEs and CEs.

Different roles of PEs and CEs: CEs are customers, and PEs are providers.

Same role of PEs and CEs: CEs and PEs are both customers.

Procedure

  • Different roles of PEs and CEs

    Perform the following steps on each PE:

    1. Run system-view

      The system view is displayed.

    2. Run bpdu-tunnel stp bridge role provider

      The PE is configured as a provider.

      This command is supported only on the Admin-VS but takes effect on all VSs.

    3. Run interface interface-type interface-number

      The view of the interface connected to a CE is displayed.

    4. (Optional) Run port link-type { hybrid | trunk }

      The interface type is configured.

    5. Run port vlan-stacking vlan vlan-id1 [ to vlan-id2 ] stack-vlan vlan-id3

      The interface is configured to add an outer VLAN tag to BPDUs that the interface receives.

    6. (Optional) Run stp disable

      The spanning tree calculation is disabled on the interface.

    7. Run commit

      The configuration is committed.

  • Same role of PEs and CEs

    Perform the following steps on each PE:

    1. Run system-view

      The system view is displayed.

    2. Run bpdu-tunnel stp group-mac group-mac

      The well-known destination Media Access Control (MAC) address of BPDUs is changed to a specified MAC address.

      This command is supported only on the Admin-VS but takes effect on all VSs.

      The well-known MAC address of BPDUs can be changed only to a multicast MAC address, which cannot be a reserved multicast MAC address in the range of 0180-C200-0000 to 0180-C200-002F.

    3. Run interface interface-type interface-number

      The view of the interface connected to a CE is displayed.

    4. Run port vlan-stacking vlan vlan-id1 [ to vlan-id2 ] stack-vlan vlan-id3

      The interface is configured to add an outer VLAN tag to BPDUs that the interface receives.

    5. Run bpdu-tunnel stp vlan vlan-id1 [ to vlan-id2 ]

      BPDU tunneling is enabled on the interface to transparently transmit BPDUs with specified VLAN IDs.

      The VLAN ID range specified in this step must include the inner VLAN IDs specified in Step 4.

    6. Run stp disable

      The spanning tree calculation is disabled on the interface.

    7. Run commit

      The configuration is committed.

    NOTE:

    In this scenario, no special configuration is required on Ps.

Configuring an Interface to Allow Packets with Specified VLAN IDs to Pass

To enable users to communicate through a carrier network, configure interfaces on provider edges (PEs) that are connected to the carrier network to allow the passing of packets with specified virtual local area network (VLAN) IDs.

Context

Perform the following steps on PEs.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The view of the interface connected to the carrier network is displayed.

  3. Run port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] } &<1-10> | all }

    The interface connected to the carrier network is configured to allow the passing of packets with specified VLAN IDs.

    The specified VLAN IDs must be the same as the outer VLAN IDs carried in BPDUs that the PE receives.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of the QinQ-based BPDU Tunneling Function

After configuring QinQ-based bridge protocol data unit (BPDU) tunneling, verify the configuration (QinQ is short for 802.1Q in 802.1Q).

Prerequisites

QinQ-based BPDU tunneling has been configured.

Procedure

  • Run the display bpdu-tunnel interface config command to check BPDU tunneling configuration on an interface.
  • Run the display bpdu-tunnel global config command to check BPDU tunneling configuration globally.
  • Run the display stp [ brief ] command to check spanning tree information.
  • Run the display vlan [ vlan-id [ verbose ] ] command to check VLAN information.

    NOTE:
    • The display bpdu-tunnel global config command can be run only in the system view.

    • The display bpdu-tunnel interface config command can be run only in the interface view.

Example

Run the display bpdu-tunnel global config command on a provider edge (PE). The command output shows the role of the PE on the network and the multicast destination Media Access Control (MAC) address of BPDUs generated by the spanning tree protocol on the PE.

<PE> system-view
[*PE] display bpdu-tunnel global config
BridgeRole       customer
GroupMac         0100-0ccd-cdd0
Run the display bpdu-tunnel interface config command on the PE. The command output shows that the interface of the PE allows the passing of BPDUs with a specified VLAN ID.
<PE> system-view
[*PE] interface gigabitethernet 1/0/1
[*PE-GigabitEthernet1/0/1] display bpdu-tunnel interface config
BpduDot1qStatus  disable
BpduOneQStatus   disable
BpduTwoQStatus   enable
EtherType        8100
Dot1qVlan        
TwoQList         10

Run the display stp [ brief ] command on each CE. The command output shows that the spanning tree protocol is enabled on the CE interfaces and that there is a Designated interface and a Root interface.

<CE1> display stp
-------[CIST Global Info][Mode MSTP]-------
CIST Bridge         :32768.0a02-4ccc-4400
Config Times        :Hello 2s MaxAge 20s FwDly 15s MaxHop 20
Active Times        :Hello 2s MaxAge 20s FwDly 15s MaxHop 19
CIST Root/ERPC      :4096.0a70-d038-ce00 / 0
CIST RegRoot/IRPC   :4096.0a70-d038-ce00 / 20000
CIST RootPortId     :128.10 (Eth-Trunk60)
BPDU-Protection     :Disabled
TC or TCN received  :0
TC count per hello  :0
STP Converge Mode   :Normal
Time since last TC  :0 days 0h:3m:23s
Number of TC        :1
Last TC occurred    :Eth-Trunk60
----[Port10(GigabitEthernet1/0/2)][FORWARDING]----
 Port Protocol       :Enabled
 Port Role           :Designated Port
 Port Priority       :128
 Port Cost(Dot1T)    :Config=auto / Active=20000
 Designated Bridge/Port   :32768.0a02-4ccc-4400 / 128.21
 Port Edged          :Config=enabled / Active=enabled
 Point-to-point      :Config=auto / Active=true
 Transit Limit       :147 packets/hello-time
 Protection Type     :None
 Port STP Mode       :MSTP
 Port Protocol Type  :Config=auto / Active=dot1s
 BPDU Encapsulation  :Config=stp / Active=stp
 PortTimes           :Hello 2s MaxAge 20s FwDly 15s RemHop 19
 TC or TCN send      :0
 TC or TCN received  :0
 BPDU Sent           :82
          TCN: 0, Config: 0, RST: 0, MST: 82
 BPDU Received       :0
          TCN: 0, Config: 0, RST: 0, MST: 0
<CE2> display stp
-------[CIST Global Info][Mode MSTP]-------
CIST Bridge         :32768.0a02-4ccc-4400
Config Times        :Hello 2s MaxAge 20s FwDly 15s MaxHop 20
Active Times        :Hello 2s MaxAge 20s FwDly 15s MaxHop 19
CIST Root/ERPC      :4096.0a70-d038-ce00 / 0
CIST RegRoot/IRPC   :4096.0a70-d038-ce00 / 20000
CIST RootPortId     :128.10 (Eth-Trunk60)
BPDU-Protection     :Disabled
TC or TCN received  :0
TC count per hello  :0
STP Converge Mode   :Normal
Time since last TC  :0 days 0h:3m:23s
Number of TC        :1
Last TC occurred    :Eth-Trunk60
----[Port10(GigabitEthernet1/0/1)][FORWARDING]----
 Port Protocol       :Enabled
 Port Role           :Root Port
 Port Priority       :128
 Port Cost(Dot1T)    :Config=auto / Active=20000
 Designated Bridge/Port   :4096.0a70-d038-ce00 / 128.4
 Port Edged          :Config=default / Active=disabled
 Point-to-point      :Config=auto / Active=true
 Transit Limit       :147 packets/hello-time
 Protection Type     :None
 Port STP Mode       :MSTP
 Port Protocol Type  :Config=auto / Active=dot1s
 BPDU Encapsulation  :Config=stp / Active=stp
 PortTimes           :Hello 2s MaxAge 20s FwDly 15s RemHop 20
 TC or TCN send      :2
 TC or TCN received  :0
 BPDU Sent           :7
          TCN: 0, Config: 0, RST: 0, MST: 7
 BPDU Received       :105
          TCN: 0, Config: 0, RST: 0, MST: 105

Run the display vlan command. The command output shows whether the VLAN is enabled and whether broadcast and MAC address learning are enabled in the VLAN.

<HUAWEI> display vlan 2 verbose
  VLAN ID          : 2
  VLAN Type        : Common
  Description     : VLAN 0002
  Status           : Enable
  Broadcast        : Enable
  MAC learning     : Enable
  Statistics       : Disable
  ----------------
  Untagged   Port: Eth-Trunk1                  Eth-Trunk2 
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059440

Views: 26310

Downloads: 18

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