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

NE20E-S2 V800R010C10SPC500 Configuration Guide - LAN Access and MAN Access 01

This is NE20E-S2 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 Interface-based BPDU Tunneling Function

Configuring Interface-based BPDU Tunneling Function

When each interface of devices on a carrier network is connected to only one user network, you can configure interface-based bridge protocol data unit (BPDU) tunneling to transparently transmit BPDUs from different user networks over the carrier network.

Usage Scenario

If each interface of a provider edge (PE) is connected to one customer edge (CE) and BPDUs sent from user networks are untagged, you can configure interface-based BPDU tunneling to transparently transmit these BPDUs over the carrier network. With interface-based BPDU tunneling configured, BPDUs from user networks are transparently transmitted through different BPDU tunnels over the Layer 2 network of the carrier network to perform the spanning tree calculation.

Pre-configuration Tasks

Before configuring interface-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-3 Flowchart for configuring interface-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

    The spanning tree calculation is enabled.

  3. Run commit

    The configuration is committed.

Adding an Interface to a Specified VLAN

Each interface on a provider edge (PE) is connected to one user network, and user networks belong to different local area networks (LANs). BPDUs sent from user networks to PEs are untagged. The PEs, however, need to identify the LANs to which the BPDUs belong. In this situation, you need to add the PE interfaces to specified virtual local area networks (VLANs).

Context

Perform the following steps on PEs.

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. If the VLAN to be created exists, the command displays the VLAN view.

  3. Run port interface-type { interface-number1 [ to interface-number2 ] } &<1-10>

    The interface on the PE that is connected to a customer edge (CE) is added to the created VLAN.

    NOTE:

    To add an interface on the PE that is connected to a CE to a specified VLAN, you can also run the port default vlan vlan-id1 command on the interface.

  4. Run commit

    The configuration is committed.

Configuring Interface-based BPDU Tunneling

You can configure interface-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. After the configuration is complete, when an interface of a PE receives a BPDU from a user network, the PE adds a VLAN tag to the BPDU based on the PVID of the interface, selects a BPDU tunnel based on the VLAN ID in the tag, and transmits the BPDU through the BPDU tunnel. In this manner, BPDUs from different user networks are isolated.

Context

You can configure interface-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
    1. On a PE, 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 stp disable

      The spanning tree calculation is disabled on the interface.

    5. Run commit

      The configuration is committed.

    NOTE:

    If PEs and CEs are configured with different roles, the PEs can transparently transmit BPDUs sent by the CEs. In this case, you do not need to enable BPDU tunneling on the interfaces of the PEs.

  • Same role of PEs and CEs
    1. On a PE, 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 bpdu-tunnel enable

      BPDU tunneling is enabled on the interface to transparently transmit BPDUs from a user network.

    5. Run stp disable

      The spanning tree calculation is disabled on the interface.

    6. Run commit

      The configuration is committed.

    NOTE:

    If PEs and CEs have the same role, the PEs cannot transparently transmit BPDUs sent by the CEs. In this case, you need to enable BPDU tunneling on the PE interfaces.

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.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of the Interface-based BPDU Tunneling Function

After configuring interface-based bridge protocol data unit (BPDU) tunneling, verify the configuration.

Prerequisites

Interface-based BPDU tunneling has been configured.

Procedure

  1. Run the display stp [ brief ] command to check spanning tree information.

Example

Run the display stp [ brief ] command on each customer edge (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(GigabitEthernet0/1/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(GigabitEthernet0/1/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
Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055378

Views: 16955

Downloads: 35

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