Configuration Guide - LAN Access and MAN Access (V600R003C00 - 02)

HUAWEI NetEngine80E/40E Router
V600R003C00
Configuration Guide - LAN Access

and MAN Access
Issue 02
Date 2011-09-10
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 02 (2011-09-10) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Configuration Guide - LAN Access and MAN Access About This Document
About This Document
Purpose
This manual describes LAN access and MAN access technologies, including principles,
configuration steps, and configuration examples of MAC address, Ethernet, LACP, VLAN,
QinQ, MSTP, BPDU tunnel, and RRPP.
NOTE
l This document takes interface numbers and link types of the NE40E-X8 as an example. In working
situations, the actual interface numbers and link types may be different from those used in this
document.
l In NE80E/40E series (except for the NE40E-X1/X2), line processing boards are called Line Processing
Units (LPUs) and switching fabric boards are called Switching Fabric Units (SFUs). The NE40E- X1/
X2 has no LPU and SFU, and packet switching and forwarding are centrally performed by the Network
Processing Unit (NPU).
Related Versions
The following table lists the product versions related to this document.
Product Name Version
HUAWEI NetEngine80E/40E V600R003C00

Router
Intended Audience
This document is intended for:
l Commissioning engineer
l Data configuration engineer
l Network monitoring engineer
l System maintenance engineer
Issue 02 (2011-09-10) Huawei Proprietary and Confidential ii

Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Alerts you to a high risk hazard that could, if not avoided,

result in serious injury or death.
DANGER
Alerts you to a medium or low risk hazard that could, if

not avoided, result in moderate or minor injury.
WARNING
Alerts you to a potentially hazardous situation that could,

if not avoided, result in equipment damage, data loss,
CAUTION
performance deterioration, or unanticipated results.
TIP Provides a tip that may help you solve a problem or save
time.
NOTE Provides additional information to emphasize or

supplement important points in the main text.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
&<1-n> The parameter before the & sign can be repeated 1 to n times.
# A line starting with the # sign is comments.
Issue 02 (2011-09-10) Huawei Proprietary and Confidential iii

Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Changes in Issue 02 (2011-09-10)

This is the second release.
Changes in Issue 01 (2011-06-30)

This is the first release.
Issue 02 (2011-09-10) Huawei Proprietary and Confidential iv

Configuration Guide - LAN Access and MAN Access Contents
Contents
About This Document.....................................................................................................................ii

1 MAC Address Table Configuration...........................................................................................1
1.1 MAC Address Table Introduction......................................................................................................................2
1.1.1 MAC Address Table Overview.................................................................................................................2
1.1.2 MAC Addresses Learning Limit Supported by the NE80E/40E...............................................................2
1.2 Configuring the MAC Address Table Based on the VLAN and Layer 2 Interface...........................................2
1.2.1 Establishing the Configuration Task.........................................................................................................3
1.2.2 Configuring MAC Address Entries...........................................................................................................3
1.2.3 Configuring MAC Address Entries Based on the Layer 2 VE Interface...................................................4
1.2.4 Checking the Configuration.......................................................................................................................5
1.3 Configuring the MAC Address Table Based on the VSI and Layer 3 Interface................................................6
1.3.1 Establishing the Configuration Task.........................................................................................................6
1.3.2 Configuring MAC Address Entries...........................................................................................................7
1.3.3 Configuring MAC Address Entries Based on the VLANIF Interface.......................................................8
1.3.4 Checking the Configuration.......................................................................................................................9
1.4 Configuring the Aging Time of a MAC Address Table...................................................................................10
1.4.1 Establishing the Configuration Task.......................................................................................................11
1.4.2 Setting the Aging Time of a MAC Address Table..................................................................................11
1.4.3 Checking the Configuration.....................................................................................................................12
1.5 Maintaining MAC Address Table....................................................................................................................12
1.5.1 Clearing the Dynamic MAC Address......................................................................................................12
1.6 Configuration Examples...................................................................................................................................13
1.6.1 Example for Configuring the MAC Address Table Based on the Interface and VLAN.........................13
1.6.2 Example for Configuring the MAC Address Table Based on the dot1q Termination Sub-interface and
VSI....................................................................................................................................................................17
1.6.3 Example for Configuring the MAC Address Table Based on the QinQ Termination Sub-interface and
VSI....................................................................................................................................................................24
1.6.4 Example for Configuring the MAC Address Table Based on the VLANIF Interface and VSI..............33
1.6.5 Example for Configuring the MAC Address Table Based on the VLAN and Layer 2 VE Interface
..........................................................................................................................................................................41
1.6.6 Example for Configuring the MAC Address Table Based on the Interface and VSI..............................44
2 Ethernet Interface Configuration.............................................................................................46

2.1 Ethernet Interface Introduction.........................................................................................................................47
Issue 02 (2011-09-10) Huawei Proprietary and Confidential v

2.1.1 Introduction to Ethernet Interfaces..........................................................................................................47

2.1.2 Features of Ethernet Interfaces Supported by the NE80E/40E...............................................................47
2.2 Configuring Ethernet Interfaces of the Interface Board...................................................................................51
2.2.2 Configuring the MTU of an Ethernet Interface.......................................................................................51
2.2.3 Configuring the Working Mode of an Ethernet Interface.......................................................................53
2.2.4 Configuring the Speed of an Ethernet Electrical Interface......................................................................53
2.2.5 Configuring the GE/FE Optical/Electrical Interface...............................................................................54
2.2.6 Configuring LAN/WAN Transmission Mode for a 10 GE Interface......................................................55
2.2.7 Configuring Overhead Bytes of the 10GE WAN Interface.....................................................................56
2.2.8 Configuring Flow Control on the GE Interface.......................................................................................56
2.2.9 Configuring Self-Loop Detection on the GE Interface............................................................................57
2.2.10 Switching the Working Mode of an Ethernet Interface.........................................................................58
2.2.11 Checking the Configuration...................................................................................................................58
2.3 Configuring Ethernet Interfaces of the SRU....................................................................................................60
2.3.2 Assigning an IP Address to an Ethernet Interface...................................................................................60
2.3.3 Configuring the Working Mode of an Ethernet Electrical Interface.......................................................61
2.3.4 Configuring the Speed of an Ethernet Electrical Interface......................................................................62
2.3.5 Configuring the Promiscuity Mode.........................................................................................................62
2.4 Configuring Ethernet Interfaces Layer 2 Parameters.......................................................................................63
2.4.2 Configuring Link Layer Type of an Ethernet Interface...........................................................................64
2.5 Configuring SmartLink Flush Function...........................................................................................................64
2.5.2 Enabling a Port to Process SmartLink Flush Packets..............................................................................65
2.6 Maintaining Ethernet Interfaces.......................................................................................................................66
2.6.1 Testing the Loop of Ethernet Interfaces..................................................................................................66
2.7 Configuration Examples...................................................................................................................................67
2.7.1 Example for Configuring a Layer 3 Ethernet Interface...........................................................................67
2.7.2 Example for Configuring VLANs to Communicate Through Ethernet Sub-interfaces..........................69
2.7.3 Example for Configuring a Device to Handle Smartlink Flush Packets.................................................69
3 Eth-Trunk Interface Configuration..........................................................................................74

3.1 Eth-Trunk Interface Introduction......................................................................................................................76
3.1.1 Introduction to Eth-Trunk Interfaces and LACP.....................................................................................76
3.1.2 Eth-Trunk Interface and LACP Features Supported by the NE80E/40E................................................77
3.2 Configuring an Eth-Trunk Interface in Manual Load Balancing Mode...........................................................80
3.2.2 Creating an Eth-Trunk Interface..............................................................................................................81
3.2.3 (Optional) Configuring a Working Mode for an Eth-Trunk Interface....................................................82
3.2.4 Configuring an Eth-Trunk Interface to Work in Manual Load Balancing Mode....................................82
3.2.5 Adding Interfaces to an Eth-Trunk Interface...........................................................................................83
Issue 02 (2011-09-10) Huawei Proprietary and Confidential vi


3.3 Configuring an Eth-Trunk Interface in 1:1 Active/Standby Mode...................................................................85
3.3.2 Configuring an Eth-Trunk Interface to Work in 1:1 Active/Standby Mode...........................................86
3.3.3 Adding Interfaces to an Eth-Trunk Interface and Setting the Master Interface......................................87
3.3.4 Enabling the Function of Sending Flush Packets....................................................................................88
3.3.5 Creating a Control VLAN.......................................................................................................................89
3.3.6 Enabling an Interface to Receive Packets from a Control VLAN...........................................................89
3.3.7 Enabling an Interface to Receive Flush Packets......................................................................................90
3.4 Configuring an Eth-Trunk Interface in Static LACP Mode.............................................................................91
3.4.2 Creating an Eth-Trunk Interface..............................................................................................................92
3.4.3 (Optional) Configuring a Working Mode for an Eth-Trunk Interface....................................................93
3.4.4 Configuring an Eth-Trunk Interface to Work in Static LACP Mode......................................................94
3.4.5 Adding Interfaces to an Eth-Trunk Interface...........................................................................................94
3.4.6 (Optional) Setting an LACP System Priority..........................................................................................96
3.4.7 (Optional) Setting the Maximum Number of Active Member Interfaces...............................................96
3.4.8 (Optional) Setting an LACP Interface Priority........................................................................................97
3.4.9 (Optional) Configuring the Mode for Selecting Active Member Interfaces...........................................98
3.4.10 (Optional) Enabling LACP Preemption and Setting an LACP Preemption Delay...............................98
3.4.11 (Optional) Setting a Timeout Period for Receiving LACPDUs............................................................99
3.4.12 Checking the Configuration.................................................................................................................100
3.5 Associating an Eth-Trunk Interface in Static LACP Mode with an mVRRP Backup Group........................101
3.5.1 Establishing the Configuration Task.....................................................................................................101
3.5.2 Configuring VRRP to Track the Status of a Member Interface of an Eth-Trunk Interface in Static LACP
Mode...............................................................................................................................................................104
3.5.3 Associating an Eth-Trunk Interface in Static LACP Mode with an mVRRP Backup Group...............105
3.6 Configuring Layer 2 Attributes for an Eth-Trunk Interface...........................................................................106
3.6.2 (Optional) Configuring the Minimum Number of Up Member Links..................................................107
3.6.3 (Optional) Configuring the Maximum Number of Up Member Links.................................................108
3.6.4 (Optional) Configuring an Eth-Trunk Interface to Carry Out Load Balancing.....................................109
3.6.5 (Optional) Configuring Weights for Member Interfaces.......................................................................110
3.6.6 (Optional) Configuring the Mode for Eth-Trunk Member Interfaces to Send Traps............................110
3.7 Configuring Layer 3 Attributes for an Eth-Trunk Interface...........................................................................112
3.7.2 Configuring an IP address for an Eth-Trunk Interface..........................................................................113
3.7.3 (Optional) Configuring a MAC Address for an Eth-Trunk Interface....................................................113
3.7.4 (Optical) Configuring the MTU for an Eth-Trunk Interface.................................................................114
3.7.5 (Optional) Configuring the Minimum Number of Up Member Links..................................................115
Issue 02 (2011-09-10) Huawei Proprietary and Confidential vii

3.7.6 (Optional) Configuring a Load Balancing Mode for an Eth-Trunk Interface.......................................115

3.7.7 (Optional) Configuring Weights for Member Interfaces.......................................................................116
3.7.8 (Optional) Configuring the Load Balancing Mode for Access Users on an Eth-Trunk Interface.........117
3.7.9 (Optional) Configuring the Mode for Eth-Trunk Member Interfaces to Send Traps............................117
3.8 Configuring an Eth-Trunk Sub-interface........................................................................................................120
3.8.2 Creating an Eth-Trunk Sub-interface.....................................................................................................121
3.8.3 Configuring an IP address for an Eth-Trunk Sub-interface...................................................................121
3.8.4 Configuring the Encapsulation Type for an Eth-Trunk Sub-interface..................................................122
3.8.5 (Optical) Configuring the MTU for an Eth-Trunk Sub-interface..........................................................123
3.8.6 (Optional) Configuring the Rate for Eth-Trunk Sub-interfaces to Send Gratuitous ARP Packets.......123
3.9 Configuring E-Trunk......................................................................................................................................125
3.9.2 Configuring the LACP System ID and Priority for E-Trunk................................................................126
3.9.3 Creating an E-Trunk Group and Configuring the E-Trunk Priority......................................................127
3.9.4 Configuring Local and Peer IP Addresses.............................................................................................127
3.9.5 (Optional)Binding an E-Trunk Group to a BFD Session......................................................................128
3.9.6 Adding an Eth-Trunk Interface to an E-Trunk Group...........................................................................129
3.9.7 (Optional) Configuring the Working Mode for an Eth-Trunk Interface...............................................129
3.9.8 (Optional) Configuring a Password.......................................................................................................130
3.9.9 (Optional) Configuring a Timeout Period.............................................................................................131
3.9.10 (Optional) Setting a Revert Delay.......................................................................................................132
3.10 Maintaining Eth-Trunk Interfaces................................................................................................................133
3.10.1 Clearing Statistics About an Eth-Trunk Interface...............................................................................133
3.11 Configuration Examples...............................................................................................................................134
3.11.1 Example for Configuring Eth-Trunk Interfaces in Manual Load Balancing Mode............................134
3.11.2 Example for Configuring an Eth-Trunk Interface in 1:1 Active/Standby Mode.................................137
3.11.3 Example for Configuring Eth-Trunk Interfaces in Static LACP Mode...............................................142
3.11.4 Example for Associating an Eth-Trunk Interface in Static LACP Mode with an mVRRP Backup Group
........................................................................................................................................................................146
3.11.5 Example for Configuring Eth-Trunk Interfaces in Static LACP Mode to Communicate over a VLL
Network..........................................................................................................................................................157
3.11.6 Example for Configuring a Layer 2 Eth-Trunk Interface to Allow VLAN Frames to Pass Through
........................................................................................................................................................................166
3.11.7 Example for Configuring a Layer 3 Eth-Trunk Interface in Manual Load Balancing Mode..............168
3.11.8 Example for Configuring Inter-VLAN Communication by Using Eth-Trunk Sub-interfaces............171
3.11.9 Example for Connecting an E-Trunk to a VPLS Network..................................................................175
3.11.10 Example for Connecting an E-Trunk to PW Redundancy.................................................................187
4 VLAN Configuration................................................................................................................201
4.1 VLAN Introduction........................................................................................................................................203
Issue 02 (2011-09-10) Huawei Proprietary and Confidential viii

4.1.1 Introduction...........................................................................................................................................203
4.1.2 VLAN Features Supported by the NE80E/40E.....................................................................................210
4.2 Configuring a VLAN Based on Ports.............................................................................................................215
4.2.2 Creating a VLAN...................................................................................................................................216
4.2.3 Configuring the Type of a Layer 2 Ethernet Port..................................................................................216
4.2.4 Adding a Port to a VLAN......................................................................................................................219
4.3 Creating a VLANIF Interface.........................................................................................................................220
4.3.2 Creating a VLANIF Interface................................................................................................................221
4.3.3 Assigning an IP Address to a VLANIF Interface..................................................................................221
4.3.4 (Optional) Setting a Delay After Which a VLANIF Interface Goes Down..........................................222
4.3.5 (Optional) Configuring Bandwidth for a VLANIF Interface................................................................223
4.4 Configuring Inter-VLAN Communication.....................................................................................................224
4.4.2 Configuring Sub-interfaces for Inter-VLAN Communication..............................................................226
4.4.3 Configuring VLANIF Interfaces for Inter-VLAN Communication......................................................228
4.4.4 Configuring VLAN Mapping for Inter-VLAN Communication...........................................................229
4.5 Configuring VLAN Security Attributes.........................................................................................................233
4.5.2 Disabling a Port from Broadcasting Packets to Other Ports in the Same VLAN..................................235
4.5.3 Disabling MAC Address Learning in a VLAN.....................................................................................236
4.5.4 Enabling Flexible MAC Address Learning in a VLAN........................................................................237
4.5.5 (Optional) Disabling an Interface from Sending Unknown Unicast Packets to Other Interfaces in a VLAN
........................................................................................................................................................................238
4.6 Configuring VLAN Aggregation to Save IP Addresses.................................................................................239
4.6.2 Creating a Sub-VLAN...........................................................................................................................241
4.6.3 Creating a Super-VLAN........................................................................................................................241
4.6.4 Assigning an IP Address to the VLANIF Interface of a Super-VLAN.................................................242
4.6.5 (Optional) Configuring an IP Address Pool for a Sub-VLAN..............................................................242
4.6.6 (Optional) Enabling Proxy ARP on the VLANIF Interface of a Super-VLAN....................................243
4.7 Configuring VLAN Policy-based VPN Access..............................................................................................245
4.7.2 Configuring a VLAN Policy..................................................................................................................247
4.7.3 Configuring a VPN................................................................................................................................249
4.8 Configuring Interface Isolation in a VLAN...................................................................................................251
Issue 02 (2011-09-10) Huawei Proprietary and Confidential ix


4.8.2 Configuring Interface Isolation in a VLAN..........................................................................................252
4.8.3 Enabling ARP Proxy in a VLAN..........................................................................................................253
4.9 Configuring the Isolation Based on Interface Groups in a VLAN.................................................................253
4.9.2 Adding an Interface to the Group to Be Isolated...................................................................................254
4.10 Configuring Ethernet Loop Detection for a VLAN......................................................................................255
4.10.1 Establishing the Configuation Task.....................................................................................................256
4.10.2 Configuring Ethernet Loop Detection for a VLAN.............................................................................256
4.10.3 (Optional) Configuring the Block Priority for an Interface.................................................................257
4.11 Maintaining VLAN.......................................................................................................................................258
4.11.1 Clearing the Statistics of VLAN Packets............................................................................................259
4.12.1 Example for Configuring Users in a VLAN to Communicate by Using a Trunk Link.......................259
4.12.2 Example for Configuring Inter-VLAN Communication by Using Sub-interfaces.............................264
4.12.3 Example for Configuring VLAN and Non-VLAN Users to Communicate by Using Sub-interfaces
........................................................................................................................................................................268
4.12.4 Example for Configuring Inter-VLAN Communication by Using VLANIF Interfaces.....................271
4.12.5 Example for Configuring 1 to 1 VLAN Mapping for Inter-VLAN Communication..........................275
4.12.6 Example for Configuring Communication Between VLANs Through VLAN Aggregation..............279
4.12.7 Example for Configuring VLAN+802.1p for L2VPN Access (on a Common Sub-interface)...........283
4.12.8 Example for Configuring VLAN+DSCP for L2VPN Access (on a Common Sub-interface)............289
4.12.9 Example for Configuring VLAN+EthType for L2VPN Access (on a Common Sub-interface)........295
4.12.10 Example for Configuring VLAN+DSCP for L3VPN Access (on a Common Sub-interface)..........301
4.12.11 Example for Configuring VLAN+802.1p for L3VPN Access (on a Common Sub-interface).........310
4.12.12 Example for Configuring Untagged+DSCP for L3VPN Access.......................................................319
4.12.13 Example for Configuring Interface Isolation in a VLAN..................................................................328
4.12.14 Example for Configuring the Isolation Based on Interface Groups in a VLAN...............................330
4.12.15 Example for Configuring Ethernet Loop Detection for a VLAN......................................................333
5 QinQ Configuration..................................................................................................................337
5.1 QinQ Introduction...........................................................................................................................................339
5.1.1 QinQ Overview......................................................................................................................................339
5.1.2 QinQ Feature Supported by the NE80E/40E.........................................................................................340
5.2 Configuring the QinQ Tunnel Function.........................................................................................................349
5.2.2 Creating the Outer VLAN Tag for a Layer 2 Interface.........................................................................350
5.2.3 Configuring QinQ for a Layer 2 Interface.............................................................................................351
5.2.4 (Optional) Configuring the Protocol Type for the Outer Tag................................................................351
5.2.5 (Optional) Configuring the Protocol Type for the InnerTag.................................................................352
Issue 02 (2011-09-10) Huawei Proprietary and Confidential x

5.3 Configuring Selective QinQ on a Layer 2 Interface.......................................................................................353

5.3.2 Creating the Outer VLAN Tag for a Layer 2 Interface.........................................................................354
5.3.3 Configuring Selective QinQ on a Layer 2 Interface..............................................................................354
5.3.4 (Optional) Configuring the Protocol Type for the Outer Tag................................................................355
5.3.5 (Optional) Configuring the Protocol Type for the InnerTag.................................................................356
5.4 Configuring the Sub-interface for VLAN Tag Termination to Access the IP Service...................................357
5.4.2 Configuring the Interface Mode as the User-Termination Mode..........................................................359
5.4.3 Configuring the Sub-interface for dot1q VLAN Tag Termination.......................................................359
5.4.4 Configuring the Sub-interface for QinQ VLAN Tag Termination........................................................360
5.4.5 Configuring the IP Service....................................................................................................................360
5.5 Configuring the Sub-interface for VLAN Tag Termination to Access the Multicast Service.......................362
5.5.5 Configuring the Multicast Service.........................................................................................................365
5.6 Configuring the Sub-interface for VLAN Tag Termination to Access the VPN Service..............................368
5.6.5 Configuring the VPN Service................................................................................................................373
5.7 Configuring the Sub-interface for VLAN Tag Termination to Access the MPLS Service............................378
5.7.5 Configuring the MPLS Service.............................................................................................................381
5.8 Configuring the Sub-interface for QinQ VLAN Tag Termination to Support 802.1p Mapping...................382
5.8.3 Configuring the Sub-interface for QinQ VLAN Tag Termination to Support 802.1p Mapping..........384
5.9 Configuring the Sub-interface for QinQ Stacking to Access an L2VPN.......................................................385
Issue 02 (2011-09-10) Huawei Proprietary and Confidential xi


5.9.3 Configuring the Sub-interface for VLAN Stacking..............................................................................387
5.9.4 Configuring the L2VPN........................................................................................................................388
5.10 Configuring Dynamic QinQ.........................................................................................................................393
5.10.1 Establishing the Configuration Task...................................................................................................393
5.10.2 Configuring the Interface Mode as the User-Termination Mode........................................................394
5.10.3 Configuring Dynamic QinQ................................................................................................................394
5.10.4 Configuring DHCP Snooping..............................................................................................................395
5.11 Configuring the Sub-interface for QinQ VLAN Tag Termination to Support URPF..................................397
5.11.2 Configuring the Ethernet Interface of the PE......................................................................................398
5.11.3 Configuring the Ethernet Sub-interface of the PE...............................................................................398
5.11.4 Configuring URPF on the Sub-interface for QinQ VLAN Tag Termination......................................399
5.12 Configuring the User-Side QinQ..................................................................................................................400
5.12.2 Creating a User-Side VLAN................................................................................................................400
5.13 Maintaining QinQ.........................................................................................................................................402
5.13.1 Clearing QinQ Statistics......................................................................................................................402
5.13.2 Monitoring the Operating Status of the Termination Sub-interface....................................................402
5.14.1 Example for Configuring the QinQ Tunnel.........................................................................................403
5.14.2 Example for Configuring Selective QinQ on a Layer 2 Interface.......................................................407
5.14.3 Example for Configuring Compatibility of the EthType Field in the Outer Tag of QinQ Packets
........................................................................................................................................................................410
5.14.4 Example for Configuring the Sub-interface for dot1q VLAN Tag Termination to Support Proxy ARP
........................................................................................................................................................................411
5.14.5 Example for Configuring the Sub-interface for QinQ VLAN Tag Termination to Support Proxy ARP
........................................................................................................................................................................414
5.14.6 Example for Configuring the Sub-interface for dot1q VLAN Tag Termination to Support VRRP
........................................................................................................................................................................418
5.14.7 Example for Configuring the Sub-interface for QinQ VLAN Tag Termination to Support VRRP
........................................................................................................................................................................426
5.14.8 Example for Configuring the Sub-interface for dotlq and QinQ VLAN Tag Termination to Access an
L3VPN............................................................................................................................................................438
5.14.9 Example for Configuring the Dot1q Termination Sub-interface to Access the VLL..........................451
5.14.10 Example for Configuring the Sub-interface for QinQ VLAN Tag Termination to Access a VLL
........................................................................................................................................................................460
5.14.11 Example for Configuring the Sub-interface for dot1q and QinQ VLAN Tag Termination to Access a
VPLS..............................................................................................................................................................469
5.14.12 Example for Configuring the Sub-interface for QinQ VLAN Tag Termination to Access a VPLS
Network..........................................................................................................................................................480
Issue 02 (2011-09-10) Huawei Proprietary and Confidential xii

5.14.13 Example for Configuring a Sub-interface for QinQ VLAN Tag Termination to Support the Local
Connection......................................................................................................................................................494
5.14.14 Example for Configuring the Sub-interface for dot1q VLAN Tag Termination to Support the DHCP
Relay Function................................................................................................................................................499
5.14.15 Example for Configuring the Sub-interface for QinQ VLAN Tag Termination to Support the DHCP
Relay Function................................................................................................................................................503
5.14.16 Example for Configuring Dynamic QinQ.........................................................................................508
5.14.17 Example for Configuring the Sub-interface for VLAN Stacking to Access a VLL..........................516
5.14.18 Example for Configuring the Sub-interface for QinQ VLAN Stacking to Access a VPLS Network
........................................................................................................................................................................526
5.14.19 Example for Configuring the Sub-interface for QinQ VLAN Tag Termination to Support URPF
........................................................................................................................................................................539
5.14.20 Example for Configuring the dot1q Termination Sub-interface in a VSI to Support IGMP Snooping
........................................................................................................................................................................541
5.14.21 Example for Configuring the QinQ Termination Sub-interface in a VSI to Support IGMP Snooping
........................................................................................................................................................................549
5.14.22 Example for Configuring the dot1q Termination Sub-interface to Support IGMP and Access an L3VPN
........................................................................................................................................................................557
5.14.23 Example for Configuring the QinQ Termination Sub-interface to Support IGMP and Access an L3VPN
........................................................................................................................................................................567
5.14.24 Example for Configuring the QinQ Termination Sub-interface to Support Single-AS MD VPN
........................................................................................................................................................................575
5.14.25 Example for Configuring the Sub-interface for QinQ VLAN Tag Termination to Support MPLS TE
........................................................................................................................................................................586
5.14.26 Example for Configuring the User-Side QinQ..................................................................................594
5.14.27 Example for Configuring VLAN+802.1p for L2VPN Access (on a Sub-interface for Dot1q VLAN Tag
Termination)...................................................................................................................................................595
5.14.28 Example for Configuring VLAN+EthType for L2VPN Access (on a Sub-interface for Dot1q VLAN
Tag Termination)............................................................................................................................................602
5.14.29 Example for Configuring VLAN+DSCP for L2VPN Access (on a Sub-interface for Dot1q VLAN Tag
Termination)...................................................................................................................................................610
5.14.30 Example for Configuring QinQ Stacking Sub-interface+802.1p for L2VPN Access.......................617
5.14.31 Example for Configuring Stacking Sub-interface+EthType for L2VPN Access..............................624
5.14.32 Example for Configuring Stacking Sub-interface+DSCP for L2VPN Access..................................631
5.14.33 Example for Configuring VLAN+802.1p for L3VPN Access (on a Sub-interface for Dot1q VLAN Tag
Termination)...................................................................................................................................................638
5.14.34 Example for Configuring VLAN+DSCP for L3VPN Access (on a Sub-interface for Dot1q VLAN Tag
Termination)...................................................................................................................................................649
6 STP/RSTP Configuration.........................................................................................................660
6.1 STP/RSTP Overview......................................................................................................................................661
6.1.1 STP/RSTP Overview.............................................................................................................................661
6.1.2 STP/RSTP Features Supported by the NE80E/40E..............................................................................666
6.2 Configuring Basic STP/RSTP Functions.......................................................................................................668
6.2.2 Configuring the STP/RSTP Mode.........................................................................................................670
6.2.3 (Optional) Configuring Switching Device Priorities.............................................................................670
Issue 02 (2011-09-10) Huawei Proprietary and Confidential xiii

6.2.4 (Optional) Setting the Path Cost for a Port............................................................................................671

6.2.5 (Optional) Configuring Port Priorities...................................................................................................672
6.2.6 Enabling STP/RSTP..............................................................................................................................673
6.3 Configuring STP/RSTP Parameters on an Interface......................................................................................675
6.3.2 Setting System Parameters....................................................................................................................678
6.3.3 Setting Port Parameters.........................................................................................................................679
6.4 Configuring RSTP Protection Functions........................................................................................................682
6.4.2 Configuring BPDU Protection on a Switching Device.........................................................................684
6.4.3 Configuring TC Protection on a Switching Device...............................................................................685
6.4.4 Configuring Root Protection on a Port..................................................................................................686
6.4.5 Configuring Loop Protection on a Port.................................................................................................687
6.5 Configuring STP/RSTP Interoperability Between Huawei Devices and Non-Huawei Devices....................689
6.5.2 Configuring the BPDU Format on a Switching Device........................................................................689
6.5.3 Configuring the Proposal/Agreement Mechanism................................................................................690
6.6 Maintaining STP/RSTP..................................................................................................................................692
6.6.1 Clearing STP/RSTP Statistics...............................................................................................................692
6.7 Configuration Examples.................................................................................................................................693
6.7.1 Example for Configuring Basic STP Functions....................................................................................693
6.7.2 Example for Configuring Basic RSTP Functions..................................................................................700
7 MSTP Configuration.................................................................................................................707
7.1 MSTP Overview.............................................................................................................................................709
7.1.1 MSTP Introduction................................................................................................................................709
7.1.2 MSTP Features Supported by the NE80E/40E......................................................................................717
7.2 Configuring Basic MSTP Functions...............................................................................................................722
7.2.2 Configuring the MSTP Mode................................................................................................................724
7.2.3 Configuring and Activating an MST Region........................................................................................724
7.2.4 (Optional) Setting a Priority for a Switching Device in an MSTI.........................................................726
7.2.5 (Optional) Setting a Path Cost of a Port in an MSTI.............................................................................727
7.2.6 (Optional) Setting a Port Priority in an MSTI.......................................................................................728
7.2.7 Enabling MSTP.....................................................................................................................................729
7.3 Configuring MSTP Multi-process..................................................................................................................731
7.3.2 Creating an MSTP Process....................................................................................................................732
Issue 02 (2011-09-10) Huawei Proprietary and Confidential xiv

7.3.3 Adding an Interface to an MSTP Process - Access Links.....................................................................733

7.3.4 Adding an Interface to an MSTP Process - Share Link.........................................................................734
7.3.5 Configuring Priorities and Root Protection in MSTP Multi-process....................................................734
7.3.6 Configuring TC Notification in MSTP Multi-process..........................................................................735
7.4 Configuring MSTP Parameters on an Interface.............................................................................................736
7.4.2 Configuring System Parameters............................................................................................................737
7.4.3 Configuring Port Parameters.................................................................................................................739
7.5 Configuring MSTP Protection Functions.......................................................................................................742
7.5.2 Configuring BPDU Protection on a Switching Device.........................................................................745
7.5.3 Configuring TC Protection on a Switching Device...............................................................................745
7.5.4 Configuring Root Protection on an Interface........................................................................................746
7.5.5 Configuring Loop Protection on an Interface........................................................................................747
7.5.6 Configuring Share-Link Protection on a Switching Device..................................................................748
7.6 Configuring MSTP Interoperability Between Huawei Devices and Non-Huawei Devices...........................750
7.6.2 Configuring the BPDU Format on a Switching Device........................................................................751
7.6.3 Configuring a Proposal/Agreement Mechanism...................................................................................751
7.6.4 Configuring the MSTP Protocol Packet Format on an Interface...........................................................753
7.6.5 Binding VLANs for an Interface to an MSTP Process.........................................................................754
7.6.6 Enabling the Digest Snooping Function................................................................................................754
7.7 Maintaining MSTP.........................................................................................................................................756
7.7.1 Clearing MSTP Statistics.......................................................................................................................756
7.8.1 Example for Configuring Basic MSTP Functions.................................................................................757
7.8.2 Example for Configuring MSTP Multi-process....................................................................................766
7.8.3 Example for Configuring MSTP Multi-process for Layer 2 Single-Access Rings and Layer 2 Multi-Access
Rings...............................................................................................................................................................776
7.8.4 Example for Configuring E-STP - Inter-AS Option A (Martini Mode)................................................783
7.8.5 Example for Configuring E-STP - Inter-AS PW Interconnection (Martini Mode)...............................797
7.8.6 Example for Configuring E-STP for CE Dual-Homing........................................................................812
8 BPDU Tunnel Configuration..................................................................................................824

8.1 BPDU Tunnel Overview................................................................................................................................825
8.1.1 Introduction to BPDU............................................................................................................................825
8.1.2 BPDU Tunnel Features Supported by the NE80E/40E.........................................................................826
8.2 Configuring Interface-based BPDU Tunnels.................................................................................................831
Issue 02 (2011-09-10) Huawei Proprietary and Confidential xv

8.2.2 Enabling STP function on the PEs and the CEs....................................................................................832

8.2.3 Adding the Interfaces of the PE Connected with the CE to a Specified VLAN...................................832
8.2.4 Configuring Interface-based BPDU Tunnel..........................................................................................833
8.2.5 Configuring PE Interfaces Connecting PSNs to Permit Packets with Specified Tags..........................834
8.3 Configuring VLAN-based BPDU Tunnels.....................................................................................................836
8.3.2 Enabling the STP Function on CEs and PEs.........................................................................................837
8.3.3 Configuring BPDUs from CEs to PEs to Carry Specified Tags............................................................837
8.3.4 Configuring VLAN-based BPDU Tunnel.............................................................................................838
8.3.5 Configuring PE Interfaces Connecting PSN to Permit Packets with Specified Tags............................840
8.4 Configuring QinQ-based BPDU Tunnels.......................................................................................................842
8.4.2 Enabling the STP Function on CEs and PEs.........................................................................................843
8.4.3 Configuring the BPDUs from CEs to PEs to Carry the Specified Tags................................................843
8.4.4 Configuring QinQ-based BPDU Tunnel...............................................................................................844
8.4.5 Configuring PE Interfaces Connecting PSNs to Permit the Packets with Specified Tags....................846
8.5.1 Example for Configuring Interface-based BPDU Tunnel (Devices of Different Roles).......................849
8.5.2 Example for Configuring Interface-based BPDU Tunnel (Devices of the Same Role)........................855
8.5.3 Example for Configuring VLAN-based Tunnel of BPDUs..................................................................862
8.5.4 Example for Configuring Tunnel of BPDUs Based on QinQ...............................................................869
9 RRPP Configuration.................................................................................................................877
9.1 RRPP Introduction..........................................................................................................................................879
9.1.1 Overview of RRPP................................................................................................................................879
9.1.2 RRPP Features Supported by the NE80E/40E......................................................................................879
9.2 Configuring RRPP Functions.........................................................................................................................883
9.2.2 Creating the RRPP Domain...................................................................................................................884
9.2.3 Creating the Control VLAN..................................................................................................................885
9.2.4 (Optional) Setting the Values of RRPP Domain Timers.......................................................................885
9.2.5 Configuring the Ports on a RRPP Ring.................................................................................................886
9.2.6 Creating the RRPP Ring........................................................................................................................887
9.2.7 Enabling the RRPP Ring.......................................................................................................................888
9.2.8 Enabling RRPP......................................................................................................................................889
9.3 Configuring the Monitoring Interface............................................................................................................891
9.3.2 Configuring the Monitoring Interface...................................................................................................892
Issue 02 (2011-09-10) Huawei Proprietary and Confidential xvi

9.4 Configuring RRPP Snooping..........................................................................................................................893

9.4.2 Enabling RRPP Snooping......................................................................................................................895
9.4.3 (Optional) Configuring the VSI Associated with the RRPP Snooping.................................................896
9.5 Maintaining RRPP..........................................................................................................................................897
9.5.1 Clearing RRPP Running Information....................................................................................................897
9.6.1 Example for Configuring a Single RRPP Ring.....................................................................................898
9.6.2 Example for Configuring a Crossed RRPP Ring...................................................................................902
9.6.3 Example for Configuring a Tangent RRPP Ring..................................................................................911
9.6.4 Example for Configuring a Crossed RRPP Ring to Connect Dual NPE...............................................918
9.6.5 Example for Configuring the RRPP Snooping......................................................................................934
A Glossary......................................................................................................................................943
B Acronyms and Abbreviations.................................................................................................950
Issue 02 (2011-09-10) Huawei Proprietary and Confidential xvii

Configuration Guide - LAN Access and MAN Access 1 MAC Address Table Configuration
1 MAC Address Table Configuration
About This Chapter
Each workstation or server that is connected to the Ethernet interface on a device has a unique
Medium Access Control (MAC) address. The MAC address table on the device contains the
MAC addresses of all the other devices that are connected to this device. The MAC address table
is used for data forwarding.
1.1 MAC Address Table Introduction

A MAC address table is an interface-based Layer 2 forwarding table. It stores information about
the MAC addresses learned by the device.
1.2 Configuring the MAC Address Table Based on the VLAN and Layer 2 Interface
If user networks are connected through Layer 2 devices and do not forward data through Layer
3 routing, you can configure a MAC address table based on Layer 2 interfaces and VLANs for
data forwarding. Thus, user networks can communicate with each other.
1.3 Configuring the MAC Address Table Based on the VSI and Layer 3 Interface
If user networks are connected through a Virtual Private LAN Service (VPLS) network, you can
configure a MAC address table based on Layer 3 interfaces and Virtual Switch Instances (VSIs).
Thus, user networks can communicate with each other.
1.4 Configuring the Aging Time of a MAC Address Table
After the network topology changes, dynamic MAC address entries are not automatically
updated in time. As a result, a device cannot learn new MAC addresses and thus user traffic
cannot be normally forwarded. To addresses this problem, you need to configure the aging time
of MAC address entries.
1.5 Maintaining MAC Address Table
This section provides commands used to maintain MAC address tables, including the command
that is used to delete dynamic MAC address tables.
1.6 Configuration Examples
This section lists networking requirements, configuration roadmap, and data preparation to
describe the typical application scenarios of MAC address tables, and provides related
configuration files.
Issue 02 (2011-09-10) Huawei Proprietary and Confidential 1

1.1 MAC Address Table Introduction

A MAC address table is an interface-based Layer 2 forwarding table. It stores information about
the MAC addresses learned by the device.
1.1.1 MAC Address Table Overview

MAC address entries can be classified into dynamic entries, static entries, and blackhole entries.
All workstations and servers connected by the Ethernet interfaces of a device have unique MAC
(Medium Access Control) address. The MAC address table on the device contains the
information about the MAC addresses of all the devices connected by this device.
MAC address entries are classified into the following types:
l Dynamic entries
Dynamic entries are learned and stored on interface boards. The dynamic entries expire
and are lost after hot swapping or interface-board resetting, or device rebooting.
l Static entries
Static entries are configured by users. They are automatically delivered to each interface
board. Static entries do not expire and are not lost after device rebooting, hot swapping, or
interface-board resetting.
l Blackhole entries
Blackhole entries, configured by users, are used to discard frames containing specified
MAC address. They are delivered to each interface board. The blackhole entries do not
expire and are not lost after device rebooting, hot swapping or interface-board resetting.
1.1.2 MAC Addresses Learning Limit Supported by the NE80E/40E

As the capacity of a MAC address table is limited, it is necessary to specify the maximum number
of MAC addresses to be learned and limit the rate at which MAC addresses are learned. In this
manner, you can control the number of access users and prevent malicious users from attacking
user devices and networks through MAC addresses.
For the MAC address learning limit, refer to the HUAWEI NetEngine80E/40E Router
Configuration Guide - Security.
1.2 Configuring the MAC Address Table Based on the

VLAN and Layer 2 Interface
If user networks are connected through Layer 2 devices and do not forward data through Layer
3 routing, you can configure a MAC address table based on Layer 2 interfaces and VLANs for
data forwarding. Thus, user networks can communicate with each other.

1.2.1 Establishing the Configuration Task

Before configuring a MAC address table based on Layer 2 interfaces and VLANs, familiarize
yourself with the applicable environment, complete the pre-configuration tasks, and obtain the
required data. This can help you complete the configuration task quickly and accurately.
Applicable Environment
NOTE
The ATM interface cannot be configured on the X1 and X2 models of the NE80E/40E.
Generally, a device automatically creates MAC address tables by learning source addresses.
To enhance the security of an interface, network administrators can manually bind a MAC
address and an interface in the table. This can prevent malicious users with counterfeit MAC
address from logging in to the local device through other switches.
To discard the frames to the specified destination MAC address, configure blackhole entries.
Pre-configuration Tasks
Before configuring the MAC address table based on the VLAN and Layer 2 interface, complete
the following tasks:
l Creating a VLAN
l Ensuring that the Layer 2 ports in the MAC address entries are added to the VLAN
l Ensuring that the mapping between the VE interface and the PVC of the ATM interface is
established if the outbound interface is a VE interface
NOTE
For the configuration of the mapping between the VE interface and the PVC of the ATM interface, refer
to the HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access.
Data Preparation
To configure the MAC address table based on the VLAN and Layer 2 interface, you need the
following data.
No. Data
1 MAC address
2 Port number
3 VLAN ID
1.2.2 Configuring MAC Address Entries

To enhance the security of an interface and to prevent the invalid users from accessing the
interface, the network administrator can manually configure static MAC address entries and bind
MAC addresses to the interface, or discard the packets with specified destination MAC
addresses. The interface to which the MAC addresses are bound must be a switched interface,

and must be added to a specified VLAN, or the interface allows the packets with specified VLAN
IDs to pass through.
Procedure
Step 1 Run:
system-view
The system view is displayed.

Step 2 Run:
mac-address static mac-address interface-type interface-number vlan vlan-id [ ce-
vlan ce-vlan]
MAC address entries are added.

Note the following:
l You can add only unicast MAC addresses rather than multicast MAC addresses and special
MAC addresses to a MAC address table. Special MAC addresses are reserved for special
usage, such as MAC addresses of special packets.
l The interface type can be physical interface such as Ethernet interface and GE interface, or
logical interface such as Eth-Trunk interface and MAC-Tunnel. The interface specified in
the mac-address static command must be a switched interface, serving as an outbound
interface for Layer 2 forwarding.
l The vlan-id must be associated with ports. That is, the VLAN contains the port. Alternatively,
this interface allows the VLAN to pass through.
l When ce-vlan is used, it indicates that the interface specified by interface-type interface-
number is added to the specified VLAN in VLAN mapping mode. The parameter ce-vlan
indicates the exterior VLAN ID in frames received by the port.
l When ce-vlan is not used, it indicates that the interface specified by interface-type interface-
number is added to the specified VLAN in port default, trunk, or VLAN stacking mode.
l A maximum of 1024 non-dynamic entries can be added.
Step 3 Run:
mac-address blackhole mac-address vlan vlan-id
The blackhole MAC address entry is configured.
----End
1.2.3 Configuring MAC Address Entries Based on the Layer 2 VE

Interface
If the interface bound to the MAC address of a user device is a Virtual Ethernet (VE) interface,
you can configure a MAC address table based on Layer 2 VE interfaces. In this manner, the
packets with specific destination MAC addresses are forwarded by specified interfaces.
Context
NOTE
Do as follows on the router where the VLAN is created:

Procedure
Step 1 Run:
system-view
Step 2 Run:
mac-address static mac-address virtual-ethernet interface-number atm interface-
number pvc { pvc-name [ vpi | vci ] | vpi | vci } vlan vlan-id
MAC address entries are added. Note the following:
l The VE interface must be a switched interface. In addition, the VE interface must be
associated with the VLAN specified by vlan-id. That is, the VLAN contains this VE interface;
or this VE interface is added to VLAN by default.
l The mapping between the VE interface and the PVC of the ATM interface is established,
and the VE interface is added to the specified VLAN.
----End
1.2.4 Checking the Configuration

After the MAC address table based on Layer 2 interfaces and VLANs is successfully configured,
you can view the destination MAC addresses, outbound interfaces, and MAC address types.
Prerequisite
The configurations of the MAC address table based on the VLAN and layer 2 interface are
complete.
Procedure
l Run the display mac-address [ mac-address [ vlan vlan-id | vsi vsi-name | verbose ] ]
command to check information about all MAC address entries.
l Run the display mac-address blackhole [ vlan vlan-id | vsi vsi-name ] to check information
about black-hole MAC address entries.
l Run the display mac-address static [ vlan vlan-id | vsi vsi-name ] to check information
about static MAC address entries.
l Run the following commands to check information about dynamic MAC address entries.
– Run the display mac-address dynamic verbose command.
– Run the display mac-address dynamic [ slot-id ] [ vlan vlan-id | vsi vsi-name | source-
slot source-slot-id | interface-type interface-number ] command.
l Run the display mac-address summary command to check statistic information about
MAC address entries.
----End

Example
Run the display mac-address command. You can view the information about the MAC address,
the outbound interface corresponding to the MAC address, and the MAC address type. For
example:
<HUAWEI> display mac-address
MAC address table of slot 0:
--------------------------------------------------------------------------------
MAC Address VLAN/ PEVLAN CEVLAN Port Type LSP/LSR-ID
VSI/SI MAC-Tunnel
--------------------------------------------------------------------------------
0011-2233-4455 abc 1 - GE1/0/1.10 static 2/-
0002-0002-0002 2 - - GE2/0/1 static -
--------------------------------------------------------------------------------
Total matching items on slot 0 displayed = 2

--------------------------------------------------------------------------------
VSI/SI MAC-Tunnel
--------------------------------------------------------------------------------
0000-c102-0104 200 - - GE1/0/1 dynamic -
0000-c102-0105 200 - - GE1/0/1 dynamic -
0000-c102-0102 200 - - GE1/0/1 dynamic -
0000-c102-0106 200 - - GE1/0/1 dynamic -
0000-c102-0103 200 - - GE1/0/1 dynamic -
-------------------------------------------------------------------------------
Run the display mac-address summary command to display all the statistics of the MAC
address entries. Such as:
<HUAWEI> display mac-address summary
-------------------------------------------------------------
Slot Total Blackhole Static Dynamic Capacity FE
-------------------------------------------------------------
1 1 0 0 1 0 0
2 0 0 0 0 0 0
-------------------------------------------------------------
1.3 Configuring the MAC Address Table Based on the VSI

and Layer 3 Interface
If user networks are connected through a Virtual Private LAN Service (VPLS) network, you can
configure a MAC address table based on Layer 3 interfaces and Virtual Switch Instances (VSIs).
Thus, user networks can communicate with each other.

Before configuring a MAC address table based on Layer 3 interfaces and VSIs, familiarize
NOTE

In a Virtual Private LAN Service (VPLS) network, provider edges (PEs) learn MAC addresses.
A PE learns the MAC address of the remote PE through the pseudo wire (PW) and learns the
MAC address of the customer edge (CE) that directly accesses the PE through the Attachment
Circuit (AC). In this manner, the PE automatically establishes the MAC address table.
To improve the network security, configure the mapping between the MAC address of the CE
and the PE interface in the MAC address table of the PE, that is, the static MAC address entries
on the AC side. On the PE, binding a MAC address to an interface can prevent illegal users from
accessing the network.
To discard the frames to the specified destination MAC address, configure blackhole entries.
NOTE
For concepts and configurations in VPLS, refer to the "VPLS Configuration" in the HUAWEI
NetEngine80E/40E Router Configuration Guide - VPN.
Before configuring the MAC address table based on the virtual switching instance (VSI) and
Layer 3 interface, complete the following tasks:
l Configuring the VPLS and binding the VSI to the outbound interface
l Establishing the mapping between the VE interface and the PVC of the ATM interface if
the outbound interface is a VE interface
l Configuring the sub-interface with dot1q termination or QinQ termination or qinq stacking
or vlan-type dot1q if the outbound interface is a sub-interface
NOTE
l For the configuration of the mapping between the VE interface and the PVC of the ATM interface,
refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access.
l For the configuration of dot1q termination or QinQ termination or qinq stacking on a sub-interface,
refer to QinQ Configuration.
Data Preparation
To configure the MAC address table based on the VSI and Layer 3 interface, you need the
following data.
No. Data
1 VSI name
2 MAC addresses
3 Interface type and number
4 PE VLAN ID
5 CE VLAN ID
1.3.2 Configuring MAC Address Entries

To enhance the security of an interface and to prevent the invalid users from connecting to the
interface, the network administrator can manually configure static MAC address entries and bind

MAC addresses to the main interface or sub-interfaces, or discard the packets with specified
destination MAC addresses. An interface that is bound to certain MAC addresses must be bound
to a specified VSI.
Context
Do as follows on the equipment where the VSI is created:
Procedure
Step 1 Run:
system-view

Step 2 Run:
mac-address static mac-address interface-type interface-number vsi vsi-name [ pe-
vid pe-vid [ ce-vid ce-vid ] ]
MAC address entries are added.

Note the following:
l The interface type can be Ethernet interface, Ethernet sub-interface, GE interface, GE sub-
interface, Eth-Trunk interface, or Eth-Trunk sub-interface.
l Ensure that the interface in this command is bound to the VSI specified by vsi-name.
l When pe-vid is used, the interface specified by interface-type interface-number must be a
sub-interface. In addition, this sub-interface must be configured with dot1q termination, qinq
stacking or vlan-type dot1q and bound to the VSI.
NOTE
The parameter pe-vid must be configured when configuring static MAC address entries based on the
sub-interface of qinq stacking, or the traffic would be blocked.
l When pe-vid and ce-vid are used, the interface specified by interface-type interface-
number must be a sub-interface. In addition, this sub-interface must be configured with QinQ
termination and bound to the VSI.
Step 3 Run:
mac-address blackhole mac-address vsi vsi-name
----End
1.3.3 Configuring MAC Address Entries Based on the VLANIF

Interface
The PEs that are connected to the VPLS network are Layer 2 switching devices with Layer 2
interfaces. To enable the packets from the PEs to be transmitted on the VPLS network, you need
to configure VLANIF interfaces, and bind the VLANIF interfaces to VSIs to access the VPLS

network. Configuring a MAC address table based on VLANIF interfaces can prevent invalid
users from connecting to the device.
Context
Do as follows on the equipment where the VSI is created:
Procedure
Step 1 Run:
system-view

Step 2 Run:
mac-address static mac-address interface-type interface-number vlanif interface-
number vsi vsi-name
MAC address entries are added. Note the following:

l The interface-type can be Ethernet interface, GE interface, or Eth-Trunk interface.
l The interface specified by interface-type interface-number is added to the VLAN
corresponding to the VLANIF interface, and the VLANIF interface is bound to the specified
VSI.
Step 3 Run:
mac-address blackhole mac-address { vlan vlan-id | vsi vsi-name
----End

After the MAC address table based on Layer 3 interfaces and VSIs is successfully configured,
you can view the destination MAC addresses, outbound interfaces, and MAC address types.
Prerequisite
The configurations of the MAC address table based on the VSI and layer 3 interface are complete.
Procedure
l Run the display mac-address [ mac-address [ vlan vlan-id | vsi vsi-name | verbose ] ]
command to check information about all MAC address entries.
l Run the display mac-address blackhole [ vlan vlan-id | vsi vsi-name ] to check information
about black-hole MAC address entries.
l Run the display mac-address static [ vlan vlan-id | vsi vsi-name ] to check information
about static MAC address entries.
l Run the following commands to check information about dynamic MAC address entries.

– Run the display mac-address dynamic verbose command.

– Run the display mac-address dynamic [ slot-id ] [ vlan vlan-id | vsi vsi-name | source-
slot source-slot-id | interface-type interface-number ] command.
l Run the display mac-address summary command to check statistic information about
MAC address entries.
----End
Example
Run the display mac-address command. If information about the MAC address, the outbound
interface corresponding to the MAC address, and the MAC address type is displayed, it means
that the configuration succeeds. For example:
<HUAWEI> display mac-address
--------------------------------------------------------------------------------
VSI/SI MAC-Tunnel
--------------------------------------------------------------------------------
0011-2233-4455 abc 1 - GE1/0/1.10 static 2/-
0002-0002-0002 2 - - GE2/0/1 static -
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
VSI/SI MAC-Tunnel
--------------------------------------------------------------------------------
0000-c102-0104 200 - - GE1/0/1 dynamic -
0000-c102-0105 200 - - GE1/0/1 dynamic -
0000-c102-0102 200 - - GE1/0/1 dynamic -
0000-c102-0106 200 - - GE1/0/1 dynamic -
0000-c102-0103 200 - - GE1/0/1 dynamic -
-------------------------------------------------------------------------------
Run the display mac-address summary command to display all the statistics of the MAC
address entries. Such as:
<HUAWEI> display mac-address summary
-------------------------------------------------------------
Slot Total Blackhole Static Dynamic Capacity FE
-------------------------------------------------------------
1 1 0 0 1 0 0
2 0 0 0 0 0 0
-------------------------------------------------------------
1.4 Configuring the Aging Time of a MAC Address Table

After the network topology changes, dynamic MAC address entries are not automatically
updated in time. As a result, a device cannot learn new MAC addresses and thus user traffic
cannot be normally forwarded. To addresses this problem, you need to configure the aging time


Before configuring the aging time of MAC address entries, familiarize yourself with the
applicable environment, complete the pre-configuration tasks, and obtain the required data. This
can help you complete the configuration task quickly and accurately.
After the network topology changes, dynamic MAC entries are not automatically updated in
time. In this case, user traffic cannot be normally forwarded because the device cannot learn the
new MAC address.
Thus, you need to configure the aging time of dynamic MAC addresses. When the set aging
time expires, dynamic MAC address entries are automatically deleted. The device re-learns
MAC addresses to generate a new dynamic MAC address type.
The aging time is valid only on dynamic MAC address entries.
The configurations in this section are optional.
None
Data Preparation
To configure the aging time of a MAC address table, you need the following data.
No. Data
1 Aging time
1.4.2 Setting the Aging Time of a MAC Address Table

After the aging time of MAC address entries is configured, the dynamic MAC address entries
are automatically deleted if the aging time expires.
Context
Do as follows on all the devices:
Procedure
Step 1 Run:
system-view

Step 2 Run:
mac-address aging-time seconds [ vlan { vlan-id1 [ to vlan-id2 ] } &<1-10> ]
The aging time of a MAC address table is set.

In a MAC address table, only dynamic entries age.
The aging time ranges from 60 to 1000000 seconds. The default is 300 seconds.
The aging time 0 means that no MAC address entry is aged.
----End

After the aging time of MAC address entries is successfully configured, you can view
information about the aging time of MAC address entries.
Prerequisite
The configurations of the aging time of a MAC address table are complete.
Procedure
Step 1 Run the display mac-address aging-time [ vlan [ vlanid ] ] command to check the aging time
----End
Example
Run the display mac-address aging-time command. If the aging time of MAC address entries
is displayed, it means that the configuration succeeds. For example:
<HUAWEI> display mac-address aging-time
Aging time: 300 seconds
<HUAWEI> display mac-address aging-time vlan 10
Vlan Aging Time(sec)
10 100
1.5 Maintaining MAC Address Table

This section provides commands used to maintain MAC address tables, including the command
that is used to delete dynamic MAC address tables.
1.5.1 Clearing the Dynamic MAC Address

The NE80E/40E provides two methods of deleting dynamic MAC addresses. You can either use
a command to delete dynamic MAC addresses or wait for the system to delete MAC entries that
have become invalid after interfaces go Down, VLANs are deleted, or VSIs are deleted. In
addition, the NE80E/40E supports the batch deletion of dynamic MAC addresses in a VLAN,
in a VSI, on an interface, on an interface of a VLAN, or on an interface of a VSI.
Context
After the network topology changes, the router's failure to learn new MAC addresses interrupts
the forwarding of user traffic if the dynamic MAC entries are not refreshed in time.
The router needs to provide various entry deletion methods to:

l Minimize the effect on normal services

l Promptly delete the invalid MAC entries
l Release MAC address resources
l Ensure the generation of new MAC entries
Procedure
l To delete the dynamic MAC entries based on a VLAN, run the undo mac-address
dynamic vlan vlan-id command.
l To delete the dynamic MAC entries based on a VSI, run the undo mac-address
dynamic vsi vsi-name command.
l To delete the dynamic MAC entries based on a port, run the undo mac-address
dynamic { ethernet | gigabitethernet | eth-trunk } interface-number command.
l To delete the dynamic MAC entries based on a port in a VLAN, run the undo mac-address
dynamic { ethernet | gigabitethernet | eth-trunk } interface-number vlan vlan-id
command.
l To delete the dynamic MAC entries based on a port and the VSI, run the undo mac-address
dynamic { ethernet | gigabitethernet | eth-trunk } interface-number vsi vsi-name
command.
----End

This section lists networking requirements, configuration roadmap, and data preparation to
describe the typical application scenarios of MAC address tables, and provides related
NOTE
This document takes interface numbers and link types of the NE40E-X8 as an example. In working
situations, the actual interface numbers and link types may be different from those used in this document.
1.6.1 Example for Configuring the MAC Address Table Based on

the Interface and VLAN
In this networking, the network administrator binds MAC addresses of user devices to the access
interface, which can prevent invalid users from accessing the network through other switching
devices.
Networking Requirements
A device learns source MAC addresses and then creates a MAC address table. MAC address
learning, however, cannot identify whether the packets are from legal users or hackers, which
brings security threats.
To improve interface security, a network administrator can manually add specific MAC address
entries to the MAC address table. The MAC addresses of user devices and interfaces are then
bound to prevent illegal users from obtaining data.
On the network shown in Figure 1-1, static MAC address entries can be configured to be bound
to interfaces, preventing attacks.

Figure 1-1 Networking diagram of configuring the MAC address table based on the interface
and VLAN
PE
GE1/0/1 GE1/0/2
GE1/0/2 GE1/0/2
CE1 CE2
GE1/0/1 GE1/0/1
PC1 PC2 PC3 PC4

VLAN 2 VLAN 2
Configuration Roadmap
The configuration roadmap is as follows:
1. Create a VLAN on each CE.
2. Configure interface attributes and associate each interface with the VLAN on each CE and
the PE.
3. Configure static MAC address entries on the PE, and bind them to interfaces.
Data Preparation
To complete the configuration, you need the following data:
l User VLAN ID
l MAC address of each CE
In this example, CE1's MAC address is 0011-2233-44aa, and CE2's MAC address is
0011-2233-44bb.
Procedure
Step 1 Create VLANs.
# Configure CE 1.
<HUAWEI> system-view
<HUAWEI> sysname CE1
[CE1] vlan 2
[CE1-vlan2] quit
# Configure CE 2.
<HUAWEI> sysname CE2
[CE2] vlan 2
[CE2-vlan2] quit

# Configure PE.
<HUAWEI> sysname PE
[PE] vlan 2
[PE-vlan2] quit
Step 2 Configure interface attributes and associate the interface to the VLAN.
# Configure CE 1.
[CE1] interface gigabitethernet 1/0/1
[CE1-GigabitEthernet1/0/1] undo shutdown
[CE1-GigabitEthernet1/0/1] portswitch
[CE1-GigabitEthernet1/0/1] port link-type access
[CE1-GigabitEthernet1/0/1] port default vlan 2
[CE1-GigabitEthernet1/0/1] quit
[CE1-GigabitEthernet1/0/2] port link-type trunk
[CE1-GigabitEthernet1/0/2] port trunk allow-pass vlan 2
# Configure CE 2.
# Configure PE.
[PE] interface gigabitethernet 1/0/1
[PE-GigabitEthernet1/0/1] undo shutdown
[PE-GigabitEthernet1/0/1] portswitch
[PE-GigabitEthernet1/0/1] port link-type trunk
[PE-GigabitEthernet1/0/1] port trunk allow-pass vlan 2
[PE-GigabitEthernet1/0/1] quit
Step 3 Configure static MAC address entries.

[PE] mac-address static 0011-2233-44aa gigabitethernet 1/0/1 vlan 2
[PE] mac-address static 0011-2233-44bb gigabitethernet 1/0/2 vlan 2
Step 4 Verify the configuration.

# After completing the preceding configurations, run the display mac-address static command
on the PE. The configured static MAC address entries are displayed.
[PE] display mac-address static
-------------------------------------------------------------------------------
VSI/SI MAC-Tunnel
-------------------------------------------------------------------------------

0011-2233-44aa 2 - - GE1/0/1 static -

0011-2233-44bb 2 - - GE1/0/2 static -
-------------------------------------------------------------------------------
----End
Configuration Files
l Configuration file of CE1
#
sysname CE1
#
vlan batch 2
#
interface GigabitEthernet1/0/1
portswitch
undo shutdown
port link-type access
port default vlan 2
#
portswitch
undo shutdown
port link-type trunk
port trunk allow-pass vlan 2
#
return
l Configuration file of PE2

#
sysname CE2
#
vlan batch 2
#
portswitch
undo shutdown
port default vlan 2
#
portswitch
undo shutdown
#
return
l Configuration file of PE
#
sysname PE
#
vlan batch 2
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#

mac-address static 0011-2233-44aa GigabitEthernet1/0/1 vlan 2

mac-address static 0011-2233-44bb GigabitEthernet1/0/2 vlan 2
#
return

the dot1q Termination Sub-interface and VSI
In a VPLS network, MAC address learning is performed on PEs. A PE automatically sets up a
MAC address table by learning the MAC address of the remote PE through a Pseudo-Wire (PW),
and learning the MAC address of the directly connected CE through an AC. When a PE receives
a user packet with one tag, you need to bind the Dot1q termination sub-interface on the PE to a
VSI to access the VPLS network, and bind the MAC address of the packet to the VSI. This helps
to prevent invalid users from accessing the VPLS network.
As shown in Figure 1-2, in a VPLS networking, PEs are connected to CEs through dot1q
termination sub-interfaces.
On PE1, set the user who accesses PE1 through CE1 and whose MAC address is 0011-2233-4455
as a static MAC entry. This helps to prevent invalid users from accessing the VPLS network.
Figure 1-2 Networking diagram of configuring the MAC address table based on the dot1q
termination sub-interface and VSI
Loopback1 Loopback1 Loopback1
1.1.1.9/32 2.2.2.9/32 3.3.3.9/32
POS2/0/0 POS1/0/0
PE1 192.168.1.1/30 192.168.2.2/30
PE2
POS1/0/0 POS2/0/0
GE1/0/0.1 192.168.1.2/30 P 192.168.2.1/30 GE2/0/0.1
GE1/0/2 GE1/0/2
GE1/0/1 CE1 CE2 GE1/0/1
MAC:0011-2233-4455
PC1 PC2
1. Configure a VPLS network.

2. Bind the dot1q termination sub-interface to the VSI

3. Configure static MAC address entries.
Data Preparation
l MAC address of the user: 0011-2233-4455
l VSI named ldp1
Procedure
Step 1 Configure IGP on the MPLS backbone network. OSPF is used in this example.
According to Figure 1-2 configure the addresses for the interfaces on PE and P. Configure OSPF
to advertise the addresses of the loopback interfaces on PE1, P, and PE2.
# Configure PE1.
[HUAWEI] sysname PE1
[PE1] interface loopback 1
[PE1-LoopBack1] ip address 1.1.1.9 32
[PE1-LoopBack1] quit
[PE1] interface pos 2/0/0
[PE1-Pos2/0/0] ip address 192.168.1.1 30
[PE1-Pos2/0/0] undo shutdown
[PE1-Pos2/0/0] quit
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1-area-0.0.0.0] network 1.1.1.9 0.0.0.0
[PE1-ospf-1-area-0.0.0.0] quit
[PE1-ospf-1] quit
# Configure P.
[HUAWEI] sysname P
[P] interface loopback 1
[P-LoopBack1] ip address 2.2.2.9 32
[P-LoopBack1] quit
[P] interface pos 1/0/0
[P-Pos1/0/0] ip address 192.168.1.2 30
[P-Pos1/0/0] undo shutdown
[P-Pos1/0/0] quit
[P-Pos2/0/0] ip address 192.168.2.1 30
[P-Pos2/0/0] quit
[P] ospf
[P-ospf-1] area 0
[P-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0
[P-ospf-1-area-0.0.0.0] quit
[P-ospf-1] quit
# Configure PE2.
[PE2-Pos1/0/0] ip address 192.168.2.2 30


[PE2-Pos1/0/0] quit
[PE21] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
After this step, PE1 and PE2 learn the route to the loopback interface of the peer through the
OSPF protocol. PE1 and PE2 can ping through each other.
Take the display on PE1 as an example:

[PE1] display ip routing-table
Route Flags: R - relied, D - download to fib
------------------------------------------------------------------------------
Routing Tables: Public
Destinations : 9 Routes : 9
Destination/Mask Proto Pre Cost Flags NextHop Interface
1.1.1.9/32 Direct 0 0 D 127.0.0.1
InLoopBack0
2.2.2.9/32 OSPF 10 2 D 192.168.1.2 Pos1/0/0
3.3.3.9/32 OSPF 10 3 D 192.168.1.2 Pos1/0/0
192.168.1.0/24 Direct 0 0 D 192.168.1.1 Pos2/0/0
192.168.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0
192.168.1.2/32 Direct 0 0 D 192.168.1.2 Pos1/0/0
192.168.2.0/24 OSPF 10 2 D 192.168.1.2 Pos1/0/0
[PE1] ping 192.168.2.2
PING 192.168.2.2: 56 data bytes, press CTRL_C to break
Reply from 192.168.2.2: bytes=56 Sequence=1 ttl=254 time=200 ms
--- 192.168.2.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 60/106/200 ms
Step 2 Enable the basic MPLS capabilities and LDP on the MPLS backbone network.
# Configure PE1.
[PE1] mpls lsr-id 1.1.1.9
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
[PE1-Pos2/0/0] mpls
[PE1-Pos2/0/0] mpls ldp
[PE1-Pos2/0/0] quit
# Configure P.
[P] mpls lsr-id 2.2.2.9
[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
[P-Pos1/0/0] mpls
[P-Pos1/0/0] mpls ldp
[P-Pos1/0/0] quit

[P-Pos2/0/0] mpls
[P-Pos2/0/0] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2-Pos1/0/0] mpls
[PE2-Pos1/0/0] quit
Step 3 Set up the remote LDP session between PEs.

# Configure PE1.
[PE1] mpls ldp remote-peer 3.3.3.9
[PE1-mpls-ldp-remote-3.3.3.9] remote-ip 3.3.3.9
[PE1-mpls-ldp-remote-3.3.3.9] quit
# Configure PE2.
After the configuration, the sessions between PE1 and PE2 are set up. Running the display mpls
ldp sessioncommand, you can view that the Status field is "Operational".
For example, the following displays the session information on PE1:
[PE1] display mpls ldp session
LDP Session(s) in Public Network
------------------------------------------------------------------------------
Peer-ID Status LAM SsnRole SsnAge KA-Sent/Rcv
------------------------------------------------------------------------------
2.2.2.9:0 Operational DU Passive 000:00:04 18/18
------------------------------------------------------------------------------
TOTAL: 2 session(s) Found.
LAM : Label Advertisement Mode SsnAge Unit : DDD:HH:MM
Step 4 Enable MPLS L2VPN on PEs.

# Configure PE1.
[PE1] mpls l2vpn
# Configure PE2.
[PE2] mpls l2vpn
Step 5 Create VSIs and specify LDP as the signaling protocol on VSIs.
# Configure PE1.
[PE1] vsi ldp1 static
[PE1-vsi-ldp1] pwsignal ldp
[PE1-vsi-ldp1-ldq] vsi-id 1
[PE1-vsi-ldp1-ldq] peer 3.3.3.9
[PE1-vsi-ldp1-ldq] quit
[PE1-vsi-ldp1] quit
# Configure PE2.


[PE2-vsi-ldp1] quit
Step 6 Configure the interface mode to user termination.

# Configure PE1.
[PE1] interface gigabitethernet 1/0/0
[PE1-GigabitEthernet1/0/0] mode user-termination
[PE1-GigabitEthernet1/0/0] undo shutdown
[PE1-GigabitEthernet1/0/0] quit
# Configure PE2.
Step 7 Configure the sub-interface for dot1q VLAN tag termination and bind VSIs and AC interfaces.
# Configure PE1.
[PE1] interface gigabitethernet 1/0/0.1
[PE1-GigabitEthernet1/0/0.1] control-vid 1 dot1q-termination
[PE1-GigabitEthernet1/0/0.1] dot1q termination vid 10
[PE1-GigabitEthernet1/0/0.1] l2 binding vsi ldp1
[PE1-GigabitEthernet1/0/0.1] undo shutdown
[PE1-GigabitEthernet1/0/0.1] quit
# Configure PE2.
NOTE
On different sub-interfaces, the vid values cannot overlap.
Step 8 Configure the Layer 2 forwarding function.

# Configure CE1.
[HUAWEI] sysname CE1
[CE1]interface gigabitethernet 1/0/1
[CE1] vlan 10
[CE1-vlan10] port gigabitethernet 1/0/1
[CE1-vlan10] quit
# Configure CE2.

[CE2] vlan 10
[CE2-vlan10] port gigabitethernet 1/0/1
[CE2-vlan10] quit
Step 9 Configure the MAC address table based on the dot1q termination sub-interface and VSI.
[PE1] mac-address static 0011-2233-4455 gigabitethernet 1/0/0.1 vsi ldp1 pe-vid 10

# After completing the preceding configurations, run the display mac-address static command
on the PE1. The configured static MAC address entries are displayed.
[PE1] display mac-address static
--------------------------------------------------------------------------------
MAC Address VLAN/ PEVLAN CEVLAN Port Type LSP/LSR-
ID
VSI/SI MAC-Tunnel
--------------------------------------------------------------------------------
0011-2233-4455 ldp1 10 - GE1/0/0.1 static -
--------------------------------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 3.3.3.9
#
mpls ldp remote-peer 3.3.3.9
remote-ip 3.3.3.9
#
mpls ldp
#
undo shutdown
mode user-termination
#
interface GigabitEthernet1/0/0.1
undo shutdown
control-vid 1 dot1q-termination
dot1q termination vid 10
l2 binding vsi ldp1
#
interface Pos2/0/0
undo shutdown
ip address 192.168.1.1 255.255.255.252
mpls

mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 192.168.1.0 0.0.0.3
#
mac-address static 0011-2233-4455 gigabitethernet 1/0/0.1 vsi ldp1 pe-vid 10
#
return
l Configuration file of P
#
sysname P
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
interface Pos1/0/0
undo shutdown
ip address 192.168.1.2 255.255.255.252
mpls
mpls ldp
#
interface Pos2/0/0
undo shutdown
ip address 192.1168.2.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 192.168.1.0 0.0.0.3
network 192.168.2.0 0.0.0.3
#
return
#
sysname PE2
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.9
#
remote-ip 1.1.1.9
#
mpls ldp
#
undo shutdown
#

undo shutdown
l2 binding vsi ldp1
#
interface Pos1/0/0
undo shutdown
ip address 192.168.2.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 192.168.2.0 0.0.0.3
#
return

#
sysname CE1
#
vlan batch 10
#
portswitch
undo shutdown
port default vlan 10
#
portswitch
undo shutdown
#
return

#
sysname CE2
#
vlan batch 10
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#
return

the QinQ Termination Sub-interface and VSI
In a VPLS network, MAC address learning is performed on PEs. A PE automatically sets up a
MAC address table by learning the MAC address of the remote PE through a PW, and learning
the MAC address of the directly connected CE through an AC. When a PE receives a user packet
with double tags, you need to bind the QinQ termination sub-interface on the PE to a VSI, connect
the sub-interface to the VPLS network, and bind the MAC address of the packet to the VSI. This
helps to prevent invalid users from connecting to the VPLS network.

As shown in Figure 1-3, in a VPLS networking, PEs are connected to CEs through QinQ
termination sub-interfaces.
as a static MAC entry.
Figure 1-3 Networking diagram of configuring the MAC address table based on the qinq
termination sub-interface and VSI
1.1.1.9/32 2.2.2.9/32 3.3.3.9/32
POS2/0/0 POS1/0/0
192.168.1.1/30 192.168.2.2/30
PE1 PE2
POS1/0/0 POS2/0/0
GE1/0/0.1 192.168.1.2/30 P 192.168.2.1/30 GE2/0/0.1
GE1/0/2 GE1/0/2
GE1/0/1 Switch1 GE1/0/1 Switch2

GE1/0/1.1 GE1/0/1.1
10.1.1.1/24 10.1.1.2
CE1 CE2
PC1 PC2
MAC:0011-2233-4455
2. Bind the QinQ termination sub-interface to the VSI
Data Preparation
l MAC address of the user: 0011-2233-4455
l VSI named ldp1
Procedure

# Configure PE1.
[PE1-Pos2/0/0] ip address 192.168.1.1 30
[PE1-Pos2/0/0] quit
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure P.
[HUAWEI] sysname P
[P-LoopBack1] quit
[P-Pos1/0/0] ip address 192.168.1.2 30
[P-Pos1/0/0] quit
[P-Pos2/0/0] ip address 192.168.2.1 30
[P-Pos2/0/0] quit
[P] ospf
[P-ospf-1] area 0
[P-ospf-1] quit
# Configure PE2.
[PE2-Pos1/0/0] ip address 192.168.2.2 30
[PE2-Pos1/0/0] quit
[PE21] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit

------------------------------------------------------------------------------


1.1.1.9/32 Direct 0 0 D 127.0.0.1
InLoopBack0
2.2.2.9/32 OSPF 10 2 D 192.168.1.2 Pos1/0/0
3.3.3.9/32 OSPF 10 3 D 192.168.1.2 Pos1/0/0
192.168.1.0/24 Direct 0 0 D 192.168.1.1 Pos2/0/0
192.168.1.2/32 Direct 0 0 D 192.168.1.2 Pos1/0/0
192.168.2.0/24 OSPF 10 2 D 192.168.1.2 Pos1/0/0
[PE1] ping 192.168.2.2
0.00% packet loss
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
[PE1-Pos2/0/0] mpls
[PE1-Pos2/0/0] quit
# Configure P.
[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
[P-Pos1/0/0] mpls
[P-Pos1/0/0] quit
[P-Pos2/0/0] mpls
[P-Pos2/0/0] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2-Pos1/0/0] mpls
[PE2-Pos1/0/0] quit
# Configure PE1.


# Configure PE2.
ldp session command, you can view that the Status field is "Operational".
------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------

# Configure PE1.
[PE1] mpls l2vpn
# Configure PE2.
[PE2] mpls l2vpn

# Configure PE1.
# Configure PE2.
# Configure PE1.
[PE1-vsi-ldp1] quit
# Configure PE12.

[PE2-vsi-ldp1] quit
Step 7 Configure the sub-interface for qinq VLAN tag termination and bind VSIs and AC interfaces.
# Configure PE1.
[PE1-GigabitEthernet1/0/0.1] control-vid 1 qinq-termination
[PE1-GigabitEthernet1/0/0.1] qinq termination l2 symmetry
[PE1-GigabitEthernet1/0/0.1] qinq termination pe-vid 100 ce-vid 10
# Configure PE21.
NOTE
When the qinq termination command is used, the ranges of ce-vid cannot overlap if pe-vid of two sub-
interfaces is the same.
Step 8 Configure QinQ and set the packets sent from the switch to the PE to carry double tags.
# Configure CE1.
[CE1]vlan batch 100 to 200
[CE1]interface gigabitethernet 1/0/1.1
[CE1-GigabitEthernet1/0/1.1] undo shutdown
[CE1-GigabitEthernet1/0/1.1] ip address 10.1.1.1 24
[CE1-GigabitEthernet1/0/1.1] vlan-type dot1q 100 200
[CE1-GigabitEthernet1/0/1.1] quit
# Configure CE2.
[CE2]vlan batch 100 to 200
[CE2]interface gigabitethernet 1/0/1.1
[CE2-GigabitEthernet1/0/1.1] vlan-type dot1q 100 200
# Configure Switch 1.
[HUAWEI] sysname Switch1
[Switch1]interface gigabitethernet 1/0/1
[Switch1-GigabitEthernet1/0/1] portswitch
[Switch1-GigabitEthernet1/0/1] undo shutdown
[Switch1-GigabitEthernet1/0/1] port trunk allow-pass vlan 10
[Switch1-GigabitEthernet1/0/1] quit
[Switch1-GigabitEthernet1/0/2] port vlan-stacking vlan 100 to 200 stack-vlan 10

[Switch2-GigabitEthernet1/0/2] port vlan-stacking outside-vlan 100 to 200 stack-
vlan 10
NOTE
If the device does not support the port vlan-stacking command, you can run the commands port link-
type dot1q-tunnel and port default vlan to configure QinQ.
Step 9 Configure the MAC address table based on the qinq termination sub-interface and VSI.
[PE1] mac-address static 0011-2233-4455 gigabitethernet 1/0/0.1 vsi ldp1 pe-vid 10
ce-vid 100

# View the static MAC address table.
--------------------------------------------------------------------------------
ID
VSI/SI MAC-Tunnel
--------------------------------------------------------------------------------
0011-2233-4455 ldp1 10 100 GE1/0/0.1 static -
--------------------------------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 3.3.3.9
#
remote-ip 3.3.3.9
#
mpls ldp
#
undo shutdown
#
control-vid 1 qinq-termination
qinq termination l2 symmetry

qinq termination pe-vid 10 ce-vid 100 to 200

l2 binding vsi ldp1
#
interface Pos2/0/0
undo shutdown
ip address 192.168.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 192.168.1.0 0.0.0.3
#
mac-address static 0011-2233-4455 gigabitethernet 1/0/0.1 vsi ldp1 pe-vid 10
ce-vid 100
#
return
#
sysname P
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
interface Pos1/0/0
undo shutdown
ip address 192.168.1.2 255.255.255.252
mpls
mpls ldp
#
interface Pos2/0/0
undo shutdown
ip address 192.1168.2.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 192.168.1.0 0.0.0.3
network 192.168.2.0 0.0.0.3
#
return
#
sysname PE2
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.9
#
remote-ip 1.1.1.9

#
mpls ldp
#
undo shutdown
#
l2 binding vsi ldp1
#
interface Pos1/0/0
undo shutdown
ip address 192.168.2.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 192.168.2.0 0.0.0.3
#
return
l Configuration file of Switch1
#
sysname Switch1
#
vlan batch 10
#
portswitch
undo shutdown
#
portswitch
undo shutdown
port vlan-stacking vlan 100 to 200 stack-vlan 10
#
return
#
sysname Switch2
#
vlan batch 10
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#
return
#
sysname CE1
#
vlan batch 100 to 200

#
vlan-type dot1q 100 200
ip address 10.1.1.1 255.255.255.0
#
return

#
sysname CE2
#
#
vlan-type dot1q 100 200
ip address 10.1.1.2 255.255.255.0
#
return

the VLANIF Interface and VSI
In this networking, Layer 2 switches function as PEs accessing the VPLS network. To enable
the packets from PEs to be transmitted on the VPLS network, you need to configure VLANIF
interfaces, bind the VLANIF interfaces to VSIs, connect the VLANIF interfaces to the VPLS
network, and bind the MAC addresses of the user packets to the VSIs. This helps to prevent
invalid users from connecting to the VPLS network.
As shown in Figure 1-4, in a VPLS networking, PEs are connected to CEs through a VLANIF
interface.
as a static MAC entry.
Figure 1-4 Networking diagram of configuring the MAC address table based on the VLANIF
interface and VSI
1.1.1.9/32 2.2.2.9/32 3.3.3.9/32
POS2/0/0 POS1/0/0
192.168.1.1/30 192.168.2.2/30
PE1 PE2
POS1/0/0 POS2/0/0
GE1/0/1 192.168.1.2/30 P 192.168.2.1/30 GE2/0/0
VLANIF10 VLANIF10
GE1/0/2 GE1/0/2
GE1/0/1 CE1 GE1/0/1 CE2
MAC:0011-2233-4455
PC1 PC2

2. Configure a VLAN and create a VLANIF interface.
3. Bind the VLANIF interface to the VSI.
Data Preparation
l MAC address of the user PC1
l GE 1/0/1, an interface in VLAN 10
l VLANIF 10, an interface on PE1
l VSI named abc
Procedure
# Configure PE1.
[PE1-Pos2/0/0] ip address 192.168.1.1 30
[PE1-Pos2/0/0] quit
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure P.
[HUAWEI] sysname P
[P-LoopBack1] quit
[P-Pos1/0/0] ip address 192.168.1.2 30
[P-Pos1/0/0] quit
[P-Pos2/0/0] ip address 192.168.2.1 30
[P-Pos2/0/0] quit

[P] ospf
[P-ospf-1] area 0
[P-ospf-1] quit
# Configure PE2.
[PE2-Pos1/0/0] ip address 192.168.2.2 30
[PE2-Pos1/0/0] quit
[PE21] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit

Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------

2.2.2.9/32 OSPF 10 1 D 192.168.1.2 Pos2/0/0
3.3.3.9/32 OSPF 10 2 D 192.168.1.2 Pos2/0/0
192.168.1.0/30 Direct 0 0 D 192.168.1.1 Pos2/0/0
192.168.1.2/32 Direct 0 0 D 192.168.1.2 Pos2/0/0
192.168.2.0/30 OSPF 10 2 D 192.168.1.2 Pos2/0/0
[PE1] ping 192.168.2.2

0.00% packet loss
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit

[PE1] mpls ldp

[PE1-mpls-ldp] quit
[PE1-Pos2/0/0] mpls
[PE1-Pos2/0/0] quit
# Configure P.
[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
[P-Pos1/0/0] mpls
[P-Pos1/0/0] quit
[P-Pos2/0/0] mpls
[P-Pos2/0/0] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2-Pos1/0/0] mpls
[PE2-Pos1/0/0] quit

# Configure PE1.
# Configure PE2.
ldp session command, you can view that the Status field is "Operational".

Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
A '*' before a session means the session is being deleted.
------------------------------------------------------------------------------
PeerID Status LAM SsnRole SsnAge KASent/Rcv
------------------------------------------------------------------------------
------------------------------------------------------------------------------

# Configure PE1.
[PE1] mpls l2vpn

[PE1-l2vpn] quit
# Configure PE2.
[PE2] mpls l2vpn
[PE2-l2vpn] quit
# Configure PE1.
[PE1-vsi-ldp1] quit
# Configure PE2.
[PE2-vsi-ldp1] quit
Step 6 # Create VLANIF 10 and bind it to the VSI.

# Configure PE1.
[PE1] vlan 10
[PE1-vlan10] quit
[PE1-GigabitEthernet1/0/1] portswitch
[PE1-GigabitEthernet1/0/1] port default vlan 10
[PE1] interface vlanif 10
[PE1-Vlanif10] l2 binding vsi ldp1
[PE1-Vlanif10] quit
# Configure PE2.
[PE2] vlan 10
[PE2-vlan10] quit
[PE2] interface vlanif 10
[PE2-Vlanif10] l2 binding vsi ldp1
[PE2-Vlanif10] quit
After the preceding configuration, run the display vsi name ldp1 verbose command on PE1.
you can find that PWs to PE2 and PE3 are set up on the VSI named ldp1. The VSI status is Up.
[PE1] display vsi name ldp1 verbose
***VSI Name : ldp1

Administrator VSI : no
Isolate Spoken : disable
VSI Index : 0
PW Signaling : ldp
Member Discovery Style : static
PW MAC Learn Style : unqualify

Encapsulation Type : vlan

MTU : 1500
Diffserv Mode : uniform
Service Class : --
Color : --
DomainId : 255
Domain Name :
Ignore AcState : disable
Create Time : 0 days, 0 hours, 3 minutes, 48 seconds
VSI State : up
VSI ID : 1
*Peer Router ID : 3.3.3.9
VC Label : 1026
Peer Type : dynamic
Session : up
Tunnel ID : 0x1000005
Broadcast Tunnel ID : 0x1000005
CKey : 2
NKey : 1
StpEnable : 0
PwIndex : 0
Interface Name : Vlanif10

State : up
Last Up Time : 2010/05/06 19:15:24
Total Up Time : 0 days, 0 hours, 0 minutes, 33 seconds
**PW Information:
*Peer Ip Address : 3.3.3.9

PW State : up
Local VC Label : 1026
Remote VC Label : 1026
PW Type : label
Ckey : 0x2
Nkey : 0x1
Main PW Token : 0x1000005
Slave PW Token : 0x0
Tnl Type : LSP
OutInterface : Pos2/0/0
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2010/05/06 19:15:24
PW Total Up Time : 0 days, 0 hours, 0 minutes, 17 seconds
Step 7 Configure a MAC address table based on VLANIF 10 and VSI.

[PE1] mac-address static 0011-2233-4455 gigabitethernet 1/0/1 vlanif 10 vsi ldp1
Step 8 Configure the basic Layer 2 forwarding function on CEs.
# Configure CE1.
[CE1]vlan 10
[CE1-vlan10] quit

# Configure CE2.
[CE2]vlan 10
[CE2-vlan10] quit

# View the static MAC address table.
-------------------------------------------------------------------------------
VSI/SI MAC-Tunnel
-------------------------------------------------------------------------------
0011-2233-4455 ldp1 10 - GE1/0/1 static -
-------------------------------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
vlan batch 10
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 3.3.3.9
#
mpls ldp
#
remote-ip 3.3.3.9
undo remote-ip pwe3
#
interface Vlanif10
l2 binding vsi ldp1
#
portswitch
undo shutdown
#
interface Pos2/0/0
link-protocol ppp

ip address 192.168.1.1 255.255.255.252

mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 192.168.1.0 0.0.0.3
#
mac-address static 0011-2233-4455 GigabitEthernet1/0/1 Vlanif10 vsi ldp1
#
return
#
sysname P
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
interface Pos1/0/0
link-protocol ppp
ip address 192.168.1.2 255.255.255.252
mpls
mpls ldp
#
interface Pos2/0/0
link-protocol ppp
ip address 192.168.2.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 192.168.1.0 0.0.0.3
network 192.168.2.0 0.0.0.3
#
return
#
sysname PE2
#
vlan batch 10
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.9
#
mpls ldp
#
remote-ip 1.1.1.9
undo remote-ip pwe3
#

interface Vlanif10
l2 binding vsi ldp1
#
portswitch
undo shutdown
#
interface Pos1/0/0
link-protocol ppp
ip address 192.168.2.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 192.168.2.0 0.0.0.3
#
return

#
sysname CE1
#
vlan batch 10
#
portswitch
#
portswitch
undo shutdown
#
return

#
sysname CE2
#
vlan batch 10
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#
return

the VLAN and Layer 2 VE Interface
In this networking, the outbound interfaces in the MAC address table are VE interfaces. Before
you configure a MAC address table based on Layer 2 VE interfaces and VLANs, the Layer 2
VE interfaces must have already been added to the specified VLANs, and the mappings between
the VE interfaces and the PVCs on ATM interfaces must be configured.

NOTE
NOTE
MAC address entries based on the VE interface can be configured only on the ATM interfaces of the ATM
flexible plug-in card.
As shown in Figure 1-5, the hosts in two Ethernet networks are connected to the Digital
Subscriber Line Access Multiplexer (DSLAM) through Router ADSL and access the ATM
network through Router C.
The specific networking is as follows:
l The VE interface on Router C is added to VLAN 100.

l Configure an IP address for VLANIF 100 that acts as a gateway.
l The virtual path identifiers (VPIs) or virtual channel identifiers (VCIs) of the two PVCs
through which Router C is connected to the DSLAM are 0/60 and 0/61 respectively. The
two PVCs are connected to ADSL Router A and ADSL Router B respectively.
Workstation A accesses Router C in ATM 1483B mode. On Router C, configure the MAC
address entry of workstation A to be the static MAC address entry. In this manner, the MAC
address entry of workstation A cannot be aged.
Figure 1-5 Networking diagram of configuring the MAC address table based on the VLAN and
Layer 2 VE interface
workstation A
MAC:00e0-3344-5566
ADSL router A
workstation B
Ethernet
DSLAM
server
router C
workstation C To ADSL router A:0/60
Ethernet
To ADSL router B:0/61

Interface:Virtual-ethernet1/0/0
ADSL router B
server
1. Create a VE interface and switch it to a Layer 2 interface.

2. Create a VLAN and add the VE interface to the VLAN.

3. Enter the ATM interface and create PVCs.

4. Establish the mapping between the PVC and VE interface.
Data Preparation
l MAC address of workstation A: 00e0-3344-5566

l VLAN ID of 100
l VE 1/0/0
l ATM 1/0/0
l PVC named to_adsl_a
l VPI/VCI of the PVC network: 0/60 and 0/61
Procedure
Step 1 Create VE 1/0/0 and switch it to a Layer 2 interface.
[HUAWEI] sysname Router C
[Router C] interface virtual-ethernet 1/0/0
[Router C-Virtual-Ethernet1/0/0] undo shutdown
[Router C-Virtual-Ethernet1/0/0] portswitch
[Router C-Virtual-Ethernet1/0/0] quit
Step 2 Create VLAN 100 and add VE 1/0/0 to VLAN 100.

[Router C] vlan 100
[Router C-vlan100] port virtual-ethernet 1/0/0
[Router C-vlan100] quit
Step 3 Create a PVC and associate the VPI/VCI of 0/60 in the ATM network with VE 1/0/0.
[Router C] interface atm 1/0/0
[Router C-Atm1/0/0] undo shutdown
[Router C-Atm1/0/0] pvc to_adsl_a 0/60
[Router C-atm-pvc-Atm1/0/0-0/60-to_adsl_a] map bridge virtual-ethernet 1/0/0
[Router C-atm-pvc-Atm1/0/0-0/60-to_adsl_a] quit
[Router C-Atm1/0/0] quit

[Router C] mac-address static 00e0-3344-5566 virtual-ethernet 1/0/0 atm 1/0/0 pvc
to_adsl_a 0/60 vlan 100
Run the display mac-address static command. If information about MAC address entries is
displayed, it means that the configuration succeeds. For example:
<Router C> display mac-address static
ID
VSI/SI MAC-
Tunnel
---------------------------------------------------------------------------------
00e0-3344-5566 100 - - VE1/0/0 static -
Total matching items displayed = 1
----End

Configuration Files
#
sysname Router C
#
vlan batch 100
#
interface Atm1/0/0
undo shutdown
pvc to_adsl_a 0/60
map bridge Virtual-Ethernet1/0/0
#
interface Virtual-Ethernet1/0/0
undo shutdown
portswitch
#
mac-address static 00e0-3344-5566 Virtual-Ethernet1/0/0 Atm1/0/0 pvc 0/60 vlan 100
return

the Interface and VSI
You can configure a static MAC address table based on an interface of a VSI and set the aging
time for dynamic MAC entries.
For an existing user, MAC address is 0011-2233-4455, VSI name is vsi2 and the port is GE
1/0/0.
Set this entry as static to prevent it from aging and set the aging time of other dynamic entries
as 500 seconds.
1. Create a VSI, and then configure port to join the VSI.

2. Configure the static address entry.
3. Configure the aging time.
Data Preparation
l MAC address: 0011-2233-4455

l VSI name and the interface
l Aging time
Procedure
Step 1 Create vsi2 and configure interface GE 1/0/0 to join the vsi.

[HUAWEI] mac-address static 0011-2233-4455 gigabitethernet 1/0/0 vsi2

Step 3 Set the aging time of dynamic entries to 500 seconds.

[HUAWEI] mac-address aging-time 500

# View the aging time of the dynamic MAC address table.
[HUAWEI] display mac-address aging-time
Aging time: 500 seconds
----End
Configuration Files
#
sysname HUAWEI
#
mac-address aging-time 500
#
mac-address static 0011-2233-4455 GigabitEthernet1/0/0 vsi 2
#
return

Configuration Guide - LAN Access and MAN Access 2 Ethernet Interface Configuration
2 Ethernet Interface Configuration
About This Chapter
Being flexible, simple, and easy to implement, the Ethernet becomes the most important LAN
networking technology.
2.1 Ethernet Interface Introduction

Ehthernet interfaces include traditional Ethernet interfaces, Fast Ethernet (FE) interfaces, and
Gigabit Ethernet (GE) interfaces.
2.2 Configuring Ethernet Interfaces of the Interface Board
You can configure Ethernet interfaces on the Interface Boards to ensure correct physical
connections between NE80E/40Es.
2.3 Configuring Ethernet Interfaces of the SRU
By configuring an Ethernet interface on an MPU, you can connect the NE80E/40E to a network
management system (NMS) for management.
2.4 Configuring Ethernet Interfaces Layer 2 Parameters
After an Ethernet interface is configured with Layer 2 attributes, it can access a device or directly
forward Ethernet frames on a Layer 2 network. Layer 2 attributes define link layer information
of Ethernet interfaces.
2.5 Configuring SmartLink Flush Function
Some Layer 2 devices in the network support the Smart Link function. By default, Huawei data
communication devices do not process the SmartLink flush packets sent from these Layer 2
devices. To enable the communication between the Huawei devices and the devices of other
vendors, you need to configure the SmartLink Flush function on Huawei data communication
devices.
2.6 Maintaining Ethernet Interfaces
The commands related to Ethernet interfaces can be used to locate the faults on an Ethernet
interface.
This section lists the networking requirements, configuration roadmap, and data preparation to
describe the typical application scenarios of Ethernet interfaces, and provides related

2.1 Ethernet Interface Introduction

Ehthernet interfaces include traditional Ethernet interfaces, Fast Ethernet (FE) interfaces, and
Gigabit Ethernet (GE) interfaces.
2.1.1 Introduction to Ethernet Interfaces

There are two types of Ethernet interfaces, namely, Fast Ethernet (FE) interfaces and Gigabit
Ethernet (GE) interfaces. Ethernet interfaces support both the half duplex mode and the full
duplex mode and can work in auto-negotiation mode.
The Ethernet is one of the most important types of Local Area Network (LAN).
The Ethernet is flexible, simple, and easy to be deployed. Therefore, it is the most important
LAN networking technology.
The interface board of the NE80E/40E supports the Ethernet interfaces such as the 10M/100M/
1000M auto-sense Ethernet electrical interface, 100M Ethernet optical interface, GE optical
interface, GE/FE optical/electrical interface, 10GE optical interface (LAN), and 10GE optical
interface (WAN).
MPU/SRU supports the 10M/100M/1000M auto-sense Ethernet electrical interface.
l Traditional Ethernet interface: It complies with 10Base-T specifications, and can work at
the speed of 10 Mbit/s.
l Fast Ethernet (FE) interface: It complies with 100Base-TX specifications and is compatible
with 10Base-T specifications.
l Gigabit Ethernet (GE) interface: It complies with 1000Base-TX specifications, and is
compatible with 10Base-T and 100Base-TX specifications.
The GE/FE optical/electrical interface has the following functions:
l Provides the functions of a GE optical interface by the GE optical module plugged into the
interface.
l Provides the functions of an FE optical interface by the FE optical module plugged into the
interface.
l Provides the functions of a 10M/100M/1000M auto-sensing electrical interface by the
electrical module plugged into the interface.
Ethernet electrical interfaces can work in either the full-duplex mode or the half-duplex mode.
They support auto-negotiation. In the auto-negotiation mode, they negotiate with other network
devices for the most suitable working mode and speed. This simplifies system configuration and
management.
NOTE
This chapter explains the configuration of the FE and GE interfaces. The configuration of traditional
Ethernet interface is simple and similar to that of the fast Ethernet interface.
2.1.2 Features of Ethernet Interfaces Supported by the NE80E/40E

In a LAN, an Ethernet interface can transmit Layer 2 and Layer 3 services according to different
interface attributes. An Ethernet interface has both Layer 2 and Layer 3 attributes.

Ethernet Sub-interface
You can create the sub-interface on an Ethernet main interface. LAN interfaces that can be
configured with sub-interfaces include the following types:
l Ethernet interfaces
l GE interfaces
l Eth-Trunk interfaces
The NE80E/40E supports the configuration of sub-interfaces on both the Layer 3 Ethernet
interface and the Layer 2 Ethernet interface. After Ethernet sub-interfaces are encapsulated with
802.1Q and associated with the VLAN, the VLAN can communicate with devices out of the
VLAN through Ethernet sub-interface. An Ethernet sub-interface can associate with one VLAN.
The Ethernet sub-interface is also applied to dot1q termination and QinQ termination mode. For
details about the principle, see the chapter QinQ Configuration.
Besides the preceding applications, the Layer 2 Ethernet sub-interface can transmit the Layer 2
and Layer 3 services simultaneously on one physical link. As shown in Figure 2-1, the Universal
Media Gateway (UMG) is dual-homed to two PEs. PE1 and PE2 run VRRP. A layer 2 link is
required between PE1 and PE2 to prevent the route change when the UMG active/standby
switchover is performed.
At the same time, the TE tunnel is required between PE1 and remote PE3. The active TE tunnel
is PE1 to P1 to PE3 and the standby TE tunnel is PE1 to PE2 to P2 to PE3. A Layer 3 link is
required between PE1 and PE2 to configure the Layer 3 service and TE tunnel.
When a single physical link exists between PE1 and PE2, The Layer 2 Ethernet sub-interface is
applicable. That is, a Layer 2 Ethernet sub-interface can be set up for the implementation of
MPLS TE functions.
Then, the Layer 2 primary interface can send VRRP packets as usual. Moreover, the route does
not change because of the active/standby switchover.
Figure 2-1 Typical application of a Layer 2 Ethernet sub-interface (VRRP + TE tunnel)
PE2 P2
el
u nn )
T up
TE ack
(B
VRRP nnel
TE Tu
(Main) PE3
UMG8900
PE1 P1
Handling the SmartLink Flush Packet

The Smart Link is a function supported by non-Huawei switches. The Smart Link adopts dual
uplinks or downlinks to realize redundancy backup by active/standby switchover, and the
switchover of Layer 2 traffic between the active link and standby link. To ensure that the Smart
Link function can take effect on theses non-Huawei switches, Huawei data communication
devices must be capable of recognizing and handling SmartLink Flush packets. In Figure 2-2
and Figure 2-3, Router A, Router B, and Router C are Huawei data communication devices,
and the Switch is a non-Huawei switch that supports Smart Link function.
The ports of Router A, Router B, and Router C are working on Layer 2 and enable SmartLink
Flush packets to be processed.
Figure 2-2 Schematic diagram of the Smart Link in the normal state
Backbone
network
RouterC
RouterA RouterB
Active link Inactive link
Switch
Link
Data flow
As shown in Figure 2-2, the switch enables the Smart Link function with two uplinks, namely,
an active link and a standby link. The active and standby links constitute the Smart Link Group,
namely, a backup link group. Normally, the Layer 2 traffic flows to backbone network through
active link. The standby link is blocked by Switch and cannot forward the traffic.
If the active link fails, the traffic will quickly switch to the standby link, through which the traffic
flows to backbone network as shown in Figure 2-3.

Figure 2-3 Schematic diagram in which the active Smart link fails
Backbone
network
RouterC
RouterA RouterB
Inactive link Active link
Switch
Link
Data flow
SmartLink flush
When the active link fails, the Switch unblocks the standby link and at the same time, sends
SmartLink Flush packets to notify other equipments on the network to delete dynamic MAC
and ARP entries.
The SmartLink Flush packet contains the control VLAN ID and all IDs of the VLANs whose
packets are permitted on the Switch port that connects the active link. Through the control
VLAN, the SmartLink Flush packets are transmitted in the control VLAN only. All VLAN IDs
that are permitted passing the active link port are used to indicate the VLAN whose dynamic
MAC and ARP entries need to be deleted.
Router B processes SmartLink Flush packets as follows:
1. Compare the control VLAN ID of the port that receives the SmartLink Flush packet with
the VLAN ID contained in the SmartLink Flush packet.
l If they are the same, Router B deletes the dynamic MAC and ARP entries of the VLAN
according to VLAN data contained in the SmartLink Flush packet.
l If they are different, the packet is directly forwarded.
2. Router B broadcasts SmartLink Flush packets within the control VLAN.
After receiving SmartLink Flush packets, Router A and Router C process packets in the
same way as Router B.
By now, Router A, Router B, and Router C have deleted the dynamic MAC and ARP entries
before the active link fails. When the downstream traffic of the backbone network reaches
Router C, Router C forwards the Layer 2 traffic to Router B according to the refreshed
MAC and ARP entries.

On Smart Link networking, after the active link returns to the normal state, to keep the
stable traffic, the traffic does not switch back to the active link voluntarily.
2.2 Configuring Ethernet Interfaces of the Interface Board

You can configure Ethernet interfaces on the Interface Boards to ensure correct physical
connections between NE80E/40Es.

Before configuring Ethernet interfaces, familiarize yourself with the applicable environment,
complete the pre-configuration tasks, and obtain the required data. This can help you complete
the configuration task quickly and accurately.
When configuring an Ethernet interface, you must assign an IP address to it. For other
parameters, you can use default values. If you have to change them, keep them consistent with
the peer device.
When a router has the function of the Layer 2 switch and the function is in use, you need to
configure the Layer 2 parameters of the Ethernet interface.
NOTE
For the application of the Layer 2 features, refer to "VLAN Configuration" and "MSTP Configuration" in
this manual.
None
Data Preparation
To configure an Ethernet interface, you need the following data.
No. Data
1 Interface number
2 IP address and mask of the Ethernet interface
3 MTU of the Ethernet interface
2.2.2 Configuring the MTU of an Ethernet Interface

The Maximum Transfer Unit (MTU), which is expressed in bytes, is closely associated with the
link layer protocol. The MTU varies according to the network type. Correctly configuring MTUs
is a prerequisite to network communication.
Context
Do as follows on each router:

Procedure
l Configuring the IPv4 MTU
1. Run:
system-view

2. Run:
interface { ethernet | gigabitethernet } interface-number
The Ethernet interface view is displayed.

3. Run:
mtu mtu
TheIPv4 MTU of the Ethernet interface is configured.

The MTU is expressed in bytes. The MTU range of Ethernet interfaces depends on
devices. By default, the MTU is 1500 bytes.
CAUTION
If IPv6 is run on an Ethernet interface and the MTU set by using the mtu command
on the interface is smaller than 1280 bytes, IPv6 works abnormally on this interface.
To avoid this situation, when IPv6 is run on an Ethernet interface, set the MTU of the
interface to a value greater than or equal to 1280.
l Configuring the IPv6 MTU

1. Run:
system-view

2. Run:

3. Run:
ipv6 enable
The IPv6 is enabled in this interface.

4. Run:
ipv6 mtu mtu
The IPv6 MTU of the Ethernet interface is configured.

The MTU is measured in bytes. The MTU range of Ethernet interfaces depends on
physical devices.
By default, MTU is 1500 bytes.
----End
Follow-up Procedure
If the MTU is too small whereas the packet size is large, the packet is probably split into many
fragments. Thus, the packet may be discarded due to the insufficient QoS queue length. To avoid

this situation, lengthen the QoS queue accordingly. The default queue scheduling mechanism is
First in First out (FIFO), and the queue length can be changed. For the configuration of a QoS
queue, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - QoS.
2.2.3 Configuring the Working Mode of an Ethernet Interface

There are two working modes at the physical layer of an Ethernet network, namely, half duplex
mode and full duplex mode. Correctly configuring working modes for Ethernet electrical
interfaces is a prerequisite to network communication.
Context
Do as follows on each interface of the router:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Perform the following as required:

l Run the duplex { full | half | auto } command to configure the working mode of the interface.
l Run the negotiation auto command to configure the working mode of the interface to be the
auto-negotiation mode.
NOTE
l Ethernet optical interfaces can work only in the full-duplex mode.

l When connected to a Hub, Ethernet electrical interfaces of a router must work in half-duplex mode.
When connected to a LAN Switch, the interfaces can work in either full-duplex mode or half-duplex
mode only if the mode is consistent with that on the peer device.
l The speed of 1000 Mbit/s and the half-duplex mode cannot be configured simultaneously on a GE
electrical interface.
l When a GE electrical interface works in auto-negotiation mode and at a rate of 1000 Mbit/s, you cannot
set the simplex or duplex mode for the interface or delete the auto-negotiation mode
l When a GE electrical interface works at a rate of 10 Mbit/s or 100 Mbit/s, you can set the simplex or
duplex mode, and auto-negotiation mode for the interface.
l If the auto-negotiation mode is enabled on the GE optical interface, the two connected ends must enable
the auto-negotiation mode.
----End
2.2.4 Configuring the Speed of an Ethernet Electrical Interface

Ethernet electrical interfaces working at different speeds transmit different volumes of data
during the same period of time. Correctly configuring speeds of Ethernet electrical interfaces is
a prerequisite to network communication.

Context
The speed of electrical interfaces needs to be set; while that of optical interface need not be set.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The interface view is displayed.
Step 3 Run:
speed { 10 | 100 | auto }
The speed on the Ethernet interface is configured.
NOTE
By default, GE electrical interfaces work at a rate of 1000 Mbit/s and in auto-negotiation mode. You can
manually change the rate if you can ensure that the rate of the local interface is the same as that of the
remote interface. When a GE electrical interface works at 10 Mbit/s or 100 Mbit/s, the auto-negotiation
mode is deleted.
----End
2.2.5 Configuring the GE/FE Optical/Electrical Interface

Generally, the NE80E/40E sets an Ethernet interface to an optical or electrical interface based
on the interface module's type. If the NE80E/40E cannot identify an interface module, you need
to manually set the interface to the optical or electrical mode.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
port-type { copper | fiber-100 | fiber-1000 }
The interface type is set.

Once the SFP module is identified, the system can automatically set the interface type according
to the type of the SFP module. No configuration is required.
If the SFP module that cannot be identified works well, you need to forcibly set the interface
type.
NOTE
l When an SFP module is being replaced, the configurations such as the loopback test, interface speed,
auto-negotiation mode, and duplex mode on the interface are all restored to default ones. You need to
reconfigure them on the interface.
l After the port-type command is run, the configurations such as the loopback test, interface speed, auto-
negotiation mode, and duplex mode on the interface are all restored to default ones. You need to
reconfigure them on the interface.
l The parameter copper can be configured in the port-type command only when an optical/electrical
SFP module is installed.
----End
2.2.6 Configuring LAN/WAN Transmission Mode for a 10 GE

Interface
The 10G XFP multi-mode optical transceiver works in either LAN or WAN mode. You can set
a proper mode as required.
Context
Do as follows on the router:
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface gigabitethernet interface-number
The view of the 10 GE interface is displayed.

Step 3 Run:
shutdown
The interface is shut down.

Step 4 Run:
set transfer-mode { lan | wan }
The transmission mode is configured for the 10 GE interface.

The transmission mode of the 10GE LAN/WAN interface on the local end and that on the remote
end must be consistent.
Step 5 Run:
undo shutdown
The interface is started.

NOTE
Before configuring the transmission mode of an interface to WAN or LAN, you need to shut down the
interface and clear all configurations except ip address.
----End
2.2.7 Configuring Overhead Bytes of the 10GE WAN Interface

The Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) provides
various overhead bytes to implement monitoring functions in different hierarchies.
Context
The 10GE WAN LPU shall adapt SDH/SONET during the packet processing. Therefore, the
interface need configure the flag parameters.
Do as follows on the routers:
Procedure
Step 1 Run:
system-view

Step 2 Run:
The 10GE interface view is displayed.

Step 3 To configure the overhead bytes of the 10GE WAN interface, choose the following commands
as required:
l Run the flag j0 64byte-or-null-mode [ j0-value ] or the flag j0 { 16byte-mode | 1byte-
mode } j0-value command to configure the overhead byte j0.
l Run the flag j1 64byte-or-null-mode [ j1-value ] or the flag j1 { 16byte-mode | 1byte-
mode } j1-value command to configure the overhead byte j1.
l Run the flag c2 c2-value command to configure the overhead byte c2 of the 10GE WAN
interface.
----End
2.2.8 Configuring Flow Control on the GE Interface

Configuring flow control on an interface ensures that the interface can properly process received
frames.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
The GE interface view is displayed.
Step 3 Run:
flow control [ receive | send ]
The flow control function is enabled.
By default, flow control is enabled on a GE interface.
After flow control is enabled on an interface, the interface sends a Pause frame to notify the peer
interface to send traffic at a slower rate, if the received traffic reaches the set threshold (for
example, when the traffic rate on a GE interface exceeds 1 Gbit/s). If the peer interface also
supports flow control, it sends traffic at a slower rate after receiving the Pause frame so that the
local interface can process received frames properly.
----End
2.2.9 Configuring Self-Loop Detection on the GE Interface

After the self-loop detection function is enabled, the self-loop on an interface can be detected
and then the interface is blocked.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
The GE interface view is displayed.
Step 3 Run:
loopback-detect enable
The self-loop detection function is enabled.
Step 4 Run:
loopback-detect block block-time
Set the delay time of the interface recovery after the self-loop on the interface is eliminated.
By default, the interface recovers 10 seconds after the self-loop on the interface is eliminated.
----End

2.2.10 Switching the Working Mode of an Ethernet Interface

By default, Ethernet interfaces on the NE80E/40E are Layer 3 interfaces. To use Layer 2
attributes of Ethernet interfaces, you need to convert Ethernet interfaces into Layer 2 interfaces.
Context
After a Layer 3 interface switches to the Layer 2 mode, the Layer 3 ID and functions are disabled,
and the MAC address is adopted.
Procedure
l Switching the Working Mode of a Specified Ethernet Interface
1. Run:
system-view

2. Run:
The specified Ethernet interface is displayed.

3. Run:
portswitch
The Ethernet interface is switched to a Layer 2 interface.

l Switching the Working Mode of Ethernet Interfaces in Batch
1. Run:
system-view

2. Run:
portswitch batch interface-type { interface-number1 [ to interface-
number2 ] } &<1-10>
The working mode of Ethernet interfaces are switched in batch.
By default, Ethernet interfaces work in the Layer 3 mode.
----End

After an Ethernet interface is configured, you can check information about the interface,
including the IP address, MTU, speed, working mode, interface mode, and number of received
and sent frames.
Procedure
l Run the display interface { ethernet | gigabitethernet } [ interface-number ] command
to check the status of the specified Ethernet interface.

l Run the display interface ethernet brief command to check the brief information about
the Ethernet interface.
----End
Example
Run the display interface command. You can view the MTU, IP address and mask, working
speed and mode. For example:
<HUAWEI> display interface gigabitethernet 2/0/0
GigabitEthernet2/0/0 current state : UP
Line protocol current state : UP
Description : GigabitEthernet2/0/0 Interface, Route Port
The Maximum Transmit Unit is 1500 bytes, Hold timer is 10(sec)
Internet Address is 1.1.3.1/24
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc01-0054
Media type: twisted-pair ,Link type: auto negotiation
Loopback:none, Maximal BW:1G, Current BW:100M, full-duplex mode,
Pause Flowcontrol:Send and Receive Enable
Statistics last cleared:never
Last 30 seconds input rate: 0 bits/sec, 0 packets/sec
Last 30 seconds output rate: 0 bits/sec, 0 packets/sec
Input: 0 Bytes, 0 Packets
Output: 0 Bytes, 0 Packets
Input:
Unicast: 0, Multicast: 0
Broadcast: 0, JumboOctets: 0
CRC: 0, Symbol: 0
Overrun: 0 , InRangeLength: 0
LongPacket: 0 , Jabber: 0, Alignment: 0
Fragment: 0, Undersized Frame: 0
RxPause: 0
Output:
Unicast: 0, Multicast: 0
Broadcast: 0, JumboOctets: 0
Lost: 0, Overflow: 0, Underrun: 0
TxPause: 0
Input bandwidth utilization : 0.01%
Output bandwidth utilization : 0.01%
Running the display interface ethernet brief command, you can view the brief information
about the Ethernet interface. The information includes the physical status, auto-negotiation
mode, full-duplex mode, interface rate, and the average bandwidth utility in the recent period in
the receiving direction and sending direction.
<HUAWEI> display interface ethernet brief
*down: administratively down
^down: standby
(l): loopback
(b): BFD down
InUti/OutUti: input utility/output utility
Interface Physical Auto-Neg Duplex Bandwidth InUti OutUti
Trunk
GigabitEthernet0/0/0 up enable half 100M 0% 0%
--
GigabitEthernet2/0/0 up disable full 1000M 0.01% 0.01%
--
GigabitEthernet2/0/1 up disable full 1000M 0% 0%
--
GigabitEthernet2/0/2 down disable full 1000M 0% 0%
--
GigabitEthernet3/0/0 down enable full 1000M 0% 0%
--
--

GigabitEthernet3/0/1.1 down enable full 100M 0% 0%

--
GigabitEthernet3/0/2 up enable full 1000M 0.01% 0.01%
--
--
2.3 Configuring Ethernet Interfaces of the SRU

By configuring an Ethernet interface on an MPU, you can connect the NE80E/40E to a network
management system (NMS) for management.

Before configuring an Ethernet interface on an MPU, familiarize yourself with the applicable
environment, complete the pre-configuration tasks, and obtain the required data. This can help
you complete the configuration task quickly and accurately.
Ethernet interface of the MPU/SRU is used to connect the network management station of the
system.
Pre-configured Tasks
None
Data Preparation
To configure the Ethernet interface, you need the following data.
No. Data
1 Ethernet interface number
2 IP address and mask of the Ethernet interface
2.3.2 Assigning an IP Address to an Ethernet Interface

You can assign an IP address to an Ethernet interface on the NE80E/40Eto implement
communication between the NE80E/40E and the NMS.
Context
For detailed information about IP address configuration, refer to the HUAWEI NetEngine80E/
40E Router Configuration Guide - IP Services.
Procedure
Step 1 Run:

system-view

Step 2 Run:
The GigabitEthernet interface view is displayed.

Step 3 Run:
ip address { mask |mask-length } [ sub ]
An IP address is assigned for the interface.

Note that the parameter sub is used to configure the second or more IP addresses for the interface.
----End
2.3.3 Configuring the Working Mode of an Ethernet Electrical

Interface
There are two working modes at the physical layer of an Ethernet network, namely, half duplex
mode and full duplex mode. Correctly configuring working modes for Ethernet electrical
interfaces is a prerequisite to network communication.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run
duplex { auto | half | full }
The working mode of the Ethernet electrical interface is configured.

The Ethernet electrical interface can work in both full-duplex and half-duplex mode.
NOTE
l When connected to a Hub, Ethernet electrical interfaces of the router must work in half-duplex mode.
l When connected to a LAN Switch, Ethernet electrical interfaces of the routers can work in either full-
duplex mode or half-duplex mode only if consistent with the configuration on the peer device.
l The operating mode of the Ethernet interface on the local end and that on the remote end must be
consistent.
By default, the auto mode, which is the best half-duplex mode of system auto-negotiation, is
adopted.
----End

2.3.4 Configuring the Speed of an Ethernet Electrical Interface

Ethernet electrical interfaces working at different speeds transmit different volumes of data
during the same period of time. Correctly configuring speeds of Ethernet electrical interfaces is
a prerequisite to network communication.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
speed { auto | 10 | 100 | 1000 }
The speed on the Ethernet electrical interface is configured.

The NE80E/40E Ethernet electrical interface supports three kinds of operating speed: 10Mbit/
s, 100Mbit/s, and 1000Mbit/s.
By default, the auto mode, which is the best half-duplex mode of system auto-negotiation, is
adopted.
You can specify the operating speed of an interface manually. Do keep the rate the same as that
of the peer device.
----End
2.3.5 Configuring the Promiscuity Mode

The promiscuity mode of an interface determines how the NE80E/40E receives frames from the
physical layer.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
promode { on | off }
The Promiscuity Mode is set.
By default, the promiscuity mode of the Ethernet interface on SRU/MPU is off.
----End
2.4 Configuring Ethernet Interfaces Layer 2 Parameters

After an Ethernet interface is configured with Layer 2 attributes, it can access a device or directly
forward Ethernet frames on a Layer 2 network. Layer 2 attributes define link layer information
of Ethernet interfaces.

Before configuring Layer 2 attributes for Ethernet interfaces, familiarize yourself with the
The Ethernet interfaces provided by the NE80E/40E can work in the following two modes:
routed mode (Layer 3 mode) and switched mode (Layer 2 mode).
l Routed mode: can be configured with the Layer 3 attributes and switched to the Layer 2
mode by commands.
By default, the Ethernet interface is in the Layer 3 mode.
l Switched mode: can be configured with the Layer 2 attributes and switched to the Layer 3
mode by commands.
When the router is used as a Layer 2 switch, Layer 2 parameters are required on Ethernet
interface.
Pre-configured Tasks
None
Data Preparation
To configure the Ethernet interface, you need the following data.
No. Data
1 Ethernet interface number
2 802.1p priority value of the Ethernet interface

2.4.2 Configuring Link Layer Type of an Ethernet Interface

Link types of Ethernet interfaces are access, hybrid, trunk, and dot1q-tunnel. You need to
configure a proper link type for an Ethernet interface so that the interface can transmit VLAN-
tagged frames.
Context
The Ethernet interface supports four types of links: Access, dot1q-tunnel, Trunk and Hybrid.
l Access: In this mode, the interface belongs to only one VLAN and is generally used to
connect PCs.
l dot1q-tunnel: In this mode, the interface is enabled Q-in-Q function.
l Hybrid: In this mode, the interface can belong to multiple VLANs to receive and send
packets of these VLANs. It is used to connect switches or PCs.
l Trunk: In this mode, the interface can belong to multiple VLANs to receive and send packets
of these VLANs. It is used to connect switches.
The difference between the Hybrid interface and the trunk interface lies that, the Hybrid interface
allows transmitting untagged packets of multiple VLANs whereas the trunk interface allows that
of the default VLAN only.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
portswitch
The Ethernet interface is switched to Layer 2 mode.

Step 4 Run:
port link-type { access | hybrid | trunk | dot1q-tunnel }
The interface type is specified.

By default, the link type is Hybrid.
----End
2.5 Configuring SmartLink Flush Function

Some Layer 2 devices in the network support the Smart Link function. By default, Huawei data
communication devices do not process the SmartLink flush packets sent from these Layer 2
devices. To enable the communication between the Huawei devices and the devices of other

vendors, you need to configure the SmartLink Flush function on Huawei data communication
devices.

Before configuring the SmartLink Flush function, familiarize yourself with the applicable
Some Layer 2 devices on network support the Smart Link function. By default, Huawei data
communication devices do not process the SmartLink Flush packets sent by these devices.
To ensure the Smart Link function to be enabled on these Layer 2 devices, Huawei data
communication devices are required processing SmartLink Flush packets when working with
non-Huawei switches supporting the Smart Link function on a network.
Before configuring equipment to process SmartLink Flush packets, complete the following
tasks:
l Ensuring that the physical interfaces on network devices are correctly connected and in the
state of Up.
l Enabling the port that can process SmartLink Flush packets to allow the packet that carries
the control VLAN tag passing.
Data Preparation
Before configuring equipment to process SmartLink Flush packets, you need the following data.
No. Data
1 Number of the interface that can recognize SmartLink Flush packets
2 Control VLAN ID
2.5.2 Enabling a Port to Process SmartLink Flush Packets

The Huawei device can process the SmartLink flush packets only after being enabled with the
SmartLink Flush function; otherwise, the device discards the SmartLink flush packets.
Context
Do as follows on routers that are deployed together with the switch enabled with the Smart Link
function.

Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
portswitch
Step 4 Run:
smart-link flush enable control-vlan vlan-id
The Ethernet interface is enabled to process SmartLink Flush packets.
If the SmartLink Flush packet carries the control VLAN Tag, vlan-id must accord with the
control VLAN ID in the SmartLink Flush packet. Otherwise, the equipment does not process
this SmartLink Flush packet.
----End
2.6 Maintaining Ethernet Interfaces

The commands related to Ethernet interfaces can be used to locate the faults on an Ethernet
interface.
2.6.1 Testing the Loop of Ethernet Interfaces

To test an Ethernet interface itself, you can run the loopback command in the Ethernet interface
view. When the interface works normally, you must disable the loopback function.
Context
The loop of Ethernet interfaces is generally used to test the interfaces. Run the following
command in the Ethernet interface view.
When interfaces work normally, disable the loop.
Procedure
Step 1 Run the loopback { local | remote } command in Ethernet interface view or GE interface view
to enable the loop on interfaces.
----End


This section lists the networking requirements, configuration roadmap, and data preparation to
describe the typical application scenarios of Ethernet interfaces, and provides related
NOTE
2.7.1 Example for Configuring a Layer 3 Ethernet Interface

In this networking, you need to configure only the IP address, because other configuration items
retain their default values. If the values of other configuration items need to be changed, you
must set them to be the same as those on the remote device.
As shown in Figure 2-4, Ethernet interfaces of RouterA, RouterB, and RouterC are connected
to the IP network 100.1.1.0/24.
Figure 2-4 Networking diagram of Ethernet interface configuration
RouterA RouterB
GE1/0/0 GE1/0/0
100.1.1.1/24 100.1.1.2/24
GE1/0/0
100.1.1.3/24
RouterC
1. Configure description about each router.
2. Configure IP addresses for interfaces on each router.
Data Preparation
To configure an Ethernet interface, you need the following data:
l Interface number

l IP address of the interface
Procedure
Step 1 Configure RouterA.
[HUAWEI] sysname RouterA
[RouterA] interface gigabitethernet 1/0/0
[RouterA-GigabitEthernet1/0/0] undo shutdown
[RouterA-GigabitEthernet1/0/0] description RouterA
[RouterA-GigabitEthernet1/0/0] ip address 100.1.1.1 255.255.255.0
[RouterA-GigabitEthernet1/0/0] quit
Step 2 Configure RouterB.

[HUAWEI] sysname RouterB
[RouterB] interface gigabitethernet 1/0/0
[RouterB-GigabitEthernet1/0/0] undo shutdown
[RouterB-GigabitEthernet1/0/0] description RouterB
[RouterB-GigabitEthernet1/0/0] ip address 100.1.1.2 255.255.255.0
[RouterB-GigabitEthernet1/0/0] quit
Step 3 Configure RouterC.

[HUAWEI] sysname RouterC
[RouterC] interface gigabitethernet 1/0/0
[RouterC-GigabitEthernet1/0/0] undo shutdown
[RouterC-GigabitEthernet1/0/0] description RouterC
[RouterC-GigabitEthernet1/0/0] ip address 100.1.1.3 255.255.255.0
[RouterC-GigabitEthernet1/0/0] quit
After the configuration, using the following methods, you can check whether the interface works
normally with the configuration.
l In the case of small traffic volume, ping Ethernet interfaces of a router from another router.
The interfaces are normal if all the ping packets are returned.
l Check the statistics of a router. The interfaces are normal if the number of received error
frames does not change.
Check the interface status of each router. In the normal situation, the physical status and protocol
status are Up.
Take RouterA as an example:

<RouterA> display ip interface brief
!down: FIB overload down
(l): loopback
(s): spoofing
The number of interface that is UP in Physical is 2
The number of interface that is DOWN in Physical is 0
The number of interface that is UP in Protocol is 2
The number of interface that is DOWN in Protocol is 0
Interface IP Address/Mask Physical Protocol
GigabitEthernet1/0/0 100.1.1.1 up up
NULL0 unassigned up up(s)
----End

Configuration Files
l Configuration file of RouterA
#
sysname RouterA
#
undo shutdown
ip address 100.1.1.1 255.255.255.0
description RouterA
#
return
l Configuration file of RouterB

#
sysname RouterB
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
description RouterB
#
return
l Configuration file of RouterC

#
sysname RouterC
#
undo shutdown
ip address 100.1.1.3 255.255.255.0
description RouterC
#
return
2.7.2 Example for Configuring VLANs to Communicate Through

Ethernet Sub-interfaces
To enable communications between different VLANs, you can create sub-interfaces specific to
VLANs on the Ethernet interfaces that connect a router and a switch. In addition, you can
configure 802.1Q encapsulation on and assign IP addresses to the sub-interfaces. In this manner,
communications between VLANs can be implemented through Layer 2 switches and routers.
Context
For details, refer to 4.12.2 Example for Configuring Inter-VLAN Communication by Using
Sub-interfaces in the 4 VLAN Configuration.
2.7.3 Example for Configuring a Device to Handle Smartlink Flush

Packets
In this networking, the devices of other vendors support the SmartLink function but the Huawei
devices do not support the SmartLink function by default. When the Huawei data communication
devices need to communicate with the switches of other vendors that support the SmartLink
function, you need to enable the Huawei devices to process SmartLink flush packets.

As shown in Figure 2-5, RouterA, RouterB, and RouterC are Huawei devices and the Switch
supports the Smart Link function. The Smart Link is enabled on the Switch. Two uplinks
constitute a Smart Link Group, namely, a backup link group.
RouterA is the active link for the Switch and RouterB is the standby link. At last, the data reach
the backbone network through RouterC.
The control VLAN ID of the Switch is 10.
It requires the interfaces on RouterA, RouterB, and RouterC to enable to process SmartLink
Flush packet. This can help the Switch to realize the switchover between active and standby
links.
Figure 2-5 Networking diagram of configuring equipment to process Smart Link packets
Backbone
network
RouterC
GE1/0/0 GE2/0/0
GE2/0/0 GE2/0/0
RouterA RouterB
GE1/0/0 GE1/0/0
Active link Inactive link
VLAN 10 VLAN 10
smart-link
Switch
Link
1. Change the interface on the router to Layer 2 mode and configure the port to allow packets
from VLAN 10 to pass.
2. Enable a Layer 2 port to recognize the SmartLink Flush packet.
Data Preparation
l Control VLAN ID

l Number of the interface on the router
Procedure
Step 1 Configure the interface on a router
# Create VLAN 1 to VLAN 4094 on RouterA.
[HUAWEI] syname RouterA
[RouterA] vlan batch 1 to 4094
# Switch the interfaces GE 1/0/0 and GE 2/0/0 on RouterA to Layer 2 mode and configure them
as VLAN trunk ports that allow all VLAN frames to pass.
[RouterA-GigabitEthernet1/0/0] portswitch
[RouterA-GigabitEthernet1/0/0] port link-type trunk
[RouterA-GigabitEthernet1/0/0] port trunk allow-pass vlan all
[RouterA-GigabitEthernet2/0/0] port trunk allow-pass vlan all
# Create VLAN 1 to VLAN 4094 on RouterB.

[HUAWEI] syname RouterB
[RouterB] vlan batch 1 to 4094
# Switch GE 1/0/0 and GE 2/0/0 on RouterB to Layer 2 mode and configure them as VLAN
trunk ports that allow all VLAN frames to pass.
[RouterB-GigabitEthernet1/0/0] portswitch
[RouterB-GigabitEthernet1/0/0] port link-type trunk
[RouterB-GigabitEthernet1/0/0] port trunk allow-pass vlan all
[RouterB-GigabitEthernet2/0/0] port trunk allow-pass vlan all
# Create VLAN 1 to VLAN 4094 on RouterC.

[HUAWEI] syname RouterC
[RouterC] vlan batch 1 to 4094
# Switch GE 1/0/0 and GE 2/0/0 on RouterC to Layer 2 mode and configure them as VLAN
trunk ports that allow all VLAN frames to pass.
[RouterC-GigabitEthernet1/0/0] portswitch
[RouterC-GigabitEthernet1/0/0] port link-type trunk
[RouterC-GigabitEthernet1/0/0] port trunk allow-pass vlan all

[RouterC-GigabitEthernet2/0/0] port trunk allow-pass vlan all
Step 2 Enable the port to recognize SmartLink Flush packets

# Enable GE 1/0/0 and GE 2/0/0 on RouterA to recognize SmartLink Flush packets.
[RouterA-GigabitEthernet1/0/0] smart-link flush enable control-vlan 10
[RouterA-GigabitEthernet2/0/0] smart-link flush enable control-vlan 10
# Enable GE 1/0/0 and GE 2/0/0 on RouterB to recognize SmartLink Flush packets.

[RouterB-GigabitEthernet1/0/0] smart-link flush enable control-vlan 10
# Enable GE 1/0/0 and GE 2/0/0 on RouterC to recognize SmartLink Flush packets.

[RouterC-GigabitEthernet1/0/0] smart-link flush enable control-vlan 10

# Run the display this command. You can check whether the smart-link flush enable command
is configured and a correct VLAN ID is specified. Take RouterA as an example:
[RouterA-GigabitEthernet1/0/0] display this
#
undo shutdown
portswitch
port trunk allow-pass vlan 1 to 4094
smart-link flush enable control-vlan 10
#return
----End
Configuration Files
#
sysname RouterA
#
#
undo shutdown
portswitch
#
undo shutdown

portswitch
#
return

#
sysname RouterB
#
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return

#
sysname RouterC
#
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return

Configuration Guide - LAN Access and MAN Access 3 Eth-Trunk Interface Configuration
3 Eth-Trunk Interface Configuration
About This Chapter
You can configure Eth-Trunk interfaces to implement load balancing, increase interface
bandwidth, and improve transmission reliability.
3.1 Eth-Trunk Interface Introduction

Trunk is a binding technology. Multiple Ethernet interfaces can be bound into a logical interface,
which is called an Eth-Trunk interface. The Ethernet interfaces are called member interfaces.
3.2 Configuring an Eth-Trunk Interface in Manual Load Balancing Mode
Of the two directly connected devices between which an Eth-Trunk connection is established,
one device does not support the Link Aggregation Control Protocol (LACP). In this case, you
can create an Eth-Trunk interface in manual load balancing mode on each device, and then add
interfaces to the Eth-Trunk interface to increase bandwidth and improve reliability.
3.3 Configuring an Eth-Trunk Interface in 1:1 Active/Standby Mode
Eth-Trunk interfaces in 1:1 active/standby mode can be configured on two devices so that data
can be transmitted over the links working in 1:1 backup mode.
3.4 Configuring an Eth-Trunk Interface in Static LACP Mode
LACP provides a standard negotiation mode for the devices that exchange data. In this
negotiation mode, the system can automatically form aggregation links based on its
configuration and enable the aggregation links to receive and send data, which thus improves
fault tolerance. In addition, member links can work in M:N backup mode, ensuring reliable data
transmission.
3.5 Associating an Eth-Trunk Interface in Static LACP Mode with an mVRRP Backup Group
After an Eth-Trunk interface in static LACP mode is associated with an mVRRP backup group,
the Eth-Trunk interface can detect the status change in the mVRRP backup group, and thus
rapidly switch traffic to an available path. This ensures reliable data transmission.
3.6 Configuring Layer 2 Attributes for an Eth-Trunk Interface
Layer 2 attributes define link layer attributes for an Eth-Trunk interface.
3.7 Configuring Layer 3 Attributes for an Eth-Trunk Interface
To use an Eth-Trunk interface to transmit Layer 3 packets, you need to configure Layer 3
attributes for the Eth-Trunk interface.
3.8 Configuring an Eth-Trunk Sub-interface

Layer 2 and Layer 3 Eth-Trunk interfaces on the NE80E/40E can be configured with sub-
interfaces. Creating a sub-interface on a Layer 2 Eth-Trunk interface and then configuring MPLS
TE on the sub-interface enable a physical link to transmit both Layer 2 and Layer 3 services.
3.9 Configuring E-Trunk
Enhanced Trunk (E-Trunk) is an extension of LACP to implement link aggregation among
multiple devices. It guarantees device-level link reliability.
3.10 Maintaining Eth-Trunk Interfaces
Statistics clearing commands helps to locate faults on Eth-Trunk interfaces.
This section describes typical application scenarios for Eth-Trunk interfaces, providing
networking requirements, configuration roadmap, data preparation, and configuration files.

3.1 Eth-Trunk Interface Introduction

Trunk is a binding technology. Multiple Ethernet interfaces can be bound into a logical interface,
which is called an Eth-Trunk interface. The Ethernet interfaces are called member interfaces.
3.1.1 Introduction to Eth-Trunk Interfaces and LACP

In addition to all functions of an Ethernet interface, an Eth-Trunk interface provides wider
bandwidth and higher transmission reliability.
Eth-Trunk Interfaces
Trunk interfaces are classified into Eth-Trunk interfaces and IP-Trunk interfaces. An Eth-Trunk
link consists of Ethernet links only. For detailed configurations of IP-Trunk interfaces, refer to
the HUAWEI NetEngine80E/40E Router Configuration Guide - WAN Access.
A maximum of 64 trunk interfaces (including Eth-Trunk and IP-Trunk interfaces) can be created
on one router; each Eth-Trunk interface contains up to 16 physical member links.
The Eth-Trunk technology has the following advantages:
l Increasing bandwidth: The bandwidth of an Eth-Trunk interface is the sum of the bandwidth
of all member interfaces.
l Improving reliability: If a member link fails, traffic automatically switches to another
available link.
An Eth-Trunk interface has the following characteristics:
l Supports the features of an Ethernet interface.
l Supports the configuration of an IP address, and its member interfaces borrow this IP
address.
l Supports Layer 2 forwarding, MPLS forwarding, and Layer 3 unicast and multicast
forwarding. The Hash algorithm can be used in load balancing by flow.
l Supports QoS based on physical interfaces and logical interfaces.
l Supports MPLS and VPN instance binding.
l Supports hot backup and hot swap.
NOTE
Eth-Trunk sub-interfaces are used between VLANs. For the configuration of Eth-Trunk sub-interfaces,
refer to the chapter "VLAN Configuration" in this manual.
LACP
Link aggregation is a method of binding a group of physical interfaces into a logical interface
to increase bandwidth. The bound interfaces are called a multi-interface load sharing group or
a link aggregation group (LAG). For more information about link aggregation, refer to IEEE
802.3ad.
Establishing an LAG between two devices provides wider bandwidth and greater reliability.
Link aggregation provides protection for communications between devices without the need of
upgrading the devices' hardware.

l Active and inactive interfaces

Interfaces that are in the active state and responsible for forwarding data are called active
interfaces. On the contrary, interfaces that are in the inactive state and do not forward data
are called inactive interfaces. Based on working modes, active and inactive interfaces are
classified as follows:
– Manual load balancing mode: generally, all member interfaces are active ones unless a
fault occurs on a member interface.
– 1:1 active/standby mode: normally, the master interface is the active interface and the
backup interface is the inactive interface. If the master interface fails, the backup
interface is activated and the master interface becomes inactive.
– Static LACP mode: the interfaces connected to M links are active interfaces that are
responsible for forwarding data; the interfaces connected to N links are inactive
interfaces that back up the active interfaces.
l Actor and Partner
In static LACP mode, the device with a higher LACP priority in an LAG is the Actor and
the device with a lower LACP priority is the Partner.
Differentiating the Actor and the Partner helps both devices to select the same interfaces
as the active interfaces. If the two devices select active interfaces based on interface
priorities, different interfaces are probably selected. As a result, active links cannot be
established. Therefore, the Actor must be determined. The Partner then selects active
interfaces based on interface priorities of the Actor, as shown in Figure 3-1.
Figure 3-1 Actor determines active links in static LACP mode

RouterA RouterB
The device with higher The device with lower

system priority system priority
The actor determines
the active links
RouterA RouterB
l Control VLAN
In 1:1 active/standby mode, a VLAN that sends or receives Flush packets is called a control
VLAN.
3.1.2 Eth-Trunk Interface and LACP Features Supported by the

NE80E/40E
Before configuring Eth-Trunk interfaces, familiarize yourself with the concepts such as link
aggregation modes, load balancing, lower and upper thresholds for Up member links, member
interface backup, and Eth-Trunk sub-interfaces. This will help you complete the configuration
tasks quickly and accurately.

Lower and Upper Thresholds for Up Member Links

The number of Up member links of an Eth-Trunk link affects the status and bandwidth of the
Eth-Trunk link. To stabilize the Eth-Trunk link, you can set thresholds to limit the number of
Up member interfaces, thus reducing the possibilities of status changes of the Eth-Trunk link.
l Lower threshold for Up member links: If the number of Up member links falls below this
threshold, the Eth-Trunk link becomes Down.
l Upper threshold for Up member links: After the number of Up member links reaches this
threshold, more member interfaces becoming Up will not increase the bandwidth of the
Eth-Trunk link. If the number of Up member links falls below this threshold, the bandwidth
of the Eth-Trunk link will decrease.
Load Balancing
Traffic transmitted over an Eth-Trunk link are distributed to member links. The volume of traffic
transmitted over a member interface is determined by the weight configured for the member
link.
Load balancing can be carried out in the following ways:
l Per-destination load balancing: packets with the same source and destination IP addresses
or with the same source and destination MAC addresses are transmitted over one member
link.
Layer 2 Eth-Trunk interfaces support only per-destination load balancing for packets with
the same source and destination MAC addresses.
Layer 3 Eth-Trunk interfaces support only per-destination load balancing for packets with
the same source and destination IP addresses.
l Per-packet load balancing: packets are transmitted over different member links.
Both Layer 2 and Layer 3 Eth-Trunk interfaces support per-packet load balancing.
Member Interface Backup

To improve the reliability of an Eth-Trunk interface, you can configure member interface
backup.
If a member interface goes Down, traffic rapidly switches to another member interface. The
backup interface is an Up member interface of the same Eth-Trunk interface.
NOTE
If member interfaces of a trunk interface reside on different LPUs, a BFD session needs to be configured
to detect the member link status, with the process-pst command being used to associate the BFD session
with member interfaces. Otherwise, traffic will be lost in certain situations (for example, when the LPU
where a member interface resides is restarted).
For the configuration of a BFD session, refer to the HUAWEI NetEngine80E/40E Router Configuration
Guide - Reliability.
Eth-Trunk Sub-interfaces
Sub-interfaces can be created on an Eth-Trunk interface. The NE80E/40E supports creation of
sub-interfaces on both Layer 3 Eth-Trunk interfaces and Layer 2 Eth-Trunk interfaces.
After an Eth-Trunk sub-interface is encapsulated with 802.1Q and associated with a VLAN,
devices in this VLAN can communicate with other devices by using the Eth-Trunk sub-interface.

An Eth-Trunk sub-interface can be configured with dot1q termination or QinQ termination. For
details, see QinQ Configuration.
In addition to the preceding applications, a Layer 2 Eth-Trunk sub-interface can transmit both
Layer 2 and Layer 3 services along one physical link. As shown in Figure 3-2, the backbone of
the MAN is a Layer 2 Eth-Trunk ring network that supports QinQ services. On the Eth-Trunk
ring network. Each NE80E/40E is connected to a Layer 2 ring network consisting of several
switches. The digital subscriber line access multiplexer (DSLAM) devices are connected to
switches and access the broadband remote access servers (BRASs) by using VLAN mapping
over the Layer 2 ring network and the Eth-Trunk network. The entire Eth-Trunk ring network
supporting Layer 2 functions is required.
In addition, the NE80E/40E provides access for CEs and provides L3VPN services by using TE
tunnels. This requires the Layer 2 interfaces of the NE80E/40Es forming the Eth-Trunk ring
network support TE tunnels based on Layer 3 interfaces.
In this case, Layer 2 Eth-Trunk sub-interfaces can be configured to meet the requirements. On
the Eth-Trunk ring network, Eth-Trunk interfaces provide Layer 2 functions and Layer 2 Eth-
Trunk sub-interfaces provide MPLS TE functions.
Figure 3-2 Application of Layer 2 Eth-Trunk sub-interfaces (Eth-Trunk ring network)

NE40E
TE Tunnel (Backup)
Layer2 NE40E
Ring BRAS
Eth-Trunk Ring NE40E
TE Tunnel (Main)
NE40E BRAS
NE40E
L3VPN Network
DSLAM CE1 CE2
Manual Load Balancing Mode

The manual load balancing mode allows interfaces to be manually added to an LAG to transmit
packets. The NE80E/40E supports these manual load balancing modes: IP, MAC, and Packet-
all. IP and MAC are applicable to per-destination load balancing and Packet-all is applicable to
per-packet load balancing.
1:1 Active/Standby Mode

In 1:1 active/standby mode, an LAG contains only two member interfaces. One is master and
the other is backup.

In manual mode, an Eth-Trunk interface is manually created; interfaces are manually added to
the Eth-Trunk; member interfaces are manually set to the active or inactive state. In this mode,
Link Aggregation Control Protocol Date Units (LACPDUs) are not involved.
The manual mode is used when the peer device does not support LACP.
Static LACP Mode

The static LACP mode is a link aggregation method of determining active and inactive interfaces
by using LACPDUs to negotiate parameters. In static LACP mode, an Eth-Trunk is manually
created and interfaces are manually added to the Eth-Trunk interface. LACP is then used to
determine active and inactive member interfaces.
The static LACP mode is also called the M: N mode, which implements both load balancing and
member interface backup. In an LAG, M links are active to forward data and perform load
balancing; N links are inactive, which function as backup links and do not forward data. When
a link of M links fails, the system selects the link with the highest priority from N links to replace
the faulty link. In this case, the backup link becomes active and starts to forward data.
3.2 Configuring an Eth-Trunk Interface in Manual Load

Balancing Mode
Of the two directly connected devices between which an Eth-Trunk connection is established,
one device does not support the Link Aggregation Control Protocol (LACP). In this case, you
can create an Eth-Trunk interface in manual load balancing mode on each device, and then add
interfaces to the Eth-Trunk interface to increase bandwidth and improve reliability.

Before configuring an Eth-Trunk interfaces in manual load balancing mode, familiarize yourself
with the applicable environment, complete the pre-configuration tasks, and obtain the data
required for the configuration. This will help you complete the configuration task quickly and
accurately.
To improve link communication capabilities, you can bind multiple Ethernet interfaces to form
an Eth-Trunk interface. The bandwidth of the Eth-Trunk interface is the total bandwidth of all
member interfaces. In this manner, the interface bandwidth is increased.
Load balancing can be carried out on an Eth-Trunk interface by distributing traffic to member
links to send the traffic to the same destination. This prevents network congestion.
Configuring an Eth-Trunk interface improves the link reliability. If a member interface of the
Eth-Trunk interface goes Down, traffic switches to other member interfaces.
If one of two directly-connected devices does not support LACP, an Eth-Trunk in manual load
balancing mode can be configured on the Router and interfaces can be added to the Eth-Trunk
interface to increase bandwidth and reliability.
As shown in Figure 3-3, RouterA supports LACP, but RouterB does not support LACP.

NOTE
In manual load balancing mode, interfaces at different speeds, in different duplex modes, or on different
boards can be added to one Eth-Trunk interface.
Figure 3-3 Networking diagram for link aggregation in manual load balancing mode
Eth-Trunk 1 Eth-Trunk 1
Eth-Trunk
RouterA RouterB
Before configuring an Eth-Trunk interface in manual load balancing mode, complete the
following task:
l Powering on the Router and ensuring a successful self-check.
Data Preparation
To create an Eth-Trunk interface in manual load balancing mode, you need the following data.
No. Data
1 Eth-Trunk ID
2 Type and number of each interface to be added to the Eth-Trunk interface
3.2.2 Creating an Eth-Trunk Interface

An Eth-Trunk ID uniquely identifies an Eth-Trunk link. Physical interfaces can be added to an
Eth-Trunk interface only after the Eth-Trunk interface is created.
Context
Do as follows on the device where an Eth-Trunk interface needs to be configured.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface eth-trunk trunk-id

An Eth-Trunk interface is created.
----End
3.2.3 (Optional) Configuring a Working Mode for an Eth-Trunk

Interface
To transmit Layer 2 services, an Eth-Trunk interface needs to be switched into a Layer 2
interface.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The Eth-Trunk interface view is displayed.
Step 3 Run:
portswitch
The Layer 3 Eth-Trunk interface is switched into a Layer 2 interface.
By default, an Eth-Trunk interface works in Layer 3 mode.
After an Eth-Trunk interface is switched into a Layer 2 interface, its Layer 3 functions are
disabled and the interface is identified by the system MAC address.
An Eth-Trunk interface needs to be switched into a Layer 2 interface before being bound to a
VLAN. Before switching between working modes, delete all configurations of the Eth-Trunk
interface.
The undo portswitch command is used to switch a Layer 2 Eth-Trunk interface into a Layer 3
one.
NOTE
l The minimum interval between the portswitch command and the undo portswitch command is 30
seconds.
l The working mode of an Eth-Trunk interface does not affect the addition of interfaces. An Ethernet
interface can join either a Layer 2 Eth-Trunk interface or a Layer 3 Eth-Trunk interface.
----End
3.2.4 Configuring an Eth-Trunk Interface to Work in Manual Load

Balancing Mode
The manual load balancing mode allows interfaces to be manually added to an Eth-Trunk
interface.

Context
NOTE
Before configuring a working mode for an Eth-Trunk interface, ensure that the Eth-Trunk interface does
not have any member interface; otherwise, the working mode cannot be changed. To delete a member
interface, run the undo eth-trunk command in the interface view.
Both Layer 2 and Layer 3 Eth-Trunk interfaces support the manual load balancing mode.
Do as follows on the devices at the two ends of an Eth-Trunk link:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
mode manual load-balance
The working mode of the Eth-Trunk interface is set to manual load balancing.
By default, an Eth-Trunk interface works in manual load balancing mode.
----End
3.2.5 Adding Interfaces to an Eth-Trunk Interface

After an Eth-Trunk interface is successfully configured, interfaces need to be added to the Eth-
Trunk interface to increase bandwidth, improve reliability, and implement load balancing.
Context
NOTE
A physical interface added to an Eth-Trunk interface is affected by the Eth-Trunk interface:

l If the shutdown command is run on the Eth-Trunk interface before or after the physical interface is
added, the physical status of the Eth-Trunk interface becomes Administratively DOWN.
Accordingly, the configuration file shows that the physical interface is shutdown and its physical
status is Administratively DOWN.
l If the undo shutdown command is run on the Eth-Trunk interface after the physical interface is
added, the configuration file shows that the physical interface is undo shutdown.
Do as follows as required:
Procedure
l To add one or more physical interfaces to an Eth-Trunk interface in the Eth-Trunk interface
view
1. Run:
system-view


2. Run:

3. Run the following command as required.
– trunkport interface-type { interface-number1 [ to interface-number2 ] }
&<1-16>
Interfaces are added to the Eth-Trunk interface in batches.

– trunkport interface-type interface-number
An interface is added to the Eth-Trunk interface.

A maximum of 16 interfaces can be added to or deleted from an Eth-Trunk interface
once.
l To add a physical interface to an Eth-Trunk interface in the view of the physical interface
1. Run:
system-view

2. Run:
The view of an interface to be added to an Eth-Trunk interface is displayed.

3. Run:
eth-trunk trunk-id
The interface is added to the Eth-Trunk interface.

Before adding interfaces to an Eth-Trunk interface, note the following points:
– An Eth-Trunk interface can have a maximum of 16 member interfaces.
– The interfaces cannot be configured with either Layer 3 configurations such as IP
addresses or services.
– The interfaces cannot be configured with static MAC addresses.
– The interfaces cannot be Eth-Trunk interfaces.
– An Ethernet interface can join only one Eth-Trunk interface. To join another Eth-
Trunk interface, the Ethernet interface must quit from the original Eth-Trunk first.
– Fast Ethernet and Gigabit Ethernet interfaces can be added to one Eth-Trunk
interface.
– Ethernet interfaces on different boards can be added to one Eth-Trunk interface.
– Before adding a Layer 2 interface on the router to an Eth-Trunk interface, you need
to run the undo portswitch command to switch it into a Layer 3 interface.
– An Eth-Trunk interface works in either Layer 2 mode or Layer 3 mode. An Ethernet
interface can be added to either a Layer 2 Eth-Trunk interface or a Layer 3 Eth-
Trunk interface.
– If an Eth-Trunk interface is created on a device, the peer device's interfaces that
are directly connected to the member interfaces of the Eth-Trunk interface must
be bound into an Eth-Trunk interface. Otherwise, the two devices cannot
communicate.
----End


After an Eth-Trunk interface in manual load balancing mode is successfully configured, you can
check information about the Eth-Trunk interface, including the Eth-Trunk ID, working mode,
and status of member interfaces.
Prerequisite
The configurations of an Eth-Trunk interface in manual load balancing mode are complete.
Procedure
Step 1 Run the display trunkmembership eth-trunk trunk-id command to check information about
Eth-Trunk member interfaces.
----End
Example
Run the display trunkmembership eth-trunk command. If information about the working
mode of the Eth-Trunk interface and the usage status of member interfaces is displayed, it means
that the configuration succeeds. For example:
<HUAWEI> display trunkmembership eth-trunk 1
Trunk ID: 1
used status: VALID
TYPE: ethernet
Working Mode : Normal
Working State: Normal
Number Of Ports in Trunk = 2
Number Of UP Ports in Trunk = 2
operate status: up
Interface GigabitEthernet1/0/0, valid, operate up, weight=1,

3.3 Configuring an Eth-Trunk Interface in 1:1 Active/

Standby Mode
Eth-Trunk interfaces in 1:1 active/standby mode can be configured on two devices so that data
can be transmitted over the links working in 1:1 backup mode.

Before configuring an Eth-Trunk interface in 1:1 active/standby mode, familiarize yourself with
the applicable environment, complete the pre-configuration tasks, and obtain the data required
for the configuration. This will help you complete the configuration task quickly and accurately.
On the network shown in Figure 3-4, Router A and Router D are NE80E/40E devices. The
transit device can receive Flush packets. Backup links are required to be configured between
Router A and Router D to ensure reliable data transmission.

Figure 3-4 Networking diagram for link aggregation in 1:1 active/standby mode
RouterB
RouterA RouterD
RouterC
Active links
Backup links
NOTE
In 1:1 active/standby mode, interfaces at different speeds, in different duplex modes, or on different boards
can be added to one Eth-Trunk interface.
Before configuring an Eth-Trunk interface in 1:1 active/standby mode, complete the following
task:
l Creating an Eth-Trunk interface
Data Preparation
To configure an Eth-Trunk interface in 1:1 active/standby mode, you need the following data.
No. Data
1 ID of the LAG of Router A and Router D
2 Type and number of each interface to be added to the Eth-Trunk interface
3 ID of the control VLAN that is used to send or receive Flush packets
3.3.2 Configuring an Eth-Trunk Interface to Work in 1:1 Active/

Standby Mode
Link aggregation in 1:1 active/standby mode provides a backup link for data transmission. One
Eth-Trunk interface has only two member interfaces, namely, an active interface and a standby
interface.

Context
NOTE
Ensure that an Eth-Trunk interface does not have any member interface before configuring the working
mode for the Eth-Trunk interface; otherwise, the working mode cannot be changed. To delete a member
interface, run the undo eth-trunk command in the interface view. For details, refer to the chapter "Link
Aggregation" in the Command Reference.
Layer 2 Eth-Trunk interfaces support the 1:1 active/standby mode, but Layer 3 Eth-Trunk interfaces do
not.
Do as follows on Router A and Router D:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
portswitch
The Eth-Trunk interface is switched from a Layer 3 interface to a Layer 2 interface.

Step 4 Run:
mode manual backup
The Eth-Trunk interface is configured to work in 1:1 active/standby mode.

----End
3.3.3 Adding Interfaces to an Eth-Trunk Interface and Setting the

Master Interface
After link aggregation in 1:1 active/standby mode is successfully configured, two interfaces need
to be added to each Eth-Trunk interface and set one interface as the master interface. In this
manner, links are in 1:1 backup mode.
Context
NOTE


Procedure
Step 1 Run:
system-view

Step 2 Run:
interface interface-type interface-number
The view of the interface to be added to an Eth-Trunk interface is displayed.

Step 3 Run:
eth-trunk trunk-id

In 1:1 active/standby mode, only two interfaces can be added to one Eth-Trunk interface.
NOTE
Before adding an interface to an Eth-Trunk interface, ensure that the interface does not have any
configuration. The display this command can be used to check the configurations of an interface. Except
for shutdown, undo shutdown, and description, the configurations must be deleted by using
corresponding undo commands.
Step 4 Run:
port-master
The member interface of the Eth-Trunk interface is specified as the master interface.
By default, each member interface of an Eth-Trunk interface in 1:1 active/standby mode is the
backup interface. Therefore, only the master interface needs to be specified.
Of the two member interfaces of an Eth-Trunk interface, only one interface can be specified as
the master interface.
----End
3.3.4 Enabling the Function of Sending Flush Packets

After the function of sending Flush packets is enabled and the master/backup interface
switchover is performed, Flush packets are sent by the new master interface to instruct the peer
to age MAC entries. This prevents service interruption caused by asynchronous MAC address
information.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
smart-link flush send vlan vlan-id
The function of sending Flush packets is enabled.
NOTE
The VLAN specified in this command is a control VLAN. After the command is used, Flush packets are
sent from the new master interface after a master/backup interface switchover to instruct the peer to age
MAC entries, thus preventing service interruption caused by asynchronous MAC address information.
----End
3.3.5 Creating a Control VLAN

A control VLAN is used to receive Flush packets sent between the two devices on which Eth-
Trunk interfaces in 1:1 active/standby mode are configured.
Context
Do as follows on Router B and Router C:
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
A VLAN is created and the VLAN view is displayed.
The VLAN is used to receive Flush packets sent by Router A or Router D. Therefore, the VLAN
ID must be the same as the VLAN ID used to send Flush packets.
----End
3.3.6 Enabling an Interface to Receive Packets from a Control VLAN

Intermediate devices must be enabled with the function of receiving packets from a control
VLAN. In this manner, a remote device can receive Flush packets, and then delete dynamic
MAC entries and ARP entries based on the Flush packets.
Context
Do as follows on the interfaces of active and standby links connecting to Router B and Router
C:
Procedure
Step 1 Run:
system-view

Step 2 Run:
Step 3 Run:
portswitch
The Ethernet interface is switched from a Layer 3 interface to a Layer 2 interface.
Step 4 Run:
port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] } & <1-10> | all }
The function of receiving packets from a control VLAN is enabled.
The VLAN ID used to receive Flush packets must be the same as the VLAN ID used to send
Flush packets.
----End
3.3.7 Enabling an Interface to Receive Flush Packets

Intermediate devices are able to process Flush packets only after being enabled with the function
of receiving Flush packets.
Context
Do as follows on the interfaces of active and standby links connecting to Router B and Router
C:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
smart-link flush enable control-vlan vlan-id
The function of receiving Flush packets is enabled.
----End

After an Eth-Trunk interface in 1:1 active/standby mode is successfully configured, you can
view the Eth-Trunk ID, working mode, and local member interface status of the Eth-Trunk
interface.

Prerequisite
The configurations of an Eth-Trunk interface in 1:1 active/standby mode function are complete.
Procedure
l Run the display trunkmembership eth-trunk trunk-id command to check the member
interfaces of the Eth-Trunk interface.
l Run the display eth-trunk [ trunk-id [ interface interface-type interface-number ] ]
command to check the working mode of the Eth-Trunk interface and the master and backup
member interfaces.
----End
Example
Use Router A as an example. Run the display trunkmembership eth-trunk command. If the
working mode is Backup and the master interface GigabitEthernet1/0/1 is Up, it means that the
configuration succeeds.
Trunk ID: 1
used status: VALID
TYPE: ethernet
Working Mode : Backup-access
operate status: up

Interface GigabitEthernet1/0/2, valid, operate down, weight=1,
<HUAWEI> display eth-trunk 1
Eth-Trunk1's state information is:
WorkingMode: BACKUP
WorkingState: Master
--------------------------------------------------------------------------------
PortName Slave/Master
GigabitEthernet1/0/1 M
GigabitEthernet1/0/2 S
3.4 Configuring an Eth-Trunk Interface in Static LACP

Mode
LACP provides a standard negotiation mode for the devices that exchange data. In this
negotiation mode, the system can automatically form aggregation links based on its
configuration and enable the aggregation links to receive and send data, which thus improves
fault tolerance. In addition, member links can work in M:N backup mode, ensuring reliable data
transmission.

Before configuring an Eth-Trunk interface in static LACP mode, familiarize yourself with the
applicable environment, complete the pre-configuration tasks, and obtain the data required for
the configuration. This will help you complete the configuration task quickly and accurately.

To increase bandwidth between two devices and improve reliability, you can configure an LAG
on the devices. After the configurations:
l The links between the two devices back up each other. After a fault occurs on a link, a
backup link replaces the faulty one to transmit data.
l Active links carry out load balancing.
Figure 3-5 Networking diagram for link aggregation in static LACP mode
Eth-Trunk
RouterA RouterB
Active links
Backup links
NOTE
In static LACP mode, interfaces at different speeds, in different duplex modes, and on different boards can
be added to one Eth-Trunk interface. Member interfaces at different speeds cannot be in the forwarding
state at the same time; member interfaces in half duplex mode cannot forward data.
Before configuring an Eth-Trunk interface in static LACP mode, complete the following task:
l Powering on the device and starting it normally.
Data Preparation
To configure an Eth-Trunk interface in static LACP mode, you need the following data.
No. Data
1 Number of the Eth-Trunk interface
2 Type and number of each member interface
3 Maximum number of active member interfaces
3.4.2 Creating an Eth-Trunk Interface

An Eth-Trunk ID uniquely identifies an Eth-Trunk link. Physical interfaces can be added to an
Eth-Trunk interface only after the Eth-Trunk interface is created.
Context
Do as follows on the device where an Eth-Trunk interface needs to be configured.

Procedure
Step 1 Run:
system-view
Step 2 Run:
----End
3.4.3 (Optional) Configuring a Working Mode for an Eth-Trunk

Interface
To transmit Layer 2 services, an Eth-Trunk interface needs to be switched into a Layer 2
interface.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
portswitch
The Layer 3 Eth-Trunk interface is switched into a Layer 2 interface.
After an Eth-Trunk interface is switched into a Layer 2 interface, its Layer 3 functions are
disabled and the interface is identified by the system MAC address.
An Eth-Trunk interface needs to be switched into a Layer 2 interface before being bound to a
VLAN. Before switching between working modes, delete all configurations of the Eth-Trunk
interface.
The undo portswitch command is used to switch a Layer 2 Eth-Trunk interface into a Layer 3
one.
NOTE
l The minimum interval between the portswitch command and the undo portswitch command is 30
seconds.
l The working mode of an Eth-Trunk interface does not affect the addition of interfaces. An Ethernet
interface can join either a Layer 2 Eth-Trunk interface or a Layer 3 Eth-Trunk interface.
----End

3.4.4 Configuring an Eth-Trunk Interface to Work in Static LACP

Mode
In addition to improving reliability and increasing bandwidth, an Eth-Trunk interface in static
LACP mode can automatically adjust or disassemble link aggregation.
Context
NOTE
Before configuring a working mode for an Eth-Trunk interface, ensure that the Eth-Trunk interface does
not have any member interface. Otherwise, the working mode cannot be changed. To delete an existing
member interface, run the undo eth-trunk command in the interface view. For details, see the chapter
"Link Aggregation" in the Command Reference.
Both Layer 2 and Layer 3 Eth-Trunk interfaces support the static LACP mode.
Do as follows on the devices at both ends:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
mode lacp-static
The Eth-Trunk interface is configured to work in static LACP mode.
----End
3.4.5 Adding Interfaces to an Eth-Trunk Interface

After an Eth-Trunk interface is successfully configured, interfaces need to be added to the Eth-
Trunk interface to increase bandwidth, improve reliability, and implement load balancing.
Context
NOTE

Do as follows as required:

Procedure
l To add one or more physical interfaces to an Eth-Trunk interface in the Eth-Trunk interface
view
1. Run:
system-view

2. Run:

3. Run the following command as required.
– trunkport interface-type { interface-number1 [ to interface-number2 ] }
&<1-16>
Interfaces are added to the Eth-Trunk interface in batches.

– trunkport interface-type interface-number
An interface is added to the Eth-Trunk interface.
A maximum of 16 interfaces can be added to or deleted from an Eth-Trunk interface

once.
l To add a physical interface to an Eth-Trunk interface in the view of the physical interface
1. Run:
system-view

2. Run:
The view of an interface to be added to an Eth-Trunk interface is displayed.

3. Run:
eth-trunk trunk-id
Before adding interfaces to an Eth-Trunk interface, note the following points:
– An Eth-Trunk interface can have a maximum of 16 member interfaces.

– The interfaces cannot be configured with either Layer 3 configurations such as IP
addresses or services.
– The interfaces cannot be configured with static MAC addresses.
– The interfaces cannot be Eth-Trunk interfaces.
– An Ethernet interface can join only one Eth-Trunk interface. To join another Eth-
Trunk interface, the Ethernet interface must quit from the original Eth-Trunk first.
– Fast Ethernet and Gigabit Ethernet interfaces can be added to one Eth-Trunk
interface.
– Ethernet interfaces on different boards can be added to one Eth-Trunk interface.
– Before adding a Layer 2 interface on the router to an Eth-Trunk interface, you need
to run the undo portswitch command to switch it into a Layer 3 interface.

– An Eth-Trunk interface works in either Layer 2 mode or Layer 3 mode. An Ethernet

interface can be added to either a Layer 2 Eth-Trunk interface or a Layer 3 Eth-
Trunk interface.
– If an Eth-Trunk interface is created on a device, the peer device's interfaces that
are directly connected to the member interfaces of the Eth-Trunk interface must
be bound into an Eth-Trunk interface. Otherwise, the two devices cannot
communicate.
----End
3.4.6 (Optional) Setting an LACP System Priority

LACP system priorities are used to prioritize devices. The device of a high LACP priority is
selected as the Actor, which determines active interfaces in the link aggregation group.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
lacp priority priority
The LACP system priority is set.
The smaller the priority value, the higher the LACP system priority.
The device with a smaller LACP system priority value functions as the Actor. By default, the
LACP system priority value is 32768. To make a device function as the Actor, set its LACP
system priority value to be smaller than 32768, leaving the LACP system priority value of the
peer device unchanged.
----End
3.4.7 (Optional) Setting the Maximum Number of Active Member

Interfaces
After the maximum number of active member interfaces is set for an Eth-Trunk interface, adding
more interfaces to the Eth-Trunk interface does not increase the number of its active member
interfaces.
Context
In static LACP mode, after the maximum number of active member interfaces is set to M, the
remaining member interfaces are in the standby state.
If the upper threshold is not configured, a maximum of 16 member interfaces of an Eth-Trunk

interface can be in the active state.

NOTE
The maximum number of active member interfaces set for one device can be different from that set for the
peer device. In this case, the maximum number of active member interfaces is subject to the smaller one.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
max active-linknumber link-number
The maximum number of active member interfaces is set.

By default, the maximum number of active member interfaces is 16.
----End
3.4.8 (Optional) Setting an LACP Interface Priority

LACP interface priorities are used to prioritize member interfaces of an Eth-Trunk interface.
Interfaces of high priorities are selected as active interfaces.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
lacp priority priority
The interface is configured with an LACP priority value.
NOTE
Active member interfaces are selected based on LACP interface priorities. The smaller the priority value,
the higher the LACP interface priority. By default, the LACP interface priority value is 32768.
----End

3.4.9 (Optional) Configuring the Mode for Selecting Active

Member Interfaces
As defined in LACP, active member interfaces are selected based on interface LACP priorities.
In certain cases, low-speed member interfaces may be selected. To make the system select only
high-speed member interfaces, configure the mode for selecting active member interfaces.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
lacp selected { priority | speed }
The mode for selecting active member interfaces is configured.

As defined in LACP, active member interfaces are selected based on interface LACP priorities.
In certain cases, low-speed member interfaces are selected. To make the system select only high-
speed member interfaces, run the lacp selected speed command.
By default, member interfaces of high LACP priorities are selected as active member interfaces.
NOTE
To ensure that Eth-Trunk interfaces work normally, configure the same mode for selecting active member
interfaces for both ends of an Eth-Trunk link.
----End
3.4.10 (Optional) Enabling LACP Preemption and Setting an LACP

Preemption Delay
After LACP preemption is enabled, Eth-Trunk member interfaces with high priorities are always
active interfaces.
Context
Procedure
Step 1 Run:
system-view


Step 2 Run:

Step 3 Run:
lacp preempt enable
LACP preemption is enabled.

If LACP preemption is enabled, member interfaces with high LACP priorities are always active
interfaces. For example, if LACP preemption is enabled, an interface with a high priority
becomes active immediately after it recovers; if LACP preemption is disabled, the interface
cannot become active after it recovers.
NOTE
Enabling or disabling LACP preemption for both ends of an Eth-Trunk link is recommended.
Step 4 Run:
lacp preempt delay delay-time
An LACP preemption delay is set.

The LACP preemption delay is a period of time before an inactive member interface of an Eth-
Trunk interface in static LACP mode becomes active.
LACP preemption delays set for the two ends may be different. In this case, the system uses the
longer one.
----End
3.4.11 (Optional) Setting a Timeout Period for Receiving LACPDUs

After a timeout period for receiving LACPDUs is set, the local end sends an LACPDU to inform
the peer of the timeout period.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
lacp timeout { fast | slow }
A timeout period for receiving LACPDUs is set.

By default, the timeout period for receiving LACPDUs is 90 seconds (slow).
NOTE
l After the command is used, the local end sends an LACPDU to inform the peer of the timeout period
for receiving LACPDUs.
l If fast is configured, the timeout period for receiving LACPDUs is 3 seconds, and the peer sends
an LACPDU every second.
l If slow is configured, the timeout period for receiving LACPDUs is 90 seconds, and the peer sends
an LACPDU every 30 seconds.
l Timeout periods set for the two ends can be different. Setting the same timeout period for the two ends
to receive LACPDUs is recommended to facilitate maintenance.
----End

After an Eth-Trunk interface in static LACP mode is successfully configured, you can view
information about the Eth-Trunk interface, including the Eth-Trunk ID, working mode, status
of each member interface, LACP system priority, LACP priority of each member interface, and
LACP preemption delay.
Prerequisite
The configurations of an Eth-Trunk interface in static LACP mode are complete.
Procedure
l Run the display trunkmembership eth-trunk trunk-id command to check information
about member interfaces of the Eth-Trunk interface.
l Run the display eth-trunk [ trunk-id [ interface interface-type interface-number ] ]
command to check information about the Eth-Trunk interface and its active member
interfaces.
----End
Example
Run the display trunkmembership eth-trunk command. If the working mode, LACP system
priority, LACP interface priority, and active member interfaces are displayed, it means that the
configuration succeeds.
Local:
LAG ID: 1 WorkingMode: STATIC
Preempt Delay: Disabled Hash arithmetic: According to flow
System Priority: 60 System ID: 00e0-fca8-041a
Least Active-linknumber: 1 Max active-linknumber: 3
Operate status: up Number Of Up Port In Trunk: 3
------------------------------------------------------------------------------
ActorPortName Status PortType PortPri PortNo PortKey PortState
Weight
GigabitEthernet3/0/3 Selected 1GE 32768 387 561 11111100
1
1
1
GigabitEthernet1/0/0 Unselect 10GE 32768 64 577 11100000

1
GigabitEthernet2/0/0 Unselect 10GE 32768 192 577 11100010
1
Partner:
------------------------------------------------------------------------------
ActorPortName SysPri SystemID PortPri PortNo PortKey
PortState
GigabitEthernet3/0/3 32768 00e0-fca6-7f85 32768 387 561
11111100
11111100
11111100
11100000
GigabitEthernet2/0/0 0 0000-0000-0000 0 0 0
11100011
Trunk ID: 1
used status: VALID
TYPE: ethernet
Working Mode : Static
operate status: up

3.5 Associating an Eth-Trunk Interface in Static LACP Mode

with an mVRRP Backup Group
the Eth-Trunk interface can detect the status change in the mVRRP backup group, and thus
rapidly switch traffic to an available path. This ensures reliable data transmission.

Before associating an Eth-Trunk interface in static LACP mode with an mVRRP backup group,
familiarize yourself with the applicable environment, complete the pre-configuration tasks, and
obtain the data required for the configuration. This will help you complete the configuration task
quickly and accurately.
Reliable networking usually involves both device-level reliability and link-level reliability
techniques. If VRRP is used to provide device-level reliability and the trunk technique is used
to provide link-level reliability, the device switchover and link switchover may not be performed
simultaneously after a fault occurs on the master device or the active link. As a result, traffic is
interrupted. To prevent such a problem, you can associate a trunk interface with a VRRP backup
group.

Figure 3-6 Typical networking for a CE dual-homed to UPEs
IP/MPLS IP/MPLS
Core Core
UPE1 UPE2 UPE1 UPE2

VRRP
CE CE
Active link
Standby link
Eth-Trunk interface
VRRP-tracked interface
As shown in Figure 3-6, a CE is dual-homed to UPEs. UPEs are configured with VRRP so that
UPE1 and UPE2 function as the master and backup devices respectively. In addition, the physical
links between the CE and UPEs are bundled into Eth-Trunk links to improve link reliability and
increase bandwidth.
To implement the integrated networking, you need to ensure that the device switchover and the
link switchover are performed at the same time. When UPE1 functions as the master device, the
link between CE1 and UPE1 must be the active link; otherwise, traffic is interrupted. For
example, if UPE1 becomes backup while the link between CE1 and UPE1 is the active link,
traffic is still transmitted along this link to UPE1. However, the backup device UPE1 does not
forward packets. As a result, traffic is interrupted.

NOTE
l The point-to-point (P2P) Eth-Trunk technique can be used in this point-to-multipoint (P2MP)
networking because VRRP is configured on UPEs so that the UPEs are grouped to function as a virtual
router. Therefore, this networking can be considered as a P2P networking.
l Eth-Trunk interfaces configured on the CE and UPEs must work in static LACP mode. This is because
the master/backup UPEs require the active/standby links, and only Eth-Trunk interfaces in static LACP
mode can work in either active or standby mode.
l An mVRRP backup group must be configured on directly-connected UPEs to implement a fast
switchover in the VRRP backup group.
An mVRRP backup group is able to ignore the event that the interface goes Down. If the interface
where the mVRRP backup group resides goes Down, the mVRRP backup group rapidly changes to
Master but not Initialize.
For detailed information about VRRP, see the chapter that describes VRRP principles in the NE80E/
40E Feature Description - Reliability.
VRRP is able to monitor the status of the local device. After being configured to track interface
status, VRRP monitors the status of upstream and downstream interfaces on UPEs. If the master
device or the active link fails, the backup device and the standby link become master and active
at the same time. In the following situations, however, the switchover cannot be performed
synchronously:
l If the upstream interface of the master UPE fails, the device switchover is performed but
the link switchover does not take place.
l If the device switchover is performed after the priority of a UPE is changed, the link
switchover does not take place.
To prevent traffic interruption caused by asynchronous switchovers in such an integrated

networking, Huawei develops the technique to associate an Eth-Trunk interface in static LACP
mode with an mVRRP backup group.
On a network where the interface connecting the master device to the upstream device fails or
on a trouble-free network, when the master device in the mVRRP backup group changes to
backup, the Eth-Trunk interface associated with the mVRRP backup group can detect the status
change in the mVRRP backup group and thus perform the link switchover between Eth-Trunk
member links. This ensures reliable data transmission.
NOTE
On a dual-homing network, you can either associate an Eth-Trunk interface in static LACP mode with an
mVRRP backup group or use the E-Trunk technique to implement both device-level and link-level
reliability. For E-Trunk configurations, see 3.9 Configuring E-Trunk.
Before associating an Eth-Trunk interface in static LACP mode with an mVRRP backup group,
complete the following tasks:
l 3.4 Configuring an Eth-Trunk Interface in Static LACP Mode

l Configuring mVRRP Backup Groups
Data Preparation
To associate an Eth-Trunk interface in static LACP mode with an mVRRP backup group, you
need the following data.

No. Data
2 Type and number of each member interface
3 ID of the VRRP backup group
4 VRRP priority of each UPE
5 Virtual IP address of the VRRP backup group
6 ID of the mVRRP backup group
3.5.2 Configuring VRRP to Track the Status of a Member Interface

of an Eth-Trunk Interface in Static LACP Mode
If VRRP is configured to track the status of a member interface of an Eth-Trunk interface, after
the member interface fails, VRRP can detect the fault and carry out the device switchover in the
VRRP backup group.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the interface where the VRRP backup group resides is displayed.
Step 3 Run:
vrrp vrid virtual-router-id track interface interface-type interface-number
[ increased value-increased | reduced value-reduced ]
A VRRP backup group is configured to track the status of the member interface.
By default, if the tracked interface goes Down, the VRRP priority value of the device reduces
by 10.
A VRRP backup group can track a maximum of eight interfaces in either Increase or Reduce
mode.
l In Increase mode, after the tracked interface goes Down, the VRRP priority value of the
device where the tracked interface resides increases.
increased value-increased specifies the value by which the VRRP priority value increases
once the tracked interface goes Down. The value is an integer ranging from 1 to 255. This
parameter takes effect only when the device is the backup device in the VRRP backup group.
l In Reduce mode, after the tracked interface goes Down, the VRRP priority value of the device
where the tracked interface resides decreases.
reduced value-reduced specifies the value by which the VRRP priority value decreases once
the tracked interface goes Down. The value is an integer ranging from 1 to 255.

If the VRRP priority of either device reduces to 0, the device switchover will be performed
in the VRRP backup group.
l The interface specified by interface interface-type interface-number must be a member
interface of an Eth-Trunk interface in static LACP mode.
NOTE
For detailed information about VRRP tracking interface status, see Configuring VRRP to Track the Status
of an Interface.
----End
3.5.3 Associating an Eth-Trunk Interface in Static LACP Mode with

an mVRRP Backup Group
Before associating an Eth-Trunk interface with a VRRP backup group, ensure that the Eth-Trunk
interface works in static LACP mode and the VRRP backup group is an mVRRP backup group.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of an Eth-Trunk interface in static LACP mode is displayed.

Step 3 Run:
lacp track vrrp vrid vrid interface interface-type interface-number
The Eth-Trunk interface in static LACP mode is associated with an mVRRP backup group.
l vrid vrid must specify an mVRRP backup group.
l The interface specified by interface interface-type interface-number must have been
configured with the mVRRP backup group.
----End

the Eth-Trunk link switchover is performed along with the device switchover in the mVRRP
backup group.
Prerequisite
The configurations of associating an Eth-Trunk interface in static LACP mode with an mVRRP
backup group are complete.
Procedure
Step 1 Run the display vrrp [ interface interface-type interface-number [ virtual-router-id ] ]
[ brief ] command to check the status and configurations of the VRRP backup group.

Step 2 Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ] ]
command to check the configurations of the Eth-Trunk interface in static LACP mode and
information about its member interfaces.
----End
Example
Run the display vrrp command. If the status and type of the VRRP backup group as well as the
type, number, and status of the tracked interface are displayed, it means that the configuration
succeeds.
<HUAWEI> display vrrp
GigabitEthernet1/0/3 | Virtual Router 1
State : Master
Virtual IP : 1.1.1.10
Master IP : 1.1.1.1
PriorityRun : 120
PriorityConfig : 120
MasterPriority : 120
Preempt : YES Delay Time : 0
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Config type : admin-vrrp
Track IF : GigabitEthernet1/0/1 priority reduced : 40
IF State : UP
IF State : UP
Config track link-bfd down-number : 0
Run the display eth-trunk command. If the working mode of the Eth-Trunk interface and
information about its member interfaces are displayed, it means that the configuration succeeds.
Local:
System Priority: 32768 System ID: 00e0-6923-4900
Least Active-linknumber: 1 Max Active-linknumber: 16
--------------------------------------------------------------------------------
ActorPortName Status PortType PortPri PortNo PortKey PortState Weight
GigabitEthernet1/0/1 Selected 1GE 32768 257 5169 10111100 1
Partner:
--------------------------------------------------------------------------------
PortState
GigabitEthernet1/0/1 32768 00e0-b94e-fb00 32768 257 2609 10111100
3.6 Configuring Layer 2 Attributes for an Eth-Trunk

Interface
Layer 2 attributes define link layer attributes for an Eth-Trunk interface.


Before configuring Layer 2 attributes for an Eth-Trunk interface, familiarize yourself with the
Before adding an Eth-Trunk interface to a VLAN, you need to configure Layer 2 attributes for
the Eth-Trunk interface.
Layer 2 Eth-Trunk interfaces are mainly used to increase bandwidth for communication between
devices in different VLANs.
Configuration procedures in this section are optional.
Before configuring Layer 2 attributes for an Eth-Trunk interface, complete the fallowing tasks:
l Configuring an Eth-Trunk Interface in Manual Load Balancing Mode

l Configuring an Eth-Trunk Interface in Static LACP Mode
Data Preparation
To configure Layer 2 attributes for an Eth-Trunk interface, you need the following data.
No. Data
1 Eth-Trunk ID
2 Type and number of each Eth-Trunk member interface
3 Upper and lower thresholds of Up member links
4 Weight of each member interface
5 Mode for Eth-Trunk member interfaces to send trap messages
3.6.2 (Optional) Configuring the Minimum Number of Up Member

Links
After the number of Up member links falls below the minimum number, the Eth-Trunk link goes
Down. Configuring the minimum number of Up member links guarantees the minimum
bandwidth provided by the Eth-Trunk link.
Procedure
Step 1 Run:
system-view

Step 2 Run:
Step 3 Run:
portswitch
The Layer 3 Eth-Trunk interface is switched to the Layer 2 mode.
Step 4 Run:
least active-linknumber link-number
The minimum number of Up member links is set.
The default value is 1. That is, the Eth-Trunk link is Up as long as one member link is Up.
NOTE
l The minimum number of Up member links can be configured on both Layer 2 and Layer 3 Eth-Trunk
interfaces.
l Configuring the same minimum number of Up member links for Eth-Trunk interfaces at the two ends
of a link is recommended for data transmission.
----End
3.6.3 (Optional) Configuring the Maximum Number of Up Member

Links
After the number of Up member links reaches the upper threshold, the bandwidth of the Eth-
Trunk link does not increase even if more member links go Up. This ensures high network
reliability and guarantees sufficient bandwidth.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
portswitch
Step 4 Run:
max bandwidth-affected-linknumber link-number
The maximum number of Up member links is set.
The default value is 16.

NOTE
The max bandwidth-affected-linknumber command can be configured only on Layer 2 Eth-Trunk

interfaces.
----End
3.6.4 (Optional) Configuring an Eth-Trunk Interface to Carry Out

Load Balancing
Configuring a load balancing mode ensures bandwidth utilization or orderly packet transmission.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
portswitch
Step 4 Run:
load-balance { src-dst-mac | src-dst-ip | packet-all }
A load balancing mode is configured for the Eth-Trunk interface.
By default, Layer 3 Eth-Trunk interfaces carry out load balancing based on IP addresses; Layer
2 Eth-Trunk interfaces carry out load balancing based on MAC addresses.
To ensure the bandwidth usage of each member link, configure packet-all to allow the Eth-
Trunk interface to carry out per-packet load balancing.
l Per-packet load balancing distributes traffic among member links. Data is transmitted packet
by packet.
l Per-packet load balancing guarantees bandwidth usage of each member link, but not orderly
packet transmission. Therefore, it is applicable to the scenario where orderly packet
transmission is not strictly required.
l Layer 3 Eth-Trunk interfaces cannot carry out load balancing based on MAC addresses.
To ensure that packets arrive at the destination in sequence, configure src-dst-ip, src-dst-mac
to allow the Eth-Trunk interface to carry out per-destination load balancing.
l Per-destination load balancing differentiates data flows based on MAC addresses or IP

addresses and allows packets of one data flow to be transmitted through the same member
link.
l Per-destination load balancing guarantees orderly data transmission, but not the bandwidth
usage of each member link.
----End

3.6.5 (Optional) Configuring Weights for Member Interfaces

Member interfaces of an Eth-Trunk interface can be configured with different weights to carry
out load balancing.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The view of an Eth-Trunk member interface is displayed.
Step 3 Run:
distribute-weight weight-value
A weight is configured for the interface.
For an Eth-Trunk interface, the sum of weights of all its member interfaces cannot be greater
than 16. The Eth-Trunk interface implements load balancing based on the weight of each member
interface.
On an Eth-Trunk interface, the greater the weight of a member interface is, the heavier traffic
the member interface carries.
By default, the weight of a member interface is 1.
NOTE
If an Eth-Trunk interface transmits multicast traffic and the distribute-weight command is used to change
the load balancing weight for a member interface, run the shutdown and undo shutdown commands to
restart the member interface to make the configuration take effect.
----End
3.6.6 (Optional) Configuring the Mode for Eth-Trunk Member

Interfaces to Send Traps
After an Eth-Trunk member interface goes Up or Down, the trap sent by using a public MIB
does not carry information about the Eth-Trunk interface. To allow the trap to carry information
about the Eth-Trunk interface, you can configure traps to be sent by using a private MIB.
Context
Do as follows on the devices at both ends.
Procedure
Step 1 Run:
system-view

Step 2 Run:
trunk-member trap in private-mib enable
Eth-Trunk member interfaces are configured to send traps by using a private MIB after Eth-
Trunk member interfaces go Up or Down.
By default, traps are sent by using a public MIB after Eth-Trunk member interfaces go Up or
Down.
Traps sent by using a public MIB do not carry information about the Eth-Trunk interface. To
allow traps to carry information about the Eth-Trunk interface, use this command to change the
mode for sending traps by using a private MIB.
----End

After Layer 2 attributes are successfully configured for an Eth-Trunk interface, you can view
brief information about the Eth-Trunk interface, including physical status, protocol status, and
interface bandwidth utilization.
Prerequisite
The configurations of Layer 2 attributes for an Eth-Trunk interface are complete.
Procedure
l Run the display interface eth-trunk [ trunk-id ] command to check the Eth-Trunk interface
status.
l Run the display interface brief command to check brief information about the Eth-Trunk
interface, including physical status, protocol status, and bandwidth utilization.
----End
Example
Run the display interface eth-trunk command. If information about the Eth-Trunk interface,
including the IP address, MAC address, and load balancing mode, is displayed, it means that the
configuration succeeds. For example:
<HUAWEI> display interface Eth-Trunk 1
Eth-Trunk1 current state : UP
Last line protocol up time: 2008-04-02, 11:00:19
Description : Eth-Trunk1 Interface
Route Port,Hash arithmatic : According to flow,The Maximum Transmit Unit is 1500
Internet protocol processing : disabled
Physical is ETH_TRUNK
Current system time: 2010-08-29 20:26:18
Statistics last cleared: 2008-08-02 15:32:27
Last 300 seconds input rate 0 bytes/sec, 0 packets/sec
Last 300 seconds output rate 0 bytes/sec, 0 packets/sec
Realtime 0 seconds input rate 0 bits/sec, 0 packets/sec
Realtime 0 seconds output rate 0 bits/sec, 0 packets/sec
Input: 1 packets,3 bytes,
7 unicast,9 broadcast,8 multicasts
10 errors,5 drops,11 unknowprotocol
Output: 2 packets,4 bytes,
12 unicast,14 broadcast,13x multicasts

15 errors,6 drops
-----------------------------------------------------
PortName Status Weight
-----------------------------------------------------
GigabitEthernet1/0/1 UP 1
-----------------------------------------------------
The Number of Ports in Trunk : 2
The Number of UP Ports in Trunk : 2
Run the display interface brief command. If the brief information about the Eth-Trunk interface,
including the physical status, link protocol status, bandwidth utilization, and error packet
number, is displayed, it means that the configuration succeeds. For example:
<HUAWEI> display interface brief | begin Eth-Trunk
PHY: Physical
^down: standby
(l): loopback
(s): spoofing
(b): BFD down
(d): Dampening Suppressed
InUti/OutUti: input utility/output utility
Interface PHY Protocol InUti OutUti inErrors outErrors
Eth-Trunk1 up up 0% 0% 0 0
GigabitEthernet2/0/1 up up 0% 0% 0 0
GigabitEthernet3/0/1 up up 0% 0% 0 0
Eth-Trunk1.1 up up 0% 0% 0 0
3.7 Configuring Layer 3 Attributes for an Eth-Trunk

Interface
To use an Eth-Trunk interface to transmit Layer 3 packets, you need to configure Layer 3
attributes for the Eth-Trunk interface.

Before configuring Layer 3 attributes for an Eth-Trunk interface, familiarize yourself with the
To use an Eth-Trunk interface as a Layer 3 interface, you need to configure Layer 3 attributes
for the Eth-Trunk interface.
Before configuring Layer 3 attributes for an Eth-Trunk interface, complete the following task:
Data Preparation
Before configuring Layer 3 attributes for an Eth-Trunk interface, you need the following data.

No. Data
1 IP address of the Eth-Trunk interface
2 MAC address of the Eth-Trunk interface
3 Minimum number of Up member links
4 Weight of each member interface
3.7.2 Configuring an IP address for an Eth-Trunk Interface

IP addresses are assigned to Eth-Trunk interfaces for communication between network devices.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
ip address ip-address { mask | mask-length } [ sub ]
An IP address is assigned to the Eth-Trunk interface.
----End
3.7.3 (Optional) Configuring a MAC Address for an Eth-Trunk

Interface
If multiple Layer 3 Eth-Trunk interfaces on the router are connected to Layer 2 interfaces on a
switch, the Layer 3 Eth-Trunk interfaces must be configured with MAC addresses to ensure that
packets from the switch can be correctly sent to the Layer 3 Eth-Trunk interfaces.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
mac-address mac-address

A MAC address is configured for the Eth-Trunk interface.
NOTE
The mac-address command is available for only Layer 3 Eth-Trunk interfaces.

If the MAC address of an Eth-Trunk interface that has a large number of sub-interfaces is changed, many
ARP update packets will be sent to the peer. If the peer is configured with CP CAR, increase the bandwidth
for ARP packets to prevent the loss of ARP update packets.
----End
3.7.4 (Optical) Configuring the MTU for an Eth-Trunk Interface

Configuring the maximum transmission unit (MTU) for each Eth-Trunk interface to ensure
communications between network devices.
Procedure
Step 1 Run:
system-view
Step 2 Run:
By default, the Eth-Trunk interface works in Layer 3 mode.
Step 3 Run:
mtu mtu
The MTU is set for the Eth-Trunk interface.
The MTU is expressed in bytes.
By default, the MTU is 1500 bytes.
CAUTION
l Layer 2 Eth-Trunk interfaces cannot be configured with MTUs.
l Interfaces at both ends of a directly-connected link must be the same. If the mtu command
is used to change the MTU of an interface, use this command to change the MTU of the peer
interface. Otherwise, there is a possibility that services are interrupted.
l If IPv6 runs on an Eth-Trunk interface, running the mtu command to set the MTU value to
be smaller than 1280 bytes will cause IPv6 unable to work properly on this interface. To
prevent such a problem, setting the MTU to a value not less than 1280 bytes is recommended
for an Eth-Trunk interface that uses IPv6.
----End

3.7.5 (Optional) Configuring the Minimum Number of Up Member

Links
If the number of Up member links of an Eth-Trunk link falls below the minimum number, the
Eth-Trunk link goes Down. Configuring the minimum number of Up member links guarantees
the minimum bandwidth provided by the Eth-Trunk link.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
least active-linknumber link-number
The minimum number of Up member links is configured.
The default value is 1. That is, the Eth-Trunk link is Up as long as one member link is Up.
NOTE
l The minimum number of Up member links can be configured on both Layer 2 and Layer 3 Eth-Trunk
interfaces.
l Configuring the same minimum number of Up member links for Eth-Trunk interfaces at the two ends
of a link is recommended for data transmission.
----End
3.7.6 (Optional) Configuring a Load Balancing Mode for an Eth-

Trunk Interface
Configuring a load balancing mode ensures bandwidth utilization or orderly packet transmission.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
load-balance { src-dst-mac | src-dst-ip | packet-all }
A load balancing mode is configured for the Eth-Trunk interface.

By default, Layer 3 Eth-Trunk interfaces carry out load balancing based on IP addresses; Layer
2 Eth-Trunk interfaces carry out load balancing based on MAC addresses.
To ensure the bandwidth usage of each member link, configure packet-all to allow the Eth-
Trunk interface to carry out per-packet load balancing.
l Per-packet load balancing distributes traffic among member links. Data is transmitted packet
by packet.
l Per-packet load balancing guarantees bandwidth usage of each member link, but not orderly
packet transmission. Therefore, it is applicable to the scenario where orderly packet
transmission is not strictly required.
l Layer 3 Eth-Trunk interfaces cannot carry out load balancing based on MAC addresses.
To ensure that packets arrive at the destination in sequence, configure src-dst-ip, src-dst-mac
to allow the Eth-Trunk interface to carry out per-destination load balancing.
l Per-destination load balancing differentiates data flows based on MAC addresses or IP

addresses and allows packets of one data flow to be transmitted through the same member
link.
l Per-destination load balancing guarantees orderly data transmission, but not the bandwidth
usage of each member link.
----End
3.7.7 (Optional) Configuring Weights for Member Interfaces

Member interfaces of an Eth-Trunk interface can be configured with different weights to carry
out load balancing.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The view of an Eth-Trunk member interface is displayed.
Step 3 Run:
distribute-weight weight-value
A weight is configured for the interface.
For an Eth-Trunk interface, the sum of weights of all its member interfaces cannot be greater
than 16. The Eth-Trunk interface implements load balancing based on the weight of each member
interface.
On an Eth-Trunk interface, the greater the weight of a member interface is, the heavier traffic
the member interface carries.
By default, the weight of a member interface is 1.

NOTE
If an Eth-Trunk interface transmits multicast traffic and the distribute-weight command is used to change
the load balancing weight for a member interface, run the shutdown and undo shutdown commands to
restart the member interface to make the configuration take effect.
----End
3.7.8 (Optional) Configuring the Load Balancing Mode for Access

Users on an Eth-Trunk Interface
Load balancing can be implemented among member interfaces of an Eth-Trunk interface based
on the traffic volume of access users or the number of access users.
Context
NOTE
The load balancing mode for access users on an Eth-Trunk interface cannot be configured on the X1 models
of the NE80E/40E series.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
bas-load-balance { flow-mode | user-mode }
The load balancing mode is configured on the Eth-Trunk interface for access users.
The router supports the configuration of a load balancing mode based on the traffic volume of
access users or the number of access users.
When users get online, the control plane identifies different user traffic based on the HQoS
configurations and the status of online users, and then distributes traffic to member interfaces
of the Eth-Trunk interface to minimize the number of access users on each member interface or
to maximize the remaining bandwidth of each member interface.
By default, an Eth-Trunk interface implements load balancing based on the number of access
users.
----End
3.7.9 (Optional) Configuring the Mode for Eth-Trunk Member

Interfaces to Send Traps
After an Eth-Trunk member interface goes Up or Down, the trap sent by using a public MIB
does not carry information about the Eth-Trunk interface. To allow the trap to carry information
about the Eth-Trunk interface, you can configure traps to be sent by using a private MIB.

Context
Do as follows on the devices at both ends.
Procedure
Step 1 Run:
system-view

Step 2 Run:
trunk-member trap in private-mib enable
Eth-Trunk member interfaces are configured to send traps by using a private MIB after Eth-
Trunk member interfaces go Up or Down.
By default, traps are sent by using a public MIB after Eth-Trunk member interfaces go Up or
Down.
Traps sent by using a public MIB do not carry information about the Eth-Trunk interface. To
allow traps to carry information about the Eth-Trunk interface, use this command to change the
mode for sending traps by using a private MIB.
----End

After Layer 3 attributes are successfully configured for an Eth-Trunk interface, you can view
information about the Eth-Trunk interface, including the interface status, information about its
member interfaces, and the forwarding table for the Eth-Trunk interface.
Prerequisite
The configurations of Layer 3 attributes for an Eth-Trunk interface are complete.
Procedure
l Run the display interface eth-trunk [ trunk-id ] command to check the status of the Eth-
Trunk interface.
l Run the display trunkmembership eth-trunk trunk-id command to check information
about member interfaces of the Eth-Trunk interface.
l Run the display trunkfwdtbl eth-trunk trunk-id [ slot slot-id ] command to check the
forwarding table for the Eth-Trunk interface.
----End
Example
Run the display interface eth-trunk command. If information about the Eth-Trunk interface,
such as the IP address, MAC address, and load balancing mode, is displayed, it means that the
<HUAWEI> display interface Eth-Trunk 1

Description : Eth-Trunk1 Interface, Route Port

Route Port,Hash arithmatic : According to flow,The Maximum Transmit Unit is 1500
Statistics last cleared: 2008-08-02 15:32:27
15 errors,6 drops
-----------------------------------------------------
-----------------------------------------------------
-----------------------------------------------------
Run the display trunkmembership eth-trunk command. If the usage and working modes of
member interfaces are displayed, it means that the configuration succeeds. For example:
Trunk ID: 0
used status: VALID
TYPE: ethernet
operate status: up

Run the display trunkfwdtbl eth-trunk command. If the number of the interfaces on the active
and standby Eth-Trunk member links is displayed, it means that the configuration succeeds. For
example:
<HUAWEI> display trunkfwdtbl eth-trunk 1
Show the Trunk Forwarding Table
Eth-Trunk1's forwarding table is:
MASTER SLAVE
GigabitEthernet1/0/0 GigabitEthernet1/0/0

3.8 Configuring an Eth-Trunk Sub-interface

interfaces. Creating a sub-interface on a Layer 2 Eth-Trunk interface and then configuring MPLS
TE on the sub-interface enable a physical link to transmit both Layer 2 and Layer 3 services.

Before configuring an Eth-Trunk sub-interface, familiarize yourself with the applicable
environment, complete the pre-configuration tasks, and obtain the data required for the
configuration. This will help you complete the configuration task quickly and accurately.
interfaces.
NOTE
l For applications of Eth-Trunk sub-interfaces in a VLAN, see VLAN Configuration.

l For applications of Eth-Trunk sub-interfaces in QinQ, see QinQ Configuration.
In addition to the preceding applications, Layer 2 Eth-Trunk sub-interfaces can be used in the
following situation:
If MPLS TE is required and devices are connected by using Layer 2 Eth-Trunk interfaces that
cannot be configured with MPLS TE, you can configure a sub-interface on the Layer 2 Eth-
Trunk interface and configure MPLS TE on the sub-interface. In this manner, a physical link
can transmit both Layer 2 and Layer 3 services.
Before configuring an Eth-Trunk sub-interface, complete the following tasks:

l Using physical links to connect devices
Data Preparation
To configure an Eth-Trunk sub-interface, you need the following data.
No. Data
2 Number of the Eth-Trunk sub-interface
3 VLAN ID associated with the sub-interface
4 Rate at which gratuitous ARP packets are sent

3.8.2 Creating an Eth-Trunk Sub-interface

If a Layer 3 device uses an Eth-Trunk interface to connect to a Layer 2 device, a sub-interface
needs to be created on the Eth-Trunk interface to make the two devices communicate with each
other.
Procedure
l Creating a Layer 3 Eth-Trunk sub-interface
1. Run:
system-view

2. Run:
interface eth-trunk trunk-id.subnumber
A sub-interface is created and the sub-interface view is displayed.

subnumber specifies the number of the Eth-Trunk sub-interface. The number ranges
from 1 to 4096.
l Creating a Layer 2 Eth-Trunk sub-interface
1. Run:
system-view

2. Run:
A Layer 3 Eth-Trunk interface is created.

3. Run:
portswitch

4. Run:
A sub-interface is created for the Layer 2 Eth-Trunk interface.

----End
3.8.3 Configuring an IP address for an Eth-Trunk Sub-interface

IP addresses are assigned to Eth-Trunk sub-interfaces for communication between network
devices.
Procedure
Step 1 Run:
system-view

Step 2 Run:

interface eth-trunk interface-number.subinterface-number
The Eth-Trunk sub-interface view is displayed.
Step 3 Run:
An IP address is assigned to the Eth-Trunk sub-interface.
For details about IP address configuration, see the HUAWEI NetEngine80E/40E Router
Configuration Guide - IP Services.
If two or more IP addresses are configured for an Eth-Trunk interface, the keyword sub must
be used to indicate the second ip address and the following ip addresses.
----End
3.8.4 Configuring the Encapsulation Type for an Eth-Trunk Sub-

interface
If a Layer 3 device uses an Eth-Trunk sub-interface to connect to a Layer 2 device and the Eth-
Trunk interface connecting the Layer 2 device to the Layer 3 device has been added to a specified
VLAN, configure the encapsulation type for the Eth-Trunk sub-interface on the Layer 3 device
for communication between the two devices.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
vlan-type dot1q vlan-id
The encapsulation type and associated VLAN ID are configured for the Eth-Trunk sub-interface.
NOTE
An Eth-Trunk sub-interface on the NE80E/40E can be associated with one VLAN.

For the configuration about sub-interfaces for dot1q or QinQ VLAN tag termination, see QinQ
Configuration.
By default, a sub-interface is not configured with any encapsulation type or VLAN ID.
For communication in a VLAN, the interfaces at the two ends of a link must be configured with
the same VLAN ID.
VLAN IDs configured for the Layer 2 Eth-Trunk interface and its sub-interface must be different.
----End

3.8.5 (Optical) Configuring the MTU for an Eth-Trunk Sub-

interface
Configuring a proper MTU is the prerequisite for communication between network devices.
Context
NOTE
If the mtu command is used to change the MTU of an interface, run this command on each peer interface
to change its MTU to the same value. Otherwise, there is a possibility that services are interrupted.
Do as follows on each device:
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface eth-trunk interface-number.subinterface-number
Step 3 Run:
mtu mtu
The MTU is set for the Eth-Trunk sub-interface.
The MTU ranges from 46 to 9600, in bytes. By default, the MTU is 1500 bytes.
NOTE
The Quality of Service (QoS) queue length is limited. If the MTU is too small whereas the packet size is
large, packets are probably divided into many fragments, and thus discarded by the QoS queue. To resolve
this problem, lengthen the QoS queue.
----End
3.8.6 (Optional) Configuring the Rate for Eth-Trunk Sub-interfaces

to Send Gratuitous ARP Packets
To prevent the peer router from discarding gratuitous ARP packets, set a proper rate for Eth-
Trunk sub-interfaces on the local router to send gratuitous ARP packets so that the peer router
can receive all the packets.
Procedure
Step 1 Run:
system-view
Step 2 Run:


Step 3 Run:
arp send-speed-limit limit
The rate for sub-interfaces of the Eth-Trunk interface to send gratuitous ARP packets is set.
By default, the rate is 2000 packets per second.
To prevent the peer router from discarding gratuitous ARP packets, limit the rate for Eth-Trunk
sub-interfaces on the local router to send gratuitous ARP packets so that the peer router is able
to receive all the gratuitous ARP packets sent by the local router.
----End

After an Eth-Trunk sub-interface is successfully configured, you can view information about
the sub-interface, including the IP address and MAC address.
Prerequisite
The configurations of an Eth-Trunk sub-interface are complete.
Procedure
Step 1 Run the display interface eth-trunk [ trunk-id [ .subnumber ] ] command to check the status
of the Eth-Trunk sub-interface.
----End
Example
Run the display interface eth-trunk command. If information about the Eth-Trunk sub-
interface, including its IP address and MAC address, is displayed, it means that the configuration
succeeds. For example:
<HUAWEI> display interface eth-trunk 1.1
Eth-Trunk1.1 current state : UP
Description : Eth-Trunk1.1 Interface
Hash arithmetic : According to IP, The Maximum Transmit Unit is 1500
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-3f60-ec00
Encapsulation dot1q Virtual LAN, The number of Vlan is 1, Vlan ID 2
Output:0 packets,0 bytes,
0 errors,0 drops
-----------------------------------------------------
-----------------------------------------------------

-----------------------------------------------------
3.9 Configuring E-Trunk

Enhanced Trunk (E-Trunk) is an extension of LACP to implement link aggregation among
multiple devices. It guarantees device-level link reliability.

Before configuring E-Trunk, familiarize yourself with the applicable environment, complete the
pre-configuration tasks, and obtain the data required for the configuration. This will help you
complete the configuration task quickly and accurately.
As shown in Figure 3-7, two Eth-Trunk interfaces in static LACP mode connect a CE to two
PEs to access the VPLS network. The two links back up each other. In addition, the two Eth-
Trunk interfaces on the PEs are configured as an E-Trunk group so that PE1 and PE2 back up
each other. In this manner, the network reliability is enhanced.
Figure 3-7 Networking diagram of E-Trunk

LACP E-Trunk System ID:1-1-1
PE1 LACP E-Trunk Priority:100
10 E-Trunk Priority:10
- T runk
Et h
E-Trunk1 MPLS/IP core
CE E
th-T
ru nk 1
0
PE2 LACP E-Trunk System ID:1-1-1
LACP E-Trunk Priority:100
E-Trunk Priority:20
NOTE
As shown in Figure 3-7, if an E-Trunk is configured between PE1 and PE2, the E-Trunk IDs on both PE1
and PE2 must be the same. The Eth-Trunk IDs can be the same or different. The E-Trunk ID can be the
same as or different from any of the Eth-Trunk IDs.
Before configuring E-Trunk, complete the following tasks:
l Using physical links to connect devices

l Configuring Eth-Trunk interfaces in static LACP mode

Data Preparation
To configure E-Trunk, you need the following data.
No. Data
1 LACP system ID and priority
2 E-Trunk ID and priority
3 Eth-Trunk interface number and working mode
4 IP address of each interface
5 Password
6 Interval at which Hello packets are sent and multiplier for detecting Hello packets
3.9.2 Configuring the LACP System ID and Priority for E-Trunk

To make the CE consider the two PEs as one device, configure the same LACP priority and
system ID for both the master PE and the backup PE in the E-Trunk group.
Context
Do as follows on the devices in the E-Trunk group:
Procedure
Step 1 Run:
system-view

Step 2 Run:
lacp e-trunk system-id mac-address
The LACP system ID is configured for the E-Trunk group.

By default, the LACP system ID of an E-Trunk group is the MAC address of the Ethernet
interface on the MPU/SRU.
The LACP system ID of the master device in the E-Trunk group must be the same as that of the
backup device.
NOTE
The LACP system ID cannot be all 0s.

If the value is all Fs, it indicates that the LACP system ID is restored to the default.
Step 3 Run:
lacp e-trunk priority priority
The LACP priority is configured for the E-Trunk group.

By default, the LACP priority for the E-Trunk group is 32768.

The LACP priority of the master device in the E-Trunk group must be the same as that of the
backup device.
----End
3.9.3 Creating an E-Trunk Group and Configuring the E-Trunk

Priority
E-Trunk priorities determine the master and backup devices in the E-Trunk group.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
e-trunk e-trunk-id
An E-Trunk group is created.
A maximum of 64 E-Trunk groups can be created on a device.
If the E-Trunk group already exists, running the e-trunk e-trunk-id command displays the E-
Trunk view.
Step 3 Run:
priority priority
The E-Trunk priority is configured for the local device.
The E-Trunk priority determines the master/backup status of the local device in the E-Trunk
group. The device with a higher priority is the master. The smaller the priority value, the higher
the priority.
If the E-Trunk priorities of the two devices are the same, the device with the smaller system ID
is the master.
By default, the E-Trunk priority value is 100.
----End
3.9.4 Configuring Local and Peer IP Addresses

E-Trunk packets carry the source IP address and protocol port number that are configured on
the local device. To change either of the IP addresses of the two devices, change the other IP
address accordingly. Otherwise, E-Trunk packets will be discarded.
Context

Procedure
Step 1 Run:
system-view
Step 2 Run:
e-trunk e-trunk-id
The E-Trunk view is displayed.
Step 3 Run:
peer-address peer-ip-address source-address source-ip-address
The local and peer IP addresses are configured.
The peer IP address of the local device is the source IP address of the peer device. The source
IP address of the local device is the peer IP address of the peer device. For example, an E-Trunk
group is configured on device A and device B. If the peer and local IP addresses of device A are
set to 2.2.2.2 and 1.1.1.1 respectively, the peer and local IP addresses of device B must be set
to 1.1.1.1 and 2.2.2.2 respectively.
----End
3.9.5 (Optional)Binding an E-Trunk Group to a BFD Session

A device cannot rapidly detect a fault on the peer by merely relying on the timeout period for
receiving packets. To help the device rapidly detect a fault on the peer, configure Bidirectional
Forwarding Detection (BFD) on the device. Each device in the E-Trunk group must be specified
with a peer IP address, and a BFD session is configured on both devices. In this manner, if a
fault occurs, the BFD session notifies the devices of the fault so that the devices can respond in
time.
Procedure
Step 1 Run:
system-view
Step 2 Run:
e-trunk e-trunk-id
Step 3 Run:
e-trunk track bfd-session session-id
The E-Trunk group is bound to a BFD session.
The BFD session is configured to rapidly detect a fault on the control link between the two
devices in the E-Trunk group.
----End

3.9.6 Adding an Eth-Trunk Interface to an E-Trunk Group

After an E-Trunk group is successfully configured, add Eth-Trunk interfaces to the E-Trunk
group to enable LACP on the two devices. E-Trunk helps to implement inter-device link
aggregation, thus improving network reliability.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Only Eth-Trunk interfaces in static LACP mode can be added to E-Trunk groups.
Step 3 Run:
e-trunk e-trunk-id remote-eth-trunk eth-trunk-id
The Eth-Trunk interface is added to the E-Trunk group.

An Eth-Trunk interface can be added to only one E-Trunk group.
If Eth-Trunk IDs created on one PE are different from those created on the other PE, configure
remote-eth-trunk with specified peer Eth-Trunk IDs when adding Eth-Trunk interfaces in static
LACP mode to the E-Trunk group, thus ensuring that the E-Trunk group works properly.
----End
3.9.7 (Optional) Configuring the Working Mode for an Eth-Trunk

Interface
Only Eth-Trunk interfaces that have been added to E-Trunk groups can be configured with
working modes. An Eth-Trunk interface can work in automatic, forcible master, or forcible
backup mode.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Only Eth-Trunk interfaces in static LACP mode can be added to an E-Trunk group.
Step 3 Run:
e-trunk mode { auto | force-master | force-backup }
A work mode is configured for the Eth-Trunk interface.
By default, Eth-Trunk interfaces in an E-Trunk group work in automatic mode.
This command can be used for only Eth-Trunk interfaces that have been added to an E-Trunk
group, and the configuration will be automatically deleted after the Eth-Trunk interface exits
from the E-Trunk group.
If the working mode of the Eth-Trunk interface is set to automatic or is switched from forcible
master/backup to automatic, the status of the local Eth-Trunk interface will be determined by
the local E-Trunk status and whether the peer Eth-Trunk interface is faulty.
l If the local E-Trunk status is Master, the local Eth-Trunk interface works in forcible master
mode.
l If the local E-Trunk status is Backup and the peer Eth-Trunk is faulty, the local Eth-Trunk
interface works in forcible master mode. After the local Eth-Trunk interface receives a
message indicating that the peer Eth-Trunk interface recovers, the local Eth-Trunk interface
becomes Backup.
Changing the interval at which packets are sent or the timeout period for receiving packets when
the E-Trunk group works properly will cause the E-Trunk status to alternate between Master
and Backup. Therefore, set the working mode of the Eth-Trunk interface to forcible master/
backup before changing the interval or timeout period. After new configurations take effect,
restore the working mode to automatic.
----End
3.9.8 (Optional) Configuring a Password

To enhance system security, set a password on each device. The passwords set for the two devices
in an E-Trunk group must be the same.
Context
CAUTION
If simple is configured, the password will be saved into the configuration file in plain text. Users
at low levels can easily obtain the password by viewing the configuration file, threatening the
network security. Therefore, configuring cipher to save the password in cipher text is
recommended.

Procedure
Step 1 Run:
system-view
Step 2 Run:
e-trunk e-trunk-id
Step 3 Run:
security-key { simple simple-key | cipher cipher-key }
A password is configured for encrypting packets.
A password can be configured to enhance the system security. Passwords configured on the two
devices in an E-Trunk group must be the same.
The password can be configured in either plain or cipher text.

l If the password is in plain text, it is directly displayed in the configuration file.
l If the password is in cipher text, the password is displayed as illegible characters in the
configuration file.
----End
3.9.9 (Optional) Configuring a Timeout Period

If the backup E-Trunk does not receive any Hello packet from the peer before the timeout period
expires, the backup E-Trunk becomes the master E-Trunk after the timeout period expires. The
timeout period refers to the one contained in the Hello packet sent from the peer but not the one
set on the local device.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
e-trunk e-trunk-id
Step 3 Run:
timer hello hello-value
The interval at which Hello packets are sent is configured.
By default, the interval is 10 x 100 ms, that is, a Hello packet is sent every second.

Step 4 Run:
timer hold-on-failure multiplier multiplier
The multiplier for detecting Hello packets is configured.
The peer device checks the timeout period carried in the received packet to determine whether
the local device times out. If the peer device is Backup and does not receive Hello packets sent
by the local device within the timeout period, the peer device becomes Master after the timeout
period.
By default, the multiplier for detecting Hello packets is 20.
NOTE
Timeout period = Interval at which Hello packets are sent x Time multiplier for detecting Hello packets
You are recommended to set the Timeout period to larger than 5 minute..
----End
3.9.10 (Optional) Setting a Revert Delay

If a revert delay is set for the master E-Trunk, after the E-Trunk recovers, it becomes the master
E-Trunk only after the revert delay expires. This delays the switching of traffic from the backup
E-Trunk to the master E-Trunk, thus preventing service interruption.
Context
If E-Trunk works together with other features, after the fault on the original master E-Trunk is
rectified, the Eth-Trunk interface becomes the master E-Trunk again prior to restoration of other
services. If traffic is switched back immediately after the master E-Trunk recovers, services will
be interrupted.
If a revert delay is set for the master E-Trunk, after the E-Trunk recovers, it becomes the master
E-Trunk only after the revert delay expires. This delays the switching of traffic from the backup
E-Trunk to the master E-Trunk, thus preventing service interruption.
Procedure
Step 1 Run:
system-view
Step 2 Run:
e-trunk e-trunk-id
Step 3 Run:
timer revert delay delay-value
A revert delay is set.
By default, the revert delay is 120 seconds.
----End


After an E-Trunk group is successfully configured, you can view information about the E-Trunk
group, including the E-Trunk priority, system ID, source IP address, peer IP address, revert
delay, master/backup status, and reason for the master/backup status.
Prerequisite
The configurations of the E-Trunk group are complete.
Procedure
Step 1 Run the display e-trunk etrunk-id command to check configurations of the E-Trunk group.
----End
Example
Run the display e-trunk command. If the E-Trunk priority, system ID, source and peer IP
addresses, timeout period, and statistics about packets are displayed, it means that the
<HUAWEI> display e-trunk 1
The E-Trunk information

E-TRUNK-ID : 1 Revert-Delay-Time (s) : 120
Priority : 10 System-ID : 00e0-e213-9100
Peer-IP : 1.1.1.2 Source-IP : 1.1.1.1
State : Master Causation : TIMEOUT
Send-Period (100ms) : 9 Fail-Time (100ms) : 27
Receive : 1 Send : 1006
RecDrop : 0 SndDrop : 0
Peer-Priority : - Peer-System-ID : -
Peer-Fail-Time (100ms) : - BFD-Session : 1
--------------------------------------------------------------------------------
The Member information
Type ID LocalPhyState Work-Mode State Causation
Eth-Trunk 10 Up auto Master ETRUNK_MASTER
3.10 Maintaining Eth-Trunk Interfaces

Statistics clearing commands helps to locate faults on Eth-Trunk interfaces.
3.10.1 Clearing Statistics About an Eth-Trunk Interface

Before collecting traffic statistics in a specified time period on an interface, clear the existing
statistics on the interface.
Context
CAUTION
Statistics cannot be restored after it is cleared. Exercise caution when running the commands.

To clear the statistics, run the following reset command in the user view:
Procedure
l Run the reset counters interface eth-trunk [ trunk-id ] command to clear statistics about
an Eth-Trunk interface.
l Run the reset e-trunk packet-statistics [ e-trunk-id e-trunk-id ] command to clear
statistics about E-Trunk packets.
----End

This section describes typical application scenarios for Eth-Trunk interfaces, providing
networking requirements, configuration roadmap, data preparation, and configuration files.
NOTE
3.11.1 Example for Configuring Eth-Trunk Interfaces in Manual

Load Balancing Mode
In this networking, establishing an Eth-Trunk interface, adding interfaces to the Eth-Trunk
interface, and selecting active member interfaces are all manually configured, without the
participation of LACP. In manual load balancing mode, all active member interfaces participate
in data forwarding and load balancing.
As shown in Figure 3-8, Router A and Router B are two NE80E/40Es. It is required that the
link between Router A and Router B be highly reliable and traffic be transmitted through member
links.
Figure 3-8 Networking diagram for link aggregation in manual load balancing mode
GE1/0/1 GE1/0/1
GE1/0/2 GE1/0/2
Eth-Trunk
GE1/0/3 GE1/0/3
RouterA RouterB
1. Create an Eth-Trunk interface.
2. Add interfaces to the Eth-Trunk interface.
3. Verify the configuration.

NOTE
After an Eth-Trunk interface is created, it works in the default mode, that is, the manual load balancing
mode. Therefore, the manual load balancing mode does not need to be configured for an Eth-Trunk interface
by default. If the current working mode is not manual load balancing, use the mode command to change
the mode to manual load balancing. For details, see the chapter "Link Aggregation" in the Command
Reference.
Data Preparation
l Number of the LAG

l Type and number of the member interface of the Eth-Trunk
Procedure
Step 1 Create an Eth-Trunk interface.
# Configure Router A.
[RouterA] interface eth-trunk 1
[RouterA-Eth-Trunk1] quit
# Configure Router B.
[RouterB] interface eth-trunk 1
[RouterB-Eth-Trunk1] quit
Step 2 Add interfaces to the Eth-Trunk interface.
# Configure RouterA.
[RouterA-Gigabitethernet1/0/1] undo shutdown
[RouterA-Gigabitethernet1/0/1] eth-trunk 1
[RouterA-Gigabitethernet1/0/1] quit
# Configure RouterB.
[RouterB-Gigabitethernet1/0/1] undo shutdown
[RouterB-Gigabitethernet1/0/1] eth-trunk 1
[RouterB-Gigabitethernet1/0/1] quit


Run the display trunkmembership command in any view. You can check whether Eth-Trunk
1 is created and whether interfaces are correctly added. Use Router A as an example.
[RouterA] display trunkmembership eth-trunk 1
Trunk ID: 1
used status: VALID
TYPE: ethernet
operate status: up

----End
Configuration Files
l Configuration file of Router A
#
sysname RouterA
#
interface Eth-Trunk1
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
return
l Configuration file of Router B

#
sysname RouterB
#
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
return

3.11.2 Example for Configuring an Eth-Trunk Interface in 1:1

Active/Standby Mode
In this networking, an Eth-Trunk interface has only two member interfaces: an active interface
and a standby interface. This networking is applicable to the scenario where one end or both
ends do not support LACP.
As shown in Figure 3-9, Router A and Router D are NE80E/40Es. Transit devices can receive
Flush packets. Master and backup links need to be configured between Router A and Router D
to implement reliable transmission.
Figure 3-9 Networking diagram for configuring link aggregation in 1:1 active/standby mode
RouterB
GE 2/0/1 GE 2/0/3
Main Main
interface GE 2/0/2 interface
GE 1/0/1 GE 1/0/1
RouterA Eth-Trunk 1 Eth-Trunk 1 RouterD
GE 1/0/2 GE 1/0/2
GE 2/0/2
GE 2/0/1 GE 2/0/3
RouterC
Active links
Backup links
Do as follows on theRouters that need to be configured with link aggregation in 1:1 active/
standby mode.
1. Create an Eth-Trunk interface and set the working mode of the Eth-Trunk interface to 1:1
active/standby.
2. Add interfaces to the Eth-Trunk interface and specify an active member interface.
3. Enable interfaces to send Flush packets.
Do as follows on each transit device:
1. Create a control VLAN.

2. Enable interfaces to receive packets from the control VLAN.
3. Enable interfaces to receive Flush packets.

Data Preparation
l Number of the LAG on Router A and Router D
l Type and number of each member interface
l Control VLAN ID
Procedure
Step 1 Create an Eth-Trunk interface and set the working mode of the Eth-Trunk interface to 1:1 active/
standby.
# Create an Eth-Trunk interface on Router A and set the working mode of the Eth-Trunk interface
to 1:1 active/standby.
[RouterA-Eth-Trunk1] portswitch
[RouterA-Eth-Trunk1] mode manual backup
# Create an Eth-Trunk interface on Router D and set the working mode of the Eth-Trunk interface
to 1:1 active/standby.
[HUAWEI] sysname RouterD
[RouterD] interface eth-trunk 1
[RouterD-Eth-Trunk1] portswitch
[RouterD-Eth-Trunk1] mode manual backup
[RouterD-Eth-Trunk1] quit
Step 2 Add interfaces to the Eth-Trunk interface and specify an active member interface.
# On Router A, add GE 1/0/1 and GE 1/0/2 to Eth-Trunk 1 and specify GE 1/0/1 as the active
interface.
[RouterA-GigabitEthernet1/0/1] eth-trunk 1
[RouterA-GigabitEthernet1/0/1] port-master
# On Router D, add GE 1/0/1 and GE 1/0/2 to Eth-Trunk 1 and specify GE 1/0/1 as the active
interface.
[RouterD] interface gigabitethernet 1/0/1
[RouterD-GigabitEthernet1/0/1] undo shutdown
[RouterD-GigabitEthernet1/0/1] eth-trunk 1
[RouterD-GigabitEthernet1/0/1] port-master
[RouterD-GigabitEthernet1/0/1] quit
[RouterD-GigabitEthernet1/0/2] eth-trunk 1
Step 3 Enable interfaces to send Flush packets.

# Enable the interface on Router A to send Flush packets.


[RouterA-Eth-Trunk1] smart-link flush send vlan 5
# Enable the interface on Router D to send Flush packets.

[RouterD] interface eth-trunk 1
[RouterD-Eth-Trunk1] smart-link flush send vlan 5
[RouterD-Eth-Trunk1] quit
Step 4 Create a control VLAN on each transit device.

[RouterB] vlan 5
[RouterB-vlan5] quit
# Configure Router C.
[RouterC] vlan 5
[RouterC-vlan5] quit
Step 5 Enable interfaces on the transit devices to receive packets from the control VLAN.
[RouterB-GigabitEthernet2/0/1] port trunk allow-pass vlan 5
[RouterC-GigabitEthernet2/0/1] port trunk allow-pass vlan 5
Step 6 Enable interfaces on the transit devices to receive Flush packets.



# Check information about the LAG on the Routers that are configured with link aggregation in
1:1 active/standby mode. Use Router A as an example. If the configuration is correct, you can
view information about the working mode, active member interface, and standby member
interface.
[RouterA] display eth-trunk 1
WorkingMode: BACKUP
WorkingState: Master
--------------------------------------------------------------------------------
PortName Slave/Master
GigabitEthernet1/0/1 M
GigabitEthernet1/0/2 S
# Check the configurations about the interfaces on the transit devices. Use GE 2/0/1 on Router
B as an example.
[RouterB-GigabitEthernet2/0/1] display current-configuration interface
gigabitethernet 2/0/1
----End
Configuration Files
#
sysname RouterA
#
portswitch
mode manual backup
smart-link flush send vlan 5
#
undo shutdown
eth-trunk 1
port-master
#
undo shutdown
eth-trunk 1
#
return


#
sysname RouterB
#
vlan batch 5
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return
l Configuration file of Router C

#
sysname RouterC
#
vlan batch 5
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return
l Configuration file of Router D

#
sysname RouterD
#
portswitch
mode manual backup
smart-link flush send vlan 5
#
undo shutdown
eth-trunk 1
port-master
#
undo shutdown
eth-trunk 1

#
return
3.11.3 Example for Configuring Eth-Trunk Interfaces in Static

LACP Mode
In static LACP mode, creating an Eth-Trunk interface and adding interfaces to the Eth-Trunk
interface are manually configured. LACP packets are sent to negotiate link aggregation
parameters to determine active and non-active member interfaces in an LAG.
On the two Routers shown in Figure 3-10, an LAG in static LACP mode needs to be configured
to improve bandwidth and reliability. The requirements are as follows:
l m active links carry out load balancing.

l n backup links exist between two devices. If a fault occurs on an active link, a backup link
replaces the faulty link to ensure reliable data transmission.
l A member interface enabled with preemption becomes active after it recovers.
Figure 3-10 Networking diagram for link aggregation in static LACP mode
GE1/0/1 GE1/0/1
GE1/0/2 GE1/0/2
Eth-Trunk
GE1/0/3 GE1/0/3
RouterA RouterB
Active links
Backup links
1. Create an Eth-Trunk interface on the Router and configure the Eth-Trunk interface to work
in static LACP mode.
3. Configure LACP system priorities to determine the Actor.
4. Configure the maximum number of active member interfaces.
5. Configure LACP interface priorities to determine active member links.
6. Configure LACP preemption and set a delay for LACP preemption.
Data Preparation

l Number of the LAG on Routers

l LACP system priority of Router A
l Maximum number of active member interfaces
l LACP priority of each active member interface
l Delay for LACP preemption
Procedure
Step 1 Create an Eth-Trunk interface and configure the Eth-Trunk interface to work in static LACP
mode.
<RouterA> system-view
[RouterA-Eth-Trunk1] mode lacp-static
<RouterB> system-view
[RouterB-Eth-Trunk1] mode lacp-static
Step 2 Add interfaces to the Eth-Trunk interface.
Step 3 Set the LACP system priority of Router A to 100 so that Router A functions as the Actor.
[RouterA] lacp priority 100
Step 4 Set the maximum number of active member interfaces on Router A to 2.

[RouterA-Eth-Trunk1] max active-linknumber 2

NOTE
When Router A functions as the Actor, Router B does not need to be configured with the maximum number
of active member interfaces.
Step 5 Set LACP interface priorities to determine active member links.

[RouterA-Gigabitethernet1/0/1] lacp priority 100
[RouterB-Gigabitethernet1/0/1] lacp priority 100
Step 6 Configure LACP preemption and set a delay for LACP preemption.
[RouterA-Eth-Trunk1] lacp preempt enable
[RouterA-Eth-Trunk1] lacp preempt delay 20
[RouterB-Eth-Trunk1] lacp preempt enable
[RouterB-Eth-Trunk1] lacp preempt delay 20

# View information about the LAG on the Routers to check whether the LACP negotiation
succeeds.
[RouterA] display eth-trunk 1
Local:
Preempt Delay: 20 Hash arithmetic: According to flow
System Priority: 100 System ID: 00e0-fca8-0417
----------------------------------------------------------------------------------
-------
Weight
GigabitEthernet1/0/3 Unselect 1GE 150 6147 2865 11100000 1
Partner:
ActorPortName SysPri SystemID PortPri PortNo PortKey PortState
GigabitEthernet1/0/1 32768 00e0-fca6-7f85 32768 6145 2609 11111100


<RouterB> display eth-trunk 1
Local:
Preempt Delay: 20 Hash arithmetic: According to flow
System Priority: 32768 System ID: 00e0-fca6-7f85
----------------------------------------------------------------------------------
-----------
ActorPortName Status PortType PortPri PortNo PortKey
PortState Weight
1
1
GigabitEthernet1/0/3 Unselect 1GE 32768 6147 2609
11100000 1
Partner:
------------------------------------------------------------------------------
GigabitEthernet1/0/1 32768 00e0-fca8-0417 100 6145 2865 11111100
The preceding information shows that the LACP system priority of Router A is 100, which is
higher than the LACP system priority of Router B. In the LAG, GE 1/0/1 and GE 1/0/2 are active
and in the Selected state. GE 1/0/3 is in the Unselected state. In this case, load balancing can
be implemented on two member links and the remaining member link backs up.
----End
Configuration Files
#
sysname RouterA
#
lacp priority 100
#
mode lacp-static
max active-linknumber 2
lacp preempt enable
lacp preempt delay 20
#
undo shutdown
eth-trunk 1
lacp priority 100
#
undo shutdown
eth-trunk 1
lacp priority 100
#
undo shutdown
eth-trunk 1
lacp priority 150
#
return

#
sysname RouterB
#
mode lacp-static
lacp preempt enable
lacp preempt delay 20
#
undo shutdown
eth-trunk 1
lacp priority 100
#
undo shutdown
eth-trunk 1
lacp priority 100
#
undo shutdown
eth-trunk 1
lacp priority 150
#
return
3.11.4 Example for Associating an Eth-Trunk Interface in Static

LACP Mode with an mVRRP Backup Group
In the networking, the status of the mVRRP backup group determines the status of the associated
Eth-Trunk interface in static LACP mode.
As shown in Figure 3-11, a CE is dual-homed to two UPEs by using Eth-Trunk interfaces in
static LACP mode. An mVRRP backup group is configured on the two UPEs and VRRP tracking
interface status is configured. Initially, UPE1 is Master and UPE2 is Backup. After VRRP detects
that the physical interface GE 1/0/4 on UPE1 goes Down, the master/backup switchover is
performed in the mVRRP backup group but traffic is still interrupted. Analysis shows that traffic
is not switched from the link between the CE and UPE1 to the link between the CE and UPE2,
causing traffic interruption.
To prevent the problem, associate the Eth-Trunk interface in static LACP mode with the mVRRP
backup group on the UPEs.

Figure 3-11 Typical networking for associating an Eth-Trunk interface in static LACP mode
with an mVRRP backup group
IP/MPLS
Core
Backup group 1
Virtual IP address:1.1.1.10
GE1/0/4 GE1/0/3 GE1/0/3 GE1/0/4

1.1.1.1/24 1.1.1.2/24
UPE1 UPE2
G mVRRP
GE1/0/1 E1 GE1/0/2
/1
/0
/0
E1
/2
G
Eth-Trunk 20 Eth-Trunk 10 Eth-Trunk 30
3
GE
/0/
1
1
4
GE
/0/
GE
/0/
2
1
1
GE
/0/
1
CE
VRRP-tracked interface
After the Eth-Trunk interface in static LACP mode is associated with the mVRRP backup group,
the master/backup status of the UPEs in the mVRRP backup group determines the status of the
Eth-Trunk links:
l When UPE1 is Master and the Eth-Trunk link between the CE and UPE1 is Up, the Eth-
Trunk link between the CE and UPE2 is Down.
l When UPE1 is Backup and the Eth-Trunk link between the CE and UPE1 is Down, the
Eth-Trunk link between the CE and UPE2 is Up.
Configuration Notes
l The IDs of Eth-Trunk interfaces to which GE interfaces on the CE, UPE1, and UPE2 are
added can be different.
The Eth-Trunk interfaces must work in static LACP mode.
l An mVRRP backup group must be configured on directly-connected UPEs to implement
a fast switchover in the VRRP backup group.
An mVRRP backup group is able to ignore the event that the interface goes Down. If the
interface where the mVRRP backup group resides goes Down, the mVRRP backup group
rapidly changes to Master but not Initialize.

1. Configure Eth-Trunk interfaces to work in static LACP mode.

(1) Configure Eth-Trunk interfaces with different IDs to work in static LACP mode on
the CE, UPE1, and UPE2.
(2) Add GE interfaces to the Eth-Trunk interfaces.
2. Configure an mVRRP backup group on UPEs.
(1) Create VRRP backup group 1 on GE 1/0/3 of UPE1 and configure UPE1 with a higher
VRRP priority to ensure that UPE1 is Master.
(2) Create VRRP backup group 1 on GE 1/0/3 of UPE2 and configure UPE2 with the
default VRRP priority (lower than the VRRP priority of UPE1) to ensure that UPE2
is Backup.
3. Configure VRRP tracking interface status on UPEs.
4. Associate the Eth-Trunk interfaces in static LACP mode with the mVRRP backup group.
Data Preparation
l IDs of the Eth-Trunk interfaces in static LACP mode on the CE, UPE1, and UPE2
l Types and numbers of interfaces that will be added to the Eth-Trunk interfaces in static
LACP mode
l IDs and virtual IP addresses of the VRRP backup group and mVRRP backup group
l VRRP priority of UPE1
Procedure
Step 1 Configure Eth-Trunk interfaces in static LACP mode and add GE interfaces to the Eth-Trunk
interfaces.
NOTE
Ensure that the GE interfaces to be added to Eth-Trunk interfaces in static LACP mode are Up. If a GE
interface is Down, run the undo shutdown command in the view of the GE interface.
# Configure the CE.

[HUAWEI] sysname CE
[CE] interface Eth-Trunk 10
[CE-Eth-Trunk10] mode lacp-static
[CE-Eth-Trunk10] trunkport gigabitethernet 1/0/1 to 1/0/4
[CE-Eth-Trunk10] quit
# Configure UPE1.
[HUAWEI] sysname UPE1
[UPE1] interface Eth-Trunk 20
[UPE1-Eth-Trunk20] mode lacp-static
[UPE1-Eth-Trunk20] trunkport gigabitethernet 1/0/1 to 1/0/2
[UPE1-Eth-Trunk20] quit
# Configure UPE2.
[UPE2-Eth-Trunk30] mode lacp-static
[UPE2-Eth-Trunk30] trunkport gigabitethernet 1/0/1 to 1/0/2

After the configurations, run the display eth-trunk command on the CE or a UPE to check
whether the working mode of the Eth-Trunk interface is STATIC and to view the configuration
of member interfaces. Use UPE1 as an example:
[UPE1] display eth-trunk 20
Local:
System Priority: 32768 System ID: 00e0-6923-4900
--------------------------------------------------------------------------------
ActorPortName Status PortType PortPri PortNo PortKey PortState Weight
Partner:
--------------------------------------------------------------------------------
Step 2 Configure the mVRRP backup group.

NOTE
l In this example, you must configure the keyword ignore-if-down when configuring the mVRRP
backup group. In this manner, if the interface where the mVRRP backup group resides goes Down, the
VRRP backup group changes to Master but not Initialize.
If the keyword ignore-if-down is not configured, when GE 1/0/3 on UPE1 goes Down, GE 1/0/3 on
UPE2 also changes to Down. As a result, VRRP configured on GE 1/0/3 of UPE2 changes from Backup
to Initialize, and the master/backup switchover in the mVRRP backup group cannot be implemented.
l Except for a failure of UPE1, it is not recommended to run the shutdown command on GE 1/0/3 of
UPE1. Otherwise, VRRP on both UPE1 and UPE2 becomes Master, causing service interruption.
l In other scenarios, it is not recommended to configure the keyword ignore-if-down unless otherwise
stated. Otherwise, the VRRP state machine is inconsistent with that defined in the RFC.
# Configure IP addresses of GE interfaces on UPE1 as described in Figure 3-11 and create

VRRP backup group 1. Set the VRRP priority of UPE1 to 120 so that UPE1 functions as the
master.
[UPE1] interface gigabitethernet 1/0/3
[UPE1-GigabitEthernet1/0/3] undo shutdown
[UPE1-GigabitEthernet1/0/3] ip address 1.1.1.1 255.255.255.0
[UPE1-GigabitEthernet1/0/3] vrrp vrid 1 virtual-ip 1.1.1.10
[UPE1-GigabitEthernet1/0/3] vrrp vrid 1 priority 120
[UPE1-GigabitEthernet1/0/3] admin-vrrp vrid 1 ignore-if-down
# Configure IP addresses of GE interfaces on UPE2 as described in Figure 3-11 and create

VRRP backup group 1. Configure the default VRRP priority value for UPE2. Thus, UPE2
functions as the backup.
[UPE2-GigabitEthernet1/0/3] ip address 1.1.1.2 255.255.255.0
[UPE2-GigabitEthernet1/0/3] vrrp vrid 1 virtual-ip 1.1.1.10
[UPE2-GigabitEthernet1/0/3] admin-vrrp vrid 1 ignore-if-down
Step 3 Configure VRRP tracking interface status.
# Configure UPE1.

[UPE1-GigabitEthernet1/0/3] vrrp vrid 1 track interface gigabitethernet1/0/1

reduced 40
reduced 40
reduced 40
[UPE1-GigabitEthernet1/0/3] quit
# Configure UPE2.
reduced 40
reduced 40
reduced 40
After the configurations, you can run the display vrrp command on UPE1 to check whether the
status of UPE1 is Master or run the display vrrp command on UPE2 to check whether the status
of UPE2 is Backup and view the type of the VRRP backup group and the tracked interface.
[UPE1] display vrrp
State : Master
Master IP : 1.1.1.1
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
IF State : UP
IF State : UP
IF State : UP
[UPE2] display vrrp
State : Backup
Master IP : 1.1.1.2
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
IF State : UP
IF State : UP
IF State : UP
Step 4 Associate an Eth-Trunk interface in static LACP mode with an mVRRP backup group.
# Configure UPE1.


[UPE1-Eth-Trunk20] lacp track vrrp vrid 1 interface gigabitethernet1/0/3
# Configure UPE2.
[UPE2-Eth-Trunk30] lacp track vrrp vrid 1 interface gigabitethernet1/0/3

l Run the display interface eth-trunk command on each UPE. You can see that the Eth-Trunk
link between the CE and UPE1 is Up and the Eth-Trunk link between the CE and UPE2 is
Down.
[UPE1] display interface eth-trunk 20
Line protocol current state : DOWN
Description:HUAWEI, Eth-Trunk20 Interface
Route Port,Hash arithmetic : According to flow,Maximal BW: 2G, Current BW: 2G,
The Maximum Transmit Unit is 1500
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-6923-4900
QoS max-bandwidth : 0 Kbps
Output queue : (Urgent queue : Size/Length/Discards) 0/50/0
Output queue : (Protocol queue : Size/Length/Discards) 0/1000/0
Output queue : (FIFO queue : Size/Length/Discards) 0/256/0
Last 300 seconds input rate 64 bits/sec, 0 packets/sec

Last 300 seconds output rate 56 bits/sec, 0 packets/sec
0 unicast,0 broadcast,1044 multicast
0 errors,0 drops,0 unknownprotocol
0 errors,0 drops
-----------------------------------------------------
-----------------------------------------------------
-----------------------------------------------------
[UPE2] display interface eth-trunk 30
Eth-Trunk30 current state : DOWN
Route Port,Hash arithmetic : According to flow,Maximal BW: 2G, Current BW: 0M,
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-4c45-3500



0 errors,0 drops
-----------------------------------------------------
-----------------------------------------------------
GigabitEthernet1/0/1 DOWN 1
-----------------------------------------------------
l Run the vrrp vrid 1 priority 140 command in the view of GE 1/0/3 on UPE2 to increase
the VRRP priority of UPE2 so that UPE2 becomes Master and UPE1 becomes Backup. Then,
do as follows on UPEs:
– On UPE1, run the display vrrp command and you can see that UPE1 is Backup; run the
display interface eth-trunk command and you can see that the Eth-Trunk link between
the CE and UPE1 is Down.
[UPE1] display vrrp
State : Backup
Master IP : 1.1.1.1
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
IF State : UP
IF State : UP
IF State : UP
[UPE1] display interface Eth-Trunk 20
Route Port,Hash arithmetic : According to flow,Maximal BW: 2G, Current BW:
0M, T
he Maximum Transmit Unit is 1500
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is
00e0-6923-4900



0 errors,0 drops
-----------------------------------------------------
-----------------------------------------------------
-----------------------------------------------------
– On UPE2, run the display vrrp command and you can see that UPE2 is Master; run the
display interface eth-trunk command and you can see that the Eth-Trunk link between
the CE and UPE2 is Up.
[UPE2] display vrrp
State : Master
Master IP : 1.1.1.2
PriorityRun : 140
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
IF State : UP
IF State : UP
IF State : UP
2G,
00e0-4c45-3500

0 errors,0 drops

-----------------------------------------------------
-----------------------------------------------------
-----------------------------------------------------
l Run the shutdown command on GE 1/0/1 that is a member interface of the Eth-Trunk
interface on UPE2 to simulate a failure of the member interface. Then, do as follows on
UPEs:
– On UPE2, run the display vrrp command and you can see that UPE2 changes from Master
to Backup and the tracked interface goes Down; run the display interface eth-trunk
command and you can see that the Eth-Trunk link between the CE and UPE2 goes Down.
[UPE2] display vrrp
State : Backup
Master IP : 1.1.1.2
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
IF State : DOWN
IF State : UP
IF State : UP
0M,
00e0-4c45-3500

0 errors,0 drops
-----------------------------------------------------

-----------------------------------------------------
-----------------------------------------------------
– On UPE1, run the display vrrp command and you can see that UPE1 changes from
Backup to Master; run the display interface eth-trunk command and you can see that
the Eth-Trunk link between the CE and UPE1 goes Up.
[UPE1] display vrrp
State : Master
Master IP : 1.1.1.1
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
IF State : UP
IF State : UP
IF State : UP
Route Port,Hash arithmetic : According to flow,Maximal BW: 2G, Current BW: 2G,
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-6923-4900

0 errors,0 drops
-----------------------------------------------------
-----------------------------------------------------
-----------------------------------------------------
----End

Configuration Files
l Configuration file of the CE
#
sysname CE
#
mode lacp-static
#
undo shutdown
eth-trunk 10
#
undo shutdown
eth-trunk 10
#
undo shutdown
eth-trunk 10
#
undo shutdown
eth-trunk 10
#
return
l Configuration file of UPE1

#
sysname UPE1
#
mode lacp-static
lacp track vrrp vrid 1 interface GigabitEthernet1/0/3
#
undo shutdown
eth-trunk 20
#
undo shutdown
eth-trunk 20
#
undo shutdown
ip address 1.1.1.1 255.255.255.0
vrrp vrid 1 virtual-ip 1.1.1.10
admin-vrrp vrid 1 ignore-if-down
vrrp vrid 1 priority 120
vrrp vrid 1 track interface GigabitEthernet1/0/1 reduced 40
#
return

#
sysname UPE2
#
mode lacp-static
lacp track vrrp vrid 1 interface GigabitEthernet1/0/3
#
shutdown
eth-trunk 30
#
undo shutdown

eth-trunk 30
#
undo shutdown
ip address 1.1.1.2 255.255.255.0
admin-vrrp vrid 1 ignore-if-down
#
return
3.11.5 Example for Configuring Eth-Trunk Interfaces in Static

LACP Mode to Communicate over a VLL Network
Establishing an Eth-Trunk between a CE and a PE can effective improve the reliability and
bandwidth utilization of the link between the CE and the PE. The Eth-Trunk on the PE, however,
can be bound to only one VLL. Therefore, the VCs between PEs cannot be effectively used, that
is, the utilization of the bandwidths of the network between the CEs cannot be increased.
After a link aggregation group between the CEs is configured, that is, the Eth-Trunk between
the CEs crosses VLLs, the interfaces connecting PEs and CEs do not need to be added to the
Eth-Trunk and can be added to different VLLs. LACP packets can be transparently transmitted
over VLLs, and the transparent transmission paths do not interfere with each other. The Eth-
Trunk status of the CEs is thus ensured. In this manner, the bandwidth utilization and reliability
of the link between the CEs are improved.
As shown in Figure 3-12, CE1 and CE2 communicate through Eth-Trunk interfaces in static
LACP mode over a VLL network in Martini mode. The Eth-Trunk interface on CE1 has two
member interfaces, which are connected to two interfaces on PE1 at the user side. Another two
interfaces on PE1 at the network side are bound to different VLLs. That is, GE 1/0/0 on PE1 is
bound to VLL1 and GE 1/0/1 is bound to VLL2. Member interfaces of the Eth-Trunk interface
on CE2 are connected to GE 2/0/0s on PE2 and PE3. GE 2/0/0 on PE2 is bound to VLL1 and
GE 2/0/0 on PE3 is bound to VLL2.
It is required that LACP packets be transparently transmitted over the VLL network to maintain
Eth-Trunk interfaces on CE1 and CE2 and untagged Layer 2 packets be transparently transmitted
from CE1 to CE2.

Figure 3-12 Example for configuring Eth-Trunk interfaces in static LACP mode to communicate
over a VLL network
P1 PE2
Loopback4 Loopback2
GE2/0/0 Eth-Trunk1
Eth-Trunk1 Loopback1 GE2/0/0
GE1/0/0
GE1/0/0 GE1/0/0 GE2/0/0 GE1/0/0 GE1/0/0
Loopback5 Loopback3
CE1 GE1/0/1 GE1/0/1 GE2/0/1 GE1/0/0
PE1 CE2
GE1/0/0 GE2/0/0 GE2/0/0 GE1/0/1
P2 PE3
Item Interface IP Address
PE1 GE 2/0/0 10.1.1.1/24
GE 2/0/1 10.1.3.1/24
Loopback1 1.1.1.9/32
PE2 GE 1/0/0 10.1.2.2/24
PE3 GE 1/0/0 10.1.4.2/24
P1 GE 1/0/0 10.1.1.2/24
GE 2/0/0 10.1.2.1/24
P2 GE 1/0/0 10.1.3.2/24
GE 2/0/0 10.1.4.1/24
1. Configure a routing protocol on the devices (PEs and the Ps) on the backbone network to
make them reachable to each other, and enable MPLS.
2. Use the default tunnel policy and set up LSPs to transmit user data.
3. Enable MPLS L2VPN on PEs and establish VCs.
4. Create Eth-Trunk interfaces on CEs and configure the Eth-Trunk interfaces to work in static
LACP mode.
Data Preparation

l VLAN ID tagged with which packets can be transmitted on links between CEs
l Name of the remote peer of each PE
l ID of each VC
Procedure
Step 1 Configure CEs.
# Configure CE1 to be the LACP Actor.

[CE1] vlan 10
[CE1-vlan10] quit
[CE1] interface eth-trunk 1
[CE1-Eth-Trunk1] quit
[CE1-GigabitEthernet1/0/0] eth-trunk 1
[CE1] interface eth-trunk1
[CE1-Eth-Trunk1] portswitch
[CE1-Eth-Trunk1] port default vlan 10
[CE1-Eth-Trunk1] mode lacp-static
[CE1] lacp priority 100
# Configure CE2 to be the LACP Partner.

[CE2] vlan 10
[CE2-vlan10] quit
[CE2] interface eth-trunk 1
[CE2] interface eth-trunk1
[CE2-Eth-Trunk1] port default vlan 10
NOTE
You can configure either the same interface number or different interface numbers for Eth-Trunk interfaces
on CE1 and CE2.
Step 2 Configure an IGP on the MPLS backbone network (in this example, OSPF is used).
As shown in Figure 3-12, configure an IP address for each interface on PEs and P1. When
configuring OSPF, note that the 32-bit loopback addresses of PE1, PE2, PE3, P1, and P2, which
are used as LSR IDs, must be advertised.
Configuration details are not mentioned here.
After the configuration, OSPF neighbor relationships can be established between PE1, P1, and
PE2 and between PE1, P2, and PE3. By running the display ospf peer command, you can view

that OSPF neighbor relationships are Full. By running the display ip routing-table command,
you can view that PEs have learned loopback addresses from each other.
Step 3 Configure based MPLS functions and LDP on the MPLS backbone network.
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
[PE1-GigabitEthernet2/0/0] mpls
[PE1-GigabitEthernet2/0/0] mpls ldp
# Configure P1.
[P1] mpls lsr-id 4.4.4.9
[P1] mpls
[P1-mpls] quit
[P1] mpls ldp
[P1-mpls-ldp] quit
[P1] interface gigabitethernet 1/0/0
[P1-GigabitEthernet1/0/0] mpls
[P1-GigabitEthernet1/0/0] mpls ldp
[P1-GigabitEthernet1/0/0] quit
# Configure P2.
[P2] mpls lsr-id 5.5.5.9
[P2] mpls
[P2-mpls] quit
[P2] mpls ldp
[P2-mpls-ldp] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
# Configure PE3.
[PE3] mpls

[PE3-mpls] quit
[PE3] mpls ldp
[PE3-mpls-ldp] quit
Step 4 Establish remote LDP sessions between PE1 and PE2 and between PE1 and PE3.
# Configure PE1.
# Configure PE2.
# Configure PE3.
After the configuration, run the display mpls ldp session command on PE1 to view information
about LDP sessions. You can view that both remote LDP sessions have been established.
<PE1> display mpls ldp session
------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Step 5 Enable MPLS L2VPN on PEs and create VCs.

# Configure PE1: create VC1 on GE 1/0/0 and VC2 on GE 1/0/1.
[PE1] mpls l2vpn
[PE1-l2vpn] mpls l2vpn default martini
[PE1-l2vpn] quit
[PE1-GigabitEthernet1/0/0] mpls l2vc 2.2.2.9 101
# Configure PE2: create VC1 on GE 2/0/0.

[PE2] mpls l2vpn

[PE2-l2vpn] quit
# Configure PE3: create VC2 on GE 2/0/0.

[PE3] mpls l2vpn
[PE3-l2vpn] quit
On PE1, check information about L2VPN connections. You can view that two L2VCs have been
created and are in the Up state.
Take the display on GE 1/0/0 as an example:

<PE1> display mpls l2vc interface gigabitethernet 1/0/0
*client interface : GigabitEthernet1/0/0 is up
Administrator PW : no
session state : up
AC state : up
VC state : up
VC ID : 101
VC type : VLAN
destination : 2.2.2.9
local group ID : 0 remote group ID : 0
local VC label : 146433 remote VC label : 133121
local AC OAM State : up
local PSN State : up
local forwarding state : forwarding
local status code : 0x0
remote AC OAM state : up
remote PSN state : up
remote forwarding state: forwarding
remote status code : 0x0
BFD for PW : unavailable
manual fault : not set
active state : active
forwarding entry : exist
link state : up
local VC MTU : 1500 remote VC MTU : 1500
local VCCV : alert lsp-ping bfd
remote VCCV : alert lsp-ping bfd
local control word : disable remote control word : disable
tunnel policy name : --
traffic behavior name : --
PW template name : --
primary or secondary : primary
VC tunnel/token info : 1 tunnels/tokens
NO.0 TNL type : lsp , TNL ID : 0x2008007
create time : 0 days, 1 hours, 25 minutes, 29 seconds
up time : 0 days, 1 hours, 19 minutes, 52 seconds
last change time : 0 days, 1 hours, 19 minutes, 52 seconds
VC last up time : 2010/01/03 05:54:05
VC total up time : 0 days, 1 hours, 25 minutes, 18 seconds
CKey : 3
NKey : 1
PW redundancy mode : --
AdminPw interface : --
AdminPw link state : --

In this case, untagged Layer 2 packets can be transparently transmitted from CE1 to CE2.
----End
Configuration Files
#
sysname CE1
#
vlan batch 10
#
lacp priority 100
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
portswitch
mode lacp-static
#
return

#
sysname CE2
#
vlan batch 10
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
portswitch
mode lacp-static
#
return

#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
mpls l2vpn default martini
#
mpls ldp
#
remote-ip 2.2.2.9
#
remote-ip 3.3.3.9
#

undo shutdown
mpls l2vc 2.2.2.9 101
#
undo shutdown
mpls l2vc 3.3.3.9 111
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 10.1.3.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.1.3.0 0.0.0.255
#
return
l Configuration file of P1
#
sysname P1
#
mpls lsr-id 4.4.4.9
mpls
#
mpls ldp
#
undo shutdown
ip address 10.1.1.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 10.1.2.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack4
ip address 4.4.4.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 4.4.4.9 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.1.2.0 0.0.0.255
#
return
l Configuration file of P2
#
sysname P2
#
mpls lsr-id 5.5.5.9
mpls
#

mpls ldp
#
undo shutdown
ip address 10.1.3.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 10.1.4.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack5
ip address 5.5.5.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 5.5.5.9 0.0.0.0
network 10.1.3.0 0.0.0.255
network 10.1.4.0 0.0.0.255
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
mpls ldp
#
remote-ip 1.1.1.9
#
undo shutdown
mpls l2vc 1.1.1.9 101
#
undo shutdown
ip address 10.1.2.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack2
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.2.0 0.0.0.255
#
return
#
sysname PE3
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#

mpls ldp
#
remote-ip 1.1.1.9
#
undo shutdown
mpls l2vc 1.1.1.9 111
#
undo shutdown
ip address 10.1.4.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack3
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 10.1.4.0 0.0.0.255
#
return
3.11.6 Example for Configuring a Layer 2 Eth-Trunk Interface to

Allow VLAN Frames to Pass Through
Eth-Trunk interfaces on two devices are configured to allow all VLAN frames between the two
devices to pass through, and thus the two devices can communicate with each other.
As shown in Figure 3-13, Router A is connected to Router B by using Eth-Trunk 1, which is a
Layer 2 interface.
Configure Eth-Trunk 1 to allow all VLAN frames transmitted between Router A and Router B
to pass through.
Figure 3-13 Configuring a Layer 2 Eth-Trunk interface to allow VLAN frames to pass through
RouterA RouterB
GE1/0/0 Eth-Trunk1 GE1/0/0
GE2/0/0 GE2/0/0
1. Create an Eth-Trunk interface.

2. Switch the Eth-Trunk interface to the Layer 2 mode.
3. Configure the Eth-Trunk interface to allow VLAN frames to pass through.
4. Add Ethernet interfaces to the Eth-Trunk interface.

Data Preparation
l Two Eth-Trunk member interfaces GE 1/0/0 and GE 2/0/0 on Router A
l Two Eth-Trunk member interfaces GE 1/0/0 and GE 2/0/0 on Router B
Procedure
Step 1 Configure Router A.
# Configure VLAN IDs on the interface.

[RouterA-Eth-Trunk1] port link-type trunk
[RouterA-Eth-Trunk1] port trunk allow-pass vlan all
# Add GE 1/0/0 and GE 2/0/0 to Eth-Trunk 1.

Step 2 Configure Router B.

# Create Eth-Trunk 1 and configure VLAN IDs on the interface.

[RouterB-Eth-Trunk1] portswitch
[RouterB-Eth-Trunk1] port link-type trunk
[RouterB-Eth-Trunk1] port trunk allow-pass vlan all

[RouterB-GigabitEthernet1/0/0] eth-trunk 1

You can see that the interface is Up. Use the display of Router A as an example.
[RouterA] display trunkmembership eth-trunk 1
Trunk ID: 1
used status: VALID
TYPE: ethernet


operate status: up

Run the display port vlan command. You can view information about the VLAN IDs allowed
on the Eth-Trunk interface. Use Router A as an example.
[RouterA] display port vlan Eth-Trunk 1
Port Link Type PVID Trunk VLAN List
-----------------------------------------------------------------
Eth-Trunk1 trunk 0 1-4094
----End
Configuration Files
#
sysname RouterA
#
portswitch
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
return

#
sysname RouterB
#
portswitch
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
return
3.11.7 Example for Configuring a Layer 3 Eth-Trunk Interface in

Manual Load Balancing Mode
In this networking, only the configuration of the IP addresses of Layer 3 Eth-Trunk interfaces
differs from that in the example for configuring an Eth-Trunk interface in manual load balancing
mode.

As shown in Figure 3-14, an Eth-Trunk interface formed by bundling two GE interfaces is
created between Router A and Router B.
Figure 3-14 Networking diagram for configuring a Layer 3 Eth-Trunk interface
RouterA Eth-Trunk1 RouterB

GE1/0/0 100.1.1.1/24 GE1/0/0
GE2/0/0
Eth-Trunk1 GE2/0/0
100.1.1.2/24
1. Create an Eth-Trunk interface and configure an IP address for it.
2. Add Ethernet interfaces to the Eth-Trunk interface.
Data Preparation
l Layer 3 GE interface through which Router A is connected to Router B
l IP address of the Eth-Trunk interface on Router A
l IP address of the Eth-Trunk interface on Router B
Procedure
# Create an Eth-Trunk interface and configure an IP address for it.

[RouterA-Eth-Trunk1] ip address 100.1.1.1 255.255.255.0


# Create an Eth-Trunk interface and configure an IP addresses for it.


[RouterB-Eth-Trunk1] ip address 100.1.1.2 255.255.255.0


Run the display interface eth-trunk command. You can see that the interface is Up.
Use the display of Router A as an example.
[RouterA] display interface eth-trunk 1
Description : Eth-Trunk1 Interface
15 errors,6 drops
-----------------------------------------------------
-----------------------------------------------------
-----------------------------------------------------
Eth-Trunk interfaces on Router A and Router B can ping through each other.
[RouterA] ping -a 100.1.1.1 100.1.1.2
0.00% packet loss
----End
Configuration Files
#

sysname RouterA
#
ip address 100.1.1.1 255.255.255.0
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
return

#
sysname RouterB
#
ip address 100.1.1.2 255.255.255.0
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
return
3.11.8 Example for Configuring Inter-VLAN Communication by

Using Eth-Trunk Sub-interfaces
To allow devices in different VLANs to communicate with each other, create Eth-Trunk sub-
interfaces on the Eth-Trunk interfaces interconnecting a router and a switch, configure the
802.1Q encapsulation mode and an IP address on each sub-interface, and associate each sub-
interface with a VLAN. In this manner, the devices in different VLANs can communicate with
each other by using a Layer 2 switch and a router.To allow devices in different VLANs to
communicate with each other, create Eth-Trunk sub-interfaces on the Eth-Trunk interfaces
interconnecting a router and a switch, configure the 802.1Q encapsulation mode and an IP
address on each sub-interface, and associate each sub-interface with a VLAN. In this manner,
the devices in different VLANs can communicate with each other by using a Layer 2 switch and
a router.
As shown in Figure 3-15, Router A is connected to Router B by using Eth-Trunk 1, and
Router B is connected to Router C by using Eth-Trunk 2.
Configure VLAN 10 on Router A and VLAN 20 on Router C.
Create a sub-interface on Router B so that VLAN 10 and VLAN 20 can communicate by using
the Eth-Trunk sub-interface.

Figure 3-15 Networking diagram for configuring VLANs to communicate by using Eth-Trunk
sub-interfaces
Eth-Trunk1.1 Eth-Trunk2.1
RouterA Eth-Trunk1 10.110.1.10/24 10.110.2.10/24 Eth-Trunk2 RouterC
GE1/0/0 GE1/0/0 GE1/0/1 GE1/0/0
GE2/0/0 GE2/0/0 GE2/0/1 GE2/0/0

RouterB
VLAN10 VLAN20
1. On RouterB, create an Eth-Trunk sub-interface and configure an IP address for it.
2. Configure the encapsulation mode of the Eth-Trunk sub-interface as 802.1Q and configure
the associated VLANs.
3. Configure Eth-Trunk interfaces on Router A and Router C as Layer 2 interfaces to allow
VLAN frames to pass through.
Data Preparation
l Two member interfaces GE 1/0/0 and GE 2/0/0 of a Layer 2 interface Eth-Trunk 1 on
Router A
Router B
Router B
Router C
l VLAN 10 associated with sub-interface Eth-Trunk 1.1 and VLAN 20 associated with Eth-
Trunk 2.1 on Router B
l IP address 10.110.1.10 of sub-interface Eth-Trunk 1.1 and IP address 10.110.2.10 of sub-
interface Eth-Trunk 2.1
Procedure


[RouterA-Eth-Trunk1] port link-type trunk
[RouterA-Eth-Trunk1] port trunk allow-pass vlan 10

Step 2 Configure Router C.


[RouterC] interface eth-trunk 2
[RouterC-Eth-Trunk2] portswitch
[RouterC-Eth-Trunk2] port link-type trunk
[RouterC-Eth-Trunk2] port trunk allow-pass vlan 20
[RouterC-Eth-Trunk2] quit

[RouterC-GigabitEthernet1/0/0] eth-trunk 2
[RouterC-GigabitEthernet2/0/0] eth-trunk 2

# Create Eth-Trunk 1.

# Create Eth-Trunk 1.1 and configure an IP address for it.

[RouterB] interface eth-trunk 1.1
[RouterB-Eth-Trunk1.1] ip address 10.110.1.10 24
# Configure 802.1Q as the encapsulation mode for Eth-Trunk 1.1 and associate the sub-interface
with VLAN 10.
[RouterB-Eth-Trunk1.1] vlan-type dot1q 10
[RouterB-Eth-Trunk1.1] quit

# Create Eth-Trunk 2.

# Create Eth-Trunk 2.1 and configure an IP address for it.

[RouterB] interface eth-trunk 2.1
[RouterB-Eth-Trunk2.1] ip address 10.110.2.10 24
# Configure 802.1Q as the encapsulation mode for Eth-Trunk 2.1 and associate the sub-interface
with VLAN 20.
[RouterB-Eth-Trunk2.1] vlan-type dot1q 20
[RouterB-Eth-Trunk2.1] quit

On the hosts in VLAN 10, configure the IP address of the host to be in the same network segment
as the address of Eth-Trunk 1.1 and configure the default gateway address as the IP address
10.110.1.10/24 of Eth-Trunk 1.1.
On the host in VLAN 20, configure the IP address of the host to be in the same network segment
as the address of Eth-Trunk 2.1 and configure the default gateway address as the IP address
10.110.2.10/24 of Eth-Trunk 2.1.
After the configuration, the hosts between VLAN 10 and VLAN 20 can ping through each other.
----End
Configuration Files
#
sysname RouterA
#
portswitch
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
return

#
sysname RouterB
#

#
interface Eth-Trunk1.1
vlan-type dot1q 10
ip address 10.110.1.10 255.255.255.0
#
#
vlan-type dot1q 20
ip address 10.110.2.10 255.255.255.0
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 2
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 2
#
return
l Configuration file of Router C

#
sysname RouterC
#
portswitch
#
undo shutdown
eth-trunk 2
#
undo shutdown
eth-trunk 2
#
return
3.11.9 Example for Connecting an E-Trunk to a VPLS Network

Without E-Trunk, a CE can be connected to only one PE by using an Eth-Trunk link. In this
case, if the Eth-Trunk link or the PE fails, the CE cannot communicate with the PE. By using
E-Trunk, a CE can be dual-homed to two PEs, which implements device-level link reliability.
As shown in Figure 3-16, the CE is dual-homed to PE1 and PE2 by using two Eth-Trunk links
to access a VPLS network.
Normally, the CE communicates with devices on the VPLS network by using PE1. If the Eth-
Trunk link between the CE and PE1 becomes faulty, or PE1 becomes faulty, the CE is no longer
able to communicate with PE1. To prevent services from being interrupted, E-Trunk needs to
be deployed on PE1 and PE2 so that traffic sent by the CE can be switched from PE1 to PE2,
and the CE can continue to communicate with devices on the VPLS network by using PE2.

When the fault on the Eth-Trunk link between the CE and PE1 or on PE1 is rectified, traffic is
switched back to PE1. In this manner, E-Trunk implements the backup of PE1 and PE2 that are
in a link aggregation group, thus enhancing network stability.
Figure 3-16 Networking diagram for Connecting an E-Trunk to a VPLS Network

Loopback1
1.1.1.9/32
PE1
GE1/0/1
0
n k1 2 100.1.1.1/30
u /
-Tr /0
Eth E1
G
E-Trunk 1
GE1/0/1
VPLS
CE
Eth-Trunk 20
GE1/0/2
Eth GE1/
-Tr 0 /1
un
k1 GE1/0/2
0
100.1.1.10/30
PE2
Loopback2
2.2.2.9/32
E-Trunk, as an extension of LACP, is a protocol that controls and implements link aggregation
among multiple devices. E-Trunk can implement device-level link reliability, instead of board-
level link reliability implemented by LACP.
E-Trunk is mainly applied to the scenario where a CE is dual homed to two PEs to access the
VPLS, VLL, or PWE3 network. In this scenario, E-Trunk is used to protect the PEs and the links
between the CE and PEs through the link and PE switchover.
1. Configure the CE to access the VLPS network as follows:

(1) Run an IGP to ensure the connectivity of devices on the backbone network.
(2) Run a routing protocol to ensure connectivity of routes on the backbone network,
enable basic MPLS capabilities, and set up an LSP tunnel between the PEs.
(3) Enable MPLS L2VPN on the PEs.
(4) Establish a VSI and then configure the VSI.
2. Configure the E-Trunk group as follows:

(1) Create an Eth-Trunk link between the CE and PE1 and between the CE and PE2
separately. Set the two Eth-Trunk interfaces to the static LACP mode and add
interfaces to the two Eth-Trunk interfaces.
(2) Create an E-Trunk group on PE1 and PE2 and add the two Eth-Trunk interfaces in
static LACP mode to the E-Trunk group.
(3) Configure the following attributes for the E-Trunk group:
l Priority
l LACP system ID and priority
l Interval at which Hello packets are sent
l Multiplier for detecting Hello packets
l Local and peer IP addresses in the E-Trunk group
Data Preparation
l VSI IDs on PEs (they must be consistent)
l MPLS LSR ID of each PE
l Names of the VSIs on PE1 and PE2
l Interfaces to which the VSIs are bound
l E-Trunk priority
l E-Trunk LACP system ID and priority
l Eth-Trunk interface numbers and working modes
l Local and peer IP addresses
l Interval at which Hello packets are sent and multiplier for detecting Hello packets
Procedure
Step 1 Configure a VPLS network.
1. Configure an IGP for the MPLS backbone network. OSPF is used in this example.
Assign an IP address to each interface on the PEs as shown in Figure 3-16. When
configuring OSPF, configure PEs to advertise the 32-bit addresses of loopback interfaces.
# Configure PE1.
[PE1-LoopBack1] ip address 1.1.1.9 255.255.255.255
[PE1-GigabitEthernet1/0/1] ip address 100.1.1.10 255.255.255.252
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure PE2.

[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
After the configuration, PE1 and PE2 detect IP routes to the peer loopback1 by using OSPF.
PE1 and PE2 can ping through each other.
Use the display on PE1 as an example.
------------------------------------------------------------------------------

2.2.2.9/32 OSPF 10 1 D 100.1.1.2
GigabitEthernet1/0/1
100.1.1.0/30 Direct 0 0 D 100.1.1.10
[PE1] ping 2.2.2.9

0.00% packet loss
2. Enable basic MPLS functions and LDP on the MPLS backbone network.
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit

After the configuration, LDP sessions are established between the PEs. Run the display
mpls ldp session command. The Status field displays Operational. Run the display mpls
ldp lsp command. You can see that LDP LSPs have been established.
------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
[PE1] display mpls ldp lsp
LDP LSP Information
------------------------------------------------------------------------------
----------------------
DestAddress/Mask In/OutLabel NextHop OutInterface UpstreamPeer
------------------------------------------------------------------------------
----------------------
1.1.1.9/32 3/NULL 127.0.0.1 InLoop0 2.2.2.9
*1.1.1.9/32 Liberal
2.2.2.9/32 NULL/3 100.1.1.2 GE1/0/1 -
2.2.2.9/32 1024/3 100.1.1.2 GE1/0/1/ 2.2.2.9
------------------------------------------------------------------------------
----------------------
TOTAL: 3 Normal LSP(s) Found.
TOTAL: 1 Liberal LSP(s) Found.
A '*' before an LSP means the LSP is not established
A '*' before a Label means the USCB or DSCB is stale
A '*' before a UpstreamPeer means the session is in GR state
NOTE
If PEs are indirectly connected, run the mpls ldp remote-peer command and the remote-ip command
to establish remote LDP sessions between the PEs.
3. Enable MPLS L2VPN on the PEs.
# Configure PE1.
[PE1] mpls l2vpn
[PE1-l2vpn] quit
# Configure PE2.
[PE2] mpls l2vpn
[PE2-l2vpn] quit
4. Create VSIs and specify LDP as the signaling protocol for VSIs.
# Configure PE1.
[PE1-vsi-ldp1-ldp] vsi-id 2
[PE1-vsi-ldp1-ldp] peer 2.2.2.9
[PE1-vsi-ldp1-ldp] mac-withdraw enable
[PE1-vsi-ldp1-ldp] interface-status-change mac-withdraw enable
[PE1-vsi-ldp1-ldp] quit
[PE1-vsi-ldp1] ignore-ac-state
[PE1-vsi-ldp1] quit
# Configure PE2.


[PE2-vsi-ldp1-ldp] mac-withdraw enable
[PE2-vsi-ldp1-ldp] interface-status-change mac-withdraw enable
[PE2-vsi-ldp1-ldp] quit
[PE2-vsi-ldp1] ignore-ac-state
[PE2-vsi-ldp1] quit
NOTE
The ignore-ac-state command is configured to prevent VSI status from being affected by the
Attachment Circuit (AC) status. In this manner, the VSI can still be Up even if no AC is connected
to the VSI. Exercise caution when using the ignore-ac-state command.
5. Configure Eth-Trunk sub-interfaces on PEs and bind VSIs to AC interfaces.
# Configure PE1.
[PE1] interface Eth-Trunk 10
[PE1-Eth-Trunk10] quit
[PE1] interface Eth-Trunk 10.1
[PE1-Eth-Trunk10.1] vlan-type dot1q 1
[PE1-Eth-Trunk10.1] l2 binding vsi ldp1
[PE1-Eth-Trunk10.1] undo shutdown
[PE1-Eth-Trunk10.1] quit
# Configure PE2.
[PE2-Eth-Trunk10.1] vlan-type dot1q 1
[PE2-Eth-Trunk10.1] l2 binding vsi ldp1
6. Configure Layer 2 forwarding on the CE.

# Add Eth-Trunk 20 to VLAN 1.
[HUAWEI] sysname CE
[CE-Eth-Trunk20] portswitch
[CE] vlan 1
[CE-vlan1] port Eth-Trunk 20
[CE-vlan1] quit
[CE-Eth-Trunk20] port trunk allow-pass vlan 1
# Configure the work mode of Eth-Trunk 20 as the static LACP mode.

[CE-Eth-Trunk20] mode lacp-static
# Add the member interface to Eth-Trunk 20.

[CE] interface gigabitethernet 1/0/1
[CE-GigabitEthernet1/0/1] undo shutdown
[CE-GigabitEthernet1/0/1] eth-trunk 20
[CE-GigabitEthernet1/0/1] quit
[CE] interface gigabitethernet 1/0/2
[CE-GigabitEthernet1/0/2] undo shutdown
[CE-GigabitEthernet1/0/2] eth-trunk 20
[CE-GigabitEthernet1/0/2] quit
Step 2 Configure the E-Trunk.

1. Create Eth-Trunk 10 and configure the Eth-Trunk interface to work in static LACP mode.
# Configure PE1.
[PE1] interface eth-trunk 10

[PE1-Eth-Trunk10] mode lacp-static

# Configure PE2.

# Configure PE1.
[PE1-GigabitEthernet1/0/2] eth-trunk 10
# Configure PE2.
3. Create an E-Trunk group and add the two static LACP Eth-Trunk interfaces to the E-Trunk
group.
# Configure PE1.
[PE1] e-trunk 1
[PE1-e-trunk-1] quit
[PE1-Eth-Trunk10] e-trunk 1
# Configure PE2.
[PE2] e-trunk 1
4. Configure E-Trunk attributes.

l Configure the E-Trunk priority.
# Configure PE1.
[PE1] e-trunk 1
[PE1-e-trunk-1] priority 10
# Configure PE2.
[PE2] e-trunk 1
l Configure the E-Trunk LACP system ID and priority.

# Configure PE1.
[PE1] lacp e-trunk priority 1
[PE1] lacp e-trunk system-id 00E0-FC00-0000
# Configure PE2.
[PE2] lacp e-trunk system-id 00E0-FC00-0000
The E-Trunk LACP system IDs and priorities configured on PE1 and PE2 must be the
same.
l Configure a multiple for E-Trunk to detect Hello packets.
# Configure PE1.
[PE1] e-trunk 1

[PE1-e-trunk-1] timer hold-on-failure multiplier 3
# Configure PE2.
[PE2] e-trunk 1
l Configure the interval at which E-Trunk members send Hello packets.

# Configure PE1.
[PE1-e-trunk-1] timer hello 9
# Configure PE2.
5. Configure the local and peer IP addresses for devices in the E-Trunk group.
# Configure PE1.
[PE1-e-trunk-1] peer-address 100.1.1.2 source-address 100.1.1.10
# Configure PE2.
6. Bind E-Trunk to a BFD session.

l Create a BFD session.
# Configure PE1.
[PE1] bfd
[PE1-bfd] quit
[PE1] bfd hello bind peer-ip 100.1.1.2 source-ip 100.1.1.10
[PE1-bfd-session-hello] discriminator local 1
[PE1-bfd-session-hello] discriminator remote 2
[PE1-bfd-session-hello] commit
[PE1-bfd-session-hello] quit
The local and peer IP addresses to which the BFD session is bound must be consistent
with the local and peer IP addresses of devices in the E-Trunk group.
# Configure PE2.
[PE2] bfd
[PE2-bfd] quit
l Bind E-Trunk to the BFD session.

# Configure PE1.
[PE1] e-trunk 1
[PE1-e-trunk-1] e-trunk track bfd-session 1
# Configure PE2.
[PE2] e-trunk 1
After the configuration, run the display bfd session all verbose command on PE1 and
PE2. The command output shows that the BFD session has been established and the
session status is Up.
[PE1] display bfd session all verbose
---------------------------------------------------------------------------
-----

Session MIndex : 256 (Multi Hop) State : Up Name : hello

---------------------------------------------------------------------------
-----
Local Discriminator : 1 Remote Discriminator : 2
Session Detect Mode : Asynchronous Mode Without Echo Function
BFD Bind Type : Peer IP Address
Bind Session Type : Static
Bind Peer IP Address : 100.1.1.2
Bind Interface : -
Bind Source IP Address : 100.1.1.10
FSM Board Id : 1 TOS-EXP : 7
Min Tx Interval (ms) : 1000 Min Rx Interval (ms) : 1000
Actual Tx Interval (ms): - Actual Rx Interval (ms): -
Local Detect Multi : 3 Detect Interval (ms) : -
Echo Passive : Disable Acl Number : -
Destination Port : 3784 TTL : 254
Proc Interface Status : Disable Process PST :
Disable
WTR Interval (ms) : - Local Demand Mode :
Disable
Last Local Diagnostic : No Diagnostic
Bind Application : E-TRUNK
Session TX TmrID : - Session Detect TmrID : -
Session Init TmrID : - Session WTR TmrID : -
Session Echo Tx TmrID : -
PDT Index : FSM-0 | RCV-0 | IF-0 | TOKEN-0
Session Description : -
---------------------------------------------------------------------------
-----
Total UP/DOWN Session Number : 1/0

# Run the display eth-trunk command on the CE to check the configurations of Eth-Trunk
interfaces.
[CE] display eth-trunk 20
Local:
System Priority: 32768 System ID: 00e0-657a-6300
--------------------------------------------------------------------------------
Weight
GigabitEthernet1/0/1 Selected 100M 32768 128 2593 11111100 1
GigabitEthernet1/0/2 Unselect 100M 32768 129 2593 11100010 1
Partner:
--------------------------------------------------------------------------------
PortState
GigabitEthernet1/0/1 1 00e0-fc00-0000 32768 129 2593
11111100
GigabitEthernet1/0/2 1 00e0-fc00-0000 32768 32896 2593
11010000
The command output shows on the CE that the member interfaces GigabitEthernet 1/0/1 and
GigabitEthernet 1/0/2 are in the Selected and Unselect state respectively.
# Run the display e-trunk command to check configurations of the E-Trunk.
[PE1] display e-trunk 1
Priority : 10 System-ID : 00e0-0f74-eb00

Peer-IP : 100.1.1.2 Source-IP : 100.1.1.10

State : Master Causation : PRI
Peer-Priority : 20 Peer-System-ID : 00e0-3b6c-6100
Peer-Fail-Time (100ms) : 27 BFD-Session : 1
--------------------------------------------------------------------------------
Eth-Trunk 10 Up auto Master PEER_MEMBER_DOWN
Priority : 20 System-ID : 00e0-3b6c-6100
Peer-IP : 100.1.1.10 Source-IP : 100.1.1.2
State : Backup Causation : PRI
Peer-Priority : 10 Peer-System-ID : 00e0-0f74-eb00
--------------------------------------------------------------------------------
Eth-Trunk 10 Down auto Backup PEER_MEMBER_UP
The command output shows priority of the E-Trunk on PE1 is 10 and the E-Trunk is in the
Master state. The priority of the E-Trunk on PE2 is 20 and the E-Trunk is in the Backup state.
In this manner, the link backup is implemented.
# Run the display vsi name ldp1 verbose command to check PW information.
***VSI Name : ldp1
VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
Ignore AcState : enable
VSI State : up
VSI ID : 2
LDP MAC-WITHDRAW : Interface-status-change Enable
VC Label : 19456
Peer Type : dynamic
Session : up
CKey : 2
NKey : 1
StpEnable : 0
PwIndex : 0
Interface Name : Eth-Trunk10.1

State : up

Last Up Time : 2009/03/28 15:32:50

**PW Information:

PW State : up
PW Type : label
Ckey : 0x2
Nkey : 0x1
Tnl Type : LSP
OutInterface : GigabitEthernet1/0/1
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2009/03/28 15:12:13
The command output shows that a PW has been established between the VSI named ldp1 and
PE2; both the VSI and PW are Up; the Eth-Trunk sub-interface bound to the VSI is Up.
----End
Configuration Files
l Configuration file of the CE
#
sysname CE
#
vlan batch 1
#
portswitch
port default vlan 1
mode lacp-static
#
undo shutdown
eth-trunk 20
#
undo shutdown
eth-trunk 20
#
return

#
sysname PE1
#
e-trunk 1
#
lacp e-trunk system-id 00e0-fc00-0000
lacp e-trunk priority 1
#
bfd
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#

vsi ldp1 static

pwsignal ldp
vsi-id 2
mac-withdraw enable
interface-status-change mac-withdraw enable
peer 2.2.2.9
ignore-ac-state
#
mpls ldp
#
mode lacp-static
e-trunk 1
#
vlan-type dot1q 1
l2 binding vsi ldp1
#
undo shutdown
ip address 100.1.1.10 255.255.255.252
mpls
mpls ldp
#
undo shutdown
eth-trunk 10
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
bfd hello bind peer-ip 100.1.1.2 source-ip 100.1.1.10
discriminator local 1
discriminator remote 2
commit
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 100.1.1.0 0.0.0.3
#
e-trunk 1
priority 10
peer-address 100.1.1.2 source-address 100.1.1.10
timer hello 9
e-trunk track bfd-session 1
#
return
#
sysname PE2
#
e-trunk 1
#
lacp e-trunk system-id 00e0-fc00-0000
#
bfd
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 2
mac-withdraw enable
interface-status-change mac-withdraw enable

peer 1.1.1.9
ignore-ac-state
#
mpls ldp
#
mode lacp-static
e-trunk 1
#
vlan-type dot1q 1
l2 binding vsi ldp1
#
undo shutdown
eth-trunk 10
#
undo shutdown
ip address 100.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
commit
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 100.1.1.0 0.0.0.3
#
e-trunk 1
priority 20
timer hello 9
#
return
3.11.10 Example for Connecting an E-Trunk to PW Redundancy

As shown in Figure 3-17, CE1 is dual-homed to PE1 and PE2 by using Eth-Trunk links to access
a PWE3 network.
Normally, CE1 communicates with devices on the PWE3 network by using PE1. If the Eth-
Trunk link between CE1 and PE1 becomes faulty, or PE1 becomes faulty, CE1 is no longer able
to communicate with PE1. To prevent services from being interrupted, E-Trunk needs to be
deployed on PE1 and PE2 so that traffic sent by CE1 can be switched from PE1 to PE2, and
CE1 can continue to communicate with devices on the PWE3 network by using PE2.
If the fault on the Eth-Trunk link between CE1 and PE1 or on PE1 is rectified, traffic is switched
back to PE1. In this manner, E-Trunk implements the backup of PE1 and PE2 that are in a link
aggregation group, thus enhancing network stability.

Figure 3-17 Networking diagram for Connecting an E-Trunk to PW Redundancy

Loopback0
1.1.1.1/32
GE1/0/0
GE1/0/2 10.1.3.2/24
Loopback0
GE1/0/1 PE1 GE1/0/1 3.3.3.3/32
10.1.4.1/24
GE1/0/1 GE1/0/0
CE1 Eth-Trunk20 10.1.3.1/24 10.1.1.1/24
GE1/0/1 GE1/0/0
GE1/0/2 10.1.4.2/24
PE2 GE1/0/2 PE3 CE2
10.1.2.1/24
GE1/0/0
GE1/0/2
10.1.2.2/24
Loopback0
2.2.2.2/32
E-Trunk, as an extension of LACP, is a protocol that controls and implements link aggregation
among multiple devices. E-Trunk implements device-level link reliability, instead of board-level
link reliability implemented by LACP.
E-Trunk is mainly applied to the scenario where a CE is dual-homed to two PEs to access the
VPLS, VLL, or PWE3 network. In this scenario, E-Trunk is used to protect the PEs and the links
between the CE and PEs by using the link and PE switchover.
1. Configure PW redundancy.
(1) Configure an IGP to ensure connectivity of devices on the backbone network.
(2) Configure a routing protocol to ensure connectivity of routes on the backbone network,
enable basic MPLS capabilities, and set up an LDP LSP between PE1 and PE3, and
set up another LDP LSP between PE2 and PE3.
(3) Set up the remote LDP session between PE1 and PE3, and between PE2 and PE3.
(4) Configure LDP FRR and Synchronization Between LDP and IGP.
(5) Enable MPLS L2VPN on the PEs.
(6) Configure a PW between PE1 and PE3.
(7) Configure a secondary PW between PE2 and PE3.
2. Configure E-Trunk.
(1) Create an Eth-Trunk link between CE1 and PE1 and between CE1 and PE2 separately.
Configure the two Eth-Trunk interfaces to work in static LACP mode and add
interfaces to the two Eth-Trunk interfaces.

(2) Create an E-Trunk group on PE1 and PE2 and add the two Eth-Trunk interfaces in
static LACP mode to the E-Trunk group.
(3) Configure the following E-Trunk attributes:
l Priority
l LACP system ID and priority
l Interval at which Hello packets are sent
l Multiplier for detecting Hello packets
l Local and peer IP addresses for the E-Trunk group
Data Preparation
l MPLS LSR ID of each PE
l VC IDs and VC-Types on PEs
l E-Trunk priority
l E-Trunk LACP system ID and priority
l Eth-Trunk interface numbers and working modes
l Local and peer IP addresses
l Interval at which Hello packets are sent and multiplier for detecting Hello packets
Procedure
Step 1 Configure the MPLS backbone network.
1. Configure an IGP on the MPLS backbone network. OSPF is used in this example.
Assign an IP address to each interface on the PEs as shown in Figure 3-17. When
configuring OSPF, configure PEs to advertise the 32-bit addresses of loopback interfaces.
# Configure PE1.
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure PE2.


[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
# Configure PE3.
[PE3] ospf
[PE3-ospf-1] area 0
[PE3-ospf-1] quit
After the configuration, PEs detect IP routes to the peer loopback0 by using OSPF. PE1
and PE3, PE2 and PE3 can ping through each other.
[PE1] ping 3.3.3.3

0.00% packet loss
2. Enable basic MPLS functions and MPLS LDP on the MPLS backbone network.
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit


# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
# Configure PE3.
[PE3] mpls
[PE3-mpls] quit
[PE3] mpls ldp
[PE3-mpls-ldp] quit
After the configuration, LDP sessions are set up. Run the display mpls ldp session
command. The Status field displays Operational.

------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
3. Configure LDP FRR and synchronization between LDP and IGP.

Configure LDP FRR on PE3.
[PE3] interface gigabitethernet1/0/1
[PE3-GigabitEthernet1/0/1] mpls ldp frr nexthop 10.1.2.2
Configure synchronization between LDP and IGP.

Configure PE1.
[PE1-GigabitEthernet1/0/0] ospf ldp-sync
Configure PE2.


Configure PE3.
4. Configure remote MPLS LDP peers.

# Configure PE1.
# Configure PE2.
# Configure PE3.
5. Enable MPLS L2VPN on PEs.

# Configure PE1.
[PE1] mpls l2vpn
[PE1-l2vpn] quit
# Configure PE2.
[PE2] mpls l2vpn
[PE2-l2vpn] quit
# Configure PE3.
[PE3] mpls l2vpn
[PE3-l2vpn] quit
Step 2 Configure an E-Trunk group on PE1 and PE2.

1. Configure Eth-Trunk on PE1 and PE2.
# Create an Eth-Trunk interface on PE1.
[PE1-Eth-Trunk20] portswitch
[PE1-Eth-Trunk20] mode user-termination
# Configure the Eth-Trunk interface to work in static LACP mode.

# Add an interface to the Eth-Trunk interface.

# Create an Eth-Trunk sub-interface on PE1.

# Configure QinQ termination on the Eth-Trunk sub-interface.

[PE1-Eth-Trunk20.100] control-vid 100 qinq-termination
[PE1-Eth-Trunk20.100] qinq termination pe-vid 100 ce-vid 100


# Configure PE2.
[PE2-Eth-Trunk20] portswitch
[PE2-Eth-Trunk20] mode user-termination
[PE2-Eth-Trunk20.100] control-vid 100 qinq-termination
[PE2-Eth-Trunk20.100] qinq termination pe-vid 100 ce-vid 100
2. Configure Eth-Trunk on CE1.

# Add Eth-Trunk 20 to VLAN 100.
[CE1] interface Eth-Trunk 20
[CE1] vlan 100
[CE1-vlan100] port Eth-Trunk 20
[CE1-vlan100] quit
[CE1] interface Eth-Trunk 20
[CE-Eth-Trunk20] port trunk allow-pass vlan 100
# Configure Eth-Trunk 20 to work in static LACP mode.

# Add interfaces to Eth-Trunk 20.

3. Create an E-Trunk group on PE1 and PE2, and add the two Eth-Trunk interfaces in static
LACP mode to the E-Trunk group.
# Configure PE1.
[PE1] e-trunk 1
# Configure E-Trunk system ID. The system IDs of devices in the same E-Trunk group
must be the same.
[PE1] lacp e-trunk system-id 0000-0000-0001
# Configure PE2.
[PE2] e-trunk 1
[PE2] lacp e-trunk system-id 0000-0000-0001

4. Configure E-Trunk attributes.

l Configure the E-Trunk priority and specify the local and peer IP addresses.
# Configure PE1.
Configure the E-Trunk priority.
[PE1] e-trunk 1
Specify the local and peer IP addresses for the E-Trunk group.
# Configure PE2.
Configure the E-Trunk priority.
[PE2] e-trunk 1
l Configure the E-Trunk LACP priority.

The LACP priorities of devices in the same E-Trunk group must be the same.
# Configure PE1.
# Configure PE2.
l Configure the multiple for the E-Trunk group to detect Hello packets.
# Configure PE1.
[PE1] e-trunk 1
# Configure PE2.
[PE2] e-trunk 1
l Configure the interval at which Hello packets are sent.

# Configure PE1.
# Configure PE2.
l Set the revert delay for the E-Trunk group.

# Configure PE1.
[PE1-e-trunk-1] timer revert delay 0
# Configure PE2.
[PE2-e-trunk-1] timer revert delay 0
5. Bind the E-Trunk group to a BFD session.

l Create a BFD session.
# Configure PE1.
[PE1] bfd
[PE1-bfd] quit

The local and peer IP addresses to which the BFD session is bound must be consistent
with the local and peer IP addresses for the E-Trunk group.
# Configure PE2.
[PE2] bfd
[PE2-bfd] quit
l Bind the E-Trunk group to the BFD session.

# Configure PE1.
[PE1] e-trunk 1
# Configure PE2.
[PE2] e-trunk 1
# After the configuration, run the display bfd session all verbose command on PE1
and PE2. The command output shows that the BFD session has been established and
the session is Up.
[PE1] display bfd session all verbose
---------------------------------------------------------------------------
-----
Session MIndex : 256 (Multi Hop) State : Up Name : hello
---------------------------------------------------------------------------
-----
Session Detect Mode : Asynchronous Mode Without Echo Function
BFD Bind Type : Peer IP Address
Bind Peer IP Address : 2.2.2.2
Bind Interface : -
Bind Source IP Address : 1.1.1.1
Actual Tx Interval (ms): - Actual Rx Interval (ms): -
Local Detect Multi : 3 Detect Interval (ms) : -
Echo Passive : Disable Acl Number : -
Destination Port : 3784 TTL : 254
Proc Interface Status : Disable Process PST :
Disable
WTR Interval (ms) : - Local Demand Mode :
Disable
Bind Application : E-TRUNK
Session TX TmrID : - Session Detect TmrID : -
Session Init TmrID : - Session WTR TmrID : -
Session Echo Tx TmrID : -
PDT Index : FSM-0 | RCV-0 | IF-0 | TOKEN-0
Session Description : -
---------------------------------------------------------------------------
-----
Total UP/DOWN Session Number : 1/0
Step 3 Configure PW.

# Configure PE1.

[PE1] interface Eth-Trunk20.100

[PE1-Eth-Trunk20.100] mpls l2vc 3.3.3.3 103
# Configure PE2.
[PE2] interface Eth-Trunk20.100
[PE2-Eth-Trunk20.100] mpls l2vc 3.3.3.3 203
# Configure PE3.
[PE3] interface GigabitEthernet1/0/0.100
[PE3-GigabitEthernet1/0/0.100] mpls l2vc 1.1.1.1 103
[PE3-GigabitEthernet1/0/0.100] mpls l2vc 2.2.2.2 203 secondary
[PE3-GigabitEthernet1/0/0.100] mpls l2vpn redundancy independent

# Run the display eth-trunk command on CE1. You can view the configurations of Eth-Trunk
interfaces.
[CE1] display eth-trunk 20
Local:
System Priority: 32768 System ID: 00e0-657a-6300
--------------------------------------------------------------------------------
Weight
GigabitEthernet1/0/1 Selected 100M 32768 128 2593 11111100 1
GigabitEthernet1/0/2 Unselect 100M 32768 129 2593 11100010 1
Partner:
--------------------------------------------------------------------------------
PortState
11111100
11010000
On CE1, the command output shows that the member interfaces GigabitEthernet 1/0/1 and
GigabitEthernet 1/0/2 are in the Selected and Unselect state respectively.
# Run the display e-trunk command. You can view the configurations of the E-Trunk group.
Priority : 10 System-ID : 0018-82d7-b58b
Peer-IP : 2.2.2.2 Source-IP : 1.1.1.1
State : Master Causation : PRI
Peer-Priority : 20 Peer-System-ID : 0018-82f7-c752
--------------------------------------------------------------------------------
Eth-Trunk 20 Up auto Master PEER_MEMBER_DOWN
Priority : 20 System-ID : 0018-82f7-c752

Peer-IP : 1.1.1.1 Source-IP : 2.2.2.2

State : Backup Causation : PRI
Peer-Priority : 10 Peer-System-ID : 0018-82d7-b58b
--------------------------------------------------------------------------------
Eth-Trunk 20 Down auto Backup PEER_MEMBER_UP
The command output shows that the E-Trunk priority of PE1 is 10 and PE1 is in the Master
state. The E-Trunk priority of PE2 is 20 and PE2 is in the Backup state. In this manner, link
backup is implemented.
# Run the display mpls l2vc brief command. You can view the PW status.
[PE3] display mpls l2vc brief
Total ldp vc : 2 2 up 0 down
*Client Interface : GigabitEthernet1/0/0.100

AC status : up
VC State : up
VC ID : 103
VC Type : VLAN
session state : up
Destination : 1.1.1.1
link state : up

AC status : up
VC State : up
VC ID : 203
VC Type : VLAN
session state : up
link state : up
The command output shows that the PWs have been established.
----End
Configuration Files
#
sysname CE1
#
vlan batch 1
#
portswitch
mode lacp-static
#
undo shutdown
eth-trunk 20
#
undo shutdown
eth-trunk 20

#
return
#
sysname PE1
#
e-trunk 1
#
#
bfd
#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
mpls ldp
#
remote-ip 3.3.3.3
undo remote-ip pwe3
#
portswitch
mode lacp-static
e-trunk 1
lacp e-trunk system-id 0000-0000-0001
#
qinq termination pe-vid 100 ce-vid 100
mpls l2vc 3.3.3.3 103
#
undo shutdown
ip address 10.1.3.2 255.255.255.0
ospf ldp-sync
mpls
mpls ldp
#
undo shutdown
ip address 10.1.4.1 255.255.255.0
mpls
mpls ldp
#
undo shutdown
eth-trunk 20
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.255
#
commit
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 10.1.3.0 0.0.0.255
network 10.1.4.0 0.0.0.255
#
e-trunk 1
priority 10

timer hello 9
timer hold-on-failure multiplier 3
timer revert delay 0
#
return
#
sysname PE2
#
e-trunk 1
#
#
bfd
#
mpls lsr-id 2.2.2.2
mpls
#
mpls l2vpn
#
mpls ldp
#
remote-ip 3.3.3.3
undo remote-ip pwe3
#
portswitch
mode lacp-static
e-trunk 1
lacp e-trunk system-id 0000-0000-0001
#
mpls l2vc 3.3.3.3 203
#
undo shutdown
ip address 10.1.2.2 255.255.255.0
ospf ldp-sync
mpls
mpls ldp
#
undo shutdown
ip address 10.1.4.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
eth-trunk 20
#
interface LoopBack0
ip address 2.2.2.2 255.255.255.255
#
commit
#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 10.1.2.0 0.0.0.255
network 10.1.4.0 0.0.0.255

#
e-trunk 1
priority 20
timer hello 9
timer hold-on-failure multiplier 3
timer revert delay 0
#
return

#
sysname PE3
#
mpls lsr-id 2.2.2.2
mpls
#
mpls l2vpn
#
mpls ldp
#
remote-ip 1.1.1.1
undo remote-ip pwe3
#
remote-ip 2.2.2.2
undo remote-ip pwe3
#
undo shutdown
ip address 10.1.3.1 255.255.255.0
ospf ldp-sync
mpls
mpls ldp
mpls ldp frr nexthop 10.1.2.2
#
undo shutdown
ip address 10.1.2.1 255.255.255.0
ospf ldp-sync
mpls
mpls ldp
#
undo shutdown
mpls l2vc 1.1.1.1 103
mpls l2vc 2.2.2.2 203 secondary
mpls l2vpn redundancy independent
#
interface LoopBack0
ip address 3.3.3.3 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.3 0.0.0.0
network 10.1.2.0 0.0.0.255
network 10.1.3.0 0.0.0.255
#
return

Configuration Guide - LAN Access and MAN Access 4 VLAN Configuration
4 VLAN Configuration
About This Chapter
Virtual Local Area Networks (VLANs) have advantages of broadcast domain isolation, security
enhancement, flexible networking, and good extensibility.
4.1 VLAN Introduction

The VLAN technology logically divides a physical LAN into multiple broadcast domains
(VLANs).
4.2 Configuring a VLAN Based on Ports
Configuring a VLAN based on ports allows PCs in the VLAN to communicate with each other.
4.3 Creating a VLANIF Interface
VLANIF interfaces are Layer 3 logical interfaces. After creating VLANIF interfaces on Layer
2 devices, you can configure Layer 3 features on these interfaces.
4.4 Configuring Inter-VLAN Communication
Configuring inter-VLAN communication allows users in different VLANs to communicate with
each other. Currently, the NE80E/40E supports several inter-VLAN communication schemes.
Choose one of them as required.
4.5 Configuring VLAN Security Attributes
Configuring VLAN security attributes ensures reliable transmission of user data. Currently, the
NE80E/40E supports several security attributes. You can configure security attributes as
required.
4.6 Configuring VLAN Aggregation to Save IP Addresses
VLAN aggregation prevents the waste of IP addresses and implements inter-VLAN
communication.
4.7 Configuring VLAN Policy-based VPN Access
VLAN policy-based VPN access allows VLLs, VSIs, or VPN instances to transmit separate
services. Currently, the NE80E/40E supports several VLAN policy-based VPN access schemes.
4.8 Configuring Interface Isolation in a VLAN
After interface isolation in a VLAN is configured, interfaces in the VLAN cannot communicate
with each other. To have isolated interfaces communicate with each other, you need to configure
ARP proxy in the VLAN. In this manner, you can monitor traffic in the VLAN at Layer 3.

4.9 Configuring the Isolation Based on Interface Groups in a VLAN

You can isolate interfaces in a VLAN by adding interfaces to different interface groups.
4.10 Configuring Ethernet Loop Detection for a VLAN
In the case of an uncontrollable user network, the NE80E/40E supports the deployment of
Ethernet loop detection on the provider's network to prevent loops in a VLAN.
4.11 Maintaining VLAN
A command of clearing statistics helps to locate the faults in a VLAN.
This section describes the typical application scenarios of VLANs, including networking
requirements, configuration roadmap, and data preparation, and provides related configuration
files.

4.1 VLAN Introduction

The VLAN technology logically divides a physical LAN into multiple broadcast domains
(VLANs).
4.1.1 Introduction
The VLAN technology is important for forwarding on Layer 2 networks. This section describes
the background, functions, and advantages of the VLAN technology.
Overview of VLAN
The Ethernet technology is for sharing communication mediums and data based on the Carrier
Sense Multiple Access/Collision Detect (CSMA/CD). If there are a large number of PCs on an
Ethernet network, collision becomes a serious problem and can lead to broadcast storms. As a
result, network performance deteriorates. This can even cause the Ethernet network to become
unavailable. Switches can be used to interconnect local area networks (LANs). Switches forward
information received by inbound ports to specified outbound ports, thereby preventing access
collision in a shared medium. If no specified outbound port is found for information received
by an inbound port, the switch will forward the information from all ports except the inbound
port. This forms a broadcast domain.
To prevent broadcast domains from being too broad and causing problems, you can divide a
network into segments. In this manner, a large broadcast domain is divided into multiple small
broadcast domains to confine the possible scope of broadcast packets. Routers can be deployed
at the network layer to separate broadcast domains, but this method has disadvantages, which
include: complex network planning, inflexible networking, and high levels of expenditure. The
Virtual Local Area Network (VLAN) technology can divide a large Layer 2 network into
broadcast domains to prevent broadcast storms and protect network security.
Definition of VLAN
The VLAN technology is used to divide a physical LAN into multiple logical broadcast domains,
each of which is called a VLAN. Each VLAN contains a group of PCs that have the same
requirements. A VLAN has the same attributes as a LAN. PCs of a VLAN can be placed on
different LAN segments. If two PCs are located on one LAN segment but belong to different
VLANs, they do not broadcast packets to each other. With VLAN, the broadcast traffic volume
is reduced; fewer devices are required; network management is simplified; and network security
is improved.
Figure 4-1 shows a typical VLAN application. Three switches are placed in different locations,
for example, different stories of an office building. The VLAN technology allows enterprises to
share LAN facilities and ensures information security for each enterprise network.

Figure 4-1 Schematic diagram for a typical VLAN application
Router
Switch1 Switch2 Switch3
VLAN-A
VLAN-B
VLAN-C
This application shows the following VLAN advantages:

l Broadcast domains are confined. A broadcast domain is confined to a VLAN. This saves
bandwidth and improves network processing capabilities.
l Network security is enhanced. Packets from different VLANs are separately transmitted.
PCs in one VLAN cannot directly communicate with PCs in another VLAN.
l Network robustness is improved. A fault in a VLAN does not affect PCs in other VLANs.
l Virtual groups are set up flexibly. With the VLAN technology, PCs in different
geographical areas can be grouped together. This facilitates network construction and
maintenance.
Basic VLAN Concepts and Principles

l 802.1Q and VLAN frame format
A conventional Ethernet frame is encapsulated with the Length/Type field for an upper-
layer protocol following the Destination address and Source address fields, as shown in
Figure 4-2.
Figure 4-2 Conventional Ethernet frame format
6bytes 6bytes 2bytes 46-1500bytes 4bytes

Destination Source Data FCS
Length/Type
address address
IEEE 802.1Q is an Ethernet networking standard for a specified Ethernet frame format. It
adds a 32-bit field between the Source address and the Length/Type fields of the original
frame, as shown in Figure 4-3.

Figure 4-3 802.1Q frame format

6bytes 6bytes 4bytes 2bytes 46-1500bytes 4bytes
Destination Source 802.1Q Length/
Data FCS
address address Tag Type
TPID PRI CFI VID
2bytes 3bits 1bit 12bits
– Tag Protocol Identifier (TPID): a 16-bit field set to a value of 0x8100 in order to identify
the frame as an IEEE 802.1Q-tagged frame. If an 802.1Q-incapable device receives an
802.1Q frame, it will discard the frame.
– Priority (PRI): a 3-bit field which indicates the frame priority. The value ranges from 0
to 7. The greater the value, the higher the priority. These values can be used to prioritize
different classes of traffic to ensure that frames with high priorities are transmitted first
when traffic is heavy.
For details, see the NE80E/40E Configuration Guide - QoS.
– Canonical Format Indicator (CFI): a 1-bit field. If the value of this field is 1, the MAC
address is in the non-canonical format. If the value is 0, the MAC address is in the
canonical format. CFI is used to ensure compatibility between Ethernet networks and
Token Ring networks. It is always set to zero for Ethernet switches.
– VLAN Identifier (VID): a 12-bit field specifying the VLAN to which the frame belongs.
On the NE80E/40E, VLAN IDs range from 0 to 4095. The values 0 and 4095 are
reserved, and therefore VLAN IDs range from 1 to 4094.
Each frame sent by an 802.1Q-capable switch carries a VLAN ID. On a VLAN, Ethernet
frames are classified into the following types:
– Tagged frames: frames with 32-bits 802.1Q tags.
– Untagged frames: frames without 32-bits 802.1Q tags.
l Type of VLAN links

Figure 4-4 Schematic diagram for VLAN links
VLAN3 VLAN3
PC3 PC4
Access link
3
3 3
Trunk link Trunk link
2 2
CE1 PE CE2
2
Access link
PC1 PC2
VLAN2 VLAN2
As shown in Figure 4-4, there are the following types of VLAN links:
– Access link: connects a PC to a switch. Generally, a PC does not know which VLAN
it belongs to, and PC hardware cannot distinguish frames with VLAN tags. Therefore,
PCs send and receive only untagged frames.
– Trunk link: connects a switch to another switch or to a router. Data of different VLANs
are transmitted along a trunk link. The two ends of a trunk link must be able to distinguish
frames with VLAN tags. Therefore, only tagged frames are transmitted along trunk
links.
l Port types
Table 4-1 lists VLAN port types.

Table 4-1 Port types

Port Method of Method of Method of Application
Type Processing Processing Sending
Received Received Frames
Untagged Frames Tagged
Frames
Access Accepts an untagged l Accepts a Removes the tag An access port

port frame and adds a tag tagged from a frame and connects a
with the default frame if the sends the frame. switch to a PC
VLAN ID to the VLAN ID and can be
frame. carried in added to only
the frame is one VLAN.
the same as
the default
VLAN ID.
l Discards a
tagged
frame if the
VLAN ID
carried in
the frame is
different
from the
default
VLAN ID.


Frames
Trunk Discards the frame. l Accepts a l Removes the A trunk port

port tagged tag from a can be added to
frame if the received multiple
port permits frame and VLANs to send
the VLAN sends the and receive
ID carried in frame if the frames for these
the frame. VLAN ID VLANs. A
l Discards a carried in the trunk port
tagged frame is the connects a
frame if the same as the switch to
port denies default another switch
the VLAN VLAN ID or to a router.
ID carried in and
the frame. permitted by
the port.
l Directly
sends a
received
frame if the
VLAN ID
carried in the
frame is
different
from the
default
VLAN ID
but permitted
by the port.
Hybrid Sends a received A hybrid port

port frame if the port can be added to
permits the multiple
VLAN ID VLANs to send
carried in the and receive
frame. A frames for these
specified VLANs. A
command can be hybrid port can
used to connect a
determine switch to a PC
whether a hybrid or connect a
port sends network device
frames with or to another
without tags. network
device.


Frames
QinQ QinQ ports are enabled with the IEEE 802.1QinQ protocol. A QinQ port adds
port a tag to a single-tagged frame, and thus supports a maximum of 4094 x 4094
VLAN tags, which meets the requirement of a Metropolitan Area Network
(MAN)for the number of VLANs.
For details about QinQ, see 5 QinQ Configuration.
Each access, trunk, hybrid, or QinQ port can be configured with a default VLAN, namely,
the port default VLAN ID (PVID) to specify the VLAN to which the port belongs.
– The PVID of an access port indicates the VLAN to which the port belongs.
– As a trunk or hybrid port can be added to multiple VLANs, the port must be configured
with PVIDs.
By default, a port is added to VLAN 0.
l Principle for data switching in a VLAN
Use the network shown in Figure 4-4 as an example. If PC 1 in VLAN 2 intends to send
data to PC 2, the data is forwarded as follows:
1. An access port on CE 1 receives an untagged frame from PC 1 and adds a PVID
(VLAN 2) to the frame. CE 1 searches the MAC address table for an outbound port.
Then the frame is transmitted from the outbound port.
NOTE
Assume that VLANs are configured based on MAC addresses. After an access port on CE 1
receives an untagged frame from PC 1, the port checks the VLAN mapping table for a VLAN
ID corresponding to the source MAC address, and adds a tag with the obtained VLAN ID to
the frame.
2. After the trunk port on CE 1 and PE receives the frame, the port checks whether the
VLAN ID carried in the frame is the same as that configured on the port. If the VLAN
ID has been configured on the port, the port transparently transmits the frame to CE
2. If the VLAN ID is not configured on the port, the port discards the frame.
3. After a trunk port on CE 2 receives the frame, the system searches the MAC address
table for an outbound port which connects CE 2 to PC 2.
4. After the frame is sent to the access port connecting CE 2 to PC 2, the port checks that
the VLAN ID carried in the frame is the same as that configured on the port. The port
then removes the tag from the frame and sends the untagged frame to PC 2.
l VLANIF interface
A VLANIF interface is a Layer 3 logical interface, which can be configured on either a
Layer 3 switch or a router.
Layer 3 switching combines routing and switching techniques to implement routing on a
switch, thus improving the overall network performance. After sending the first data flow,
a Layer 3 switch generates mappings between MAC addresses and IP addresses. To send
the same data flow, the switch directly sends the data flow at Layer 2 but not Layer 3 based
on this mapping table.

To allow that new data flows are correctly forwarded based on the routing table, be sure
that the routing table's routing entries are correct. Therefore, VLANIF interfaces and
routing protocols must be configured on Layer 3 switches for reachable Layer 3 routes.
NOTE
Key points are summarized as follows:

l A PC does not need to know the VLAN to which it belongs. It sends only untagged frames.
l After receiving an untagged frame from a PC, a switching device determines the VLAN to which
the frame belongs. The determination is based on the configured VLAN division method such as port
information, and then the switching device processes the frame accordingly.
l If the frame needs to be forwarded to another switching device, the frame must be transparently
transmitted along a trunk link. Frames transmitted along trunk links must carry VLAN tags to allow
other switching devices to properly forward the frame based on the VLAN information.
l Before sending the frame to the destination PC, the switching device connected to the destination PC
removes the VLAN tag from the frame to ensure that the PC receives an untagged frame.
Generally, only tagged frames are transmitted on trunk links; only untagged frames are transmitted on
access links. In this manner, switching devices on the network can properly process VLAN information
and PCs are not concerned about VLAN information.
4.1.2 VLAN Features Supported by the NE80E/40E

This section describes VLAN features supported by the NE80E/40E in light of better
understanding the process of configuring VLANs.
The VLAN technology helps set up virtual groups to separate broadcast domains and implements
both intra-VLAN and inter-VLAN communication.
1. After VLANs are configured, users in a VLAN can communicate with each other.
2. In addition to intra-VLAN communication, users in different VLANs need to communicate
with each other sometimes.
NOTE
Intra-VLAN communication and inter-VLAN communication are basic VLAN functions.
3. Security configurations are required to ensure reliable VLAN data transmission.
4. The following VLAN features are also supported to meet requirements of special
applications and extended functions:
l VLAN aggregation: prevents the waste of IP addresses and implements inter-VLAN
communication.
l VLAN policy: allows user traffic of different types in a VPN to be distinguished and
reasonably scheduled on the backbone network. This provides better service quality
experience for users.
Port-based VLAN Division

Ports on Layer 2 switches can be added to a specific VLAN to forward frames of the VLAN.
PCs in the VLAN can directly communicate with each other, whereas PCs in different VLANs
cannot directly communicate with each other. In this manner, broadcast packets are forwarded
only within a single VLAN.
To classify VLANs based on ports, you only need to add ports on Layer 2 switches to VLANs.
Port-based VLAN classification is applicable to large-scale and topology-stable networks.

Inter-VLAN Communication
After VLANs are configured, users in a VLAN can communicate with each other. Users in
different VLANs cannot directly communicate with each other. Table 4-2 lists schemes for inter-
VLAN communication.
Table 4-2 Schemes for inter-VLAN communication

Inter-VLAN Advantage Disadvantage Usage Scenario
Communica
tion Scheme
Sub-interface After sub-interfaces are l Both Layer 2 and This scheme is

configured, users in Layer 3 devices are applicable to small-
different VLANs and required, which scale networks on
network segments can increases which users belong to
communicate with expenditure. different network
each other as long as l If multiple users on a segments.
routes are reachable. network belong to If Layer 3 forwarding
different VLANs, of packets is mainly
each VLAN requires required, use sub-
a sub-interface on a interfaces.
Layer 3 device. Each
sub-interface needs
to be assigned an IP
address. This
increases
configuration
workload and uses
up a large number of
IP addresses.
VLANIF After VLANIF If multiple users on a This scheme is

interface interfaces are network belong to applicable to small-
configured, users in different VLANs, each scale networks on
different VLANs and VLAN requires a which users belong to
network segments can VLANIF interface. different network
communicate with Each VLANIF interface segments and IP
each other as long as needs to be assigned an addresses of these
routes are reachable. IP address. This users are seldom
Inter-VLAN increases configuration changed.
communication can workload and uses a lot If a large number of
also be implemented by of IP addresses. VLANs are configured
Layer 3 switches if and both Layer 2 and
routes are reachable. Layer 3 forwarding of
This scheme boasts of packets are required,
low operating costs. use VLANIF
interfaces.


Communica
tion Scheme
VLAN This scheme is easily IP addresses of users in This scheme is

mapping configured and does different VLANs must applicable to large-
not rely on routes. belong to the same scale networks on
network segment. which multiple users
belong to one network
segment.
VLAN Security Deployment

Table 4-3 lists schemes that can be deployed to ensure reliable transmission of VLAN data.
Table 4-3 Security schemes for VLANs

Securit Description Advantage Disadvantage Usage
y Scenario
Schem
e
Disabli If a port in a - - This security

ng a VLAN receives a scheme is
port broadcast or applicable to
from unknown unicast topology-stable
broadca packet, it will networks or
sting broadcast the networks on
packets packet to other which MAC
to other ports in the addresses are
ports in VLAN. If the configured and
the broadcast or forwarding
same unknown unicast paths are
VLAN packet is specified.
malicious, system
resources waste
and device
performance
deteriorates or
even the device
malfunctions.
Disabling the port
from broadcasting
packets to other
ports in the VLAN
prevents
malicious attacks.


y Scenario
Schem
e
Disabli l If a device has l MAC address This security scheme This security
ng only one entries are requires that the scheme is
MAC inbound port saved. network has fixed applicable to
address and one l Security is users and forwarding topology-stable
learning outbound port, guaranteed paths have been networks or
in a MAC address because no established by using networks on
VLAN learning in a new users will dynamic MAC which MAC
VLAN can be be connected address learning or addresses are
disabled. to the network. by manually configured and
l This security configuring MAC forwarding
scheme is addresses. paths are
applicable to If there are a large specified.
networks that number of users
are no longer connected to a
accommodatin switch, each user
g new users. needs to be
configured with a
static forwarding
path. This imposes a
configuration burden
on network
administrators.
This security scheme
prohibits new users
from visiting the
network.
Enablin If a device has This security This scheme allows This security
g only one inbound scheme saves malicious users to scheme is
flexible port and one MAC address visit the network and applicable to all
MAC outbound port, entries and allows the system learns Layer 2
address enabling flexible new users to visit MAC addresses of networks.
learning MAC address the network. these users, which
in a learning saves threatens network
VLAN MAC address security.
entries.
When a new user
connects to the
device, MAC
address learning is
automatically
enabled.
VLAN Policy-based VPN Access

On a Metro Ethernet (ME) network, devices use VLAN IDs to identify various services or user
data flows before sending them to various Virtual Switching Instances (VSIs), Virtual Leased

Lines (VLLs), or Virtual Private Network (VPN) instances. In some scenarios (such as multiple
users or services sharing one VLAN), services or user data flows cannot be distinguished by
merely using VLAN IDs. To prevent this problem, you can configure a VLAN policy to use
combinations of VLAN IDs and traffic priorities to distinguish services or user data flows. Table
4-4 shows VLAN policies.
Table 4-4 VLAN policies
VLAN Description
Policy
VLAN VLAN IDs and 802.1p priority values in frames are used to distinguish users
+802.1p or services.
This policy helps user data flows or services access L2VPNs or L3VPNs.
VLAN VLAN IDs and DSCP priority values in packets are used to distinguish users
+DSCP or services.
This policy helps user data flows or services access L2VPNs or L3VPNs.
VLAN VLAN IDs and EthType values in frames are used to distinguish users or
+EthType services.
This policy helps user data flows or services access only L2VPNs.
Port Isolation in a VLAN

The NE80E/40E supports port isolation in a VLAN. One or a group of ports can be isolated in
the VLAN.
For port-based isolation in a VLAN, the isolated ports cannot communicate with each other at
the data link layer. For communication, ARP proxy in the VLAN must be configured for the
isolated ports. In this way, traffic in the VLAN can be monitored at the network layer.
For the isolation based on port groups in a VLAN, you can isolate the packets between port
groups by adding ports to different port groups. The ports in an isolated port group can
communicate with each other and with the ports that are not added to an isolated port group.
The isolation based on port groups supports the flexible planning of a VLAN and is mainly
applied on the RRPP network. A VLAN involves multiple RRPP rings. The ports on different
RRPP rings can be added to different port groups to avoid the broadcast storm.
Ethernet Loop Detection for a VLAN

To avoid the impact of single point failures on services, user networks are connected to the
VLAN network of a carrier through redundant links. The redundant links, however, lead to loops,
which further causes the broadcast storm. In networking applications, you can deploy the
Spanning Tree Protocol (STP) or common loopback detection technologies to avoid the
preceding problems. In practice, however, STP should be deployed at the user side, and the
common loopback detection technology requires the devices at the user side to allow special
Layer 2 loopback detection packets to pass through. When user networks cannot be controlled,
you can deploy Ethernet loop detection supported by the NE80E/40E over the carrier network.
Ethernet loop detection need not be deployed at the user side. This also avoids the broadcast
storm caused by loops formed in a VLAN network.

4.2 Configuring a VLAN Based on Ports

Configuring a VLAN based on ports allows PCs in the VLAN to communicate with each other.

Before configuring a VLAN based on ports, familiarize yourself with the applicable
A company has multiple departments located in different buildings. For service security, it is
required that employees in one department be able to communicate with each other, whereas
employees in different departments be prohibited from communicating with each other. Devices
on the network shown in Figure 4-5 are configured as follows:
l Add ports connecting switches to PCs of the financial department to VLAN 5 and ports
connecting switches to PCs of the marketing department to VLAN 9. This configuration
prevents employees in financial and marketing departments from communicating with each
other.
l Configure links between switches and router as trunk links to allow frames from VLAN 5
and VLAN 9 to pass through, allowing employees of the same department but different
buildings to communicate with each other.
Figure 4-5 Networking diagram for configuring a VLAN Based on Ports
network
PE
CE1 CE2
GE1/0/1 GE1/0/1
GE1/0/1 GE1/0/2
Trunk ( VLAN 5 VLAN 9 )
VLAN 5 VLAN 9 VLAN 5 VLAN 9

Finance Marketing Finance Marketing
Department Department Department Department

Before configuring a VLAN based on ports, complete the following task:
l Connecting ports and configuring physical parameters of the ports, ensuring that the ports
are physically Up
Data Preparation
To configure a VLAN based on ports, you need the following data.
No. Data
1 ID of a VLAN
2 Number of each Ethernet port to be added to the VLAN
3 Type and priority of each Ethernet port
4.2.2 Creating a VLAN

Creating a VLAN isolates PCs that do not need to communicate with each other. This improves
network security, reduces broadcast traffic, and prevents broadcast storms.
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
A VLAN is created, and the VLAN view is displayed. If the specified VLAN has been created,
the VLAN view is directly displayed.
By default, the VLAN ID is 0.
The VLAN ID ranges from 1 to 4094. If VLANs need to be created in batches, you can run the
vlan batch command to create VLANs in batches, and then run the vlan vlan-id command to
enter the view of a specified VLAN.
----End
4.2.3 Configuring the Type of a Layer 2 Ethernet Port

On a Layer 2 switching device, some ports identify frames with VLAN tags, whereas the others
do not. Configure ports types for Layer 2 Ethernet ports as needed.
Context
Table 4-5 lists Layer 2 Ethernet port types.

Table 4-5 Port types

Received Untagged Received Frames
Frames Tagged
Frames
Access Accepts an untagged l Accepts a Removes the tag An access port

port frame and adds a tag tagged frame from a frame and connects a
with the default if the VLAN sends the frame. switch to a PC
VLAN ID to the ID carried in and can be added
frame. the frame is to only one
the same as VLAN.
the default
VLAN ID.
l Discards a
tagged frame
if the VLAN
ID carried in
the frame is
different
from the
default
VLAN ID.
Trunk Discards the frame. l Accepts a l Removes the A trunk port can
port tagged frame tag from a be added to
if the port received multiple VLANs
permits the frame and to send and
VLAN ID sends the receive frames
carried in the frame if the for these
frame. VLAN ID VLANs. A trunk
l Discards a carried in the port connects a
tagged frame frame is the switch to
if the port same as the another switch
denies the default VLAN or to a router.
VLAN ID ID and
carried in the permitted by
frame. the port.
l Directly sends
a received
frame if the
VLAN ID
carried in the
frame is
different from
the default
VLAN ID but
permitted by
the port.


Received Untagged Received Frames
Frames Tagged
Frames
Hybrid Sends a received A hybrid port

port frame if the port can be added to
permits the multiple VLANs
VLAN ID carried to send and
in the frame. A receive frames
specified for these
command can be VLANs. A
used to determine hybrid port can
whether a hybrid connect a switch
port sends frames to a PC or
with or without connect a
tags. network device
to another
network device.
QinQ QinQ ports are enabled with the IEEE 802.1QinQ protocol. A QinQ port adds a
port tag to a single-tagged frame, and thus supports a maximum of 4094 x 4094 VLAN
tags, which meets the requirement of a Metropolitan Area Network (MAN)for the
number of VLANs.
For details about QinQ, see 5 QinQ Configuration.
Do as follows on the PE.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of a Layer 3 Ethernet interface to be added to a VLAN is displayed.

Step 3 Run:
portswitch
The Layer 3 interface is switched to the Layer 2 mode.

l If an interface is borrowing the IP address of an Ethernet, a GE, or an Eth-Trunk, the
portswitch command cannot be run on the Ethernet, GE, or Eth-Trunk.
l If the Ethernet, GE, or Eth-Trunk has any Layer 3 configuration, the portswitch command
cannot be run on the interface. Before running the portswitch command on the interface,
clear all Layer 3 configurations on the interface.
Step 4 Run:

The port type is configured.

By default, the port type is hybrid.
----End
4.2.4 Adding a Port to a VLAN

Adding a port to a VLAN associates the port with the VLAN.
Context
l A port connecting a switch to a PC must be configured as an access or a hybrid port.
The port trunk allow-pass vlan command is invalid on access ports.
l A port connecting one switch to another must be configured as a trunk or hybrid port.
The port default vlan command cannot be used on trunk ports.
Procedure
l Add an Ethernet port to a VLAN in the port view.
1. Run:
system-view

2. Run:
The view of a Layer 2 Ethernet interface to be added to a VLAN is displayed.

3. Run:
port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] } &<1-10> | all }
To add a port to a VLAN in tagged mode.

l Add an Ethernet port to a VLAN in the VLAN view.
1. Run:
system-view

2. Run:
vlan vlan-id
The view of the created VLAN is displayed.

3. Run:
port interface-type { interface-number1 [ to interface-number2 ] } &<1-10>
A port or a group of ports are added to a VLAN.
NOTE
The input port format must be correct. The port number following to must be greater than the
port number before to. If a group of ports are specified, ensure that these ports are of the same
type and all specified ports exist.
In one port command, a maximum of 10 groups of ports can be specified by using to.
----End


After VLANs are configured based on ports, you can view the number of created VLANs and
VLAN types.
Prerequisite
The configurations of port-based VLAN division are complete.
Procedure
Step 1 Run the display vlan [ vlan-id [ verbose ] ] command to check VLAN information.
----End
Example
Run the display vlan command. The command output shows the number of created VLANs on
the device and information about VLANs such as VLAN types. For example:
<HUAWEI> display vlan
The total number of vlans is : 6
VLAN ID Type Status MAC Learning Broadcast/Multicast/Unicast
Property
---------------------------------------------------------------------------------
1 sub enable enable forward forward forward default
2 super enable enable forward forward forward default
3 sub enable enable forward forward forward default
4 common enable enable forward forward forward default
10 common enable disable discard discard discard
backboneVLAN
4.3 Creating a VLANIF Interface

VLANIF interfaces are Layer 3 logical interfaces. After creating VLANIF interfaces on Layer
2 devices, you can configure Layer 3 features on these interfaces.

Before creating a VLANIF interface, familiarize yourself with the applicable environment,
complete the pre-configuration tasks, and obtain the data required for the configuration. This
will help you complete the configuration task quickly and accurately.
Layer 3 switching combines routing and switching techniques to implement routing on a switch,
thus improving the overall network performance. After sending the first data flow, a Layer 3
switch generates mappings between MAC addresses and IP addresses. To send the same data
flow, the switch directly sends the data flow at Layer 2 but not Layer 3 based on this mapping
table.
To allow that new data flows are correctly forwarded based on the routing table, be sure that the
routing table's routing entries are correct. Therefore, VLANIF interfaces and routing protocols
must be configured on Layer 3 switches for reachable Layer 3 routes.

Before creating a VLANIF interface, complete the following task:
l Creating a VLAN
Data Preparation
To create a VLANIF interface, you need to the following data.
No. Data
1 VLAN ID
2 IP address to be assigned to the VLANIF interface
3 (Optional) Delay after which the VLANIF interface goes Down
4 (Optional) Bandwidth of the VLANIF interface
4.3.2 Creating a VLANIF Interface

Before configure Layer 3 features on a Layer 2 device, you must create a VLANIF interface on
the device.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface vlanif vlan-id
A VLANIF interface is created and the VLAIF interface view is displayed.
The VLAN ID specified in this command must be the ID of an existing VLAN.
NOTE
A VLANIF interface is Up only when at least one physical port added to the corresponding VLAN is Up.
----End
4.3.3 Assigning an IP Address to a VLANIF Interface

As a VLANIF interface is a Layer 3 logical interface, it can communicate with other interfaces
at the network layer only after being assigned an IP address.
Procedure
Step 1 Run:
system-view


Step 2 Run:
The VLANIF interface view is displayed.

Step 3 Run:
An IP address is assigned to the VLANIF interface for communication at the network layer.
NOTE
If IP addresses assigned to VLANIF interfaces on a Layer 3 device belong to different network segments,
a routing protocol must be configured on the Layer 3 switch to provide reachable routes. Otherwise,
VLANIF interfaces cannot communicate with each other at the network layer. For configurations of routing
protocols, see the NE80E/40E Configuration Guide - IP Routing.
----End
4.3.4 (Optional) Setting a Delay After Which a VLANIF Interface

Goes Down
Setting a delay after which a VLANIF interface goes Down prevents network flapping caused
by changes of VLANIF interface status. This function is also called VLAN damping.
Context
If a VLAN goes Down because all ports in the VLAN go Down, the system immediately reports
the VLAN Down event to the corresponding VLANIF interface, instructing the VLANIF
interface to go Down.
To prevent network flapping caused by changes of VLANIF interface status, enable VLAN
damping on the VLANIF interface. After the last Up port in a VLAN goes Down, the system
starts a delay timer and informs the corresponding VLANIF interface of the VLAN Down event
after the timer expires. If a port in the VLAN goes Up during the delay period, the VLANIF
interface remains Up.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
damping time delay-time
The delay for VLAN damping is set.

The delay-time value ranges from 0 to 20, in seconds. By default, the value is 0 seconds,
indicating that VLAN damping is disabled.
----End
4.3.5 (Optional) Configuring Bandwidth for a VLANIF Interface

After configuring bandwidth for VLANIF interfaces, you can use the NMS to query the
bandwidth. This facilitates traffic monitoring.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
bandwidth bandwidth
The VLANIF interface is configured with bandwidth.

By default, the bandwidth of a VLANIF interface is 1000 Mbit/s.
----End

After a VLANIF interface is configured for communication at the network layer, you can check
the IP address and status of a specified VLANIF interface.
Prerequisite
The configurations of a VLANIF interface are complete.
Procedure
l Run the display interface vlanif [ vlan-id ] command to check the physical status, link
protocol status, description, and IP address of the VLANIF interface.
----End
Example
Run the display interface vlanif command. The command output shows the physical status,
link protocol status, IP address, and mask of a VLANIF interface. For example:
<HUAWEI> display interface Vlanif 10
Vlanif10 current state : UP
Last line protocol up time : 2010-08-10 15:13:07 UTC-08:00

Description:HUAWEI, Vlanif10 Interface

Route Port,The Maximum Transmit Unit is 1500
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 0018-2000-0140
Physical is VLANIF
Input bandwidth utilization : --
Output bandwidth utilization : --
4.4 Configuring Inter-VLAN Communication

Configuring inter-VLAN communication allows users in different VLANs to communicate with
each other. Currently, the NE80E/40E supports several inter-VLAN communication schemes.

Before configuring inter-VLAN communication, familiarize yourself with the applicable
Currently, schemes listed in Table 4-6 are provided for inter-VLAN communication. You can
choose one of them based on the real world situation.

Table 4-6 Schemes for inter-VLAN communication

Communica
tion Scheme
Sub-interface After sub-interfaces are l Both Layer 2 and This scheme is

configured, users in Layer 3 devices are applicable to small-
different VLANs and required, which scale networks on
network segments can increases which users belong to
communicate with expenditure. different network
each other as long as l If multiple users on a segments.
routes are reachable. network belong to If Layer 3 forwarding
different VLANs, of packets is mainly
each VLAN requires required, use sub-
a sub-interface on a interfaces.
Layer 3 device. Each
sub-interface needs
to be assigned an IP
address. This
increases
configuration
workload and uses
up a large number of
IP addresses.
VLANIF After VLANIF If multiple users on a This scheme is

interface interfaces are network belong to applicable to small-
configured, users in different VLANs, each scale networks on
different VLANs and VLAN requires a which users belong to
network segments can VLANIF interface. different network
communicate with Each VLANIF interface segments and IP
each other as long as needs to be assigned an addresses of these
routes are reachable. IP address. This users are seldom
Inter-VLAN increases configuration changed.
communication can workload and uses a lot If a large number of
also be implemented by of IP addresses. VLANs are configured
Layer 3 switches if and both Layer 2 and
routes are reachable. Layer 3 forwarding of
This scheme boasts of packets are required,
low operating costs. use VLANIF
interfaces.
VLAN This scheme is easily IP addresses of users in This scheme is

mapping configured and does different VLANs must applicable to large-
not rely on routes. belong to the same scale networks on
network segment. which multiple users
belong to one network
segment.

Before configuring inter-VLAN communication, complete the following task:
l Creating VLANs
Data Preparation
To configure inter-VLAN communication, you need the following data.
No. Data
1 Number of each Ethernet sub-interface, IP address and mask of the sub-interface,

and VLAN ID associated with the sub-interface
2 VLAN ID, VLANIF interface number, IP address and mask of the VLANIF
interface, and (optional) bandwidth of the VLANIF interface
3 (Optional) Port type, VLAN ID before mapping, and VLAN ID after mapping
4.4.2 Configuring Sub-interfaces for Inter-VLAN Communication

If users belong to different VLANs and reside on different network segments, sub-interfaces can
be created on a router and assigned IP addresses to allow these users to communicate with each
other at the network layer.
Context
During communication at the data link layer on a LAN, source MAC addresses identify where
data comes from, and destination MAC addresses guide data to destinations. If the source and
destination PCs reside on different network segments, a Layer 2 network is unable to send data
from the source to the destination. In this case, data has to be forwarded at the network layer 3.
After the default gateway address of the switch is specified as the IP address of the router, the
switch sends data that needs to be forwarded at the network layer to the router. After receiving
a packet, the router searches its routing table according to the destination address in the packet.
If the router finds a matching route in the routing table, the router directly forwards the packet
to another network segment. If the router does not find any matching route, it discards the packet.
On the network shown in Figure 4-6, VLANs 2 to n belong to different network segments. To
allow users in VLANs 2 to n to communicate with each other, you can create a sub-interface on
the router for each VLAN and assign an IP address to each sub-interface. After VLANs are
configured, the switch is logically divided into n parts. Accordingly, the router must have n
logical interfaces corresponding to n VLANs. The detailed implementation process is as follows:
1. A PC in VLAN 2 checks the destination IP address and finds that the destination PC in
VLAN n is on a different network segment.
2. The PC in VLAN 2 sends an ARP request. After receiving the request, the router considers
itself the destination, translates its MAC address into an IP address, and sends an ARP reply
to the PC in VLAN 2.
3. After receiving data from the PC in VLAN 2, the Layer 2 switch adds a VLAN tag to the
data and searches the MAC address table for an outbound port.
4. The router receives the frame and sends it to sub-interface 2.

5. Sub-interface 2 removes the VLAN tag from the frame, searches for an ARP entry based
on the IP address in the IP header, and forwards the packet at the network layer.
6. Sub-interface n receives the packet, reencapsulates the packet with the VLAN ID of n and
the destination MAC address of the MAC address of the destination PC, and sends the
frame.
7. After receiving the frame, the Layer 2 switch searches the MAC address table for the
destination MAC address based on the VLAN ID carried in the packet to determine the
outbound port.
8. The PC in VLAN n receives the frame from VLAN 2.
If a PC in VLAN n sends a packet to a PC in VLAN 2, the process is similar and not
described in this document.
Figure 4-6 Networking diagram for configuring sub-interfaces for inter-VLAN communication
Router
GE1/0/1.2 GE1/0/1.n
IP Address:x.x.x.x/x IP Address:x.x.x.x/x
Trunk
Switch
Access port
VLAN2 VLANn
On the network shown in Figure 4-6, downstream ports on the switch are separately added to
VLAN 2 to VLAN n. The configuration roadmap for communication between these VLANs is
as follows:
1. Create n-1 sub-interfaces on the Etherent interface connecting the router to the switch.
2. The sub-interface is associated with a VLAN.
3. Assign an IP address to each sub-interface for communication at the network layer.
4. Configure the port connecting the switch to the router as a trunk or hybrid port to allow
frames with VLAN IDs from 2 to n to pass through.
NOTE
The default gateway address of each PC in a VLAN must be the IP address of the corresponding sub-
interface. Otherwise, inter-VLAN communication fails.

Procedure
l Do as follows on the router:
1. Run:
system-view

2. Run:
interface { ethernet | gigabitethernet } interface-number.subinterface-
number
An Ethernet sub-interface is created and the view of the Ethernet sub-interface is

displayed.
The Ethernet interface in this step is the interface connecting the router to the switch.
3. Run:
vlan-type dot1q vlan-id
The sub-interface is associated with a VLAN.
NOTE
Sub-interfaces of different interfaces can be associated with the same VLAN; sub-interfaces
of one interface cannot be associated with the same VLAN.
4. Run:
An IP address is assigned to the sub-interface for communication at the network layer.

l Do as follows on the switch:
Configure VLANs. For details, see 4.2 Configuring a VLAN Based on Ports.
----End
4.4.3 Configuring VLANIF Interfaces for Inter-VLAN

Communication
Configuring VLANIF interfaces for inter-VLAN communication saves expenditure and helps
implement fast forwarding.
Context
VLAIF interfaces are Layer 3 logical interfaces. After being assigned IP addresses, VLANIF
interfaces are able to communicate at the network layer. Layer 3 switches and routers can be
configured with VLANIF interfaces.
By using VLANIF interfaces to implement inter-VLAN communication, you need to configure
a VLANIF interface for each VLAN and assign an IP address to each VLANIF interface. The
communication process by using VLANIF interfaces is similar to that by using sub-interfaces.

Figure 4-7 Networking diagram for configuring VLANIF interfaces for inter-VLAN
communication
PE
VLANIF2 VLANIFn
CE1 CE2
VLAN2 VLANn
NOTE
The default gateway address of each PC in a VLAN must be the IP address of the corresponding VLANIF
interface. Otherwise, inter-VLAN communication will fail.
Procedure
Step 1 Run:
system-view
Step 2 Run:
A VLANIF interface is created and the VLAIF interface view is displayed.
NOTE
A VLANIF interface is Up only when at least one physical port added to the corresponding VLAN is Up.
Step 3 Run:
An IP address is assigned to the VLANIF interface.
VLANIF interfaces must belong to different network segments.
----End
4.4.4 Configuring VLAN Mapping for Inter-VLAN Communication

The configuration of VLAN mapping is simple and independent of Layer 3 routing.

Context
VLAN mapping is also called VLAN translation. With VLAN mapping, a switch maps the
VLAN tag of a frame to another VLAN tag after receiving the frame and before sending the
frame. On the network shown in Figure 4-8, ports connecting CE 1 to users are added to VLAN
2 and ports connecting CE 2 to users are added to VLAN 3. To allow users in VLAN 2 and
VLAN 3 to communicate with each other, configure VLAN mapping on GE 1/0/1 connecting
CE 1 to CE 2.
l Before sending a frame to VLAN 3, GE 1/0/1 on CE 1 replaces the VLAN ID 2 in the frame
with the VLAN ID 3.
l After receiving a frame from VLAN 3, GE 1/0/1 on CE 1 replaces the VLAN ID 3 in the
frame with the VLAN ID 2.
Figure 4-8 Networking diagram for configuring VLAN mapping for inter-VLAN
communication
VLAN2 VLAN3
2 3
CE1 GE1/0/1 3 CE2
2 3
2 3
172.16.0.1/16 172.16.0.7/16
NOTE
Before configuring VLAN mapping to allow PCs in two VLANs to communicate, IP addresses of the PCs
must belong to the same network segment. Otherwise, devices in different VLANs must communicate with
each other at the network layer. In this case, VLAN mapping does not make sense.
Procedure
Step 1 Run:
system-view
Step 2 Add ports connecting CE 1 and CE 2 to users to separate VLANs.

Configure VLANs. For details, see 4.2 Configuring a VLAN Based on Ports.
Step 3 Configure the Layer 2 port type.
1. Run the interface interface-ytpe interface-number command to enter the view of an
Ethernet port to be configured with VLAN mapping.
2. Run the port link-type trunk command to configure the Layer 2 Ethernet port as a trunk
port.
Step 4 Run:
port vlan-mapping vlan vlan-id1 [ to vlan-id2 ] map-vlan vlan-id3
VLAN mapping is configured to change the outer VLAN tag to vlan-id3.

By default, VLAN mapping is disabled on ports.
Step 5 Run the port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] } &<1-10> | all } command to
specify the VLAN IDs. Frames carrying these VLAN IDs can pass through the port configured
with VLAN mapping.
The VLAN ID specified in this command must be private VLAN IDs but not public VLAN IDs.
----End

After inter-VLAN communication is configured, you can check whether users in different
VLANs can communicate with each other and check information about VLANs to which users
belong.
Prerequisite
The configurations of inter-VLAN communication are complete.
Procedure
l Run the ping [ ip ] [ -a source-ip-address | -c count | -d | -f | -h ttl-value | -i interface-
type interface-number | -m time | -n | -p pattern | -q | -r | -s packetsize | -system-time | -t
timeout | -tos tos-value | -v | -vpn-instance vpn-instance-name ] * host command to check
whether users in different VLANs can communicate with each other.
If the ping fails, you can run the following commands to locate the fault:
– Run the display vlan [ vlan-id [ verbose ] ] command to check information about all
VLANs or a specified VLAN.
– Run the display interface vlanif [ vlan-id ] command to check information about
VLANIF interfaces.
Before running this command, ensure that VLANIF interfaces have been configured.
– If VLAN aggregation is configured, run the following commands:
– Run the display super-vlan [ vlan-id ] command to check sub-VLANs contained
in a super-VLAN.
– Run the display sub-vlan [ vlan-id ] command to check mappings between sub-
VLANs and super-VLANs.
----End

Example
Check whether the PC at 10.1.1.2 is reachable.
<HUAWEI> ping 10.1.1.2
0.00% packet loss
If the ping fails, you can run the following commands to locate the fault:
l Run the display vlan command. The command output shows the VLAN ID, VLAN type,
and VLAN status. For example:
VLAN ID Type Status MAC Learning Broadcast/Multicast/Unicast
Property
------------------------------------------------------------------------------
--
30 *common enable enable forward forward forward default
l Run the display interface vlanif command. The command output shows the physical
status, link protocol status, IP address, and mask of a VLANIF interface. For example:
<HUAWEI> display interface Vlanif 10
Last line protocol up time : 2010-08-10 15:13:07 UTC-08:00
Description:HUAWEI, Vlanif10 Interface
0018-2000-0140
Input: 0 packets, 0 bytes
Output: 0 packets, 0 bytes
Input bandwidth utilization : --

Output bandwidth utilization : --
l Run the display sub-vlan command. The command output shows the VLAN ID of each
sub-VLAN and the VLAN ID of each super-VLAN to which a sub-VLAN belongs.
<HUAWEI> display sub-vlan
VLAN ID Super-vlan
-----------------------------
10 40
20 40
30 40
l Run the display super-vlan command. The command output shows the VLAN ID of each
sub-VLAN and the VLAN ID of each super-VLAN to which a sub-VLAN belongs.
<HUAWEI> display super-vlan
VLAN ID Sub-vlan
--------------------------
40 10 20 30

4.5 Configuring VLAN Security Attributes

Configuring VLAN security attributes ensures reliable transmission of user data. Currently, the
NE80E/40E supports several security attributes. You can configure security attributes as
required.

Before configuring VLAN security attributes, familiarize yourself with the applicable
Table 4-7 lists VLAN security attribute schemes.
Table 4-7 Security schemes for VLANs

y Scenario
Schem
e
Disabli If a port in a - - This security

ng a VLAN receives a scheme is
port broadcast or applicable to
from unknown unicast topology-stable
broadca packet, it will networks or
sting broadcast the networks on
packets packet to other which MAC
to other ports in the addresses are
ports in VLAN. If the configured and
the broadcast or forwarding
same unknown unicast paths are
VLAN packet is specified.
malicious, system
resources waste
and device
performance
deteriorates or
even the device
malfunctions.
Disabling the port
from broadcasting
packets to other
ports in the VLAN
prevents
malicious attacks.


y Scenario
Schem
e
Disabli l If a device has l MAC address This security scheme This security
ng only one entries are requires that the scheme is
MAC inbound port saved. network has fixed applicable to
address and one l Security is users and forwarding topology-stable
learning outbound port, guaranteed paths have been networks or
in a MAC address because no established by using networks on
VLAN learning in a new users will dynamic MAC which MAC
VLAN can be be connected address learning or addresses are
disabled. to the network. by manually configured and
l This security configuring MAC forwarding
scheme is addresses. paths are
applicable to If there are a large specified.
networks that number of users
are no longer connected to a
accommodatin switch, each user
g new users. needs to be
configured with a
static forwarding
path. This imposes a
configuration burden
on network
administrators.
This security scheme
prohibits new users
from visiting the
network.
Enablin If a device has This security This scheme allows This security
g only one inbound scheme saves malicious users to scheme is
flexible port and one MAC address visit the network and applicable to all
MAC outbound port, entries and allows the system learns Layer 2
address enabling flexible new users to visit MAC addresses of networks.
learning MAC address the network. these users, which
in a learning saves threatens network
VLAN MAC address security.
entries.
When a new user
connects to the
device, MAC
address learning is
automatically
enabled.
Before configuring VLAN security attributes, complete the following task:

l Creating VLANs
Data Preparation
To configure VLAN security attributes, you need the following data.
No. Data
1 VLAN ID and (optional) VLAN name
4.5.2 Disabling a Port from Broadcasting Packets to Other Ports in

the Same VLAN
Disabling a port from broadcasting packets to other ports in the same VLAN prevents malicious
attacks and improves network security.
Context
If a port in a VLAN receives a broadcast or unknown unicast packet, it will broadcast the packet
to other ports in the VLAN. If the broadcast or unknown unicast packet is malicious, system
resources waste and device performance deteriorates or even the device malfunctions. Disabling
the port from broadcasting packets to other ports in the VLAN prevents malicious attacks.
This security scheme is applicable to topology-stable networks or networks on which MAC

addresses are configured and forwarding paths are specified.
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
The VLAN view is displayed.

TIP
If a device is configured with multiple VLANs, do as follows to configure a name for each VLAN:
Run the name vlan-name command in the VLAN view. After a VLAN name is configured, you can run
the vlan vlan-name vlan-name command in the system view to enter the corresponding VLAN view.
Step 3 Run:
broadcast discard
The port is disabled from broadcasting packets to other ports in the same VLAN.
By default, a port can broadcast packets to other ports in the same VLAN.
----End

4.5.3 Disabling MAC Address Learning in a VLAN

If a device has only one inbound port and one outbound port, or the network topology is stable,
MAC address learning in a VLAN can be disabled.
Context
A company has multiple departments located in different stories of a building. It is required that
PCs of one department be grouped into a VLAN and PCs in different departments be grouped
into different VLANs.
On the network shown in Figure 4-9, department 1 belongs to VLAN 2; department 2 belongs
to VLAN 3; the public sector belongs to VLAN 10. Users in VLANs 2 and 3 can access VLAN
10. Users in VLAN 2 or 3 can communicate with each other. Users in VLAN 2 cannot
communicate with users in VLAN 3. To reduce the number of MAC address entries saved on
the core switching device and prevent visitors from accessing the company's network, you can
disable MAC address learning in a VLAN on CE 1 and CE 5.
NOTE
Disabling MAC address learning in a VLAN is suitable for a device that has only one inbound port and
one outbound port or a network with a stable topology.
Figure 4-9 Networking diagram for disabling MAC address learning in a VLAN
PE
mac-address mac-address
learning disable learning disable
CE1 CE2
S1 S4
S2 S3 S5
Department1 Department2 Department1 Public sector

VLAN2 VLAN3 VLAN2 VLAN 10
Procedure
Step 1 Run:
system-view

Step 2 Run:
vlan vlan-id

TIP
Step 3 Run:
mac-address learning disable
MAC address learning in a VLAN is disabled.
By default, MAC address learning is enabled in a VLAN.
----End
Follow-up Procedure
After MAC address learning in a VLAN is disabled, to guarantee high forwarding efficiency,
do as follows:
l Limit the number of MAC addresses in the MAC address table.
l Select an action to be taken when the number of MAC addresses exceeds the upper
threshold, such as discard, forward, or alarm.
4.5.4 Enabling Flexible MAC Address Learning in a VLAN

If a Layer 2 switching device enabled with flexible MAC address learning in a VLAN has only
one inbound port and one outbound port, the system automatically disables MAC address
learning to release resources that have been used for MAC address learning.
Context
If the core switching device of a company has only one inbound port and one outbound port,
you can disable MAC address learning in a VLAN to save resources. On the network shown in
Figure 4-10, after MAC address learning in a VLAN is disabled on CE 1, S1 cannot access the
network. This hinders network expansion. To address this problem, you can enable flexible MAC
address learning in a VLAN on CE 1.
After flexible MAC address learning is enabled on CE 1:

l If CE 1 has only one inbound port and one outbound port, the system automatically disables
MAC address learning to save resources.
l If CE 1 has multiple inbound or outbound ports, the system automatically enables MAC
address learning.
NOTE
l Newly-added users must be in the VLAN enabled with MAC address learning.
l Any Layer 2 network can be enabled with flexible MAC address learning in a VLAN.

Figure 4-10 Networking diagram for enabling flexible MAC address learning in a VLAN
PE PE
mac-learning
mac-address smart vlan enable
learning disable
CE1 CE1
S1 S1
S2 S2
Department1 Departmentn Department1 Departmentn

VLAN2 VLANn VLAN2 VLANn
Procedure
Step 1 Run:
system-view

Step 2 Run:
mac-learning smart vlan { vlan-id1 [ to vlan-id2 ] } &<1-10> enable
Flexible MAC address learning is enabled in a VLAN.

By default, flexible MAC address learning is disabled in a VLAN.
----End
4.5.5 (Optional) Disabling an Interface from Sending Unknown

Unicast Packets to Other Interfaces in a VLAN
Prohibiting interfaces in a VLAN from sending unknown unicast packets can effectively guard
against the broadcast of malicious packets within the VLAN.
Procedure
Step 1 Run:
system-view

Step 2 Run:

vlan vlan-id
Step 3 Run:
unknown-unicast discard [ mac-learning ]
The interfaces in the VLAN are configured to discard unknown unicast packets.
When an interface in a VLAN receives an unknown unicast packet, the interface broadcasts the
packet in the VLAN by default. When the discarding of unknown unicast packets is configured,
you can forbid interfaces in a VLAN to forward unknown unicast packets to restrict broadcast
of malicious packets.
If mac-learning is configured, the interfaces in the VLAN can learn the source MAC addresses
of the received unknown unicast packets when discarding the packets.
----End

After VLAN security attributes are configured, you can check whether a VLAN is enabled with
the broadcast function and the MAC address learning function.
Prerequisite
The configurations of VLAN security attributes are complete.
Procedure
l Run the display vlan [ vlan-id [ verbose ] ] command to check information about all
VLANs or a specified VLAN.
----End
Example
Run the display vlan command. The command output shows that VLANs have been enabled
with the broadcast function and the MAC address learning function. For example:
VLAN ID Type Status MAC Learning Broadcast/Multicast/Unicast Property
--------------------------------------------------------------------------------
4.6 Configuring VLAN Aggregation to Save IP Addresses

VLAN aggregation prevents the waste of IP addresses and implements inter-VLAN
communication.


Before configuring VLAN aggregation, familiarize yourself with the applicable environment,
complete the pre-configuration tasks, and obtain the data required for the configuration. This
will help you complete the configuration task quickly and accurately.
As networks expand, address resources become insufficient. VLAN aggregation is developed
to save IP addresses.
In VLAN aggregation, one super-VLAN is associated with multiple sub-VLANs. Physical ports
cannot join a super-VLAN but a VLANIF interface can be created for the super-VLAN and an
IP address can be assigned to the VLANIF interface. Physical ports can join a sub-VLAN but
no VLANIF interface can be created for the sub-VLAN. All the ports in the sub-VLAN use the
same IP address with the VLANIF interface of the super-VLAN. This saves subnet IDs, default
gateway addresses of the subnets, and directed broadcast addresses of the subnets. In addition,
different broadcast domains can use the addresses in the same subnet segment. As a result, subnet
differences are eliminated, addressing becomes flexible, and the number of idle addresses is
reduced. VLAN aggregation allows each sub-VLAN to function as a broadcast domain and
reduces the waste of IP addresses to be assigned to ordinary VLANs.
Figure 4-11 shows the typical VLAN aggregation networking.
Figure 4-11 Typical networking diagram for VLAN aggregation

PE
Super
VLAN4
CE1 CE2
Sub-VLAN 2 Sub-VLAN 3
Before configuring VLAN aggregation, complete the following task:
l Connecting ports and configuring physical parameters of the ports, ensuring that the ports
are physically Up

Data Preparation
To configure VLAN aggregation, you need the following data.
No. Data
1 ID of each sub-VLAN and number of each port belonging to the sub-VLAN
2 ID of a super-VLAN
3 IP address and mask of a VLANIF interface
4.6.2 Creating a Sub-VLAN

Each sub-VLAN functions as a broadcast domain.
Procedure
Step 1 Run:
system-view

Step 2 Run:
vlan vlan-id
A sub-VLAN is created and the sub-VLAN view is displayed.

TIP
Step 3 Run:
A port is added to the sub-VLAN.
----End
4.6.3 Creating a Super-VLAN

A super-VLAN consists of several sub-VLANs. No physical port can be added to a super-VLAN,
but a VLANIF interface can be configured for the super-VLAN and an IP address can be assigned
to the VLANIF interface.
Context
NOTE
Before configuring a super-VLAN, ensure that sub-VLANs have been configured.
Procedure
Step 1 Run:

system-view

Step 2 Run:
vlan vlan-id
A VLAN is created, and the VLAN view is displayed.

The VLAN ID of a super-VLAN must be different from every sub-VLAN ID.
Step 3 Run:
aggregate-vlan
A super-VLAN is created.
Using the undo aggregate-vlan command in the VLAN view changes a super-VLAN to a sub-
VLAN.
Step 4 Run:
access-vlan { vlan-id1 [ to vlan-id2 ] } &<1-10>
A sub-VLAN is added to a super-VLAN.

Only sub-VLANs can be added to a super-VLAN. Before adding sub-VLANs to a super-VLAN
in batches, ensure that these sub-VLANs are not configured with VLANIF interfaces.
----End
4.6.4 Assigning an IP Address to the VLANIF Interface of a Super-

VLAN
The IP address of the VLANIF interface of a super-VLAN must contain the subnet segments
where users in sub-VLANs reside. All the sub-VLANs use the IP address of the VLANIF
interface of the super-VLAN, thus saving IP addresses.
Procedure
Step 1 Run:
system-view

Step 2 Run:
A VLANIF interface is created for a super-VLAN, and the view of the VLANIF interface is
displayed.
Step 3 Run:
An IP address is assigned to the VLANIF interface.
----End
4.6.5 (Optional) Configuring an IP Address Pool for a Sub-VLAN

Specifying an IP address range for users in a sub-VLAN filters out invalid users of which IP
addresses are beyond the range.

Context
After configuring an IP address pool for a sub-VLAN, note the following points:
l The sub-VLAN processes only packets carrying IP addresses in this address pool, such as
ARP Request, ARP Reply, ARP Proxy, and ARP Miss packets.
l If the super VLAN is enabled with proxy ARP, the system directly sends an ARP Request
packet from a user in the sub-VLAN to the sub-VLAN based on the IP address carried in
the packet. This reduces broadcast traffic.
l When sending an ARP Miss packet carrying the IP address in the address pool, the system
directly broadcasts the packet in the sub-VLAN to ensure that traffic is properly forwarded.
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
The view of a created sub-VLAN is displayed.
Step 3 Run:
ip pool start-address [ to end-address ]
An IP address pool is configured for the sub-VLAN.
----End
4.6.6 (Optional) Enabling Proxy ARP on the VLANIF Interface of a

Super-VLAN
PCs in different sub-VLANs cannot directly communicate with each other in Layer2 network.
To allow these PCs to communicate with each other at Layer 3, enable proxy ARP on the
VLANIF interface of the super-VLAN.
Context
VLAN aggregation allows sub-VLANs to use the same subnet address, but prevents PCs in
different sub-VLANs from communicating with each other at the network layer.
PCs in ordinary VLANs can communicate with each other at the network layer by using different
gateway addresses. In VLAN aggregation, PCs in a super-VLAN use the same subnet address
and gateway address. As PCs in different sub-VLANs belong to one subnet, they communicate
with each other only at Layer 2, not Layer 3. These PCs are isolated from each other at Layer
2. Consequently, PCs in different sub-VLANs cannot communicate with each other.
Proxy ARP is required to enable PCs in a sub-VLAN to communicate with PCs in another sub-
VLAN or PCs on other networks. After a super-VLAN and its VLANIF interface are created,
proxy ARP must be enabled to allow the super-VLAN to forward or process ARP request and
reply packets. Proxy ARP helps PCs in sub-VLANs communicate with each other at the network
layer.

NOTE
An IP address must have been assigned to the VLANIF interface corresponding to the super-VLAN.
Otherwise, proxy ARP cannot take effect.
VLAN aggregation simplifies configurations for the network where many VLANs are
configured and PCs in different VLANs need to communicate with each other.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the VLANIF interface of the super-VLAN is displayed.

Step 3 Run:
arp-proxy enable
Proxy ARP is enabled on the VLANIF interface.

Step 4 Run:
arp-proxy inter-sub-vlan-proxy enable
Inter-sub-VLAN proxy ARP is enabled.
----End

After VLAN aggregation is configured, you can view VLAN types and information about
VLANIF interfaces, such as the physical status, link protocol status, IP address, and mask.
Prerequisite
The VLAN aggregation configurations are complete.
Procedure
l Run the display vlan [ vlan-id [ verbose ] ] command to check VLAN information.
l Run the display interface vlanif [ vlan-id ] command to check information about a specific
VLANIF interface.
l Run the display sub-vlan command to check mappings between sub-VLANs and super-
VLANs.
l Run the display super-vlan command to check sub-VLANs contained in a super-VLAN.
----End
Example
Run the display vlan verbose command. The command output shows the VLAN type. For
example:
<HUAWEI> display vlan 40 verbose

VLAN ID : 40
VLAN Type : Super
Description : VLAN 0040
Status : Enable
Broadcast : Enable
MAC learning : Enable
Statistics : Disable
---------------
sub-VLAN List: 3
Run the display interface vlanif command. The command output shows the physical status,
link protocol status, IP address, and mask of a VLANIF interface. For example:
<HUAWEI> display interface vlanif 2
Last line protocol up time : 2009-04-07 10:51:54
Description : Vlanif10 Interface, Route Port
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-ab74-7700
Physical is VLANIF
0 errors,0 drops
Run the display sub-vlan command. The command output shows mappings between sub-
VLANs and super-VLANs.
<HUAWEI> display sub-vlan
VLAN ID Super-vlan
-----------------------------
10 40
20 40
30 40
Run the display super-vlan command. The command output shows sub-VLANs contained in
a super-VLAN.
<HUAWEI> display super-vlan
VLAN ID Sub-vlan
--------------------------
40 10 20 30
4.7 Configuring VLAN Policy-based VPN Access

VLAN policy-based VPN access allows VLLs, VSIs, or VPN instances to transmit separate
services. Currently, the NE80E/40E supports several VLAN policy-based VPN access schemes.

Before configuring VLAN policy-based VPN access, familiarize yourself with the applicable

On a Metro Ethernet (ME) network, VLAN IDs are used to identify various services or user
packets before them access to various VSIs, VLLs, or VPN instances. If multiple types of
services share one VLAN ID, as shown in Figure 4-12, services cannot be differentiated merely
by using VLAN IDs. As a result, part of high-priority traffic over the operator's network cannot
be scheduled in time, which deteriorates users' experience.
Figure 4-12 Networking diagram for multiple types of services sharing one VLAN ID
BTV VOD
Platform
SR Video
PW 1
HSI UPE
VoIP Switch
Internet
PW 2
BRAS
IPTV Data flow1
VLAN 10
Data flow2
It is required that the UPE be able to identify VLAN IDs carried in frames and parse priorities
of the frames. The UPE sends frames to different PWs based on the VLAN IDs and priorities
of the frames. In this manner, frames with high priorities can be scheduled in time.
Before configuring VLAN policy-based VPN access, complete the following task:
l Ensuring that the UPE receives only untagged or single-tagged frames
Data Preparation
To configure VLAN policy-based VPN access, you need the following data.
No. Data
1 802.1p priority, DCSP priority, or EthType value

No. Data
2 Number of the interface connecting the UPE to users and IP address of this
interface
l Data for configuring an L2VPN, including:
– VSI ID (Two ends of a PW must be configured with the same VSI ID.)
– MPLS LSR ID
– VSI name
– Interface to which the VSI is bound
l Data for configuring an L3VPN, including:
– VPN instance name and RD
– VPN target
– AS number of the UPE
– IP address and interface by which the UPE establishes a BGP peer
relationship
– Mode for the UPE and switch to exchange routing information: static
routes, Routing Information Protocol (RIP), Open Shortest Path First
(OSPF), Intermediate System to Intermediate System (IS-IS), or Border
Gateway Protocol (BGP)
– (Optional) Description of the VPN instance
– (Optional) Routing policy for sending and receiving VPN routing
information
– (Optional) Tunnel policy
– (Optional) Maximum number of routes allowed by the VPN instance
4.7.2 Configuring a VLAN Policy

VLAN policies refer to VLAN+802.1p, VLAN+DSCP, and VLAN+EthType policies. With
VLAN policies, a device can send services to corresponding VLLs, VSIs, or VPN instances. In
this manner, Different types of services are transmitted in separate VLLs, VSIs, or VPN
instances.
Context
If non-IP services are transmitted between the Base Transceiver Station (BTS) and the CSG,
either of the following policies can be configured:
l VLAN+802.1p
On the network shown in Figure 4-13, Asynchronous Transfer Mode (ATM) or Time
Division Multiplex (TDM) links interconnect the BTS and CSG, and the Mobile
Aggregation Site Gateway (MASG) and Base Station Controller (BSC). To transmit ATM
services from the BTS to the remote BSC, you need to configure PWE3 between the CSG
and the MASG to transparently transmit ATM cells.
Figure 4-13 uses the VLAN+802.1p-based L2VPN access as an example. The process for
VLAN+802.1p-based L3VPN access is similar and not described in this document.

Figure 4-13 Networking diagram for VLAN+802.1p-based L2VPN access
Signal PWE3
xDSL IP/Eth IP/Eth

Voice
Manage
PE1 VSI PE2 BSC
CSG IP DSLAM MASG
Data BTS VSI
VSI
VSI
PE3 PE4
Per Service Per VSI

Ethernet over
ATM/TDM Ethernet VSI Ethernet ATM/TDM
l VLAN+DSCP
On the network shown in Figure 4-14, ATM or TDM links interconnect the BTS and CSG,
and the MASG and BSC. To allow ATM cells to be transmitted over an IPv4 network, you
need to configure Generic Routing Encapsulation (GRE) for ATM cells. To transmit ATM
services from the BTS to the remote BSC, you need to configure PWE3 between the CSG
and the MASG to transparently transmit ATM cells.
Figure 4-14 uses VLAN+DSCP-based L2VPN access as an example. The process for
VLAN+DSCP-based L3VPN access, untagged+DSCP-based L3VPN access, or VLAN
+DSCP-based L2VPN access is similar and not described in this document.
Figure 4-14 Networking diagram for VLAN+DSCP-based L2VPN access

GRE GRE
encapsulation PW decapsulation
Signal
CSG VLAN+DSCP
Voice
L2VPN
Manage PE1 PE2 MASG BSC
Data BTS
GRE
ATM/TDM PW over GRE ATM/TDM

NOTE
l The DSCP value is carried in IP packets. To make the VLAN+DSCP policy take effect, ensure that
only IP services are sent to the CSG.
If non-IP services are sent to the CSG, a GRE tunnel must be configured on the CSG to transparently
transmit the non-IP services over the IPv4 network.
l There is no difference in PE configurations regardless of whether IP or non-IP services are sent to the
BTS.
In this usage scenario, only PE configurations are concerned. For configurations of other devices, see
related configuration manuals.
l 802.1p or DSCP priorities can be changed on the CSG by using commands.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface { ethernet | gigabitethernet } interface-number.subinterface-number
The view of an Ethernet sub-interface connecting PE 1 to users is displayed.
Step 3 Run:
vlan-type dot1q vlanid { 8021p { 8021p-value1 [ to 8021p-value2 ] } &<1-10> | dscp
{ dscp-value1 [ to dscp-value2 ] } &<1-10> | eth-type eth-type-value | default }
A VLAN policy is configured on the sub-interface for dot1q VLAN tag termination.
NOTE
If the sub-interfaces of one interface are configured with the same VLAN ID, only one type of VLAN
policies (VLAN+802.1p, VLAN+DSCP, or VLAN+EthType) can be configured on these sub-interfaces.
A VLAN ID can be assigned to a maximum of eight sub-interfaces.
l The eth-type parameter takes effect only on PPPoE services currently. If the eth-type
parameter is configured, IPoE packets will be processed by the default sub-interface.
l If the default parameter is configured, all the services that do not match any VLAN policy
will be processed by the default sub-interface.
l If the vlan-type dot1q command has been used in the view of an Ethernet sub-interface, the
sub-interface exclusively uses this VLAN, and the VLAN ID can no longer be configured
in any VLAN policy for other sub-interfaces.
l If the undo vlan-type dot1q command is used with a specified VLAN ID and an 802.1p
priority value, a DSCP priority value, or an EtherType value, only the specified VLAN policy
associated with this VLAN ID is deleted from the sub-interface. If the undo vlan-type dot1q
vlanid command is used with a specified VLAN ID but not an 802.1p priority value, a DSCP
priority value, or an EtherType value, all VLAN policies associated with this VLAN ID are
deleted from the sub-interface.
----End
4.7.3 Configuring a VPN

After a VLAN matching policy is configured, you need to configure a VPN so that users over
an L2VPN and an L3VPN can communicate with each other.

Procedure
Step 1 Run:
system-view
Step 2 Run:
interface { ethernet | gigabitethernet } interface-number.subinterface-number
The view of an Ethernet sub-interface to be configured with a VLAN policy is displayed.
Step 3 Configure the VPN service.
Deploy one of the following services as required:
l L2VPN
For detailed information, see the chapters "VLL Configuration", "PWE3 Configuration", and
"VPLS Configuration" in the HUAWEI NetEngine80E/40E Router Configuration Guide -
VPN.
The sub-interface for QinQ VLAN tag termination can be bound to a homogeneous VLL in
the following modes:
– Local CCC connection
– Remote CCC connection
– Remote SVC connection
– Local Kompella connection
– Remote Kompella connection
– Remote Martini connection
The sub-interface for dot1q VLAN tag termination can be bound to a homogeneous VLL or
a heterogeneous VLL in the following modes:
– Remote Kompella remote connection
– Local Martini connection
The sub-interface for QinQ/dot1q VLAN tag termination can be bound to VPLS in the
following modes:
– Martini VPLS
– Kompella VPLS
l L3VPN
For detailed information, see the chapter "BGP MPLS IP VPN Configuration" in the
HUAWEI NetEngine80E/40E Router Configuration Guide - VPN.
----End

After VLAN policy-based VPN access is configured, you can check information about sub-
interfaces with the same VLAN ID on an interface.

Prerequisite
The configurations of VLAN policy-based VPN access are complete.
Procedure
l Run the display interface interface-type interface-number vlan { vlan-id | untagged }
command to check VLAN policies configured for sub-interfaces with a specified VLAN
ID or without VLAN IDs.
----End
Example
Run the display interface vlan command. The command output shows VLAN policies
configured for sub-interfaces on an interface with a specified VLAN ID. For example:
<HUAWEI> display interface gigabitethernet1/0/1 vlan 1
Sub-Interface VlanPolicy
-----------------------------------------------------------
GE1/0/1.1 8021p 1 3 to 7
GE1/0/1.2 dscp 3 6 to 10
GE1/0/1.3 default
-----------------------------------------------------------
Interface:GE1/0/1 VLAN ID: 1 Sub-Interface num: 3
4.8 Configuring Interface Isolation in a VLAN

After interface isolation in a VLAN is configured, interfaces in the VLAN cannot communicate
with each other. To have isolated interfaces communicate with each other, you need to configure
ARP proxy in the VLAN. In this manner, you can monitor traffic in the VLAN at Layer 3.

Before configuring interface isolation in a VLAN, familiarize yourself with the applicable
environment, pre-configuration tasks, and required data. This can help you complete the
configuration task quickly and accurately.
When some interfaces are limited not to connect directly, you can configure the interface
isolation in a VLAN.
When the interfaces isolated in a VLAN need to connect, the connection must be implemented
through the layer 3 route. In this way, the users in a VLAN can be managed and controlled
flexibly.
Before configuring the interface isolation in VLAN, complete the configuration of VLAN based
on the interface.
Data Preparation
To configure the interface isolation in VLAN, you need the following data.

No. Data
1 VLAN number
2 Numbers of interfaces that need to be isolated in a VLAN
3 IP addresses and sub net masks of the VLANIF interfaces
4.8.2 Configuring Interface Isolation in a VLAN

Isolated interfaces in a VLAN cannot communicate with each other, but can communicate with
non-isolated interfaces.
Context
The device provides the following two methods of isolating the interfaces in a VLAN:
l Enabling the interface isolation state in a VLAN.
l Configuring the interfaces that need to be isolated in the VLAN view.
You can choose one of the following methods as required:
Procedure
l Enabling the Interface Isolation
1. Run:
system-view

2. Run:
interface { gigabitethernet | eth-trunk } interface-number
The specified Ethernet interface view is displayed.

3. Run:
portswitch
The interface is set to the switched interface.

4. Run:
port default vlan vlan-id
The default VLAN to which the port belongs is configured.

5. Run:
port isolate-state enable vlan { vlan-id1 [ to vlan-id2 ] } &<1-10>
The interface isolation is enabled in a VLAN.

When this command is run, the VLAN should include this interface.
l Configuring the Interface Isolation in the VLAN View
1. Run:
system-view

2. Run:
vlan vlan-id

3. Run:
port isolate { { interface-type interface-number} &<1-10>| all }
The interfaces that need to be isolated are configured in a VLAN.
----End
4.8.3 Enabling ARP Proxy in a VLAN

To have isolated interfaces in a VLAN communicate with each other, you must create a VLANIF
interface and enable ARP proxy in the VLAN.
Context
Do as follows on the devices:
Procedure
Step 1 Run:
system-view
Step 2 Run:
The VLANIF interface is created.
Step 3 Run:
The IP addresses are configured for the VLANIF interfaces.
The IP addresses of the VLANIF interfaces and those of the hosts in the VLAN are on the same
network segment.
The IP addresses of different VLANIF interfaces should be on the different network segments,
so that there are reachable routes between the users in different VLANs.
Step 4 Run:
arp-proxy inner-sub-vlan-proxy enable
The ARP proxy is enabled in a VLAN.
----End
4.9 Configuring the Isolation Based on Interface Groups in

a VLAN
You can isolate interfaces in a VLAN by adding interfaces to different interface groups.


Before configuring interface group isolation in a VLAN, familiarize yourself with the applicable
NOTE
The interface group isolation in a VLAN is not supported in X1 and X2 of the NE80E/40E.
When you need to isolate packets between interface groups, you can configure the isolation
based on interface groups in a VLAN.
You can add the interfaces to be isolated to different interface groups and the interfaces in the
interface groups cannot communicate with each other.
Before configuring the isolation based on interface groups in a VLAN, complete the
configuration of the interface-based VLAN.
Data Preparation
To configure the isolation based on interface groups in a VLAN, you need the following data.
No. Data
1 VLAN number
2 Numbers of interfaces and interface groups to be isolated in a VLAN
4.9.2 Adding an Interface to the Group to Be Isolated

Interfaces in the same isolation group are not isolated from each other. Interfaces in an isolation
group can communicate with interfaces that do not belong to any isolation group.
Context
Do as follows on the devices:
Procedure
Step 1 Run:
system-view
Step 2 Run:

Step 3 Run:
portswitch
The interface is set as a switched interface.
Step 4 Run:
port-isolation group group-id
The interface is added to a specific group.
The interface must be added to the VLAN before you run this command.
----End

After interfaces are added to an isolation group, you can check information about the interface
isolation group.
Procedure
Step 1 Run the display port-isolation group { group-id | brief } command to view information about
an isolated interface group.
----End
Example
Run the display port-isolation group group-id command. You can view the information about
an isolated interface group. For example:
[HUAWEI] display port-isolation group 4
Port islation group 4
Eth-Trunk3
Eth-Trunk5
port islation group 4 has 2 ports
Run the display port-isolation group brief command. You can view the information about all
isolated interface groups. For example:
[HUAWEI] display port-isolation group brief
Eth-Trunk3
Eth-Trunk5
Eth-Trunk4
Eth-Trunk6
4.10 Configuring Ethernet Loop Detection for a VLAN

In the case of an uncontrollable user network, the NE80E/40E supports the deployment of
Ethernet loop detection on the provider's network to prevent loops in a VLAN.

4.10.1 Establishing the Configuation Task

Before configuring Ethernet loop detection for a VLAN, familiarize yourself with the applicable
As shown in Figure 4-15, when CE1, the Customer Edge (CE) device, accesses to the Provider
Edge (PE) devices in the same VLAN through redundant links, you can configure Ethernet loop
detection for the VLAN on PE devices. This avoids the broadcast storm on the network.
Figure 4-15 Networking diagram of configuring Ethernet loop detection for a VLAN
PE1 PE2
VLAN 100
AC1 AC2
CE1
Before configuring Ethernet loop detection for a VLAN, complete the following tasks:
l Connecting the interfaces and configuring the physical parameters of the interfaces to make
the physical status of the interfaces Up
l Creating a VLAN in the carrier network and connecting a CE device to PE devices
Data Preparation
To configure Ethernet loop detection for a VLAN, you need the following data.
No. Data
1 Times of loopback, interval of the detection time, cycle of the detection interval, time
for blocking a loop, and retry times for blocking an interface permanently
2 (Optional) Block priority of an interface
4.10.2 Configuring Ethernet Loop Detection for a VLAN

After Ethernet loop detection is configured for a VLAN, the NE80E/40E blocks a certain
interface, records a log, and sends an alarm after detecting a loop in the VLAN.

Context
Do as follows on the PE devices:
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
Step 3 Run:
loop-detect eth-loop loop-times loop-times detect-cycle detect-cycle-time cycles
cycles { retry-times retry-times block-time block-time | alarm-only }
Ethernet loop detection is enabled for the VLAN.
When block-time and retry-times are selected, the router blocks a certain interface in the VLAN
after a loop is detected in the VLAN. In addition, the router records the event in the log and
sends an alarm message to the NMS.
When alarm-only is selected, the router does not block the interface in the VLAN after detecting
a loop. Instead, the router only records the event in the log and sends an alarm message to the
NMS.
Step 4 Run:
quit
Step 5 (Optional) Run:

reset loop-detect eth-loop vlan vlan-id { all | interface interface-type interface-
number }
The interface which blocked by the Ethernet loop detetion for a VLAN is restored.
As shown in Figure 4-15, if Ethernet loop detection is configured for both PE1 and PE2 in
VLAN 100, you can set different values for cycles to first block the link on either device first.
For example, if cycles is set to 1 on PE1 and 3 on PE2, PE1 blocks the port the first time a loop
is detected. PE2, however, blocks the port when a loop is detected for three times. Therefore,
PE1 blocks a loop faster than PE2.
----End
4.10.3 (Optional) Configuring the Block Priority for an Interface

You can configure block priorities for interfaces so that a specific link is preferentially blocked
when a loop is detected.
Context
Do as follows on the PE devices:

Procedure
Step 1 Run:
system-view

Step 2 Run:
interface { ethernet | gigabitethernet | eth-trunk } interface-number
The view of the specified Ethernet interface is displayed.

The specified interface must be an interface in a VLAN enabled with Ethernet loop detection.
Step 3 Run:
loop-detect eth-loop priority priority
The block priority is configured for the interface.

The smaller priority is, the faster an interface is blocked.
As shown in Figure 4-15, if you want to block the link between PE1 and PE2 first, you can
configure different priority values for interfaces on the PE devices, when a loop is formed
between CE1, PE1, and PE2. In this manner, you can first block the link between PE1 and PE2.
----End

After Ethernet loop detection for a VLAN is configured, you can check information about
Ethernet loop detection.
Context
Run the following command to check the previous configuration.
Action Command
Check information about Ethernet loop display loop-detect eth-loop vlan vlan-id
detection in a VLAN.
Run the display loop-detect eth-loop vlan vlan-id command. You can view the information
about Ethernet loop detection in a VLAN. For example:
<HUAWEI> display loop-detect eth-loop vlan 100
VLAN/VSI LTimes D-Cycle Cycles Retry Action BPolicy
------------------------------------------------------------------------
VLAN 100 1 2 3 -- Alarm-only --
Total Items = 1
Blocked Port:
---------------
4.11 Maintaining VLAN

A command of clearing statistics helps to locate the faults in a VLAN.

4.11.1 Clearing the Statistics of VLAN Packets

Before collecting traffic statistics in a specified time period on an interface, you need to reset
the original statistics on the interface.
Context
CAUTION
Statistics about VLAN packets cannot be restored after you clear it. So, confirm the action before
you use the command.
To clear the Statistics of VLAN Packets, run the following reset command in the user view:
Procedure
l Run the reset vlan statistics [ vid ] vlan-id command to clear packets of a specified VLAN
statistics.
l Run the reset vlan statistics interface interface-type interface-number.subinterface-
number command to clear the VLAN packets on a specified sub-interface statistics.
----End

This section describes the typical application scenarios of VLANs, including networking
files.
NOTE
4.12.1 Example for Configuring Users in a VLAN to Communicate

by Using a Trunk Link
If employees of a department work in different buildings, switches in the buildings can be
connected by using a trunk link to allow the employees to communicate.
A company has several departments. Employees of each department reside in different buildings.
On the network shown in Figure 4-16, employees of the financial or marketing department work
in different buildings. It is required that employees of the same department be able to
communicate with each other, whereas employees of different departments not communicate
with each other.

Figure 4-16 Networking diagram for configuring users in a VLAN to communicate by using a
trunk link
network
CE1 PE CE2
GE1/0/5 GE1/0/5
GE1/0/1 GE1/0/2
Trunk ( VLAN 5 VLAN 9 ) GE1/0/4
GE1/0/1
GE1/0/4 GE1/0/1
GE1/0/2 GE1/0/3 GE1/0/2 GE1/0/3

Finance Marketing Finance Marketing
Department Department Department Department
1. Add ports connecting switches to PCs of the financial department to VLAN 5 and ports
connecting switches to PCs of the marketing department to VLAN 9. This configuration
prevents employees in financial and marketing departments from communicating with each
other.
2. Configure links between switches and PE as trunk links to allow frames from VLAN 5 and
VLAN 9 to pass through, allowing employees of the same department but different
buildings to communicate with each other.
NOTE
Only Layer 2 ports are able to identify frames with tags. All interfaces on PE and CEs 1 and 2 must
function as Layer 2 ports.
Data Preparation
l Number of each port connecting a switch to a PC

l Number of each port connecting a switch to the router
l Number of each port connecting the router to a switch

l ID of each VLAN
Procedure
Step 1 Add ports connecting switches to PCs to specified VLANs.
# Configure CE 1.
[CE1] vlan batch 5 9
[CE1] interface GigabitEthernet 1/0/1
# Configure CE 2.
Step 2 Configure links between switches and the router as trunk links.
# Configure CE 1.


[CE1-GigabitEthernet1/0/5] port trunk allow-pass vlan 5 9
# Configure CE 2.
Step 3 # Configure PE.

[HUAWEI] sysname PE
[PE] interface GigabitEthernet 1/0/1
[PE-GigabitEthernet1/0/1] port trunk allow-pass vlan 5 9
[PE] interface GigabitEthernet 1/0/2
After the configurations are complete, run the display vlan command to view VLAN status. In
the following example, the display on CE1 is used:
[CE1] display vlan 5
* : management-vlan
---------------------
--------------------------------------------------------------------------------
-------------------
Tagged Port: GigabitEthernet1/0/1 GigabitEthernet1/0/2
-------------------
Active tag Port: GigabitEthernet1/0/1 GigabitEthernet1/0/2
-------------------
Interface Physical
GigabitEthernet1/0/1 UP
[CE1] display vlan 9
* : management-vlan
---------------------
--------------------------------------------------------------------------------
-------------------
Tagged Port: GigabitEthernet1/0/3 GigabitEthernet1/0/4
-------------------
Active tag Port: GigabitEthernet1/0/3 GigabitEthernet1/0/4
-------------------
Interface Physical

Run the display port vlan command to view the list of VLANs configured on port. In the
following example, the display on CE1 is used:
[CE1] display port vlan gigabitethernet1/0/5
Port Link Type PVID Trunk VLAN List
--------------------------------------------------------------
GigabitEthernet1/0/5 trunk 0 5 9
In either VLAN 5 or VLAN 9, a PC connected to CE 1 can ping a PC connected to CE 2

successfully.
----End
Configuration Files
l Configuration file of CE 1
#
sysname CE1
#
vlan batch 5 9
#
portswitch
undo shutdown
port default vlan 5
#
portswitch
undo shutdown
port default vlan 5
#
portswitch
undo shutdown
port default vlan 9
#
portswitch
undo shutdown
port default vlan 9
#
portswitch
undo shutdown
port trunk allow-pass vlan 5 9
#
return
#
sysname CE2
#
vlan batch 5 9
#
portswitch
undo shutdown
port default vlan 5
#
portswitch

undo shutdown
port default vlan 5
#
portswitch
undo shutdown
port default vlan 9
#
portswitch
undo shutdown
port default vlan 9
#
portswitch
undo shutdown
#
return
#
sysname PE
#
vlan batch 5 9
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#
return

Using Sub-interfaces
Configuring sub-interfaces enables users in different VLANs and network segments to
communicate with each other.
Users in different residential compounds in different network segments require various services
such as Internet, IPTV, and VoIP services. The network administrator of each residential
compound configures a VLAN for each service to simplify management. After the configuration,
users in different residential compounds belong to different VLANs, but they need to
communicate with each other for the same type of service.
On the network shown in Figure 4-17, users in residential compounds 1 to 4 belong to different
VLANs in different network segments but all require the Internet service. Therefore,
communication between these users is required.

Figure 4-17 Networking diagram for configuring inter-VLAN communication by using sub-
interfaces
PE
GE2/0/0.1: 10.110.4.3/24 GE1/0/1.1: 10.110.6.3/24
GE2/0/0.2: 10.110.3.3/24 GE1/0/1.2: 10.110.5.3/24
GE1/0/3 GE1/0/3
CE1 CE2
GE1/0/1 GE1/0/2 GE1/0/1 GE1/0/2
community1 community2 community3 community4

10.110.4.0/24 10.110.3.0/24 10.110.6.0/24 10.110.5.0/24
1. Create VLANs on switches and determine mappings between users and VLANs.
2. Configure trunk ports on switches to allow frames with certain VLAN IDs to pass through.
3. Create sub-interfaces on PE and associate the sub-interfaces with VLANs.
4. Assign an IP address to each sub-interface for communication at the network layer.
NOTE
The default gateway address of each PC in a VLAN must be the IP address of the corresponding sub-
interface. Otherwise, inter-VLAN communication fails.
Data Preparation
l User VLAN ID
l User IP address
l Number and IP address of each sub-interface on PE
Procedure
Step 1 Create VLANs on CE 1 and CE 2.
# Configure CE 1.

# Configure CE 2.
Step 2 Configure trunk ports on CE 1 and CE 2 to allow frames with certain VLAN IDs to pass through.
# Configure CE 1.
# Configure CE 2.
Step 3 Create sub-interfaces on PE and associate the sub-interfaces with VLANs.

[HUAWEI] sysname PE
[PE] interface gigabitethernet 1/0/1.1
[PE-GigabitEthernet1/0/1.1] vlan-type dot1q 10
[PE-GigabitEthernet1/0/1.1] quit


Step 4 Configure IP addresses.

[PE-GigabitEthernet1/0/1.1] ip address 10.110.6.3 24
On PCs in VLAN 10, configure the IP address 10.110.6.3/24 of GE 1/0/1.1 as the default gateway
address.
address.
address.
address.
After the configurations, PCs in VLANs 10, 20, 30, and 40 can ping each other successfully.
----End
Configuration Files
#
sysname CE1
#
vlan batch 30 40
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#

return
#
sysname CE2
#
vlan batch 10 20
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#
return
#
sysname PE
#
undo shutdown
#
vlan-type dot1q 10
ip address 10.110.6.3 255.255.255.0
#
vlan-type dot1q 20
ip address 10.110.5.3 255.255.255.0
#
undo shutdown
#
vlan-type dot1q 30
ip address 10.110.4.3 255.255.255.0
#
vlan-type dot1q 40
ip address 10.110.3.3 255.255.255.0
#
return
4.12.3 Example for Configuring VLAN and Non-VLAN Users to

Communicate by Using Sub-interfaces
This example describes how to configure communication between VLAN users and non-VLAN
users.
Residents in a residential compound belong to different network segments. To simplify
management, the network administrator of the residential compound adds users to different

VLANs. Residents in another residential compound are not added to any VLAN. VLAN users
must be able to communicate with non-VLAN users.
On the network shown in Figure 4-18, users in residential compound 1 belong to different
VLANs and reside on different network segments; users in residential compound 2 do not belong
to any VLAN. It is required that users in VLAN 10 be able to communicate with users in
residential compound 2.
Figure 4-18 Networking diagram for configuring VLAN and non-VLAN users to communicate
by using sub-interfaces
PE
GE1/0/1.1 GE2/0/0
10.110.2.5/24 10.110.3.5/24
GE1/0/3 GE1/0/2
GE1/0/1 GE1/0/2 CE2
CE1 GE1/0/1
community1
community2
User1 User2
VLAN10 VLAN20
10.110.2.0/24 10.110.4.0/24 10.110.3.0/24
2. Configure the trunk port on CE 1 to allow frames with certain VLAN IDs to pass through.
3. Create a sub-interface on the interface connecting the router to VLAN users and associate
the sub-interface with VLAN 10.
4. Assign IP addresses to interfaces for communication at the network layer.
l Assign an IP address to the sub-interface.
l Assign an IP address to the interface connecting the router to non-VLAN users.
NOTE
l The IP address assigned to the sub-interface connected to VLAN users must be on the same network
segment with IP addresses of VLAN users.
l The IP address assigned to the interface connected to non-VLAN users must be on the same network
segment with IP addresses of non-VLAN users.
l The default gateway addresses of PCs in VLAN 10 must be the IP address of the sub-interface.
Otherwise, VLAN and non-VLAN users cannot communicate with each other.

Data Preparation
l User VLAN ID
l User IP address
l Number and IP address of each sub-interface on PE
Procedure
Step 1 Create a VLAN on CE 1.
[CE1] vlan batch 10
[CE1-vlan10] quit
Step 2 Configure the trunk port on CE 1 to allow frames with certain VLAN IDs to pass through.
Step 3 Create a sub-interface on PE and associate the sub-interface with VLAN 10.
[HUAWEI] sysname PE
Step 4 Configure IP addresses.

[PE-GigabitEthernet2/0/0] ip address 10.110.3.5 24
address.
On CE 2, configure the IP address 10.110.3.5 of GE 2/0/0 as the default gateway address.
After the configurations, users in VLAN 10 and non-VLAN users can ping each other
successfully.
----End

Configuration Files
#
sysname CE1
#
vlan batch 10
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#
return
#
sysname PE
#
undo shutdown
#
vlan-type dot1q 10
ip address 10.110.2.5 255.255.255.0
#
undo shutdown
ip address 10.110.3.5 255.255.255.0
#
return

Using VLANIF Interfaces
In this example, Layer 3 forwarding is performed by a Layer 3 PE instead of a router. This allows
PCs in different VLANs to communicate with each other and reduces operating costs.
Users in different residential compounds in different network segments require various services
such as Internet, IPTV, and VoIP services. The network administrator of each residential
compound configures a VLAN for each service to simplify management. After the configuration,
users in different residential compounds belong to different VLANs, but they need to
communicate with each other for the same type of service.
On the network shown in Figure 4-19, users in residential compounds 1 to 4 belong to different
VLANs in different network segments but require the same online service. It is required that
these users communicate with each other at a low operating cost.

Figure 4-19 Networking diagram for configuring inter-VLAN communication by using

VLANIF interfaces
VLANIF30: 10.110.4.3/24 PE VLANIF10: 10.110.6.3/24
VALNIF40: 10.110.3.3/24 VALNIF20: 10.110.5.3/24
GE1/0/1 GE1/0/2
GE1/0/3 GE1/0/3
CE1 CE2
GE1/0/1 GE1/0/2 GE1/0/1 GE1/0/2
community1 community2 community3 community4

10.110.4.0/24 10.110.3.0/24 10.110.6.0/24 10.110.5.0/24
2. Configure trunk ports on switches to allow frames with certain VLAN IDs to pass through.
3. Create VLANIF interfaces on the PE and assign IP addresses to the interfaces to allow
Layer 3 communication.
NOTE
The default gateway address of each PC in a VLAN must be the IP address of the corresponding VLANIF
interface. Otherwise, inter-VLAN communication will fail.
Data Preparation
l User VLAN ID
l User IP address
l Number of the ports interconnecting switches
l Number and IP address of each VLANIF interface on the PE
Procedure
Step 1 Create VLANs on CE 1 and CE 2.
# Configure CE 1.

# Configure CE 2.
Step 2 Configure trunk ports on CE 1 and CE 2 to allow frames with certain VLAN IDs to pass through.
# Configure CE 1.
# Configure CE 2.
Step 3 Create VLANIF interfaces on PE and assign IP addresses to the VLANIF interfaces.
[HUAWEI] sysname PE
[PE] vlan batch 10 to 40

[PE] interface Vlanif 10
[PE-Vlanif10]ip address 10.110.6.3 24
[PE-Vlanif10]quit
[PE-Vlanif20]quit
[PE-Vlanif30]quit
[PE-Vlanif40]quit

On PCs in VLAN 10, configure the IP address 10.110.6.3/24 of VLANIF 10 as the default
gateway address.
gateway address.
gateway address.
gateway address.
After the configurations, PCs in VLANs 10, 20, 30, and 40 can ping each other successfully.
----End
Configuration Files
#
sysname CE1
#
vlan batch 30 40
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#
return
#
sysname CE2
#
vlan batch 10 20
#

portswitch
undo shutdown
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#
return
#
sysname PE
#
vlan batch 10 to 40
#
interface Vlanif10
ip address 10.110.6.3 255.255.255.0
#
interface Vlanif20
ip address 10.110.5.3 255.255.255.0
#
interface Vlanif30
ip address 10.110.4.3 255.255.255.0
#
interface Vlanif40
ip address 10.110.3.3 255.255.255.0
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#
return
4.12.5 Example for Configuring 1 to 1 VLAN Mapping for Inter-

VLAN Communication
1 to 1 VLAN mapping allows user VLAN IDs and the ISP VLAN ID to be replaced with each
other to help users in different VLANs to communicate with each other.
Users in different residential compounds use IPTV, VoIP, and Internet services. To simplify
management, the network administrator of each residential compound configures a separate
VLAN for each type of services. After the configuration, users using the same type of services
in different residential compounds belong to different VLANs, but they need to communicate
with each other.

On the network shown in Figure 4-20, the same type of services in residential compounds 1 and
2 belong to different VLANs. It is required that these users communicate with each other at a
low operating cost.
Figure 4-20 Networking diagram for configuring 1 to 1 VLAN mapping
PE1 PE2
GE1/0/1 ISP GE1/0/1
VLAN10
CE1 GE1/0/3 GE1/0/3 CE2
GE1/0/1 GE1/0/2 GE1/0/1 GE1/0/2
Community1 Community2
VLAN6 VLAN5
172.16.0.2/16 172.16.0.6/16
172.16.0.1/16 172.16.0.3/16 172.16.0.5/16 172.16.0.7/16
1. Add ports connecting switch 1 to residential compound 1 to VLAN 6. Add ports connecting
switch 2 to residential compound 2 to VLAN 5.
2. Configure 1 to 1 VLAN mapping on switches 3 and 4 at the edge of the ISP network to
map user VLAN IDs to the ISP VLAN ID to allow users in different VLANs to
Data Preparation
l Number of each port connecting a switch to a user device
l Number of the ports interconnecting switches
l VLAN IDs configured on switches
l VLAN ID provided by the ISP
Procedure
Step 1 Add ports connecting switches to user devices to specified VLANs.
# Configure CE 1.
[CE1] vlan 6

[CE1-vlan6] quit
# Configure CE 2.
[CE2] vlan 5
[CE2-vlan5] quit
Step 2 Configure 1 to 1 VLAN mapping.
# Configure PE 1.
[PE1] vlan 10
[PE1-vlan10] quit
[PE1] interface GigabitEthernet 1/0/1
[PE1-GigabitEthernet1/0/1] port vlan-mapping vlan 6 map-vlan 10
# Configure PE 2.
[PE2] vlan 10
[PE2-vlan10] quit
[PE2] interface GigabitEthernet 1/0/1
[PE2-GigabitEthernet1/0/1] port vlan-mapping vlan 5 map-vlan 10


After completing the configurations, run the display vlan command to check information about
1 to 1 VLAN mapping. Use the display on PE 1 as an example.
[PE1] display vlan 10
* : management-vlan
---------------------
--------------------------------------------------------------------------------
----------------
QinQ-map Port: GigabitEthernet1/0/1
----------------
Interface Physical
Users in residential compounds 1 and 2 can communicate with each other.
----End
Configuration Files
#
sysname CE1
#
vlan batch 6
#
undo shutdown
portswitch
port default vlan 6
#
undo shutdown
portswitch
port default vlan 6
#
undo shutdown
portswitch
#
return
#
sysname CE2
#
vlan batch 5
#
undo shutdown
portswitch
port default vlan 5
#
undo shutdown
portswitch
port default vlan 5

#
undo shutdown
portswitch
#
return
l Configuration file of PE 1
#
sysname PE1
#
vlan batch 10
#
undo shutdown
portswitch
port vlan-mapping vlan 6 map-vlan 10
#
return
l Configuration file of PE 2
#
sysname PE2
#
vlan batch 10
#
undo shutdown
portswitch
port vlan-mapping vlan 5 map-vlan 10
#
return
4.12.6 Example for Configuring Communication Between VLANs

Through VLAN Aggregation
This part describes how to configure communication between VLANs with fewer IP addresses.
Assume that an enterprise has many departments and IP addresses of these departments are on
the same network segment, to improve the service security, IP addresses of PCs used by
employees in the same department are added to the same VLAN and IP addresses of PCs used
by employees in different departments are added to different VLANs. IP addresses of PCs used
by employees in different departments need to communicate with each other.
As shown in Figure 4-21, IP addresses of the R&D department and test department belong to
different VLANs. It is required that IP addresses of PCs used by employees in different VLANs

Figure 4-21 Networking diagram of configuring communication between VLANs through

VLAN aggregation
PE
GE1/0/1 GE1/0/2
VLAN4
VLANIF4:
100.1.1.12/24
GE1/0/3 GE1/0/3
GE1/0/1 GE1/0/2 GE1/0/1 GE1/0/2
CE1 CE2
VLAN2 VLAN3
Development Test
Department Department
100.1.1.1/24 100.1.1.2/24
IP addresses of the R&D department and test department are on the same network segment. To
save IP address resources, you can deploy VLAN aggregation on devices of the R&D department
and test department. This ensures that different VLANs can communicate with each other.
1. Create VLAN on CE1 and CE2 to determine mappings between users and VLANs.
2. Configure VLAN aggregation on PE.
(1) Configure the Layer 2 forwarding function.
(2) Create a super-VLAN, and add sub-VLANs to the super-VLAN for VLAN
aggregation.
(3) Create the VLANIF interface of the super-VLAN and assign an IP address to the
VLANIF interface as the network gateway address.
(4) Enable ARP proxy on the VLANIF interface of the super-VLAN and between sub-
VLANs so that sub-VLANs can communicate with each other on the Layer 3 network.
Data Preparation
l User VLAN ID

l User IP address
l Sub-VLAN ID and super-VLAN ID
l Number and IP address of the VLANIF interface of the super-VLAN
Procedure
Step 1 Create a VLAN on CE and add Layer 2 interfaces to the VLAN.
# Configure CE 1.
[CE1] vlan batch 2
# Configure CE 2.
[CE2] vlan batch 3
Step 2 Configure VLAN aggregation on PE.

1. Configure the Layer 2 forwarding function.
[HUAWEI] sysname PE
[PE] vlan batch 2 to 4


2. Create a super-VLAN and add sub-VLANs to the super-VLAN.

[PE] vlan 4
[PE-vlan4] aggregate-vlan
[PE-vlan4] access-vlan 2 to 3
[PE-vlan4] quit
3. Create a VLANIF interface for the super-VLAN and assign an IP address to the VLANIF
interface.
[PE] interface vlanif 4
[PE-Vlanif4] ip address 100.1.1.12 24
After the preceding configurations, you can configure IP addresses as shown in Figure
4-21 to PCs. IP address of PCs and the VLANIF interface are on the same network segment.
If the configuration succeeds, IP addresses of PCs used by employees in different VLANs
and the switch can ping each other; IP addresses of PCs used by employees in VLAN2 and
VLAN3 cannot ping each other.
4. Enable ARP proxy on the VLANIF interface of the super-VLAN and between sub-VLANs.
# Enable ARP proxy on the VLANIF interface of the super-VLAN.
[PE-Vlanif4] arp-proxy enable
# Enable ARP proxy between sub-VLANs.

[PE-Vlanif4] arp-proxy inter-sub-vlan-proxy enable
[PE-Vlanif4] quit

After the configuration, IP addresses of PCs used by employees in VLAN2 and VLAN3 can
ping each other.
----End
Configuration Files
l Configuration file of the CE1
#
sysname CE1
#
vlan batch 2
#
portswitch
undo shutdown
port default vlan 2
#
portswitch
undo shutdown
port default vlan 2
#
portswitch
undo shutdown


#
return
l Configuration file of the CE2

#
sysname CE2
#
vlan batch 3
#
portswitch
undo shutdown
port default vlan 3
#
portswitch
undo shutdown
port default vlan 3
#
portswitch
undo shutdown
#
return
l Configuration file of the PE

#
sysname PE
#
vlan batch 2 to 4
#
vlan 4
aggregate-vlan
access-vlan 2 to 3
#
interface Vlanif4
ip address 100.1.1.12 255.255.255.0
arp-proxy enable
#
portswitch
undo shutdown
#
portswitch
undo shutdown
#
return
4.12.7 Example for Configuring VLAN+802.1p for L2VPN Access

(on a Common Sub-interface)
In the networking of this configuration example, VLAN+802.1p is configured on the sub-
interface at the AC side of PE1; the sub-interface is bound to different VSIs. Packets are
transmitted through different VSIs based on the 802.1p priorities of the packets. The following
takes the scenario where a CSG accesses IP services as an example.

On an ME network, VLAN IDs are used to identify various services or user packets before they
access various VSIs, VLLs, or VPN instances. If multiple user packets or services share one
VLAN ID, part of high-priority traffic over the operators' network cannot be scheduled in time,
which deteriorates users' experience.
On the network shown in Figure 4-22, various services are tagged with the same VLAN ID on
a CSG. After receiving these services, PE1 cannot identify them, resulting in a failure in traffic
distribution. To help resolve this problem, a VLAN matching policy needs to be configured on
PE1. PE1 maps a VLAN ID to a packet priority before distributing a packet to a specific PW,
ensuring correct scheduling of packets.
NOTE
In this example, PE1 parses 802.1p values in the received packets for scheduling.
Figure 4-22 Networking diagram for VLAN+802.1p-based L2VPN access

Loopback1
2.2.2.9/32
PE2
GE1/0/1.1
GE1/0/2
=3
Database
10.1.1.1/30
p
2.1
80
CSG GE1/0/1.2
GE1/0/2
GE1/0/1.1 10.1.1.2/30
GE1/0/3
PE1 20.1.1.2/30
Loopback1
80
1.1.1.9/32 GE1/0/2
2.1
20.1.1.1/30 Internet
p
VLAN 10
=2
GE1/0/1.1
PE3
Loopback1
3.3.3.9/32
VLAN PW VLAN
NOTE
L2VPN includes VLL, PWE3, and VPLS. You can configure any one of them as required. The following
takes the VPLS application as an example.

1. Configure basic VPLS functions.

(1) Run an IGP to ensure intercommunication between router on the backbone network.
(2) Configure basic MPLS functions on the backbone network.
(3) Set up LSPs between PEs.
(4) Enable MPLS L2VPN on PEs.
(5) Create VSIs on PEs.
2. Configure VLAN+802.1p.
3. Bind AC interfaces to the VSIs.
4. Configure the Layer 2 forwarding function on CSG.
Data Preparation
l IP addresses of interfaces
l MPLS LSR IDs of PEs
l VSI names and VSI IDs on PEs
l Names of the interfaces bound to the VSIs
Procedure
Step 1 Configure basic VPLS functions.
# Set up a VPLS connection between PE1 and PE2, and between PE1 and PE3, with LDP being
the signaling protocol; configure the VSI names to be LDP1 and LDP2. The detailed
configurations are not mentioned here. You can refer to the chapter "VPLS Configuration" in
the NE80E/40E Configuration Guide - VPN or the configuration files in this configuration
example.
Step 2 Configure VLAN+802.1p.
# Configure PE1.
<PE1> system-view
[PE1-GigabitEthernet1/0/1.1] vlan-type dot1q 10 8021p 3
# Configure PE2.
<PE2> system-view
[PE2-GigabitEthernet1/0/1.1] vlan-type dot1q 10
# Configure PE31.
<PE3> system-view
Step 3 Bind each sub-interface to a VSI.

# Configure PE1.
# Configure PE2.
# Configure PE3.
Step 4 Configure basic functions of the CSG.

The detailed configurations are not mentioned here. It is required that the CSG support the
following:
l Configures the 802.1p priorities of packets through commands.
l Differentiates service types (voice, data, or signal) based on timeslots in TDM or PVCs in
ATM in the case that the CSG accesses non-IP services.
NOTE
Packets sent from CSG to PE1 carry VLAN tags with different 802.1p priorities.

After the preceding configurations, run the display vsi name ldp1 verbose command on PEs,
and you can view that a PW to PE2 is set up for a VSI named ldp1 and the VSI is in the Up
state.
Take the command output on PE1 as an example.
***VSI Name : ldp1

VSI Index : 1
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
VSI State : up
VSI ID : 1

VC Label : 30720
Peer Type : dynamic
Session : up
Tunnel ID : 0x81000b
Broadcast Tunnel ID : 0x81000b
CKey : 2
NKey : 1
StpEnable : 0
PwIndex : 0
Interface Name : GigabitEthernet1/0/1.1

State : up
Last Up Time : 2009/09/01 16:10:40
**PW Information:

PW State : up
PW Type : label
Ckey : 0x2
Nkey : 0x1
Main PW Token : 0x81000b
Tnl Type : LSP
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2009/09/01 16:10:40
Run the display interface vlan command, and you can view the matching policy with the
specified VLAN ID on a main interface.
[PE1] display interface gigabitethernet1/0/1 vlan 10
Interface VlanPolicy
-----------------------------------------------------------
GE1/0/1.1 8021p 3
GE1/0/1.2 8021p 2
-----------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 2.2.2.9
#
vsi ldp2 static
pwsignal ldp

vsi-id 2
peer 3.3.3.9
#
mpls ldp
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10 8021p 3
l2 binding vsi ldp1
#
undo shutdown
l2 binding vsi ldp2
#
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 20.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10
l2 binding vsi ldp1
#
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp

#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return

#
sysname PE3
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10
l2 binding vsi ldp2
#
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 20.1.1.0 0.0.0.3
#
return
4.12.8 Example for Configuring VLAN+DSCP for L2VPN Access

In the networking of this configuration example, VLAN+DSCP is configured on the sub-
interface at the AC side of PE1; the sub-interface is bound to different VPN instances. Packets
are transmitted through different VSIs based on the DSCP values of the packets. The following

As show in Figure 4-23, various services are tagged with the same VLAN ID on a CSG. After
receiving these services, PE1 cannot identify them, resulting in a failure in traffic distribution.
To help resolve this problem, a VLAN matching policy needs to be configured on PE1. PE1
maps a VLAN ID to a packet priority before distributing a packet to a specific PW, ensuring
correct scheduling of packets.
NOTE
In this example, PE1 parses DSCP values in the received packets for scheduling.
The DSCP is carried in each IP packet. For correct deployment of the VLAN+DSCP policy, you need to
ensure that the CSG accesses only IP services.
If the CSG accesses non-IP services, you have to configure GRE tunnels on the CSG so that encapsulated
packets can be transmitted over an IPv4 network.

Loopback1
2.2.2.9/32
PE2
GE1/0/1.1
=3 GE1/0/2
10.1.1.1/30 Database
CP
DS
CSG GE1/0/1.2 GE1/0/2

GE1/0/1.1 10.1.1.2/30
GE1/0/3
PE1 20.1.1.2/30
Loopback1
DS
1.1.1.9/32 GE1/0/2 Internet

CP
VLAN 10 20.1.1.1/30
=2
GE1/0/1.1
PE3
Loopback1
3.3.3.9/32
VLAN PW VLAN
NOTE



2. Configure VLAN+DSCP.
4. Configure the Layer 2 forwarding function on CSG.
Data Preparation
Procedure
example.
Step 2 Configure VLAN+DSCP.
# Configure PE1.
<PE1> system-view
[PE1-GigabitEthernet1/0/1.1] vlan-type dot1q 10 dscp 3
# Configure PE2.
<PE2> system-view
# Configure PE3.
<PE3> system-view

# Configure PE1.


# Configure PE2.
# Configure PE3.

following:
l Configures the DSCP values of packets through commands.
NOTE
Packets sent from the CSG to PE1 carry VLAN tags with different DSCP values.

state.
***VSI Name : ldp1

VSI Index : 1
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
VSI State : up
VSI ID : 1
VC Label : 30720
Peer Type : dynamic
Session : up

CKey : 2
NKey : 1
StpEnable : 0
PwIndex : 0

State : up
Last Up Time : 2009/09/01 16:10:40
**PW Information:

PW State : up
PW Type : label
Ckey : 0x2
Nkey : 0x1
Tnl Type : LSP
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2009/09/01 16:10:40
-----------------------------------------------------------
GE1/0/1.1 dscp 3
GE1/0/1.2 dscp 2
-----------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 2.3.4.9
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 3.3.3.9
#
mpls ldp
#

undo shutdown
#
undo shutdown
vlan-type dot1q 10 dscp 3
l2 binding vsi ldp1
#
undo shutdown
l2 binding vsi ldp2
#
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 20.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10
l2 binding vsi ldp1
#
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1

area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return

#
sysname PE3
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10
l2 binding vsi ldp2
#
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 20.1.1.0 0.0.0.3
#
return
4.12.9 Example for Configuring VLAN+EthType for L2VPN Access

In the networking of this configuration example, VLAN+EthType is configured on the sub-
interface at the AC side of PE1; the sub-interface is bound to different VSIs. In this manner,
packets of different EthTypes enter different VSIs, and different services can be transmitted
through different VSIs.
On the network shown in Figure 4-24, various services are tagged with the same VLAN ID on
a switch. After receiving these services, PE1 cannot identify them, resulting in a failure in
distributing traffic. To help resolve this problem, a policy for mapping a VLAN ID to a priority

needs to be configured on PE1. PE1 maps a VLAN ID to the packet priority before distributing
the packet to a specific PW, ensuring correct scheduling of packets.
Figure 4-24 Networking diagram of VLAN+EthType-based L2VPN access

Loopback1
2.2.2.9/32
PE2
GE1/0/1.1
GE1/0/2
Video/BTV
E
10.1.1.1/30
Po
VOD
PP
Platform
Switch GE1/0/1.2 GE1/0/2
GE1/0/1.1 10.1.1.2/30
GE1/0/3
PE1 20.1.1.2/30
Loopback1
1.1.1.9/32 Internet
IPo
GE1/0/2
20.1.1.1/30
E
VLAN 10
GE1/0/1.1
PE3
Loopback1
3.3.3.9/32
VLAN PW VLAN
NOTE

2. Configure VLAN+EthType.
4. Configure the Layer 2 forwarding function on Switch.

Data Preparation
Procedure
example.
Step 2 Configure VLAN+EthType.
# Configure PE1.
<PE1> system-view
[PE1-GigabitEthernet1/0/1.1] vlan-type dot1q 10 eth-type pppoe
[PE1-GigabitEthernet1/0/1.2] vlan-type dot1q 10 default
# Configure PE2.
<PE2> system-view
# Configure PE3.
<PE3> system-view

# Configure PE1.
# Configure PE2.

# Configure PE3.
Step 4 Configure basic functions of Switch.

The configuration details are not mentioned here. For detailed configuration of Switch, refer to
the related configuration guide.
state.
***VSI Name : ldp1

VSI Index : 1
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
VSI State : up
VSI ID : 1
VC Label : 30720
Peer Type : dynamic
Session : up
CKey : 2
NKey : 1
StpEnable : 0
PwIndex : 0

State : up
Last Up Time : 2009/09/01 16:10:40
**PW Information:

PW State : up
PW Type : label
Ckey : 0x2
Nkey : 0x1


Tnl Type : LSP
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2009/09/01 16:10:40
-----------------------------------------------------------
GE1/0/1.1 eth-type pppoe
GE1/0/1.2 default
-----------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 2.2.2.9
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 3.3.3.9
#
mpls ldp
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10 eth-type pppoe
l2 binding vsi ldp1
#
undo shutdown
vlan-type dot1q 10 default
l2 binding vsi ldp2
#
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 20.1.1.2 255.255.255.252

mpls
mpls ldp
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10 eth-type pppoe
l2 binding vsi ldp1
#
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return
#
sysname PE3
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
#
mpls ldp
#

undo shutdown
#
undo shutdown
vlan-type dot1q 10 default
l2 binding vsi ldp2
#
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 20.1.1.0 0.0.0.3
#
return

In the networking of this configuration example, VLAN+DSCP is configured on the sub-
interface at the AC side of PE1; the sub-interface is bound to different VPN instances. In this
manner, packets of different DSCP values enter different VPN instances, and different services
can be transmitted through different VPN instances. The following takes the scenario where a
CSG accesses IP services as an example.
As shown in Figure 4-25, different service packets are added with the same tag on the CSG.
Therefore, when PE1 receives packets, it cannot identify services based on tags, which affects
the traffic distribution. To address the problem, you can deploy a VLAN policy on PE1. PE1
distributes traffic to different VPN instances based on VLAN IDs and packet priorities. This
ensures that packets can be scheduled in time.
NOTE


Loopback1
2.2.2.9/32
PE2 GE1/0/1.1 CE2

100.2.1.1/24
GE1/0/1
GE1/0/2 100.2.1.2/24
=3
CP
AS65420
DS
CSG GE1/0/1.2
GE1/0/2
200.1.1.1/24
10.1.1.2/30
GE1/0/1.1 GE1/0/3
100.1.1.1/24 20.1.1.2/30
GE1/0/1.2 PE1
DS
Loopback1 Internet
200.1.1.2/24 GE1/0/2
CP
GE1/0/1.1 1.1.1.9/32 20.1.1.1/30 GE1/0/1 AS65421
=2
100.1.1.2/24
CE1 200.2.1.2/24
GE1/0/1.1
PE3 200.2.1.1/24 CE3
Loopback1
3.3.3.9/32
VLAN 10 AS65410 L3VPN

AS100
1. Configure basic L3VPN functions.

(2) Configure basic MPLS functions and MPLS LDP, and set up MPLS LSPs on the
backbone network.
(4) Create VPN instances on PEs.
2. Configure VLAN+DSCP and bind AC interfaces to the VPN instances.
3. Configure the basic Layer 2 forwarding function on CSG.
4. Configure EBGP on CEs and PEs to exchange VPN routing information.
5. Set up MP-IBGP peer relationships between PEs.
Data Preparation

l Names of the VPN instances on PEs

l RDs and VPN targets of the VPN instances
l Interfaces bound to the VPN instances
Procedure
Step 1 Configure basic L3VPN functions.
1. Configure the IP addresses of interfaces on CEs and PEs as described in Figure 4-26. The
detailed configurations are not mentioned here. You can see the configuration files in this
configuration example.
2. Configure an IGP on the MPLS backbone network. In this example, OSPF is adopted as
an IGP.
The detailed configurations are not mentioned here. You can see the configuration files in
this configuration example.
After the preceding configurations, PE1 and PE2, and PE1 and PE3 have routes discovered
through OSPF to Loopback 1 of each other. PE1 and PE2, and PE1 and PE3 can ping
through each other.
<PE1> display ip routing-table

2.2.2.9/32 OSPF 10 1 D 10.1.1.1
3.3.3.9/32 OSPF 10 1 D 20.1.1.1
10.1.1.0/30 Direct 0 0 D 10.1.1.2
20.1.1.0/30 Direct 0 0 D 20.1.1.2
<PE1> ping 2.2.2.9


0.00% packet loss
After the preceding configurations, MPLS LSPs are successfully created, and LDP sessions
are set up between PE1 and PE2 and between PE1 and PE3. Run the display mpls ldp
session command, and you can view that the Status field is displayed as Operational.


------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
4. Configure VPN instances.

# Configure PE1.
<PE1> system-view
[PE1] ip vpn-instance vpn1
[PE1-vpn-instance-vpn1] route-distinguisher 100:1
[PE1-vpn-instance-vpn1] vpn-target 100:1 both
[PE1-vpn-instance-vpn1] quit
# Configure PE2.
<PE2> system-view
# Configure PE3.
<PE3> system-view
Step 2 Configure VLAN+DSCP, and bind common sub-interfaces to the VPN instances.
# Configure PE1.
[PE1-GigabitEthernet1/0/1.1] ip binding vpn-instance vpn1
[PE1-GigabitEthernet1/0/1.1] ip address 100.1.1.1 24
# Configure PE2.
# Configure PE3.


After the preceding configurations, run the display ip vpn-instance verbose command on PEs,
and you can view the configurations of the VPN instances.
[PE1] display ip vpn-instance verbose
Total VPN-Instances configured : 2
VPN-Instance Name and ID : vpn1, 1

Create date : 2009/09/01 17:22:49
Up time : 0 days, 00 hours, 11 minutes and 46 seconds
Route Distinguisher : 100:1
Export VPN Targets : 100:1
Import VPN Targets : 100:1
Label Policy : label per route
The diffserv-mode Information is : uniform
The ttl-mode Information is : pipe
Log Interval : 5
Interfaces : GigabitEthernet1/0/1.1

Create date : 2009/09/01 17:27:07
Log Interval : 5

following:
NOTE
Packets sent from the CSG to PE1 carry VLAN tags with different DSCP values.
Step 4 Set up EBGP peer relationships between the PEs and the CEs to import VPN routes.
The detailed configurations are not mentioned here. You can refer to the chapter "BGP/MPLS
IP VPN Configuration" in the NE80E/40E Configuration Guide - VPN or the configuration files
in this configuration example.
Step 5 Set up MP-IBGP peer relationships between the PEs.
After the preceding configurations, run the display bgp peer command on the PEs, and you can
view that BGP peer relationships between PEs have been established and are in the Established
state.


[PE1] display bgp peer
BGP local router ID : 1.1.1.9

Local AS number : 100
Total number of peers : 2 Peers in established state : 2
Peer V AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv
2.2.2.9 4 100 10 15 0 00:04:53 Established 0

3.3.3.9 4 100 6 11 0 00:01:06 Established 2
Run the display ip routing-table vpn-instance command on PEs, and you can view the routes
to remote CEs.
[PE1] display ip routing-table vpn-instance vpn1
------------------------------------------------------------------------------
Routing Tables: vpn1
100.1.1.0/24 Direct 0 0 D 100.1.1.1

GigabitEthernet1/0/1.1
100.2.1.0/24 BGP 255 0 RD 2.2.2.9 GigabitEthernet1/0/2
------------------------------------------------------------------------------
200.1.1.0/24 Direct 0 0 D 200.1.1.1

Run the display interface vlan command, and you can view the matching policy configured on
sub-interfaces in VLAN 10.
-----------------------------------------------------------
GE1/0/1.2 dscp 2
GE1/0/1.1 dscp 3
-----------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
ip vpn-instance vpn1
route-distinguisher 100:1
vpn-target 100:1 export-extcommunity
vpn-target 100:1 import-extcommunity

#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
mpls ldp
#
ip binding vpn-instance vpn1
ip address 100.1.1.1 255.255.255.0
#
ip address 200.1.1.1 255.255.255.0
#
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 20.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
bgp 100
peer 2.2.2.9 as-number 100
peer 2.2.2.9 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
peer 2.2.2.9 enable
peer 3.3.3.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 2.2.2.9 enable
peer 3.3.3.9 enable
#
ipv4-family vpn-instance vpn1
import-route direct
#
import-route direct
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
#
return

#
sysname PE2
#
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
mpls ldp
#
vlan-type dot1q 10
ip address 100.2.1.1 255.255.255.0
#
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
import-route direct
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return
#
sysname PE3
#
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
mpls ldp
#
vlan-type dot1q 10


ip address 200.2.1.1 255.255.255.0
#
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
import-route direct
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 20.1.1.0 0.0.0.3
#
return
#
sysname CE1
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
bgp 65410
#
undo shutdown
ip address 200.1.1.2 255.255.255.0
bgp 65410
#
ipv4-family unicast
import-route direct
peer 100.1.1.1 enable
#
return
#
sysname CE2
#
undo shutdown
ip address 100.2.1.2 255.255.255.0
bgp 65420
#
ipv4-family unicast

import-route direct
#
return

#
sysname CE3
#
undo shutdown
ip address 200.2.1.2 255.255.255.0
bgp 65421
#
ipv4-family unicast
import-route direct
#
return

In the networking of this configuration example, VLAN+802.1p is configured on the sub-
interface at the AC side of a PE; the sub-interfaces are bound to different VPN instances. Packets
are transmitted through different VPN instances based on the 802.1p priorities of the packets.
The following takes the scenario where a CSG accesses IP services as an example.
As shown in Figure 4-26, different service packets are added with the same tag on the CSG.
Therefore, when PE1 receives packets, it cannot identify services based on tags, which affects
the traffic distribution. To address the problem, you can deploy a VLAN policy on PE1. PE1
distributes traffic to different VPN instances based on VLAN IDs and packet priorities. This
ensures that packets can be scheduled in time.
NOTE
In this example, PE1 parses 802.1p values in the received packets for scheduling.

Figure 4-26 Networking diagram of VLAN+802.1p-based L3VPN access

Loopback1
2.2.2.9/32
PE2 GE1/0/1.1 CE2

100.2.1.1/24
GE1/0/1
Loopback1 GE1/0/2 100.2.1.2/24 Database
=3
1.1.1.9/32 10.1.1.1/30 AS65420
p
2.1
80
CSG GE1/0/1.2
GE1/0/2
200.1.1.1/24
10.1.1.2/30
GE1/0/1.1 GE1/0/3
100.1.1.1/24 PE1 20.1.1.2/30
80
GE1/0/1.1 GE1/0/1.2
GE1/0/2 Internet
2.1
100.1.1.2/24 200.1.1.2/24
20.1.1.1/30 GE1/0/1 AS65421
CE1 p
=2 200.2.1.2/24
GE1/0/1.1
PE3 200.2.1.1/24 CE3
Loopback1
3.3.3.9/32
VLAN 10 AS65410 L3VPN

AS100

backbone network.
2. Configure VLAN+802.1p and bind AC interfaces to the VPN instances.
Data Preparation


Procedure
an IGP.
through each other.

2.2.2.9/32 OSPF 10 1 D 10.1.1.1
3.3.3.9/32 OSPF 10 1 D 20.1.1.1
10.1.1.0/30 Direct 0 0 D 10.1.1.2
20.1.1.0/30 Direct 0 0 D 20.1.1.2
<PE1> ping 2.2.2.9


0.00% packet loss


------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------

# Configure PE1.
<PE1> system-view
# Configure PE2.
<PE2> system-view
# Configure PE3.
<PE3> system-view
Step 2 Configure VLAN+802.1p, and bind common sub-interfaces to the VPN instances.
# Configure PE1.
# Configure PE2.
# Configure PE3.



Create date : 2009/09/01 17:22:49
Log Interval : 5

Create date : 2009/09/01 17:27:07
Log Interval : 5

following:
NOTE
state.



2.2.2.9 4 100 10 15 0 00:04:53 Established 0

3.3.3.9 4 100 6 11 0 00:01:06 Established 2
to remote CEs.
------------------------------------------------------------------------------
100.1.1.0/24 Direct 0 0 D 100.1.1.1

------------------------------------------------------------------------------
200.1.1.0/24 Direct 0 0 D 200.1.1.1

-----------------------------------------------------------
GE1/0/1.2 8021p 2
GE1/0/1.1 8021p 3
-----------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#

#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
mpls ldp
#
ip address 100.1.1.1 255.255.255.0
#
ip address 200.1.1.1 255.255.255.0
#
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 20.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 2.2.2.9 enable
peer 3.3.3.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 2.2.2.9 enable
peer 3.3.3.9 enable
#
import-route direct
#
import-route direct
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
#
return

#
sysname PE2
#
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
mpls ldp
#
vlan-type dot1q 10
ip address 100.2.1.1 255.255.255.0
#
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
import-route direct
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return
#
sysname PE3
#
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
mpls ldp
#
vlan-type dot1q 10


ip address 200.2.1.1 255.255.255.0
#
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
import-route direct
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 20.1.1.0 0.0.0.3
#
return
#
sysname CE1
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
bgp 65410
#
undo shutdown
ip address 200.1.1.2 255.255.255.0
bgp 65410
#
ipv4-family unicast
import-route direct
#
return
#
sysname CE2
#
undo shutdown
ip address 100.2.1.2 255.255.255.0
bgp 65420
#
ipv4-family unicast

import-route direct
#
return

#
sysname CE2
#
undo shutdown
ip address 200.2.1.2 255.255.255.0
bgp 65421
#
ipv4-family unicast
import-route direct
#
return
4.12.12 Example for Configuring Untagged+DSCP for L3VPN

Access
In the networking of this configuration example, PE1 receives untagged packets with different
DSCP values; untagged+DSCP is configured on the sub-interface at the AC side of PE1; the
sub-interface is bound to different VPN instances. Packets are transmitted through different VPN
instances based on the DSCP values of the packets. The following takes the scenario where a
CSG accesses IP services as an example.
On an ME network, VLAN IDs are used to identify various services or user packets before them
access to various VSIs, VLLs, or VPN instances. If multiple user packets or services are not
tagged, part of high-priority traffic over the operator's network cannot be scheduled in time,
On the network shown in Figure 4-27, a CSG forwards untagged packets. After receiving these
packets, PE1 cannot identify them, resulting in a failure in distributing packets. To help resolve
this problem, a DSCP-based policy needs to be configured on PE1. PE1 distributes packets to
specific VPN instances based on priorities, ensuring correct scheduling of packets.
NOTE

Figure 4-27 Networking diagram for untagged+DSCP-based L3VPN access

Loopback1
2.2.2.9/32
PE2 GE1/0/1.1 CE2

100.2.1.1/24
GE1/0/1
GE1/0/2 100.2.1.2/24
=3
Database
10.1.1.1/30
CP
GE1/0/1.2 AS65420
DS
200.1.1.1/24
CSG GE1/0/1.1 GE1/0/2
100.1.1.1/24 10.1.1.2/30
GE1/0/3
untagged+ 20.1.1.2/30
DSCP
PE1
DS
Loopback1 GE1/0/2 Internet
CP
1.1.1.9/32 20.1.1.1/30 GE1/0/1 AS65421
=2
GE1/0/1.1 GE1/0/1.2
100.1.1.2/24 200.1.1.2/24 200.2.1.2/24
GE1/0/1.1
CE1
PE3 200.2.1.1/24 CE3
Loopback1
3.3.3.9/32
L3VPN
AS65410
AS100

backbone network.
2. Configure untagged+DSCP and bind AC interfaces to the VPN instances.
Data Preparation


Procedure
an IGP.
through each other.

2.2.2.9/32 OSPF 10 1 D 10.1.1.1
3.3.3.9/32 OSPF 10 1 D 20.1.1.1
10.1.1.0/30 Direct 0 0 D 10.1.1.2
20.1.1.0/30 Direct 0 0 D 20.1.1.2
<PE1> ping 2.2.2.9


0.00% packet loss


------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------

# Configure PE1.
<PE1> system-view
# Configure PE2.
<PE2> system-view
# Configure PE3.
<PE3> system-view
Step 2 Configure untagged+DSCP, and bind sub-interfaces to the VPN instances.

# Configure PE1.
[PE1-GigabitEthernet1/0/1.1] untagged dscp 3
[PE1-GigabitEthernet1/0/1.2] untagged dscp 2
# Configure PE2.
# Configure PE3.


Create date : 2009/09/01 17:22:49
Log Interval : 5

Create date : 2009/09/01 17:27:07
Log Interval : 5

following:
state.


2.2.2.9 4 100 10 15 0 00:04:53 Established 0

3.3.3.9 4 100 6 11 0 00:01:06 Established 2
to remote CEs.
------------------------------------------------------------------------------
100.1.1.0/24 Direct 0 0 D 100.1.1.1

------------------------------------------------------------------------------
200.1.1.0/24 Direct 0 0 D 200.1.1.1

Run the display interface vlan command, and you can view the matching policy on a main
interface.
[PE1] display interface GigabitEthernet1/0/1 vlan untagged
-----------------------------------------------------------
GE1/0/1.2 dscp 2
GE1/0/1.1 dscp 3
-----------------------------------------------------------
Interface:GE1/0/1 VLAN ID: UNTAGGED Sub-Interface num: 2
----End
Configuration Files
#
sysname PE1
#
#
mpls lsr-id 1.1.1.9
mpls

#
mpls l2vpn
#
mpls ldp
#
untagged dscp 3
ip address 100.1.1.1 255.255.255.0
#
untagged dscp 2
ip address 200.1.1.1 255.255.255.0
#
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 20.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 2.2.2.9 enable
peer 3.3.3.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 2.2.2.9 enable
peer 3.3.3.9 enable
#
import-route direct
#
import-route direct
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
#
return
#
sysname PE2
#

#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
mpls ldp
#
ip address 100.2.1.1 255.255.255.0
#
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
import-route direct
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return
#
sysname PE3
#
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
mpls ldp
#
ip address 200.2.1.1 255.255.255.0
#
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#

interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
import-route direct
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 20.1.1.0 0.0.0.3
#
return
#
sysname CE1
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
bgp 65410
#
undo shutdown
ip address 200.1.1.2 255.255.255.0
bgp 65410
#
ipv4-family unicast
import-route direct
#
return
#
sysname CE2
#
undo shutdown
ip address 100.2.1.2 255.255.255.0
bgp 65420
#
ipv4-family unicast
import-route direct
#
return
#
sysname CE3

#
undo shutdown
ip address 200.2.1.2 255.255.255.0
bgp 65421
#
ipv4-family unicast
import-route direct
#
return
4.12.13 Example for Configuring Interface Isolation in a VLAN

After interface isolation in a VLAN is configured, isolated interfaces cannot communicate with
each other in the VLAN.
As shown in Figure 4-28, the VLAN10 is configured on the router. GE1/0/0 and Host A are
connected through switch, and GE2/0/0 and Host B are connected through switch.
Requirements: Host A and Host B cannot be connected directly in a VLAN. The traffic from
Host A to Host B must pass through layer 3 route, which is convenient for statistics.
Figure 4-28 Networking diagram of configuring interface isolation in a VLAN

Router
GE1/0/0 GE2/0/0
VLAN10
HostA HostB
1. Switch the routed interfaces to the layer 2 interfaces.

2. Add the routed interfaces into the corresponding VLANs.
3. Configure the isolated interfaces of GE1/0/0 and GE2/0/0.
4. Enable the ARP proxy in a VLAN.

5. Add the switch interfaces into the same VLAN.
Data Preparation
To complete the configuration, you need the following data
l GE1/0/0 and GE2/0/0 that belongs to VLAN10
l The IP address 10.1.1.1/24 of VLANIF 10
Procedure
Step 1 Configuring interface isolation in a VLAN.
# Create VLAN10.
[HUAWEI] vlan 10
[HUAWEI-vlan10] quit
# Add the interface into VLAN10, and configure the interface isolation.
[HUAWEI] interface gigabitethernet 1/0/0
[HUAWEI-GigabitEthernet1/0/0] portswitch
[HUAWEI-GigabitEthernet1/0/0] port default vlan 10
[HUAWEI-GigabitEthernet1/0/0] port isolate-state enable vlan 10
[HUAWEI-GigabitEthernet1/0/0] quit
[HUAWEI-GigabitEthernet2/0/0] port isolate-state enable vlan 10
After the configuration, Host A and Host B cannot ping through each other.
Step 2 Enable the ARP proxy in a VLAN.
# Create the VLANIF interface.
[HUAWEI] interface vlanif 10
[HUAWEI-vlanif10] ip address 10.1.1.1 24
# Enable the ARP proxy in a VLAN.

[HUAWEI-vlanif10] arp-proxy inner-sub-vlan-proxy enable

When the configuration is complete, Host A and Host B can ping through each other.
----End
Configuration Files
Configuration file of router
#
sysname HUAWEI
#
vlan 10
#
interface Vlanif10
ip address 10.1.1.1 255.255.255.0

arp-proxy inner-sub-vlan-proxy enable

#
undo shutdown
portswitch
port isolate-state enable vlan 10
#
undo shutdown
portswitch
port isolate-state enable vlan 10
#
return
4.12.14 Example for Configuring the Isolation Based on Interface

Groups in a VLAN
After interface group isolation in a VLAN is configured, interfaces that belong to different groups
in a VLAN cannot communication with each other, but interfaces in the same isolation group
can communication with each other.
NOTE
The interface group isolation in a VLAN is not supported in NE80E/40E-X1 and NE80E/40E-X2.
As shown in Figure 4-29, VLAN 10 is created on the router. GE 1/0/0 is connected with host
A through switch; GE 2/0/0 is connected with host B through switch; GE 2/0/1 is connected
with host C through switch; GE 1/0/1 is connected with host D through switch; GE 3/0/0 is
connected with host E through switch.
The requirements are as follows:
l host A can communicate with host B and host C can communicate with host D.
l host A and host B cannot communicate with host C and host D.
l host E can communicate with the hosts in VLAN 10.
Figure 4-29 Networking diagram of configuring the isolation based on interface groups in a
VLAN
Router
GE1/0/0 GE1/0/1
GE2/0/0 GE2/0/1
GE3/0/0
hostA hostB hostE hostC hostD
VLAN10

1. Switch the interfaces of the router to be Layer 2 interfaces.
2. Add the interfaces of the router to different isolated interface groups.
3. Add the interfaces that cannot communicate with each other to different isolated interface
groups.
4. Add the switch interfaces into the same VLAN.
Data Preparation
l GE 1/0/0, GE 2/0/0, GE 2/0/1, GE 1/0/1, and GE 3/0/0 that belong to VLAN 10
l GE 1/0/0 and GE 2/0/0 that belong to the isolated group 1
l GE 2/0/1 and GE 1/0/1 that belong to the isolated group 2
Procedure
Step 1 Create an interface-based VLAN 10.
# Create VLAN 10.
[HUAWEI] vlan 10
[HUAWEI-vlan10] quit
# Add interfaces to VLAN 10.

Step 2 Add the interfaces to the isolated group.

# Add GE 1/0/0 and GE 2/0/0 to the isolated group 1.
[HUAWEI-GigabitEthernet1/0/0] port-isolation group 1


# Add GE 2/0/1 and GE 1/0/1 to the isolated group 2.


After the configuration, you can run the display port-isolation group command to view the
configuration of the isolated group.
[HUAWEI] display port-isolation group brief
After the configuration, host E can communicate with other hosts. host A cannot communicate
with host C and host D. host B cannot communicate with host C and host D.
----End
Configuration Files
The configuration file of the router is as follows:
#
sysname HUAWEI
#
vlan 10
#
undo shutdown
portswitch
port-isolation group 1
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown

portswitch
#
return
4.12.15 Example for Configuring Ethernet Loop Detection for a

VLAN
After Ethernet loop detection for a VLAN is configured, the NE80E/40E can block a
corresponding interface when detecting a loop, thus preventing broadcast storms on the network.
As shown in Figure 4-30, CE1 accesses PE1 and PE2 in the carrier network through redundant
links. Interfaces on PE1 and PE2 belong to the same VLAN. The two interfaces that connect
CE1 to PE1 and PE2 also belong to the same VLAN. It is required that Ethernet loop detection
be configured for the VLAN on the PE devices and interfaces on PE2 be blocked first when a
loop occurs.
Figure 4-30 Networking diagram of configuring Ethernet loop detection for a VLAN
PE1 PE2
GE2/0/0 GE1/0/0
GE1/0/0 GE2/0/0
CE1
GE1/0/0 GE2/0/0
1. Create a VLAN on the PE and CE devices to ensure interworking between them.

2. Configure Ethernet loop detection for the VLAN.
3. Configure the block priority for each interface in the VLAN.
Data Preparation
l ID of the VLAN
l Times of loopback, interval of the detection time, cycle of the detection interval, time for
blocking a loop, and retry times for blocking a port permanently

l Block priority of each interface
Procedure
Step 1 Create a VLAN on the PE and CE devices to ensure Layer 2 interworking.
# Configure PE1.
[PE1] vlan 100
[PE1-vlan100] quit
[PE1-GigabitEthernet1/0/0] port link-type access
[PE1-GigabitEthernet2/0/0] port link-type trunk
[PE1-GigabitEthernet2/0/0] port trunk allow-pass vlan 100
# Configure PE2.
[PE2] vlan 100
[PE2-vlan100] quit
[PE2-GigabitEthernet1/0/0] port link-type trunk
[PE2-GigabitEthernet2/0/0] port link-type access
# Configure CE1.
CE1 is a switch and interfaces on CE1 default to Layer 2 interfaces. In this example, you can
configure GE 1/0/0 and GE 2/0/0 on CE1 as access interfaces and add them to VLAN 100.
Step 2 Configure Ethernet loop detection for the VLAN and set the block priority of each interface.
# Configure PE1.
[PE1] vlan 100
[PE1-vlan100] loop-detect eth-loop loop-times 10 detect-cycle 10 cycles 3 retry-
times 3 block-time 100
[PE1-vlan100] quit
[PE1-GigabitEthernet1/0/0] loop-detect eth-loop priority 1
# Configure PE2.
[PE2] vlan 100

[PE2-vlan100] loop-detect eth-loop loop-times 10 detect-cycle 10 cycles 1 retry-

times 3 block-time 100
[PE2-vlan100] quit
After the preceding configuration, run the display loop-detect eth-loop command on PE
devices. You can view the parameters of Ethernet loop detection for VLAN 100.
[PE1] display loop-detect eth-loop vlan 100
VLAN/VSI LTimes D-Cycle Cycles Retry Action
-----------------------------------------------------------------------
VLAN 100 10 10 3 3 Block 100s
Total Items = 1
Blocked Port:
---------------
VLAN/VSI Block Port Link-Block Port Detect MAC
------------------------------------------------------------------------------
[PE2] display loop-detect eth-loop vlan 100
VLAN/VSI LTimes D-Cycle Cycles Retry Action
-----------------------------------------------------------------------
VLAN 100 10 10 1 3 Block 100s
Total Items = 1
Blocked Port:
---------------
VLAN/VSI Block Port Link-Block Port Detect MAC
------------------------------------------------------------------------------
1 GE2/0/0
At this time, cycles is set to 3 on PE1 and set to 1 on PE2. In this case, when a loop occurs in
VLAN 100, interfaces on PE2 are blocked first. On PE2, the priority of GE 2/0/0 is lower than
that of GE 1/0/0. Thus, GE 2/0/0 is blocked first.
----End
Configuration Files
#
sysname PE1
#
vlan batch 100
loop-detect eth-loop loop-times 10 detect-cycle 10 cycles 3 retry-times 3
block-time 100
#
undo shutdown
portswitch
loop-detect eth-loop priority 1
#
undo shutdown
portswitch
#
return


#
sysname PE2
#
vlan batch 100
loop-detect eth-loop loop-times 10 detect-cycle 10 cycles 1 retry-times 3
block-time 100
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return

Configuration Guide - LAN Access and MAN Access 5 QinQ Configuration
5 QinQ Configuration
About This Chapter
The QinQ technology makes up for the shortage of public VLAN ID resources, and also provides
a simpler Layer 2 VPN solution for LANs or small-scale MANs.
5.1 QinQ Introduction

The QinQ protocol is a Layer 2 tunneling protocol based on the IEEE 802.1Q standard.
5.2 Configuring the QinQ Tunnel Function
This section describes how to configure a QinQ Layer 2 tunnel. Thus, packets with double tags
can be transmitted. In addition, the EthType in the outer tag can be flexibly configured.
5.3 Configuring Selective QinQ on a Layer 2 Interface
This section describes how to configure Layer 2 selective QinQ. Thus, a packet with different
outer VLAN tags can be transmitted and the EthType in the outer VLAN tag can be flexibly
configured.
5.4 Configuring the Sub-interface for VLAN Tag Termination to Access the IP Service
IP services include proxy ARP, and DHCP services. You can deploy IP services on sub-
interfaces for VLAN tag termination to enable the interworking between users in different
VLANs, thus ensuring reliable, stable, and uninterrupted connections between the users and the
network.
5.5 Configuring the Sub-interface for VLAN Tag Termination to Access the Multicast Service
With the wide use of multicast services on the Internet, you need to deploy sub-interfaces for
QinQ/dot1q VLAN tag termination to process the user packets carrying a single tag or double
tags for multicast services. In this manner, the UPE can maintain information about the outbound
interface of multicast packets according to the established multicast forwarding table to ensure
the normal communications between hosts and the multicast source.
5.6 Configuring the Sub-interface for VLAN Tag Termination to Access the VPN Service
VPN services are classified into L2VPN services and L3VPN services. You can configure sub-
interfaces for VLAN tag termination on PEs to access VPNs to enable the interworking between
CEs and users.
5.7 Configuring the Sub-interface for VLAN Tag Termination to Access the MPLS Service
The sub-interface for VLAN tag termination to access the MPLS service are classified into the
following types of MPLS LDP service and MPLS TE service.

5.8 Configuring the Sub-interface for QinQ VLAN Tag Termination to Support 802.1p Mapping
After tags are terminated on PEs, packets are sent to the IP or MPLS network of the ISP. To
ensure the completeness of the QoS information in the packets, the 802.1p values in outer and
inner tags need to be mapped to the DSCP field or the EXP field.
5.9 Configuring the Sub-interface for QinQ Stacking to Access an L2VPN
You can configure sub-interfaces for QinQ stacking on PEs to access L2VPNs so that the inner
tags of user packets are invisible on the ISP network.
5.10 Configuring Dynamic QinQ
Dynamic QinQ is configured on the sub-interface for VLAN tag termination of the DHCP relay
at the client side to allocate VLAN tag resources for login users. When a user abnormally logs
out after obtaining an IP address, the system can sense the event automatically, delete the binding
in the DHCP binding table, and instruct the DHCP server to release the IP address and VLAN
tag resources.
5.11 Configuring the Sub-interface for QinQ VLAN Tag Termination to Support URPF
Configuring sub-interfaces for QinQ VLAN tag termination to support Unicast Reverse Path
Forwarding (URPF) effectively prevents attacks based on source address spoofing through sub-
interfaces for QinQ VLAN tag termination.
5.12 Configuring the User-Side QinQ
When configuring a user VLAN on an Ethernet sub-interface, you can specify either the start
and end VLAN IDs or the start and end QinQ VLAN IDs. Note that a maximum of 16 consecutive
QinQ VLAN IDs can be specified in a command. When the NE80E/40E is connected to users
through two switches, the switch adjacent to users adds an inner tag to a user packet (or remove
the inner tag from the user packet) and the switch adjacent to the NE80E/40E adds an outer tag
to the user packet (or remove the outer tag from the user packet).
5.13 Maintaining QinQ
Commands of clearing statistics on a QinQ interface helps to locate the faults on a QinQ interface.
This section describes the typical application scenarios of QinQ, including networking
files.

5.1 QinQ Introduction

The QinQ protocol is a Layer 2 tunneling protocol based on the IEEE 802.1Q standard.
5.1.1 QinQ Overview

The QinQ technology improves the utilization of VLANs by adding another 802.1Q tag to a
packet with an 802.1Q tag. In this manner, services from the private VLAN can be transparently
transmitted through the public network.
In intercommunication between Layer 2 LANs on the basis of the traditional IEEE 802.1Q
protocol, when two user networks access each other through an ISP, the ISP must assign VLAN
IDs to users of different VLANs, as shown in Figure 5-1. Suppose User Network1 and User
Network2 access the backbone network through PE1 and PE2 of an ISP.
Figure 5-1 Intercommunication between Layer 2 LANs on the basis of the traditional IEEE
802.1Q protocol
Trunk Trunk
VLAN100~200 VLAN100~200
CE1 PE1
Trunk
VLAN100~200
P
Trunk
User VLAN100~200
Network1 PE2 CE2
ISP
Network
User
Network2
To connect VLAN 100 - VLAN 200 on User Network1 to VLAN 100 - VLAN 200 on User
Network2, you must change the attribute of the interfaces of CE1, PE1, and P that connect PE2
and CE2 to the trunk and allow packets of VLAN 100 - VLAN 200 to pass.
This configuration makes user's VLANs visible on the backbone network. In this case, the VLAN
ID resources (4094 VLAN IDs) of an ISP are wasted. In addition, the ISP has to manage user
VLAN IDs and users have no right to manage their VLANs.
A rush of too many users accessing the network may cause the ISP network to be short of VLAN
IDs because an ISP network has only 4094 VLAN IDs.
In addition, different users cannot use the same VLAN ID and user's VLAN IDs must be planned
by an ISP.
QinQ is a technology used to expand the VLAN space by encapsulating a packet that carries an
802.1Q tag in another 802.1Q tag. The private VLANs thus can transparently transmit packets
over the public network and the preceding problem is solved.

The QinQ technology expands the VLAN space by encapsulating a packet that carries an 802.1Q
tag in another 802.1Q tag. The private VLANs thus can transparently transmit packets over the
public network. This function is the same as the Layer 2 VPN. Packets that are forwarded over
the backbone network carry two 802.1Q tags, one for the public network and the other for the
private network. This is called 802.1Q-in-802.1Q, or QinQ for short.
The ISP network only provides one VLAN ID for different VLANs from the same user network.
This saves VLAN IDs of an ISP. Meanwhile, the QinQ provides a simple Layer 2 VPN solution
to a small metropolitan area network (MAN) or a local area network (LAN).
The QinQ technology has been widely used on ISPs' networks because of its easy application.
The QinQ technology can be applied to multiple services in a metropolitan area Ethernet solution.
The emergence of flexible QinQ that is VLAN stacking enables QinQ services to widely spread
among ISPs.
This technology has the following features:
l Private networks are effectively segregated from the public network.
l ISP's VLAN IDs are saved to the maximum.
With the development of the metropolitan area Ethernet, all device vendors have put forward
their solutions to the metropolitan area Ethernet. The QinQ technology plays an important role
in the solutions because of its simplicity and flexibility.
5.1.2 QinQ Feature Supported by the NE80E/40E

Owing to its simplicity and flexibility, QinQ plays an important role in solutions.
QinQ of Layer 2 Interfaces

l QinQ tunnel
l Selective QinQ (VLAN stacking)
l Compatibility of QinQ EType in the outer tag or inner tag.
As shown in Figure 5-2, 802.1Q defines that the Ethernet encapsulation type field (EType) value
of the Tag Protocol Identifier (TPID) is 0x8100. In QinQ encapsulation, the value of the EType
in the inner TPID of devices from each vendor is 0x8100. The value of the EType in the outer
TPID, however, varies with vendors.
Figure 5-2 802.1 encapsulation

802.1Q Encapsulation
DA SA ETYPE TAG LEN/ETYPE DATA FCS
6 Bytes 6 Bytes 2 Bytes 2 Bytes 2 Bytes 46 Byte~1500 Bytes 4 Bytes
QinQ
Encapsulation
DA SA ETYPE TAG ETYPE TAG LEN/ETYPE DATA FCS
6 Bytes 6 Bytes 2 Bytes 2 Bytes 2 Bytes 2 Bytes 2 Bytes 46 Byte~1500 Bytes 4 Bytes
The NE80E/40E supports the compatibility of ETypes in different QinQ outer TPIDs. That is,
the NE80E/40E can identify and encapsulate packets with different outer ETypes, thus
implementing inter-operation among devices from different vendors.

NOTE
IEEE 802.1ad defines the value of the EType field in the outer TPID to 0x88a8.
As shown in Figure 5-3, on Router B, the inbound interface can identify the QinQ packet with
the Etype value in the outer TPID being 0x9100 and the outbound interface can set ETypes in
the outer TPID to different values according to vendors, such as 0x9100, 0x8100, or other values.
Thus, Router B can inter-operate with the devices of different vendors.
Figure 5-3 Compatibility of Etypes in the outer TPIDs of QinQ packets
00
0x91
0x9100
Switch A
IP/MPLS
Core 0x81
Router A Router B 00
Router C
As shown in Figure 5-4, Router A and Switch A are non-Huawei devices, and Router B is a
Huawei Datacom device. By default, the inbound interface on Router B can identify the QinQ
packets with ETypes of both inner and outer tags being 0x8100. Then, to implement interworking
between non-Huawei devices and the Huawei device, you should configure the compatibility of
ETypes of the tags carried in the QinQ packets sent by the devices of different vendors.
Figure 5-4 Compatibility of ETypes in the outer TPIDs of QinQ packets

xxxx 0x9100 10 xxxx xxxx 0x9100 100 0x9100 10 xxxx
GE1/0/1
RouterA SwitchA RouterB
Sub-interface for QinQ/Dot1q VLAN Tag Termination

Termination refers to identifying single or double tags of QinQ packets and then stripping one
tag or double tags or sending the packets according to the subsequent forwarding operations.
Termination is usually conducted on route sub-interfaces, that is, sub-interfaces for QinQ/dot1q
VLAN tag termination.
l A route sub-interface that terminates a single tag is called the sub-interface for dot1q VLAN
tag termination.
l A route sub-interface that terminates double tags is called the sub-interface for QinQ VLAN
tag termination.
Table 5-1 shows the differences among the VLANIF interface, dot1q sub-interface, sub-
interface for dot1q VLAN tag termination, and sub-interface for QinQ VLAN tag termination.

Table 5-1 Differences among types of interfaces

Interfa Description Supported Service Difference
ce
Type VLL PWE3 VPLS L3V
(CCC PN
mode
)
VLANI You can run Not Not Suppor Supp l The dot1q sub-interface
F the interface suppo suppor ted orted and sub-interface for
interfac vlanif rted ted dot1q VLAN tag
e command to termination have the
create a same function. Their
VLANIF difference is that packets
interface. sent from the dot1q sub-
A VLANIF interface are
interface is a encapsulated with only
Layer 3 one VLAN tag; packets
logical sent from the sub-
interface, interface for dot1q
which can be VLAN tag termination
configured can be encapsulated with
with an IP multiple VLAN tags.
address to l You can configure both
communicate sub-interfaces for dot1q
with devices VLAN tag termination
at the and sub-interfaces for
network QinQ VLAN tag
layer. termination on the same
main interface. In this
Dot1q You can run Suppo Suppo Suppor Supp
manner, the same main
sub- the vlan-type rted rted ted orted
interface can terminate
interfac dot1q
both single-tagged
e command to
packets and double-
configure an
tagged packets. If a main
Ethernet sub-
interface is configured
interface to
with QinQ VLAN tag
be a dot1q
termination, single-
sub-
tagged packets can be
interface.
terminated only on sub-
Sub- You can run Not Suppo Suppor Supp interfaces for dot1q
interfac the dot1q suppo rted ted orted VLAN tag termination
e for termination rted rather than on dot1q sub-
dot1q vid command interfaces.
VLAN to configure a
tag sub-interface
terminat to terminate
ion single-tagged
packets.

Interfa Description Supported Service Difference

ce
Type VLL PWE3 VPLS L3V
(CCC PN
mode
)
Sub- You can run Suppo Suppo Suppor Supp

interfac the qinq rted rted ted orted
e for termination
QinQ pe-vid ce-
VLAN vid command
tag to configure a
terminat sub-interface
ion to terminate
double-
tagged
packets.
Table 5-2 and Table 5-3 show how interfaces of different types process VLAN tags carried in
packets to be transmitted across a VPLS network.
Table 5-2 Packet processing on the inbound interface

Type of the Inbound Procedure of Processing VLAN Tags
Interface
Ethernet-encapsulated VLAN-encapsulated
Packets Packets
VLANIF interface Tags are stripped. No action is performed.
Dot1q sub-interface Tags are stripped. No action is performed.
Sub-interface for dot1q Tags are stripped. No action is performed.

VLAN tag termination
Sub-interface for QinQ l Outer tags are stripped in l No action is performed in

VLAN tag termination symmetric mode. symmetric mode.
l Double tags are stripped in l Double tags are stripped in
asymmetric mode. asymmetric mode and then a
tag is added.

Table 5-3 Packet processing on the outbound interface

Type of the Procedure of Processing VLAN Tags
Outbound Interface
Ethernet-encapsulated VLAN-encapsulated
Packets Packets
VLANIF interface l No action is performed by l The tag is stripped by

default. default.
l A specific tag is added in l The tag is replaced in trunk
trunk mode. mode.
Dot1q sub-interface A specific tag is added. The tag is replaced.
Sub-interface for dot1q A specific tag is added. The tag is replaced.

Sub-interface for QinQ l Outer tags are added in l Outer tags are replaced in
VLAN tag termination symmetric mode. symmetric mode.
l Double tags are added in l One tag is stripped and
asymmetric mode. double tags are added in
asymmetric mode.
Figure 5-5 Networking diagram of service deployment on the sub-interface for QinQ/dot1q
Set the interface mode to the
user-termination mode
Create a sub-interface
Configure the sub-interface Configure the sub-interface

for dot1q VLAN tag for QinQ VLAN tag
termination termination
Deploy services such as ARP, VRRP,

L2VPN, and L3VPN services on the sub-
interface
The detailed implementation and function of the sub-interface for QinQ VLAN tag termination
are related with the specific scenario. As shown in Figure 5-5, the sut-interface for QinQ/dot1q
VLAN tag termination can be deployed with services listed in Table 5-4.

Table 5-4 Services supported by the sut-interface for QinQ/dot1q VLAN tag termination
Sub- Supporte Service Sub- Description
interface d Service type
Type Type
QinQ/Dot1q IP Service ARP Proxy The sub-interface for VLAN tag termination
VLAN Tag can connect different VLANs to the same
Termination network segment. If users on the same network
segment belong to different VLANs, they
cannot communicate with each other on the
Layer 2 network unless the sub-interface for
VLAN tag termination supports ARP proxy
and thus implements IP forwarding.
For details of proxy ARP, see the chapter
"ARP" in the HUAWEI NetEngine80E/40E
Feature Description - IP Services.
DHCP l The sub-interface for VLAN tag

l DHCP termination can be configured with the
Server Dynamic Host Configuration Protocol
(DHCP) server function to assign IP
l DHCP addresses to users.
Relay
l The sub-interface for VLAN tag
termination can be configured with the
DHCP relay function to provide reference
for the DHCP server to assign IP addresses
and parameters by inserting tag information
into Option82.
For details of DHCP, see the chapter "DHCP"
in the HUAWEI NetEngine80E/40E Feature
Description - IP Services.
VRRP Users usually require communicating with

certain networks at any time. In this case, The
Virtual Router Redundancy Protocol (VRRP)
running on the sub-interface for VLAN tag
termination ensure a reliable communication
and provides an active/standby mechanism for
dot1q or QinQ users.
For details of VRRP, see the chapter "VRRP"
in the HUAWEI NetEngine80E/40E Feature
Description - Reliability.


Type Type
Multicast Layer 2 After being bound to a VSI and enabled with

Service Multicast IGMP snooping, the sub-interface for QinQ/
dot1q VLAN tag termination can listen IGMP
messages exchanged between the multicast
device and hosts, and therefore can learn which
interfaces have multicast receivers. In this
case, multicast packets are transmitted on the
Layer 2 network in multicast mode rather than
broadcast mode, and consequently received
only by members of the multicast group.
For details of Layer 2 multicast, see the chapter
"Layer 2 Multicast" in the HUAWEI
NetEngine80E/40E Feature Description - IP
Multicast.
Layer 3 Multicast protocol packets with double tags are

Multicast sent from the UPE to the upper network. After
the sub-interface for QinQ or dot1q VLAN tag
termination is configured on the UPE, the UPE
creates the forwarding table and the routing
table. When receiving multicast protocol
packets from hosts, the UPE can identify the
packets and correctly forward the packets.
Based on the established multicast forwarding
table, the UPE can replicate and deliver
multicast packets correctly.
In this section, Layer 3 multicast refers to
IGMP. For details of IGMP, see the chapter
"IGMP" in the HUAWEI NetEngine80E/40E
Feature Description - IP Multicast.
VPN L2VPN l The access of the sub-interface for QinQ/

Service l PWE3/ dot1q VLAN tag termination to PWE3/
VLL VLL means that the sub-interface for QinQ/
dot1q VLAN tag termination is configured
l VPLS with PWE3/VLL functions.
l The support of VPLS by the sub-interface
for QinQ/dot1q VLAN tag termination
refers to configuring VPLS on the sub-
interface for VLAN tag termination.
For details of L2VPN, see the chapter "PWE3",
"VLL", and "VPLS" in the HUAWEI
NetEngine80E/40E Feature Description -
VPN.


Type Type
L3VPN The access of the sub-interface for QinQ/dot1q

VLAN tag termination to L3VPN means that
the sub-interface for QinQ/dot1q VLAN tag
termination is configured with L3VPN
functions.
For details of L3VPN, see the chapter "BGP/
MPLS IP VPN" in the HUAWEI
NetEngine80E/40E Feature Description -
VPN.
QinQ 802.1p, - After being terminated on the PE, the packet is

termination DSCP sent to the ISP network. To ensure the
sub- Remark completeness of the QoS information in the
interface packet, the 802.1p values in outer and inner
tags need to be mapped to the DSCP field.
802.1p, - After being terminated on the PE, the packet is

EXP sent to the ISP MPLS network. To ensure the
(MPLS) completeness of the QoS information in the
Remark packet, the 802.1p values in outer and inner
tags need to be mapped to the EXP field.
NOTE
l Services that can be deployed on sub-interfaces for VLAN tag termination are not limited to those
listed in Table 5-4.
l For details of services that can be deployed on sub-interfaces for VLAN tag termination, see the chapter
"QinQ" in the HUAWEI NetEngine80E/40E Feature Description - LAN Access and MAN Access.
Access to L2VPN Through the Sub-interface for QinQ Stacking

l Access to a PWE3/VLL Network Through the Sub-interface for QinQ Stacking
VLL is a point-to-point L2VPN, which is not supported by the VLANIF interface. In this
case, users can access the L2VPN only through a main interface. However, a physical
interface is unable to access multiple users to the L2VPN at the same time. To solve the
problem, you can configure the VLAN-based QinQ function at different sub-interfaces. In
this scenario, CE-VLANs on both sides must be symmetrical.
l Access to a VPLS Through the Sub-interface for QinQ Stacking
When users access an ISP network in VPLS mode, you can enable packets from user
VLANs to be transmitted transparently over ISP networks in the following two ways:
– Enable VLAN-based QinQ on the switched interface and bind the VLANIF interface
to a VSI.
– Create a sub-interface on a routed interface and then configure VLAN stacking on the
sub-interface.

Dynamic QinQ
A common sub-interface for QinQ termination can terminate a maximum of 16,000 double-
tagged user packets. When the number of the user packets exceeds 16,000, you can use the
dynamic QinQ function. After that, the sub-interface for QinQ aggregation can terminate a
maximum of 64,000 double-tagged user packets.
NOTE
After being configured with dynamic QinQ, the sub-interface for VLAN tag termination cannot support
Virtual Leased Line (VLL), Pseudo Wire Emulation Edge-to-Edge (PWE3), Virtual Private LAN Service
(VPLS), static ARP, and DHCP snooping static binding table.
Figure 5-6 Networking diagram for dynamic QinQ

DHCP Server
GE1/0/0
100.1.1.2/24
DHCP Snooping Trusted

enable IP ×× ××
GE2/0/0
100.1.1.1/24
DHCP Relay
Untrusted
GE1/0/0.1 QinQ termination
10.1.1.1/24 Dynamic QinQ
IP 30 10
GE2/0/0 IP 20 10
Switch
/ 1 GE
IP 20 E1 /0 1 /0
IP
G /2 30
DHCP Client1 DHCP Client2
As shown in Figure 5-6, the DHCP client is connected to the DHCP relay through two-hierarchy
switches and requests a valid IP address from the DHCP server through the DHCP relay.
Dynamic QinQ is configured on the sub-interface for VLAN tag termination on the client side
of the DHCP relay to allocate VLAN tags to the login users. After ARP is associated with the
DHCP binding table, when users log out abnormally after obtaining IP addresses, the system
senses this failure automatically, and then deletes the binding relationship in the DHCP binding
table and informs the DHCP server to release IP addresses and VLAN tags.

In the case of interfaces configured with dynamic QinQ, usually it is users who send the ARP
request actively to the gateway device; if ARP rigid learning is also configured on the device,
all interfaces on the device learn the responses to the ARP requests that are actively sent by
themselves instead of learning the requests sent by other devices. As a result, dynamic QinQ
interfaces on this device cannot learn ARP entries of users and then users fail to log in. To solve
the problem, you can run the arp learning strict force-disable command on the interface
configured with dynamic QinQ so that the interface can learn the ARP requests sent by users.
Sub-interfaces for QinQ VLAN Tag Termination Support URPF

Unicast Reverse Path Forwarding (URPF) is used to avoid source-address-spoofing attacks.
After being configured with URPF, the sub-interface for QinQ VLAN tag can resist source-
address-spoofing attacks.
A URPF-enabled sub-interface for QinQ VLAN tag termination resists source-address-spoofing

attacks as follows:
l Obtains the source address, the inner and outer VLAN tags, and the inbound interface of
the packet.
l Takes the source address of the packet as the destination address and searches the
forwarding table for the relevant outbound interface and the inner and outer VLAN tags.
l Compares the searching result and the obtained information of the packet. If they are
inconsistent,sub-interface for QinQ VLAN tag termination regards the source address as
spoofing and discards the packet.
In this way, hostile attacks by modifying the source address can be avoided.
There are two URPF check modes:
l Loose URPF: A packet passes the URPF check if the relevant routing entry exists in the
forwarding table.
l Strict URPF: A packet passes the URPF check only when the relevant routing entry exists
in the forwarding table and the interface information matches.
NOTE
The sub-interface for QinQ VLAN tag termination on the NE80E/40E supports only loose URPF.
Sub-interfaces for QinQ VLAN Tag Termination Support IPv6

Sub-interfaces for QinQ VLAN tag termination support IPv6 unicast and multicast, OSPFv3,
IS-ISv6, BGP4+, RIPng, IPv6 BFD, IPv6 VRRP, dynamic QinQ of IPV6, and IPv6 loose and
half-strict URPF. In addition, one sub-interface for QinQ VLAN tag termination can be bound
to L3VPN_v4 and L3VPN_v6.
5.2 Configuring the QinQ Tunnel Function

This section describes how to configure a QinQ Layer 2 tunnel. Thus, packets with double tags
can be transmitted. In addition, the EthType in the outer tag can be flexibly configured.


Before configuring a QinQ Layer 2 tunnel, familiarize yourself with the applicable environment,
complete the pre-configuration tasks, and obtain the required data. This can help you complete
When multiple VLANs are required, the QinQ tunnel need be configured. You can add the outer
tag to the VLAN so that the range of available number of VLANs is widen; thus, the number of
VLANs is no longer insufficient.
Pre-configuration Task
Before configuring the QinQ tunnel, complete the following tasks:
l Ensuring that the device is powered on correctly and operates properly

l Configuring basic attributes of the Ethernet interface
Data Preparation
To configure the QinQ tunnel, you need the following data.
No. Data
1 Interface number of the QinQ tunnel
2 ID of the outer VLAN tag
5.2.2 Creating the Outer VLAN Tag for a Layer 2 Interface

After a Layer 2 interface is configured with selective QinQ, different outer tags can be added to
packets and the EthType in QinQ tags can be flexibly configured.
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
A VLAN is created and its view is displayed.
The VLAN ID refers to the value of the outer tag specified in the QinQ tunnel function. The
VLAN ID ranges from 1 to 4094.
----End

5.2.3 Configuring QinQ for a Layer 2 Interface

After a Layer 2 interface is configured with selective QinQ, the interface adds a public VLAN
tag to the user packet that carries a private VLAN tag so that the user packet can be forwarded
on the public network.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the Ethernet interface that need be configured with the QinQ tunnel is displayed.
portswitch
The interface is configured as a Layer 2 interface.

If the interface is a Layer 2 interface, this step is unnecessary.
Step 4 Run:
port link-type dot1q-tunnel
The interface type is configured as a QinQ interface.

Step 5 Run:
port default vlan vlan-id
The outer tag is configured; namely, the default VLAN ID of the interface is configured.
NOTE
The outer tag value should be the same as the VLAN ID created in Creating the Outer VLAN Tag for a
Layer 2 Interface.
----End
5.2.4 (Optional) Configuring the Protocol Type for the Outer Tag
To implement interworking between devices of different vendors, in the case that QinQ is
configured, devices of different vendors use 0x8100 as the value of the EType in the inner TPID
but use different values as the values of EType in the outer TPID. In addition, the protocol type
of the outer tag need be configured.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
qinq protocol ethertype-value
The protocol type of the outer tag is configured.
l IEEE 802.1ad defines the value of the EType field in the outer TPID to 0x88a8.
l The value of ethertype-value ranges from 0x0600 to 0xFFFF, and the default value is 0x8100.
NOTE
qinq protocol is applicable to only the packets with double tags.
----End
5.2.5 (Optional) Configuring the Protocol Type for the InnerTag

To enable devices of different manufacturers to communicate, you can configure the type of
Ethernet encapsulation for the inner tag of a double-tagged packet.
Do as follows on the device where the type of Ethernet encapsulation for the inner tag of a
double-tagged packet needs to be configured.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The view of the Ethernet interface or Eth-Trunk interface where the type of Ethernet
encapsulation for the inner tag of a double-tagged packet needs to be configured is displayed.
Step 3 Run:
qinq protocol ce-ethtype ce-ethtype
The specified type of Ethernet encapsulation for the inner tag of a packet is configured.
The value of ce-ethtype ranges from 0x0600 to 0xFFFF, and the default value is 0x8100.
----End

After a Layer 2 QinQ tunnel is successfully configured, you can view whether the VLAN is
enabled with the broadcast function, VLAN status, whether address learning is enabled, and
whether the configured Layer 2 QinQ tunnel interface is a QinQ stack interface.
Prerequisite
The configurations of the QinQ tunnel function are complete.

Procedure
l Run the display bpdu-tunnel interface config command to check the EthType
encapsulation value of the outer tag of the interface.
----End
Example
Running the display vlan command, you can view whether broadcast, VLAN status, and address
learning are enabled and view whether the interface configured with the QinQ tunnel function
is an untagged interface.
For example:
VLAN ID : 10
VLAN Type : Common
Status : Enable
Broadcast : Enable
----------------
Untagged Port: GigabitEthernet1/0/0
Running the display bpdu-tunnel interface config command, you can view the configuration
of TPID. For example:
[HUAWEI-GigabitEthernet1/0/1] display bpdu-tunnel interface config
BpduDot1qStatus disable
BpduOneQStatus disable
BpduTwoQStatus disable
EtherType 9100
Dot1qVlan
TwoQList
5.3 Configuring Selective QinQ on a Layer 2 Interface

This section describes how to configure Layer 2 selective QinQ. Thus, a packet with different
outer VLAN tags can be transmitted and the EthType in the outer VLAN tag can be flexibly
configured.

Before configuring Layer 2 selective QinQ, familiarize yourself with the applicable
Layer 2 selective QinQ is an extension of the QinQ tunnel. Layer 2 selective QinQ is more
flexible than the QinQ tunnel.
The major difference is as follows:

l QinQ tunnel
It attaches the same outer tag to all the frames entering the Layer 2 QinQ interface.
l Selective QinQ on the Layer 2 interface
It can attach different outer tags to the frames entering the Layer 2 QinQ interface according
to different inner tags.
Before configuring selective QinQ on a Layer 2 interface, complete the following tasks:
l Ensuring that the device is powered on correctly and operates properly.
l Configuring basic attributes of the Ethernet interface.
Data Preparation
To configure selective QinQ on a Layer 2 interface, you need the following data.
No. Data
1 ID of the outer VLAN tag
2 Interface number of the selective QinQ on the Layer 2 interface, ID of the inner VLAN
tag
3 (Optional) The protocol type for the outer tag
5.3.2 Creating the Outer VLAN Tag for a Layer 2 Interface

After a Layer 2 interface is configured with selective QinQ, different outer tags can be added to
packets and the EthType in QinQ tags can be flexibly configured.
Procedure
Step 1 Run:
system-view

Step 2 Run:
vlan vlan-id
A VLAN is created and its view is displayed.

The VLAN ID refers to the value of the outer tag specified in the QinQ tunnel function. The
VLAN ID ranges from 1 to 4094.
----End
5.3.3 Configuring Selective QinQ on a Layer 2 Interface

After selective QinQ is configured on a Layer 2 interface, the interface adds a public VLAN tag
to the user packet that carries a private VLAN tag so that the user packet can be forwarded on
the public network.

Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the Ethernet interface that need be configured with the Layer 2 selective QinQ is
displayed.
portswitch
The interface is configured as a Layer 2 interface.

Step 4 Perform either of the following operations as required.
l Run the port vlan-stacking vlan vlan-id1 [ to vlan-id2 ] stack-vlan vlan-id3 command to
configure the interface type as a Layer 2 selective QinQ interface.
– In this step, vlan-id1 and vlan-id2 specify the range of the inner tag of the frame received
by the interface; vlan-id3 is the value of the outer tag attached to the frame by the interface.
l Run the vlan-switch vlan-switch-name interface interface-type1 interface-number1 vlan
vlan-id1 [ to vlan-id2 ] interface interface-type2 interface-number2 [ stack-vlan vlan-id3 ]
to enable the VLAN Switch stack-vlan function, that is, add a VLAN tag to the existing
VLAN tag of frames received on a main Ethernet interface.
– The value of vlan-id2 must be equal to or greater than the value of vlan-id1. vlan-id2 and
vlan-id1 together specify a VLAN tag range.
– If the specified source interface or destination interface is of the access type, VLAN
Switch does not take effect because it supports only the interfaces of the hybrid or trunk
type.
----End
5.3.4 (Optional) Configuring the Protocol Type for the Outer Tag
To implement interworking between devices of different vendors, in the case that QinQ is
configured, devices of different vendors use 0x8100 as the value of the EType in the inner TPID
but use different values as the values of EType in the outer TPID. In addition, the protocol type
of the outer tag need be configured.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
qinq protocol ethertype-value
The protocol type of the outer tag is configured.
l IEEE 802.1ad defines the value of the EType field in the outer TPID to 0x88a8.
l The value of ethertype-value ranges from 0x0600 to 0xFFFF, and the default value is 0x8100.
NOTE
qinq protocol is applicable to only the packets with double tags.
----End
5.3.5 (Optional) Configuring the Protocol Type for the InnerTag

To enable devices of different manufacturers to communicate, you can configure the type of
Ethernet encapsulation for the inner tag of a double-tagged packet.
Do as follows on the device where the type of Ethernet encapsulation for the inner tag of a
double-tagged packet needs to be configured.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The view of the Ethernet interface or Eth-Trunk interface where the type of Ethernet
encapsulation for the inner tag of a double-tagged packet needs to be configured is displayed.
Step 3 Run:
qinq protocol ce-ethtype ce-ethtype
The specified type of Ethernet encapsulation for the inner tag of a packet is configured.
The value of ce-ethtype ranges from 0x0600 to 0xFFFF, and the default value is 0x8100.
----End

After Layer 2 selective QinQ is successfully configured, you can view whether the VLAN is
enabled with the broadcast function, VLAN status, whether address learning is enabled, and
whether the interface configured with the QinQ Layer 2 tunnel is a QinQ stack interface.
Prerequisite
The configurations of selective QinQ on a layer 2 interface are complete.
Procedure

l Run the display bpdu-tunnel interface config command to check the EthType
encapsulation value of the outer tag of the interface.
----End
Example
Run the display vlan command, and you can view whether broadcast, VLAN status, and address
learning are enabled and view whether the interface configured with the QinQ tunnel is a QinQ
stack interface. For example:
VLAN ID : 10
VLAN Type : Common
Status : Enable
Broadcast : Enable
----------------
QinQ-stack Port: GigabitEthernet1/0/0
Running the display bpdu-tunnel interface config command, you can view the configuration
of TPID. For example:
EtherType 9100
Dot1qVlan
TwoQList
5.4 Configuring the Sub-interface for VLAN Tag

Termination to Access the IP Service
IP services include proxy ARP, and DHCP services. You can deploy IP services on sub-
interfaces for VLAN tag termination to enable the interworking between users in different
VLANs, thus ensuring reliable, stable, and uninterrupted connections between the users and the
network.

Before configuring the sub-interface for VLAN tag termination to access the IP service,
obtain the required data. This helps you complete the configuration task quickly and accurately.
IP services are classified into the following types:
l Proxy ARP
The sub-interface for VLAN tag termination can connect different VLANs to the same
network segment. If users on the same network segment belong to different VLANs, they

cannot communicate with each other on the Layer 2 network unless the sub-interface for
VLAN tag termination supports ARP proxy and thus implements IP forwarding.
l DHCP
– The sub-interface for VLAN tag termination can be configured with the Dynamic Host
Configuration Protocol (DHCP) server function to assign IP addresses to users.
– The sub-interface for VLAN tag termination can be configured with the DHCP relay
function to provide reference for the DHCP server to assign IP addresses and parameters
by inserting tag information into Option82.
l VRRP
Users usually require communicating with certain networks at any time. In this case, The
Virtual Router Redundancy Protocol (VRRP) running on the sub-interface for VLAN tag
termination ensure a reliable communication and provides an active/standby mechanism
for dot1q or QinQ users.
NOTE
Proxy ARP, DHCP, and VRRP are different types of IP services, you can deploy one of them on the sub-
interface for VLAN tag termination as required.
Before configuring the sub-interface for VLAN tag termination to access the IP service, complete
the following tasks:
l Ensuring that devices are connected correctly
l Configuring the correct VLANs of users to enable the packets received by the sub-interface
for VLAN tag termination to carry one or double tags
Data Preparation
To configure the sub-interface for VLAN tag termination to access the IP service, you need the
following data.
No. Data
1 Control VLAN ID of the termination sub-interface
2 Range of the termination tag of the interface
3 Group number of the VRRP backup group and the virtual IP address
4 Priorities of the routers in the backup group
5 Preemption mode
6 IP addresses that are forbidden to assign
7 Number of the address pool

5.4.2 Configuring the Interface Mode as the User-Termination

Mode
You can run the dot1q-related or QinQ-related command on the sub-interface only when the
interface works in user-termination mode.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The view of the Ethernet interface receiving user packets is displayed.
Step 3 Run:
The mode of the Ethernet interface is configured as user-termination mode.
When this command is run on the main interface, ensure that no sub-interface is configured
under this main interface.
----End
5.4.3 Configuring the Sub-interface for dot1q VLAN Tag

Termination
The sub-interface that terminates a single tag is called the sub-interface for dot1q VLAN tag
termination.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface interface-type interface-number.subinterface-number
The Ethernet sub-interface view or the Eth-Trunk sub-interface view is displayed.
Step 3 Run:
control-vid vid dot1q-termination [ rt-protocol ]
The VLAN ID of the sub-interface for VLAN tag termination is set to terminate the packets with
one tag.
Step 4 (Optional) Create a user VLAN group.

1. Run the vlan-group group-id command to create a user VLAN group.

2. Run the quit command to return to the Ethernet sub-interface view or the Eth-Trunk sub-
interface view.
The purpose of configuring the VLAN group for the users is to apply different QoS policies to
different VLAN groups.
Step 5 Run:
dot1q termination vid low-pe-vid [ to high-pe-vid ] [ vlan-group group-id ]
The VLAN tag termination function is configured for the dotlq sub-interface.
----End
5.4.4 Configuring the Sub-interface for QinQ VLAN Tag

Termination
If the route sub-interface that terminates double tags is called a sub-interface for QinQ VLAN
tag termination.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
control-vid vid qinq-termination [ local-switch | [ rt-protocol | dynamic ] * ]
double tags.
interface view.
Step 5 Run:
qinq termination pe-vid pe-vid [ to high-pe-vid ] ce-vid { low-ce-vid [ to high-ce-
vid ] | any } [ vlan-group group-id ]
The sub-interface for VLAN tag termination is configured.
----End
5.4.5 Configuring the IP Service

After the sub-interface for VLAN tag termination is successfully configured, you need to
configure an IP service. In this manner, the user can access the IP service through the sub-
interface for VLAN tag termination.

Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the sub-interface for VLAN tag termination is displayed.

Step 3 Configure the IP service.
l Proxy ARP
Configure proxy ARP on the device. For detailed configuration, see the chapter "ARP
Configuration" in the HUAWEI NetEngine80E/40E Router Configuration Guide - IP
Services.
Enabling or disabling the ARP broadcast on the sub-interface makes the route status change
from Down to Up on the sub-interface. This may lead to route flapping on the entire network,
and even affect the running services.
l DHCP
Configure DHCP on the device. For detailed configuration, see the chapter "DHCP
Configuration" in the HUAWEI NetEngine80E/40E Router Configuration Guide - IP
Services.
On a rather large network, if the PCs are connected to a router through other devices instead
of being directly connected to the router through Ethernet interfaces, the DHCP server based
on a global address pool needs to be configured so that the PCs can dynamically obtain IP
addresses from the router.
If a local network does not have a DHCP server, the DHCP relay function can be enabled on
the router. In this manner, the DHCP Request packet from the client can be transmitted to
the DHCP server through the DHCP relay.
l VRRP
Configure VRRP on the device. For detailed configuration, see the chapter "VRRP
Configuration" in the HUAWEI NetEngine80E/40E Router Configuration Guide -
Reliability.
NOTE
When configuring VRRP and static ARP on the dot1q termination sub-interface, QinQ termination sub-
interface, or VLANIF interface at the same time, note the following:
l Do not configure the IP address mapping to the static ARP entry on the interface as the VRRP virtual
address.
l Do not configure the virtual address of the VRRP backup group where the interface resides as the IP
address mapping to the static ARP entry on the interface.
Otherwise, incorrect host routes are generated. This affects packet forwarding between devices.
----End

After successfully configuring the sub-interface for VLAN tag termination to access the IP
service, you can view detailed configurations on the sub-interface for VLAN tag termination.

Prerequisite
The configurations of the sub-interface for VLAN tag termination to access the IP service are
complete.
Procedure
l Run the display dot1q information termination [ interface interface-type interface-
number [.subinterface-number ] ] command to check information about the sub-interface
for dot1q VLAN tag termination.
l Run the display qinq information { termination | stacking | mapping } [ interface
interface-type interface-number [.subinterface-number ] ] command to check information
about the sub-interface for QinQ VLAN tag termination.
----End
Example
Run the display dot1q information termination on the PE, and you can view information about
the sub-interface for dot1q VLAN tag termination. For example:
<HUAWEI> display dot1q information termination interface gigabitethernet 2/0/0
Total QinQ Num: 1
dot1q termination vid 10 to 20 vlan-group 1
Total vlan-group Num: 1
vlan-group Num:1
Run the display qinq information termination command on the PE, and you can view
information about the sub-interface for QinQ VLAN tag termination. For example:
<HUAWEI> display qinq information termination interface gigabitethernet 2/0/0
Total QinQ Num: 1
qinq termination pe-vid 1000 ce-vid 100 to 200 vlan-group 1
vlan-group 1

Termination to Access the Multicast Service
With the wide use of multicast services on the Internet, you need to deploy sub-interfaces for
QinQ/dot1q VLAN tag termination to process the user packets carrying a single tag or double
tags for multicast services. In this manner, the UPE can maintain information about the outbound
interface of multicast packets according to the established multicast forwarding table to ensure
the normal communications between hosts and the multicast source.

Before configuring the sub-interface for VLAN tag termination to access the multicast service,
Multicast services are classified into the following types:

l Layer 2 multicast
After being bound to a VSI and enabled with IGMP snooping, the sub-interface for QinQ/
dot1q VLAN tag termination can listen IGMP messages exchanged between the multicast
device and hosts, and therefore can learn which interfaces have multicast receivers. In this
case, multicast packets are transmitted on the Layer 2 network in multicast mode rather
than broadcast mode, and consequently received only by members of the multicast group.
l Layer 3 multicast
Multicast protocol packets with double tags are sent from the UPE to the upper network.
After the sub-interface for QinQ or dot1q VLAN tag termination is configured on the UPE,
the UPE creates the forwarding table and the routing table. When receiving multicast
protocol packets from hosts, the UPE can identify the packets and correctly forward the
packets. Based on the established multicast forwarding table, the UPE can replicate and
deliver multicast packets correctly.
Here, Layer 3 multicast mainly refers to IGMP.
Before configuring the sub-interface for VLAN tag termination to access the multicast service,
l Ensuring that devices are correctly connected and that the physical interfaces of each device
are in the Up state.
Data Preparation
To configure the sub-interface for VLAN tag termination to access the multicast service, you
No. Data
3 IGMP version
4 Multicast group address and multicast source address
5 (Optional) ACL rules for the filtering based on multicast group addresses

Mode

Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
----End

Termination
termination.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
one tag.

interface view.
Step 5 Run:

----End

Termination
tag termination.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
double tags.

interface view.
Step 5 Run:
----End
5.5.5 Configuring the Multicast Service

After the sub-interface for VLAN tag termination is successfully configured, you need to
configure the multicast service. In this manner, users can communicate with the multicast source.
Procedure
Step 1 Run:
system-view

Step 2 Run:
Step 3 Configure the multicast service.
l Configure Layer 2 multicast.

For detailed information, see the chapter "Layer 2 Multicast Configuration" in the HUAWEI
NetEngine80E/40E Router Configuration Guide - IP Multicast.
Before configuring Layer 2 multicast, ensure that a VSI has been successfully set up and the
sub-interface for VLAN tag termination has been bound to the VSI; otherwise, Layer 2
multicast cannot be successfully configured.
l Configure Layer 3 multicast.
For detailed information, see the chapter "IGMP Configuration" in the HUAWEI
NetEngine80E/40E Router Configuration Guide - IP Multicast.
WARNING
Ensure that all IGMP device interfaces in the same network segment are configured with the
same IGMP version. Otherwise, a fault occurs.
----End

After successfully configuring the sub-interface for VLAN tag termination to access the
multicast service, you can view detailed configurations on the sub-interface for VLAN tag
termination.
Prerequisite
The configurations of the sub-interface for VLAN tag termination to access the multicast service
are complete.
Procedure
l Run the display igmp-snooping querier { vsi vsi-name | vlan vlan-id } command to check
whether the IGMP querier is configured successfully.
l Run the display igmp-snooping router-port { vsi vsi-name | vlan vlan-id } command to
check information about static router ports.

l Run the display igmp-snooping port-info [ { vlan vlan-id | vsi vsi-name | slot slot-id }
[ group-address group-address ] ] [ verbose ] command to check information about Layer
2 multicast ports on the router.
l Run the display igmp [ vpn-instance vpn-instance-name | all-instance ] interface
[ interface-type interface-number ] [ verbose ] command to check the configuration and
running of IGMP on an interface.
l Run the display igmp [ vpn-instance vpn-instance-name | all-instance ] group [ group-
address | interface interface-type interface-number ] [ verbose ]command to check
information about the members of an IGMP multicast group.
----End
Example
Total QinQ Num: 1
vlan-group Num:1
Total QinQ Num: 1
vlan-group 1
After the sub-interface for VLAN tag termination is successfully configured to access Layer 2
multicast:
l Run the display igmp-snooping querier vsi command. You can check whether the querier
is configured successfully. If the Enable state is displayed as shown in the following output,
it indicates that the querier is enabled for VSI v123. For example:
<HUAWEI> display igmp-snooping querier vsi v123
VSI Querier-state
-----------------------------------------------
v123 Enable
-----------------------------------------------
l Run the display igmp-snooping router-port vsi on PE1. You can check whether the
configuration of the static router port succeeds. If STATIC is displayed as shown in the
following output, it indicates that GE 1/0/0 is already configured as a static router port in
VSI V123. For example:
<HUAWEI> display igmp-snooping router-port vsi v123
Port Name UpTime Expires Flags
---------------------------------------------------------------------
VSI v123, 1 router-port(s)
GE1/0/1.1 00:01:48 -- STATIC
l Run the display igmp-snooping port-info command, You can check information about
Layer 2 multicast ports on the router, including SSM Mapping ports, static member ports,
and dynamic member ports.
<HUAWEI> display igmp-snooping port-info

-----------------------------------------------------------------------
(Source, Group) Port Flag
-----------------------------------------------------------------------
VSI v123, 1 Entry(s)
(1.1.1.1, 234.1.1.1) GE1/0/0.2(PE:20/CE:100) -D-
1 port(s)
-----------------------------------------------------------------------
<HUAWEI> display igmp-snooping port-info slot 1
-----------------------------------------------------------------------
-----------------------------------------------------------------------
(1.1.1.1, 234.1.1.1) P--
GE1/1/0.2(PE:20/CE:100) -D-
1 port(s) include
-----------------------------------------------------------------------
After the sub-interface for VLAN tag termination is successfully configured to access Layer 3
multicast:
l Run the display igmp group command. You can view information about multicast groups.
For example:
<PE1> display igmp group
Interface group report information of VPN-Instance: public net
GigabitGigabitethernet1/0/1.1(1.1.1.9):
Total 1 IGMP Group reported
Group Address Last Reporter Uptime Expires
226.0.0.1 192.168.0.1 00:00:03 00:02:07

Termination to Access the VPN Service
VPN services are classified into L2VPN services and L3VPN services. You can configure sub-
interfaces for VLAN tag termination on PEs to access VPNs to enable the interworking between
CEs and users.

Before configuring the sub-interface for VLAN tag termination to access the VPN service,
VPN services are classified into the following types:
l L2VPN
– PWE3/VLL
The access of the sub-interface for QinQ/dot1q VLAN tag termination to PWE3/VLL
means that the sub-interface for QinQ/dot1q VLAN tag termination is configured with
PWE3/VLL functions.
– VPLS
The support of VPLS by the sub-interface for QinQ/dot1q VLAN tag termination refers
to configuring VPLS on the sub-interface for VLAN tag termination.
l L3VPN

The access of the sub-interface for QinQ/dot1q VLAN tag termination to L3VPN means
that the sub-interface for QinQ/dot1q VLAN tag termination is configured with L3VPN
functions.
NOTE
When a sub-interface for dot1q VLAN tag termination accesses user services, if it is required to differentiate
the service types, you can deploy VLAN + 8021.p/DSCP/EthType on the device configured with the sub-
interface.
l Services can be differentiated according to the 8021.p/DSCP priority or the EthType. Services are
mapped to different VSIs according to their 8021.p/DSCP/EthType values, and then transmitted to the
peer.
l Services can be differentiated according to the 8021.p priority or the DSCP priority. Services are
mapped to different VSIs according to their 8021.p or DSCP priorities, and then transmitted to the peer.
Before configuring the sub-interface for VLAN tag termination to access the VPN service,
are in the Up state
Data Preparation
To configure the sub-interface for VLAN tag termination to access the VPN service, you need
the following data.
No. Data
3 IP address of the interface
4 The VC IDs of two PW ends (The two IDs must be the same), VSI names, MPLS
LSR-ID
5 The L2VC IDs of two PW ends (The two IDs must be the same), MPLS LSR-ID
6 Name of the VPN instances
7 RD and VPN target of the VPN instances
8 802.1p priorities, DSCP values, or EthType values

Mode

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:

----End

Termination
termination.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
one tag.
interface view.
Step 5 Run the following command as required.
l Run:

l Run:
dot1q termination vid low-pe-vid [ to high-pe-vid ] { 8021p { 8021p-value1
[ to 8021p-value2 ] } &<1-10> | dscp { dscp-value1 [ to dscp-value2 ] } &<1-10>
| eth-type eth-type-value | default } [ vlan-group group-id ]
The VLAN tag termination function and VLAN+802.1p/DSCP/EthType are configured for
the dotlq sub-interface.
NOTE
l When you run the dot1q termination vid low-pe-vid [ to high-pe-vid ] [vlan-group group-id ]
command on a sub-interface without specifying 8021p-value, dscp-value, or eth-type-value, it indicates
that the VLAN range is exclusively occupied by the sub-interface and thus any VLAN within this range
cannot be used in VLAN+802.1p/DSCP on other sub-interfaces.
l eth-type eth-type-value specifies the EthType. Currently, the EthType can be PPPoE or IPoE only.
To configure a sub-interface to process IPoE packets, you need to configure default when running the
dot1q termination vid low-pe-vid [ to high-pe-vid ] default.

arp broadcast enable
The ARP broadcast of the sub-interface for VLAN tag termination is enabled.
NOTE
This configuration takes effect only when a sub-interface for QinQ VLAN tag termination accesses an
L3VPN. So, after configuring a sub-interface for QinQ VLAN tag termination to access an L3VPN, you
must enable the ARP broadcast function on the sub-interface.
Enabling or disabling the ARP broadcast on the sub-interface makes the route status change
from Down to Up on the sub-interface. This may lead to route flapping on the entire network,
and even affect the running services.
----End

Termination
tag termination.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
double tags.


qinq termination l2 { symmetry | asymmetry }
The attributes of the sub-interface for QinQ VLAN tag termination are set.
NOTE
This configuration takes effect only when a sub-interface for QinQ VLAN tag termination accesses an
L2VPN. So, after configuring a sub-interface for QinQ VLAN tag termination, you must configure the
attributes of the sub-interface.
Sub-interfaces for QinQ termination access an L2VPN in symmetrical mode or in asymmetrical

mode. User packets access an L2VPN in different modes. PEs process these packets in the ways
described in the following tables.
Table 5-5 Packet processing on the inbound interface
Type of the Inbound VLL/PWE3/VPLS

Interface
Ethernet Encapsulation VLAN Encapsulation
Symmetrical Strips the outer tag. Reserves the double tags, and
no action is required.
Asymmetrical Strips the double tags. Strips two tag and then adds
one tags.
Table 5-6 Packet processing on the outbound interface
Type of the Outbound VLL/PWE3/VPLS

Interface
Ethernet Encapsulation VLAN Encapsulation
Symmetrical Adds the outer tag. Replaces the outer tag.
Asymmetrical Adds double tags. Strips one tag and then adds
double tags

interface view.
Step 6 Run:
----End

5.6.5 Configuring the VPN Service

After successfully configuring the sub-interface for VLAN tag termination, you need to
configure the VPN service. In this manner, users can communicate with each over an L2VPN
or an L3VPN.
Do as follows on the device that supports VPN services:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Configure the VPN service.
l L2VPN
VPN.
The sub-interface for QinQ VLAN tag termination can be bound to a homogeneous VLL in
the following modes:
The sub-interface for dot1q VLAN tag termination can be bound to a homogeneous VLL or
a heterogeneous VLL in the following modes:
– Remote Kompella remote connection
– Local Martini connection
The sub-interface for QinQ/dot1q VLAN tag termination can be bound to VPLS in the
following modes:
– Martini VPLS
– Kompella VPLS
l L3VPN

For detailed information, see the chapter "BGP MPLS IP VPN Configuration" in the
----End

After successfully configuring the sub-interface for VLAN tag termination to access the VPN
Prerequisite
The configurations of the sub-interface for VLAN tag termination to access the VPN service are
complete.
Procedure
l Run the display mpls l2vpn [ l2vpn-name [ local-ce | remote-ce ] ] command to check
information about the L2VPN on the PE.
l View the configuration of the L2VPN in CCC mode:
– Run the display vll ccc [ ccc-name | type { local | remote } ] command to check
information about the CCC connection.
– Run the display l2vpn ccc-interface vc-type ccc [ up | down ] command to check
information about the SVC interface in the Up or Down state.
l View the configuration of the L2VPN in SVC mode:
– Run the display mpls static-l2vc [ interface interface-type interface-number ]
command to check information about the SVC L2VPN connection.
– Run the display l2vpn ccc-interface vc-type static-vc { up | down } command to check
l View the configuration of the L2VPN in Martini mode:
– Run the display mpls l2vc [ vc-id | interface interface-type interface-number ]
command to check information about the Martini MPLS L2VPN connection on the PE.
– Run the display mpls l2vc remote-info [ vc-id ] command to check information about
the remote Martini MPLS L2VPN connection on the PE.
l View the configuration of the L2VPN in Kompella mode:
– Run the display bgp l2vpn { all | group [ group-name ] | peer [ [ ip-address ]
verbose ] | route-distinguisher route-distinguisher [ ce-id ce-id [ label-offset label-
offset ] ] } command to check BGP information about the Kompella MPLS L2VPN.
– Run the display mpls l2vpn connection [ vpn-name { remote-ce ce-id | down | up |
verbose } | summary | interface interface-type interface-number ] command to check
information about the Kompella MPLS L2VPN.

l Run the display interface interface-type interface-number vlan vlanid command to view
configurations of all sub-interfaces on a main interface.
----End
Example
Total QinQ Num: 1
vlan-group Num:1
Total QinQ Num: 1
vlan-group 1
l After VLL/PWE3 is successfully configured:

– Run the display vll ccc command, and you can find that the CCC VC status is Up. For
example:
<HUAWEI> display vll ccc
total ccc vc : 1
local ccc vc : 0, 0 up
remote ccc vc : 1, 1 up
name: ce2-ce1, type: remote, state: up,
intf: GigabitEthernet2/0/0 (up), in-label: 201 , out-label: 101 , out-
interface : GigabitEthernet1/0/0
– Run the display l2vpn ccc-interface vc-type ccc command, and you can find that the
VC type is CCC, and the CCC status is Up. For example:
<HUAWEI> display l2vpn ccc-interface vc-type all
Total ccc-interface of CCC VC: 1
up (1), down (0)
Interface Encap Type State VC Type
GigabitEthernet1/0/0 ppp up CCC
– Run the display mpls static-l2vc command, and you can find that the VC status is Up.
For example:
<HUAWEI> display mpls static-l2vc
Total svc connections: 1, 1 up, 0 down
*Client Interface : GigabitEthernet1/0/0 is up
AC Status : up
VC State : up
VC ID : 0
VC Type : ppp
Transmit VC Label : 100
Receive VC Label : 200
Control Word : Disable
VCCV Capability : Disable
Tunnel Policy Name : --
Traffic Behavior : --
PW Template Name : --
Create time : 0 days, 0 hours, 1 minutes, 38 seconds

UP time : 0 days, 0 hours, 1 minutes, 11 seconds

Last change time : 0 days, 0 hours, 1 minutes, 11 seconds
– Run the display l2vpn ccc-interface vc-type static-l2vc up command, and you can
find that the VC type is SVC, and the SVC status is Up. For example:
up (1), down (0)
GigabitEthernet1/0/0 ppp up SVC
Run the display mpls l2vc command, and you can find that "Destination" is the peer
address of the specified VC, and "VC State" is "up". For example:
<HUAWEI> display mpls l2vc
total LDP VC : 2 2 up 0 down
*client interface : GigabitEthernet2/0/0.1
session state : up
AC status : up
VC state : up
VC ID : 101
VC type : VLAN
control word : disable
forwarding entry : existent
local group ID : 0
link state : up
traffic behavior name: --
session state : up
AC status : up
VC state : up
VC ID : 102
VC type : VLAN
local group ID : 0
link state : up
– Run the display mpls l2vc remote-info command, and you can find that " Peer Addr"
is the peer address of the specified VC. For example:
<HUAWEI> display mpls l2vc remote-info
Total remote ldp vc : 1
Transport Group Peer Remote Remote C MTU/
N S
VC ID ID Addr Encap VC Label Bit CELLS
Bit Bit

100 0 3.3.3.9 vlan 17408 0 1500

1 0
– Run the display bgp l2vpn command, and you can find "Destination" is the peer address
of the VC, "route-distinguisher" of the L2VPN is correctly configured, and the label is
assigned to the peer device. For example:
<HUAWEI> display bgp l2vpn all
BGP Local router ID : 2.2.2.9, local AS number : 100
Origin codes:i - IGP, e - EGP, ? - incomplete
bgp.l2vpn: 1 destination
Route Distinguisher: 100:1
CE ID Label Offset Label Base nexthop pref as-path
4 0 132096 3.3.3.9 100
– Run the display mpls l2vpn connection command, and you can find "VPN name" is
correctly configured, the connection status is Up, and "route-distinguisher" is correctly
configured. For example:
[HUAWEI] display mpls l2vpn connection
1 total connections,
connections: 1 up, 0 down, 0 local, 1 remote, 0 unknown
VPN name: vpn1,
CE name: ce1, id: 1,
Rid type status peer-id route-distinguisher intf
2 rmt up 3.3.3.9 100:1 GigabitEthernet1/0/0
– Run the display mpls l2vpn command on the PE, and you can view the detailed
configurations of the L2VPN. For example:
# Check the configurations of all the L2VPNs on the PE.
<HUAWEI> display mpls l2vpn
VPN number: 1
vpn-name encap-type route-distinguisher mtu ce(L) ce(R)
vpn1 ppp 100:1 128 1 1
l After VPLS is successfully configured:

Run the display vsi [ name vsi-name ] [ verbose ] command. From the display, you can
see that the "VSI State" item is "up". If you choose the parameter verbose, the "PW
Signaling" item is " ldp ", and the "VSI State" item is "up". For example:
<HUAWEI> display vsi name vsi1 verbose
***VSI Name : vsi1
VSI Index : 0
PW Signaling : ldp
MTU : 1500
Mode : uniform
Service Class : --
Color : --
DomainId : 0
Domain Name :
VSI State : up
VSI ID : 2
VC Label : 142336
Peer Type : dynamic
Session : up
Tunnel ID : 0x80800b,
VC Label : 142337
Peer Type : dynamic
Session : up
Tunnel ID : 0x608006,


State : up
**PW Information:
PW State : up
PW Type : label
PW State : up
PW Type : label
l After the L2VPN is successfully configured:

Run the display ip vpn-instance verbose [ vpn-instance-name ] command. The details
about the VPN instances created on the local device are displayed. The details cover the
creation date, the time being in the Up status, the RD value, VPN target and the policy used
to assign the labels.
<HUAWEI> display ip vpn-instance verbose
Create date : 2006/06/06 16:30:22
Label policy : label per route
The ttl-mode Information is : uniform
Run the display interface vlan command, and you can view the configurations of all sub-
interfaces on a main interface. For example:
<HUAWEI> display interface GigabitEthernet1/0/1 vlan 1
-----------------------------------------------------------
GE1/0/1.6 DSCP 10
GE1/0/1.5 default
GE1/0/1.4 8021p 2 to 5 7
-----------------------------------------------------------

Termination to Access the MPLS Service
The sub-interface for VLAN tag termination to access the MPLS service are classified into the
following types of MPLS LDP service and MPLS TE service.

Before configuring the sub-interface for VLAN tag termination to access the MPLS service,
MPLS services are classified into the following types:

l MPLS LDP service

l MPLS TE service
NOTE
l Only the VLL PW over TE and the VLL PW over LDP are supported, and the VLL PW over TE FRR
or the VLL PW over LDP over TE is not supported.
l For the VLL PW over TE, only an RSVP-TE tunnel is supported, and only IS-IS TE rather than OSPF
TE can be adopted.
l Only the sub-interfaces for Dot1q termination and QinQ termination, rather than QinQ stacking sub-
interfaces, support the preceding services.
Before configuring the sub-interface for VLAN tag termination to access the MPLS service,
are in the Up state
Data Preparation
To configure the sub-interface for VLAN tag termination to access the MPLS service, you need
the following data.
No. Data
3 IP address of the interface

Mode
Procedure
Step 1 Run:
system-view
Step 2 Run:

Step 3 Run:
----End

Termination
termination.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
one tag.

interface view.
Step 5 Run:
----End

Termination
tag termination.

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
double tags.
interface view.
Step 5 Run:
----End
5.7.5 Configuring the MPLS Service

After successfully configuring the sub-interface for VLAN tag termination, you need to
configure the MPLS service. In this manner, users can communicate with each over.
Context
Do as follows on the device that supports MPLS services:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Configure the MPLS service.

l MPLS LDP
For detailed information, see the chapters "MPLS LDP Configuration" in the HUAWEI
NetEngine80E/40E Router Configuration Guide - MPLS.
l MPLS TE
For detailed information, see the chapter "MPLS TE Configuration" in the HUAWEI
NetEngine80E/40E Router Configuration Guide - MPLS.
----End

After successfully configuring the sub-interface for VLAN tag termination to access the MPLS
Prerequisite
The configurations of the sub-interface for VLAN tag termination to access the MPLS service
are complete.
Procedure
l Run display mpls interface [ interface-type interface-number ] [ verbose ] command to
check information about an interface enabled with MPLS.
l Run display mpls ldp [ all ] [ verbose ] command to check information about LDP.
l Run the display mpls rsvp-te [ interface interface-type interface-number ] command to
check information about RSVP.
l Run the display mpls te tunnel [ destination ip-address ] [ lsp-id lsr-id session-id lsp-
id | lsr-role { all | egress | ingress | remote | transit } ] [ name tunnel-name ] [ { incoming-
interface | interface | outgoing-interface } interface-type interface-number ] [ verbose ]
command to check the tunnel information.
----End
5.8 Configuring the Sub-interface for QinQ VLAN Tag

Termination to Support 802.1p Mapping
After tags are terminated on PEs, packets are sent to the IP or MPLS network of the ISP. To
ensure the completeness of the QoS information in the packets, the 802.1p values in outer and
inner tags need to be mapped to the DSCP field or the EXP field.

Before configuring the sub-interface for QinQ VLAN tag termination to support 802.1p
mapping, familiarize yourself with the applicable environment, complete the pre-configuration
tasks, and obtain the required data. This can help you complete the configuration task quickly
and accurately.
l QinQ Termination Supports the 802.1p Remark and DSCP Remark

According to RFC 2724, six bits of the Type of Service (ToS) field in an IPv4 packet header
serve as the DiffServ Code Point (DSCP), which provides reference for differentiated
services (DiffServ) and is used to ensure the Quality of Service (QoS) on the IP network.
The operation of the traffic controller on the gateway depends on the DSCP field.
After being terminated on the PE, the packet is sent to the ISP network. To ensure the
completeness of the QoS information in the packet, the mapping relationship between the
802.1p values in outer and inner tags and the DSCP field needs to be configured.
l QinQ Termination Supports the 802.1p Remark and EXP (MPLS) Remark
The EXP field in an MPLS packet is used for Class of Service (CoS). The operation of the
traffic controller on the gateway depends on the field.
After a user packet is terminated, it is sent to the ISP MPLS network. To ensure the
completeness of the QoS information in the packet, the mapping relationship between the
802.1p values in outer and inner tags and the EXP field needs to be configured.
mapping, complete the following tasks:
are in the Up state
for VLAN tag termination to carry double tags
Data Preparation
mapping, complete the following tasks:
No. Data
3 802.1p priorities of the outer and inner tags

Mode
Procedure
Step 1 Run:
system-view

Step 2 Run:
Step 3 Run:
----End

Termination to Support 802.1p Mapping
A specific 802.1p priority in packets can be mapped to the DSCP or EXP field only after the
sub-interface for QinQ VLAN tag termination is successfully configured with 802.1p mapping.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The view of the Ethernet sub-interface on the PE connecting to users is displayed.
Step 3 Run:
double tags.
Step 4 Run:
Step 5 Run:
qinq 8021p-mode { trust { ce-vid-8021p | pe-vid-8021p } | precedence-value }
802.1p mapping is configured.
By default, the sub-interface for QinQ VLAN tag termination trusts the 802.1p priority in the
outer tag. That is, before qinq 8021p-mode is configured on the sub-interface, the sub-interface
implements QoS policies according to the 802.1p priority in the outer tag of the received packets.
----End


After successfully configuring the sub-interface for QinQ VLAN tag termination to support
802.1p mapping, you can view the detailed configurations on the sub-interface.
Prerequisite
The configurations of sub-interface for QinQ VLAN tag termination to support 802.1p mapping
are complete.
Procedure
----End
Example
GigabitEthernet 2/0/0.1
qinq 8021p-mode trust ce-vid-8021p
Total QinQ Num: 1
5.9 Configuring the Sub-interface for QinQ Stacking to

Access an L2VPN
You can configure sub-interfaces for QinQ stacking on PEs to access L2VPNs so that the inner
tags of user packets are invisible on the ISP network.

Before configuring the Sub-interface for VLAN stacking to access L2VPN, familiarize yourself
with the applicable environment, complete the pre-configuration tasks, and obtain the required
data. This helps you complete the configuration task quickly and accurately.
The packet of the user that accesses the CE has one tag. The CE accesses the ISP network through
PEs.
It is required to configure a VLL or PWE3 on the PE for the sub-interface for VLAN stacking.
In this way, the user VLAN tags can be transparently transmitted on the ISP network, and the
user networks connected to the CEs can communicate.
To enable the PE to add an outer VLAN tag to received single-tagged packets, you can configure
QinQ stacking+802.1p/DSCP/EthType on the PE. Then, each packet entering an Ethernet sub-
interface is attached with an outer VLAN tag based on the matching policy.

Before configuring the sub-interface for VLAN stacking to access L2VPN, complete the
following tasks:
l Connecting devices correctly

l Configuring the VLAN of the CE and the basic Layer 2 forwarding function to make the
packets sent from the CE to the PE carry one tag
Data Preparation
To configure the sub-interface for VLAN stacking to access L2VPN, you need the following
data.
No. Data
1 Name of the PE interface connected to the CE
2 The VC IDs of two PW ends (The two IDs must be the same)
3 MPLS LSR ID of each PE and P
4 The IP address for the remote peer of the PE
5 802.1p priorities, DSCP values, or EthTypes

Mode
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
----End

5.9.3 Configuring the Sub-interface for VLAN Stacking

If a physical interface is used to access user packets, the interface can only access packets of a
single user. In this case, you can bind sub-interfaces for QinQ stacking to VSIs or L2VCs to
access an L2VPN so that a physical interface can simultaneously access packets of multiple
users.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the Ethernet sub-interface on the PE connecting to users is displayed.

interface view.
Step 4 Run the following command as required.
l Run:
qinq stacking vid low-ce-vid [ to high-ce-vid ] [ vlan-group group-id ]
User packets with VLAN IDs within the specified range are attached with an outer VLAN
tag and QinQ stacking is configured to transparently transmit the user packets.
User packets received on Ethernet sub-interface can carry a single VLAN tag or double
VLAN tags. If an Ethernet sub-interface receives an untagged packet or a packet whose outer
VLAN VLAN tag is not the user VLAN tag, the Ethernet sub-interface discards the packet.
When running the qinq stacking vid command on different sub-interfaces of a main
interface, the values of ce-vid cannot overlap.
l Run:
qinq stacking vid low-ce-vid [ to high-ce-vid ] { 8021p { 8021p-value1 [ to 8021p-
value2 ] } &<1-10> | dscp { dscp-value1 [ to dscp-value2 ] } &<1-10> | eth-type
eth-type-value | default }
User packets received on Ethernet sub-interfaces are attached with an outer VLAN tag based
on the matching policy. The matching policy can be VLAN+802.1p, VLAN+DSCP, or
VLAN+EthType.

NOTE
l When you run the qinq stacking vid low-ce-vid [ to high-ce-vid ] [vlan-group group-id]command on
a sub-interface without configuring default or specifying 8021p-value, dscp-value, or eth-type-value,
it indicates that the VLAN range is exclusively occupied by the sub-interface and thus any VLAN
within this range cannot be used in VLAN+802.1p/DSCP/EthType on other sub-interfaces.
l eth-type eth-type-value specifies the EthType. Currently, the EthType can be PPPoE or IPoE only.
To configure a sub-interface to process IPoE packets, you need to configure default when running the
qinq stacking vid low-ce-vid [ to high-ce-vid ] default command. When default is configured, it
indicates that all services from the VLAN are processed on the default sub-interface except that the
services configured with the matching policy are processed on the corresponding sub-interface as
specified in the matching policy.
----End
5.9.4 Configuring the L2VPN

L2VPNs includes VLL, PWE3, and VPLS networks. A VLL simulates the traditional leased
line on the IP network, and provides asymmetric and low-cost digital data network (DDN)
services. The VLL is a point-to-point virtual private wire technology that can support almost all
the link layer protocols. PWE3 is an implementation mode of the VLL and the extension of the
Martini protocol. PWE3 extends the new signaling, reduces the cost of signaling, and defines
the multi-hop negotiation mode. This makes the networking more flexible. The VPLS
technology realizes a multipoint-to-multipoint VPN networking. Through this technology, the
ISP can provide Ethernet-based multipoint-to-multipoint services for users through an MPLS
backbone network.
Do as follows on the device that needs to be configured with an L2VPN.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of a sub-interface for QinQ stacking is displayed.

Step 3 Configure the L2VPN.
VPN.
l A sub-interface for QinQ stacking can be configured with various VLL connections,
including:


l A sub-interface for QinQ stacking can be configured with various VPLS connections,
including:
– Martini VPLS
– Kompella VPLS
----End

After successfully configuring the sub-interface for QinQ stacking to access an L2VPN, you can
view detailed configurations on the sub-interface.
Prerequisite
The configurations of the sub-interface for QinQ stacking to access an L2VPN are complete.
Procedure
l Run the display qinq information stacking [ interface interface-type interface-number
[.subinterface-number ] ] command to check QinQ stacking information.
l Run the display mpls l2vpn [ l2vpn-name [ local-ce | remote-ce ] ] command to check
information about the L2VPN on the PE.
l View the configuration of the L2VPN in CCC mode:
– Run the display vll ccc [ ccc-name | type { local | remote } ] command to check
information about the CCC connection.
– Run the display l2vpn ccc-interface vc-type ccc [ up | down ] command to check
l View the configuration of the L2VPN in SVC mode:
– Run the display mpls static-l2vc [ interface interface-type interface-number ]
command to check information about the SVC L2VPN connection.
– Run the display l2vpn ccc-interface vc-type static-vc { up | down } command to check
l View the configuration of the L2VPN in Martini mode:
– Run the display mpls l2vc [ vc-id | interface interface-type interface-number ]
command to check information about the Martini MPLS L2VPN connection on the PE.
– Run the display mpls l2vc remote-info [ vc-id ] command to check information about
the remote Martini MPLS L2VPN connection on the PE.
l View the configuration of the L2VPN in Kompella mode:
– Run the display bgp l2vpn { all | group [ group-name ] | peer [ [ ip-address ]
verbose ] | route-distinguisher route-distinguisher [ ce-id ce-id [ label-offset label-
offset ] ] } command to check BGP information about the Kompella MPLS L2VPN.
– Run the display mpls l2vpn connection [ vpn-name { remote-ce ce-id | down | up |
verbose } | summary | interface interface-type interface-number ] command to check
information about the Kompella MPLS L2VPN.
l Run the display interface interface-type interface-number vlan vlanid command to view
configurations of all sub-interfaces on a main interface.
----End

Example
Run the display qinq information stacking command on the PE. The details about the sub-
interface for VLAN stacking are displayed. For example:
<HUAWEI> display qinq information stacking interface gigabitethernet 1/0/1
VLL/PWE3 bound
Total QinQ Num: 2
qinq stacking vid 100 vlan-group 1
qinq stacking vid 200 vlan-group 1
vlan-group 1
l After VLL/PWE3 is successfully configured:

– Run the display vll ccc command, and you can find that the CCC VC status is Up. For
example:
<HUAWEI> display vll ccc
total ccc vc : 1
local ccc vc : 0, 0 up
remote ccc vc : 1, 1 up
name: ce2-ce1, type: remote, state: up,
intf: GigabitEthernet2/0/0 (up), in-label: 201 , out-label: 101 , out-
interface : GigabitEthernet1/0/0
– Run the display l2vpn ccc-interface vc-type ccc command, and you can find that the
VC type is CCC, and the CCC status is Up. For example:
up (1), down (0)
GigabitEthernet1/0/0 ppp up CCC
– Run the display mpls static-l2vc command, and you can find that the VC status is Up.
For example:
<HUAWEI> display mpls static-l2vc
Total svc connections: 1, 1 up, 0 down
*Client Interface : GigabitEthernet1/0/0 is up
AC Status : up
VC State : up
VC ID : 0
VC Type : ppp
Transmit VC Label : 100
Receive VC Label : 200
VCCV Capability : Disable
Traffic Behavior : --
– Run the display l2vpn ccc-interface vc-type static-l2vc up command, and you can
find that the VC type is SVC, and the SVC status is Up. For example:
up (1), down (0)
GigabitEthernet1/0/0 ppp up SVC
Run the display mpls l2vc command, and you can find that "Destination" is the peer
address of the specified VC, and "VC State" is "up". For example:
<HUAWEI> display mpls l2vc


session state : up
AC status : up
VC state : up
VC ID : 101
VC type : VLAN
local group ID : 0
link state : up
session state : up
AC status : up
VC state : up
VC ID : 102
VC type : VLAN
local group ID : 0
link state : up
– Run the display mpls l2vc remote-info command, and you can find that " Peer Addr"
is the peer address of the specified VC. For example:
<HUAWEI> display mpls l2vc remote-info
Total remote ldp vc : 1
Transport Group Peer Remote Remote C MTU/
N S
VC ID ID Addr Encap VC Label Bit CELLS
Bit Bit
100 0 3.3.3.9 vlan 17408 0 1500
1 0
– Run the display bgp l2vpn command, and you can find "Destination" is the peer address
of the VC, "route-distinguisher" of the L2VPN is correctly configured, and the label is
assigned to the peer device. For example:
<HUAWEI> display bgp l2vpn all
BGP Local router ID : 2.2.2.9, local AS number : 100
Origin codes:i - IGP, e - EGP, ? - incomplete
bgp.l2vpn: 1 destination
Route Distinguisher: 100:1
CE ID Label Offset Label Base nexthop pref as-path
4 0 132096 3.3.3.9 100

– Run the display mpls l2vpn connection command, and you can find "VPN name" is
correctly configured, the connection status is Up, and "route-distinguisher" is correctly
configured. For example:
[HUAWEI] display mpls l2vpn connection
VPN name: vpn1,
CE name: ce1, id: 1,
Rid type status peer-id route-distinguisher intf
2 rmt up 3.3.3.9 100:1 GigabitEthernet1/0/0
– Run the display mpls l2vpn command on the PE, and you can view the detailed
configurations of the L2VPN. For example:
# Check the configurations of all the L2VPNs on the PE.
<HUAWEI> display mpls l2vpn
VPN number: 1
vpn-name encap-type route-distinguisher mtu ce(L) ce(R)
vpn1 ppp 100:1 128 1 1
l After VPLS is successfully configured:

Run the display vsi [ name vsi-name ] [ verbose ] command. From the display, you can
see that the "VSI State" item is "up". If you choose the parameter verbose, the "PW
Signaling" item is " ldp ", and the "VSI State" item is "up". For example:
<HUAWEI> display vsi name vsi1 verbose
***VSI Name : vsi1
VSI Index : 0
PW Signaling : ldp
MTU : 1500
Mode : uniform
Service Class : --
Color : --
DomainId : 0
Domain Name :
VSI State : up
VSI ID : 2
VC Label : 142336
Peer Type : dynamic
Session : up
VC Label : 142337
Peer Type : dynamic
Session : up
State : up
**PW Information:
PW State : up
PW Type : label
PW State : up
PW Type : label

l After the L2VPN is successfully configured:

Run the display ip vpn-instance verbose [ vpn-instance-name ] command. The details
about the VPN instances created on the local device are displayed. The details cover the
creation date, the time being in the Up status, the RD value, VPN target and the policy used
to assign the labels.
<HUAWEI> display ip vpn-instance verbose
Create date : 2006/06/06 16:30:22
Run the display interface vlan command, and you can view the configurations of all sub-
interfaces on a main interface. For example:
<HUAWEI> display interface GigabitEthernet1/0/1 vlan 1
-----------------------------------------------------------
GE1/0/1.6 DSCP 10
GE1/0/1.5 default
GE1/0/1.4 8021p 2 to 5 7
-----------------------------------------------------------
5.10 Configuring Dynamic QinQ

Dynamic QinQ is configured on the sub-interface for VLAN tag termination of the DHCP relay
at the client side to allocate VLAN tag resources for login users. When a user abnormally logs
out after obtaining an IP address, the system can sense the event automatically, delete the binding
in the DHCP binding table, and instruct the DHCP server to release the IP address and VLAN
tag resources.

Before configuring dynamic QinQ, familiarize yourself with the applicable environment,
complete the pre-configuration tasks, and obtain the required data. This helps you complete the
A common sub-interface for QinQ termination can terminate a maximum of 16,000 double-
tagged user packets. When the number of the user packets exceeds 16,000, you can use the
dynamic QinQ function. After that, the sub-interface for QinQ aggregation can terminate a
maximum of 64,000 double-tagged user packets.
Dynamic QinQ is configured on the sub-interface for VLAN tag termination on the client side
of the DHCP relay to allocate VLAN tags to the login users. After ARP is associated with the
DHCP binding table, when users log out abnormally after obtaining IP addresses, the system
senses this failure automatically, and then deletes the binding relationship in the DHCP binding
table and informs the DHCP server to release IP addresses and VLAN tags.

Before configuring dynamic QinQ, complete the following tasks:
l Connecting devices correctly
for VLAN tag termination to carry double tags
Data Preparation
To configure dynamic QinQ, you need the following data.
No. Data
1 IP address of the interface to be configured with DHCP relay
2 Address pool range of the DHCP server
3 Tag values of the sub-interface for QinQ VLAN tag termination
4 Rate at which DHCP messages are sent to the CPU
5 Threshold for sending alarms to the NMS

Mode
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:

----End
5.10.3 Configuring Dynamic QinQ

An ordinary sub-interface for QinQ VLAN tag termination can be configured to terminate user
packets with a maximum of 16 K combinations of inner and outer tags. If the number of

combinations of inner and outer tags exceeds 16 K, you can configure dynamic QinQ. In this
manner, the sub-interface for QinQ VLAN tag termination can terminate user packets with a
maximum of 32 K combinations of inner and outer tags on each board.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
control-vid vid qinq-termination dynamic
Configures the sub-interface to support dynamic QinQ.

Step 4 Run:
qinq-dynamic max-access-user access-user-number
Dynamic QinQ resources are pre-allocated.

Step 5 Run:
qinq-dynamic user-queue queue-number bandwidth bandwidth { inbound | outbound }
The QinQ dynamic bandwidth CIR resources are pre-allocated.
NOTE
In the case of interfaces configured with dynamic QinQ, usually it is users who send the ARP request
actively to the gateway device; if ARP rigid learning is also configured on the device, all interfaces on the
device learn the responses to the ARP requests that are actively sent by themselves instead of learning the
requests sent by other devices. As a result, dynamic QinQ interfaces on this device cannot learn ARP entries
of users and then users fail to log in. To solve the problem, you can run the arp learning strict force-
disable command on the interface configured with dynamic QinQ so that the interface can learn the ARP
requests sent by users.
Step 6 Run:
----End
5.10.4 Configuring DHCP Snooping

As a DHCP security feature, Dynamic Host Configuration Protocol (DHCP) snooping filters
out untrusted DHCP messages, and creates and maintains a DHCP snooping binding table. The
binding table contains the MAC address, IP address, lease, binding type, VLAN ID, and interface
information. DHCP snooping acts as a firewall between DHCP clients and a DHCP server.
Procedure
Step 1 Run:

system-view

Step 2 Run:
The view of a sub-interface for QinQ VLAN tag termination is displayed.

Step 3 Configure DHCP snooping.
For detailed information, see the chapter "DHCP Snooping Configuration" in the HUAWEI
NetEngine80E/40E Router Configuration Guide - Security.
NOTE
l On the DHCP relay, you need to use the dhcp option82 insert enable command or the dhcp option82
rebuild enable command to enable the sub-interface for QinQ VLAN tag termination to insert the
Option 82 field into the DHCP message.
If the QinQ sub-interface is not configured with Option 82, when accessing the DHCP relay service,
the QinQ sub-interface encapsulates all the DHCP messages received from the DHCP relay with only
the smallest VLAN ID configured on it and sends the messages to the client side. The other VLAN
IDs are not processed.
l The DHCP server must support the Option82 return function. Namely, the Offer or ACK message
returned from the DHCP server must contain the Option82 information.
l Run the arp learning strict force-disable command to unfetter the dynamic QinQ interface from
global ARP rigid learning so that the dynamic QinQ interface can learn the ARP request sent by users.
----End

After successfully configuring dynamic QinQ, you can view the detailed configurations on the
sub-interface for QinQ VLAN tag termination.
Prerequisite
The configurations of dynamic QinQ are complete.
Procedure
l Run the display dhcp snooping global command to check information about DHCP
snooping.
----End
Example
Total QinQ Num: 1
vlan-group 1

Running the display dhcp snooping global command on the DHCP relay, you can find that
DHCP snooping is enabled in the global view and interface view. In addition, you can view the
statistics of the alarm message sent to the NMS.
<DHCP-Relay> display dhcp snooping global
dhcp snooping enable
dhcp snooping nomatch-packet ip action discard
dhcp snooping nomatch-packet arp action discard
dhcp snooping check dhcp-rate enable
dhcp snooping check dhcp-rate alarm enable
dhcp snooping check dhcp-rate 90
dhcp snooping check dhcp-rate alarm threshold 40
5.11 Configuring the Sub-interface for QinQ VLAN Tag

Termination to Support URPF
Configuring sub-interfaces for QinQ VLAN tag termination to support Unicast Reverse Path
Forwarding (URPF) effectively prevents attacks based on source address spoofing through sub-
interfaces for QinQ VLAN tag termination.

Before configuring sub-interfaces for QinQ VLAN tag termination to support URPF, familiarize
On the ISP network, a router may receive the packet with the spoofing source address. In this
case, you need to configure URPF on the relevant interface to avoid the attacks based on the
source address spoofing.
When a router receives a packet with double tags, you need to apply URPF on the sub-interface
for QinQ VLAN tag termination.
Before configuring the sub-interface for QinQ VLAN tag termination to support URPF,
l Configuring the physical parameters of the interface

l Configuring the link protocol of the interface
l Assigning the IP address to the interface
Data Preparation
To configure the sub-interface for QinQ VLAN tag termination to support URPF, you need the
following data.
No. Data
1 The number of QinQ interface which to be configured with URPF

No. Data
2 Termination range of the sub-interface for QinQ VLAN tag termination
5.11.2 Configuring the Ethernet Interface of the PE

You can use QinQ configuration commands on sub-interfaces only when the main interface
works in user termination mode.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
----End
5.11.3 Configuring the Ethernet Sub-interface of the PE

For a sub-interface for QinQ VLAN tag termination, you need to configure double tags that are
carried in a user packet and can be terminated by the sub-interface.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface { gigabitethernet | eth-trunk } interface-number.subinterface-number
The Ethernet sub-interface view is displayed.

Step 3 Run:

control-vid vid qinq-termination [ local-switch | [ rt-protocol | flexible ] * ]
The VLAN ID of the sub-interface for VLAN tag termination is set to terminate the user packets
with double tags.
Step 4 Run:
qinq termination pe-vid pe-vid ce-vid low-ce-vid [ to high-ce-vid ]
The VLAN tag termination function is configured for the sub-interface.
----End
5.11.4 Configuring URPF on the Sub-interface for QinQ VLAN Tag

Termination
Sub-interfaces for VLAN tag termination on the NE80E/40E support the loose URPF check
only.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface { gigabitethernet | eth-trunk } interface-number.subinterface-number
The sub-interface for QinQ VLAN tag termination view is displayed.

Step 3 Run:
ip urpf loose [ allow-default ]
URPF is enabled. That is, the IP address must be in the FIB but the interface may not be matched.
----End

After sub-interfaces for QinQ VLAN tag termination are configured to support URPF, the
NE80E/40E can effectively defend itself against network attacks with bogus source IP addresses.
Procedure
Step 1 Run the display qinq information termination [ interface interface-type interface-number
[.subinterface-number ] ] command to display the information of QinQ termination.
----End
Example
Run the display qinq information termination command on PE. The details about the sub-
interface for QinQ termination are displayed. For example:

# Display the information on the sub-interface for QinQ termination.

Total QINQ Num: 1
5.12 Configuring the User-Side QinQ

When configuring a user VLAN on an Ethernet sub-interface, you can specify either the start
and end VLAN IDs or the start and end QinQ VLAN IDs. Note that a maximum of 16 consecutive
QinQ VLAN IDs can be specified in a command. When the NE80E/40E is connected to users
through two switches, the switch adjacent to users adds an inner tag to a user packet (or remove
the inner tag from the user packet) and the switch adjacent to the NE80E/40E adds an outer tag
to the user packet (or remove the outer tag from the user packet).
NOTE
User-Side QinQ cannot be configured on the X1 and X2 models of the NE80E/40E.

Before configuring QinQ functions at the user side of the BRAS, familiarize yourself with the
When the number of VLANs on an interface is more than 4000, you should configure QinQ to
expand the VLAN capacity.
Before configuring the user-side QinQ, complete the following tasks:
l Setting the physical parameters of the relevant interfaces
l Configuring the IP addresses and BRAS attributes of the relevant interfaces
Data Preparation
To configure the user-side QinQ, you need the following data.
No. Data
1 QinQ ID
2 Sub-interface number
5.12.2 Creating a User-Side VLAN

When a Layer 2 common user accesses the device through an Ethernet sub-interface, configuring
a user-side VLAN is necessary.

Context
Do as follows on the NE80E/40E:
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface interface-type interface-number.sub-interface-nmuber
The sub-interface view is displayed.
Step 3 Run:
user-vlan { start-vlan-id [ end-vlan-id ] [ qinq start-qinq-id end-qinq-id ] | any-
other }
The user-side VLAN is created on the sub-interface.
When configuring user-side VLANs on an Ethernet sub-interface, you can specify a VLAN
range by setting start-vlan and end-vlan or specify all other VLANs by setting any-other
(containing all the VLANs that are not used by other sub-interfaces in 4094 x 4094 VLANs for
double-tag encapsulation and 4094 VLANs for one-tag encapsulation). If some VLANs are
being used by other sub-interfaces, the any-other parameter does not take effect to these VLANs.
When configuring user-side VLANs on an Ethernet sub-interface, you can also specify QinQ
VLANs. Two LAN switches are connected to the NE80E/40E. The packets of the LAN switch
close to the user are tagged with inner VLAN IDs (start-vlan-id), and the packets of the upper
LAN switch are tagged with outer QinQ VLAN IDs (qinq-id). For details, see QinQ
Configuration.
By default, no user-side VLAN is configured on the Ethernet sub-interface.
----End

After QinQ functions are configured for a sub-interface at the user side of the BRAS, users can
access the network through the sub-interface.
Context
Run the following command in the sub-interface view to check the previous configuration.
Action Command
Check the QinQ configuration on display this

the sub-interface.

5.13 Maintaining QinQ

Commands of clearing statistics on a QinQ interface helps to locate the faults on a QinQ interface.
5.13.1 Clearing QinQ Statistics

You can run the reset command to clear the QinQ statistics before recollecting QinQ statistics.
Context
CAUTION
Statistics about QinQ packets cannot be restored after you clear it. So, confirm the action before
you use the command.
To clear the QinQ Statistics, run the following reset command in the user view:
Procedure
Step 1 Run the reset qinq statistic interface interface-type interface-number.subinterface-number
vlan-group group-id command to clear the QinQ statistics.
----End
5.13.2 Monitoring the Operating Status of the Termination Sub-

interface
In routine maintenance, you can run the following display commands in any view to check the
operation of the sub-interface for QinQ/dot1q VLAN tag termination.
Procedure
number [.subinterface-number ] ] command in any view to check information about the
sub-interface for dot1q VLAN tag termination.
l Run the display qinq information termination [ interface interface-type interface-
number [.subinterface-number ] ] command in any view to check information about the
sub-interface for QinQ VLAN tag termination.
l Run the display qinq information stacking [ interface interface-type interface-number
[.subinterface-number ] ] command in any view to check information about QinQ Stacking.
----End


This section describes the typical application scenarios of QinQ, including networking
files.
NOTE
5.14.1 Example for Configuring the QinQ Tunnel

After a Layer 2 QinQ tunnel is configured, different enterprises can plan their own VLANs. In
this manner, offices in different locations of the same enterprise can communicate whereas
different enterprises cannot.
In the network as shown in Figure 5-7, enterprise 1 has two offices and enterprise 2 has three
offices; offices of enterprise 1 and enterprise 2 connect to RouterA and RouterB in the operator
network respectively. Enterprise 1 and enterprise 2 can partition their own VLANs as desired.
It is required to configure the QinQ tunnel on RouterA and RouterB. Thus, office networks in
enterprise 1 or enterprise 2 can interwork but office networks between enterprise 1 and enterprise
2 cannot interwork.

Figure 5-7 Typical networking diagram of the QinQ tunnel

Company 2 Company 2
RouterB
GE1/0/1 GE2/0/1
GE3/0/1
…… ……
RouterA GE1/0/0
VLAN1000 VLAN4094 GE1/0/1 GE3/0/1 VLAN500 VLAN2500
GE2/0/1
…… ……
……
VLAN2 VLAN500 VLAN1000 VLAN2000 VLAN100 VLAN500
Company 1 Company 2 Company 1
1. Configure the default outer VLAN tag.
2. Configure QinQ for a Layer 2 interface.
3. Configure the interfaces disabled with QinQ and allow the packets carrying the specific
outer tags to pass through the interface.
Data Preparation
l Number of the interface connecting to enterprise 1 and enterprise 2
l Default VLAN ID of the QinQ interface connecting to enterprise 1 and enterprise 2
Procedure
Step 1 Create the default outer VLAN tag for a Layer 2 interface.


[RouterA] vlan batch 10 20
[RouterB] vlan batch 20
Step 2 Configure QinQ for a Layer 2 interface.

[RouterA-GigabitEthernet1/0/1] port link-type dot1q-tunnel
[RouterA-GigabitEthernet1/0/1] port default vlan 10
[RouterB-GigabitEthernet1/0/1] port link-type dot1q-tunnel
[RouterB-GigabitEthernet1/0/1] port default vlan 20
[RouterB-GigabitEthernet2/0/1] port link-type dot1q-tunnel
[RouterB-GigabitEthernet2/0/1] port default vlan 20
Step 3 Configure other interfaces.

# Allow the packets in VLAN 20 to pass through GE 1/0/0 on RouterA.
[RouterA-GigabitEthernet1/0/0] port trunk allow-pass vlan 20
# Allow the packets in VLAN 20 to pass through GE 3/0/1 on RouterB.

[RouterB-GigabitEthernet3/0/1] portswich

Hosts in different offices but the same VLAN can ping through each other in enterprise 1.

Any host in enterprise 1 and enterprise 2 cannot ping through each other.
----End
Configuration Files
#
sysname RouterA
#
vlan batch 10 20
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return

#
sysname RouterB
#
vlan batch 20
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return

5.14.2 Example for Configuring Selective QinQ on a Layer 2

Interface
Layer 2 selective QinQ is an extension of the QinQ Layer 2 tunnel function, and is more flexible.
This example shows how a Layer 2 QinQ interface enabled with Layer 2 selective QinQ adds
different outer tags to the incoming frames with different inner tags to further classify VLANs.
As shown in Figure 5-8, enterprise 1 and enterprise 2 have many offices.
l VLAN 2 to VLAN 500 are used in the network of enterprise 1.

l VLAN 500 to VLAN 4094 are used in the network of enterprise 2.
l GE 1/0/1 on RouterA receives the packets from different VLANs of enterprise 1 and
enterprise 2 simultaneously.
It is required to configure Layer 2 selective QinQ on GE 1/0/1 of RouterA. Thus, office networks
in enterprise 1 or enterprise 2 can interwork but office networks between enterprise 1 and
enterprise 2 cannot interwork.
Figure 5-8 Typical networking diagram of Layer 2 selective QinQ

Company 2 RouterB Company 2
GE1/0/1 GE2/0/1
…… GE3/0/1 ……
RouterA GE3/0/1
VLAN1000 VLAN4094 GE1/0/1 GE2/0/1 VLAN500 VLAN2500
……
……
……
VLAN100 VLAN500
Company 1
VLAN2 VLAN500 VLAN1000 VLAN2000
Company 1 Company 2

1. Configure the default outer VLAN tag.
2. Configure selective QinQ for a Layer 2 interface.
3. Configure the interfaces disabled with QinQ and allow the packets carrying the specific
outer tags to pass through the interface.
Data Preparation
l Number of the interface connecting to enterprise 1 and enterprise 2
l Outer tags attached to the packets of different enterprises on Layer 2 interfaces of
RouterA and RouterB
Procedure
Step 1 Create the default outer VLAN tag for a Layer 2 interface.
[RouterA] vlan batch 10 20
[RouterB] vlan batch 20
Step 2 Configure selective QinQ for a Layer 2 interface.

[RouterA-GigabitEthernet1/0/1] port vlan-stacking vlan 2 to 500 stack-vlan 10
[RouterB-GigabitEthernet1/0/1] port vlan-stacking vlan 1000 to 4094 stack-vlan 20
[RouterB-GigabitEthernet2/0/1] port vlan-stacking vlan 500 to 2500 stack-vlan 20
Step 3 Configure other interfaces.

# Allow the packets of VLAN 20 to pass through GE 3/0/1 on RouterA.

[RouterA-GigabitEthernet3/0/1] port trunk allow-pass vlan 20
# Allow the packets in VLAN 20 to pass through GE 3/0/1 on Router B.

[RouterB-GigabitEthernet3/0/1] portswich

Any host in enterprise 1 and enterprise 2 cannot ping through each other.
----End
Configuration Files
#
sysname RouterA
#
vlan batch 10 20
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return
l RouterB
#
sysname RouterB
#
vlan batch 20
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#

undo shutdown
portswitch
#
return
5.14.3 Example for Configuring Compatibility of the EthType Field

in the Outer Tag of QinQ Packets
This example shows how to configure the EthType of an outer tag to enable the interworking
between the devices of different vendors.
Router B is Huawei data communications equipment. Router A and Router C are the devices of
other vendors. Switch A is the switch of other vendors. Figure 5-9 shows the networking diagram
and the EthType value in the outer tag of QinQ packets. Devices of different vendors can
cooperate by setting the EthType value in the outer tag of the interface on Router B.
Figure 5-9 Networking diagram of configuring the compatibility of the EthType field in the
outer tag of QinQ packets
100
0x9
GE1/0/0
0x9100
IP/MPLS Switch A
Core
0x81
Router A GE2/0/0 00
Router B
Router C
Device Name EthType Value in the Outer Tag Device Name EthType Value in the Outer Tag
Router A 0x9100 Router C 0x8100
Router B 0x8100 Switch A 0x9100
1. Switch Layer 3 interfaces into Layer 2 interfaces.

2. Configure the compatibility of the EthType field in the outer tag of QinQ packets on the
Layer 2 interface of the device in the demand for interworking.
Data Preparation
l EthType encapsulation value in the outer tag of the device of other vendors
l Name of the physical interface through which RouterB connects to the devices of other
vendors

Procedure
Step 1 Switch the interface connecting to the devices of other vendors into a Layer 2 interface.
Step 2 Configure the EthType encapsulation value of the outer tag on the physical interface through
which RouterB connects to the devices of other vendors.
[RouterB-GigabitEthernet1/0/0] qinq protocol 9100
After the previous configurations, running the display this command on GE 1/0/0 of RouterB,
you can view the configuration of this command.
Run the display bpdu-tunnel interface config command, you can view the configuration of
TPID.
[RouterB-GigabitEthernet1/0/0] display bpdu-tunnel interface config
EtherType 9100
Dot1qVlan
TwoQList
----End
Configuration Files
Configuration file of Router B
#
sysname RouterB
#
interface GigabitEthernet 1/0/0
undo shutdown
qinq protocol 9100
portswitch
#
undo shutdown
portswitch
#
return
5.14.4 Example for Configuring the Sub-interface for dot1q VLAN

Tag Termination to Support Proxy ARP
This example shows how to configure a sub-interface for dot1q VLAN tag termination to support
proxy ARP, and how to enable the interworking between users in the same network segment but
in different VLANs.

Network Requirements
As shown in Figure 5-10, Router 1 and Router 2 are connected through Ethernet sub-interfaces.
GE 1/0/0 and GE 1/0/1 on Router belong to different VLANs. Router 2 is connected to PC 1
and PC 2. PC 1 and PC 2 are in the same network segment. PC 1 and PC 2 are not configured
with the default gateway. Proxy ARP thus needs to be configured on the sub-interface GE 1/0/0.1
of Router 1 so that PC 1 and PC 2 can communicate with each other.
Figure 5-10 Typical networking diagram of configuring the sub-interface for dot1q VLAN tag
termination to support proxy ARP
Router1
GE1/0/0.1
10.1.1.254/24
GE1/0/2
Router2
GE1/0/0 GE1/0/1
VLAN10 VLAN20
PC1:10.1.1.1/24 PC2:10.1.1.2/24
1. Switch the Layer 3 interface of Router 2 into a Layer 2 interface.
2. Configure the basic Layer 2 forwarding function for Router 2.
3. Configure a dot1q termination sub-interface for Router 1 and enable proxy ARP.
Data Preparation
l Name of the sub-interface for dot1q VLAN tag termination
l VLAN IDs of the interfaces on Router 2
Procedure
Step 1 Switch the interface to a Layer 2 interface.
# Configure Router 2.
[HUAWEI] sysname Router2
[Router2] interface gigabitethernet 1/0/0
[Router2-GigabitEthernet1/0/0] portswitch
[Router2-GigabitEthernet1/0/0] undo shutdown

[Router2-GigabitEthernet1/0/0] quit
NOTE
If the interface is already a Layer 2 interface, the preceding operation is not required.
Step 2 Configure the basic Layer 2 forwarding function.

[Router2] vlan 10
[Router2-vlan10] port gigabitethernet 1/0/0
[Router2-vlan10] quit
[Router2] vlan 20
[Router2-GigabitEthernet1/0/2] port trunk allow-pass vlan 10 20
Step 3 Configure the sub-interface for dot1q VLAN tag termination and enable proxy ARP on the sub-
interface.
[Router1-GigabitEthernet1/0/0] mode user-termination
[Router1] interface gigabitethernet 1/0/0.1
[Router1-GigabitEthernet1/0/0.1] control-vid 1 dot1q-termination
[Router1-GigabitEthernet1/0/0.1] dot1q termination vid 10
[Router1-GigabitEthernet1/0/0.1] ip address 10.1.1.254 24
[Router1-GigabitEthernet1/0/0.1] arp-proxy inter-sub-vlan-proxy enable
[Router1-GigabitEthernet1/0/0.1] arp broadcast enable
[Router1-GigabitEthernet1/0/0.1] undo shutdown
[Router1-GigabitEthernet1/0/0.1] quit

Ping PC 2 from PC 1. The ping succeeds. If viewing the ARP table on PC 1, you can find that
the MAC address corresponding to PC 2 is the MAC address of GE 1/0/0 on Router 1.
----End
Configuration Files
l Configuration file of Router 1
#
sysname Router1
#
undo shutdown
#
undo shutdown

ip address 10.1.1.254 255.255.255.0
#
return

#
sysname Router2
#
vlan batch 10 20
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return
5.14.5 Example for Configuring the Sub-interface for QinQ VLAN

Tag Termination to Support Proxy ARP
This example shows how to configure a sub-interface for QinQ VLAN tag termination to support
proxy ARP, and how to enable the interworking between users in the same network segment but
in different VLANs.
As shown in Figure 5-11, Router 1 is connected to Router 2 through a sub-interface. GE 1/0/0
and GE 1/0/1 on Router 2 belong to different VLANs. Router 2 is connected to PC 1 and PC 2
through Router 3 and Router 4 respectively. PC 1 and PC 2 are in the same network segment
but belong to different VLANs. Configure QinQ on the convergent device Router 2, with the
outer tag as 100. The packet sent from Router 2 to Router 1 then carries double tags. Default
gateways are not configured on PC 1 and PC 2. In this case, you can configure proxy ARP on
the sub-interface GE 1/0/0.1 of Router 1 to implement inter-communication between PC 1 and
PC 2.

Figure 5-11 Typical networking diagram of configuring the sub-interface for QinQ VLAN tag
termination to support proxy ARP
Router1
GE1/0/0.1
10.1.1.254/24
GE1/0/2 Router2
GE1/0/0 GE1/0/1
GE1/0/1 GE1/0/1
Router3 Router4
GE1/0/0 GE1/0/0
VLAN10 VLAN20
PC1:10.1.1.1/24 PC2:10.1.1.2/24
1. Configure the sub-interface for QinQ VLAN tag termination on Router 1.
2. Enable proxy ARP on GE 1/0/0.1.
3. Configure QinQ on Router 2.
4. Configure the basic Layer 2 forwarding function on Router 2, Router 3, and Router 4.
Data Preparation
l Name of the sub-interface for QinQ VLAN tag termination
l Outer tag value of the packet sent from Router 2 to Router 1
l VLAN IDs of the interfaces on Router 3, and Router 4
Procedure
Step 1 Switch the interface to a Layer 2 interface.


NOTE
If the interface is already a Layer 2 interface, the preceding operation is not required.

[Router3] vlan 10
[Router3-GigabitEthernet1/0/1] port trunk allow-pass vlan 10
[Router4] vlan 20
Step 3 Configure QinQ on Router 2 and set the packet sent from Router 2 to Router 1 to carry double
VLAN tags.
[Router2] vlan 100
[Router2-GigabitEthernet1/0/0] port vlan-stacking vlan 10 stack-vlan 100
[Router2-GigabitEthernet1/0/1] port vlan-stacking vlan 20 stack-vlan 100

NOTE
type dot1q-tunnel and port default vlan on the interface to configure QinQ.
Step 4 Configure the sub-interface for QinQ VLAN tag termination and enable proxy ARP on the sub-
interface.
[Router1-GigabitEthernet1/0/0.1] control-vid 1 qinq-termination
[Router1-GigabitEthernet1/0/0.1] qinq termination pe-vid 100 ce-vid 10
[Router1-GigabitEthernet1/0/0.1] arp-proxy inter-sub-vlan-proxy enable
NOTE
When you run the qinq termination command on the same primary interface , the ce-vid values cannot
be the same if the pe-vid values of the two different sub-interfaces are the same.

Ping PC 2 from PC 1. The ping succeeds. If viewing the ARP table on PC 1, you can find that
the corresponding MAC address of PC 2 is the MAC address of GE 1/0/0 on Router 1.
----End
Configuration Files
#
sysname Router1
#
undo shutdown
#
undo shutdown
ip address 10.1.1.254 255.255.255.0
#
return

#
sysname Router2
#
vlan batch 100
#

shutdown
portswitch
port vlan-stacking vlan 10 stack-vlan 100
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return

#
sysname Router3
#
vlan batch 10
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return

#
sysname Router4
#
vlan batch 20
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return

Tag Termination to Support VRRP
This example shows how to ensure reliable and stable connections between the end users that
send packets with one tag and the network after you configure a sub-interface for dot1q VLAN
tag termination to support VRRP.
As shown in Figure 5-12, a host accesses the ISP network through the default gateway.

l As the default gateway of the host, the VRRP backup group consists of Router 1 and
Router 2.
l In normal case, Router 1 serves as the gateway. When Router 1 is faulty, Router 2 acts as
the gateway.
l When Router 1 recovers, it can become master within 20 seconds.
l The packets sent by Switch 1 have a single tag.
It is required to configure GE 2/0/0.1 respectively on Router 1 and Router 2 to implement VRRP

on the sub-interface for dot1q VLAN tag termination.
termination to support VRRP
MPLS/IP
backbone
POS1/0/0 POS1/0/1
192.168.2.2/24 192.168.1.2/24
POS1/0/0 POS1/0/0
192.168.2.1/24 Router3 192.168.1.1/24
Router1 Router2
Backup Group1
GE2/0/0.1 GE2/0/0.1
100.1.1.1/24 virture IP address 100.1.1.2/24
100.1.1.111/24
Switch
GE1/0/1 GE1/0/2
GE1/0/0
VLAN10
Host100.1.1.3/24
1. Configure the interface mode on Router 1 and Router 2 to the user termination mode.
2. Run an IGP to ensure the connectivity between routers on the backbone network.
3. Configure the GE 2/0/0.1 interfaces of Router 1 and Router 2 as the sub-interface for dot1q
4. Create the backup group1 on the interface GE 2/0/0.1 of Router 1, and configure the high
precedence for Router 1 in the backup group. Ensure that Router 1 is master, and Configure
Preemption mode.

5. Create the backup group1 on the interface GE 2/0/0.1 of Router 2, and use the default
precedence.
6. Configure the basic Layer 2 forwarding function on Switch.
Data Preparation
l Number of VRRP backup group, and virtual IP address
l Priority of the Router in the backup group
l Terminating range of the sub-interface for dot1q VLAN tag termination
Procedure
Step 2 Configure the network interconnection between the devices.

Configure IP addresses of interfaces as described in Figure 5-12. Configure IGP that runs
between Router 1, Router 2, and Router 3. In this example, OSPF is configured.
[Router1] interface pos 1/0/0
[Router1-Pos1/0/0] ip address 192.168.2.1 24
[Router1-Pos1/0/0] undo shutdown
[Router1-Pos1/0/0] quit
[Router1] ospf
[Router1-ospf-1] area 0
[Router1-ospf-1-area-0.0.0.0] network 192.168.2.0 0.0.0.255
[Router1-ospf-1-area-0.0.0.0] quit
[Router1-ospf-1] quit


[Router2] ospf
[Router3] ospf
After the preceding configurations, Router 1 and Router 2 both have routes, discovered through
OSPF, to each other. Router 1 and Router 2 can ping through each other.
Take the display on Router 1 as an example:

[Router1] display ip routing-table
------------------------------------------------------------------------------
192.168.1.0/24 OSPF 10 2 D 192.168.2.2 Pos1/0/0
192.168.2.0/24 Direct 0 0 D 192.168.2.1 Pos1/0/0
192.168.2.0/30 OSPF 10 2 D 192.168.2.2 Pos1/0/0
192.168.2.2/32 Direct 0 0 D 192.168.2.2 Pos1/0/0
Router 1 and Router 2 can ping through each other.

[Router1] ping 192.168.1.1
0.00% packet loss
Step 3 Configure VRRP on the sub-interface for dot1q VLAN tag termination.
Set the default gateway of the host to 100.1.1.111.
# Configure Router 1, create backup group 1, and set the priority of Router 1 in this backup
group to 120. (Router 1 serves as the Master.)


[Router1-GigabitEthernet2/0/0.1] dot1q vrrp vid 10
[Router1-GigabitEthernet2/0/0.1] vrrp vrid 1 virtual-ip 100.1.1.111
[Router1-GigabitEthernet2/0/0.1] vrrp vrid 1 priority 120
[Router1-GigabitEthernet2/0/0.1] vrrp vrid 1 preempt-mode timer delay 20
# Configure Router 2, create backup group 1, and set the priority of Router 2 in this backup
group to the default value. (Router 2 serves as the Backup.)
[Router2-GigabitEthernet2/0/0.1] dot1q vrrp vid 10
After the preceding steps, the sub-interfaces for dot1q VLAN tag termination on Router 1 and
Router 2 become Up. A route to the network segment 100.1.1.0/24 is generated on Router 3.

------------------------------------------------------------------------------
100.1.1.0/24 OSPF 10 2 D 192.168.2.1 Pos1/0/0
OSPF 10 2 D 192.168.1.1 Pos1/0/1
100.1.1.111/32 OSPF 10 2 D 192.168.2.1 Pos1/0/0
192.168.1.0/24 Direct 0 0 D 192.168.1.2 Pos1/0/1
192.168.1.1/32 Direct 0 0 D 192.168.1.1 Pos1/0/1
192.168.2.0/24 OSPF 10 2 D 192.168.2.1 Pos1/0/0
192.168.2.0/30 Direct 0 0 D 192.168.2.2 Pos1/0/0
192.168.2.1/32 Direct 0 0 D 192.168.2.1 Pos1/0/0
#Configure Switch.
[HUAWEI] sysname Switch
[Switch] vlan 10
[Switch-vlan10] port gigabitethernet 1/0/0
[Switch-vlan10] quit
[Switch] interface gigabitethernet 1/0/1
[Switch-GigabitEthernet1/0/1] port trunk allow-pass vlan 10
[Switch-GigabitEthernet1/0/1] quit
[Switch-GigabitEthernet1/0/1] undo shutdown

l Verify that the VRRP backup group can provide the gateway function.

Running the display vrrp command on Router 1, you can view that Router 1 is in the master
state. Running the display vrrp command, you can view that Router 2 is in the Backup state.
The results are displayed as follows:
[Router1] display vrrp
GigabitEthernet2/0/0.1 | Virtual Router 1
State : Master
Virtual IP : 100.1.1.111
Master IP : 100.1.1.1
PriorityRun : 120
Preempt : YES Delay time : 20
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES
Config type : normal-vrrp
State : Backup
Virtual IP : 100.1.1.111
Master IP : 100.1.1.2
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES
Running the display ip routing-table command, you can view that there is a direct route in
the routing table on Router 1. The destination address of the direct route is a virtual IP address.
The route is an OSPF route on Router 2.
The command output on Router 1 and Router 2 are as follows:
------------------------------------------------------------------------------
100.1.1.0/24 Direct 0 0 D 100.1.1.1 GigabitEthernet2/0/0.1
192.168.1.0/24 OSPF 10 2 D 192.168.2.2 Pos1/0/0
192.168.2.0/24 Direct 0 0 D 192.168.2.1 Pos1/0/0
192.168.2.0/30 OSPF 10 2 D 192.168.2.2 Pos1/0/0
192.168.2.2/32 Direct 0 0 D 192.168.2.2 Pos1/0/0
------------------------------------------------------------------------------
100.1.1.111/32 OSPF 10 2 D 100.1.1.1 GigabitEthernet2/0/0.1


192.168.1.0/24 Direct 0 0 D 192.168.1.1 Pos1/0/0
192.168.1.2/32 Direct 0 0 D 192.168.1.2 Pos1/0/0
192.168.2.0/30 OSPF 10 2 D 192.168.1.2 Pos1/0/0
l Verify that Router 2 becomes master when Router 1 is faulty.

Run the shutdown command on GE 2/0/0.1 of Router 1 and imitate that Router 1 is faulty.
Run the display vrrp command on Router 1 and Router 2 respectively to view VRRP status.
You can find that VRRP status on Router 1 is "Initialize" and VRRP status on Router 2 is
"Master".
State : Initialize
Virtual IP : 100.1.1.111
Master IP : 100.1.1.1
PriorityRun : 120
MasterPriority : 0
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES
State : Master
Virtual IP : 100.1.1.111
Master IP : 100.1.1.2
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES
l Verify that it can preempt after Router 1 recovers.

Run the undo shutdown command on GE 2/0/0.1 on Router 1. After GE 2/0/0.1 turns Up,
run the display vrrp command on Router 1 to view VRRP status. You can find that VRRP
status on Router 1 is Backup.
State : Backup
Virtual IP : 100.1.1.111
Master IP : 100.1.1.1
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES

After 20 seconds, run the display vrrp command on Router 1 to view VRRP status. You can
find VRRP status restores Master.
State : Master
Virtual IP : 100.1.1.111
Master IP : 100.1.1.1
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES
----End
Configuration Files
#
sysname Router1
#
undo shutdown
#
undo shutdown
dot1q vrrp vid 10
ip address 100.1.1.1 255.255.255.0
vrrp vrid 1 preempt-mode timer delay 20
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.2.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 192.168.2.0 0.0.0.255
network 100.1.1.0 0.0.0.255
#
return

#
sysname Router2
#
undo shutdown
#
undo shutdown
dot1q vrrp vid 10

ip address 100.1.1.2 255.255.255.0

#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.1.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 192.168.1.0 0.0.0.255
network 100.1.1.0 0.0.0.255
#
return

#
sysname Router3
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.2.2 255.255.255.0
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 192.168.1.2 255.255.255.0
#
ospf 1
area 0.0.0.0
network 192.168.1.0 0.0.0.255
network 192.168.2.0 0.0.0.255
#
return
l Configuration file of Switch

#
sysname Switch
#
vlan batch 10
#
undo shutdown
#
undo shutdown
#
undo shutdown
#
return

Tag Termination to Support VRRP
This example shows how to ensure reliable and stable connections between the end users that
send packets with double tags and the network after you configure a sub-interface for QinQ
VLAN tag termination to support VRRP.

As shown in Figure 5-13, a host accesses the ISP network through the default gateway.
l As the default gateway of the host, the VRRP backup group consists of Router 1 and
Router 2.
l In normal case, Router 1 serves as the gateway. When Router 1 is faulty, Router 2 acts as
the gateway.
l When Router 1 recovers, it can become master within 20 seconds.
l The packets sent by Switch 1 have double tags.
It is required to configure GE 2/0/0.1 respectively on Router 1 and Router 2 to implement VRRP
on the sub-interface for QinQ VLAN tag termination.
termination to support VRRP
MPLS/IP
backbone
POS1/0/0
192.168.2.2/24 POS1/0/1
192.168.1.2/24
POS1/0/0 Router3 POS1/0/0
192.168.2.1/24 192.168.1.1/24
Backup Group1
Router1 virture IP address Router2
100.1.1.111/24
GE2/0/0.1 100.1.1.1/24
Backup Group2 GE2/0/0.1 100.1.1.2/24
GE2/0/0.2 200.1.1.1/24 GE2/0/0.2 200.1.1.2/24
virture IP address
200.1.1.111/24
Switch1
GE1/0/2 GE1/0/3
GE1/0/0 GE1/0/1
GE1/0/1
Switch2 GE1/0/1 Switch3
GE1/0/0 GE1/0/0
VLAN10 VLAN20
Host1:100.1.1.3/24 Host2:200.1.1.3/24
1. Configure the interface mode on Router 1 and Router 2 to the user termination mode.

2. Run an IGP to ensure the connectivity between devices on the backbone network.
3. Configure the interface GE 2/0/0.1 on Router 1 and Router 2 as the sub-interface for QinQ
precedence for Router 1 in the backup group. Ensure that Router 1 is master and Configure
Preemption mode.
precedence for Router 1 in the backup group. Ensure that Router 1 is master and Configure
Preemption mode.
6. Create the backup group1 on the interface GE 2/0/0.1 of Router 2 and use the default
precedence.
7. Create the backup group2 on the interface GE 2/0/0.2 of Router 2 and use the default
precedence.
8. Configure the QinQ function on Switch 1, two tags of the packet sent from Switch1 to
Router 2 and Router 1
9. Configure the basic forwarding functions on Switch 2 and Switch 3.
Data Preparation
l Number of VRRP backup group, and virtual IP address
l router precedence in the backup group
l Terminating range of the sub-interface for QinQ VLAN tag termination
Procedure
Step 2 Configure the network interconnection between the devices.

As shown in Figure 5-13, configure IP addresses of interfaces. Configure IGP run between
Router 1, Router 2, and Router 3. Here, OSPF is configured.

[Router1] ospf
[Router2] ospf
[Router3] ospf
After the preceding configurations, Router 1 and Router 2 both have routes, discovered through
OSPF, to each other. Router 1 and Router 2 can ping through each other.
------------------------------------------------------------------------------

100.1.1.1/32 Direct 0 0 D
127.0.0.1 InLoopBack0
127.0.0.0/8 Direct 0 0 D
127.0.0.1/32 Direct 0 0 D
192.168.1.0/24 OSPF 10 2 D
192.168.2.2 Pos1/0/0
192.168.2.0/24 Direct 0 0 D
192.168.2.1 Pos1/0/0
192.168.2.1/32 Direct 0 0 D
192.168.2.2/32 Direct 0 0 D
192.168.2.2 Pos1/0/0
Router 1 and Router 2 can ping through each other.

[Router1] ping 192.168.1.1
0.00% packet loss
Step 3 Configure VRRP on the sub-interface for QinQ VLAN tag termination.
Set the default gateway of the host to 100.1.1.111.
# Configure Router 1, create backup group 1 and backup group 2, and set the priority of
Router 1 in backup group 1 and backup group 2 to 120. (Router 1 serves as the Master.)
[Router1-GigabitEthernet2/0/0.1] qinq vrrp pe-vid 100 ce-vid 10
# Configure Router 2, create backup group 1 and backup group 2, and set the priority of
Router 2 in backup group 1 and backup group 2 to the default value. (Router 2 serves as the
Backup.)


NOTE
After the preceding steps, the sub-interfaces for QinQ VLAN tag termination on Router 1 and
Router 2 turn Up. Routes to the network segments 100.1.1.0/24 and 200.1.1.0/24 are generated
on Router 3.

------------------------------------------------------------------------------
100.1.1.0/24 OSPF 10 2 D 192.168.1.1 Pos1/0/1
OSPF 10 2 D 192.168.2.1 Pos1/0/0
100.1.1.111/32 OSPF 10 2 D 192.168.2.1 Pos1/0/0
192.168.1.0/24 Direct 0 0 D 192.168.1.2 Pos1/0/1
192.168.1.1/32 Direct 0 0 D 192.168.1.1 Pos1/0/1
192.168.2.0/24 Direct 0 0 D 192.168.2.2 Pos1/0/0
192.168.2.1/32 Direct 0 0 D 192.168.2.1 Pos1/0/0
200.1.1.0/24 OSPF 10 2 D 192.168.2.1 Pos1/0/0
OSPF 10 2 D 192.168.1.1 Pos1/0/1
200.1.1.111/32 OSPF 10 2 D 192.168.2.1 Pos1/0/0
Step 4 Configure the basic Layer 2 forwarding functions on Switches.
[Switch2] vlan 10
[Switch2-vlan10] port gigabitethernet 1/0/0
[Switch2-vlan10] quit
[Switch2] interface gigabitethernet 1/0/1
[Switch3] vlan 20
Step 5 Configure QinQ on Switch 1 and set the packets sent from Switch 1 to Router 1 and Router 2
to carry double VLAN tags.

[Switch1] vlan 100
[Switch1-GigabitEthernet1/0/0] port vlan-stacking vlan 10 stack-vlan 100
NOTE

l Verify that the VRRP backup group can normally provide the gateway function.
Running the display vrrp command on Router 1, you can view that Router 1 is in the master
state. Running the display vrrp command on Router 2, you can view that Router 2 is in the
Backup state. The results are displayed as follows:
State : Master
Virtual IP : 100.1.1.111
Master IP : 100.1.1.1
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES

State : Master
Virtual IP : 200.1.1.111
Master IP : 200.1.1.1
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES
State : Backup
Virtual IP : 200.1.1.111
Master IP : 200.1.1.2

PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES

State : Backup
Virtual IP : 100.1.1.111
Master IP : 100.1.1.2
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES
Running the display ip routing-table command on Router 1 and Router 2, you can view
that there is a direct route in the routing table on Router 1. The destination address of the
direct route is a virtual IP address, and the route is an OSPF route on Router 2.
The command output on Router 1 and Router 2 are as follows:
------------------------------------------------------------------------------
OSPF 10 2 D 200.1.1.2 GigabitEthernet2/0/0.2
OSPF 10 2 D 192.168.2.2 Pos1/0/0
192.168.2.0/24 Direct 0 0 D 192.168.2.1 Pos1/0/0
192.168.2.2/32 Direct 0 0 D 192.168.2.2 Pos1/0/0
------------------------------------------------------------------------------
192.168.1.0/24 Direct 0 0 D 192.168.1.1 Pos1/0/0


192.168.1.2/32 Direct 0 0 D 192.168.1.2 Pos1/0/0
OSPF 10 2 D 192.168.1.2 Pos1/0/0
l Verify that when Router 1 is faulty, Router 2 can become master.
Run the shutdown command on GE 2/0/0.1 of Router 1 and imitate that Router 1 is faulty.
Run the display vrrp command on Router 1 and Router 2 respectively to view VRRP status.
You can find that VRRP status on Router 1 is "Initialize" and VRRP status on Router 2 is
"Master".
State : Initialize
Virtual IP : 100.1.1.111
Master IP : 100.1.1.1
PriorityRun : 120
MasterPriority : 0
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES

State : Master
Virtual IP : 200.1.1.111
Master IP : 200.1.1.1
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES
State : Backup
Virtual IP : 200.1.1.111
Master IP : 200.1.1.2
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES

State : Master
Virtual IP : 100.1.1.111

Master IP : 100.1.1.2
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES
Run the shutdown command on GE2/0/0.2 of Router 1. The operation process is as described
previously. It is not mentioned here.
l Verify that after Router 1 recovers, it can preempt.
Run the undo shutdown command on GE 2/0/0.1 on Router 1. After GE 2/0/0.1 turns Up,
run the display vrrp command on Router 1 to view VRRP status. You can find that VRRP
status on Router 1 restores Backup.
State : Backup
Virtual IP : 100.1.1.111
Master IP : 100.1.1.1
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES

State : Master
Virtual IP : 200.1.1.111
Master IP : 200.1.1.1
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES
After 20 seconds, run the display vrrp command on Router 1 to view VRRP status. You can
find VRRP status restores Master.
State : Master
Virtual IP : 100.1.1.111
Master IP : 100.1.1.1
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101

Check TTL : YES


State : Master
Virtual IP : 200.1.1.111
Master IP : 200.1.1.1
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES
----End
Configuration Files
#
sysname Router1
#
undo shutdown
#
undo shutdown
qinq vrrp pe-vid 100 ce-vid 10
ip address 100.1.1.1 255.255.255.0
#
undo shutdown
ip address 200.1.1.1 255.255.255.0
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.2.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 192.168.2.0 0.0.0.255
network 100.1.1.0 0.0.0.255
network 200.1.1.0 0.0.0.255
#
return

#
sysname Router2
#
undo shutdown
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
#
undo shutdown
ip address 200.1.1.2 255.255.255.0
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.1.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 192.168.1.0 0.0.0.255
network 100.1.1.0 0.0.0.255
network 200.1.1.0 0.0.0.255
#
return
#
sysname Router3
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.2.2 255.255.255.0
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 192.168.1.2 255.255.255.0
#
ospf 1
area 0.0.0.0
network 192.168.1.0 0.0.0.255
network 192.168.2.0 0.0.0.255
#
return
l Configuration file of Switch 1
#
sysname Switch1
#
vlan batch 100
#
undo shutdown
#

undo shutdown
#
undo shutdown
#
undo shutdown
#
return
#
sysname Switch2
#
vlan batch 10
#
undo shutdown
#
undo shutdown
#
return
#
sysname Switch3
#
vlan batch 20
#
undo shutdown
#
undo shutdown
#
return
5.14.8 Example for Configuring the Sub-interface for dotlq and

QinQ VLAN Tag Termination to Access an L3VPN
PEs are connected through an L3VPN; user packets sent to the PEs carry one tag and double
tags respectively. This example describes how users communicate with each other through an
L3VPN and how to configure sub-interfaces for dot1q VLAN tag termination, sub-interfaces
for QinQ VLAN tag termination, and L3VPNs.
As shown in Figure 5-14, both GE 1/0/0.1 of CE1 and that of CE3 are connected to PE1 through
Switch 1. QinQ is configured on Switch 1 so that the outer VLAN tag with the VLAN ID as 100
is added to a user packet from CE1 or CE3. The public VLAN IDs are thus saved. Then the user
packet sent from Switch 1 to PE1 carries double VLAN tags.
CE2 and CE4 are connected to PE2 through Switch 2 and a user packet sent from Switch 2 to
PE2 carries one VLAN tag.
It is required that the sub-interface for QinQ VLAN tag termination be configured on PE1 to
access the L3VPN; the sub-interface for dot1q VLAN tag termination be configured on PE2 to

access the L3VPN. Then the user networks connected to CE1 and CE2 can communicate with
each other; the user networks connected to CE3 and CE4 can communicate with each other.
NOTE
The types of the AC interfaces at both ends of the L3VPN are not necessarily associated with each other.
The interfaces at both ends can be sub-interfaces for QinQ VLAN tag termination or sub-interfaces for
dot1q VLAN tag termination.
Figure 5-14 Typical networking diagram of configuring the sub-interface for dot1q and QinQ
VLAN tag termination to access an L3VPN
AS100
1.1.1.9/32 2.2.2.9/32 3.3.3.9/32
POS1/0/0 POS1/0/0
100.1.1.1/24 100.1.2.2/24
PE1 PE2
POS1/0/0 POS2/0/0 GE2/0/0.1
GE2/0/0.1 100.1.1.2/24 100.1.2.1/24
P 10.2.1.1/24
10.1.1.1/24
GE2/0/0.2 GE2/0/0.2
20.1.1.1/24 20.2.1.1/24
GE1/0/0 GE1/0/0
Switch1 Switch2
GE1/0/1 GE1/0/2 GE1/0/1 GE1/0/2
GE1/0/0.1 GE1/0/0.1 GE1/0/0 GE1/0/0

10.1.1.2/24 20.1.1.2/24 10.2.1.2/24 20.2.1.2/24
CE1 AS65410 CE3 AS65411 AS65420 CE2 AS65421 CE4
1. Configure the interface mode to user termination on PE1 and PE2.

2. Run the IGP protocol to interconnect the routers on the backbone network.
3. Configure and enable basic MPLS capabilities on the backbone network.
4. Create the VPN instance, and configure the RD and VPN-Target.
5. Bind the AC interface to the VPN instance.
6. Configure Layer 2 forwarding and QinQ on switches.
7. Configure an EBGP between the CE and the PE to exchange VPN routing information.
Data Preparation
l Name of PE interface connected to CE


l VPN instance names of PE1 and PE2
l RD and VPN-Target of the VPN-Instance
l Tag value of the sub-interface for dot1q VLAN tag termination and QinQ VLAN tag
termination.
Procedure
# Configure PE1.
# Configure PE2.
Step 2 Configure IGP of the MPLS backbone network. OSPF is used in this example.
According to Figure 5-14, configure the addresses for the interfaces on PE and P. Configure
OSPF to advertise the addresses of the loopback interfaces on PE1, P, and PE2.
# Configure PE1.
<PE1> system-view
[PE1-Pos1/0/0] ip address 100.1.1.1 24
[PE1-Pos1/0/0] quit
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure P.
[HUAWEI] sysname P
[P] interface LoopBack 1
[P-LoopBack1] quit
[P-Pos1/0/0] ip address 100.1.1.2 24
[P-Pos1/0/0] quit
[P-Pos2/0/0] ip address 100.1.2.1 24
[P-Pos2/0/0] quit
[P] ospf
[P-ospf-1] area 0

[P-ospf-1] quit
# Configure PE2.
<PE2> system-view
[PE2-Pos1/0/0] ip address 100.1.2.2 24
[PE2-Pos1/0/0] quit
[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
After the preceding steps, PE1 and PE2 have routes, discovered through OSPF, to loopback1
interface of each other. PE1 and PE2 can ping through each other.
------------------------------------------------------------------------------
2.2.2.9/32 OSPF 10 2 D 100.1.1.2 Pos1/0/0
3.3.3.9/32 OSPF 10 3 D 100.1.1.2 Pos1/0/0
100.1.1.0/24 Direct 0 0 D 100.1.1.1 Pos1/0/0
100.1.1.2/32 Direct 0 0 D 100.1.1.2 Pos1/0/0
100.1.2.0/24 OSPF 10 2 D 100.1.1.2 Pos1/0/0
<PE1> ping 100.1.2.2
0.00% packet loss
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
[PE1-Pos1/0/0] mpls
[PE1-Pos1/0/0] quit
# Configure P.

[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
[P] interface pos1/0/0
[P-Pos1/0/0] mpls
[P-Pos1/0/0] quit
[P-Pos2/0/0] mpls
[P-Pos2/0/0] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2-Pos1/0/0] mpls
[PE2-Pos1/0/0] quit
After the configuration, the sessions between PE1 and the P and between PE2 and the P are set
up. Running the display mpls ldp session command, you can view that the status is
"Operational". Running the display mpls ldp lsp command, you can view the establishing status
of LDP LSP.
For example, the following displays the session information on PE1.
------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
<PE1> display mpls ldp lsp
LDP LSP Information
------------------------------------------------------------------------------
SN DestAddress/Mask In/OutLabel Next-Hop In/Out-Interface
------------------------------------------------------------------------------
1 1.1.1.9/32 3/NULL 127.0.0.1 Pos1/0/0/InLoop0
2 2.2.2.9/32 NULL/3 100.1.1.2 -------/Pos1/0/0
3 3.3.3.9/32 NULL/1024 100.1.1.2 -------/Pos1/0/0
4 100.1.2.0/24 NULL/3 100.1.1.2 -------/Pos1/0/0
------------------------------------------------------------------------------
Step 4 Configure VPN instances on PEs and bind the VPN instances to the sub-interface for dot1q
VLAN tag termination and QinQ VLAN tag termination.
# Configure PE1.
<PE1> system-view


[PE1-GigabitEthernet2/0/0.1] arp broadcast enable
# Configure PE2.
<PE2> system-view
NOTE
On different sub-interfaces, the vid values cannot overlap.
After the preceding steps, run the display ip vpn-instance verbose command on PEs to view
configurations of VPN instances.
<PE1> display ip vpn-instance verbose
Create date : 2007/03/03 16:43:43
Create date : 2007/03/03 16:45:21



Create VLAN 100 on Switch 1 so that GE 1/0/1 and GE 1/0/2 add an outer VLAN tag with the
VLAN ID as 100 to a packet of VLAN 10 or VLAN 20. Specify GE 1/0/0 as a trunk interface
and configure it to allow the packets of VLAN 100 to pass through.
[HUAWEI] sysname switch1
[switch1] vlan 100
[switch1-vlan10] quit
[switch1] interface gigabitethernet 1/0/1
[switch1-GigabitEthernet1/0/1] port vlan-stacking vlan 10 stack-vlan 100
[switch1-GigabitEthernet1/0/1] quit
[switch1-GigabitEthernet1/0/0] port trunk allow-pass vlan 100
Create VLAN 10 and 20 on Switch 2. Specify GE 1/0/1 and GE 1/0/2 as access interfaces, and
add GE 1/0/1 to VLAN 10 and GE 1/0/2 to VLAN 20. Specify GE 1/0/0 as a trunk interface and
configure it to allow the packets of VLAN 10 and VLAN 20 to pass through.
[switch2] vlan batch 10 20
[switch2-GigabitEthernet1/0/1] port link-type access
[switch2-GigabitEthernet1/0/1] port default vlan 10
[switch2-GigabitEthernet1/0/0] port trunk allow-pass vlan 10 20
# Configure IP addresses for interfaces of CEs as shown in Figure 5-14. The details are not
mentioned here.
After the configuration, All PEs can ping through their CEs.
NOTE
When multiple interfaces on the PE are bound with the same VPN, you need to specify the source IP address
that is the -a source-ip-address in the ping -vpn-instance vpn-instance-name -a source-ip-address dest-
ip-address command when you run the ping -vpn-instance command; otherwise, the ping fails.

[PE1] ping -vpn-instance vpn1 10.1.1.2


0.00% packet loss
# Configure CE1.
[CE1] bgp 65410
[CE1-bgp] peer 10.1.1.1 as-number 100
[CE1-bgp] import-route direct
# Configure CE2.
[CE2] bgp 65420
# Configure CE3.
[CE3] bgp 65411
# Configure CE4.
[CE4] bgp 65421
# Configure PE1.
[PE1] bgp 100
[PE1-bgp] ipv4-family vpn-instance vpn1
[PE1-bgp-vpn1] peer 10.1.1.2 as-number 65410
[PE1-bgp-vpn1] import-route direct
[PE1-bgp-vpn1] quit
[PE1-bgp-vpn1] quit
# Configure PE2.
[PE2] bgp 100
[PE2-bgp-vpn1] quit
[PE2-bgp-vpn1] quit
After the configuration, running the display bgp vpnv4 vpn-instance peer command on the
PE, you can view that the BGP peer relationships are set up between the PEs and the CEs and
are in the Established state.
[PE1] display bgp vpnv4 vpn-instance vpn1 peer


10.1.1.2 4 65410 6 7 0 00:02:58 Established 1

# Configure PE1.
[PE1] bgp 100
[PE1-bgp] peer 3.3.3.9 as-number 100
[PE1-bgp] peer 3.3.3.9 connect-interface loopback 1
[PE1-bgp] ipv4-family vpnv4
[PE1-bgp-af-vpnv4] peer 3.3.3.9 enable
[PE1-bgp-af-vpnv4] quit
# Configure PE2.
[PE2] bgp 100
After the configuration, running the display bgp peer or display bgp vpnv4 all peer command
on the PE, you can view that the BGP peer relationships between the PEs are set up and are in
the Established state.
3.3.3.9 4 100 5 5 0 00:00:58 Established 0
[PE1] display bgp vpnv4 all peer
3.3.3.9 4 100 5 5 0 00:01:28 Established 2
Peer of vpn instance :
vpn instance vpn1 :
10.1.1.2 4 65410 6 7 0 00:07:59 Established 1
vpn instance vpn2 :
20.1.1.2 4 65411 3 4 0 00:06:39 Established 1

Run the display qinq information command. You can view information about QinQ VLAN
tag termination. In addition, the sub-interface is bound to the L3VPN.
[PE1] display qinq information termination interface gigabitethernet 2/0/0
L3VPN binded
Total QinQ Num: 1
L3VPN binded
Total QinQ Num: 1
Run the display dot1q information command. You can view information about dot1q VLAN
tag termination. In addition, the sub-interface is bound to the L3VPN.


[PE2] display dot1q information termination interface gigabitethernet 2/0/0
L3VPN binded
Total QinQ Num: 1
L3VPN binded
Total QinQ Num: 1
The hosts connected to CE1 and CE2 can ping through each other; the hosts connected to CE3
and CE4 can ping through each other. As they belong to different VPN instances, neither CE1
nor CE2 can communicate with CE3 or CE4.
You can view relevant ARP entries on PEs. Take the display on PE1 as an example.
[PE1] display arp slot 1
IP ADDRESS MAC ADDRESS EXPIRE(M) TYPE INTERFACE VPN-INSTANCE VLAN/CEVLAN
PVC
----------------------------------------------------------------------------------
-
10.1.1.1 00e0-fc00-0001 I - GE1/0/0.1 vpn1
20.1.1.1 00e0-fc00-0001 I - GE1/0/0.2 vpn2
10.1.1.2 00e0-fc00-8fe6 12 DF1 GE1/0/0.1 vpn1 100/10
20.1.1.2 00e0-fc00-8fe6 13 DF1 GE1/0/0.2 vpn2 100/20
----------------------------------------------------------------------------------
-
Total:4 Dynamic:2 Static:0 Interface:2
----End
Configuration Files
#
sysname CE1
#
vlan-type dot1q 10
ip address 10.1.1.2 255.255.255.0
#
bgp 65410
#
ipv4-family unicast
import-route direct
#
return

#
sysname CE2
#
undo shutdown
ip address 10.2.1.2 255.255.255.0
#
bgp 65420

#
ipv4-family unicast
import-route direct
#
return

#
sysname CE3
#
vlan-type dot1q 20
ip address 20.1.1.2 255.255.255.0
#
bgp 65411
#
ipv4-family unicast
import-route direct
#
return

#
sysname CE4
#
undo shutdown
ip address 20.2.1.2 255.255.255.0
#
bgp 65421
#
ipv4-family unicast
import-route direct
#
return
l Configuration file of switch1

#
sysname switch1
#
vlan batch 100
#
undo shutdown
#
undo shutdown
#
undo shutdown
#
return

#
sysname switch2
#
vlan batch 10 20

#
undo shutdown
#
undo shutdown
#
undo shutdown
#
return
#
sysname PE1
#
#
#
mpls lsr-id 1.1.1.9
mpls
#
mpls ldp
#
undo shutdown
#
ip address 10.1.1.1 255.255.255.0
#
ip address 20.1.1.1 255.255.255.0
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast

peer 3.3.3.9 enable

#
ipv4-family vpnv4
policy vpn-target
peer 3.3.3.9 enable
#
import-route direct
#
import-route direct
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 100.1.1.0 0.0.0.255
#
return
#
sysname P
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 100.1.2.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 100.1.1.0 0.0.0.255
network 100.1.2.0 0.0.0.255
#
return
#
sysname PE2
#
#
#
mpls lsr-id 3.3.3.9

mpls
#
mpls ldp
#
undo shutdown
#
ip address 10.2.1.1 255.255.255.0
#
ip address 20.2.1.1 255.255.255.0
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.2.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
import-route direct
#
import-route direct
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 100.1.2.0 0.0.0.255
#
return
5.14.9 Example for Configuring the Dot1q Termination Sub-

interface to Access the VLL
PEs are connected through an L2VPN; user packets sent to the PEs carry one tag. This example
describes how to communicate through an L2VPN and how to configure sub-interfaces for Dot1q
VLAN tag termination and L2VPNs.

As shown in Figure 5-15, GE 1/0/0 on CE1 is connected to PE1 through a switch. The switch
adds a VLAN tag with the VLAN ID being 100 to the packets sent from CE1. CE2 is connected
to PE2 through a sub-interface.
The Dot1q termination sub-interface accesses the VLL on PE1. In this example, the Dot1q
termination sub-interface accesses the VLL in Martini mode. After the preceding configurations,
the user networks connected to CE1 and CE2 can communicate.
NOTE
The Dot1q termination sub-interface can be bound to a VLL. The Martini or Kompella VLL supports both
the homogeneous and heterogeneous transport (transport media of the same type or of different types can
communicate with each other through the VLL). The CCC or SVC VLL supports neither the homogeneous
transport nor the heterogeneous transport.
Figure 5-15 Networking diagram of configuring the Dot1q termination sub-interface to access
the VLL
1.1.1.9/32 2.2.2.9/32 3.3.3.9/32
POS1/0/0 POS1/0/0
100.1.1.1/24 100.1.2.2/24
PE1 PE2
POS1/0/0 POS2/0/0
100.1.1.2/24 P 100.1.2.1/24
GE2/0/0.1 GE2/0/0.1
GE1/0/0.1
GE1/0/0 10.1.1.2/24
Switch
GE1/0/1
CE2
GE1/0/0
VPN1
10.1.1.1/24
CE1
VPN1
1. Configure the interface mode on PE1 to user termination.

2. Run IGP on the backbone network to ensure that routers on the backbone network can
communicate with each other
3. Enable MPLS on the backbone network and set up an LSP tunnel.
4. Set up the remote MPLS LDP peer relationship between PEs at both ends of the PW.

5. Create a Dot1q termination sub-interfaces on PE1 and connect the Dot1q termination sub-
interface to an MPLS L2VC.
6. Configure Layer 2 forwarding on the switch.
Data Preparation
l Names of the interfaces connecting PEs to CEs
l L2VC IDs at both ends of the PW (must be the same)
l MPLS LSR IDs for PEs and the P
l IP address of the remote PE peer
l Tag value of the Dot1q termination sub-interface
Procedure
Step 1 Configure the interface mode on PE1 to user termination.
# Configure PE1.
Step 2 Configure IGP on the MPLS backbone network. In this example, OSPF is configured.
Assign an IP address to each interface on each PE and the P as shown in Figure 5-15. After
OSPF is enabled, the 32-bit loopback addresses of PE1, P, and PE2 must be advertised.
# Configure PE1.
[PE1-Pos1/0/0] ip address 100.1.1.1 24
[PE1-Pos1/0/0] quit
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure the P.
[HUAWEI] sysname P
[P-LoopBack1] quit
[P-Pos1/0/0] ip address 100.1.1.2 24
[P-Pos1/0/0] quit

[P-Pos2/0/0] ip address 100.1.2.1 24

[P-Pos2/0/0] quit
[P] ospf
[P-ospf-1] area 0
[P-ospf-1] quit
# Configure PE2.
[PE2-Pos1/0/0] ip address 100.1.2.2 24
[PE2-Pos1/0/0] quit
[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
After the preceding configuration, PE1 and PE2 have routes discovered through OSPF to
Loopback 1 of each other. This indicates that PE1 and PE2 can ping through each other.
Take the display on PE1 as an example.

------------------------------------------------------------------------------
2.2.2.9/32 OSPF 10 2 D 100.1.1.2 Pos1/0/0
3.3.3.9/32 OSPF 10 3 D 100.1.1.2 Pos1/0/0
100.1.1.0/24 Direct 0 0 D 100.1.1.1 Pos1/0/0
100.1.1.2/32 Direct 0 0 D 100.1.1.2 Pos1/0/0
100.1.2.0/24 OSPF 10 2 D 100.1.1.2 Pos1/0/0
<PE1> ping 100.1.2.2
0.00% packet loss
Step 3 Enable basic MPLS capabilities and LDP on the MPLS backbone network.
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit

[PE1] mpls ldp

[PE1-mpls-ldp] quit
[PE1-Pos1/0/0] mpls
[PE1-Pos1/0/0] quit
# Configure the P.
[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
[P-Pos1/0/0] mpls
[P-Pos1/0/0] quit
[P-Pos2/0/0] mpls
[P-Pos2/0/0] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2-Pos1/0/0] mpls
[PE2-Pos1/0/0] quit
After the preceding configurations, LDP sessions can be set up between PE1 and P, and between
PE2 and P. After running the display mpls ldp session command, you can view that the status
of the LDP sessions is Operational. After running the display mpls ldp lsp command, you can
view whether LDP LSPs are set up.

------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
LDP LSP Information
------------------------------------------------------------------------------
------------------------------------------------------------------------------
1 1.1.1.9/32 3/NULL 127.0.0.1 Pos1/0/0/InLoop0
2 2.2.2.9/32 NULL/3 100.1.1.2 -------/Pos1/0/0
3 3.3.3.9/32 NULL/1024 100.1.1.2 -------/Pos1/0/0
------------------------------------------------------------------------------
Step 4 Set up remote LDP sessions between PEs.
# Configure PE1.

[PE1] mpls ldp remote-peer 1

[PE1-mpls-ldp-remote-1] remote-ip 3.3.3.9
[PE1-mpls-ldp-remote-1] quit
# Configure PE2.
After the preceding configurations, LDP sessions can be set up between PE1 and PE2. After
running the display mpls ldp session command, you can view that the status of the LDP sessions
is Operational. After running the display mpls ldp lsp command, you can view whether LDP
LSPs are set up.
------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
LDP LSP Information
------------------------------------------------------------------------------
------------------------------------------------------------------------------
1 1.1.1.9/32 3/NULL 127.0.0.1 Pos1/0/0/InLoop0
2 1.1.1.9/32 3/NULL 127.0.0.1 Pos1/0/0/InLoop0
*3 1.1.1.9/32 Liberal
4 2.2.2.9/32 NULL/3 100.1.1.2 -------/Pos1/0/0
5 2.2.2.9/32 1024/3 100.1.1.2 -------/Pos1/0/0
*6 2.2.2.9/32 Liberal
7 3.3.3.9/32 NULL/1025 100.1.1.2 -------/Pos1/0/0
8 3.3.3.9/32 1025/1025 100.1.1.2 -------/Pos1/0/0
*9 3.3.3.9/32 Liberal
------------------------------------------------------------------------------
Step 5 Configure a Dot1q termination sub-interface to an L2VPN and configure the L2VPN to provide
heterogeneous transport (transport media of different types across the L2VPN can communicate
with each other).
# Configure PE1.
[PE1] mpls l2vpn
[PE1-l2vpn] quit
# Configure PE2.
[PE2] mpls l2vpn
[PE1-l2vpn] quit


Step 6 Configure the switch to add a VLAN tag with the VLAN ID being 100 to the packets sent to
PE1.
Configure the switch to add a VLAN tag with the VLAN ID being 100 to the packet received
on GE 1/0/1. Specify GE 1/0/0 as a trunk interface and configure it to allow the packets from
VLAN 100 to pass through.
[HUAWEI] sysname switch
[switch] vlan 100
[switch-vlan10] quit
[switch] interface gigabitethernet 1/0/1
[switch-GigabitEthernet1/0/1] port default vlan 100
[switch-GigabitEthernet1/0/1] quit
[switch-GigabitEthernet1/0/0] port trunk allow-pass vlan 100
Step 7 Assign IP addresses to the interfaces on CEs.

# Configure CE1.
[CE1-GigabitEthernet1/0/0] ip address 10.1.1.1 24
# Configure CE2.
[CE2] interface gigabitethernet 1/0/0.1
[CE2-GigabitEthernet1/0/0.1] vlan-type dot1q 200

Run the display dot1q information termination command, and you can view that the Dot1q
termination sub-interface is bound to the L2VPN.
<PE1> display dot1q information termination interface gigabitethernet 2/0/0.1
VLL/PWE3 binded
Total QinQ Num: 1
qinq termination vid 100
Check the L2VPN connections on PEs. You can find that an L2VC connection is set up and is
in the Up state.
<PE1> display mpls l2vc interface gigabitethernet 2/0/0.1
*client interface : GigabitEthernet2/0/0.1 is up
session state : up
AC state : up

VC state : up
VC ID : 101
VC type : VLAN
local group ID : 0 remote group ID : 0
local AC OAM State : up
local PSN State : up
local forwarding state : forwarding
remote AC OAM state : up
remote PSN state : up
remote forwarding state: forwarding
BFD for PW : unavailable
forwarding entry : exist
link state : up
local VCCV : Disable
remote VCCV : alert lsp-ping bfd
local control word : disable remote control word : disable
traffic behavior name : --
VC tunnel/token info : 1 tunnels/tokens
NO.0 TNL type : lsp , TNL ID : 0x2008002
Hosts in the same VLAN of CEs can ping through each other.
Take the display on CE1 as an example.
<CE1> ping 10.1.1.2
0.00% packet loss
----End
Configuration File
#
sysname CE1
#
ip address 10.1.1.1 255.255.255.0
#
return

#
sysname CE2
#
vlan-type dot1q 200
ip address 10.1.1.2 255.255.255.0

#
return
l Configuration file of switch
#
sysname switch
#
vlan batch 100
#
undo shutdown
#
undo shutdown
#
return
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
mpls l2vpn
#
mpls ldp
#
mpls ldp remote-peer 1
remote-ip 3.3.3.9
#
undo shutdown
#
mpls l2vc 3.3.3.9 101
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 100.1.1.0 0.0.0.255
#
return
l Configuration file of the P
#
sysname P
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
interface Pos1/0/0
link-protocol ppp

undo shutdown
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 100.1.2.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 100.1.1.0 0.0.0.255
network 100.1.2.0 0.0.0.255
#
return

#
sysname PE2
#
mpls lsr-id 3.3.3.9
mpls
mpls l2vpn
#
mpls ldp
#
remote-ip 1.1.1.9
#
vlan-type dot1q 200
mpls l2vc 1.1.1.9 101
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.2.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 100.1.2.0 0.0.0.255
#
return

Tag Termination to Access a VLL
PEs are connected through an L2VPN; user packets sent to the PEs carry double tags. This
example describes how to communicate through an L2VPN and how to configure sub-interfaces
for QinQ VLAN tag termination and L2VPNs.

As shown in Figure 5-16, GE 1/0/0.1 of CE1 is connected to PE1 through Switch. Configure
QinQ on Switch. A packet from CE1 is then added with an outer VLAN tag with the VLAN ID
as 100 to save public VLAN IDs. In this example Martini is adopted. Then the packet sent from
Switch to PE1 carries double VLAN tags. CE2 accesses PE2 through a common sub-interface.
It is required that the sub-interface for QinQ VLAN tag termination on PE1 be configured to
access a VLL; the common sub-interface on PE2 be configured to access the VLL. The user
networks connected CE1 and CE2 can thus communicate.
NOTE
At both ends of a VLL, an unsymmetric sub-interface for QinQ VLAN tag termination can communicate
with other types of AC interfaces; a symmetric sub-interface for QinQ VLAN tag termination can
communicate with only symmetric sub-interfaces for QinQ VLAN tag termination.
termination to access a VLL
1.1.1.9/32 2.2.2.9/32 3.3.3.9/32
POS1/0/0 POS1/0/0
100.1.1.1/24 100.1.2.2/24
PE1 PE2
POS1/0/0 POS2/0/0
100.1.1.2/24 P 100.1.2.1/24
GE2/0/0.1 GE2/0/0.1
GE1/0/0.1
GE1/0/0 10.1.1.2/24
Switch
GE1/0/1
CE2
GE1/0/0.1
VPN1
10.1.1.1/24
CE1
VPN1
1. Configure the interface mode to user termination on PE1.
2. Configure IGP run on the MPLS backbone network, implementing inter-communication
between routers on the backbone network.
3. Enable the basic MPLS capabilities on the MPLS backbone network and establish an LSP
tunnel.
4. Set up MPLS LDP peer relationship between PEs on two ends of a Pseudo Wire (PW).
5. Configure the Layer 2 forwarding function and QinQ on switches.
6. Create a MPLS L2VC connection between PEs.

Data Preparation
l Name of PE interface connected to CE
l Consistent L2VC IDs on the both ends of PW
l MPLS LSR-IDs on PEs and P
l IP address of the PE peer
l Tag value of the sub-interface for QinQ VLAN tag termination
Procedure
# Configure PE1.
OSPF to advertise the addresses of the loopback interfaces on PE1, P, and PE2.
# Configure PE1.
[PE1-Pos1/0/0] ip address 100.1.1.1 24
[PE1-Pos1/0/0] quit
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure P.
[HUAWEI] sysname P
[P-LoopBack1] quit
[P-Pos1/0/0] ip address 100.1.1.2 24
[P-Pos1/0/0] quit
[P-Pos2/0/0] ip address 100.1.2.1 24
[P-Pos2/0/0] quit
[P] ospf
[P-ospf-1] area 0

[P-ospf-1] quit
# Configure PE2.
[PE2-Pos1/0/0] ip address 100.1.2.2 24
[PE2-Pos1/0/0] quit
[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
------------------------------------------------------------------------------
2.2.2.9/32 OSPF 10 2 D 100.1.1.2 Pos1/0/0
3.3.3.9/32 OSPF 10 3 D 100.1.1.2 Pos1/0/0
100.1.1.0/24 Direct 0 0 D 100.1.1.1 Pos1/0/0
100.1.1.2/32 Direct 0 0 D 100.1.1.2 Pos1/0/0
100.1.2.0/24 OSPF 10 2 D 100.1.1.2 Pos1/0/0
<PE1> ping 100.1.2.2
0.00% packet loss
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
[PE1-Pos1/0/0] mpls
[PE1-Pos1/0/0] quit
# Configure P.

[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
[P-Pos1/0/0] mpls
[P-Pos1/0/0] quit
[P-Pos2/0/0] mpls
[P-Pos2/0/0] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2-Pos1/0/0] mpls
[PE2-Pos1/0/0] quit
After the preceding configurations, LDP sessions are set up between PE1 and P, and between P
and PE1. Running the display mpls ldp session command, you can see the Status field is
"Operational". Run the display mpls ldp lsp command to view the establishing status of
LDPLSP.

------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
LDP LSP Information
------------------------------------------------------------------------------
------------------------------------------------------------------------------
1 1.1.1.9/32 3/NULL 127.0.0.1 Pos1/0/0/InLoop0
2 2.2.2.9/32 NULL/3 100.1.1.2 -------/Pos1/0/0
3 3.3.3.9/32 NULL/1025 100.1.1.2 -------/Pos1/0/0
------------------------------------------------------------------------------
# Configure PE1.
# Configure PE2.

After the configuration, the sessions between PE1 and P and between PE2 and P are set up.
Running the display mpls ldp session command, you can view that the Status field is
"Operational". Running the display mpls ldp lsp command, you can view the establishing status
of LDP LSP.

------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
LDP LSP Information
------------------------------------------------------------------------------
------------------------------------------------------------------------------
1 1.1.1.9/32 3/NULL 127.0.0.1 P1/0/0/InLoop0
2 1.1.1.9/32 3/NULL 127.0.0.1 -------/InLoop0
*3 1.1.1.9/32 Liberal
4 2.2.2.9/32 NULL/3 100.1.1.2 -------/P1/0/0
5 2.2.2.9/32 1024/3 100.1.1.2 -------/P1/0/0
*6 2.2.2.9/32 Liberal
7 3.3.3.9/32 NULL/1025 100.1.1.2 -------/P1/0/0
8 3.3.3.9/32 1025/1025 100.1.1.2 -------/P1/0/0
*9 3.3.3.9/32 Liberal
------------------------------------------------------------------------------
Step 5 Enable MPLS L2VPN and create a VC. Configure the sub-interface for QinQ VLAN tag
termination.
# Configure PE1.
[PE1] mpls l2vpn
[PE1-l2vpn] quit
# Configure PE2.
[PE2] mpls l2vpn
[PE2-l2vpn] quit
Step 6 Configure QinQ so that a packet sent from the switch to the PE1 carries double VLAN tags.
Configure GE 1/0/1 on Switch to add an outer VLAN tag with the VLAN ID as 100 to a packet
of VLAN 10. Specify GE 1/0/0 as a trunk interface and configure it to allow the packets of
VLAN 100 to pass through.

[HUAWEI] sysname switch
[switch] vlan 100
[switch-vlan10] quit
[switch-GigabitEthernet1/0/1] port vlan-stacking vlan 10 stack-vlan 100
[switch-GigabitEthernet1/0/0] port trunk allow-pass vlan 100
Step 7 Configure IP addresses of the interfaces of the CEs.

# Configure CE1.
# Configure CE2.

Running the display qinq information command, you can view the QinQ terminating
information.
For example, the following displays the stacking information on PE1:
<PE1> display qinq information termination interface gigabitethernet 2/0/0.1
VLL/PWE3 binded
Total QinQ Num: 1
VLL/PWE3 binded
Total QinQ Num: 1
View the L2VPN information on the PE. You can find that an L2 VA is created and is Up.
<PE1> display mpls l2vc
session state : up
AC status : up
VC state : up
VC ID : 101
VC type : VLAN


local group ID : 0
link state : up
On CEs, the attached hosts can ping through each other if they are in the same VLAN.
Take the display on CE1 as an example:
<CE1> ping 10.1.1.2
0.00% packet loss
----End
Configuration Files
#
sysname CE1
#
vlan-type dot1q 10
ip address 10.1.1.1 255.255.255.0
#
return

#
sysname CE2
#
vlan-type dot1q 10
ip address 10.1.1.2 255.255.255.0
#
return
l Configuration file of switch

#
sysname switch
#
vlan batch 100
#
undo shutdown
#
undo shutdown

#
return
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
mpls ldp
#
remote-ip 3.3.3.9
#
undo shutdown
#
mpls l2vc 3.3.3.9 101
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 100.1.1.0 0.0.0.255
#
return
#
sysname P
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 100.1.2.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255

#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 100.1.1.0 0.0.0.255
network 100.1.2.0 0.0.0.255
#
return

#
sysname PE2
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
mpls ldp
#
remote-ip 1.1.1.9
#
vlan-type dot1q 10
mpls l2vc 1.1.1.9 101
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.2.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 100.1.2.0 0.0.0.255
#
return
5.14.11 Example for Configuring the Sub-interface for dot1q and

QinQ VLAN Tag Termination to Access a VPLS
PEs are connected through a VPLS network; user packets sent to PEs carry one tag and double
tags respectively. This example describes how to communicate through a VPLS network and
how to configure sub-interfaces for dot1q VLAN tag termination, sub-interfaces for QinQ
VLAN tag termination, and VPLS networks.
As shown in Figure 5-17, CE1 and CE2 are connected to PE1and PE2 through switches. CE3
is connected to PE3 through a sub-interface. A packet sent from CE1 to Switch 1 carries one
VLAN tag; the packet sent from CE2 to Switch 2 carries no VLAN tag. The Switch then labels
the packets from the CE with outer tags based on the inbound interface and then sends the packets
to the PE. It is required to configure the sub-interface for QinQ VLAN tag termination on PE1
and the sub-interface for dot1q VLAN tag termination on PE2 to access VPLS to implement
inter-communication between CEs 1 to 3. The backbone network adopts Martini VPLS and uses
LDP to set up PWs.

Figure 5-17 Typical networking diagram of configuring the sub-interface for dot1q and QinQ
VLAN tag termination to access VPLS
VPN1
CE3
GE1/0/0.1
10.1.1.3/24
GE2/0/0.1
POS1/0/1
POS1/0/0 100.1.2.1/30
100.1.1.2/30
PE3
Loopback1
3.3.3.9/32
POS1/0/1 POS1/0/1
100.1.1.1/30 100.1.2.2/30
POS1/0/0 POS1/0/0
Loopback1 100.1.3.1/30 100.1.3.2/30 Loopback1
1.1.1.9/32 2.2.2.9/32
PE1 GE2/0/0.1 GE2/0/0.1 PE2
GE1/0/0 GE1/0/0
Switch1 Switch2
GE1/0/1 GE1/0/1
GE1/0/0.1 GE1/0/0
10.1.1.1/24 10.1.1.2/24
CE1 CE2
VPN1 VPN1
VLAN10 VLAN10
1. Configure the interface mode to user termination on PEs.

2. Run IGP on the backbone network and interconnect the routers on the backbone network.
3. Configure the routing protocol on the backbone network to interconnect the routers and
enable the basic MPLS capabilities.
4. Set up the LSP tunnel between PEs.
5. Enable MPLS L2VPN on PE.
6. Configure the Layer 2 forwarding function on switches.
7. Bind the AC interface to the VSI.

Data Preparation
l MPLS LSR-IDs on PEs
l VSI names on PE1, PE2, and PE3
l Interface bound to VSI
Procedure
# Configure PE1.
# Configure PE2.
OSPF to advertise the addresses of the loopback interfaces on PE1, PE2, and PE3.
# Configure PE1.
[PE1-Pos1/0/0] ip address 100.1.3.1 30
[PE1-Pos1/0/0] quit
[PE1-Pos1/0/1] ip address 100.1.1.1 30
[PE1-Pos1/0/1] quit
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure PE2.
[PE2] interface LoopBack 1
[PE2-Pos1/0/0] ip address 100.1.3.2 30
[PE2-Pos1/0/0] quit
[PE2-Pos1/0/1] ip address 100.1.2.2 30

[PE2-Pos1/0/1] quit
[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
# Configure PE3.
[PE3-Pos1/0/0] ip address 100.1.1.2 30
[PE3-Pos1/0/0] quit
[PE3-Pos1/0/1] ip address 100.1.2.1 30
[PE3-Pos1/0/1] quit
[PE3] ospf
[PE3-ospf-1] area 0
[PE3-ospf-1] quit
After the preceding step, PE1 and PE2 both have routes, discovered through OSPF, to the
loopback1 interface of each other. PE1 and PE3 also have routes, discovered through OSPF, to
the loopback1 interface of each other.
------------------------------------------------------------------------------
2.2.2.9/32 OSPF 10 2 D 100.1.3.2 Pos1/0/0
3.3.3.9/32 OSPF 10 2 D 100.1.1.2 Pos1/0/1
100.1.1.0/30 Direct 0 0 D 100.1.1.1 Pos1/0/1
100.1.1.2/32 Direct 0 0 D 100.1.1.2 Pos1/0/1
100.1.2.0/30 OSPF 10 2 D 100.1.1.2 Pos1/0/1
OSPF 10 2 D 100.1.3.2 Pos1/0/0
100.1.3.0/30 Direct 0 0 D 100.1.3.1 Pos1/0/0
100.1.3.2/32 Direct 0 0 D 100.1.3.2 Pos1/0/0
<PE1> ping 100.1.2.2
0.00% packet loss

# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
[PE1-Pos1/0/0] mpls
[PE1-Pos1/0/0] quit
[PE1-Pos1/0/1] mpls
[PE1-Pos1/0/1] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2] interface pos1/0/0
[PE2-Pos1/0/0] mpls
[PE2-Pos1/0/0] quit
[PE2-Pos1/0/1] mpls
[PE2-Pos1/0/1] quit
# Configure PE3.
[PE3] mpls
[PE3-mpls] quit
[PE3] mpls ldp
[PE3-mpls-ldp] quit
[PE3-Pos1/0/0] mpls
[PE3-Pos1/0/0] quit
[PE3-Pos1/0/1] mpls
[PE3-Pos1/0/1] quit
After the preceding configurations, LDP sessions are set up between PEs. Running the display
mpls ldp session command, you can view that the Status field is "Operational". Running the
display mpls ldp lsp command, you can view the establishing status of LSP through LDP.
------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
LDP LSP Information
------------------------------------------------------------------------------
------------------------------------------------------------------------------

1 1.1.1.9/32 3/NULL 127.0.0.1 Pos1/0/0/InLoop0

2 1.1.1.9/32 3/NULL 127.0.0.1 Pos1/0/1/InLoop0
3 2.2.2.9/32 NULL/3 100.1.3.2 -------/Pos1/0/0
4 2.2.2.9/32 1025/3 100.1.3.2 Pos1/0/1/Pos1/0/0
*5 2.2.2.9/32 Liberal
6 3.3.3.9/32 NULL/3 100.1.1.2 -------/Pos1/0/1
7 3.3.3.9/32 1024/3 100.1.1.2 Pos1/0/0/Pos1/0/1
*8 3.3.3.9/32 Liberal
9 100.1.1.0/30 3/NULL 100.1.1.1 Pos1/0/0/Pos1/0/1
10 100.1.2.0/30 NULL/3 100.1.3.2 -------/Pos1/0/0
NULL/3 100.1.1.2 -------/Pos1/0/1
12 100.1.3.0/30 3/NULL 100.1.3.1 Pos1/0/1/Pos1/0/0
------------------------------------------------------------------------------
NOTE
If PEs are not directly connected, run the mpls ldp remote-peer command and the remote-ip command
to set up a remote LDP sessions between PEs.

# Configure PE1.
[PE1] mpls l2vpn
# Configure PE2.
[PE2] mpls l2vpn
# Configure PE3.
[PE3] mpls l2vpn
# Configure PE1
# Configure PE2.
# Configure PE3.
Step 6 Bind VSIs and AC interfaces.

# Configure PE1.


# Configure PE2.
# Configure PE3.
Step 7 Configure Layer 2 forwarding.

Create VLAN 100 on Switch 1. Configure GE 1/0/1 to add an outer VLAN tag with the VLAN
ID as 100 to a packet of VLAN 10. Specify GE 1/0/0 as a trunk interface and configure it to
allow the packets of VLAN 100 to pass through.
[switch1] vlan 100
Create VLAN 10 on Switch 2. Specify GE 1/0/1 as an access interface and add it to VLAN 10.
Specify GE 1/0/0 as a trunk interface and configure it to allow the packets of VLAN 10 to pass
through.
[switch2] vlan 10
# Configure IP addresses of the interfaces on CEs as shown in Figure 5-17.

# Configure CE1.
# Configure CE2.

# Configure CE3.

Run the display qinq information termination interface command. You can view QinQ
configuration.
VSI binded
Total QinQ Num: 2
Run the display dot1q information termination interface command. You can view dot1q
configuration.
VSI binded
Total QinQ Num: 2
You can view that the VSI named ldp1 sets up PWs to PE2 and PE3 and the VSI status is Up.
VSI ID : 22
***VSI Name : ldp1
VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
VSI State : up
VSI ID : 2
VC Label : 23552
Peer Type : dynamic
Session : up

VC Label : 23553
Peer Type : dynamic
Session : up
State : up
**PW Information:
PW State : up
PW Type : label
PW State : up
PW Type : label
Hosts attached to CE1, CE2, and CE3 can ping through each other.
<CE1> ping 10.1.1.2
0.00% packet loss
<CE1> ping 10.1.1.3
0.00% packet loss
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 2
peer 3.3.3.9
peer 2.2.2.9
#
mpls ldp

#
undo shutdown
#
l2 binding vsi ldp1
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.3.1 255.255.255.252
mpls
mpls ldp
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 100.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 100.1.1.0 0.0.0.3
network 100.1.3.0 0.0.0.3
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
peer 3.3.3.9
#
mpls ldp
#
undo shutdown
#
l2 binding vsi ldp1
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.3.2 255.255.255.252
mpls
mpls ldp
#
interface Pos1/0/1
link-protocol ppp

undo shutdown
ip address 100.1.2.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 100.1.3.0 0.0.0.3
network 100.1.2.0 0.0.0.3
#
return
#
sysname PE3
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
peer 2.2.2.9
#
mpls ldp
#
vlan-type dot1q 10
l2 binding vsi ldp1
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 100.1.2.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 100.1.1.0 0.0.0.3
network 100.1.2.0 0.0.0.3
#
return
#
sysname CE1
#
vlan-type dot1q 10
ip address 10.1.1.1 255.255.255.0
#

return

#
sysname CE2
#
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
return

#
sysname CE3
#
vlan-type dot1q 10
ip address 10.1.1.3 255.255.255.0
#
return

#
sysname switch1
#
vlan batch 100
#
undo shutdown
#
undo shutdown
#
return

#
sysname switch2
#
vlan batch 10
#
undo shutdown
#
undo shutdown
#
return

Tag Termination to Access a VPLS Network
PEs are connected through a VPLS network. Each of the user packets sent to the PEs carries
double tags. This example shows how to configure the users to communicate through the VPLS
network and how to configure the VPLS network and sub-interfaces for QinQ VLAN tag
termination.

As shown in Figure 5-18, VLAN 10 and VLAN 20 are connected to PEs through switches. The
packet sent from the switch to the switch carries double VLAN tags. It is required to configure
the sub-interface for QinQ VLAN tag termination to access VPLS to implement interworking
between CE1, CE2, and CE3, and between CE4, CE5, and CE6. The backbone network adopts
Martini VPLS and uses LDP to set up PWs.
Considering that the interworking is not required between CE1 (or CE2 and CE3) and CE4 (or
CE5 and CE6), in this example, the sub-interface for QinQ VLAN tag termination access VPLS
in symmetric mode. The switch uniformly labels the packets from CEs with outer VLAN tags
(tag 100), so a user can communicate with only the user in the same VLAN.
termination to access a VPLS Network
VPN1 VPN1
VLAN10 VLAN20
CE3 CE6
GE1/0/0 GE1/0/0
10.1.1.3/24 20.1.1.3/24
GE1/0/1 GE1/0/2
Switch3
GE1/0/0
GE2/0/0.1
POS1/0/0 POS1/0/1
100.1.1.2/30 100.1.2.1/30
PE3
Loopback1
3.3.3.9/32
POS1/0/1 POS1/0/1
100.1.1.1/30 100.1.2.2/30
POS1/0/0 POS1/0/0
1.1.1.9/32 2.2.2.9/32
PE1 GE2/0/0.1 GE2/0/0.1 PE2
GE1/0/0 GE1/0/0
Switch1 Switch2
GE1/0/1 GE1/0/2 GE1/0/1 GE1/0/2
GE1/0/0.1 GE1/0/0.1 GE1/0/0.1 GE1/0/0.1
10.1.1.1/24 20.1.1.1/24 10.1.1.2/24 20.1.1.2/24
CE1 CE4 CE2 CE5

VPN1 VPN1 VPN1 VPN1

1. Run IGP on the backbone network and interconnect the devices on the backbone network.
2. Configure the routing protocol on the backbone network to interconnect the devices and
enable the basic MPLS capabilities.
4. Enable MPLS L2VPN on PE.
5. Create and then configure the VSI.
6. Configure the sub-interface for QinQ VLAN tag termination and bind the AC interface to
the VSI.
7. Configure the Layer 2 forwarding function and QinQ function on switches.
Data Preparation

l VSI IDs on the PEs (The IDs must be consistent)
Procedure
# Configure PE1.
# Configure PE2.
# Configure PE3.

According to Figure 5-18, configure IP addresses of interfaces on PEs. Configure OSPF to

advertise the addresses of the loopback interfaces on PE1, PE2, and PE3.
# Configure PE1.
[PE1-Pos1/0/0] ip address 100.1.3.1 30
[PE1-Pos1/0/0] quit
[PE1-Pos1/0/1] ip address 100.1.1.1 30
[PE1-Pos1/0/1] quit
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure PE2.
[PE2-Pos1/0/0] ip address 100.1.3.2 30
[PE2-Pos1/0/0] quit
[PE2-Pos1/0/1] ip address 100.1.2.2 30
[PE2-Pos1/0/1] quit
[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
# Configure PE3.
[PE3-Pos1/0/0] ip address 100.1.1.2 30
[PE3-Pos1/0/0] quit
[PE3-Pos1/0/1] ip address 100.1.2.1 30
[PE3-Pos1/0/1] quit
[PE3] ospf
[PE3-ospf-1] area 0
[PE3-ospf-1] quit


------------------------------------------------------------------------------
2.2.2.9/32 OSPF 10 2 D 100.1.3.2 Pos1/0/0
3.3.3.9/32 OSPF 10 2 D 100.1.1.2 Pos1/0/1
100.1.1.0/30 Direct 0 0 D 100.1.1.1 Pos1/0/1
100.1.1.2/32 Direct 0 0 D 100.1.1.2 Pos1/0/1
100.1.2.0/30 OSPF 10 2 D 100.1.1.2 Pos1/0/1
OSPF 10 2 D 100.1.3.2 Pos1/0/0
100.1.3.0/30 Direct 0 0 D 100.1.3.1 Pos1/0/0
100.1.3.2/32 Direct 0 0 D 100.1.3.2 Pos1/0/0
[PE1] ping 100.1.2.2
0.00% packet loss
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
[PE1-Pos1/0/0] mpls
[PE1-Pos1/0/0] quit
[PE1-Pos1/0/1] mpls
[PE1-Pos1/0/1] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2-Pos1/0/0] mpls
[PE2-Pos1/0/0] quit
[PE2-Pos1/0/1] mpls
[PE2-Pos1/0/1] quit
# Configure PE3.


[PE3] mpls
[PE3-mpls] quit
[PE3] mpls ldp
[PE3-mpls-ldp] quit
[PE3-Pos1/0/0] mpls
[PE3-Pos1/0/0] quit
[PE3-Pos1/0/1] mpls
[PE3-Pos1/0/1] quit
After the preceding configuration, LDP sessions are set up between PEs. Running the display
mpls ldp session command, you can view that the status is "Operational".
------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
NOTE
Step 4 Enable MPLS L2VPN on the PE.

# Configure PE1.
[PE1] mpls l2vpn
# Configure PE2.
[PE2] mpls l2vpn
# Configure PE3.
[PE3] mpls l2vpn
# Configure PE1.
# Configure PE2.
# Configure PE3.


Step 6 Configure the sub-interface for QinQ VLAN tag termination and bind VSIs and AC interfaces.
# Configure PE1.
# Configure PE2.
# Configure PE3.
NOTE
Step 7 Configure QinQ and set the packets sent from the switch to the PE to carry double tags.
[Switch1] vlan 100


[Switch2] vlan 100
[Switch3] vlan 100
[Switch3-GigabitEthernet1/0/1] undo shutdonw
NOTE
Configure IP addresses of the interfaces on CEs based on Figure 5-18. Set the packet sent from
the CE to the switch to carry one VLAN tag.
# Configure CE1.
# Configure CE2.
# Configure CE3.


# Configure CE4.
# Configure CE5.
# Configure CE6.

Running the display qinq information termination interface command, you can view the
QinQ information.
The following displays the QinQ information on PE1:
VSI bound
Total QinQ Num: 2
you can find that PWs to PE2 and PE3 are set up on the VSI named ldp1. The VSI status is Up.
***VSI Name : ldp1
VSI Index : 0
PW Signaling : ldp
MTU : 1500
Mode : uniform
Service Class : --
Color : --
DomainId : 0
Domain Name :
VSI State : up

VSI ID : 2
VC Label : 142336
Peer Type : dynamic
Session : up
VC Label : 142337
Peer Type : dynamic
Session : up
State : up
**PW Information:
PW State : up
PW Type : label
PW State : up
PW Type : label
The hosts attached to CE1, CE2, and CE3 can ping through each other.
[CE1] ping 10.1.1.2
0.00% packet loss
[CE1] ping 10.1.1.3
0.00% packet loss
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
vsi ldp1 static

pwsignal ldp
vsi-id 2
peer 3.3.3.9
peer 2.2.2.9
#
mpls ldp
#
undo shutdown
#
undo shutdown
l2 binding vsi ldp1
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.3.1 255.255.255.252
mpls
mpls ldp
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 100.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 100.1.1.0 0.0.0.3
network 100.1.3.0 0.0.0.3
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
peer 3.3.3.9
#
mpls ldp
#
undo shutdown
#
undo shutdown


l2 binding vsi ldp1
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.3.2 255.255.255.252
mpls
mpls ldp
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 100.1.2.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 100.1.3.0 0.0.0.3
network 100.1.2.0 0.0.0.3
#
return
#
sysname PE3
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
peer 2.2.2.9
#
mpls ldp
#
undo shutdown
#
undo shutdown
l2 binding vsi ldp1
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 100.1.2.1 255.255.255.252
mpls
mpls ldp

#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 100.1.1.0 0.0.0.3
network 100.1.2.0 0.0.0.3
#
return
#
sysname Switch1
#
vlan batch 100
#
undo shutdown
#
undo shutdown
#
undo shutdown
#
return
#
sysname Switch2
#
vlan batch 100
#
undo shutdown
#
undo shutdown
#
undo shutdown
#
return
#
sysname Switch3
#
vlan batch 100
#
undo shutdown
#
undo shutdown
#
undo shutdown
#

return

#
sysname CE1
#
undo shutdown
vlan-type dot1q 10
ip address 10.1.1.1 255.255.255.0
#
return

#
sysname CE2
#
undo shutdown
vlan-type dot1q 10
ip address 10.1.1.2 255.255.255.0
#
return

#
sysname CE3
#
undo shutdown
vlan-type dot1q 10
ip address 10.1.1.3 255.255.255.0
#
return

#
sysname CE4
#
undo shutdown
vlan-type dot1q 20
ip address 20.1.1.1 255.255.255.0
#
return

#
sysname CE5
#
undo shutdown
vlan-type dot1q 20
ip address 20.1.1.2 255.255.255.0
#
return

#
sysname CE6
#
undo shutdown
vlan-type dot1q 20
ip address 20.1.1.3 255.255.255.0
#
return

5.14.13 Example for Configuring a Sub-interface for QinQ VLAN

Tag Termination to Support the Local Connection
Different CEs access the same VSI of a PE. The packets sent from the CEs to the PE carry double
tags and the outer tags are same. It is required that CEs communicate with each other.
As shown in Figure 5-19, PE1 and PE2 are configured with the basic VPLS function. CE1 and
CE2 access the VSI on PE1 through switches. In Figure 5-19:
l The packets sent from CE1 and CE2 to PE1 have double tags.
l Switch2 labels the packets received from CE1 with the inner tag 10. Switch3 labels the
packets received from CE2 with the inner tag 20.
l Switch1 labels the packets received from CE1 and CE2 with the same outer tag 100.
If PE1 is configured with QinQ termination sub-interface accessing the VPLS network, the
packets sent by these CEs cannot be forwarded by GE 1/0/0 because packets from CE1/0/0 to
PE1 have the same outer tag (otherwise, Switch1 learns the same MAC address entry from
different interfaces, which leads to incorrect forwarding). Thus, CEs in the same VSI on PE1
cannot communicate. In this case, to ensure that CE1 and CE2 can communicate, you can
configure the QinQ termination sub-interface to support the local switching.
Figure 5-19 QinQ termination sub-interface supporting the local switching
VSI:v1
VSI:v1
MPLS/IP core PE2
PE1
GE1/0/0
VLAN trunk 100 QinQ termination
GE1/0/0
VLAN stacking 100 GE2/0/0 GE3/0/0 VLAN stacking 100
Switch1
VLAN trunk 10
VLAN trunk 20
GE2/0/0 GE2/0/0
Switch2 Switch3
GE1/0/0 GE1/0/0
VLAN10
VLAN20
GE1/0/0 GE1/0/0
10.1.1.1/24 10.1.1.2/24
CE1 CE2

1. Configure the basic VPLS function on the PEs and ensure that the VSIs on the PEs are Up.
2. On PE1, configure the QinQ termination sub-interface to support the local switching and
configure the QinQ termination sub-interface to access the VPLS network. After the
configuration, CEs in the same VSI can communicate.
3. Configure the Layer 2 forwarding function on the switches. After the configuration, the
packets received on the PEs from the CEs have double tags with the outer tags being the
same.
4. Disable the MAC address learning on the switches connected to the termination sub-
interface on the PEs.
Data Preparation
l IP addresses of the interfaces
l L2VC IDs on the two ends of the PW (IDs are the same)
l MPLS LSR ID of the PEs
l VSI names of the PEs
l Interfaces bound to the VSIs
Procedure
Step 1 Configure the mode of the interface connected to PE1 as user-termination.
Step 2 Configure IGP, MPLS, LDP, and VPLS between the PEs.
The detailed configurations are not mentioned here. After the configuration, run the display
vsi command on PE1 and PE2, and you can find that the VSI status is Up. Take PE1 as an
example.
[PE1] display vsi
Total VSI number is 1, 1 is up, 0 is down, 1 is LDP mode, 0 is BGP mode
Vsi Mem PW Mac Encap Mtu Vsi
Name Disc Type Learn Type Value State
--------------------------------------------------------------------------
v1 static ldp unqualify vlan 1500 up
Step 3 Configure the QinQ termination sub-interface to support the local switching and to access the
VPLS network.
On PE1, configure the QinQ termination sub-interface to support the local switching and to
access the VPLS network. After the configurations, CEs in the same VSI can communicate.
[PE1-GigabitEthernet1/0/0.1] control-vid 1 qinq-termination local-switch
[PE1-GigabitEthernet1/0/0.1] qinq termination pe-vid 100 ce-vid 1 to 20
[PE1-GigabitEthernet1/0/0.1] l2 binding vsi v1

Step 4 Configure the basic Layer 2 forwarding function. After the configuration, the packets received
on PE1 from the CEs have double tags with the outer tags being the same.
# On Switch1, label the VLAN packets from GE 2/0/0 and GE 3/0/0 with the outer tag 100, and
permit GE 1/0/0 to send these packets to PE1.
[Switch1] vlan 100
[Switch1-GigabitEthernet2/0/0] port link-type dot1q-tunnel
[Switch1-GigabitEthernet2/0/0] port default vlan 100
[Switch1-GigabitEthernet3/0/0] port link-type dot1q-tunnel
# On Switch2, label the VLAN packets from GE 1/0/0 with the tag 10, and permit GE 2/0/0 to
send these packets to Switch1.
[Switch2] vlan 10
# On Switch3, label the VLAN packets from GE 1/0/0 with the tag 20, and permit GE 2/0/0 to
send these packets to Switch1.
[Switch3] vlan 10
After the configurations, run the display vlan vlan-id command on the switches, and you can
find the interfaces added to the VLAN are Up. The VLAN trunk interface is displayed as "Tagged
port"; the default VLAN interface is displayed as "Untagged port".
Take Switch1 as an example:
[Switch1] display vlan 100
VLAN ID Type Status MAC Learning
----------------------------------------------------------

100 common enable enable

----------------
Untagged Port: GigabitEthernet2/0/0 GigabitEthernet3/0/0
----------------
Tagged Port: GigabitEthernet1/0/0
----------------
Interface Physical
Step 5 Disable the MAC address learning.
Disable the MAC address learning on Switch1. Otherwise, Switch1 learns the same MAC
address from different interfaces.
[Switch1-GigabitEthernet1/0/0] mac-address learning disable
[Switch1] undo mac-address all
# CE1 and CE2 can successfully ping each other.
Take CE1 as an example:

[CE1] ping 10.1.1.2
Reply from 10.1.1.2: bytes=56 Sequence=1 ttl=255 time = 2 ms
0.00% packet loss
# Check the MAC address entries on PE1. You can find that PE1 has learned the address of GE
1/0/0 and the values of double tags with the outer tag "PEVLAN" being the same from CE1 and
CE2.
[PE1] display mac-address dynamic 1
MAC Address VLAN/VSI PEVLAN CEVLAN Port Type Lsp
--------------------------------------------------------------------------------
00e0-fc22-18e1 v1 100 20 GigabitEthernet1/0/0 dynamic 4/65546
00e0-fc7a-5747 v1 100 10 GigabitEthernet1/0/0 dynamic 4/65556
Total 2 ,2 printed
# Run the display arp interface command on the CEs, and you can find the ARP entries of the
CEs are correct.
Take CE1 as an example:

[CE1] display arp interface gigabitethernet 1/0/0
IP ADDRESS MAC ADDRESS EXPIRE(M) TYPE INTERFACE VPN-INSTANCE
VLAN PVC
------------------------------------------------------------------------------
10.1.1.1 00e0-fc7a-5747 I GigabitEthernet1/0/0
10.1.1.2 00e0-fc22-18e1 14 D GigabitEthernet1/0/0
------------------------------------------------------------------------------
Total:2 Dynamic:1 Static:0 Interface:1
----End

Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
mpls l2vpn
#
vsi v1 static
pwsignal ldp
vsi-id 100
peer 2.2.2.9
peer 3.3.3.9
#
mpls ldp
#
remote-ip 3.3.3.9
#
undo shutdown
#
undo shutdown
control-vid 1 qinq-termination local-switch
l2 binding vsi v1
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 100.1.1.0 0.0.0.255
#
return

#
sysname Switch1
#
vlan batch 100
#
undo shutdown
mac-address learning disable
#
undo shutdown
#
undo shutdown
#
return

#
sysname Switch2
#
vlan batch 10
#
undo shutdown
#
undo shutdown
#
return

#
sysname Switch3
#
vlan batch 20
#
undo shutdown
#
undo shutdown
#
return

#
sysname CE1
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
return

#
sysname CE2
#
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
return

Tag Termination to Support the DHCP Relay Function
The user packets received by the DHCP-Relay device carry one tag. If the sub-interface for dot1q
VLAN tag termination does not support the DHCP relay function, the DHCP-Relay device
regards the received packets as invalid and discards them. As a result, the DHCP client cannot
obtain IP addresses from the DHCP server.
If a local network does not have a DHCP server, the DHCP relay function can be enabled on the
router. In this manner, the DHCP Request packet from the client can be transmitted to the DHCP
server through the DHCP relay.

To receive the user packet with one tag, the sub-interface for dot1q VLAN tag termination can
be configured with the DHCP relay function.
As shown in Figure 5-20, the network segment to which the DHCP client belongs is
100.1.1.0/24, while the network segment to which the DHCP server belongs is 100.1.3.0/24.
The DHCP packets should be relayed through the router with the DHCP relay function to make
the DHCP client obtain the related configuration information such as the IP address from the
DHCP server.
The DHCP server should be assigned with an IP address pool on the network segment 100.1.1.0,
so that the DHCP server can assign appropriate IP addresses to the DHCP clients on the network
segment. You need to configure the route to the network segment 100.1.1.0 on the DHCP server.
The lease period of the addresses on the segment 100.1.1.0/24 is 10 days and 12 hours, and the
domain name is huawei.com. The DNS address is 100.1.1.2. The NetBIOS address is 100.1.1.3.
The address of the egress device is 100.1.1.1.
The packets received on the DHCP relay carries one VLAN tag.
termination to support the DHCP relay function
DHCP- Relay Pos1/0/0 DHCP- Server
100.1.2.1 24
GE2/0/0.1 Pos1/0/0
100.1.1.1 24 100.1.3.1 24
GE1/0/0
Switch
GE1/0/1
VLAN10
DHCP Client1
1. Configure the DHCP relay interface mode to user termination.

2. Configure the DHCP relay.
3. Configure the DHCP server.
4. Configure the sub-interface for dot1q termination on the DHCP relay.
Data Preparation

l IP address of the interface implementing the DHCP relay function

l Address pool range of the DHCP server
l Terminating range of the sub-interface for dot1q VLAN tag termination
Procedure
Step 1 Configure the DHCP relay interface mode to user termination.
[HUAWEI] sysname DHCP-Relay
[DHCP-Relay] interface gigabitethernet 2/0/0
[DHCP-Relay-GigabitEthernet2/0/0] undo shutdown
[DHCP-Relay-GigabitEthernet2/0/0] mode user-termination
[DHCP-Relay-GigabitEthernet2/0/0] quit
Step 2 Configure the DHCP relay.

# Configure the address of POS 1/0/0.
[DHCP-Relay] interface pos 1/0/0
[DHCP-Relay-Pos1/0/0] undo shutdown
[DHCP-Relay-Pos1/0/0] ip address 100.1.2.1 24
[DHCP-Relay-Pos1/0/0] quit
# Enter the view of the interface on which DHCP relay is to be enabled and configure its IP
address and mask to keep it and the DHCP client on the same network segment.
[DHCP-Relay] interface gigabitethernet 2/0/0.1
[DHCP-Relay-GigabitEthernet2/0/0.1] undo shutdown
[DHCP-Relay-GigabitEthernet2/0/0.1] ip address 100.1.1.1 24
[DHCP-Relay-GigabitEthernet2/0/0.1] ip relay address 100.1.3.1
[DHCP-Relay-GigabitEthernet2/0/0.1] dhcp select relay
[DHCP-Relay-GigabitEthernet2/0/0.1] quit
Step 3 Configure the DHCP server.

# Configure the route from DHCP Server to DHCP Relay.
[HUAWEI] sysname DHCP-Server
[DHCP-Server] ip route-static 100.1.1.0 24 100.1.2.1
# Configure the IP address of POS 1/0/0.

[DHCP-Server] interface pos 1/0/0
[DHCP-Server-Pos1/0/0] undo shutdown
[DHCP-Server-Pos1/0/0] ip address 100.1.3.1 24
[DHCP-Server-Pos1/0/0] quit
# Configure the features of the DHCP address pool 1, including the IP address of the gateway,
range of IP addresses in the address pool, IP addresses forbidden to be automatically assigned,
domain name suffix of the DNS server, IP address of the DNS server, and address lease.
[DHCP-Server] ip pool 1 server
[DHCP-Server-dhcp-1] gateway 100.1.1.1 255.255.255.0
[DHCP-Server-dhcp-1] section 0 100.1.1.5 100.1.1.100
[DHCP-Server-dhcp-1] excluded-ip-address 100.1.1.1 100.1.1.3
[DHCP-Server-dhcp-1] dns-suffix huawei.com
[DHCP-Server-dhcp-1] dns-server 100.1.1.2
[DHCP-Server-dhcp-1] netbios-name-server 100.1.1.3
[DHCP-Server-dhcp-1] lease 10 12
[DHCP-Server-dhcp-1] quit
Step 4 Configure the sub-interface for dot1p VLAN tag termination on the DHCP relay.

[DHCP-Relay-GigabitEthernet2/0/0.1] control-vid 1 dot1q-termination

[DHCP-Relay-GigabitEthernet2/0/0.1] dot1q termination vid 10
[DHCP-Relay-GigabitEthernet2/0/0.1] arp broadcast enable
NOTE
l If the dot1q sub-interface is not configured with Option 82, when accessing the DHCP relay service,
the dot1q sub-interface encapsulates all the DHCP messages received from the DHCP relay with only
In this example, if dot1q termination vid 10 and dot1q termination vid 20 are configured on the
dot1q sub-interface, the sub-interface encapsulates the received DHCP messages with only VLAN 10
and sends the messages to the client side. In this case, clients in VLAN 20 cannot obtain IP addresses.
l If the dot1q sub-interface is configured with Option 82, the dot1q sub-interface encapsulates the
received DHCP messages with the corresponding VLAN IDs of the clients.

# Configure Switch.
[Switch] vlan 10
[Switch-vlan10] port gigabitethernet 1/0/1
[Switch-vlan10] quit

Run the display dhcp relay address command on the DHCP relay device to view the address
configuration of the DHCP relay device.
[DHCP-Relay] display dhcp relay address all
** GigabitEthernet2/0/0.1 DHCP Relay Address **
Dhcp Option Relay Agent IP Server IP
* - 100.1.3.1
The DHCP client can obtain an IP address allocated by the DHCP server through the DHCP
relay.
----End
Configuration Files
l Configuration file of a DHCP relay
#
sysname DHCP-Relay
#
undo shutdown
#
undo shutdown
ip address 100.1.1.1 255.255.255.0
ip relay address 100.1.3.1
dhcp select relay
#
interface Pos 1/0/0

link-protocol ppp
undo shutdown
ip address 100.1.2.1 255.255.255.0
#
return
l Configuration file of a DHCP server

#
sysname DHCP-Server
#
interface Pos 1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.3.1 255.255.255.0
#
ip pool 1 server
gateway 100.1.1.1 255.255.255.0
section 0 100.1.1.5 100.1.1.100
excluded-ip-address 100.1.1.1 100.1.1.3
dns-suffix huawei.com
dns-server 100.1.1.2
netbios-name-server 100.1.1.3
lease 10 12
#
ip route-static 100.1.1.0 255.255.255.0 100.1.2.1
#
return

#
sysname Switch
#
vlan batch 10
#
undo shutdown
#
undo shutdown
#
return

Tag Termination to Support the DHCP Relay Function
The user packets received by the DHCP relay carry double tags. If the sub-interface for QinQ
VLAN tag termination does not support the DHCP relay function, the DHCP relay regards the
received packets as invalid and discards them. As a result, the DHCP client cannot obtain IP
addresses from the DHCP server.
If a local network does not have a DHCP server, the DHCP relay function can be enabled on the
router. In this manner, the DHCP Request packet from the client can be transmitted to the DHCP
server through the DHCP relay.
To receive the user packet with double tags, the sub-interface for QinQ VLAN tag termination
can be configured with the DHCP relay function.
As shown in Figure 5-21, the network segment to which the DHCP client belongs is
100.1.1.0/24, while the network segment to which the DHCP server belongs is 100.1.3.0/24.
The DHCP packets should be relayed through the router with the DHCP relay function to make

the DHCP client obtain the related configuration information such as the IP address from the
DHCP server.
The DHCP server should be assigned an IP address pool on the network segment 100.1.1.0, so
that the DHCP server can assign IP addresses to the DHCP clients on the network segment. You
need to configure the route to the network segment 100.1.1.0 on the DHCP server. After the
DHCP server receives a packet containing Option82 information from the DHCP relay, the
DHCP server sends a response also contains Option82 information to the DHCP relay.
The lease period of the addresses on the segment 100.1.1.0/24 is 10 days and 12 hours, and the
domain name is huawei.com. The DNS address is 100.1.1.2. The NetBIOS address is 100.1.1.3.
The address of the egress device is 100.1.1.1.
The packets received on the DHCP relay carries double VLAN tags.
termination to support the DHCP relay function
DHCP- Relay POS1/0/0 DHCP- Server

100.1.2.1/24
Internet
POS1/0/0
GE2/0/0.1 100.1.3.1/24
100.1.1.1/24
GE1/0/0
Switch1
GE1/0/1 GE1/0/2
GE1/0/1 GE1/0/1
Switch2 Switch3
GE1/0/0 GE1/0/0
VLAN10 VLAN20
DHCP Client1 DHCP Client2
1. Configure the DHCP relay interface mode to user termination.

2. Configure the DHCP relay.
3. Configure the DHCP server.
4. Configure the sub-interface for QinQ VLAN tag termination on the DHCP relay.
6. Configure the QinQ function on Switch 1.

Data Preparation
l IP address of the interface implementing the DHCP relay function
l Terminating range of the sub-interface for QinQ VLAN tag termination
Procedure
Step 1 Configure the mode of the DHCP relay to user termination.
Step 2 Configure the DHCP relay.

# Enable DHCP.
[DHCP-Relay] dhcp enable
# Configure the address for POS 1/0/0.

[DHCP-Relay] interface pos 1/0/0
[DHCP-Relay-Pos1/0/0] undo shutdown
[DHCP-Relay-Pos1/0/0] ip address 100.1.2.1 24
[DHCP-Relay-Pos1/0/0] quit
# Enter the view of the interface on which DHCP relay is to be enabled and configure its IP
address and mask to keep it and the DHCP client on the same network segment.
Step 3 Configure the DHCP server.

# Configure the route from DHCP Server to DHCP Relay.
[DHCP-Server] ip route-static 100.1.1.0 24 100.1.2.1
# Configure the client connected with POS 1/0/0 to obtain the IP address from the global address
pool.
[DHCP-Server] interface pos 1/0/0
[DHCP-Server-Pos1/0/0] undo shutdown
[DHCP-Server-Pos1/0/0] ip address 100.1.3.1 24
[DHCP-Server-Pos1/0/0] quit
# Configure the features of the DHCP address pool 1, including the IP address of the gateway,
range of IP addresses in the address pool, IP addresses forbidden to be automatically assigned,
domain name suffix of the DNS server, IP address of the DNS server, and address lease.


Step 4 Configure the sub-interface for QinQ VLAN tag termination on the DHCP relay.
[DHCP-Relay-GigabitEthernet2/0/0.1] control-vid 1 qinq-termination
[DHCP-Relay-GigabitEthernet2/0/0.1] qinq termination pe-vid 100 ce-vid 10
[DHCP-Relay-GigabitEthernet2/0/0.1] qinq termination pe-vid 100 ce-vid 20
[DHCP-Relay-GigabitEthernet2/0/0.1] dhcp option82 rebuild enable
NOTE
l When you run the qinq termination command on the same primary interface , the ce-vid values cannot
l After the relay sends a packet containing Option 82 information to the DHCP server, the Offer or ACK
message returned from the DHCP server must contain the Option 82 information.

[Switch2] vlan 10
[Switch3] vlan 20
Step 6 Configure QinQ and set the packets sent from Switch 1 to the DHCP server to carry double tags.
[Switch1] vlan 100



Run the display dhcp relay address command on the DHCP relay device to view the address
configuration of the DHCP relay device.
[DHCP-Relay] display dhcp relay address all
** GigabitEthernet2/0/0.1 DHCP Relay Address **
Dhcp Option Relay Agent IP Server IP
* - 100.1.3.1
The DHCP client can obtain an IP address allocated by the DHCP server through the DHCP
relay.
----End
Configuration Files
l Configuration file a DHCP relay
#
sysname DHCP-Relay
#
undo shutdown
#
undo shutdown
dhcp select relay
ip address 100.1.1.1 255.255.255.0
dhcp option82 rebuild enable
#
interface Pos 1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.2.1 255.255.255.0
#
return
l Configuration file a DHCP server

#
sysname DHCP-Server
#
interface Pos 1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.3.1 255.255.255.0
#
ip pool 1 server
gateway 100.1.1.1 255.255.255.0
section 0 100.1.1.5 100.1.1.100

dns-server 100.1.1.2
lease 10 12
#
ip route-static 100.1.1.0 255.255.255.0 100.1.2.1
#
return

#
sysname Switch1
#
vlan batch 100
#
undo shutdown
#
undo shutdown
#
undo shutdown
#
return

#
sysname Switch2
#
vlan batch 10
#
undo shutdown
#
undo shutdown
#
return

#
sysname Switch3
#
vlan batch 20
#
undo shutdown
#
undo shutdown
#
return
5.14.16 Example for Configuring Dynamic QinQ

A common QinQ termination sub-interface can be configured to terminate user packets with a
maximum of 16,000 combinations of inner and outer tags. If the number of combinations of
inner and outer tags exceeds 16,000, you can enable dynamic QinQ on a QinQ termination sub-
interface. In this case, the QinQ termination sub-interface can terminate user packets with a

maximum of 32,000 combinations of inner and outer tags on a single board. After beingenabled
with dynamic QinQ, the QinQ termination sub-interface cannot support Virtual Leased Line
(VLL), Pseudo Wire Emulation Edge-to-Ede (PWE3), Virtual Private LAN Service (VPLS),
static ARP, and static DHCP snooping binding table.
As shown in Figure 5-22, the DHCP client connects to the DHCP relay through two-hierarchy
switches and requests valid IP addresses from the DHCP server through the DHCP relay. The
DHCP server supports Option82 return. The lease period of the addresses on the segment
10.1.1.0/24 is 10 days and 12 hours, and the domain name is huawei.com. The DNS address is
10.1.1.2. The NetBIOS address is 10.1.1.3.
Two-hierarchy switches attach double tags to the packets that are sent from the DHCP client to
the DHCP relay. It is required to configure the sub-interface of the DHCP relay on the client
side to terminate double tags in the client packet and support the DHCP relay function.
Furthermore, the following features need be deployed on the DHCP relay:
l Dynamic QinQ
Dynamic QinQ is configured on the termination sub-interface of the DHCP relay on the
client side. When users log in, resources are allocated to users. When users log out arising
from exceptions after requesting IP addresses, the system senses this failure automatically,
then deletes the binding in the DHCP binding table, and notifies the DHCP server to release
IP addresses.
l Security features
The DHCP relay can defend itself against the following types of DHCP attacks:
– Bogus DHCP server attack
– Middleman attack and IP/MAC spoofing attack
– DoS attack by changing CHADDR
– Attack by sending bogus DHCP request messages for extending IP lease
– Attack by sending the DHCP request message

Figure 5-22 Networking diagram of dynamic QinQ

DHCP Server
GE1/0/0
100.1.1.2/24
DHCP Snooping Trusted

enable
GE2/0/0
100.1.1.1/24
DHCP Relay
Untrusted GE1/0/0.1
10.1.1.1/24
GE2/0/0
Switch
GE
/1 1
1/0 /0/
GE 2
DHCP Client DHCP Client
1. Configure the interface mode on the DHCP relay as the user termination mode.
2. Configure the basic functions of the DHCP relay.
3. Configure the basic functions of the DHCP server.
4. Configure the sub-interface for QinQ termination to support DHCP relay and dynamic
QinQ.
5. Configure the basic functions of DHCP snooping.
6. Associate ARP with DHCP snooping so that the DHCP relay can dynamically sense users'
log in and log out.
7. Configure Layer 2 forwarding and QinQ for Switch.
Data Preparation
l IP address of the interface to be configured with DHCP relay


l Tag values of the sub-interface for QinQ termination

l Rate for sending the DHCP message to CPU
l Threshold of the alarm sent to the Network Management System (NMS)
Procedure
Step 1 Configure the user termination mode on the interface of the DHCP relay.
Step 2 Configure the basic DHCP relay function.
# Enable the DHCP service.

[DHCP-Relay] dhcp enable
# Assign an IP address to GE 2/0/0.

[DHCP-Relay-GigabitEthernet2/0/0] ip address 100.1.1.1 24
# Configure a sub-interface that is to implement DHCP relay. Assign an IP address and subnet
mask to the sub-interface so that the sub-interface and the DHCP client reside on the same
segment.
Step 3 Configure a DHCP server.
# Enable a DHCP server.

# Configure the client on GE 1/0/0 to obtain IP addresses from the global address pool.
[DHCP-Server] interface gigabitethernet 1/0/0
[DHCP-Server-GigabitEthernet1/0/0] undo shutdown
[DHCP-Server-GigabitEthernet1/0/0] ip address 100.1.1.2 24
[DHCP-Server-GigabitEthernet1/0/0] quit
# Configure the attributes for DHCP address pool 1, including the address pool range, the domain
name, the egress gateway, the DNS address, and the address lease period.

Step 4 Configure the sub-interface for QinQ termination on the DHCP relay and dynamic QinQ.
[DHCP-Relay-GigabitEthernet1/0/0.1] control-vid 1 qinq-termination dynamic
[DHCP-Relay-GigabitEthernet1/0/0.1] qinq-dynamic max-access-user 3
[DHCP-Relay-GigabitEthernet1/0/0.1] qinq-dynamic user-queue 1024 bandwidth 51200
inbound
[DHCP-Relay-GigabitEthernet1/0/0.1] qinq termination pe-vid 1 ce-vid 1 to 4094
[DHCP-Relay-GigabitEthernet1/0/0.1] qinq termination pe-vid 2 ce-vid 1 to 4094
[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp option82 insert enable
[DHCP-Relay-GigabitEthernet1/0/0.1] arp learning strict force-disable
NOTE
l The DHCP server must support the Option82 return function. Namely, the Offer or ACK message
returned from the DHCP server must contain the Option82 information.
l Run the arp learning strict force-disable command to unfetter the dynamic QinQ interface from
global ARP rigid learning so that the dynamic QinQ interface can learn the ARP request sent by users.
Step 5 Enable DHCP snooping.

1. Enable global and interface-specific DHCP snooping.
[DHCP-Relay] dhcp snooping enable
[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping enable
[DHCP-Relay-GigabitEthernet2/0/0] dhcp snooping enable
2. Configure a Trusted interface.

# Configure the interface connecting to the DHCP server as a trusted interface and enable
DHCP snooping on all the interfaces connecting to the DHCP client. (If the interface on
the client side is not configured with "trusted", the default interface mode is "untrusted"
after DHCP snooping is enabled on the interface.) This prevents the bogus DHCP server
attack.
[DHCP-Relay-GigabitEthernet2/0/0] dhcp snooping trusted
3. Check specific packets.

# Check ARP packets and IP packets on the interface on the DHCP client side. This prevents
the middleman attack and IP/MAC spoofing attack.
[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping check arp enable
[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping check ip enable
# Check the DHCP request message on the interface on the DHCP client side. This prevents
the attacker from sending bogus DHCP request messages for extending IP lease.
[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping check dhcp-request enable

# Check CHADDR packets on the interface on the DHCP client side. This prevents the
DoS attack that is launched by changing the CHADDR value.
[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping check dhcp-chaddr enable
4. Restrict the sending rate of DHCP messages.

# Check the sending rate of DHCP messages to prevent the attacker from sending DHCP
request messages.
[DHCP-Relay] dhcp snooping check dhcp-rate 90
[DHCP-Relay] dhcp snooping check dhcp-rate enable
5. Configure forwarding behaviors for the packets that do not contain DHCP snooping entries.
# Configure how to process unmatched ARP and IP packets globally.
[DHCP-Relay] dhcp snooping nomatch-packet arp action discard
[DHCP-Relay] dhcp snooping nomatch-packet ip action discard
# Configure how to process unmatched ARP and IP packets on the interface.

[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping nomatch-packet arp action
discard
[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping nomatch-packet ip action
discard
6. Send alarms to the NMS.

# Send alarms to the NMS.
[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping alarm dhcp-reply enable
[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping alarm arp enable
[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping alarm dhcp-chaddr enable
[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping alarm dhcp-request enable
[DHCP-Relay] dhcp snooping check dhcp-rate alarm enable
# Set the threshold for the alarm message.

[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping alarm dhcp-reply threshold 10
[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping alarm arp threshold 10
[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping alarm dhcp-chaddr threshold
10
[DHCP-Relay-GigabitEthernet1/0/0.1] dhcp snooping alarm dhcp-request threshold
10
[DHCP-Relay] dhcp snooping check dhcp-rate alarm threshold 40
Step 6 Associate ARP with DHCP snooping.

# The system sends the ARP packet to probe the IP address that expires within the aging time
in the DHCP snooping entry and does not exist in the ARP entry. If no user is detected within
the specified detection times, the system deletes the binding relationship in the DHCP binding
table and notifies the DHCP server to release the IP address.
[DHCP-Relay] arp dhcp-snooping-detect enable
Step 7 Configure QinQ so that the packets sent from Switch to the DHCP relay carry double tags.
# Configure Switch.
[Switch] vlan batch 1 to 2
[Switch-GigabitEthernet2/0/0] port trunk allow-pass vlan 1 to 2

[Switch-GigabitEthernet1/0/1] port vlan-stacking vlan 1 to 4094 push vlan 1 inbound
[Switch-GigabitEthernet1/0/2] port vlan-stacking vlan 1 to 4094 push vlan 2 inbound

The DHCP client can request valid IP addresses. Running the display this command on the
termination sub-interface configured with dynamic QinQ, you can find that the control-vid
dynamic command is configured on the sub-interface.
[DCHP-Relay-GigabitEthernet1/0/0.1] display this
#
control-vid 1 qinq-termination dynamic
ip address 10.1.1.1 255.255.255.0
dhcp select relay
dhcp snooping check arp enable
dhcp snooping alarm arp enable
dhcp snooping alarm arp threshold 10
dhcp snooping check ip enable
dhcp snooping alarm dhcp-reply enable
dhcp snooping alarm dhcp-reply threshold 10
dhcp snooping check dhcp-chaddr enable
dhcp snooping alarm dhcp-chaddr enable
dhcp snooping alarm dhcp-chaddr threshold 10
dhcp snooping check dhcp-request enable
dhcp snooping alarm dhcp-request enable
dhcp snooping alarm dhcp-request threshold 10
dhcp option82 insert enable
#
Running the display dhcp snooping global command on the DHCP relay, you can find that
DHCP snooping is enabled in the global view and interface view. In addition, you can view the
statistics of the alarm message sent to the NMS.
[DHCP-Relay] display dhcp snooping global
[DHCP-Relay] display dhcp snooping interface gigabitethernet 1/0/0.1


arp total 0
ip total 0
dhcp-request total 0
chaddr&src mac total 0
dhcp-reply total 0
[DHCP-Relay] display dhcp snooping interface gigabitethernet 2/0/0
dhcp snooping trusted
arp total 0
ip total 0
dhcp-request total 0
chaddr&src mac total 0
dhcp-reply total 0
[DHCP-Relay] display dhcp option82 interface gigabitethernet 1/0/0.1
dhcp option82 insert enable interface GigabitEthernet1/0/0.1
----End
Configuration Files
l Configuration file of a DHCP relay
#
sysname DHCP-Relay
#
#
undo shutdown
#
undo shutdown
control-vid 1 qinq-termination dynamic
qinq-dynamic max-access-user 3
qinq-dynamic user-queue 1024 bandwidth 51200 inbound
ip address 10.1.1.1 255.255.255.0
dhcp select relay
arp learning strict force-disable
dhcp option82 insert enable
#
undo shutdown

dhcp snooping trusted

#
arp dhcp-snooping-detect enable
#
return
l Configuration file of a DHCP server

#
sysname DHCP-Server
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
#
ip pool 1 server
gateway 10.1.1.1 255.255.255.0
section 0 10.1.1.5 10.1.1.100
dns-server 10.1.1.2
lease 10 12
#
return

#
sysname Switch
#
vlan batch 1 to 2
#
undo shutdown
port vlan-stacking vlan 1 to 4094 push vlan 1 inbound
#
undo shutdown
port vlan-stacking vlan 1 to 4094 push vlan 2 inbound
#
undo shutdown
#
return
5.14.17 Example for Configuring the Sub-interface for VLAN

Stacking to Access a VLL
VLL is a point-to-point L2VPN. Because the VLANIF interface does not support VLL, you
have to use the main interface to access VPN. Such a configuration is not flexible because the
same physical interface cannot be accessed by multiple users. To make one physical interface
accessed by multiple users, you can use the VLAN-based QinQ function at different sub-
interfaces as mentioned previously. In this case, CE-VLANs on both sides must be symmetrical.
As shown in Figure 5-23, the sub-interfaces GE1/0/0.1 of CEs are connected to PEs through
switches. The packet sent from the CE to the switch carries no tag. The switch then labels the
packets from the CE with different outer tags according to the inbound interface. The packets
sent from the switch to the PE carries one VLAN tag. It is required to configure the sub-interface
for VLAN stacking on the PE to access an L2VPN to implement inter-communication between
CE1 and CE2, and between CE3 and CE4.

Figure 5-23 Typical networking diagram of configuring the sub-interface for VLAN stacking
to access a VLL
1.1.1.9/32 2.2.2.9/32 3.3.3.9/32
POS1/0/0 POS1/0/0
100.1.1.1/24 100.1.2.2/24
PE1 PE2
POS1/0/0 POS2/0/0
GE2/0/0.1 100.1.1.2/24 100.1.2.1/24
P GE2/0/0.1
GE1/0/0 GE1/0/0
Switch1 Switch2
GE1/0/1
GE1/0/1 GE1/0/2 GE1/0/2
GE1/0/0 GE1/0/0
GE1/0/0 20.1.1.1/24 10.1.1.2/24 GE1/0/0
10.1.1.1/24 20.1.1.2/24
CE1 CE3 CE2 CE4

VPN1 VPN1 VPN1 VPN1
1. Configure the interface mode on PE1 and PE2 as the user termination mode.
2. Run IGP on the backbone network to interconnect the devices.
3. Enable basic MPLS capabilities to set up an LSP in the backbone network.
4. Set up MPLS LDP remote peer relationship between the PEs at both ends of the PW.
5. Configure the sub-interface for QinQ VLAN stacking on the client side to access an L2VPN
on the PE.
6. Configure Layer 2 forwarding on Switch.
Data Preparation
l Names of the interfaces through which the PEs and the CEs are connected
l L2VC IDs that must be identical at both ends of the PW
l MPLS LSR IDs on the PEs and Ps
l IP addresses of the remote peers of the PEs
Procedure
# Configure PE1.

# Configure PE2.
Step 2 Configure IGP on the MPLS backbone network. OSPF is configured in this example.
Configure the IP addresses of the interfaces on the PEs and Ps, as shown in Figure 5-23. When
you configure OSPF, advertise the IP addresses of the loopback interfaces on PE1, P, and PE2.
# Configure PE1.
[PE1-Pos1/0/0] ip address 100.1.1.1 24
[PE1-Pos1/0/0] quit
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure P.
[HUAWEI] sysname P
[P-LoopBack1] quit
[P-Pos1/0/0] ip address 100.1.1.2 24
[P-Pos1/0/0] quit
[P-Pos2/0/0] ip address 100.1.2.1 24
[P-Pos2/0/0] quit
[P] ospf
[P-ospf-1] area 0
[P-ospf-1] quit
# Configure PE2.
[PE2-Pos1/0/0] ip address 100.1.2.2 24
[PE2-Pos1/0/0] quit

[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
After this step, PE1 and PE2 can discover the routes of Loopback1 through OSPF and ping
through each other.

------------------------------------------------------------------------------
2.2.2.9/32 OSPF 10 2 D 100.1.1.2 Pos1/0/0
3.3.3.9/32 OSPF 10 3 D 100.1.1.2 Pos1/0/0
100.1.1.0/24 Direct 0 0 D 100.1.1.1 Pos1/0/0
100.1.1.2/32 Direct 0 0 D 100.1.1.2 Pos1/0/0
100.1.2.0/24 OSPF 10 2 D 100.1.1.2 Pos1/0/0
[PE1] ping 100.1.2.2
0.00% packet loss
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
[PE1-Pos1/0/0] mpls
[PE1-Pos1/0/0] quit
# Configure P.
[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
[P-Pos1/0/0] mpls
[P-Pos1/0/0] quit
[P-Pos2/0/0] mpls
[P-Pos2/0/0] quit

# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2-Pos1/0/0] mpls
[PE2-Pos1/0/0] quit
After the preceding configurations, LDP sessions are set up between PE1 and P, and between
PE1 and PE2. Running the display mpls ldp session command, you can view that the Status
field is "Operational". Running the display mpls ldp lsp command, you can view the
establishment status of the LDP LSP.
------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
LDP LSP Information
------------------------------------------------------------------------------
------------------------------------------------------------------------------
1 1.1.1.9/32 3/NULL 127.0.0.1 Pos1/0/0/InLoop0
2 2.2.2.9/32 NULL/3 100.1.1.2 -------/Pos1/0/0
3 3.3.3.9/32 NULL/1024 100.1.1.2 -------/Pos1/0/0
4 100.1.2.0/24 NULL/3 100.1.1.2 -------/Pos1/0/0
------------------------------------------------------------------------------
Step 4 Set up remote LDP sessions between the PEs.

# Configure PE1.
# Configure PE2.
After the configuration, LDP sessions can be set up between PE1 and P and between PE2 and
P.
Running the display mpls ldp session command, you can view that the Status is "Operational".
Running the display mpls ldp lsp command, you can view the setup of the LDP LSP.
Take PE1 as an example.
------------------------------------------------------------------------------


------------------------------------------------------------------------------
------------------------------------------------------------------------------
LDP LSP Information
------------------------------------------------------------------------------
------------------------------------------------------------------------------
1 1.1.1.9/32 3/NULL 127.0.0.1 Pos1/0/0/InLoop0
2 2.2.2.9/32 NULL/3 100.1.1.2 -------/Pos1/0/0
3 3.3.3.9/32 NULL/1025 100.1.1.2 -------/Pos1/0/0
4 100.1.1.0/24 3/NULL 100.1.1.1 -------/Pos1/0/0
5 100.1.2.0/24 NULL/3 100.1.1.2 -------/Pos1/0/0
*6 100.1.2.0/24 Liberal
------------------------------------------------------------------------------
Step 5 Enable MPLS L2VPN on the PEs and set up VCs, and configure the Sub-interface for VLAN
Stacking.
# Configure PE1.
[PE1] mpls l2vpn
[PE1-l2vpn] quit
[PE1-GigabitEthernet2/0/0.1] qinq stacking vid 10
# Configure PE2.
[PE2] mpls l2vpn
[PE1-l2vpn] quit
NOTE
Here, when configuring the sub-interface for QinQ VLAN stacking, you need to specify the value of only
the inner VLAN tag. The value of the outer tag is not required. The outer VLA tag is appended automatically
by the system.
Step 6 Configure the basic Layer 2 forwarding function and set the packet sent from the switch to the
PE to carry one VLAN tag.
[Switch1] vlan 10
[Switch1] vlan 20

[Switch1-GigabitEthernet1/0/0] port trunk allow-pass vlan 10 20

[Switch2] vlan 10
[Switch2] vlan 20
the CE to the switch to carry no VLAN tag.
# Configure CE1.
# Configure CE2.
# Configure CE3.
# Configure CE4.

On the PEs, you can view that an L2 VC is set up and is in the Up state.
[PE1] display mpls l2vc
Total ldp vc : 2 2 up 0 down
Session State : up
AC Status : up

VC State : up
VC ID : 102
VC Type : vlan
Local VC MTU : 1500
Remote VC MTU : 1500
Traffic Behavior Name: --
Session State : up
AC Status : up
VC State : up
VC ID : 101
VC Type : vlan
Local VC MTU : 1500
Remote VC MTU : 1500
Traffic Behavior Name: --
The hosts attached to CEs can ping through each other if they are in the same VLAN.
Take the display on CE1 as an example:
[CE1] ping 10.1.1.2
0.00% packet loss
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
mpls l2vpn
#
#
mpls ldp
#

remote-ip 3.3.3.9
#
undo shutdown
#
undo shutdown
qinq stacking vid 10
mpls l2vc 3.3.3.9 101
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 100.1.1.0 0.0.0.255
#
return
#
sysname P
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 100.1.2.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 100.1.1.0 0.0.0.255
network 100.1.2.0 0.0.0.255
#
return
#
sysname PE2
#
mpls lsr-id 3.3.3.9
mpls
#

mpls l2vpn
#
mpls ldp
#
remote-ip 1.1.1.9
#
undo shutdown
#
undo shutdown
mpls l2vc 1.1.1.9 101
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.2.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 100.1.2.0 0.0.0.255
#
return
#
sysname Switch1
#
vlan batch 10 20
#
undo shutdown
#
undo shutdown
#
undo shutdown
#
return
#
sysname Switch2
#
vlan batch 10 20
#
undo shutdown
#
undo shutdown
#

undo shutdown
#
return

#
sysname CE1
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
return

#
sysname CE2
#
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
return

#
sysname CE3
#
undo shutdown
ip address 20.1.1.1 255.255.255.0
#
return

#
sysname CE4
#
undo shutdown
ip address 20.1.1.2 255.255.255.0
#
return

Stacking to Access a VPLS Network
This example shows how to configure a Layer 3 sub-interface for QinQ stacking to access a
VPLS network. The sub-interface adds an outer VLAN tag of the ISP network to the user packet.
The sub-interface is bound to a VSI and accesses the VPLS network.
As shown in Figure 5-24, CEs are connected to PEs through switches. The packet sent from the
switch to the switch carries no VLAN tags. The switch then labels the packets from the CE with
different outer tags according to the inbound interface and send the packets to the PE. It is
required to configure the sub-interface for QinQ VLAN stacking to access VPLS to implement
interworking between CE1, CE2, and CE3, and between CE4, CE5, and CE6. The backbone
network adopts Martini VPLS and uses LDP to set up PWs.

Figure 5-24 Typical networking diagram of configuring the sub-interface for VLAN stacking
to access VPLS
VPN1 VPN1
VLAN10 VLAN20
CE3 CE6
GE1/0/0 GE1/0/0
10.1.1.3/24 20.1.1.3/24
GE1/0/1 GE1/0/2
Switch3
GE1/0/0
GE2/0/0.1
POS1/0/0 POS1/0/1
100.1.1.2/30 100.1.2.1/30
PE3
Loopback1
3.3.3.9/32
POS1/0/1 POS1/0/1
100.1.1.1/30 100.1.2.2/30
POS1/0/0 POS1/0/0
1.1.1.9/32 2.2.2.9/32
PE1 GE2/0/0.1 GE2/0/0.1 PE2
GE1/0/0 GE1/0/0
Switch1 Switch2
GE1/0/1 GE1/0/2 GE1/0/1 GE1/0/2
GE1/0/0 GE1/0/0 GE1/0/0 GE1/0/0
10.1.1.1/24 20.1.1.1/24 10.1.1.2/24 20.1.1.2/24
CE1 CE4 CE2 CE5

VPN1 VPN1 VPN1 VPN1
1. Run the IGP protocol to connect the devices on the backbone network.
2. Configure the basic MPLS capabilities on the backbone network.
5. Create and then configure the VSI.
6. Configure the sub-interface for QinQ VLAN stacking on PEs and bind VSIs and AC
interfaces.

Data Preparation
Procedure
# Configure PE1.
# Configure PE2.
# Configure PE3.
According to Figure 5-24, configure the addresses for the interfaces on PE. Configure OSPF to
advertise the addresses of the loopback interfaces on PE1, PE2, and PE3.
# Configure PE1.
[PE1-Pos1/0/0] ip address 100.1.3.1 30
[PE1-Pos1/0/0] quit
[PE1-Pos1/0/1] ip address 100.1.1.1 30
[PE1-Pos1/0/1] quit
[PE1] ospf
[PE1-ospf-1] area 0


[PE1-ospf-1] quit
# Configure PE2.
[PE2-Pos1/0/0] ip address 100.1.3.2 30
[PE2-Pos1/0/0] quit
[PE2-Pos1/0/1] ip address 100.1.2.2 30
[PE2-Pos1/0/1] quit
[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
# Configure PE3.
[PE3-Pos1/0/0] ip address 100.1.1.2 30
[PE3-Pos1/0/0] quit
[PE3-Pos1/0/1] ip address 100.1.2.1 30
[PE3-Pos1/0/1] quit
[PE3] ospf
[PE3-ospf-1] area 0
[PE3-ospf-1] quit
------------------------------------------------------------------------------
2.2.2.9/32 OSPF 10 2 D 100.1.3.2 Pos1/0/0
3.3.3.9/32 OSPF 10 2 D 100.1.1.2 Pos1/0/1
100.1.1.0/30 Direct 0 0 D 100.1.1.1 Pos1/0/1
100.1.1.2/32 Direct 0 0 D 100.1.1.2 Pos1/0/1
100.1.2.0/30 OSPF 10 2 D 100.1.1.2 Pos1/0/1
OSPF 10 2 D 100.1.3.2 Pos1/0/0
100.1.3.0/30 Direct 0 0 D 100.1.3.1 Pos1/0/0


100.1.3.2/32 Direct 0 0 D 100.1.3.2 Pos1/0/0
[PE1] ping 100.1.2.2
0.00% packet loss
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
[PE1-Pos1/0/0] mpls
[PE1-Pos1/0/0] quit
[PE1-Pos1/0/1] mpls
[PE1-Pos1/0/1] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2-Pos1/0/0] mpls
[PE2-Pos1/0/1] mpls
[PE2-Pos1/0/1] quit
# Configure PE3.
[PE3] mpls
[PE3-mpls] quit
[PE3] mpls ldp
[PE3-mpls-ldp] quit
[PE3-Pos1/0/0] mpls
[PE3-Pos1/0/0] quit
[PE3-Pos1/0/1] mpls
[PE3-Pos1/0/1] quit
After the configuration, the sessions between PE1, PE2 and PE3 are set up. Running the display
mpls ldp session command, you can view that the Status field is "Operational".
For example, the following displays the session information on PE1.


------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
NOTE
Step 4 Enable MPLS L2VPN on the PE.
# Configure PE1.
[PE1] mpls l2vpn
# Configure PE2.
[PE2] mpls l2vpn
# Configure PE3.
[PE3] mpls l2vpn
# Configure PE1.
# Configure PE2.
# Configure PE3.
Step 6 Configure the sub-interface for QinQ VLAN stacking, and bind VSIs and AC interfaces.
# Configure PE1
# Configure PE2.


# ConfigurePE3
NOTE
Here, when configuring the sub-interface for QinQ VLAN stacking, you need to specify the value of only
the inner VLAN tag. The value of the outer tag is not required. The outer VLA tag is appended automatically
by the system.
Step 7 Configure the Layer 2 forwarding function and set the packet sent from the switch to the PE to
carry one VLAN tag.
[Switch1] vlan 10
[Switch1] vlan 20
[Switch2] vlan 10
[Switch2] vlan 20
[Switch3] vlan 10
[Switch3] vlan 20

the CE to the switch to carry no VLAN tag.
# Configure CE1.
# Configure CE2.
# Configure CE3.
# Configure CE4.
# Configure CE5.
# Configure CE6.

Running the display qinq information stacking interface command, you can view the stacking
information.
The following displays the stacking information on PE1:
[PE1] display qinq information stacking interface gigabitethernet 2/0/0
VSI bound
Total QinQ Num: 2
qinq Stacking vid 10

qinq Stacking vid 20

After the preceding configuration, run the display vsi ldp1 verbose command on PE1. You can
find that PWs to PE2 and PE3 are set up on the VSI named ldp1. The VSI status is Up.
[PE1] display vsi bgp1 verbose
***VSI Name : ldp1
VSI Index : 0
PW Signaling : ldp
MTU : 1500
VSI State : up
VSI ID : 2
VC Label : 23552
Peer Type : dynamic
Session : up
VC Label : 23553
Peer Type : dynamic
Session : up
State : up
**PW Information:
PW State : up
PW Type : label
PW State : up
PW Type : label
The hosts attached to CE1, CE2, and CE3 can ping through each other.
[CE1] ping 10.1.1.2
0.00% packet loss
[CE1] ping 10.1.1.3
0.00% packet loss
----End

Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 2
peer 3.3.3.9
peer 2.2.2.9
#
mpls ldp
#
undo shutdown
#
undo shutdown
l2 binding vsi ldp1
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.3.1 255.255.255.252
mpls
mpls ldp
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 100.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 100.1.1.0 0.0.0.3
network 100.1.3.0 0.0.0.3
#
return

#
sysname PE2
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
peer 3.3.3.9
#

mpls ldp
#
undo shutdown
#
undo shutdown
l2 binding vsi ldp1
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.3.2 255.255.255.252
mpls
mpls ldp
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 100.1.2.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 100.1.3.0 0.0.0.3
network 100.1.2.0 0.0.0.3
#
return
#
sysname PE3
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
peer 2.2.2.9
#
mpls ldp
#
undo shutdown
#
undo shutdown
l2 binding vsi ldp1
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 100.1.1.2 255.255.255.252
mpls
mpls ldp

#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 100.1.2.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 100.1.1.0 0.0.0.3
network 100.1.2.0 0.0.0.3
#
return
#
sysname Switch1
#
vlan batch 10 20
#
undo shutdown
#
undo shutdown
#
udno shutdown
#
return
#
sysname Switch2
#
vlan batch 10 20
#
undo shutdown
#
undo shutdown
#
und shutdown
#
return
#
sysname Switch3
#
vlan batch 10 20
#
undo shutdown
#

undo shutdown
#
undo shutdown
#
return

#
sysname CE1
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
return

#
sysname CE2
#
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
return

#
sysname CE3
#
undo shutdown
ip address 10.1.1.3 255.255.255.0
#
return

#
sysname CE4
#
undo shutdown
ip address 20.1.1.1 255.255.255.0
#
return

#
sysname CE5
#
undo shutdown
ip address 20.1.1.2 255.255.255.0
#
return

#
sysname CE6
#
undo shutdown
ip address 20.1.1.3 255.255.255.0
#
return


Tag Termination to Support URPF
To protect the NE80E/40E against attacks based on source address spoofing, you need to enable
URPF on the corresponding interface. This example describes how to configure sub-interfaces
for QinQ VLAN tag termination to support URPF.
As shown in Figure 5-25, Switch A and Switch B access the ISP network through Router A and
Router B. URPF is configured on the sub-interface for QinQ VLAN tag termination GE 2/0/0.1
of Router A and Router B to perform strict URPF for the packets with the outer VLAN tag as
100 and the inner VLAN tag as 10 to 20.
termination to support URPF
RouterA RouterB
POS1/0/0 POS1/0/0
100.1.1.1/24 100.1.1.2/24
GE2/0/0.1 GE2/0/0.1
10.1.1.1/24 10.2.1.1/24
GE1/0/0 GE1/0/0
SwitchA SwitchB
VLAN100 VLAN100
1. Configure GE 2/0/0.1 of Router A and Router B as the sub-interface for QinQ VLAN tag
termination.
2. Enable URPF on GE 2/0/0.1.
Data Preparation
l IP addresses of the interfaces

l QinQ VLAN tags to be terminated on the sub-interface for QinQ VLAN tag termination

Procedure
Step 1 Configure IGP. OSPF is used in this example.
[HUAWEI] sysname A
[RouterA] interface pos 1/0/0
[RouterA-Pos1/0/0] ip address 100.1.1.1 24
[RouterA-Pos1/0/0] quit
[RouterA] ospf
[RouterA-ospf-1] area 0
[RouterA-ospf-1-area-0.0.0.0] network 100.1.1.0 0.0.0.255
[RouterA-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[RouterA-ospf-1-area-0.0.0.0] quit
[RouterA-ospf-1] quit
[HUAWEI] sysname B
[RouterB] interface pos 1/0/0
[RouterB-Pos1/0/0] ip address 100.1.1.2 24
[RouterB-Pos1/0/0] quit
[RouterB] ospf
[RouterB-ospf-1] area 0
[RouterB-ospf-1-area-0.0.0.0] network 100.1.1.0 0.0.0.255
[RouterB-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255
[RouterB-ospf-1-area-0.0.0.0] quit
[RouterB-ospf-1] quit
Step 2 Configure the sub-interface for QinQ VLAN tag termination and enable URPF.
[RouterA-GigabitEthernet2/0/0] mode user-termination
[RouterA] interface gigabitethernet 2/0/0.1
[RouterA-GigabitEthernet2/0/0.1] control-vid 1 qinq-termination
[RouterA-GigabitEthernet2/0/0.1] qinq termination pe-vid 100 ce-vid 10 to 20
[RouterA-GigabitEthernet2/0/0.1] ip address 10.1.1.1 24
[RouterA-GigabitEthernet2/0/0.1] arp broadcast enable
[RouterA-GigabitEthernet2/0/0.1] ip urpf loose
[RouterB-GigabitEthernet2/0/0] mode user-termination
[RouterB] interface gigabitethernet 2/0/0.1
[RouterB-GigabitEthernet2/0/0.1] control-vid 1 qinq-termination
[RouterB-GigabitEthernet2/0/0.1] qinq termination pe-vid 100 ce-vid 10 to 20
[RouterB-GigabitEthernet2/0/0.1] ip address 10.2.1.1 24
[RouterB-GigabitEthernet2/0/0.1] arp broadcast enable
[RouterB-GigabitEthernet2/0/0.1] ip urpf loose
Running the display qinq information termination interface command on Router, you can
view information about QinQ termination. Configuring the URPF check on the interace can
effectively avoid the attack of the packets whith the pseudo IP addresses.
----End

Configuration Files
#
sysname RouterA
#
#
ip address 10.1.1.1 255.255.255.0
ip urpf loose
#
interface Pos1/0/0
link-protocol ppp
ip address 100.1.1.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 100.1.1.0 0.0.0.255
#
return

#
sysname RouterB
#
#
ip address 10.2.1.1 255.255.255.0
ip urpf loose
#
interface Pos1/0/0
link-protocol ppp
ip address 100.1.1.2 255.255.255.0
#
ospf 1
area 0.0.0.0
network 10.2.1.0 0.0.0.255
network 100.1.1.0 0.0.0.255
#
return
5.14.20 Example for Configuring the dot1q Termination Sub-

interface in a VSI to Support IGMP Snooping
You can configure a sub-interface for QinQ termination to support IGMP on only Layer 3
interfaces rather than Layer 2 interfaces.
In the networking shown in Figure 5-26, CE1 labels each multicast protocol packet received
from hosts with one tag, and then sends the packets to PE1. After the sub-interface for dot1q
VLAN tag termination is configured on PE1, PE1 accesses the VPLS network . After terminating
the PW, PE2 joins the related multicast VLAN and accesses the multicast source.

PE2 functions as a Superstratum PE (SPE) device, and PE1 functions an Underlayer PE (UPE)
device. When HVPLS is deployed, multicast packets are broadcast in a VSI if PE1 and PE2 do
not support IGMP snooping. This wastes network resources.
After IGMP snooping is configured, multicast packets are sent to only access devices of multicast
receivers.
In a stable network, the PW on PE1 is configured as a static router port in the VSI. In this manner,
receivers can steadily receive the multicast data.
To reduce the number of IGMP Query packets from the upstream router, you should configure
PE2 as a querier. This saves bandwidths.
Figure 5-26 Networking diagram of configuring the sub-interface for dot1q VLAN tag
termination in a VSI to support IGMP snooping

1.1.1.1/32 2.2.2.2/32 3.3.3.3/32
IGMP Source
PE1 P PE2
GE1/0/1 GE1/0/1 GE1/0/1
GE1/0/0 GE1/0/0
Dot1q GE1/0/0
Termination MPLS Network
IP 20
GE1/0/1
CE1
GE1/0/0
PC
Device Interface IP Address
PE1 GE1/0/0
GE1/0/1 192.168.12.1/24
P GE1/0/0 192.168.12.2/24
GE1/0/1 192.168.23.1/24
PE2 GE1/0/0 192.168.23.2/24
GE1/0/1

1. Configure the termination mode on PE1 to the user termination mode.

3. Enable global IGMP snooping and IGMP snooping for a VSI.
4. Bind a VSI to an AC interface on PE1 and PE2 respectively.
5. Configure a PW on PE1, P, and PE2, and PE1, P, and PE2 accesses the VPLS network in
asymmetrical mode.
6. Configure static router ports and configure PE2 as a querier.
Data Preparation
l ID of the multicast VLAN
l ID of the VLAN on CE1
l ID of the VSI
l MPLS LSR ID of PE1, P, and PE2
Procedure
Step 1 Configure the mode of the QinQ interface on PE1 as user termination.
Step 2 Configure dot1q termination on PE1.

Step 3 Configure IGP on the MPLS backbone network. In this example, OSPF is adopted to advertise
routes. When configuring OSPF, advertise the 32-bit loopback interface addresses of PE1, P,
and PE2.
# Configure PE1.
[PE1-GigabitEthernet1/0/1] ip address 192.168.12.1 24
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure P.
[HUAWEI] sysname P

[P-LoopBack2] quit
[P] interface gigabitethernet 1/0/0
[P-GigabitEthernet1/0/0] ip address 192.168.12.2 24
[P-GigabitEthernet1/0/0] undo shutdown
[P-GigabitEthernet1/0/0] quit
[P] ospf
[P-ospf-1] area 0
[P-ospf-1] quit
# Configure PE2.
[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
Step 4 Configure basic MPLS functions and LDP.

# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
[PE1-GigabitEthernet1/0/1]quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
# Configure P.
[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
[P-GigabitEthernet1/0/0] mpls

[P-GigabitEthernet1/0/0] mpls ldp

Step 5 Enable MPLS L2VPN and configure a VSI.

# Configure PE1.
[PE1] mpls l2vpn
[PE1-l2vpn] quit
[PE1] vsi v123 static
[PE1-vsi-v123] pwsignal ldp
[PE1-vsi-v123-ldp] vsi-id 123
[PE1-vsi-v123-ldp] peer 3.3.3.3
[PE1-vsi-v123-ldp] quit
[PE1-vsi-v123] quit
# Configure PE2.
[PE2] mpls l2vpn
[PE2-l2vpn] quit
[PE2-vsi-v123-ldp] peer 1.1.1.1 upe
[PE2-vsi-v123] quit
Step 6 Configure remote MPLS LDP sessions for PE1 and PE2.
# Configure PE1.
[PE1] mpls ldp remote-peer PE2
[PE1-mpls-ldp-remote-PE2] remote-ip 3.3.3.3
[PE1-mpls-ldp-remote-PE2] quit
# Configure PE2.
Step 7 Bind the VSI and the interface on a PE.

# Configure PE1.
[PE1] vlan 1
[PE1-vlan1] quit
# Configure PE2.
Step 8 Enable IGMP snooping on PE1 and PE2 in the VSI.

# Configure PE1. The configurations of PE2 is similar to the configuration of PE1 and are not
mentioned here.
[PE1] vsi v123
[PE1-vsi-v123] igmp-snooping enable

Step 9 Configure the PW on PE1 as a static router port , and configure the querier on PE2. The default
values are used for the querier.
# Configure PE1.
[PE1] vsi v123
[PE1-vsi-v123] igmp-snooping static-router-port remote-peer 3.3.3.3
# Configure PE2.
[PE2] igmp-snooping send-query enable
[PE2] vsi v123
[PE2-vsi-v123] igmp-snooping querier enable
[PE2-vsi-v123] quit

Run the display dot1q information termination interface command on PE1, and you can view
information about the configured sub-interface for dot1q VLAN tag termination.
vsi bound
Total QinQ Num: 1
Run the display mpls ldp session command, and you view that MPLS LDP sessions on PE1,
P, and PE2 are in the Operational state.
Take the display of PE1 as an example.
<PE1>display mpls ldp session
------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Run the display igmp-snooping querier vsi command on PE1, and you can check whether the
configuration of the querier succeeds. If the Enable state is displayed as shown in the following
output, it indicates that the querier is enabled for VSI v123.
<PE1> display igmp-snooping querier vsi v123
VSI Querier-state
-----------------------------------------------
v123 Enable
-----------------------------------------------
Run the display igmp-snooping router-port vsi command on PE1, and you can check whether
the configuration of the static router port succeeds. If STATIC is displayed as shown in the
following output, it indicates that PW (1.1.1.1/123) is configured as a static router port.
<PE1> display igmp-snooping router-port vsi v123
---------------------------------------------------------------------
PW(1.1.1.1/123) 00:06:59 -- STATIC
----End

Configuration Files
#
sysname PE1
#
igmp-snooping send-query
enable
#
vlan
20
igmp-snooping enable
#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
vsi v123 static
pwsignal ldp
vsi-id 123
peer 3.3.3.3
igmp-snooping static-router-port remote-peer 3.3.3.3
#
mpls ldp
#
mpls ldp remote-peer pe2
remote-ip 3.3.3.3
undo remote-ip pwe3
#
interface Gigabitethernet1/0/0
#
interface
Gigabitethernet1/0/0.1
control-vid 10 dot1q-
termination
igmp enable l2 binding vsi v123
#
ip address 192.168.12.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 192.168.12.0 0.0.0.255
#
return
#
sysname P
#
mpls lsr-id 2.2.2.2
mpls
#
mpls ldp
#
ip address 192.168.12.2 255.255.255.0
mpls
mpls ldp

#
ip address 192.168.23.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack2
ip address 2.2.2.2 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 192.168.12.0 0.0.0.255
network 192.168.23.0 0.0.0.255
#
return
#
sysname PE2
#
vlan batch 10
#
igmp-snooping send-query enable
#
mpls lsr-id 3.3.3.3
mpls
#
mpls l2vpn
#
vsi v123 static
pwsignal ldp
vsi-id 123
peer 1.1.1.1
igmp-snooping querier enable
#
mpls ldp
#
remote-ip 1.1.1.1
undo remote-ip pwe3
#
ip address 192.168.23.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
#
interface Gigabitethernet1/0/1.1
vlan-type dot1q 20
l2 binding vsi v123
igmp-snooping static-router-port vsi v123
#
interface LoopBack3
ip address 3.3.3.3 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.3 0.0.0.0
network 192.168.23.0 0.0.0.255
#
return
#
sysname CE1
#

vlan batch 20
#
portswitch
#
portswitch
#
return
5.14.21 Example for Configuring the QinQ Termination Sub-

interface in a VSI to Support IGMP Snooping
You can configure a sub-interface for QinQ termination to support IGMP snooping on only
Layer 2 interfaces rather than Layer 3 interfaces.
In the network shown in Figure 5-27, Multicast protocol packets are labeled with an outer tag
and an inner tag on CE1 and CE2 respectively, and then sent to PE1. After receiving the packets,
PE1 terminates two tags, and then accesses the VPLS network in an asymmetrical manner. PE2
terminates the PW, joins the related multicast VLAN, and accesses the multicast source.
PE2 functions as a Superstratum PE (SPE) device, and PE1 functions an Underlayer PE (UPE)
device. When the Hierarchical Virtual Private LAN Service (HVPLS) is deployed, multicast
packets are broadcast in a VSI if PE1 and PE2 do not support IGMP snooping. This wastes
network resources.
After IGMP snooping is configured, multicast packets are sent to only access devices of multicast
receivers.
In the network with a stable topology, the PW on PE1 is configured as a static router interface
in the VSI. Therefore, receivers can steadily receive multicast data.
To reduce the number of IGMP Query packets from the upstream router, you should configure
PE2 as a querier. This saves bandwidths.

Figure 5-27 Networking diagram of configuring the sub-interface for QinQ VLAN tag
termination to support IGMP snooping in a VPLS network

1.1.1.1/32 2.2.2.2/32 3.3.3.3/32
IGMP Source
PE1 P PE2
GE1/0/1 GE1/0/1 GE1/0/1
GE1/0/0 GE1/0/0
Q-in-Q GE1/0/0
Termination MPLS Network
IP 20 100
GE1/0/1
CE1
IP 100 GE1/0/0
VLAN100
GE1/0/1
CE2
GE1/0/0
PC
Device Interface IP Address
PE1 GE 1/0/0 -
GE 1/0/1 192.168.12.1/24
Loopback 1 1.1.1.1/32
P GE 1/0/0 192.168.12.2/24
GE 1/0/1 192.168.23.1/24
Loopback 2 2.2.2.2/32
PE2 GE 1/0/0 192.168.23.2/24
GE 1/0/1 -
Loopback 3 3.3.3.3/32
1. Configure the termination mode on PE1 to the user termination mode.

3. Enable global IGMP snooping and IGMP snooping for a VSI.
4. Bind a VSI to an AC interface on PE1 and PE2 respectively.
5. Configure a PW on PE1, P, and PE2, and PE1, P, and PE2 accesses the VPLS network in
asymmetrical mode.

6. Configure static router ports and configure PE2 as a querier.
Data Preparation
l Inner VLAN ID
l Outer VLAN ID
l ID of the VSI
l MPLS LSR IDs of PE1, P, and PE2
Procedure
Step 1 Configure the mode of the QinQ interface on PE1 to the user termination mode.
Step 2 Configure QinQ termination on PE1.

[PE1-GigabitEthernet1/0/0.1] qinq termination l2 asymmetry
Step 3 Configure IGP on the MPLS backbone network. In this example, OSPF is adopted to advertise
routes. When configuring OSPF, advertise the 32-bit loopback interface addresses of PE1 and
PE2.
# Configure PE1.
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure P.
[HUAWEI] sysname P
[P-LoopBack2] quit

[P] ospf
[P-ospf-1] area 0
[P-ospf-1] quit
# Configure PE2.
[PE2-LoopBack3]quit
[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
Step 4 Configure basic MPLS functions and LDP.
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
# Configure P.
[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
Step 5 Enable MPLS L2VPN and configure a VSI.

# Configure PE1.
[PE1] mpls l2vpn
[PE1-l2vpn] quit
[PE1-vsi-v123-ldp] peer 3.3.3.3
[PE1-vsi-v123] quit
# Configure PE2.
[PE2] mpls l2vpn
[PE2-l2vpn] quit
[PE2-vsi-v123-ldp] peer 1.1.1.1 upe
[PE2-vsi-v123] quit
Step 6 Configure remote MPLS LDP sessions for PE1 and PE2.
# Configure PE1.
# Configure PE2.
Step 7 Bind the interface to the VSI on a PE.

# Configure PE1. The configurations of GE 1/0/1 on PE2 are similar to the configuration of PE1,
and are not mentioned here.
[PE1] vlan 10
[PE1-vlan10] quit
Step 8 Enable global IGMP snooping on the PE1 and PE2 and IGMP snooping in the VSI.
# Configure PE1. The configurations of PE2 is similar to the configuration of PE1 and are not
mentioned here.
[PE1] igmp-snooping enable
[PE1] vsi v123
[PE1-vsi-v123] igmp-snooping enable
Step 9 Configure the PW on PE1 as a static router port, and configure the querier on PE2. The default
values are used for the querier and thus no special configuration is required.
# Configure PE1.
[PE1] vsi v123
[PE1-vsi-v123] igmp-snooping static-router-port remote-peer 3.3.3.3
# Configure PE2.
[PE2] igmp-snooping send-query enable
[PE2] vsi v123

[PE2-vsi-v123] igmp-snooping querier enable

[PE2-vsi-v123] quit

Run the display qinq information termination interface command on PE1, and you can view
information about the configured QinQ sub-interface.
<PE1> display qinq information termination interface gigabitethernet 1/0/0
VSI bound
qinq termination l2 asymmetry
Total QinQ Num: 1
Run the display mpls ldp session command, and you can view that the MPLS LDP sessions
between PE1, P, and PE2 are in the Operational state.
<PE1>display mpls ldp session
------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Run the display igmp-snooping querier vsi command on PE1, and you can check whether the
configuration of the querier succeeds. If the Enable state is displayed in the following output,
it indicates that the querier is enabled for VSI v123.
<PE1> display igmp-snooping querier vsi v123
VSI Querier-state
-----------------------------------------------
v123 Enable
Run the display igmp-snooping router-port vsi command on PE1, and you can check whether
the configuration of the static router port succeeds. If STATIC is displayed as shown in the
following output, it indicates that PW (1.1.1.1/123) is configured as a static router port.
<PE1> display igmp-snooping router-port vsi v123
---------------------------------------------------------------------
PW(1.1.1.1/123) 00:06:59 -- STATIC
Run the display igmp-snooping port-info [ vlan vlan-id [ group-address group-address ] |

vsi vsi-name [ group-address group-address ] ] [ slot slot-id ] [ verbose ] on PE1, and you can
view information about multicast VLAN tags and multicast groups on a specified QinQ interface.
<UPE> display igmp-snooping port-info
-----------------------------------------------------------------------
-----------------------------------------------------------------------
(1.1.1.1, 234.1.1.1) GE1/0/0.2(PE:20/CE:100) -D-
1 port(s)
-----------------------------------------------------------------------
<UPE> display igmp-snooping port-info slot 1
-----------------------------------------------------------------------

-----------------------------------------------------------------------
(1.1.1.1, 234.1.1.1) P--
GE1/1/0.2(PE:20/CE:100) -D-
1 port(s) include
-----------------------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
#
igmp-snooping send-query
enable
#
vlan
10
#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
vsi v123 static
pwsignal ldp
vsi-id 123
peer 3.3.3.3
#
mpls ldp
#
remote-ip 3.3.3.3
undo remote-ip pwe3
#
#
l2 binding vsi v123
#
ip address 192.168.12.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 192.168.12.0 0.0.0.255
#
return
#
sysname P

#
mpls lsr-id 2.2.2.2
mpls
#
mpls ldp
#
ip address 192.168.12.2 255.255.255.0
mpls
mpls ldp
#
ip address 192.168.23.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack2
ip address 2.2.2.2 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 192.168.12.0 0.0.0.255
network 192.168.23.0 0.0.0.255
#
return
#
sysname PE2
#
vlan batch 10
#
igmp-snooping send-query enable
#
mpls lsr-id 3.3.3.3
mpls
#
mpls l2vpn
#
vsi v123 static
pwsignal ldp
vsi-id 123
peer 1.1.1.1
igmp-snooping querier enable
#
mpls ldp
#
remote-ip 1.1.1.1
undo remote-ip pwe3
#
ip address 192.168.23.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
portswitch
igmp-snooping static-router-port vlan 10
#
vlan-type dot1q 10
l2 binding vsi v123

#
interface LoopBack3
ip address 3.3.3.3 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.3 0.0.0.0
network 192.168.23.0 0.0.0.255
#
return

#
sysname CE1
#
vlan batch 20
#
portswitch
#
portswitch
#
return

#
sysname CE2
#
vlan batch 100
#
portswitch
#
portswitch
#
return
5.14.22 Example for Configuring the dot1q Termination Sub-

interface to Support IGMP and Access an L3VPN
IGMP is used by IP hosts and adjacent multicast static routers to establish multicast group
memberships. Therefore, IGMP is applied where hosts and routers are connected. In addition,
IGMP can be used where hosts and routers are of different versions. This example shows how
to configure a sub-interface for Dot1q termination on a PE to support IGMP and to access a
L3VPN. Thus, the hosts connected to the PE can join the related multicast groups to receive
multicast traffic.
As shown in Figure 5-28, multicast protocol packets sent by CE1 to PE1 carry one tag. The sub-
interface for dot1q VLAN tag termination is configured on PE1, and PE1 can access the L3VPN..
Therefore, hosts connected to CE1 can join related multicast groups normally, and then receive
multicast data.

Figure 5-28 Networking diagram of configuring the dot1q termination sub-interface to support
IGMP and access an L3VPN
L3VPN
1.1.1.9/32 2.2.2.9/32 3.3.3.9/32
GE1/0/1 GE1/0/1
Source
PE1 P PE2
192.168.12.1/24 192.168.23.2/24
GE1/0/0 GE1/0/1
192.168.12.2/24 192.168.23.1/24 GE1/0/0.1
GE1/0/0.1
10.2.1.1/24
10.1.1.1/24 Dot1q Termination
GE1/0/0
CE1
1. Configure the interface mode on PE1 and PE2 to the user termination mode.
2. Enable global IGMP .
3. Run an IGP to ensure the connectivity between devices on the backbone network.
4. Configure basic MPLS functions on the backbone network.
5. Configure a VPN instance and the sub-interface for dot1q VLAN tag termination on PE1
and bind the sub-interface for dot1q VLAN tag termination to the VPN instance.
6. Enable IGMP on the dot1q termination sub-interfaces of PE1.
7. Set up MP-IBGP peer relationships between the PEs.
Data Preparation
l Name of the interface connecting the PE to the CE
l IGMP version
l Names of the VPN instances on PE1 and PE2
l Tag values of the sub-interface for QinQ VLAN tag termination
Procedure
Step 1 Configure the interface mode to the user termination mode.
# Configure PE1.

# Configure PE2.
Step 2 Configure an IGP over the MPLS backbone network. OSPF is used as the IGP protocol in this
example.
Assign an IP address to each interface on the PEs and P as shown in Figure 5-28. When
configuring OSPF, advertise the 32-bit loopback interface addresses of PE1, P, and PE2.
# Configure PE1.
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure P.
[HUAWEI] sysname P
[P-LoopBack1] quit
[P] ospf
[P-ospf-1] area 0
[P-ospf-1] quit
# Configure PE2.

[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
After the preceding configurations, PE1 and PE2 have routes discovered through OSPF to
Loopback 1 of each other. PE1 and PE2 can ping through each other.
Step 3 Enable basic MPLS functions and LDP over the MPLS backbone network.
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
# Configure P.
[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
[P] interface gigabitethernet1/0/0
[P] interface gigabitethernet1/0/1
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
After the preceding configurations, LDP sessions should be set up between PE1 and P, and
between PE2 and P. Running the display mpls ldp session command, you can view that
Status is Operational. Run the display mpls ldp command, and you can view whether LDP
sessions are set up.

------------------------------------------------------------------------------
------------------------------------------------------------------------------
2.2.2.9:0 Operational DU Active 000:00:05 22/22

------------------------------------------------------------------------------
<PE1> display mpls ldp
LDP Global Information

------------------------------------------------------------------------------
Protocol Version : V1 Neighbor Liveness : 600 Sec
Graceful Restart : Off FT Reconnect Timer : 300 Sec
MTU Signaling : On Recovery Timer : 300 Sec
LDP Instance Information

------------------------------------------------------------------------------
Instance ID : 0 VPN-Instance :
Instance Status : Active LSR ID : 1.1.1.9
Hop Count Limit : 32 Path Vector Limit : 32
Loop Detection : Off
DU Re-advertise Timer : 10 Sec DU Re-advertise Flag : On
DU Explicit Request : Off Request Retry Flag : On
Label Distribution Mode : Ordered Label Retention Mode : Liberal
------------------------------------------------------------------------------
Step 4 Configure VPN instances on the PEs. Bind VPN instances and sub-interfaces for dot1q VLAN
tag termination.
# Configure PE1.
[PE1-vpn-instance-vpn1] multicast routing-enable
# Configure PE2.
NOTE
Values of VLAN IDs for dot1q termination on different sub-interfaces cannot overlap.
After the configuration, run the display ip vpn-instance verbose command on the PEs to view
the configurations of VPN instances.
<PE1> display ip vpn-instance verbose


Create date : 2008/08/29 10:50:18
Interfaces : Gigabitethernet1/0/0.1

# Configure PE1.
[PE1] bgp 100
# Configure PE2.
[PE2] bgp 100
After the configuration, run the display bgp peer or display bgp vpnv4 all peer command on
a PE, and you can view that the BGP peer relationship between PEs is in the Established state.

3.3.3.9 4 100 2 6 0 00:01:03 Established 0

[PE1] display bgp vpnv4 all peer

3.3.3.9 4 100 4 8 0 00:03:06 Established 0
Step 6 Enable global IGMP and configure the IGMP version.

# Configure PE1, enable IGMP and PIM-SM on PE1, and configure the IGMP version to
IGMPv2. The configurations of PE2 and P are the same as that of PE1, and are not mentioned
here.
[PE1] multicast routing-enable
[PE1-GigabitEthernet1/0/0] pim sm
[PE1-GigabitEthernet1/0/0] igmp enable
[PE1-GigabitEthernet1/0/0] igmp version 2
[PE1-GigabitEthernet1/0/0.1] pim sm
[PE1-GigabitEthernet1/0/0.1] igmp enable
[PE1-GigabitEthernet1/0/0.1] igmp version 2


# Configure CE1.

Run the display dot1q information termination command, and you can view information about
the configured sub-interface for dot1q VLAN tag termination. You can also find that the sub-
interfaces are bound to the L3VPN.
L3VPN bound
Total QinQ Num: 1
Run the display igmp [ vpn-instance vpn-instance-name | all-instance ] group [ group-

address | interface interface-type interface-number ] [ verbose ] command, and you can view
information about members of a group.
[PE1]display igmp group
GigabitEthernet1/0/1.1(1.1.1.9):
227.0.0.1 192.168.12.1 00:00:05 00:02:05
----End
Configuration Files
#
sysname
PE1
#
multicast routing-
enable
#
ip vpn-instance
vpn1
route-distinguisher
100:1
vpn-target 100:1 export-
extcommunity
vpn-target 100:1 import-
extcommunity
#
mpls lsr-id
1.1.1.9
mpls

#
mpls
ldp
#
interface
Gigabitethernet1/0/0
mode user-
termination
ip address 191.162.1.1
255.255.255.0
pim
sm
igmp
enable
#
interface
termination
ip binding vpn-instance
vpn1
ip address 10.1.1.1
255.255.255.0
igmp enable
#
interface
ip address 192.168.12.1
255.255.255.0
#
interface
LoopBack1
ip address 1.1.1.9
255.255.255.255
#
bgp
100
peer 3.3.3.9 as-number
100
peer 3.3.3.9 connect-interface
LoopBack1
#
ipv4-family
unicast
undo
synchronization
peer 3.3.3.9
enable
#
ipv4-family
vpnv4
policy vpn-
target
peer 3.3.3.9
enable
#
ospf
1
area
0.0.0.0
network 1.1.1.9
0.0.0.0
network 192.168.12.0
0.0.0.255

#
return
#
sysname
P
#
multicast routing-
enable
#
mpls lsr-id
2.2.2.9
mpls
#
mpls
ldp
#
interface
ip address 192.168.12.2 255.255.255.0
pim
sm
igmp enable
mpls
mpls
ldp
#
interface
ip address 192.168.23.1
255.255.255.0
pim
sm
igmp
enable
mpls
mpls
ldp
#
interface
LoopBack1
ip address 2.2.2.9
255.255.255.255
#
ospf
1
area
0.0.0.0
network 2.2.2.9
0.0.0.0
network 192.168.12.0
0.0.0.255
network 192.168.23.0
0.0.0.255
#
return
#
sysname
PE2
#
multicast routing-
enable
#

ip vpn-instance
vpn1
route-distinguisher
100:1
extcommunity
extcommunity
#
mpls lsr-id
3.3.3.9
mpls
#
mpls
ldp
#
interface
pim sm
igmp enable
#
interface
termination
vpn1
ip address 10.2.1.1 255.255.255.0
igmp enable
#
interface
ip address 192.168.23.2
255.255.255.0
pim
sm
igmp
enable
mpls
mpls
ldp
#
interface
LoopBack3
ip address 3.3.3.9
255.255.255.255
#
bgp
100
100
LoopBack3
#
ipv4-family
unicast
undo
synchronization
peer 1.1.1.9
enable
#
ipv4-family

vpnv4
policy vpn-
target
peer 1.1.1.9
enable
#
ospf
1
area
0.0.0.0
network 3.3.3.9
0.0.0.0
network 192.168.23.0
0.0.0.255
#
return

#
sysname CE1
#
vlan batch 100
#
interface gigabitethernet1/0/0
undo shutdown
#
return

interface to Support IGMP and Access an L3VPN
By sending IGMP Query messages to hosts and receiving IGMP Join messages and IGMP Leave
messages from hosts, a multicast router can identify the receivers (multicast group members)
on the connected network segment. This example shows how to configure a sub-interface for
QinQ termination to support IGMP on a PE and to access a L3VPN. Thus, the hosts connected
to the PE can communicate with the upper-layer multicast source.
As shown in Figure 5-29, CE1 sends the data packets of users to PE1 through CE2. CE2 labels
the user packets received from CE1 with tag 100. Thus, the multicast protocol packets of users
sent by CE2 to PE1 carry two tags. Configure the sub-interface for QinQ VLAN tag termination
to support IGMP on PE1. PE1 can then access the L3VPN. Therefore, the hosts connected to
PE1 can interwork with the upper-layer multicast source.

Figure 5-29 Example for Configuring the Sub-interface for QinQ VLAN Tag Termination to
Support IGMP and Access an L3VPN
L3VPN
1.1.1.9/32 2.2.2.9/32 3.3.3.9/32
GE1/0/1 GE1/0/1 PE2
PE1 P
192.168.12.1/24 192.168.23.2/24
GE1/0/0 GE1/0/1
192.168.12.2/24 192.168.23.1/24 GE1/0/0.1
GE1/0/0.1 Q-in-Q 10.2.1.1/24
10.1.1.1/24 Termination
GE1/0/0
CE2
GE1/0/1
VLAN 100
GE1/0/0 Source
CE1
1. Configure the interface mode on PE1 and PE2 to the user termination mode.
2. Run an IGP to ensure the connectivity of devices on the backbone network.
4. Configure a VPN instance and the sub-interface for QinQ VLAN tag termination on a PE
and bind the VPN instance to the sub-interface for QinQ VLAN tag termination on the PE.
5. Configure EBGP on the CE and the PE to exchange VPN routing information.
6. Set up MP-IBGP peer relationships between the PEs.
Data Preparation
l Name of the interface connecting the PE to the CE

l IP address of the interface.
l IGMP version
l Names of the VPN instances on PE1 and PE2
l Tag values of the sub-interface for QinQ termination

Procedure
Step 1 Configure the interface mode to the user termination mode.
# Configure PE1.
# Configure PE2.
Step 2 Configure an IGP over the MPLS backbone network, and configure basic MPLS functions and
LDP. For details, see Example for Configuring the dot1q Termination Sub-interface to
Support IGMP and Access an L3VPN.
Step 3 Configure VPN instances on the PEs. Bind the VPN instances and the sub-interfaces for QinQ
# Configure PE1.
# Configure PE2.
NOTE
When you run the qinq termination command, specify two different values of ce-vid on the two sub-
interfaces if the values of pe-vid on the two sub-interfaces are the same.
Step 4 Set up MP-IBGP peer relationships between PEs.

# Configure PE1.

[PE1] bgp 100

# Configure PE2.
[PE2] bgp 100
Step 5 Set up the EBGP peer relationships between the PEs and the CEs to import VPN routes.
# Configure CE1.
[CE1] bgp 65410
# Configure PE1.
[PE1] bgp 100
[PE1-bgp-vpn1] quit
# Configure PE2.
[PE2] bgp 100
[PE2-bgp-vpn1] quit
After the configuration, run the display bgp peer or display bgp vpnv4 all peer command on
a PE, and you can view that the BGP peer relationship between PEs is in the Established state.
Step 6 Enable global IGMP and configure the IGMP version.
# Configure PE1, enable IGMP and PIM-SM on PE1, and configure the IGMP version to
IGMPv2. The configurations of PE2 and P are the same as that of PE1, and are not mentioned
here.
[PE1] multicast routing-enable
[PE1-GigabitEthernet1/0/0] pim sm
[PE1-GigabitEthernet1/0/0] igmp enable
[PE1-GigabitEthernet1/0/0] igmp version 2
[PE1-GigabitEthernet1/0/0.1] pim sm
[PE1-GigabitEthernet1/0/0.1] igmp enable
[PE1-GigabitEthernet1/0/0.1] igmp version 2
Step 7 Configure the QinQ function. The packets sent by the CEs to the PEs then carry double tags.
# Configure CE1.
[CE1] vlan 100
[CE1-vlan100] quit


# Configure CE2.
[CE2] vlan 10
[CE2-vlan10] quit
[CE2-GigabitEthernet1/0/1] port vlan-stacking vlan 100 stack-vlan 10

Run the display qinq information termination command, and you can view information about
QinQ termination and that the sub-interface is bound to the L3VPN.
<PE1> display qinq information termination interface gigabitethernet 1/0/0
VSI bound
Total QinQ Num: 1
Run the display igmp [ vpn-instance vpn-instance-name | all-instance ] group [ group-

address | interface interface-type interface-number ] [ verbose ] command, and you can view
information about members of a group.
<PE1> display igmp group
GigabitEthernet1/0/1.1(1.1.1.9):
226.0.0.1 192.168.0.1 00:00:03 00:02:07
----End
Configuration Files
#
sysname CE1
#
vlan batch 100
#
undo shutdown
#
bgp 65410
#
ipv4-family unicast
import-route direct


#
return
#
sysname CE2
#
vlan batch 10
#
undo shutdown
#
undo shutdown
#
return
#
sysname
PE1
#
multicast routing-
enable
#
ip vpn-instance
vpn1
route-distinguisher
100:1
extcommunity
extcommunity
#
mpls lsr-id
1.1.1.9
mpls
#
mpls
ldp
#
interface
mode user-
termination
ip address 191.162.1.1
255.255.255.0
pim
sm
igmp
enable
mpls
mpls
ldp
#
interface
control-vid 20 qinq-
termination
qinq termination pe-vid 10 ce-vid
100
vpn1
ip address 10.1.1.1 255.255.255.0


#
interface
ip address 192.168.12.1 255.255.255.0
mpls
mpls ldp
#
interface
LoopBack1
ip address 1.1.1.9
255.255.255.255
#
bgp
100
100
LoopBack1
#
ipv4-family
unicast
undo
synchronization
peer 3.3.3.9
enable
#
ipv4-family
vpnv4
policy vpn-
target
peer 3.3.3.9
enable
#
ospf
1
area
0.0.0.0
network 1.1.1.9
0.0.0.0
network 192.168.12.0
0.0.0.255
#
return
#
sysname
P
#
multicast routing-
enable
#
mpls lsr-id
2.2.2.9
mpls
#
mpls
ldp
#
interface
ip address 192.168.12.2
255.255.255.0
mpls
mpls

ldp
#
interface
ip address 192.168.23.1
255.255.255.0
pim
sm
igmp
enable
mpls
mpls
ldp
#
interface
LoopBack1
ip address 2.2.2.9
255.255.255.255
#
ospf
1
area
0.0.0.0
network 2.2.2.9
0.0.0.0
network 192.168.12.0
0.0.0.255
network 192.168.23.0
0.0.0.255
#
return
#
sysname PE2
#
ip vpn-instance
vpn1
route-distinguisher
100:1
extcommunity
extcommunity
#
mpls lsr-id
3.3.3.9
mpls
#
mpls
ldp
#
interface
pim sm
igmp enable
#
interface
control-vid 20 qinq-
termination
qinq termination pe-vid 10 ce-vid
100
vpn1
ip address 10.2.1.1 255.255.255.0


#
interface
ip address 192.168.23.2
255.255.255.0
pim
sm
igmp
enable
mpls
mpls ldp
#
interface
LoopBack1
ip address 3.3.3.9
255.255.255.255
#
bgp
100
100
LoopBack3
#
ipv4-family
unicast
undo
synchronization
peer 1.1.1.9
enable
#
ipv4-family
vpnv4
policy vpn-
target
peer 1.1.1.9
enable
#
ospf
1
area
0.0.0.0
network 3.3.3.9
0.0.0.0
network 192.168.23.0
0.0.0.255
#
return

interface to Support Single-AS MD VPN
By configuring sub-interfaces for QinQ VLAN tag termination on a PE, access users can join
multicast groups and receive multicast data.
NOTE
The example for configuring the QinQ termination sub-interface to support single-AS MD VPN cannot be
configured on the X1 and X2 models of the NE80E/40E.

In the single-AS MPLS/BGP VPN shown in Figure 5-30, the MD solution is used to deploy
multicast services.
On PE-B and PE-C, configure sub-interfaces for QinQ termination to access VPNs. Ensure that
the users of CE-Bc can join the required multicast groups to receive multicast traffic.
Figure 5-30 Networking diagram of configuring single-AS MD VPN

Source
GE1 Loopback1
VPN
BLUE GE2
Loopback1
CE-Bb Public
GE2.1
PE-B GE1 P PE-C
GE2 GE3
Loopback2
GE1
GE3.1
Loopback1 GE2
VPN
CE-Bc
BLUE
GE1
PC
NOTE
In Table 5-7, GE1 stands for GE 1/0/0, GE2 stands for GE 2/0/0, GE3 stands for GE 3/0/0, GE2.1 stands
for GE 2/0/0.1 and GE3.1 stands for GE 3/0/0.1. The IP address of each interface is shown in the following
table.
The devices support two processing modes of the multicast VPN service: distributed mode and integrated
mode. In distributed mode, you must run the multicast-vpn slot command to specify the slot that supports
multicast VPN in all cases except that both the upstream and downstream interfaces of the LPUF-20/21 or
LPUF-40 forwarding multicast VPN traffic are physical interfaces. In integrated mode, you must run the
set board-type slot and multicast-vpn slot commands to set the service mode of the SPUC to be Tunnel
mode and enable multicast VPN on an SPUC separately. The following configuration example use the
distributed mode to configure the multicast VPN service.
Table 5-7 Configuration information about interfaces
Device IP Address of Interface Remarks
P GE2: 192.168.7.2/24 -
GE3: 192.168.8.2/24 -
Loopback1: 2.2.2.2/32 Functioning as C-RP of the public

network
PE-B GE1: 192.168.7.1/24 Public network instance
GE2.1: 10.110.3.1/24 VPN-BLUE instance

Device IP Address of Interface Remarks
Loopback1: 1.1.1.2/32 Public network instance

Loopback 1 interfaces of PE-A, PE-B,
and PE-C set up IBGP peer
relationships.
PE-C GE1: 192.168.8.1/24 Public network instance
GE3.1: 10.110.6.1/24 VPN-BLUE instance
Loopback1: 1.1.1.3/32 Public network instance

Loopback 1 interfaces of PE-A, PE-B,
and PE-C set up IBGP peer
relationships.
Loopback2: 33.33.33.33/32 VPN-BLUE instance

Acts as C-RP of VPN-BLUE
Source 10.110.8.2/24 Multicast source in the VPN-BLUE
PC 10.110.11.2/32 Multicast receiver in the VPN-BLUE
Table 5-8 Networking requirements of Single-AS MD VPN solution

Item Networking Requirements
Multicast Multicast source of VPN BLUE is Source. The receiver is PC. In VPN BLUE,
source/ Share-Group address is 239.2.2.2 and Switch-Group address pool ranges from
receiver 225.4.4.1 to 225.4.4.16.
VPN On PE-B, GE2.1 belongs to VPN-BLUE instance, and GE1 and Loopback1
instance belong to the public network instance. On PE-C, GE3.1 and Loopback2 belong
which the to VPN-BLUE instance, and GE1 and Loopback1 belong to the public network
interfaces instance.
on PEs
belong to
Routing Configure OSPF on the public network. Establish a BGP peer connection and
protocol transmit all VPN routes between Loopback1 interfaces on PE-B and PE-C.
and MPLS Enable MPLS forwarding on the public network.
Multicast Enable multicast on P. Enable multicast on the public network instance on PE-
function B and PE-C. Enable multicast on VPN-BLUE instance on PE-B and PE-C.
PIM Enable PIM-SM on all the VPN interfaces in VPN-BLUE instance. Enable
function PIM-SM on all the interfaces of P and CEs, as well as public network instance
interfaces of PEs. Configure Loopback1 of P as the C-BSR and C-RP of public
network (serving all multicast groups). Configure Loopback2 of PE-C as the
C-BSR and C-RP of VPN-BLUE (serving all multicast groups).
QinQ The packets sent from CE to the PE contain the inner tag 10 and the outer tag
function 100.

1. Configure QinQ on each CE.
2. Configure the sub-interfaces of PE-B and PE-C with the user termination mode.
3. Configure the MPLS/BGP VPN to ensure that the VPN works normally and unicast routes
are reachable.
4. Configure sub-interfaces for QinQ termination on the PE-B and PE-C, and bind the sub-
interfaces to the VPN instance.
5. Enable multicast VPN services of integrated mode.
6. Enable multicast and PIM in the entire network. Enable multicast of public network on PEs
and Ps, and enable multicast of the VPN instances on PEs and CEs.
7. Configure the same Share-group address, the same MTI, and the same switch-group-pool
for the same VPN instance on each PE.
8. Configure the MTI address of each PE as the IBGP peer interface address in the public
network, and enable PIM on the MTI.
Data Preparation
See Table 5-8.
Procedure
Step 1 Configure the QinQ function.
# Configure CE-Bb.
[HUAWEI] sysname CE-Bb
[CE-Bb] vlan 100
[CE-Bb-vlan100] quit
[CE-Bb] interface gigabitethernet 2/0/0
[CE-Bb-GigabitEthernet2/0/0] port trunk allow-pass vlan 100
[CE-Bb-GigabitEthernet2/0/0] undo shutdown
[CE-Bb-GigabitEthernet2/0/0] quit
[CE-Bb] interface gigabitethernet 1/0/0
[CE-Bb-GigabitEthernet1/0/0] port vlan-stacking outside-vlan 10 stack-vlan 100
[CE-Bb-GigabitEthernet1/0/0] undo shutdown
[CE-Bb-GigabitEthernet1/0/0] quit
# Configure CE-Bc.
[HUAWEI] sysname CE-Bc
[CE-Bc] vlan 100
[CE-Bc-vlan100] quit
[CE-Bc] interface gigabitethernet 2/0/0
[CE-Bc-GigabitEthernet2/0/0] port trunk allow-pass vlan 100
[CE-Bc-GigabitEthernet2/0/0] undo shutdown
[CE-Bc-GigabitEthernet2/0/0] quit
[CE-Bc] interface gigabitethernet 1/0/0
[CE-Bc-GigabitEthernet1/0/0] port vlan-stacking outside-vlan 10 stack-vlan 100
[CE-Bc-GigabitEthernet1/0/0] undo shutdown
[CE-Bc-GigabitEthernet1/0/0] quit
Step 2 Configure the interface with the user termination mode.

# Configure PE-B.

[HUAWEI] sysname PE-B
[PE-B] interface gigabitethernet 2/0/0
[PE-B-GigabitEthernet2/0/0] mode user-termination
[PE-B-GigabitEthernet2/0/0] undo shutdown
[PE-B-GigabitEthernet2/0/0] quit
# Configure PE-C
[HUAWEI] sysname PE-C
[PE-C] interface gigabitethernet 3/0/0
[PE-C-GigabitEthernet3/0/0] mode user-termination
[PE-C-GigabitEthernet3/0/0] undo shutdown
[PE-C-GigabitEthernet3/0/0] quit
Step 3 Configure PE-B.

# Configure an ID for PE-B, enable multicast in the public network, configure MPLS LSR-ID,
and enable LDP.
[PE-B] router id 1.1.1.2
[PE-B] multicast routing-enable
[PE-B] mpls lsr-id 1.1.1.2
[PE-B] mpls
[PE-B-mpls] quit
[PE-B] mpls ldp
[PE-B-mpls-ldp] quit
# Set the service mode of the SPUC to be Tunnel mode.Enable multicast VPN services on the
SPUC of the PE. Suppose that the SPUC is in slot 4, the configuration is as follows:
[PE-B] quit
<PE-B> set board-type slot 4 tunnel
<PE-B> system-view
[PE-B] multicast-vpn slot 4
# Create VPN BLUE instance and enter the VPN instance view. Configure VPN IPv4 prefix
and create the egress and ingress routes for the instance. Enable IP multicast and configure Share-
Group. Specify an MTI bound to the VPN instance and the range of the switch-address-pool.
[PE-B] ip vpn-instance BLUE
[PE-B-vpn-instance-BLUE] route-distinguisher 200:1
[PE-B-vpn-instance-BLUE] vpn-target 200:1 export-extcommunity
[PE-B-vpn-instance-BLUE] vpn-target 200:1 import-extcommunity
[PE-B-vpn-instance-BLUE] multicast routing-enable
[PE-B-vpn-instance-BLUE] multicast-domain share-group 239.2.2.2 binding mtunnel 1
[PE-B-vpn-instance-BLUE] multicast-domain switch-group-pool 225.4.4.1 28
# Enable LDP and PIM-SM on the interface GE 1/0/0 in the public network.
[PE-B] interface gigabitethernet 1/0/0
[PE-B-GigabitEthernet1/0/0] ip address 192.168.7.1 24
[PE-B-GigabitEthernet1/0/0] pim sm
[PE-B-GigabitEthernet1/0/0] mpls
[PE-B-GigabitEthernet1/0/0] mpls ldp
# Bind the interface GE 2/0/0.1 to VPN BLUE instance, and enable PIM-SM.
[PE-B] interface gigabitethernet 2/0/0.1
[PE-B-GigabitEthernet2/0/0.1] ip binding vpn-instance BLUE
[PE-B-GigabitEthernet2/0/0.1] ip address 10.110.3.1 24
[PE-B-GigabitEthernet2/0/0.1] pim sm
[PE-B-GigabitEthernet2/0/0.1] control-vid 1 qinq-termination
[PE-B-GigabitEthernet2/0/0.1] qinq termination pe-vid 100 ce-vid 10
# Assign an IP address for the interface Loopback1, and enable PIM-SM.

[PE-B] interface loopback 1

[PE-B-LoopBack1] ip address 1.1.1.2 32

[PE-B-LoopBack1] pim sm
[PE-B-LoopBack1] quit
# Assign an IP address for MTI1. The address of MTI1 is the same as that of the interface
Loopback1. Enable PIM-SM on the interface.
[PE-B] interface MTunnel 1
[PE-B-MTunnel1] ip address 1.1.1.2 32
[PE-B-MTunnel1] pim sm
# Configure BGP, OSPF, and RIP.

[PE-B] bgp 100
[PE-B-bgp] group VPN-G internal
[PE-B-bgp] peer VPN-G connect-interface LoopBack1
[PE-B-bgp] peer 1.1.1.3 group VPN-G
[PE-B-bgp] ipv4-family vpn-instance BLUE
[PE-B-bgp-BLUE] import-route rip 3
[PE-B-bgp-BLUE] import-route direct
[PE-B-bgp-BLUE] quit
[PE-B-bgp] ipv4-family vpnv4
[PE-B-bgp-af-vpnv4] peer VPN-G enable
[PE-B-bgp-af-vpnv4] peer 1.1.1.3 group VPN-G
[PE-B-bgp-af-vpnv4] quit
[PE-B-bgp] quit
[PE-B] ospf 1
[PE-B-ospf-1] area 0.0.0.0
[PE-B-ospf-1-area-0.0.0.0] network 1.1.1.2 0.0.0.0
[PE-B-ospf-1-area-0.0.0.0] network 192.168.0.0 0.0.255.255
[PE-B-ospf-1-area-0.0.0.0] quit
[PE-B-ospf-1] quit
[PE-B] rip 3 vpn-instance BLUE
[PE-B-rip-3] network 10.0.0.0
[PE-B-rip-3] import-route bgp cost 3
Step 4 Configure PE-C.

# Configure an ID for PE-C, enable IP multicast of the public network, configure MPLS LSR-
ID, and enable LDP.
[PE-C] router id 1.1.1.3
[PE-C] multicast routing-enable
[PE-C] mpls lsr-id 1.1.1.3
[PE-C] mpls
[PE-C-mpls] quit
[PE-C] mpls ldp
[PE-C-mpls-ldp] quit
# Set the service mode of the SPUC to be Tunnel mode.Enable multicast VPN services on the
SPUC of the PE. Suppose that the SPUC is in slot 4, the configuration is as follows:
[PE-C] quit
<PE-C> set board-type slot 4 tunnel
<PE-C> system-view
[PE-C] multicast-vpn slot 4
# Create VPN RED instance and enter the VPN instance view. Configure VPN IPv4 prefix and
create egress and ingress routes for the instance. Enable IP multicast and configure Share-Group.
Specify an MTI bound to the VPN instance and the range of the switch-addres-pool.
[PE-C] ip vpn-instance RED
[PE-C-vpn-instance-RED] route-distinguisher 100:1
[PE-C-vpn-instance-RED] vpn-target 100:1 export-extcommunity
[PE-C-vpn-instance-RED] vpn-target 100:1 import-extcommunity
[PE-C-vpn-instance-RED] multicast routing-enable
[PE-C-vpn-instance-RED] multicast-domain share-group 239.1.1.1 binding mtunnel 0
[PE-C-vpn-instance-RED] multicast-domain switch-group-pool 225.2.2.1 28

# Create VPN BLUE instance and enter the VPN instance view. Configure the VPN IPv4 prefix
and create egress and ingress routes for the instance. Enable IP multicast and configure Share-
Group. Specify an MTI bound to the VPN instance and the range of the switch-address-pool.
[PE-C] ip vpn-instance BLUE
[PE-C-vpn-instance-BLUE] route-distinguisher 200:1
[PE-C-vpn-instance-BLUE] vpn-target 200:1 export-extcommunity
[PE-C-vpn-instance-BLUE] vpn-target 200:1 import-extcommunity
[PE-C-vpn-instance-BLUE] multicast routing-enable
[PE-C-vpn-instance-BLUE] multicast-domain share-group 239.2.2.2 binding mtunnel 1
[PE-C-vpn-instance-BLUE] multicast-domain switch-group-pool 225.4.4.1 28
# Enable LDP and PIM-SM on the interface GE 1/0/0 in the public network.
[PE-C] interface gigabitethernet 1/0/0
[PE-C-GigabitEthernet1/0/0] ip address 192.168.8.1 24
[PE-C-GigabitEthernet1/0/0] pim sm
[PE-C-GigabitEthernet1/0/0] mpls
[PE-C-GigabitEthernet1/0/0] mpls ldp
# Bind the interface GigabitEthernet3/0/0.1 to VPN BLUE instance, and enable PIM-SM.
[PE-C] interface gigabitethernet 3/0/0.1
[PE-C-GigabitEthernet3/0/0.1] ip binding vpn-instance BLUE
[PE-C-GigabitEthernet3/0/0.1] ip address 10.110.6.1 24
[PE-C-GigabitEthernet3/0/0.1] pim sm
[PE-C-GigabitEthernet3/0/0.1] control-vid 1 qinq-termination
[PE-C-GigabitEthernet3/0/0.1] qinq termination pe-vid 100 ce-vid 10
# Assign an IP address for the interface Loopback1, and enable PIM-SM.

[PE-C] interface loopback 1
[PE-C-LoopBack1] ip address 1.1.1.3 32
[PE-C-LoopBack1] pim sm
[PE-C-LoopBack1] quit
# Assign the an IP address for MTI1. The address of MTI1 is the same as that of the interface
Loopback1. Enable PIM-SM on the interface.
[PE-C]interface MTunnel 1
[PE-C-MTunnel1] ip address 1.1.1.3 32
[PE-C-MTunnel1] pim sm
# Bind the interface Loopback2 to VPN BLUE instance, and enable PIM-SM.
[PE-C] interface loopback 2
[PE-C-LoopBack2] ip binding vpn-instance BLUE
[PE-C-LoopBack2] pim sm
[PE-C-LoopBack2] quit
# Configure the interface Loopback2 as the C-BSR and the C-RP of VPN-BLUE.
[PE-C] pim vpn-instance BLUE
[PE-C-pim-blue] c-bsr Loopback2
[PE-C-pim-blue] c-rp Loopback2
[PE-C-pim-blue] quit
# Enable BGP, OSPF, and RIP.

[PE-C] bgp 100
[PE-C-bgp] group VPN-G internal
[PE-C-bgp] peer VPN-G connect-interface LoopBack1
[PE-C-bgp] peer 1.1.1.2 group VPN-G
[PE-C-bgp] ipv4-family vpn-instance BLUE
[PE-C-bgp-BLUE] import-route rip 3
[PE-C-bgp-BLUE] import-route direct
[PE-C-bgp-BLUE] quit
[PE-C-bgp] ipv4-family vpnv4
[PE-C-bgp-af-vpnv4] peer VPN-G enable

[PE-C-bgp-af-vpnv4] peer 1.1.1.2 group VPN-G

[PE-C-bgp-af-vpnv4] quit
[PE-C-bgp] quit
[PE-C] ospf 1
[PE-C-ospf-1] area 0.0.0.0
[PE-C-ospf-1-area-0.0.0.0] network 1.1.1.3 0.0.0.0
[PE-C-ospf-1-area-0.0.0.0] network 192.168.0.0 0.0.255.255
[PE-C-ospf-1-area-0.0.0.0] quit
[PE-C-ospf-1] quit
[PE-C] rip 3 vpn-instance BLUE
[PE-C-rip] network 10.0.0.0
[PE-C-rip] import-route bgp cost 3
Step 5 Configure P.
# Enable multicast in the public network, configure MPLS LSR ID, and enable LDP.
[P] multicast routing-enable
[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
# Enable LDP and PIM-SM on GE 2/0/0 in the public network.

[P-GigabitEthernet2/0/0] pim sm
# Enable LDP and PIM-SM on GE 3/0/0 in the public network.

[P-GigabitEthernet3/0/0] pim sm
# Assign an IP address for the interface Loopback1 and enable PIM-SM.

[P-LoopBack1] pim sm
[P-LoopBack1] quit
# Configure the interface Loopback1 as the C-BSR and C-RP of the public network instance.
[P] pim
[P-pim] c-bsr Loopback1
[P-pim] c-rp Loopback1
# Configure OSPF.
[P] ospf 1
[P-ospf-1] area 0.0.0.0
After the preceding configurations are complete, PC can receive multicast information from
Source.
----End

Configuration Files
l Configuration file of PE-B
#
sysname PE-B
#
router id 1.1.1.2
#
multicast routing-enable
#
multicast-vpn slot 4
#
mpls lsr-id 1.1.1.2
mpls
#
mpls ldp
#
ip vpn-instance BLUE
multicast-domain share-group 239.2.2.2 binding MTunnel 1
multicast-domain switch-group-pool 225.4.4.0 255.255.255.240
#
undo shutdown
ip address 192.168.7.1 255.255.255.0
pim sm
mpls
mpls ldp
#
undo shutdown
#
ip binding vpn-instance BLUE
ip address 10.110.3.1 255.255.255.0
pim sm
#
interface LoopBack1
ip address 1.1.1.2 255.255.255.255
pim sm
#
interface MTunnel1
ip address 1.1.1.2 255.255.255.255
pim sm
#
bgp 100
group VPN-G internal
peer VPN-G connect-interface LoopBack1
peer 1.1.1.3 group VPN-G
#
ipv4-family unicast
peer VPN-G enable
peer 1.1.1.3 enable
#
ipv4-family vpnv4
policy vpn-target
peer VPN-G enable
peer 1.1.1.3 enable

#
ipv4-family vpn-instance BLUE
import-route rip 3
import-route direct
#
ospf 1
area 0.0.0.0
network 1.1.1.2 0.0.0.0
network 192.168.0.0 0.0.255.255
#
rip 3 vpn-instance blue
network 10.0.0.0
import-route bgp cost 3
#
return
l Configuration file of PE-C
#
sysname PE-C
#
router id 1.1.1.3
#
#
multicast-vpn slot 4
#
mpls lsr-id 1.1.1.3
mpls
#
mpls ldp
#
ip vpn-instance BLUE
multicast-domain share-group 239.2.2.2 binding MTunnel 1
multicast-domain switch-group-pool 225.4.4.0 255.255.255.240
#
undo shutdown
ip address 192.168.8.1 255.255.255.0
pim sm
mpls
mpls ldp
#
undo shutdown
#
ip address 10.110.6.1 255.255.255.0
pim sm
#
interface LoopBack1
ip address 1.1.1.3 255.255.255.255
pim sm
#
interface LoopBack2
ip address 33.33.33.33 255.255.255.255
pim sm
#
pim vpn-instance BLUE
c-bsr LoopBack2
c-rp LoopBack2
#

interface MTunnel1
ip address 1.1.1.3 255.255.255.255
pim sm
#
bgp 100
group VPN-G internal
peer VPN-G connect-interface LoopBack1
#
ipv4-family unicast
peer VPN-G enable
peer 1.1.1.2 enable
#
ipv4-family vpnv4
policy vpn-target
peer VPN-G enable
peer 1.1.1.2 enable
#
ipv4-family vpn-instance BLUE
import-route rip 3
import-route direct
#
ospf 1
area 0.0.0.0
network 1.1.1.3 0.0.0.0
network 192.168.0.0 0.0.255.255
#
rip 3 vpn-instance BLUE
network 10.0.0.0
import-route bgp cost 3
#
return
#
sysname P
#
#
mpls lsr-id 2.2.2.2
mpls
#
mpls ldp
#
undo shutdown
ip address 192.168.7.2 255.255.255.0
pim sm
mpls
mpls ldp
#
undo shutdown
ip address 192.168.8.2 255.255.255.0
pim sm
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
pim sm
#
pim
c-bsr Loopback1
c-rp Loopback1

#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 192.168.0.0 0.0.255.255
#
return
l Configuration file of CE-Bb

#
sysname CE-Bb
#
#
undo shutdown
portswitch
port vlan-stacking outside-vlan 10 stack-vlan 100
#
undo shutdown
portswtich
#
return
l Configuration file of CE-Bc

#
sysname CE-Bc
#
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return

Tag Termination to Support MPLS TE
Sub-interfaces for QinQ VLAN tag termination support MPLS TE only when the NE80E/40E
runs IS-IS. Each sub-interface can be configured with only one pair of tags.
As shown in Figure 5-31, CE1 is connected to the PEs through Switch 1. QinQ is configured
on Switch 1 so that the outer VLAN tag with the VLAN ID as 100 is added to a user packet from
CE1. The public VLAN IDs are thus saved. Then, a user packet sent from Switch 1 to PE1 carries
double VLAN tags.
CE2 is connected to the PEs through Switch 2. QinQ is configured on Switch 2 so that the outer
VLAN tag with the VLAN ID as 100 is added to a user packet from CE2. Then, a user packet
sent from Switch 2 to PE2 carries double VLAN tags.
It is required that VLAN swap be configured on GE 1/0/0 of PE1 to implement the swap of inner
and outer VLAN tags, and GE 1/0/0.1 for QinQ VLAN tag termination be configured to support
MPLS TE. It is also required that VLAN swap be configured on GE 1/0/0 of PE2 to implement

the swap of inner and outer VLAN tags, and GE 1/0/0.1 for QinQ VLAN tag termination be
configured to support MPLS TE. Then, the user networks connected to CE1 and CE2 can
communicate.
A TE tunnel is set up between PE1 and PE2 by using RSVP-TE.
NOTE
In the scenario where sub-interfaces for QinQ VLAN tag termination are configured to support MPLS TE,
IS-IS must be adopted as the routing protocol.
When configuring sub-interfaces for QinQ VLAN tag termination to support MPLS TE, note that the sub-
interfaces transmit packets with a specified inner VLAN tag and a specified outer VLAN tag.
Figure 5-31 Networking for configuring the sub-interface for QinQ VLAN tag termination to
support MPLS TE
Loopback1 Loopback1
1.1.1.9/32 2.2.2.9/32
GE1/0/0.1 GE1/0/0.1
100.1.1.1/24 100.1.1.2/24
PE1 PE2
GE2/0/0 GE2/0/0
GE1/0/0 GE1/0/0
Switch1 Switch2
GE1/0/1 GE1/0/1
CE1 CE2
VLAN 10 VLAN 10
1. Configure the mode of QinQ interfaces on PE1 and PE2 as user termination.
2. Run IS-IS on the backbone network.
4. Configure VLAN swap on PE1 and PE2 to implement the swap of inner and outer VLAN
tags.
5. Configure the basic Layer 2 forwarding function on Switch 1 and Switch 2.
6. Set up an MPLS TE tunnel between PE1 and PE2.
Data Preparation

l Names of the interfaces connecting the PEs to the CEs

l IP addresses of the sub-interfaces on the PEs
l VLAN IDs of the sub-interfaces for QinQ VLAN tag termination
Procedure
Step 1 Configure the mode of QinQ interfaces on PE1 and PE2 as user termination.
# Configure PE1.
# Configure PE2.
Step 2 Configure VLAN swap on PE1 and PE2, and the VLANs whose frames can pass through PE1
and PE2.
# Configure PE1.
[PE1-GigabitEthernet1/0/0] vlan-swap enable
# Configure PE2.
[PE2-GigabitEthernet1/0/0] vlan-swap enable
Step 3 Configure the sub-interfaces for QinQ VLAN tag termination on PE1 and PE2.
# Configure PE1.
# Configure PE2.


Step 4 Configure IGP over the MPLS backbone network. IS-IS is used as the IGP protocol in this
example.
# Configure PE1.
[PE1] isis 100
[PE1-isis-100] network-entity 00.0005.0000.0000.0001.00
[PE1-isis-100] is-level level-2
[PE1-isis-100] quit
[PE1-GigabitEthernet1/0/0.1] isis enable 100
[PE1-LoopBack1] isis enable 100
# Configure PE2.
[PE2] isis 100
[PE2-isis-100] network-entity 00.0005.0000.0000.0002.00
[PE2-isis-100] is-level level-2
[PE2-isis-100] quit
[PE2-GigabitEthernet1/0/0.1] isis enable 100
[PE2-LoopBack1] isis enable 100
Step 5 Enable basic MPLS functions, MPLS TE, and RSVP-TE on PE1 and PE2 on the MPLS backbone
network.
# Configure PE1.
[PE1] mpls
[PE1-mpls] mpls te
[PE1-mpls] mpls rsvp-te
[PE1-mpls] quit
[PE1-GigabitEthernet1/0/0.1] mpls
[PE1-GigabitEthernet1/0/0.1] mpls te
[PE1-GigabitEthernet1/0/0.1] mpls rsvp-te
# Configure PE2.
[PE2] mpls
[PE2-mpls] mpls te
[PE2-mpls] mpls rsvp-te
[PE2-mpls] quit
[PE2-GigabitEthernet1/0/0.1] mpls
[PE2-GigabitEthernet1/0/0.1] mpls te
[PE2-GigabitEthernet1/0/0.1] mpls rsvp-te
Step 6 Configure IS-IS TE.
# Configure PE1.

[PE1] isis 100

[PE1-isis-100] cost-style wide
[PE1-isis-100] traffic-eng level-2
[PE1-isis-100] quit
# Configure PE2.
[PE2] isis 100
[PE2-isis-100] cost-style wide
[PE2-isis-100] traffic-eng level-2
[PE2-isis-100] quit
Step 7 Configure MPLS TE tunnel interfaces.

# On the ingress of the tunnel, create a tunnel interface and set the IP address, tunnel protocol,
destination IP address, tunnel ID, and dynamic signaling protocol for the tunnel interface. Then,
run the mpls te commit command to commit the configuration. Advertise the routes of the tunnel
interface, ensuring that traffic is transmitted through the TE tunnel.
# Configure PE1.
[PE1] interface tunnel 1/0/0
[PE1-Tunnel1/0/0] ip address unnumbered interface loopback 1
[PE1-Tunnel1/0/0] tunnel-protocol mpls te
[PE1-Tunnel1/0/0] destination 2.2.2.9
[PE1-Tunnel1/0/0] mpls te tunnel-id 10
[PE1-Tunnel1/0/0] mpls te singal-protocol rsvp-te
[PE1-Tunnel1/0/0] mpls te igp shortcut isis
[PE1-Tunnel1/0/0] mpls te igp metric absolute 1
[PE1-Tunnel1/0/0] mpls te commit
[PE1-Tunnel1/0/0] isis enable 100
[PE1-Tunnel1/0/0] quit
After the configuration, run the display interface tunnel command on PE1. You can view that
the tunnel is Up.
[PE1] display interface tunnel
Tunnel1/0/0 current state : UP
Last line protocol up time : 2009-06-04 14:58:51
Description: Tunnel1/0/0 Interface
Internet Address is unnumbered, using address of LoopBack1(1.1.1.9/32)
Encapsulation is TUNNEL, loopback not set
Tunnel destination 2.2.2.9
Tunnel up/down statistics 1
Tunnel protocol/transport MPLS/MPLS, ILM is available,
primary tunnel id is 0x1008001, secondary tunnel id is 0x0
300 seconds output rate 0 bits/sec, 0 packets/sec
0 seconds output rate 0 bits/sec, 0 packets/sec
0 packets output, 0 bytes
0 output error
Run the display mpls te tunnel-interface command on PE1. You can view details about the
tunnel.
[PE1-Tunnel1/0/0] display mpls te tunnel-interface
Tunnel Name : Tunnel1/0/0
Tunnel State Desc : CR-LSP is Up
Tunnel Attributes :
Session ID : 10
Ingress LSR ID : 1.1.1.9 Egress LSR ID: 2.2.2.9
Admin State : UP Oper State : UP
Signaling Protocol : RSVP
Tie-Breaking Policy : None Metric Type : None
Car Policy : Disabled Bfd Cap : None
BypassBW Flag : Not Supported
BypassBW Type : - Bypass BW : -

Retry Limit : 5 Retry Int : 2 sec

Reopt : Disabled Reopt Freq : -
Auto BW : Disabled
Current Collected BW: - Auto BW Freq : -
Min BW : - Max BW : -
Tunnel Group : Primary
Interfaces Protected: -
Excluded IP Address : -
Is On Radix-Tree : Yes Referred LSP Count: 0
Primary Tunnel : - Pri Tunn Sum : -
Backup Tunnel : -
Group Status : Up Oam Status : Up
IPTN InLabel : -
BackUp Type : None BestEffort : Disabled
Secondary HopLimit : -
BestEffort HopLimit : -
Secondary Explicit Path Name: -
Secondary Affinity Prop/Mask: 0x0/0x0
BestEffort Affinity Prop/Mask: 0x0/0x0
Primary LSP ID : 1.1.1.9:1

Setup Priority : 7 Hold Priority: 7
Affinity Prop/Mask : 0x0/0x0 Resv Style : SE
CT0 Bandwidth(Kbit/sec) : 0 CT1 Bandwidth(Kbit/sec) : 0
Actual Bandwidth(kbps): -
Explicit Path Name : - Hop Limit : -
Record Route : Disabled Record Label : Disabled
Route Pinning : Disabled
FRR Flag : Disabled
IdleTime Remain : -
Create VLAN 100 on Switch 1 and configure GE 1/0/1 on Switch 1 to add the outer VLAN tag
with the VLAN ID as 100 to a packet from VLAN 10. Specify GE 1/0/0 as a trunk interface and
configure it to allow the packets from VLAN 100 to pass through.
[Switch1] vlan 100
[Switch1-GigabitEthernet1/0/1] port vlan-stacking outside-vlan 10 stack-vlan 100
Create VLAN 100 on Switch 2 and configure GE 1/0/1 on Switch 2 to add the outer VLAN tag
with the VLAN ID as 100 to a packet from VLAN 10. Specify GE 1/0/0 as a trunk interface and
configure it to allow the packets from VLAN 100 to pass through.
[Switch2] vlan 100

[Switch2-GigabitEthernet1/0/1] port vlan-stacking outside-vlan 10 stack-vlan 100

After the configuration, CE1 and CE2 can communicate.
You can view the ARP entries on the PEs. Take the command output on PE1 as an example.
[PE1] display arp all
IP ADDRESS MAC ADDRESS EXPIRE(M) TYPE INTERFACE VPN-INSTANCE
VLAN/CEVLAN PVC
------------------------------------------------------------------------------
100.1.1.1 00e0-fc7f-7258 I - GE1/0/0.1
100.1.1.2 00e0-fcc8-1b31 9 DF1 GE1/0/0.1
10/100
----End
Configuration Files
#
sysname Switch1
vlan batch 100
#
#
#
return

#
sysname Switch2
vlan batch 100
#
#
#
return

#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
mpls te
mpls rsvp-te
#
isis 100
is-level level-2
cost-style wide
network-entity 00.0005.0000.0000.0001.00
traffic-eng level-2
#
undo shutdown
portswitch

vlan-swap enable
#
undo shutdown
portswitch
#
ip address 100.1.1.1 24
isis enable 100
mpls
mpls te
mpls rsvp-te
#
interface loopback 1
ip address 1.1.1.9 255.255.255.255
isis enable 100
#
interface tunnel 1/0/0
ip address unnumbered interface loopback 1
tunnel-protocol mpls te
destination 2.2.2.9
mpls te tunnel-id 10
mpls te singal-protocol rsvp-te
mpls te igp shortcut isis
mpls te igp metric absolute 1
mpls te commit
isis enable 100
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.9
mpls
mpls te
mpls rsvp-te
#
isis 100
is-level level-2
cost-style wide
network-entity 00.0005.0000.0000.0002.00
traffic-eng level-2
#
undo shutdown
portswitch
vlan-swap enable
#
undo shutdown
portswitch
#
ip address 100.1.1.2 24
isis enable 100
mpls
mpls te
mpls rsvp-te

#
interface loopback 1
ip address 2.2.2.9 255.255.255.255
isis enable 100
#
return
5.14.26 Example for Configuring the User-Side QinQ

When the NE80E/40E is connected to users through two switches, the switch adjacent to users
adds an inner tag to each user packet (or remove the inner tag from each user packet) and the
switch adjacent to the NE80E/40E adds an outer tag to each user packet (or remove the outer
tag from each user packet). Users access the switch through BAS interfaces.
NOTE
User-Side QinQ cannot be configured on the X1 and X2 models of the NE80E/40E.
Figure 5-32 shows the networking.

l The router is connected to two switches, namely, Switch A and Switch B.
l Switch A, which is close to the user, is tagged with VLAN.
l Switch B, which is close to the router, is tagged with QinQ VLAN.
Figure 5-32 Networking of configuring user-side QinQ VLAN
User1
GE1/0/8.1
VlAN 100 192.168.10.1/24
QinQ 400
VLAN 200
Switch A Switch B Router
User2
1. Create a QinQ VLAN on the sub-interface.
2. Configure the BAS interface.
Data Preparation
l VLAN ID and QinQ VLAN ID
l Authentication mode on the sub-interface
Procedure
Step 1 Create a QinQ VLAN on the sub-interface.

[HUAWEI] interface gigabitethernet 1/0/8.1
[HUAWEI-GigabitEthernet1/0/8.1] user-vlan 100 qinq 400
[HUAWEI-GigabitEthernet1/0/8.1] user-vlan 200 qinq 400
[HUAWEI-GigabitEthernet1/0/8.1] quit
[HUAWEI-GigabitEthernet1/0/8] undo shutdown
Step 2 Configure the BAS interface.

# Configure the BAS interface and set the access type on the interface to layer-2 access.
[HUAWEI-GigabitEthernet1/0/8.1] bas
[HUAWEI-GigabitEthernet1/0/8.1] access-type layer2-subscriber
# Set the authentication mode on the interface to PPP authentication.

[HUAWEI-GigabitEthernet1/0/8.1] authentication-method ppp
[HUAWEI-GigabitEthernet1/0/8.1] quit
# Bind the sub-interface to a virtual template.

[HUAWEI-GigabitEthernet1/0/8.1] pppoe-server bind virtual-template 1
----End
Configuration Files
Configuration file of the router
#
sysname HUAWEI
#
undo shutdown
#
pppoe-server bind Virtual-Template 1
user-vlan 100 qinq 400
user-vlan 200 qinq 400
bas
access-type layer2-subscriber
authentication-method ppp
#
return

(on a Sub-interface for Dot1q VLAN Tag Termination)
In this networking, PE1 receives tagged packets with different 802.1p priorities; a sub-interface
for Dot1q VLAN tag termination and VLAN+802.1p are configured on the interface at the AC
side of PE1; the sub-interface for Dot1q VLAN tag termination is bound to different VPN
instances. Packets are transmitted through different VSIs based on the 802.1p priorities of the
packets. The following takes the scenario where a CSG accesses IP services as an example.
As shown in Figure 5-33, CE1 sends untagged packets to the CSG; the CSG sends packets
tagged with different VLAN IDs and different 802.1p priorities to PE1. It is required that the
sub-interfaces for Dot1q VLAN tag termination be configured on PEs to access the VPLS and
differentiated service transmission be implemented. In such a scenario, you can deploy VLAN
+802.1p on the sub-interface at the AC side of PE1 so that PE1 can differentiate services based
on 802.1p priorities and hence different services can be transmitted through different PWs.

Figure 5-33 Networking diagram of VLAN+802.1p for L2VPN access (on a sub-interface for
Dot1q VLAN tag termination)
VLAN 10 Loopback1
2.2.2.9/32
CE1 PE2
GE1/0/1.1
GE1/0/1
192.1.1.1/24 GE1/0/2
=3
Database
10.1.1.1/30
p
2.1
80
GE1/0/2 GE1/0/1.1 GE1/0/2
GE1/0/1.2 10.1.1.2/30
CSG
GE1/0/1 GE1/0/3
GE1/0/3 PE1 20.1.1.2/30
Loopback1
80
GE1/0/1
GE1/0/2
2.1
192.1.1.4/24 1.1.1.9/32 Internet
p
20.1.1.1/30
=2
GE1/0/1.1
CE2
PE3
VLAN 20 Loopback1
3.3.3.9/32
VLAN PW VLAN
NOTE
L2VPN includes the VLL, PWE3, and VPLS. You can configure any one of them as required. The following
1. Configure the interface mode on PEs to user termination.

2. Run an IGP to ensure intercommunication between routers on the backbone network.
3. Configure basic MPLS functions, and set up LSPs between PEs.
5. Set up VSIs and then configure them.
6. Configure sub-interfaces for Dot1q VLAN tag termination on PEs, and bind the AC
interfaces to VSIs.
7. Configure the Layer 2 forwarding function on the CEs and CSG.
Data Preparation

l VSI IDs on PEs (VSI IDs must be consistent)
l MPLS LSR IDs on PEs
l Names of the VSIs on PEs
l Names of interfaces bound to the VSIs
Procedure
the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN or the configuration files
Step 2 Configure the interface mode on PEs to user termination.
# Configure PE1.
<PE1> system-view
# Configure PE2.
<PE2> system-view
# Configure PE3.
<PE3> system-view
Step 3 Configure VLAN+802.1p.
# Configure PE1.
[PE1-GigabitEthernet1/0/1.1] dot1q termination vid 10 8021p 3
NOTE
On different sub-interfaces of the same main interface, if 802.1p priorities are different, the VIDs to be
terminated can overlap.
# Configure PE2.


# Configure PE3.
Step 4 Configure the sub-interfaces for Dot1q VLAN tag termination on PEs, and bind AC interfaces
to VSIs.
# Configure PE1.
# Configure PE2.
# Configure PE3.

following:
Step 6 Configure the Layer 2 forwarding function on CEs.
The detailed configurations are not mentioned here. You can refer to the configuration files in
Run the display dot1q information termination interface command, and you can view
information about sub-interfaces for Dot1q VLAN tag termination.
VSI bound
Total QinQ Num: 2


VSI bound
Total QinQ Num: 2
After the preceding configurations, run the display vsi name ldp1 verbose command on PE1,
state.
***VSI Name : ldp1

VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
VSI State : up
VSI ID : 1
VC Label : 30720
Peer Type : dynamic
Session : up
CKey : 2
NKey : 1
StpEnable : 0
PwIndex : 0

State : up
Last Up Time : 2009/09/02 08:46:56
**PW Information:

PW State : up
PW Type : label
Ckey : 0x2
Nkey : 0x1
Tnl Type : LSP
Stp Enable : 0

Mac Flapping : 0
PW Last Up Time : 2009/09/02 08:47:35
-----------------------------------------------------------
GE1/0/1.1 8021p 3
GE1/0/1.2 8021p 2
-----------------------------------------------------------
[PE1] display interface GigabitEthernet1/0/1 vlan 20
-----------------------------------------------------------
GE1/0/1.1 8021p 3
GE1/0/1.2 8021p 2
-----------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 2.2.2.9
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 3.3.3.9
#
mpls ldp
#
undo shutdown
#
dot1q termination vid 10 8021p 3
l2 binding vsi ldp1
#
l2 binding vsi ldp2
#
undo shutdown
ip address 10.1.1.2 255.255.255.252

mpls
mpls ldp
#
undo shutdown
ip address 20.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#
l2 binding vsi ldp1
#
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return
#
sysname PE3
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn

#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#
l2 binding vsi ldp2
#
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 20.1.1.0 0.0.0.3
#
return
#
sysname CE1
#
undo shutdown
ip address 192.1.1.1 255.255.255.0
#
return
#
sysname CE2
#
undo shutdown
ip address 192.1.1.4 255.255.255.0
#
return
5.14.28 Example for Configuring VLAN+EthType for L2VPN

Access (on a Sub-interface for Dot1q VLAN Tag Termination)
In this networking, PE1 receives tagged packets with different EthTypes; a sub-interface for
Dot1q VLAN tag termination and VLAN+EthType are configured on the interface at the AC
side of PE1; the sub-interface for Dot1q VLAN tag termination is bound to different VSIs.
Packets are transmitted through different VSIs based on the EthTypes of the packets.
As shown in Figure 5-34, CEs send untagged packets to Switch 1; Switch 1 sends packets tagged
with different VLAN IDs and different EthTypes to PE1. It is required that the sub-interfaces

for Dot1q VLAN tag termination be configured on PEs to access the VPLS and differentiated
service transmission be implemented. In such a scenario, you can deploy VLAN+EthType on
the sub-interface at the AC side of PE1 so that PE1 can differentiate services based on EthType
fields and hence different services can be transmitted through different PWs.
Figure 5-34 Networking diagram of VLAN+EthType for L2VPN access (on a sub-interface for
Loopback1
2.2.2.9/32
PE2
GE1/0/1.1
CE1
VLAN 10
GE1/0/2 Video/BTV
E
10.1.1.1/30 VOD
Po
GE1/0/1
Platform
PP
192.1.1.1/24
GE1/0/2 GE1/0/1.1 GE1/0/2
GE1/0/1.2 10.1.1.2/30
Switch1 GE1/0/1 GE1/0/3
GE1/0/3 PE1 20.1.1.2/30
Loopback1
1.1.1.9/32
IPo
GE1/0/2
VLAN 20
GE1/0/1 Internet
20.1.1.1/30
E
192.1.1.4/24
GE1/0/1.1
CE2
PE3
Loopback1
3.3.3.9/32
VLAN PW VLAN
NOTE

6. Configure sub-interfaces for Dot1q VLAN tag termination on PEs and bind AC interfaces
to VSIs.
7. Configure the Layer 2 forwarding function on CEs.

Data Preparation
Procedure
# Configure PE1.
<PE1> system-view
# Configure PE2.
<PE2> system-view
# Configure PE3.
<PE3> system-view
Step 3 Configure VLAN+EthType.
# Configure PE1.
[PE1-GigabitEthernet1/0/1.1] dot1q terminatio vid 10 eth-type pppoe
[PE1-GigabitEthernet1/0/1.1] dot1q terminatio vid 20 eth-type pppoe
[PE1-GigabitEthernet1/0/1.2] dot1q terminatio vid 10 default
[PE1-GigabitEthernet1/0/1.2] dot1q terminatio vid 20 default

NOTE
On different sub-interfaces of the same main interface, if the types of encapsulated Ethernet protocols are
different, the VIDs to be terminated can overlap.
# Configure PE2.
[PE2-GigabitEthernet1/0/1.1] dot1q terminatio vid 10
# Configure PE3.
<PE3> system-view
Step 4 Configure the sub-interfaces for Dot1q VLAN tag termination on PEs and bind AC interfaces
to VSIs.
# Configure PE1.
# Configure PE2.
# Configure PE3.
Step 5 Configure the Layer 2 forwarding function on Switch 1.
The detailed configurations are not mentioned here. For detailed configuration of the switch,
refer to the related configuration guide.
NOTE
Switch 1 sends packets tagged with different VLAN IDs and EthTypes to PE1.

VSI bound
Total QinQ Num: 2
VSI bound
Total QinQ Num: 2
state.
***VSI Name : ldp1

VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
VSI State : up
VSI ID : 1
VC Label : 30720
Peer Type : dynamic
Session : up
CKey : 2
NKey : 1
StpEnable : 0
PwIndex : 0

State : up
Last Up Time : 2009/09/02 08:46:56
**PW Information:

PW State : up
PW Type : label

Ckey : 0x2
Nkey : 0x1
Tnl Type : LSP
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2009/09/02 08:47:35
-----------------------------------------------------------
GE1/0/1.1 eth-type PPPOE
GE1/0/1.2 default
-----------------------------------------------------------
-----------------------------------------------------------
GE1/0/1.1 default
-----------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 2.2.2.9
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 3.3.3.9
#
mpls ldp
#
undo shutdown
#
dot1q termination vid 10 eth-type pppoe
dot1q termination vid 20 eth-type pppoe
l2 binding vsi ldp1
#

dot1q termination vid 10 default
dot1q termination vid 20 default
l2 binding vsi ldp2
#
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 20.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
#
return

#
sysname PE2
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#
l2 binding vsi ldp1
#
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3

#
return

#
sysname PE3
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#
l2 binding vsi ldp2
#
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 20.1.1.0 0.0.0.3
#
return

#
sysname CE1
#
undo shutdown
ip address 192.1.1.1 255.255.255.0
#
return

#
sysname CE2
#
undo shutdown
ip address 192.1.1.4 255.255.255.0
#
return


In this networking, PE1 receives tagged packets with different DSCP values; a sub-interface for
Dot1q VLAN tag termination and VLAN+DSCP are configured on the interface at the AC side
of PE1; the sub-interface for Dot1q VLAN tag termination is bound to different VSIs. Packets
are transmitted through different VSIs based on the DSCP values of the packets. The following
As shown in Figure 5-35, CE1 sends untagged packets to the CSG; the CSG sends packets
tagged with different VLAN IDs and different DSCP values to PE1. It is required that sub-
interfaces for Dot1q VLAN tag termination be configured on PEs to access the L2VPN and
differentiated service transmission be implemented. In such a scenario, you can deploy VLAN
+DSCP on the sub-interfaces at the AC side of PEs so that PEs can differentiate services based
on DSCP values and hence different services can be transmitted through different PWs.
NOTE
Figure 5-35 Networking diagram of VLAN+DSCP for L2VPN access (on a sub-interface for
VLAN 10 Loopback1
2.2.2.9/32
CE1 PE2
GE1/0/1.1
GE1/0/1 GE1/0/2
=3
Database
10.1.1.1/30
CP
192.1.1.1/24
DS
GE1/0/2 GE1/0/1.1 GE1/0/2

GE1/0/1.2 10.1.1.2/30
CSG
GE1/0/1 GE1/0/3
GE1/0/3 PE1 20.1.1.2/30
GE1/0/1 Loopback1
DS
192.1.1.4/24 1.1.1.9/32 GE1/0/2 Internet

CP
20.1.1.1/30
=2
GE1/0/1.1
CE2
PE3
VLAN 20 Loopback1
3.3.3.9/32
VLAN PW VLAN

NOTE

to VSIs.
7. Configure the basic Layer 2 forwarding function on the CSG.
Data Preparation
Procedure
# Configure PE1.
<PE1> system-view
# Configure PE2.
<PE2> system-view

# Configure PE3.
<PE3> system-view
Step 3 Configuring VLAN+DSCP.

# Configure PE1.
[PE1-GigabitEthernet1/0/1.1] dot1q terminatio vid 10 dscp 3
NOTE
On different sub-interfaces of the same main interface, if DSCP values are different, the VIDs to be
terminated can overlap.
# Configure PE2.
# Configure PE3.
Step 4 Configure the sub-interfaces for Dot1q VLAN tag termination on PEs and bind AC interfaces
to VSIs.
# Configure PE1.
# Configure PE2.
# Configure PE3.



following:
VSI bound
Total QinQ Num: 2
VSI bound
Total QinQ Num: 2
and you can view that a PW to PE2 is set up for a VSI named ldp1, and the VSI is in the Up
state.
***VSI Name : ldp1

VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
VSI State : up
VSI ID : 1


VC Label : 30720
Peer Type : dynamic
Session : up
CKey : 2
NKey : 1
StpEnable : 0
PwIndex : 0

State : up
Last Up Time : 2009/09/02 08:46:56
**PW Information:

PW State : up
PW Type : label
Ckey : 0x2
Nkey : 0x1
Tnl Type : LSP
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2009/09/02 08:47:35
Run the display interface vlan command, and you can view all the sub-interfaces with the
-----------------------------------------------------------
GE1/0/1.1 dscp 3
GE1/0/1.2 dscp 2
-----------------------------------------------------------
-----------------------------------------------------------
GE1/0/1.1 dscp 3
GE1/0/1.2 dscp 2
-----------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn

#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 2.2.2.9
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 3.3.3.9
#
mpls ldp
#
undo shutdown
#
dot1q termination vid 10 dscp 3
l2 binding vsi ldp1
#
l2 binding vsi ldp2
#
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 20.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.9
#
mpls ldp
#
undo shutdown

#
l2 binding vsi ldp1
#
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return
#
sysname PE3
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#
l2 binding vsi ldp2
#
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 20.1.1.0 0.0.0.3
#
return
#
sysname CE1
#

undo shutdown
ip address 192.1.1.1 255.255.255.0
#
return

#
sysname CE2
#
undo shutdown
ip address 192.1.1.4 255.255.255.0
#
return
5.14.30 Example for Configuring QinQ Stacking Sub-interface

+802.1p for L2VPN Access
In this networking, PE1 receives tagged packets with different 802.1p priorities; QinQ stacking
+802.1p is configured on the sub-interface at the AC side of PE1 so that an outer VLAN tag of
the ISP network is added to packets on the sub-interface; the sub-interface is bound to different
VSIs for L2VPN access. Packets are transmitted through different VSIs based on the 802.1p
priorities of the packets. The following takes the scenario where a CSG accesses IP services as
an example.
As shown in Figure 5-36, the CSG sends packets tagged with different VLAN IDs and different
802.1p priorities to PE1. It is required that QinQ stacking sub-interfaces be configured on PEs
to access the L2VPN and differentiated service transmission be implemented. In such a scenario,
you can deploy QinQ stacking+802.1p on the sub-interfaces at the AC side of PEs so that PEs
can differentiate services based on the 802.1p priorities and hence different services can be
transmitted through different PWs.

Figure 5-36 Networking diagram of QinQ stacking sub-interface+802.1p-based L2VPN access
VLAN 10 Loopback1
2.2.2.9/32
CE1 PE2
GE1/0/1.1
GE1/0/1
192.1.1.1/24 GE1/0/2
=3
p
2.1
80
GE1/0/2 GE1/0/1.1 GE1/0/2
GE1/0/1 GE1/0/1.2 10.1.1.2/30
CSG
QinQ GE1/0/3
GE1/0/3 Stacking PE1 20.1.1.2/30
Loopback1
80
GE1/0/1
GE1/0/2
2.1
192.1.1.4/24 1.1.1.9/32 Internet
p
20.1.1.1/30
=2
GE1/0/1.1
CE2
PE3
VLAN 20 Loopback1
3.3.3.9/32
VLAN PW VLAN
NOTE

6. Configure QinQ stacking sub-interfaces on PEs and bind AC interfaces to VSIs.
7. Configure the basic Layer 2 forwarding function on the CSG.
Data Preparation


Procedure
# Configure PE1.
<PE1> system-view
# Configure PE2.
<PE2> system-view
# Configure PE3.
<PE3> system-view
Step 3 Configure QinQ stacking+802.1p, and bind AC interfaces to VSIs.

# Configure PE1.
<PE1> system-view
[PE1-GigabitEthernet1/0/1.1] qinq stacking vid 10 8021p 3
# Configure PE2.
<PE2> system-view

# Configure PE3.
<PE3> system-view

following:
NOTE
Packets sent from the CSG to PE1 carry VLAN tags with different 802.1p priorities.

Run the display qinq information stacking interface command, and you can view
configurations of QinQ stacking sub-interfaces.
<PE1> display qinq information stacking interface gigabitethernet 1/0/1
Total QinQ Num: 2
Total QinQ Num: 2
state.
<PE1> display vsi name ldp1 verbose
***VSI Name : ldp1

VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255

Domain Name :
VSI State : up
VSI ID : 1
VC Label : 30720
Peer Type : dynamic
Session : up
CKey : 2
NKey : 1
StpEnable : 0
PwIndex : 0

State : up
Last Up Time : 2009/09/02 12:22:04
**PW Information:

PW State : up
PW Type : label
Ckey : 0x2
Nkey : 0x1
Tnl Type : LSP
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2009/09/02 12:22:40
specified VLAN ID on a specified interface.
<PE1> display interface gigabitethernet1/0/1 vlan 10
-----------------------------------------------------------
GE1/0/1.1 8021p 3
GE1/0/1.2 8021p 2
-----------------------------------------------------------
1
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#

mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 2.2.2.9
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 3.3.3.9
#
mpls ldp
#
undo shutdown
#
qinq stacking vid 10 8021p 3
l2 binding vsi ldp1
#
l2 binding vsi ldp2
#
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 20.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
network 1.1.1.9 0.0.0.3
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.9
#
mpls ldp
#
undo shutdown

#
l2 binding vsi ldp1
#
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return
#
sysname PE3
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#
l2 binding vsi ldp2
#
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 20.1.1.0 0.0.0.3
#
return
#
sysname CE1
#
undo shutdown
ip address 192.1.1.1 255.255.255.0

#
return

#
sysname CE2
#
undo shutdown
ip address 192.1.1.4 255.255.255.0
#
return
5.14.31 Example for Configuring Stacking Sub-interface+EthType

for L2VPN Access
In this networking, PE1 receives tagged packets with different EthTypes; QinQ stacking
+EthType is configured on the sub-interface at the AC side of PE1 so that an outer VLAN tag
of the ISP network is added to packets on the sub-interface; the sub-interface is bound to different
VSIs for L2VPN access. Packets are transmitted through different VSIs based on the EthTypes
of the packets.
As shown in Figure 5-37, Switch 1 sends packets tagged with different VLAN IDs and different
EthTypes to PE1. It is required that QinQ stacking sub-interfaces be configured on PEs to access
the L2VPN and differentiated service transmission be implemented. In such a scenario, you can
deploy QinQ stacking+EthType on the sub-interfaces at the AC side of PEs so that PEs can
differentiate services based on the EthTypes and hence different services can be transmitted
through different PWs.

Figure 5-37 Networking diagram of QinQ stacking sub-interface+EthType-based L2VPN

access
VLAN 10 Loopback1
2.2.2.9/32
CE1 PE2
GE1/0/1.1
GE1/0/1
192.1.1.1/24 GE1/0/2 Database
E
10.1.1.1/30
Po
PP
GE1/0/2 GE1/0/1.1 GE1/0/2
GE1/0/1 GE1/0/1.2 10.1.1.2/30
Switch1
QinQ GE1/0/3
GE1/0/3 Stacking PE1 20.1.1.2/30
GE1/0/1 Loopback1
IPo
192.1.1.4/24 1.1.1.9/32 GE1/0/2
Internet
20.1.1.1/30
E
GE1/0/1.1
CE2
PE3
VLAN 20 Loopback1
3.3.3.9/32
VLAN PW VLAN
NOTE

to VSIs.
7. Configure the basic Layer 2 forwarding function on Switch 1.
Data Preparation

Procedure
# Configure PE1.
<PE1> system-view
# Configure PE2.
<PE2> system-view
# Configure PE3.
<PE3> system-view
Step 3 Configure QinQ stacking+EthType, and bind VSIs to AC interfaces.

# Configure PE1.
<PE1> system-view
[PE1-GigabitEthernet1/0/1.1] qinq stacking vid 10 eth-type pppoe
[PE1-GigabitEthernet1/0/1.1] qinq stacking vid 20 eth-type pppoe
[PE1-GigabitEthernet1/0/1.2] qinq stacking vid 10 default
[PE1-GigabitEthernet1/0/1.2] qinq stacking vid 20 default
# Configure PE2.
<PE2> system-view


# Configure PE3.
<PE3> system-view
Step 4 Configure the Layer 2 forwarding function on Switch 1.

The detailed configurations are not mentioned here. For detailed configuration of the switch,
refer to the related configuration guide of the switch.
NOTE
Switch 1 sends packets tagged with different VLAN IDs and EthTypes to PE1.

Total QinQ Num: 2
Total QinQ Num: 2
state.
***VSI Name : ldp1

VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :


VSI State : up
VSI ID : 1
VC Label : 30720
Peer Type : dynamic
Session : up
CKey : 2
NKey : 1
StpEnable : 0
PwIndex : 0

State : up
Last Up Time : 2009/09/02 12:22:04
**PW Information:

PW State : up
PW Type : label
Ckey : 0x2
Nkey : 0x1
Tnl Type : LSP
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2009/09/02 12:22:40
Run the display interface vlan command, and you can view all the sub-interfaces with a
specified VLAN ID on the main interface.
-----------------------------------------------------------
GE1/0/1.2 default
-----------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
vsi ldp1 static

pwsignal ldp
vsi-id 1
peer 2.2.2.9
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 3.3.3.9
#
mpls ldp
#
undo shutdown
#
qinq stacking vid 10 eth-type PPPOE
qinq stacking vid 20 eth-type PPPOE
l2 binding vsi ldp1
#
qinq stacking vid 10 default
qinq stacking vid 20 default
l2 binding vsi ldp2
#
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 20.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
network 1.1.1.9 0.0.0.3
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#


l2 binding vsi ldp1
#
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return

#
sysname PE3
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#
l2 binding vsi ldp2
#
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 20.1.1.0 0.0.0.3
#
return

#
sysname CE1
#
undo shutdown
ip address 192.1.1.1 255.255.255.0
#
return


#
sysname CE2
#
undo shutdown
ip address 192.1.1.4 255.255.255.0
#
return
5.14.32 Example for Configuring Stacking Sub-interface+DSCP for

L2VPN Access
In this networking, PE1 receives tagged packets with different DSCP values; QinQ stacking
+DSCP is configured on the sub-interface at the AC side of PE1 so that an outer VLAN tag of
the ISP network is added to packets on the sub-interface; the sub-interface is bound to different
VSIs for L2VPN access. Packets are transmitted through different VSIs based on the DSCP
values of the packets. The following takes the scenario where a CSG accesses IP services as an
example.
DSCP values to PE1. It is required that QinQ stacking sub-interfaces be configured on PEs to
access the L2VPN and differentiated service transmission be implemented. In such a scenario,
you can deploy QinQ stacking+DSCP on the sub-interfaces at the AC side of PEs so that PEs
can differentiate services based on the DSCP values and hence different services can be
transmitted through different PWs.
NOTE
The DSCP is carried in each IP packet. For correct deployment of the Stacking Sub-interface+DSCP policy,
you need to ensure that the CSG accesses only IP services.

Figure 5-38 Networking diagram of QinQ stacking sub-interface+DSCP-based L2VPN access
VLAN 10 Loopback1
2.2.2.9/32
CE1 PE2
GE1/0/1.1
GE1/0/1
192.1.1.1/24 GE1/0/2 Database
=3
10.1.1.1/30
cp
ds
GE1/0/2 GE1/0/1.1 GE1/0/2
GE1/0/1 GE1/0/1.2 10.1.1.2/30
CSG
QinQ GE1/0/3
GE1/0/3 Stacking PE1 20.1.1.2/30
GE1/0/1 Loopback1
ds
192.1.1.4/24 1.1.1.9/32 GE1/0/2
cp
Internet
20.1.1.1/30
=2
GE1/0/1.1
CE2
PE3
VLAN 20 Loopback1
3.3.3.9/32
VLAN PW VLAN
NOTE

to VSIs.
7. Configure the basic Layer 2 forwarding function on Switch 1.
Data Preparation

Procedure
# Configure PE1.
<PE1> system-view
# Configure PE2.
<PE2> system-view
# Configure PE3.
<PE3> system-view
Step 3 Configure QinQ stacking+DSCP, and bind VSIs to AC interfaces.

# Configure PE1.
<PE1> system-view
[PE1-GigabitEthernet1/0/1.1] qinq stacking vid 10 dscp 3
# Configure PE2.
<PE2> system-view


# Configure PE3.
<PE3> system-view

following:
Total QinQ Num: 2
Total QinQ Num: 2
state.
***VSI Name : ldp1

VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :


VSI State : up
VSI ID : 1
VC Label : 30720
Peer Type : dynamic
Session : up
CKey : 2
NKey : 1
StpEnable : 0
PwIndex : 0

State : up
Last Up Time : 2009/09/02 12:22:04
**PW Information:

PW State : up
PW Type : label
Ckey : 0x2
Nkey : 0x1
Tnl Type : LSP
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2009/09/02 12:22:40
specified VLAN ID on a specified interface.
-----------------------------------------------------------
GE1/0/1.1 dscp 3
GE1/0/1.2 dscp 2
-----------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
vsi ldp1 static

pwsignal ldp
vsi-id 1
peer 2.2.2.9
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 3.3.3.9
#
mpls ldp
#
undo shutdown
#
qinq stacking vid 10 dscp 3
l2 binding vsi ldp1
#
l2 binding vsi ldp2
#
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 20.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
network 1.1.1.9 0.0.0.3
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#


l2 binding vsi ldp1
#
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return

#
sysname PE3
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
vsi ldp2 static
pwsignal ldp
vsi-id 2
peer 1.1.1.9
#
mpls ldp
#
undo shutdown
#
l2 binding vsi ldp2
#
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0
network 20.1.1.0 0.0.0.3
#
return

#
sysname CE1
#
undo shutdown
ip address 192.1.1.1 255.255.255.0
#
return


#
sysname CE2
#
undo shutdown
ip address 192.1.1.4 255.255.255.0
#
return

In this networking, a sub-interface for Dot1q VLAN tag termination and VLAN+802.1p are
configured on the interface at the AC side of a PE; the sub-interface for Dot1q VLAN tag
termination is bound to different VPN instances. Packets are transmitted through different VPN
instances based on the 802.1p priorities of the packets. The following takes the scenario where
a CSG accesses IP services as an example.
As shown in Figure 5-39, CSG sends packets tagged with different VLAN IDs and different
802.1p priorities to PE1. It is required that sub-interfaces for Dot1q VLAN tag termination be
configured on PEs to access the L3VPN and differentiated service transmission be implemented.
In such a scenario, you can deploy VLAN+802.1p on the sub-interfaces at the AC side of PEs
so that PEs can differentiate services based on the 802.1p priorities and hence different services
can be transmitted through different VPN instances.

Figure 5-39 Networking diagram of VLAN+802.1p-based L3VPN access
AS65410
VLAN 10 Loopback1
2.2.2.9/32
GE1/0/1.1 CE3
CE1 PE2
GE1/0/1.2
GE1/0/1
GE1/0/2
=3
GE1/0/1 Database
p
2.1
AS65420
80
GE1/0/2 PE1 GE1/0/2
GE1/0/1 Loopback1
CSG
GE1/0/1.1 1.1.1.9/32
GE1/0/1.2 GE1/0/3
GE1/0/3
80 Internet
GE1/0/1 2.1
p=2 GE1/0/2 AS65421
GE1/0/1
CE2 GE1/0/1.1
PE3 GE1/0/1.2 CE4
VLAN 20 Loopback1
3.3.3.9/32
AS65411 L3VPN
AS100
Device Interface and IP Address Device Interface and IP Address
CE1 GE1/0/1: 100.1.1.2/24 CE2 GE1/0/1: 200.1.1.2/24
PE1 GE1/0/1: -- PE2 GE1/0/1: --
GE1/0/1.1: 100.1.1.1/30 GE1/0/1.1: 100.2.1.1/30
GE1/0/1.2: 200.1.1.1/30 GE1/0/2: 10.1.1.1/30
GE1/0/2: 10.1.1.2/30 Loopback1: 2.2.2.9/32
GE1/0/3: 20.1.1.2/30 PE3 GE1/0/1: --
Loopback1: 1.1.1.9/32 GE1/0/1.1: 200.2.1.1/30
CE3 GE1/0/1: 100.2.1.1/24 GE1/0/2: 20.1.1.1/30
CE4 GE1/0/1: 200.2.1.1/24 Loopback1: 3.3.3.9/32

2. Configure basic MPLS functions and MPLS LDP, and set up MPLS LSPs on the backbone
network.
3. Set up LSPs between PEs.
4. Create VPN instances on PEs and bind AC interfaces to the VPN instances.
Data Preparation
Procedure
Step 1 Configure the IP addresses of interfaces on CEs and PEs as described in Figure 5-39. The
Step 2 Configure an IGP on the MPLS backbone network. In this example, OSPF is adopted as an IGP.
The detailed configurations are not mentioned here. You can see the configuration files in this
through OSPF to Loopback 1 of each other. PE1 and PE2, and PE1 and PE3 can ping through
each other.

2.2.2.9/32 OSPF 10 1 D 10.1.1.1
3.3.3.9/32 OSPF 10 1 D 20.1.1.1
10.1.1.0/30 Direct 0 0 D 10.1.1.2
20.1.1.0/30 Direct 0 0 D 20.1.1.2
<PE1> ping 2.2.2.9



0.00% packet loss
Step 3 Enable basic MPLS functions and LDP on the MPLS backbone network.
After the preceding configurations, MPLS LSPs are successfully created, and LDP sessions are
set up between PE1 and PE2 and between PE1 and PE3. Run the display mpls ldp session
command, and you can view that the Status field is displayed as Operational.

------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Step 4 Configure VPN instances.

# Configure PE1.
<PE1> system-view
# Configure PE2.
<PE2> system-view
# Configure PE3.
<PE3> system-view
Step 5 Configure the interface mode on PE1 to user termination.

# Configure PE1.
# Configure PE2.


# Configure PE3.
Step 6 Configure VLAN+802.1p, and bind sub-interfaces for Dot1q VLAN tag termination to the VPN
instances.
# Configure PE1.
[PE1-GigabitEthernet1/0/1.1] dot1q terminatio vid 10 8021p 3
# Configure PE2.
# Configure PE3.

Create date : 2009/09/02 10:35:42


Log Interval : 5

Create date : 2009/09/02 10:36:03
Log Interval : 5

following:
NOTE
Step 8 Set up EBGP peer relationships between the PEs and CEs to import VPN routes.
IP VPN Configuration" in the HUAWEI NetEngine80E/40E Router Configuration Guide -
VPN or the configuration files in this configuration example.
view that BGP peer relationships between PEs have been established and are in the
Established state.

2.2.2.9 4 100 6 11 0 00:04:53 Established 0

3.3.3.9 4 100 6 10 0 00:01:06 Established 0
to remote CEs.


------------------------------------------------------------------------------
100.1.1.0/24 Direct 0 0 D 100.1.1.1

------------------------------------------------------------------------------
200.1.1.0/24 Direct 0 0 D 200.1.1.1

the configured sub-interfaces for Dot1q VLAN tag termination. You can also view that the sub-
interfaces are bound to the L3VPN.
L3VPN bound
Total QinQ Num: 2
L3VPN bound
Total QinQ Num: 2
-----------------------------------------------------------
GE1/0/1.2 8021p 2
GE1/0/1.1 8021p 3
-----------------------------------------------------------
----End
Configuration Files

#
sysname PE1
#
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
mpls ldp
#
undo shutdown
#
ip address 100.1.1.1 255.255.255.0
#
ip address 200.1.1.1 255.255.255.0
#
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 20.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 2.2.2.9 enable
peer 3.3.3.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 2.2.2.9 enable
peer 3.3.3.9 enable

#
import-route direct
#
import-route direct
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
#
return
#
sysname PE2
#
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
mpls ldp
#
undo shutdown
#
ip address 100.2.1.1 255.255.255.0
#
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
import-route direct
#

ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return
#
sysname PE3
#
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
mpls ldp
#
undo shutdown
#
ip address 200.2.1.1 255.255.255.0
#
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
import-route direct
#
ospf 1
area 0.0.0.0
network 20.1.1.0 0.0.0.3
network 3.3.3.9 0.0.0.0
#
return
#
sysname CE1

#
undo shutdown
ip address 100.1.1.2 255.255.255.0
bgp 65410
#
ipv4-family unicast
import-route direct
#
return

#
sysname CE2
#
undo shutdown
ip address 200.1.1.2 255.255.255.0
bgp 65411
#
ipv4-family unicast
import-route direct
#
return

#
sysname CE3
#
undo shutdown
ip address 100.2.1.2 255.255.255.0
bgp 65420
#
ipv4-family unicast
import-route direct
#
return

#
sysname CE4
#
undo shutdown
ip address 200.2.1.2 255.255.255.0
bgp 65421
#
ipv4-family unicast
import-route direct
#
return


In this networking, PE1 receives tagged packets with different DSCP values; a sub-interface for
Dot1q VLAN tag termination and VLAN+DSCP are configured on the interface at the AC side
of PE1; the sub-interface for Dot1q VLAN tag termination is bound to different VPN instances.
Packets are transmitted through different VPN instances based on the DSCP values of the
packets. The following takes the scenario where a CSG accesses IP services as an example.
DSCP values to PE1. It is required that sub-interfaces for Dot1q VLAN tag termination be
configured on PEs to access the L3VPN and differentiated service transmission be implemented.
In such a scenario, you can deploy VLAN+DSCP on the sub-interfaces at the AC side of PEs
so that PEs can differentiate services based on the DSCP values and hence different services can
be transmitted through different VPN instances.
NOTE

Figure 5-40 Networking diagram of VLAN+DSCP-based L3VPN access
AS65410
VLAN 10 Loopback1
2.2.2.9/32
GE1/0/1.1 CE3
CE1 PE2
GE1/0/1.2
GE1/0/1
GE1/0/2 Database
=3
GE1/0/1
CP
AS65420
DS
GE1/0/2 GE1/0/1.1 PE1 GE1/0/2
GE1/0/1 GE1/0/1.2 Loopback1
CSG
1.1.1.9/32
GE1/0/3 GE1/0/3
DS
GE1/0/1 Internet
CP
GE1/0/2 AS65421
=2 GE1/0/1
CE2 GE1/0/1.1
PE3 GE1/0/1.2 CE4
VLAN 20 Loopback1
3.3.3.9/32
AS65411 L3VPN
AS100
CE1 GE1/0/1: 100.1.1.2/24 CE2 GE1/0/1: 200.1.1.2/24
PE1 GE1/0/1: -- PE2 GE1/0/1: --
GE1/0/1.1: 100.1.1.1/30 GE1/0/1.1: 100.2.1.1/30
GE1/0/1.2: 200.1.1.1/30 GE1/0/2: 10.1.1.1/30
GE1/0/2: 10.1.1.2/30 Loopback1: 2.2.2.9/32
GE1/0/3: 20.1.1.2/30 PE3 GE1/0/1: --
Loopback1: 1.1.1.9/32 GE1/0/1.1: 200.2.1.1/30
CE3 GE1/0/1: 100.2.1.1/24 GE1/0/2: 20.1.1.1/30
CE4 GE1/0/1: 200.2.1.1/24 Loopback1: 3.3.3.9/32

2. Configure basic MPLS functions and MPLS LDP, and set up MPLS LSPs on the backbone
network.
3. Set up LSPs between PEs.
4. Create VPN instances on PEs and bind AC interfaces to the VPN instances.
Data Preparation
Procedure
Step 1 Configure the IP addresses of interfaces on CEs and PEs as described in Figure 5-40. The
Step 2 Configure an IGP on the MPLS backbone network. In this example, OSPF is adopted as an IGP.
through OSPF to Loopback 1 of each other. PE1 and PE2, and PE1 and PE3 can ping through
each other.

2.2.2.9/32 OSPF 10 1 D 10.1.1.1
3.3.3.9/32 OSPF 10 1 D 20.1.1.1
10.1.1.0/30 Direct 0 0 D 10.1.1.2
20.1.1.0/30 Direct 0 0 D 20.1.1.2

<PE1> ping 2.2.2.9



0.00% packet loss
Step 3 Enable basic MPLS functions and LDP on the MPLS backbone network.
After the preceding configurations, MPLS LSPs are successfully created, and LDP sessions are
set up between PE1 and PE2 and between PE1 and PE3. Run the display mpls ldp session
command, and you can view that the Status field is displayed as Operational.

------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Step 4 Configure VPN instances.

# Configure PE1.
<PE1> system-view
# Configure PE2.
<PE2> system-view
# Configure PE3.
<PE3> system-view

# Configure PE1.

# Configure PE2.
# Configure PE3.
Step 6 Configure VLAN+DSCP, and bind sub-interfaces for Dot1q VLAN tag termination to the VPN
instances.
# Configure PE1.
# Configure PE2.
# Configure PE3.

Create date : 2009/09/02 10:35:42


Log Interval : 5

Create date : 2009/09/02 10:36:03
Log Interval : 5
following:

ATM in the case the CSG accesses non-IP services.
Step 8 Set up the EBGP peer relationships between the PEs and CEs to import VPN routes.
state.


2.2.2.9 4 100 6 11 0 00:04:53 Established 0

3.3.3.9 4 100 6 10 0 00:01:06 Established 0
to remote CEs.


------------------------------------------------------------------------------
100.1.1.0/24 Direct 0 0 D 100.1.1.1

------------------------------------------------------------------------------
200.1.1.0/24 Direct 0 0 D 200.1.1.1

the sub-interfaces for Dot1q VLAN tag termination. You can also find that the sub-interfaces
are bound to the L3VPN.
L3VPN bound
Total QinQ Num: 2
L3VPN bound
Total QinQ Num: 2
-----------------------------------------------------------
GE1/0/1.2 dscp 2
GE1/0/1.1 dscp 3
-----------------------------------------------------------
----End
Configuration Files

#
sysname PE1
#
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
mpls ldp
#
undo shutdown
#
ip address 100.1.1.1 255.255.255.0
#
ip address 200.1.1.1 255.255.255.0
#
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 20.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 2.2.2.9 enable
peer 3.3.3.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 2.2.2.9 enable
peer 3.3.3.9 enable

#
import-route direct
#
import-route direct
#
ospf 1
area 0.0.0.0
network 1.1.1.9 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
#
return
#
sysname PE2
#
#
mpls lsr-id 2.2.2.9
mpls
#
mpls l2vpn
#
mpls ldp
#
undo shutdown
#
ip address 100.2.1.1 255.255.255.0
#
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
import-route direct
#

ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return
#
sysname PE3
#
#
mpls lsr-id 3.3.3.9
mpls
#
mpls l2vpn
#
mpls ldp
#
undo shutdown
#
ip address 200.2.1.1 255.255.255.0
#
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
import-route direct
#
ospf 1
area 0.0.0.0
network 20.1.1.0 0.0.0.3
network 3.3.3.9 0.0.0.0
#
return
#
sysname CE1

#
undo shutdown
ip address 100.1.1.2 255.255.255.0
bgp 65410
#
ipv4-family unicast
import-route direct
#
return

#
sysname CE2
#
undo shutdown
ip address 200.1.1.2 255.255.255.0
bgp 65411
#
ipv4-family unicast
import-route direct
#
return

#
sysname CE3
#
undo shutdown
ip address 100.2.1.2 255.255.255.0
bgp 65420
#
ipv4-family unicast
import-route direct
#
return

#
sysname CE4
#
undo shutdown
ip address 200.2.1.2 255.255.255.0
bgp 65421
#
ipv4-family unicast
import-route direct
#
return

Configuration Guide - LAN Access and MAN Access 6 STP/RSTP Configuration
6 STP/RSTP Configuration
About This Chapter
The Spanning Tree Protocol (STP) trims a ring network into a loop-free tree network. It prevents
replication and circular propagation of packets, provides multiple redundant paths for Virtual
LAN (VLAN) data traffic, and enables load balancing. The Rapid Spanning Tree Protocol
(RSTP) develops rapid convergence and introduces the edge port and its protection function
based on STP.
6.1 STP/RSTP Overview

STP is a management protocol on the data link layer. It is used to block redundant links on the
Layer 2 network and trim a network into a loop-free tree. RSTP is a refinement of STP and
introduces rapid convergence of the network topology.
6.2 Configuring Basic STP/RSTP Functions
STP/RSTP is used to block redundant links on the Layer 2 network and trim a network into a
loop-free tree topology.
6.3 Configuring STP/RSTP Parameters on an Interface
A feedback mechanism is provided to confirm topology convergence. Thus, rapid convergence
is implemented for RSTP.
6.4 Configuring RSTP Protection Functions
RSTP protection functions are as follows, and you can configure one or more functions as
required.
6.5 Configuring STP/RSTP Interoperability Between Huawei Devices and Non-Huawei Devices
To supports STP/RSTP interoperability between Huawei devices and non-Huawei devices,
proper parameters are required on Huawei devices running STP/RSTP to ensure nonstop
communication.
6.6 Maintaining STP/RSTP
STP/RSTP maintenance includes resetting STP/RSTP statistics.
This section shows typical usage scenarios of STP/RSTP by describing networking
files.

6.1 STP/RSTP Overview

STP is a management protocol on the data link layer. It is used to block redundant links on the
Layer 2 network and trim a network into a loop-free tree. RSTP is a refinement of STP and
introduces rapid convergence of the network topology.
6.1.1 STP/RSTP Overview

Introduction
On a complex network, loops are inevitable. With the requirement for network redundancy
backup, network designers tend to deploy multiple physical links between two devices, one of
which is the master and the others are the backup. Loops are likely or bound to occur in such a
situation.
Loops will cause broadcast storms, thereby exhausting network resources and paralyzing the
network. Loops also cause flapping of MAC address tables and thus damages MAC address
entries.
The devices running STP discover loops on the network by exchanging information with each
other and trim the ring topology into a loop-free tree topology by blocking a certain interface.
In this manner, replication and circular propagation of packets are prevented on the network. In
addition, it is prevented that the processing performance of devices is degraded when
continuously processing repeated packets.
STP, however, converges the network topology slowly. In 2001, the IEEE published document
802.1w to introduce an evolution of the Spanning Tree Protocol: Rapid Spanning Tree Protocol
(RSTP). RSTP is developed based on STP but outperforms STP.
Concepts
l Root bridge
A tree topology must have a root. Therefore, the root bridge is introduced by STP/RSTP.
There is only one root bridge on the entire STP/RSTP-capable network. The root bridge is
the logical center but is unnecessarily the physical center of the entire network. The root
bridge may be served by another switching device along with the network topology change.
l ID
There are Bridge IDs (BIDs) and port IDs (PIDs).
– BID
IEEE 802.1D defines that a BID is composed of a 2-bit bridge priority and a bridge
MAC address. That is, BID (8 bits) = Bridge priority (2 bits) + Bridge MAC address (6
bits).
On the STP-capable network, the device with the smallest BID is selected as the root
bridge. The bridge priority that is allowed to be configured on a Huawei device ranges
from 0 to 61440. By default, the bridge priority is 32768.
– PID

A 16-bit PID is composed of a 4-bit port priority and a 12-bit port number.
The PID is used when the designated port needs to be selected. That is, when the root
path costs and the sender BIDs of two ports are the same, the port with a smaller PID
is selected as the designated port. As shown in Figure 6-1, the root path costs and sender
BIDs of port A and port B on S2 are the same. Port A has a smaller PID, and is thus
selected as the designated port on the local segment. The port priority that can be
configured on a Huawei device ranges from 0 to 240, with the step 16. That is, the port
priority can be 0, 16, or 32. By default, the port priority is 128.
l Path cost
A path cost is port-specific, which is used by STP/RSTP as a reference to select a link.
STP/RSTP calculates the path cost to select the robust link and blocks redundant links to
trim the network into a loop-free tree topology.
On an STP/RSTP-capable network, the accumulative cost of the path from a certain port
to the root bridge is the sum of the costs of the segment paths into which the path is separated
by the ports on the transit bridges.
l Port roles
– STP-capable port
– Root port
The root port is the port that is nearest to the root bridge. The root port is determined
based on the path cost. Among all the ports where STP is enabled on the network
bridge, the port with the smallest root path cost is the root port. There is only one
root port on an STP-capable device, but there is no root port on the root bridge.
– Designated Port
The designated port on a switching device forwards bridge protocol data units
(BPDUs) to the downstream switching device. All ports on the root bridge are
designated ports. A designated port is selected on each network segment. The device
where the designated port resides is called the designated bridge on the network
segment.
– RSTP-capable port
Compared with STP, RSTP has two additional types of ports, namely, the alternate port
and backup port. More port roles are defined to simplify the knowledge and deployment
of STP.

Figure 6-1 Diagram of port roles

S1
Root bridge
B A
S2 S3
A A a
S1
Root bridge
B A
S2 S3
A a
B A
b
Root port
Designated port
Alternate port
Backup port
As shown in Figure 6-1, RSTP defines four port roles: root port, designated port,
alternate port, and backup port.
The functions of the root port and designated port are the same as those defined in STP.
The description of the alternate port and backup port is as follows:
– From the perspective of configuration BPDU transmission:
– The alternate port is blocked after learning the configuration BPDUs sent by
other bridges.
– The backup port is blocked after learning the configuration BPDUs sent by itself.
– From the perspective of user traffic:
– The alternate port backs up the root port and provides an alternate path from the
designated bridge to the root bridge.
– The backup port backs up the designated port and provides an alternate path from
the root node to the leaf node.
After all ports are assigned roles, topology convergence is completed.

l Port status
– STP port state
Table 6-1 shows the port status of an STP-capable port.
Table 6-1 STP port state

Port state Purpose Description
Forwardin The port in the Forwarding state Only the root port and
g forwards not only user traffic but also designated port can enter the
BPDUs. Forwarding state.
Learning When a port is in the Learning state, a This is a transition state,

device creates a MAC address table which is designed to prevent
based on the received user traffic but temporary loops.
does not forward user traffic.
Listening When a port is in the Listening state, the This is a transition state.
root bridge, root port, and designated
port are to be selected.
Blocking The port in the Blocking state receives This is the final state of a
and forwards only BPDUs but does not blocked port.
forward user traffic.
Disabled The port in the Disabled state forwards The port is Down.
neither BPDUs nor user traffic.
– RSTP port state

Table 6-2 shows the port status of an RSTP-capable port.
Table 6-2 RSTP port state

Port state Description
Forwarding A port in the Forwarding state can send and receive BPDUs as
well as forward user traffic.
Learning This is a transition state. A port in the Learning state learns

MAC addresses from user traffic to construct a MAC address
table.
In the Learning state, the port can send and receive BPDUs, but
cannot forward user traffic.
Discarding A port in the Discarding state can only receive BPDUs.

CAUTION
A Huawei datacom device is in MSTP mode by default. After a device experiences the
transition from the MSTP mode to the STP mode, an STP-capable port supports the same
port states as those supported by an MSTP-capable port, including the Forwarding,
Learning, and Discarding states. For details, see Table 6-2.
l Three timers
– Hello Timer
Sets the interval at which BPDUs are sent.
– Forward Delay Timer
Sets the time spent in the Listening and Learning states.
– Max Age
Sets the maximum lifetime of a BPDU on the network. When the Max Age time expires,
the connection to the root bridge fails.
Comparison between STP, RSTP, and MSTP

Table 6-3 shows the comparison between STP, RSTP, and MSTP.
Table 6-3 Comparison between STP, RSTP, and MSTP

Spanning Characteristics Applicable Precautions
Tree Environment
Protocol
STP A loop-free tree is Irrespective of different NOTE

generated. Thus, broadcast users or services, all l If the current
storms are prevented and VLANs share one switching device
redundancy is spanning tree. supports STP and
RSTP, RSTP is
implemented.
recommended.
RSTP l A loop-free tree is l If the current
generated. Thus, switching device
supports STP or
broadcast storms are RSTP, and MSTP,
prevented and MSTP is
redundancy is recommended. See
implemented. MSTP
Configuration.
l A feedback mechanism
is provided to confirm
topology convergence.
Thus, rapid
convergence is
implemented.

Spanning Characteristics Applicable Precautions

Tree Environment
Protocol
MSTP l In an MSTP region, a User or service-specific

loop-free tree is load balancing is
generated. Thus, required. Traffic for
broadcast storms are different VLANs is
prevented and forwarded through
redundancy is different spanning
implemented. trees, which are
l A feedback mechanism independent of each
is provided to confirm other.
Thus, rapid
convergence is
implemented.
l MSTP implements
load balancing among
VLANs. Traffic in
different VLANs is
transmitted along
different paths.
6.1.2 STP/RSTP Features Supported by the NE80E/40E

Before configuring STP/RSTP, familiarize yourself with the concepts of basic STP/RSTP
functions, topology convergence, STP/RSTP protection, and STP/RSTP interoperability
between Huawei devices and non-Huawei devices. This will help you complete the configuration
task quickly and accurately.
loop-free tree topology. The basic configuration roadmap of STP/RSTP is as follows:
1. Select a switching device (functioning as a root bridge) from switching devices for each
spanning tree. You can configure the priorities of the switching devices to preferentially
select a root bridge.
2. In each spanning tree, calculate the shortest paths from the other switching devices to the
root bridge, and select a root port for each non-root switching device. You can configure
the cost of the path from a switching device to the root bridge to preferentially select a root
port.
3. In each spanning tree, select a designated port for each connection according to the bridge
ID, the cost of path and port IDs. If the devices have the same bridge ID and the cost of
path, You can configure the port priorities to preferentially select a designated port.
STP/RSTP also supports the following features to meet requirements of special applications and
extended functions:
l A feedback mechanism is provided to confirm topology convergence. Thus, rapid
convergence is implemented.
l RSTP provides the following protection functions, as listed in Table 6-4.

l Supports STP/RSTP interoperability between Huawei devices and non-Huawei devices.

Proper parameters are required on Huawei devices running STP/RSTP to ensure nonstop
communication.
Table 6-4 RSTP Protection Function

Protection Scenario Configuration Impact
Function
BPDU An edge port changes to be After BPDU protection is enabled on the

protection a non-edge port after switching device, the switching device
receiving a BPDU, which shuts down the edge port if the edge port
triggers spanning tree receives an RST BPDU, and notifies the
recalculation. If an attacker NMS of the shutdown event. The attributes
keeps sending bogus of the edge port are not changed.
BPDUs to a switching
device, network flapping
occurs.
TC Generally, after receiving TC protection is used to suppress TC-

protection TC BPDUs (packets for BPDUs. The number of times that TC-
advertising network BPDUs are processed by a switching
topology changes), a device within a given time period is
switching device needs to configurable. If the number of TC-BPDUs
delete MAC entries and that the switching device receives within a
ARP entries. Frequent given time exceeds the specified threshold,
deletion operations will the switching device handles TC-BPDUs
exhaust CPU resources. only for the specified number of times.
Excess TC-BPDUs are processed by the
switching device as a whole for once after
the timer (that is, the specified time period)
expires. This protects the switching device
from frequently deleting MAC entries and
ARP entries, thus avoiding over-burdened.
Root Due to incorrect If a designated port is enabled with the root

protection configurations or protection function, the role of the port
malicious attacks on the cannot be changed. Once a designated port
network, a root bridge may that is enabled with root protection
receive BPDUs with a receives RST BPDUs with a higher
higher priority. priority, the port enters the Discarding state
Consequently, the and does not forward packets. If the port
legitimate root bridge is no does not receive any RST BPDUs with a
longer able to serve as the higher priority before a period (generally
root bridge, and the two Forward Delay periods) expires, the
network topology is port automatically enters the Forwarding
illegitimately changed, state.
triggering spanning tree
recalculation. This may
transfer traffic from high-
speed links to low-speed
links, causing traffic
congestion.


Function
Loop A root port or an alternate After loop protection is configured, if the

protection port will age if link root port or alternate port does not receive
congestion or a one-way RST BPDUs from the upstream switching
link failure occurs. After device for a long time, the switching device
the root port ages, a notifies the NMS that the port enters the
switching device may re- Discarding state. The blocked port remains
select a root port in the Blocked state and no longer forwards
incorrectly and after the packets. This prevents loops on the
alternate port ages, the port network. The root port restores the
enters the Forwarding Forwarding state after receiving new
state. Loops may occur in BPDUs.
such a situation.
6.2 Configuring Basic STP/RSTP Functions

STP/RSTP is commonly configured on a switching device to trim a ring network to a loop-free

network. STP/RSTP configurations on the switching device involve STP/RSTP working mode
configuration. If you need to interfere in the spanning tree calculation, the following methods
are available:
l Setting a priority for a switching device: The lower the numerical value, the higher the
priority of the switching device and the more likely the switching device becomes a root
bridge; the higher the numerical value, the lower the priority of the switching device and
the less likely that the switching device becomes a root bridge.
l Setting a path cost for a port: With the same calculation method, the lower the numerical
value, the smaller the cost of the path from the port to the root bridge and the more likely
the port becomes a root port; the higher the numerical value, the larger the cost of the path
from the port to the root bridge and the less likely that the port becomes a root port.
l Setting a priority for a port: The lower the numerical value, the more likely the port becomes
a designated port; the higher the numerical value, the less likely that the port becomes a
designated port.

Before configuring basic STP/RSTP functions, familiarize yourself with the applicable
environment, complete the pre-configuration tasks, and obtain the required data. This will help
situation.

entries.
STP/RSTP can be deployed on a network to eliminate loops. If a loop is detected, STP/RSTP

blocks one port to eliminate the loop.
As shown in Figure 6-2, RouterA, RouterB, Switch C, and Switch D form a ring network, and
STP/RSTP is enabled on the ring network to eliminate loops.
Figure 6-2 Diagram of a ring network
Network
Root
Bridge
RouterA RouterB
SwitchC SwitchD
PC1 PC2
Blocked port
NOTE
If the current switching device supports STP and RSTP, RSTP is recommended.
Before configuring basic STP/RSTP functions, complete the following task:
l Connecting interfaces and setting physical parameters for the interfaces to ensure that the
physical status of the interfaces is Up
Data Preparation
To configure basic STP/RSTP functions, you need the following data.

No. Data
1 (Optional) Priority of a switching device
2 (Optional) Priority of a port
3 (Optional) Path cost of a port
6.2.2 Configuring the STP/RSTP Mode

Before configuring basic STP/RSTP functions, you need to configure the working mode of a
switching device to STP/RSTP. RSTP is compatible with STP.
Procedure
Step 1 Run:
system-view
Step 2 Run:
stp mode { stp | rstp }
The working mode of the switching device is configured as STP/RSTP.
By default, the working mode of a switching device is configured as MSTP. MSTP is compatible
with STP and RSTP.
On a ring network running only STP, the working mode of a switching device is configured as
STP; on a ring network running RSTP, the working mode of a switching device is configured
as RSTP. In other cases, the working mode of a switching device is configured as MSTP by
default.
----End
6.2.3 (Optional) Configuring Switching Device Priorities

The lower the numerical value is, the higher priority a switching device has and the more likely
the switching device will be selected as a root bridge.
Context
On an STP/RSTP-capable network, there is only one root bridge and it is the logic center of the
entire spanning tree. In root bridge selection, the switching device with high performance and
network hierarchy is generally selected as a root bridge; however, the priority of such a device
may be not that high. Thus setting a high priority for the switching device is necessary so that
the device can function as a root bridge.
Other devices with low performance and network hierarchy are not fit to be a root bridge.
Therefore, set low priorities for these devices.

Procedure
Step 1 Run:
system-view

Step 2 Run:
stp priority priority
The priority of a switching device is configured.

The default priority value of a switching device is 32768.
NOTE
l To configure a switching device as a primary root bridge, you can run the stp root primary command
directly. The priority value of this switching device is 0.
l To configure a switching device as a secondary root bridge, run the stp root secondary command. The
priority value of this switching device is 4096.
A switching device cannot act as a primary root bridge and a secondary root bridge at the same time.
l If you want to change the priority of a switching device after you run the stp root primary command
or the stp root secondary command to configure the switching device as a primary root bridge or a
secondary root bridge, disable the root bridge function or secondary root bridge function, and then run
the stp priority priority command to re-set a priority.
----End
6.2.4 (Optional) Setting the Path Cost for a Port

The STP/RSTP path cost determines root port selection. The port from which to the root port
costs the least is selected as the root port.
Context
A path cost is port-specific, which is used by STP/RSTP as a reference to select a link.
The range of the path cost value is determined by the calculation method. After the calculation
method is determined, you are recommended to set a relatively small path cost value for the port
at a high link rate.
Use the Huawei proprietory calculation method as an example. Different link rates correspond
to default path cost values of ports. For details, see Table 6-5.
Table 6-5 Mappings between link rates and path cost values
Link Rate Recommended Recommended Value Range
value Value Range
10 Mbit/s 2000 200-20000 1-200000
100 Mbit/s 200 20-2000 1-200000
1 Gbit/s 20 2-200 1-200000
10 Gbit/s 2 2-20 1-200000
Over 10 Gbit/s 1 1-2 1-200000

On a network where loops occur, you are recommended to set a relatively large path cost for the
port at a low link rate. STP/RSTP puts the port with the large path cost in the Blocking state and
blocks the link where this port resides.
Procedure
Step 1 Run:
system-view

Step 2 Run:
stp pathcost-standard { dot1d-1998 | dot1t | legacy }
A path cost calculation method is configured.

By default, the IEEE 802.1t standard method is used to calculate the default path cost.
All switching devices on a network must use the same calculation method for path costs.
Step 3 Run:

portswitch
The interface is switched to a Layer 2 interface.
NOTE
If the interface itself is a Layer 2 interface, this step can be skipped. Run the display this command in the
interface view. If "portswitch" is displayed in the command output, the interface is a Layer 2 interface.
Step 5 Run:
stp cost cost
A path cost is set for the port.
l When the Huawei proprietory calculation method is used, cost ranges from 1 to 200000.
l When the IEEE 802.1d standard method is used, cost ranges from 1 to 65535.
l When the IEEE 802.1t standard method is used, cost ranges from 1 to 200000000.
----End
6.2.5 (Optional) Configuring Port Priorities

The lower the numerical value, the more likely the port on a switching device becomes a
designated port; the higher the numerical value, the more likely the port is to be blocked.
Context
Whether a port on a switching device will be selected as a designated port is determined by its
priority. For details, see 6.1.1 STP/RSTP Overview.

If you expect to block a port on a switching device to eliminate loops, set the port priority value
to be larger than the default value when the devices have the same bridge ID and the cost of
path. This port will be blocked in designated port selection.
Procedure
Step 1 Run:
system-view

Step 2 Run:

portswitch
NOTE
Step 4 Run:
stp port priority priority
The port priority is configured.

The default priority value of a port on a switching device is 128.
----End
6.2.6 Enabling STP/RSTP

After STP/RSTP is enabled, spanning trees are calculated.
Context
After STP/RSTP is enabled on a ring network, STP/RSTP immediately calculates spanning trees
on the network. Configurations on the switching device, such as the switching device priority
and port priority, will affect spanning tree calculation. Any change of the configurations may
cause network flapping. Therefore, to ensure rapid and stable spanning tree calculation, perform
basic configurations on the switching device and its ports and enable STP/RSTP.
Procedure
Step 1 Run:
system-view

Step 2 Run:
stp enable
STP/RSTP is enabled on the switching device.

By default, the STP/RSTP function is enabled on a NE80E/40E.
----End

After basic STP/RSTP functions are configured, you can view the information such as the port
role and port status to check whether the spanning tree calculation is correctly performed.
Prerequisite
All configurations of basic STP/RSTP functions are complete.
Procedure
l Run the display stp [ interface interface-typeinterface-number ] [ brief ] command to view
spanning-tree status and statistics.
----End
Example
Run the display stp command, and you can view the spanning-tree working mode, root bridge,
priority of the root bridge, convergence mode, path cost calculation method, and path cost of a
root port. For example:
<HUAWEI> display stp
-------[CIST Global Info][Mode RSTP]-------
CIST Bridge :32768.00e0-4e1f-b200
Bridge Times :Hello 2s MaxAge 20s FwDly 15s MaxHop 20
CIST Root/ERPC :0 .00e0-e70a-4d00 / 20
CIST RegRoot/IRPC :32768.00e0-4e1f-b200 / 0
CIST RootPortId :128.1
BPDU-Protection :disabled
TC or TCN received :0
TC count per hello :0
STP Converge Mode :Normal
Time since last TC :0 days 0h:26m:16s
----[Port1(GigabitEthernet1/0/1)][FORWARDING]----
Port Protocol :enabled
Port Role :Root Port
Port Priority :128
Port Cost(Legacy) :Config=auto / Active=20
Desg. Bridge/Port :0.00e0-e70a-4d00 / 128.5
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 :RSTP
Port Protocol Type :Config=auto / Active=dot1s
BPDU Encapsulation :Config=stp / Active=stp
PortTimes :Hello 2s MaxAge 20s FwDly 15s RemHop 0
TC or TCN send :1
BPDU Sent :4
TCN: 0, Config: 0, RST: 4, MST: 0
BPDU Received :22
----[Port2(GigabitEthernet1/0/3)][DISCARDING]----
Port Role :Alternate Port
Port Priority :160
Desg. Bridge/Port :4096.00e0-6606-be00 / 128.1


Port Stp Mode :RSTP
TC or TCN send :1
BPDU Sent :2
BPDU Received :22
6.3 Configuring STP/RSTP Parameters on an Interface

A feedback mechanism is provided to confirm topology convergence. Thus, rapid convergence
is implemented for RSTP.
STP does not implement rapid convergence; however, STP parameters, such as the network
diameter, hello time, Max Age time, and Forward Delay time, may affect network convergence.
RSTP is a refinement of STP and implements rapid convergence. In addition to the preceding
parameters, such parameters as the type of the link where the port resides, rapid transition
mechanism, and maximum number of sent BPDUs port parameters also affect STP/RSTP
For the parameters of devices running STP/RSTP, see Table 6-6.
Table 6-6 Parameters affecting the STP/RSTP topology convergence

Paramete Parameter Commands Description
r Description
System network l stp bridge-diameter It is recommended that you

parameter diameter, timer diameter set the network diameter to
value (Hello l stp timer hello hello-time determine the timer value.
Time, Forward The switching device
Delay period, l stp timer forward-delay automatically calculates
Max Age time), forward-delay the Forward Delay period,
and timeout l stp timer max-age max- Hello time, and Max Age
period for age time based on the network
waiting for l stp timer-factor factor diameter. Then, you can
BPDUs from run the stp timer-factor
the upstream (3 factor command to set the
x hello time x timeout period for waiting
time factor) for BPDUs from the
upstream (3 x hello time x
time factor).


r Description
Port Link type of a l stp point-to-point { auto | A P2P link helps

parameter port force-false | force-true } implement the rapid
convergence.
l If the port works in full-
duplex mode, the link
where the port resides is
a P2P link.
l If the port works in
half-duplex mode, you
can forcibly switch the
link where the port
resides to a P2P link.
l In other cases, you can
enable the port to
automatically
determine whether to
connect to the P2P link.
Port transition l stp mcheck On a switching device

to the RSTP running RSTP, if an
mode interface is connected to a
device running STP, the
interface automatically
transitions to the STP
mode.
Enabling MCheck on the
interface is required When
the interface fail to
automatically transition to
the RSTP mode.
Maximum l stp transmit-limit packet- If the maximum number of

number of number BPDUs sent by the
BPDUs sent by interface within each Hello
the interface time is set properly, the rate
within each at which BPDUs are sent
Hello time can be restricted, which
prevents RSTP from
consuming too many
bandwidths when network
flapping occurs.


r Description
Edge ports l stp edged-port enable The ports connecting to

terminals do not participate
in STP/RSTP calculation.
If a port is configured as an
edge port, the port does not
participate in STP/RSTP
calculation.
After BPDU protection is
configured on a switching
device, an edge port is shut
down when receiving
BPDUs. The port can be
configured to
automatically go Up after a
specific delay.

Before configuring parameters affecting STP/RSTP rapid convergence, familiarize yourself
with the applicable environment, complete the pre-configuration tasks, and obtain the required
data. This will help you complete the configuration task quickly and accurately.
On some specific networks, RSTP parameters will affect the speed of network convergence.
Configuring proper RSTP parameters is required.
NOTE
The default configurations of the parameters described in this section help implement RSTP rapid
convergence. Therefore, the configuration process and all involved procedures described in this section
are optional. You can perform some of the configurations as required.
Before configuring STP/RSTP parameters, complete the following task:
l Configuring basic STP/RSTP functions
Data Preparation
To configure STP/RSTP parameters, you need the following data.
No. Data
1 Network diameter
2 Hello time, forwarding delay time, maximum aging time, and timeout period for
waiting for BPDUs from the upstream (3 x hello time x time factor)
3 Link type of a port

No. Data
4 Whether a port is enabled with rapid transition mechanism
5 Whether a port needs to transition to the RSTP mode
6 Maximum number of sent BPDUs
7 Whether a port needs to be configured as an edge port
8 Whether auto recovery needs to be configured for an edge port being shut down
9 Whether a port needs to clear statistics of the spanning tree
10 Whether an edge port needs to be configured as a BPDU filter
6.3.2 Setting System Parameters

STP/RSTP parameters that may affect network convergence include the network diameter, hello
time, and timeout period for waiting for BPDUs from the upstream (3 x hello time x time factor).
Therefore, STP/RSTP parameters need to be set properly to help implement rapid network
convergence.
Procedure
Step 1 Run:
system-view

Step 2 Run:
stp bridge-diameter diameter
The network diameter is configured.

By default, the network diameter is 7.
l RSTP uses a single spanning tree instance on the entire network, which cannot prevent the
performance from deteriorating when the network scale grows. Therefore, the network
diameter cannot be larger than 7.
l It is recommended that you run the stp bridge-diameter diameter command to set the
network diameter. Then, the switching device calculates the optimal Forward Delay period,
Hello time, and Max Age period based on the set network diameter.
Step 3 Run:
stp timer-factor factor
The timeout period for waiting for BPDUs from the upstream of a switching device is set.
By default, the timeout period of a switching device is 9 times as long as the Hello time.
Step 4 (Optional) If the current device is at the edge of a network, run both or either of the following
commands as needed:
l To configure all ports on the devices as edge ports, run:
stp edged-port default

By default, a port is a non-edge port.

After ports on a network edge device are configured as edge ports, the ports no longer
participate in spanning tree calculation. This speeds up network topology convergence and
improves network stability.
l To configure all ports on the devices as BPDU filter ports, run:
stp bpdu-filter default
By default, a port is a non-BPDU filter port.

After ports on a network edge device are configured as BPDU filter ports, the ports no longer
process or send BPDUs.
WARNING
After the stp bpdu-filter default and stp edged-port default commands are run in the system
view, all ports on the device no longer actively send BPDUs or negotiate with directly-connected
ports; instead, all the ports are in the Forwarding state. This may lead to a loop on the network,
causing broadcast storms. Exercise caution when running these commands.
Step 5 (Optional) To set the Forward Delay period, Hello time, and Max Age period, perform the
following operations:
l Run the stp timer forward-delay forward-delay command to set the Forward Delay period
for a switching device.
The default Forward Delay period of a switching device is 1500, in centiseconds.
l Run the stp timer hello hello-time command to set the Hello time for a switching device.
The default Hello time of a switching device is 200, in centiseconds.
l Run the stp timer max-age max-age command to set the Max Age period for a switching
device.
The default Max Age period of a switching device is 2000, in centiseconds.
NOTE
The values of the Hello time, Forward Delay period, and Max Age period must comply with the following
formulas. Otherwise, networking flapping occurs.
l 2 × (Forward Delay - 1.0 second) >= Max Age
l Max Age >= 2 × (Hello Time + 1.0 second)
----End
6.3.3 Setting Port Parameters

Port parameters that may affect RSTP topology convergence include the link type and maximum
number of sent BPDUs. Proper port parameters help RSTP to implement rapid topology
convergence.
Procedure
Step 1 Run:
system-view

Step 2 Run:

portswitch

NOTE

stp point-to-point { auto | force-false | force-true }
The link type is configured for a port.

By default, a port automatically determines whether to connect to a P2P link. The P2P link
supports rapid network convergence.
l If the Ethernet port works in full-duplex mode, the port is connected to a P2P link. In this
case, force-true can be configured to implement rapid network convergence.
l If the Ethernet port works in half-duplex mode, you can configure stp point-to-point force-
true to forcibly set the link type to P2P to implement rapid network convergence.
Step 5 Run:
stp mcheck
MCheck is enabled.
On a switching device running RSTP, if a port is connected to a device running STP, the port
automatically transitions to the STP interoperable mode.
Enabling MCheck on the port is required because the port may fail to automatically transition
to the RSTP mode in the following situations:
l The switching device running STP is shut down or moved.
l The switching device running STP transitions to the RSTP mode.
NOTE
If you run the stp mcheck command in the system view, the MCheck operation is performed on all the
interfaces.
Step 6 Run:
stp transmit-limit packet-number
The maximum number of BPDUs sent by a port within each Hello time is set.
By default, the maximum number of BPDUs that a port sends within each Hello time is 147.
stp edged-port enable
The port is configured as an edge port.

If a device port is connected to a terminal, you can run this command to configure the port as
an edge port.
By default, the port is a non-edge port.

If the current port has been configured as an edge port, the port is still be able to send BPDUs.
This may cause BPDUs to be sent to other networks, leading to network flapping. To prevent
this problem, run the stp bpdu-filter command to configure the edge port as a BPDU filter port
and disable the port from processing or sending BPDUs.
WARNING
After the stp bpdu-filter command is run on a port, the port no longer processes or sends BPDUs.
The port will not negotiate with the directly-connected port to establish an STP connection.
Therefore, exercise caution when running this command.
Step 8 Run:
quit
Return to the system view.
----End
Follow-up Procedure
When the topology of a spanning tree changes, the forwarding paths to associated VLANs are
changed. Then, ARP entries corresponding to those VLANs on the switching device need to be
updated. STP/RSTP processes ARP entries in either fast or normal mode.
l In fast mode, ARP entries to be updated are directly deleted.

l In normal mode, ARP entries to be updated are rapidly aged.
The remaining lifetime of ARP entries to be updated is set to 0. The switching device rapidly
processes these aged entries. If the number of ARP aging probe attempts is not set to 0,
ARP implements aging probe for these ARP entries.
In either fast or normal mode, MAC entries are directly deleted.
You can run the stp converge { fast | normal } command in the system view to configure the
STP/RSTP convergence mode.
By default, the STP/RSTP convergence is configured as normal.
NOTE
The normal mode is recommended. If the fast mode is adopted, ARP entries will be frequently deleted,
causing the CPU usage on the MPU or LPU to reach 100%. As a result, network flapping frequently occurs.

You can verify that the configurations take effect after configuring STP/RSTP parameters that
affect the topology convergence.
Prerequisite
The parameters that affect the topology convergence have been configured.

Procedure
l Run the display stp [ interface interface-type interface-number ] [ brief ] command to
view spanning-tree status and statistics.
----End
Example
Run the display stp command to view the Hello time, Max Age period, Forward Delay period,
maximum number of sent BPDUs within each Hello time, and the status whether a port is
connected to a P2P link. For example:
<HUAWEI> display stp interface gigabitethernet 1/0/1
Port Priority :128
Port Stp Mode :RSTP
TC or TCN send :1
BPDU Sent :4
BPDU Received :22
6.4 Configuring RSTP Protection Functions

RSTP protection functions are as follows, and you can configure one or more functions as
required.

Before configuring RSTP protection functions, familiarize yourself with the applicable
RSTP provides the following protection functions, as listed in Table 6-7.

Table 6-7 RSTP Protection Function

Function
BPDU An edge port changes to be a After BPDU protection is enabled on the

protection non-edge port after switching device, the switching device shuts
receiving a BPDU, which down the edge port if the edge port receives
triggers spanning tree an RST BPDU, and notifies the NMS of the
recalculation. If an attacker shutdown event. The attributes of the edge
keeps sending bogus BPDUs port are not changed.
to a switching device,
network flapping occurs.
TC protection Generally, after receiving TC protection is used to suppress TC-BPDUs.

TC BPDUs (packets for The number of times that TC-BPDUs are
advertising network processed by a switching device within a
topology changes), a given time period is configurable. If the
switching device needs to number of TC-BPDUs that the switching
delete MAC entries and ARP device receives within a given time exceeds
entries. Frequent deletion the specified threshold, the switching device
operations will exhaust CPU handles TC-BPDUs only for the specified
resources. number of times. Excess TC-BPDUs are
processed by the switching device as a whole
for once after the timer (that is, the specified
time period) expires. This protects the
switching device from frequently deleting
MAC entries and ARP entries, thus avoiding
over-burdened.
Root Due to incorrect If a designated port is enabled with the root

protection configurations or malicious protection function, the role of the port cannot
attacks on the network, a be changed. Once a designated port that is
root bridge may receive enabled with root protection receives RST
BPDUs with a higher BPDUs with a higher priority, the port enters
priority. Consequently, the the Discarding state and does not forward
legitimate root bridge is no packets. If the port does not receive any RST
longer able to serve as the BPDUs with a higher priority before a period
root bridge, and the network (generally two Forward Delay periods)
topology is illegitimately expires, the port automatically enters the
changed, triggering Forwarding state.
spanning tree recalculation.
This may transfer traffic
from high-speed links to
low-speed links, causing
traffic congestion.


Function
Loop A root port or an alternate After loop protection is configured, if the root
protection port will age if link port or alternate port does not receive RST
congestion or a one-way link BPDUs from the upstream switching device
failure occurs. After the root for a long time, the switching device notifies
port ages, a switching device the NMS that the port enters the Discarding
may re-select a root port state. The blocked port remains in the
incorrectly and after the Blocked state and no longer forwards packets.
alternate port ages, the port This prevents loops on the network. The root
enters the Forwarding state. port restores the Forwarding state after
Loops may occur in such a receiving new BPDUs.
situation.
Before configuring basic RSTP functions, complete the following task:
l Configuring basic RSTP functions
NOTE
Configuring an edge port on the switching device before configuring BPDU protection.
Data Preparation
To configure basic RSTP functions, you need the following data.
No. Data
1 Number of the port on which root protection is to be enabled
2 Number of the port on which loop protection is to be enabled
6.4.2 Configuring BPDU Protection on a Switching Device

After BPDU protection is enabled on a switching device, the switching device shuts down an
edge port if the edge port receives a BPDU, and notifies the NMS of the shutdown event.
Context
Edge ports are directly connected to user terminals and normally, the edge ports will not receive
BPDUs. Some attackers may send pseudo BPDUs to attach the switching device. If the edge
ports receive the BPDUs, the switching device automatically configures the edge ports as non-
edge ports and triggers new spanning tree calculation. Network flapping then occurs. BPDU
protection can be used to protect switching devices against malicious attacks.
NOTE
Do as follows on a switching device having an edge port:

Procedure
Step 1 Run:
system-view
Step 2 Run:
stp bpdu-protection
BPDU protection is enabled on the switching device.
By default, BPDU protection is not enabled on the switching device.
----End
6.4.3 Configuring TC Protection on a Switching Device

After TC protection is enabled, you can set the number of times for a switching device to process
TC BPDUs within a given time. TC protection avoids frequent deletion of MAC address entries
and ARP entries, thereby protecting switching devices.
Context
An attacker may send pseudo TC BPDUs to attack switching devices. Switching devices receive
a large number of TC BPDUs in a short time and delete entries frequently, which burdens system
processing and degrades network stability.
TC protection is used to suppress TC BPDUs. The number of times that TC BPDUs are processed
by a switching device within a given time period is configurable. If the number of TC BPDUs
that the switching device receives within a given time exceeds the specified threshold, the
switching device handles TC BPDUs only for the specified number of times. Excess TC-BPDUs
are processed by the switching device as a whole for once after the specified time period expires.
This protects the switching device from frequently deleting MAC entries and ARP entries, thus
avoiding overburden.
Procedure
Step 1 Run:
system-view
Step 2 Run:
stp tc-protection
TC protection is enabled for a switching device.
By default, TC protection is not enabled on the switching device.
Step 3 Run:
stp tc-protection threshold threshold
The threshold of the number of times the switching device handles the received TC BPDUs and
updates forwarding entries within a given time is set.

NOTE
The value of the given time is consistent with the RSTP Hello time set by using the stp timer hello hello-
time command.
----End
6.4.4 Configuring Root Protection on a Port

The root protection function on a switching device protects a root bridge by preserving the role
of a designated port.
Context
Due to incorrect configurations or malicious attacks on the network, a root bridge may receive
BPDUs with a higher priority. Consequently, the legitimate root bridge is no longer able to serve
as the root bridge, and the network topology is incorrectly changed, triggering spanning tree
recalculation. This also may cause the traffic that should be transmitted over high-speed links
to be transmitted over low-speed links, leading to network congestion. The root protection
function on a switching device is used to protect the root bridge by preserving the role of the
designated port.
NOTE
Root protection is configured on a designated port. Root protection takes effect only on a designated port.
Do as follows on the root bridge.
Procedure
Step 1 Run:
system-view
Step 2 Run:

portswitch
NOTE
Step 4 Run:
stp root-protection
Root protection is configured on the switching device.
By default, root protection is disabled.
----End

6.4.5 Configuring Loop Protection on a Port

The loop protection function suppresses the loops caused by link congestion.
Context
On a network running RSTP, a switching device maintains the root port status and status of
blocked ports by receiving BPDUs from an upstream switching device. If the switching device
cannot receive BPDUs from the upstream because of link congestion or unidirectional-link
failure, the switching device re-selects a root port. The original root port becomes a designated
port and the original blocked ports change to the Forwarding state. This may cause network
loops. To address such a problem, configure loop protection.
After loop protection is configured, if the root port or alternate port does not receive BPDUs
from the upstream switching device, the root port is blocked and the switching device notifies
the NMS that the port enters the Discarding state. The blocked port remains in the Blocked state
and no longer forwards packets. This prevents loops on the network. The root port restores the
Forwarding state after receiving new BPDUs.
NOTE
An alternate port is a backup port of a root port. If a switching device has an alternate port, you need to
configure loop protection on both the root port and the alternate port.
Do as follows on a root port and an alternate port on a switching device.
Procedure
Step 1 Run:
system-view
Step 2 Run:

portswitch
NOTE
Step 4 Run:
stp loop-protection
Loop protection for the root port or the alternate port is configured on the switching device.
By default, loop protection is disabled.
----End


After RSTP protection functions are configured, you can verify that the configurations take
effect.
Prerequisite
All configurations of RSTP protection functions are complete.
Procedure
view the status of a spanning tree, including the status of protection functions on a switching
device
----End
Example
Run the display stp command to view the working mode of a spanning tree, the status of BPDU
protection on a switching device, and the status of root protection on a specified port. For
example:
<HUAWEI> display stp
CIST Bridge :32768.00e0-4e1f-b200
CIST Root/ERPC :0 .00e0-e70a-4d00 / 20
CIST RegRoot/IRPC :32768.00e0-4e1f-b200 / 0
BPDU-Protection :enabled

Port Role :Designated Port
Port Priority :128
Protection Type :Root
Port Stp Mode :RSTP
TC or TCN send :1
BPDU Sent :4
BPDU Received :22
Port Priority :160
Desg. Bridge/Port :4096.00e0-6606-be00 / 128.1


Port Stp Mode :RSTP
TC or TCN send :1
BPDU Sent :2
BPDU Received :22
6.5 Configuring STP/RSTP Interoperability Between

Huawei Devices and Non-Huawei Devices
To supports STP/RSTP interoperability between Huawei devices and non-Huawei devices,
proper parameters are required on Huawei devices running STP/RSTP to ensure nonstop
communication.

Before configuring STP/RSTP interoperability between Huawei devices and non-Huawei
devices, familiarize yourself with the applicable environment, complete the pre-configuration
tasks, and obtain the required data. This will help you complete the configuration task quickly
and accurately.
On a network running STP/RSTP, inconsistent protocol packet formats and BPDU keys may
lead to a communication failure. Configuring proper STP/RSTP parameters on Huawei devices
ensures interoperability between Huawei devices and non-Huawei devices.
Before configuring STP/RSTP interoperability between Huawei devices and non-Huawei
devices, complete the following task:
l Configuring basic STP/RSTP functions
Data Preparation
To configure STP/RSTP interoperability between Huawei devices and non-Huawei devices, you
No. Data
1 BPDU format
6.5.2 Configuring the BPDU Format on a Switching Device

To make a Huawei device interoperate with a non-Huawei device, set the BPDU format to Per
VLAN Spanning Tree (PVST).

Prerequisite
Basic VPLS functions have been configured before you can configure the BPDU format in the
PW template view.
Procedure
Step 1 Run:
system-view
Step 2 Enter the view to configure the BPDU format:

l Perform the following steps to enter the PW template view:
1. Run the vsi vsi-name [ auto | static ] command to create a VSI or enter the VSI view.
2. Run the pwsignal { bgp | ldp } command to configure a signaling mode for the VSI.
3. Run the vsi-id vsi-id command to set the VSI ID.
4. Run the peer peer-address [ negotiation-vc-id vc-id ] pw pw-name command to enter
the VSI-LDP-PW view.
l Run the interface interface-type interface-number command to enter the Ethernet interface
view. interface-type specifies the interface type. The interface types can be Ethernet, Eth-
Trunk, virtual Ethernet, and GigabitEthernet.
Step 3 Run:
stp bpdu-encapsulation { pvst | stp }
The BPDU format is configured on the switching device.
By default, the BPDU format is STP.
To make a Huawei device interoperate with a non-Huawei device, the PVST BPDU format needs
to be used.
----End
6.5.3 Configuring the Proposal/Agreement Mechanism

To enable Huawei Datacom devices to communicate with non-Huawei devices, a proper rapid
transition mechanism needs to be configured on Huawei devices based on the Proposal/
Agreement mechanism on non-Huawei devices.
Context
The rapid transition mechanism is also called the Proposal/Agreement mechanism. Switching
devices currently support the following modes:
l Enhanced mode: The current interface counts a root port when it counts the synchronization
flag bit.
– An upstream device sends a Proposal message to a downstream device, requesting rapid
status transition. After receiving the message, the downstream device sets the port
connected to the upstream device to a root port and blocks all non-edge ports.

– The upstream device then sends an Agreement message to the downstream device. After
the downstream device receives the message, the root port transitions to the Forwarding
state.
– The downstream device responds the Proposal message with an Agreement message.
After receiving the message, the upstream device sets the port connected to the
downstream device as a designated port. The designated port then transitions to the
Forwarding state.
l Common mode: The current interface ignores the root port when it counts the
synchronization flag bit.
connected to the upstream device to a root port and blocks all non-edge ports. The root
port then transitions to the Forwarding state.
– The downstream device responds the Proposal message with an Agreement message.
Forwarding state.
When Huawei datacom devices are interworking with non-Huawei devices, select either mode
depending on the Proposal/Agreement mechanisms on non-Huawei devices.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
stp no-agreement-check
The common rapid transition mechanism is configured.
By default, the interface uses the enhanced rapid transition mechanism.
----End

After MSTP parameters are configured for the interoperability between Huawei devices and
non-Huawei devices, you can verify that the configurations take effect.
Prerequisite
Parameters have been configured to ensure MSTP interoperability between Huawei devices and
non-Huawei devices.

Procedure
view spanning-tree status.
----End
Example
Run the display stp command to view the working mode of the spanning tree and the BPDU
format. For example:
<HUAWEI> display stp interface gigabitethernet 1/0/1
Port Priority :128
Port Stp Mode :RSTP
BPDU Encapsulation:Config=stp / Active=stp
TC or TCN send :1
BPDU Sent :4
BPDU Received :22
6.6 Maintaining STP/RSTP

STP/RSTP maintenance includes resetting STP/RSTP statistics.
6.6.1 Clearing STP/RSTP Statistics

You can run the reset commands to reset STP/RSTP statistics to 0.
Context
CAUTION
STP/RSTP statistics cannot be restored after you clear them. Therefore, exercise caution when
using the reset commands.
After you confirm that STP/RSTP statistics need to be cleared, run the following command in
the user view.

Procedure
Step 1 Run the reset stp [ interface interface-type interface-number ] statistics command to clear
spanning-tree statistics.
----End

This section shows typical usage scenarios of STP/RSTP by describing networking
files.
6.7.1 Example for Configuring Basic STP Functions

This example shows how to configure basic STP functions.
situation.
entries.
STP can be deployed on a network to eliminate loops by blocking some ports. On the network
shown in Figure 6-3, after RouterA, SwitchB, SwitchC, and RouterD running STP discover
loops on the network by exchanging information with each other, they trim the ring topology
into a loop-free tree topology by blocking a certain port. In this manner, replication and circular
propagation of packets are prevented on the network and the switching devices are released from
processing duplicated packets, thereby improving their processing performance.

Figure 6-3 Networking diagram of configuring basic STP functions
Network
GE1/0/3 GE1/0/3
Root
RouterD GE1/0/1 GE1/0/1
Bridge
GE1/0/2 GE1/0/2 RouterA
STP
GE1/0/3 GE1/0/3
SwitchC SwitchB
GE1/0/1 GE1/0/1
GE1/0/2 GE1/0/2
PC1 PC2
Blocked port
1. Configure basic STP functions, including:
(1) Configure the STP mode for the ring network.
(2) Configure primary and secondary root bridges.
(3) Set path costs for ports to block certain ports.
(4) Enable STP to eliminate loops, including:
l Enable STP globally.
l Enable STP on all the interfaces except the interfaces connected to terminals.
NOTE
STP is not required on the interfaces connected to terminals because these interfaces do not
need to participate in STP calculation.
By default, STP is enabled on a Layer 2 interface but not enabled on a Layer 3 interface.
Data Preparation
To complete the configuration, you need the following data.

l GE interface number, as shown in Figure 6-3

l Primary root bridge RouterA and secondary root bridge RouterD
l Path cost of a port to be blocked (20000 is used in this example)
Procedure
Step 1 Configure basic STP functions.
1. Configure the STP mode for the devices on the ring network.
# Configure the STP mode on RouterA.
[RouterA] stp mode stp
# Configure the STP mode on SwitchB.

[HUAWEI] sysname SwitchB
[SwitchB] stp mode stp
# Configure the STP mode on SwitchC.

[HUAWEI] sysname SwitchC
[SwitchC] stp mode stp
# Configure the STP mode on RouterD.

[RouterD] stp mode stp
2. Configure primary and secondary root bridges.

# Configure RouterA as a primary root bridge.
[RouterA] stp root primary
# Configure RouterD as a secondary root bridge.

[RouterD] stp root secondary
3. Set path costs for ports in each spanning tree to block certain ports.
NOTE
l The values of path costs depend on path cost calculation methods. Use the Huawei proprietary
calculation method as an example to set the path costs of the ports to be blocked to 20000.
l All switching devices on a network must use the same path cost calculation method.
# On RouterA, configure the path cost calculation method as the Huawei proprietary
method.
[RouterA] stp pathcost-standard legacy
# On RouterB, configure the path cost calculation method as the Huawei proprietary
method.
[RouterB] stp pathcost-standard legacy
# On SwitchC, configure the path cost calculation method as the Huawei proprietary method
and set the path cost of GE 1/0/1 to 20000.
[SwitchC] stp pathcost-standard legacy
[SwitchC] interface gigabitethernet 1/0/1
[SwitchC-GigabitEthernet1/0/1] stp cost 20000
[SwitchC-GigabitEthernet1/0/1] quit
# On SwitchD, configure the path cost calculation method as the Huawei proprietary
method.
[SwitchD] stp pathcost-standard legacy

4. Enable STP to eliminate loops.

l Disable STP on interfaces connected to PCs.
# Disable STP on GE 1/0/2 on SwitchB.
[SwitchB] interface gigabitethernet 1/0/2
[SwitchB-GigabitEthernet1/0/2] stp disable
[SwitchB-GigabitEthernet1/0/2] quit
# Disable STP on GE 1/0/2 on SwitchC.

[SwitchC-GigabitEthernet1/0/2] stp disable
l Enable STP globally.

# Enable STP globally on RouterA.
[RouterA] stp enable
# Enable STP globally on SwitchB.

[SwitchB] stp enable
# Enable STP globally on SwitchC.

[SwitchC] stp enable
# Enable STP globally on RouterD.

[RouterD] stp enable
l Enable STP on all the interfaces except the interfaces connected to terminals.
# Enable STP on GE 1/0/1 and GE 1/0/2 on RouterA.
[RouterA-GigabitEthernet1/0/1] stp enable
# Enable STP on GE 1/0/1 and GE 1/0/3 on SwitchB.

[SwitchB-GigabitEthernet1/0/1] stp enable
# Enable STP on GE 1/0/1 and GE 1/0/3 on SwitchC.

[SwitchC-GigabitEthernet1/0/1] stp enable
# Enable STP on GE 1/0/1 and GE 1/0/2 on RouterD.

[RouterD-GigabitEthernet1/0/1] portswitch
[RouterD-GigabitEthernet1/0/1] stp enable


After the previous configurations, run the following commands to verify the configuration when
the network is stable:
# Run the display stp brief command on RouterA to view the interface status and protection
type. The displayed information is as follows:
[RouterA] display stp brief
MSTID Port Role STP State Protection
0 GigabitEthernet1/0/1 DESI FORWARDING NONE
After RouterA is configured as a root bridge, GE 1/0/2 and GE 1/0/1 connected to SwitchB and
RouterD respectively are elected as designated ports in spanning tree calculation.
# Run the display stp interface gigabitethernet 1/0/1 brief command on SwitchB to view status
of GE 1/0/1. The displayed information is as follows:
[SwitchB] display stp interface gigabitethernet 1/0/1 brief
GE 1/0/1 is elected as a designated port in spanning tree calculation and is in the Forwarding
state.
# Run the display stp interface gigabitethernet 1/0/3 brief command on SwitchC to view status
[SwitchC] display stp interface gigabitethernet 1/0/3 brief
0 GigabitEthernet1/0/3 ROOT FORWARDING NONE
state.
# Run the display stp command on RouterD to view the interface status and protection type.
The displayed information is as follows:
[RouterD] display stp
-------[CIST Global Info][Mode STP]-------
CIST Bridge :4096 .00e0-2c09-9200
CIST Root/ERPC :0 .00e0-0543-6a00 / 20000
CIST RegRoot/IRPC :4096 .00e0-2c09-9200 / 0
CIST Root Type :SECONDARY root
Share region-configuration :enabled
Port Priority :128
Port Cost(Dot1T ) :Config=auto / Active=20000
Desg. Bridge/Port :0.00e0-0543-6a00 / 128.1
Port Stp Mode :STP

TC or TCN send :4
BPDU Sent :5
BPDU Received :177
Port Priority :128
Desg. Bridge/Port :4096.00e0-2c09-9200 / 128.2
Port Stp Mode :STP
TC or TCN send :2
BPDU Sent :165
BPDU Received :2
----End
Configuration Files
#
sysname
RouterA
#
stp mode
stp
stp instance 0 root
primary
stp pathcost-standard
legacy
stp
enable
#
interface
portswitch
undo shutdown
#
interface
portswitch
undo shutdown
#
return
l Configuration file of SwitchB

#
sysname
SwitchB
#
stp mode
stp
legacy
stp
enable

#
interface
#
stp
disable
#
interface
#
return
l Configuration file of SwitchC

#
sysname
SwitchC
#
stp mode
stp
legacy
stp
enable
#
interface
stp instance 0 cost
20000
#
interface
stp
disable
#
interface
#
return
#
l Configuration file of RouterD

#
sysname
RouterD
#
stp mode
stp
stp instance 0 root
secondary
legacy
stp
enable
#
interface
undo shutdown
portswitch
#
interface
undo shutdown
portswitch
#
return

6.7.2 Example for Configuring Basic RSTP Functions

This example shows how to configure basic RSTP functions.
situation.
entries.
RSTP can be deployed on a network to eliminate loops by blocking some ports, and it is
developed to implement the rapid convergence based on STP but outperforms STP. On the
network shown in Figure 6-4, after RouterA, SwitchB, SwitchC, and RouterD running RSTP
discover loops on the network by exchanging information with each other, they trim the ring
topology into a loop-free tree topology by blocking a certain port. In this manner, replication
and circular propagation of packets are prevented on the network and the switching devices are
released from processing duplicated packets, thereby improving their processing performance.
Figure 6-4 Networking diagram of configuring basic RSTP functions
Network
GE1/0/3 GE1/0/3
Root
GE1/0/1 GE1/0/1
Bridge
RouterD GE1/0/2 GE1/0/2 RouterA
RSTP
GE1/0/3 GE1/0/3
SwitchC SwitchB
GE1/0/1 GE1/0/1
GE1/0/2 GE1/0/2
PC1 PC2
Blocked port

1. Configure basic RSTP functions, including:
(1) Configure the RSTP mode for the ring network.
(2) Configure primary and secondary root bridges.
(3) Set path costs for ports in each MSTI to block certain ports.
(4) Enable RSTP to eliminate loops, including:
l Enable RSTP globally.
l Enable RSTP on all the interfaces except the interfaces connected to terminals.
NOTE
RSTP is not required on the interfaces connected to terminals because these interfaces do not
need to participate in RSTP calculation.
By default, RSTP is enabled on a Layer 2 interface but not enabled on a Layer 3 interface.
2. Configure RSTP protection functions, for example, root protection on a designated port of
a root bridge in each MSTI.
Data Preparation
To complete the configuration, you need the following data.
l GE interface number, as shown in Figure 6-4
l Primary root bridge RouterA and secondary root bridge RouterD
l Path cost of a port to be blocked (20000 is used in this example)
Procedure
Step 1 Configure basic RSTP functions.
1. Configure the RSTP mode for the devices on the ring network.
# Configure the RSTP mode on RouterA.
[RouterA] stp mode rstp
# Configure the RSTP mode on SwitchB.

[HUAWEI] sysname SwitchB
[SwitchB] stp mode rstp
# Configure the RSTP mode on SwitchC.

[SwitchC] stp mode rstp
# Configure the RSTP mode on RouterD.

[RouterD] stp mode rstp
2. Configure primary and secondary root bridges.

# Configure RouterA as a primary root bridge.
[RouterA] stp root primary
# Configure RouterD as a secondary root bridge.

[RouterD] stp root secondary
3. Set path costs for ports in each spanning tree to block certain ports.
NOTE
l The values of path costs depend on path cost calculation methods. Use the Huawei proprietary
calculation method as an example to set the path costs of the ports to be blocked to 20000.
l All switching devices on a network must use the same path cost calculation method.
method.
method.
and set the path cost of GE 1/0/1 to 20000.
[SwitchC-GigabitEthernet1/0/1] stp cost 20000
method.
4. Enable RSTP to eliminate loops.

l Disable RSTP on interfaces connected to PCs.
# Disable RSTP on GE 1/0/2 on SwitchB.
[SwitchB-GigabitEthernet1/0/2] stp disable
# Disable RSTP on GE 1/0/2 on SwitchC.

l Enable RSTP globally.

# Enable RSTP globally on RouterA.
# Enable RSTP globally on SwitchB.

[SwitchB] stp enable
# Enable RSTP globally on SwitchC.

# Enable RSTP globally on SwitchD.

[RouterD] stp enable
l Enable RSTP on all the interfaces except the interfaces connected to terminals.
# Enable RSTP on GE 1/0/1 and GE 1/0/2 on RouterA.


# Enable RSTP on GE 1/0/1 and GE 1/0/3 on SwitchB.

# Enable RSTP on GE 1/0/1 and GE 1/0/3 on SwitchC.

# Enable RSTP on GE 1/0/1 and GE 1/0/2 on RouterD.

Step 2 Configure RSTP protection functions, for example, root protection on a designated port of a root
bridge in each MSTI.
# Enable root protection on GE 1/0/1 on RouterA.

[RouterA-GigabitEthernet1/0/1] stp root-protection
# Enable root protection on GE 1/0/2 on RouterA.

After the previous configurations, run the following commands to verify the configuration when
the network is stable:
[RouterA] display stp brief
0 GigabitEthernet1/0/1 DESI FORWARDING ROOT
After RouterA is configured as a root bridge, GE 1/0/2 and GE 1/0/1 connected to SwitchB and
RouterD respectively are elected as designated ports in spanning tree calculation. The root
protection function is enabled on the designated ports.
# Run the display stp interface gigabitethernet 1/0/1 brief command on SwitchB to view status

[SwitchB] display stp interface gigabitethernet 1/0/1 brief

state.
# Run the display stp interface gigabitethernet 1/0/3 brief command on SwitchC to view status
state.
# Run the display stp command on RouterD to view the interface status and protection type.
The displayed information is as follows:
[RouterD] display stp
CIST Bridge :4096 .00e0-2c09-9200
CIST Root/ERPC :0 .00e0-0543-6a00 / 20000
CIST RegRoot/IRPC :4096 .00e0-2c09-9200 / 0
CIST Root Type :SECONDARY root
Share region-configuration :enabled
Port Priority :128
Desg. Bridge/Port :0.00e0-0543-6a00 / 128.1
Port Stp Mode :RSTP
TC or TCN send :4
BPDU Sent :5
BPDU Received :177
Port Priority :128
Desg. Bridge/Port :4096.00e0-2c09-9200 / 128.2
Port Stp Mode :RSTP

TC or TCN send :2
BPDU Sent :165
BPDU Received :2
----End
Configuration Files
#
sysname
RouterA
#
stp mode
rstp
stp instance 0 root
primary
legacy
stp
enable
#
interface
portswitch
undo shutdown
stp root-
protection
#
interface
portswitch
undo shutdown
stp root-
protection
#
return
l Configuration file of SwitchB

#
sysname
SwitchB
#
stp mode
rstp
legacy
stp
enable
#
interface
#
stp
disable
#
interface
#
return

#
sysname

SwitchC
#
stp mode
rstp
legacy
stp
enable
#
interface
stp instance 0 cost
20000
#
interface
stp
disable
#
interface
#
return
#

#
sysname
RouterD
#
stp mode
rstp
stp instance 0 root
secondary
legacy
stp
enable
#
interface
undo shutdown
portswitch
#
interface
undo shutdown
portswitch
#
return

Configuration Guide - LAN Access and MAN Access 7 MSTP Configuration
7 MSTP Configuration
About This Chapter
The Multiple Spanning Tree Protocol (MSTP) trims a ring network into a loop-free tree network.
It prevents replication and circular propagation of packets, provides multiple redundant paths
for Virtual LAN (VLAN) data traffic, and enables load balancing.
7.1 MSTP Overview

MSTP enables multiple VLANs to be grouped into a spanning-tree instance, forming a VLAN
mapping table. Each instance has a spanning-tree topology independent of other spanning-tree
instances. This architecture provides multiple forwarding paths for data traffic and enables load
balancing.
7.2 Configuring Basic MSTP Functions
MSTP based on the basic STP/RSTP function divides a switching network into multiple regions,
each of which has multiple spanning trees that are independent of each other. MSTP isolates
user traffic and service traffic, and load-balances VLAN traffic.
7.3 Configuring MSTP Multi-process
After an MSTP device binds its ports to different processes, the MSTP device performs the
MSTP calculation based on processes, and only relevant ports in each process take part in MSTP
calculation.
7.4 Configuring MSTP Parameters on an Interface
MSTP implements RSTP rapid convergence. To achieve rapid convergence, you need to
configure proper MSTP parameters.
7.5 Configuring MSTP Protection Functions
MSTP protection functions are as follows, and you can configure one or more functions as
required.
7.6 Configuring MSTP Interoperability Between Huawei Devices and Non-Huawei Devices
To enable Huawei devices to interwork with non-Huawei devices, configure proper parameters
and functions, including the BPDU format, MSTP protocol packet format, and digest snooping
function, on the Huawei devices running MSTP.
7.7 Maintaining MSTP
MSTP maintenance includes resetting MSTP statistics.

This section shows typical usage scenarios of MSTP by describing networking requirements,
configuration roadmap, and data preparation, and provides related configuration files.

7.1 MSTP Overview

MSTP enables multiple VLANs to be grouped into a spanning-tree instance, forming a VLAN
mapping table. Each instance has a spanning-tree topology independent of other spanning-tree
instances. This architecture provides multiple forwarding paths for data traffic and enables load
balancing.
7.1.1 MSTP Introduction

The Multiple Spanning Tree Protocol (MSTP) incorporates the functions of the Spanning Tree
Protocol (STP) and Rapid Spanning Tree Protocol (RSTP), and outperforms them. It enables
rapid convergence and provides load balancing across redundant paths.
Background
STP and RSTP are used in a LAN to prevent loops. The devices running STP/RSTP discover
loops on the network by exchanging information with each other and trim the ring topology into
a loop-free tree topology by blocking a certain interface. Replication and circular propagation
of packets are thus prevented on the network and the processing performance of devices is
improved by avoiding repeated packets on the network.
STP and RSTP both have a defect: All VLANs on a LAN use one spanning tree, and thus inter-
VLAN load balancing cannot be performed. Once a link is blocked, the link will no longer
transmit traffic, wasting bandwidth and causing a failure in forwarding certain VLAN packets.
To fix the defect of STP and RSTP, the IEEE released the 802.1s standard in 2002, defining
MSTP. MSTP compatible with STP and RSTP implements rapid convergence and provides
multiple paths to load balance VLAN traffic.
Table 7-1 shows the comparison between STP, RSTP, and MSTP.

Table 7-1 Comparison between STP, RSTP, and MSTP
Spanning Tree Characteristics Application Precautions

Protocols Scenarios
STP A loop-free tree is generated. Irrespective of NOTE

Thus, broadcast storms are different users or l If the current
prevented and redundancy is services, all switching
implemented. VLANs share one device
supports
spanning tree.
RSTP l A loop-free tree is only STP,
STP is
generated. Thus,
recommende
broadcast storms are d. For
prevented and redundancy details, see
is implemented. STP/RSTP
Configurati
l A feedback mechanism is on.
provided to confirm
l If the current
topology convergence. switching
Thus, rapid convergence device
is implemented. supports
both STP
MSTP l A loop-free tree or some User or service- and RSTP,
loop-free trees are specific load RSTP is
generated. Thus, balancing is recommende
broadcast storms are required. Traffic d. For
details, see
prevented and redundancy for different STP/RSTP
is implemented. VLANs is Configurati
l A feedback mechanism is forwarded on.
provided to confirm through different l If the current
topology convergence. spanning trees, switching
Thus, rapid convergence which are device
independent of supports
is implemented. STP or
each other.
l MSTP implements load RSTP, and
balancing among VLANs. MSTP,
MSTP is
Traffic in different recommende
VLANs is transmitted d.
along different paths.
Introduction
situation.
entries.
MSTP, compatible with STP and RSTP, isolates service traffic and user traffic by using multiple
instances and provides multiple paths to load balance VLAN traffic.

If MSTP is deployed in the LAN shown in Figure 7-1, MSTIs are generated, as shown in Figure
7-1.
Figure 7-1 Multiple spanning trees in an MST region

SwitchA SwitchD
VLAN3 VLAN2
Host C Host A
(VLAN3) VLAN3 VLAN2 (VLAN2)
SwitchB SwitchE
VLAN2
VLAN2
Host B Host D
VLAN3
(VLAN2) (VLAN3)
VLAN3
VLAN2 VLAN3
SwitchC SwitchF
MSTI1 (root switch: SwitchD) VLAN2 MSTI1

MSTI2 (root switch: SwitchF) VLAN3 MSTI2
l MSTI 1 uses Switch D as the root switching device to forward packets of VLAN 2.
l MSTI 2 uses Switch F as the root switching device to forward packets of VLAN 3.
Devices within the same VLAN can communicate with each other and packets of different
VLANs are load-balanced along different paths.
Basic MSTP Concepts

l MST region
An MST region contains multiple switching devices and network segments between them.
The switching devices have the following characteristics:
– MSTP-enabled
– Same region name
– Same VLAN-to-instance mapping
– Same MSTP revision number
A LAN can comprise several MST regions that are directly or indirectly connected.
Multiple switching devices can be grouped into an MST region by using MSTP
configuration commands.
As shown in Figure 7-2, the MST region D0 contains the switching devices S1, S2, S3,
and S4, and has three MSTIs.

Figure 7-2 MST region
AP1
D0
MSTI1
Master Bridge
root switch:S3
S1
MSTI2
root switch:S2
MSTI0 (IST)
S2 S3 root switch:S1
VLAN1 MSTI1
VLAN2,VLAN3 MSTI2
S4 other VLANs MSTI0
l VLAN mapping table

The VLAN mapping table is an attribute of the MST region. It describes mappings between
VLANs and MSTIs.
Figure 7-2 shows the mappings in the VLAN mapping table of the MST region D0:
– VLAN 1 is mapped to MSTI 1.
– VLAN 2 and VLAN 3 are mapped to MSTI 2.
– Other VLANs are mapped to MSTI 0.
l Regional root
Regional roots are classified into Internal Spanning Tree (IST) and MSTI regional roots.
In the region B0, C0, and D0 on the network shown in Figure 7-4, the switching devices
closest to the Common and Internal Spanning Tree (CIST) root are IST regional roots.
An MST region can contain multiple spanning trees, each called an MSTI. An MSTI
regional root is the root of the MSTI. On the network shown in Figure 7-3, each MSTI has
its own regional root.

Figure 7-3 MSTI
MST Region
VLAN VLA
N 10&
10&20&30 20
VLAN 20&30
VLAN VLAN VLAN

30 VLAN
10&30 20 10&30
VLAN 10
Root
Root
MSTI MSTI MSTI Root

corresponding to corresponding to corresponding to
VLAN 10 VLAN 20 VLAN 30
MSTI links
MSTI links blocked by the protocol
MSTIs are independent of each other. An MSTI can correspond to one or more VLANs,
but a VLAN can be mapped to only one MSTI.
l CIST root

Figure 7-4 MSTP network
A0
CIST Root
D0 Region Root B0
Region Root
C0
Region Root
IST
CST
On the network shown in Figure 7-4, the CIST root is the root bridge of a CIST. The CIST
root is a device in A0.
l CST
A Common Spanning Tree (CST) connects all the MST regions on a switching network.
Each MST region can be considered a node. A CST is calculated by using STP or RSTP
based on all the nodes.
As shown in Figure 7-4, the MST regions are connected to form a CST.
l IST
An IST resides within an MST region.
An IST is a special MSTI with the MSTI ID of 0, called MSTI 0.
An IST is a segment of the CIST in an MST region.
As shown in Figure 7-4, the switching devices in an MST region are connected to form an
IST.
l CIST
A CIST, calculated by using STP or RSTP, connects all the switching devices on a switching
network.
As shown in Figure 7-4, the ISTs and the CST form a complete spanning tree, that is, CIST.
l SST
A Single Spanning Tree (SST) is formed in either of the following situations:

– A switching device running STP or RSTP belongs to only one spanning tree.
– An MST region has only one switching device.
As shown in Figure 7-4, the switching device in B0 is an SST.
l Port roles
Compared with RSTP, MSTP has two additional port types. MSTP ports can be root ports,
designated ports, alternate ports, backup ports, edge ports, master ports, and regional edge
ports.
The functions of root ports, designated ports, alternate ports, backup ports, and edge ports
have been defined in RSTP. Table 7-2 lists all port roles in MSTP.
NOTE
Except edge ports, all ports participate in MSTP calculation.

A port can play different roles in different MSTIs.
Table 7-2 Port roles

Port Description
Roles
Root port A root port is the non-root bridge port closest to the root bridge. Root bridges
do not have root ports.
Root ports are responsible for sending data to root bridges.
As shown in Figure 7-5, S1 is the root; CP1 is the root port on S3; BP1 is
the root port on S2; DP1 is the root port on S4.
Designat The designated port on a switching device forwards bridge protocol data
ed port units (BPDUs) to the downstream switching device.
As shown in Figure 7-5, AP2 and AP3 are designated ports on S1; BP2 is
a designated port on S2; CP2 is a designated port on S3.
Alternate l From the perspective of sending BPDUs, an alternate port is blocked after
port a BPDU sent by another switching devices is received.
l From the perspective of user traffic, an alternate port provides an
alternate path to the root bridge. This path is different than using the root
port.
As shown in Figure 7-5, BP2 and AP4 are alternate ports.
Backup l From the perspective of sending BPDUs, a backup port is blocked after
port a BPDU sent by itself is received.
l From the perspective of user traffic, a backup port provides a backup/
redundant path to a segment where a designated port already connects.
As shown in Figure 7-5, CP3 is a backup port.

Port Description
Roles
Master A master port is on the shortest path connecting MST regions to the CIST
port root.
BPDUs of an MST region are sent to the CIST root through the master port.
Master ports are special regional edge ports, functioning as root ports on
ISTs or CISTs and master ports in instances.
As shown in Figure 7-5, S1, S2, S3, and S4 form an MST region. AP1 on
S1, being the nearest port in the region to the CIST root, is the master port.
Regional A regional edge port is located at the edge of an MST region and connects
edge port to another MST region or an SST.
During MSTP calculation, the roles of a regional edge port in the MSTI and
the CIST instance are the same. If the regional edge port is the master port
in the CIST instance, it is the master port in all the MSTIs in the region.
As shown in Figure 7-5, AP1, DP2, and DP3 in an MST region are directly
connected to other regions, and therefore they are all regional edge ports of
the MST region.
As shown in Figure 7-5, AP1 is a regional edge port and also a master port
in the CIST. Therefore, AP1 is the master port in every MSTI in the MST
region.
Edge An edge port is located at the edge of an MST region and does not connect
port to any switching device.
Generally, edge ports are directly connected to terminals.
As shown in Figure 7-5, BP3 is an edge port.
Figure 7-5 Port roles
AP1 AP4
MST Region
Root port
AP2 AP3
S1 Designated port
Root Bridge Alternate port
CP1 BP1 Backup port
S3 S2 Regional edge port
BP2 Master port
CP2 CP3 BP3
Edge port
S4
DP1 DP4 PC
DP2 DP3

l Port status
Table 7-3 lists the MSTP port status, which is the same as the RSTP port status.
Table 7-3 Port status

Port Description
Status
Forwardi A port in the Forwarding state can send and receive BPDUs as well as
ng forward user traffic.
Learning This is a transition state. A port in the Learning state learns MAC addresses
from user traffic to construct a MAC address table.
In the Learning state, the port can send and receive BPDUs, but cannot
forward user traffic.
Discardi A port in the Discarding state can only receive BPDUs.

ng
There is no necessary link between the port status and the port role. Table 7-4 lists the
relationships between port roles and port status.
Table 7-4 Relationships between port roles and port status

Port Root Port/ Designate Regional Alternate Backup
Status Master d Port Edge Port Port Port
Port
Forwardi Yes Yes Yes No No

ng
Learning Yes Yes Yes No No
Discardi Yes Yes Yes Yes Yes

ng
Yes: The port supports this status.

No: The port does not support this status.
7.1.2 MSTP Features Supported by the NE80E/40E

Before configuring MSTP, familiarize yourself with the concepts of basic MSTP functions,
topology convergence, MSTP protection, MSTP multi-process, and MSTP interoperability
between Huawei devices and non-Huawei devices. This will help you complete the configuration
task quickly and accurately.
MSTP is used to block redundant links on the Layer 2 network and trim a network into a loop-
free tree. In MSTP, multiple MSTIs can be created and VLANs are mapped into different
instances to load-balance VLAN traffic. The basic configuration roadmap of MSTP is as follows:

1. In a ring network, divide regions and create different instances for regions.
2. Select a switching device functioning as a root bridge from switching devices for each
instance.
3. In each instance, calculate the shortest paths from the other switching devices to the root
bridge, and select a root port for each non-root switching device.
4. In each instance, select a designated port for each connection according to port IDs.
According to current networking, master ports and backup ports may be involved. For details,
see 7.1.1 MSTP Introduction.
MSTP also supports the following features to meet requirements of special applications and
extended functions:
l Supports the Proposal/Agreement mechanism to implement rapid convergence.
l Supports protection functions as listed in Table 7-5.
l Supports MSTP multi-process in the scenario where MSTP and STP/RSTP are used
together. MSTP multi-process implements independent spanning tree calculation for every
access rings.
l Supports MSTP interoperability between Huawei devices and non-Huawei devices. Proper
parameters are required on Huawei devices running MSTP to ensure nonstop
communication.
l Supports Enhanced STP (E-STP). A PW, which is considered as an interface, participates
in MSTP calculation for updating the network topology to eliminate loops. E-STP prevents
loops and duplicate traffic on an inter-AS VPLS network or in the scenario where a CE is
dual-homed to two PEs. With MSTP multi-instance and multi-process features, load
balancing of VLAN traffic can be implemented. For details, see 7.8 Configuration
Examples.
Table 7-5 MSTP protection

MSTP Scenario Configuration Impact
Protection



Protection

delete MAC entries and ARP device receives within the given time exceeds
resources. number of times. Excessive TC-BPDUs are
for once after the timeout period expires. This
protects the switching device from frequently
deleting MAC entries and ARP entries, thus
avoiding over-burden.
Root Due to incorrect To address this issue, the root protection

protection configurations or malicious function can be configured to protect the root
attacks on the network, a bridge by preserving the role of the
root bridge may receive designated port. With this function, when the
BPDUs with a higher designated port receives RST BPDUs with a
priority. Consequently, the higher priority, the port enters the Discarding
legitimate root bridge is no state and does not forward the BPDUs. If the
longer able to serve as the port does not receive any RST BPDUs with a
root bridge, and the network higher priority for a certain period (double the
topology is illegitimately Forward Delay), the port transitions to the
traffic congestion.
Loop A root port or an alternate The loop protection function can be used to
protection port will age if link prevent such network loops. If the root port
congestion or a one-way link or alternate port cannot receive RST BPDUs
failure occurs. After the root from the upstream switching device, the root
port ages, a switching device port is blocked and the switching device
may re-select a root port notifies the NMS that the port enters the
incorrectly and after the Discarding state. The blocked port remains in
alternate port ages, the port the Blocked state and no longer forwards
enters the Forwarding state. packets. This prevents loops on the network.
Loops may occur in such a The root port restores the Forwarding state
situation. after new RST BPDUs are received.
Share-link In the scenario where a Share-link protection can address such a

protection switching device is dual- problem. This function forcibly changes the
homed to a network, when working mode of the local switching device
the share link of multiple to RSTP. Share-link protection needs to be
processes fails, loops may used together with root protection to avoid
occur. network loops.

MSTP Multi-process
l Background
As shown in Figure 7-6, RouterA, RouterB, and RouterC are connected through Layer 2
links, and are all enabled with MSTP. The CEs on the rings support only STP/RSTP.
Multiple access rings exist and these rings access the MST region by using different
interfaces on RouterA and RouterB.
Figure 7-6 Networking diagram of MSTP multi-process

RouterC
VPLS
PE2
PE1 RouterB
RouterA
CE CE
CE
CE
Instance1:VLAN1~100 Instance3:VLAN1~100
Process 1 Process 3
CE CE
Instance2:VLAN101~200
Process 2
On the network shown in Figure 7-6, multiple Layer 2 rings, Ring 1, Ring 2, and Ring 3
exists. STP must be enabled on these rings to prevent loops. RouterA and RouterB are
connected to multiple access rings and these rings are isolated from each other and do not
need intercommunication. STP then will not calculate out one spanning tree for all these
access rings. Instead, STP on each access ring calculates the trees independently.
MSTP supports multiple spanning tree instances (MSTIs) only when all devices support
MSTP and the devices are configured with the same MST region. In the networking, the
CEs connected to switching devices, however, support only STP/RSTP. According to
MSTP, switching devices consider that they are in different regions with CEs after receiving
STP/RSTP messages sent from the CEs. Therefore, only one spanning tree is calculated
for the ring formed by switching devices and CEs and the access rings are not independent
of each other.
In this case, MSTP multi-process can be used. Multiple MSTP processes can be configured
on RouterA and RouterB. Each MSTP process has the same function and supports MSTIs.
Each MSTP process corresponds to one access ring.

After MSTP multi-process is enabled, each MSTP process can manage some interfaces on
a device. That is, Layer 2 interfaces on the device are divided and managed by multiple
MSTP processes. Each MSTP process runs the standard MSTP.
NOTE
CEs that support MSTP can also be configured with MSTP multi-process.
After a device properly starts, there is a default MSTP process with the ID 0. MSTP configurations
in the system view and interface view both belong to this process.
l Share link
As shown in Figure 7-6, the link between RouterA and RouterB is a Layer 2 link running
MSTP. The share link between RouterA and RouterB is different from the links connecting
switching devices to CEs. The ports on the share link need to participate in the calculation
for multiple access rings and MSTP processes. This allows RouterA and RouterB to identify
from which MST BPDUs are sent.
In addition, a port on the share link participates in the calculation for multiple MSTP
processes, and obtains different status. As a result, the port cannot determine its status.
To prevent this situation, it is defined that a port on a share link always adopts its status in
MSTP process 0 when participating in the calculation for multiple MSTP processes.
E-STP
E-STP abstracts a PW(Pseudo Wire) as an interface, participates in MSTP calculation for
updating the network topology to eliminate loops. E-STP prevents loops and duplicate traffic
on an inter-AS VPLS network or in the scenario where a CE is dual-homed to two PEs. In
addition, MSTP multi-instance and multi-process features are used to implement load balancing.
The basic principles of E-STP are as follows:

l Based on MSTP, E-STP solves the problems that broadcast and unknown unicast packets
are looped and duplicate traffic is transmitted on a ring network.
l By using the MSTP multi-instance feature, E-STP associates VLANs with MSTIs to divide
a network into multiple ASs, each of which has multiple spanning trees that are independent
of each other. This helps implement load balancing and link redundancy on a VPLS
network.
l By using the MSTP multi-process feature, E-STP associates management PWs (mPWs)
with processes. Processes are independent of each other and the mPWs are independent of
each other. The processes associated with different mPWs are calculated separately to
realize load balancing and PW redundancy.
After a PW is created, you can configure mPWs and service PWs by running relevant
commands in the PW view. STP is enabled on the PW of the mVSI to allow the mPW to
participate in MSTP calculation for updating the network topology. The PW of an mVSI
controls multiple service PWs. After an mPW is blocked, the corresponding service PWs
are blocked. In this manner, service traffic can be blocked as required.
l When the network topology changes, the MAC address entries learned by the local device
need to be updated. TC-BPDUs of MSTP are sent to trigger the updating of local MAC
address entries. At the same time, the sending of TC-BPDUs triggers the PW to send the
MAC Withdraw packet to instruct the remote device on the VPLS network to update the
learned MAC address entries.
l If the AC-side network contains multiple switching devices, these devices can be grouped
into the same MST region and deployed with MSTIs; alternatively, they can be grouped
into different MSTP processes and perform MSTP calculation independently.

For detailed description, see the chapter "MSTP" in HUAWEI NetEngine80E/40E Router
Feature Description - LAN Access and MAN Access.
7.2 Configuring Basic MSTP Functions

MSTP based on the basic STP/RSTP function divides a switching network into multiple regions,
each of which has multiple spanning trees that are independent of each other. MSTP isolates
user traffic and service traffic, and load-balances VLAN traffic.
MSTP is commonly configured on a switching device to trim a ring network to a loop-free

network. MSTP configurations on the switching device involve MSTP working mode
configuration and MST region configuration and activation. If you need to interfere in the
spanning tree calculation, the following methods are available:
l Setting a priority for a switching device in an MSTI: The lower the numerical value, the
higher the priority of the switching device and the more likely the switching device becomes
a root bridge; the higher the numerical value, the lower the priority of the switching device
and the less likely that the switching device becomes a root bridge.
l Setting a path cost for a port in an MSTI: With the same calculation method, the lower the
numerical value, the smaller the cost of the path from the port to the root bridge and the
more likely the port becomes a root port; the higher the numerical value, the larger the cost
of the path from the port to the root bridge and the less likely that the port becomes a root
port.
l Setting a priority for a port in an MSTI: The lower the numerical value, the more likely the
port becomes a designated port; the higher the numerical value, the less likely that the port
becomes a designated port.

Before configuring basic MSTP functions, familiarize yourself with the applicable environment,
complete the pre-configuration tasks, and obtain the required data. This will help you complete
situation.
entries.
MSTP can be deployed on a network to eliminate loops. If a loop is detected, MSTP blocks one
or more ports to eliminate the loop. In addition, MSTIs can be configured to load-balance VLAN
traffic.
As shown in Figure 7-7, RouterA, RouterB, Swtich C, and Switch D all support MSTP. It is
required to create MSTI 1 and MSTI 2, configure a root bridge for each MSTI, and set the ports
to be blocked to load-balance traffic of VLANs 1 to 10 and VLANs 11 to 20 among different
paths.

Figure 7-7 Networking diagram of configuring basic MSTP functions
Network
MST Region
RouterA RouterB
SwitchC SwitchD
PC1 PC2
VLAN1~10 MSTI1
VLAN11~20 MSTI2
MSTI1:
Root Bridge:RouterA
Blocked port
MSTI2:
Root Bridge:RouterB
Blocked port
NOTE
If the current device supports MSTP, configuring MSTP is recommended.
Before configuring basic MSTP functions, complete the following task:

l Connecting interfaces and setting physical parameters for the interfaces to ensure that the
physical status of the interfaces is Up
Data Preparation
To configure basic MSTP functions, you need the following data.
No. Data
1 MSTP working mode
2 MST region name, VLAN-to-instance mapping, and MSTP revision number
3 (Optional) ID of an MSTI
4 (Optional) Priority of a switching device in an MSTI
5 (Optional) Priority of a port in an MSTI
6 (Optional) Path cost of a port in an MSTI
7.2.2 Configuring the MSTP Mode

Before configuring basic MSTP functions, you need to configure the working mode of a
switching device to MSTP. MSTP is compatible with STP and RSTP.
Procedure
Step 1 Run:
system-view
Step 2 Run:
stp mode mstp
The working mode of the switching device is configured as MSTP. By default, the working
mode is MSTP.
STP and MSTP cannot recognize packets of each other but MSTP and RSTP can. If a switching
device is configured to work in MSTP mode and is connected to some switching devices running
STP, the switching device automatically transits the working mode of the interfaces connected
to the switching devices running STP to STP and other interfaces still run MSTP. This enables
devices running different spanning tree protocols to interwork with each other.
----End
7.2.3 Configuring and Activating an MST Region

MSTP divides a switching network into multiple MST regions. After an MST region name,
VLAN-to-instance mappings, and an MSTP revision number are configured, activating the MST
region is necessary. After this step is done, MST region configuration is complete.

Context
An MST region contains multiple switching devices and network segments between them. These
switching devices are directly connected and have the same region name, same VLAN-to-
instance mapping, same configuration revision number after MSTP is enabled. One switching
network can have multiple MST regions and multiple switching devices can be grouped into
one MST region by using MSTP configuration commands.
CAUTION
Two switching devices belong to the same MST region when they have the same:
l Name of the MST region
l Mapping between VLANs and MSTIs
l Revision level of the MST region
Do as follows on a switching device that needs to join an MST region:
Procedure
Step 1 Run:
system-view
Step 2 Run:
stp region-configuration
The MST region view is displayed.
Step 3 Run:
region-name name
The name of an MST region is configured.
By default, the MST region name is the MAC address of the management network interface on
the MPU of the switching device.
Step 4 Perform either of the following steps to configure VLAN-to-instance mappings.

l Run the instance instance-id vlan { vlan-id [ to vlan-id ] }&<1-10> command to configure
VLAN-to-instance mappings.
l Run the vlan-mapping modulo modulo command to enable VLAN-to-instance mapping
assignment based on a default algorithm.
By default, all VLANs in an MST region are mapped to MSTI 0.
NOTE
l The instance instance-id vlan { vlan-id [ to vlan-id ] }&<1-10> command is recommended because
VLAN-to-instance mapping assignments cannot meet actual mapping requirements.
l In the command, vlan-mapping modulo indicates that the formula (VLAN ID-1)%modulo+1 is used.
In the formula, (VLAN ID-1)%modulo means the remainder of (VLAN ID-1) divided by the value of
modulo. This formula is used to map a VLAN to the corresponding MSTI. The calculation result of
the formula is ID of the mapping MSTI.


revision-level level
The MSTP revision number is set.

By default, the MSTP revision number is 0.
If the revision number of the MST region is not 0, this step is necessary.
NOTE
The change of related MST region configurations (especially change of the VLAN mapping table) causes
the recalculation of spanning trees and the route flapping in a network. Therefore, after an MST region
name, VLAN-to-instance mappings, and an MSTP revision number is configured, activating the MST
region is necessary. You can run the check region-configuration command in the MST region view to
check whether region configurations are correct. After confirming that region configurations are correct,
run the active region-configuration command to activate MST region configurations.
Step 6 Run:
active region-configuration
MST region configurations are activated so that the configured region name, VLAN-to-instance
mappings, and revision number can take effect.
If this step is not done, the preceding configurations cannot take effect.
If you have changed MST region configurations on the switching device after MSTP starts, run
the active region-configuration command to activate the MST region so that the changed
configurations can take effect.
----End
7.2.4 (Optional) Setting a Priority for a Switching Device in an MSTI

The lower the numerical value is, the higher priority a switching device has and the more likely
the switching device will be selected as a root bridge.
Context
In an MSTI, there is only one root bridge and it is the logic center of the MSTI. In root bridge
selection, the switching device with high performance and network hierarchy is generally
selected as a root bridge; however, the priority of such a device may be not that high. Thus setting
a high priority for the switching device is necessary so that the device can function as a root
bridge.
Other devices with low performance and network hierarchy are not fit to be a root bridge.
Therefore, set low priorities for these devices.
Procedure
Step 1 Run:
system-view

Step 2 Run:
stp [ instance instance-id ] priority priority
A priority is set for the switching device in an MSTI.

The default priority value of the switching device is 32768.
If the instance is not designated, a priority is set for the switching device in MSTI0.
NOTE
l To configure a switching device as a primary root bridge, you can run the stp [ instance instance-id ]
root primary command directly. The priority value of this switching device is 0.
l To configure a switching device as a secondary root bridge, run the stp [ instance instance-id ] root
secondary command. The priority value of this switching device is 4096.
In an MSTI, a switching device cannot act as a primary root bridge and a secondary root bridge at the
same time.
l If you want to change the priority of a switching device after you run the stp root primary command
or the stp [ instance instance-id ] root secondary command to configure the switching device as a
primary root bridge or a secondary root bridge, disable the root bridge function or secondary root bridge
function and then run the stp [ instance instance-id ] priority priority command to re-set a priority.
----End
7.2.5 (Optional) Setting a Path Cost of a Port in an MSTI

The MSTP path cost determines root port selection in an MSTI. The port with the lowest path
cost to the root bridge is selected as a root port.
Context
A path cost is port-specific, which is used by MSTP as a reference to select a link.
Path costs of a port are an important basis for calculating spanning trees. If you set different path
costs for a port in different MSTIs, you can make VLAN traffic be transmitted along different
physical links and thus carry out VLAN load balancing.
Use the Huawei private calculation method as an example. The following table maps link rates
and default path cost values of ports.
Table 7-6 Mapping between link rates and path cost values
Link Rate Recommended Recommended Path Cost Range

Path Cost Path Cost Range
10 Mbit/s 2000 200 to 20000 1 to 200000
100 Mbit/s 200 20 to 2000 1 to 200000
1 Gbit/s 20 2 to 200 1 to 200000
10 Gbit/s 2 2 to 20 1 to 200000
Higher than 10 Gbit/ 1 1 to 2 1 to 200000

s
On a network where loops occur, you are recommended to set a relatively large path cost for the
port at a low link rate. MSTP puts the port with the large path cost in the Blocking state and
blocks the link where this port resides.

Procedure
Step 1 Run:
system-view
Step 2 Run:
stp pathcost-standard { dot1d-1998 | dot1t | legacy }
A path cost calculation method is configured.
By default, the IEEE 802.1t standard method is used to calculate the default path cost.
All switching devices on a network must use the same path cost calculation method.
Step 3 Run:

portswitch
NOTE
Step 5 Run:
stp instance instance-id cost cost
A path cost is set for the port in the current MSTI.
l When the Huawei proprietory calculation method is used, cost ranges from 1 to 200000.
l When the IEEE 802.1d standard method is used, cost ranges from 1 to 65535.
l When the IEEE 802.1t standard method is used, cost ranges from 1 to 200000000.
----End
7.2.6 (Optional) Setting a Port Priority in an MSTI

The lower the numerical value, the more likely the port on a switching device becomes a
designated port; the higher the numerical value, the more likely the port is to be blocked.
Context
In spanning tree calculation, priorities of ports on switching devices in MSTIs determine
designated port selection.
If you expect to block a port on a switching device in an MSTI to eliminate loops, set the port
priority value to be larger than the default value. This port will be blocked in designated port
selection.

Procedure
Step 1 Run:
system-view
Step 2 Run:

portswitch
NOTE
Step 4 Run:
stp instance instance-id port priority priority
A port priority is set in an MSTI.
By default, the port priority is 128.
The value range of the priority is from 0 to 240, with the step 16. That is, the port priority can
be 0, 16, or 32.
----End
7.2.7 Enabling MSTP

After basic MSTP functions are configured on a switching device, enabling the MSTP function
is required so that MSTP can work properly.
Context
After MSTP is enabled on a ring network, MSTP immediately calculates spanning trees on the
network. Configurations on the switching device, such as, the switching device priority and port
priority, will affect spanning tree calculation. Any change of the configurations may cause
network flapping. Therefore, to ensure rapid and stable spanning tree calculation, perform basic
configurations on the switching device and its ports and enable MSTP.
Procedure
Step 1 Run:
system-view
Step 2 Run:
stp enable
MSTP is enabled on the switching device.

By default, the MSTP function is enabled on a NE80E/40E.
----End

After basic MSTP functions are configured, verify that the configurations take effect.
Prerequisite
All configurations of basic MSTP functions are complete.
Procedure
l Run the display stp [ instance instance-id ][ interface { interface-type interface-
number } ] [ brief ] command to view spanning-tree status and statistics.
l Run the display stp region-configuration command to view configurations of activated
MST regions.
l Run the display stp region-configuration [ digest ] command to view the digest
configurations of activated MST regions.
----End
Example
Run the display stp command, and you can view the spanning-tree working mode, priorities of
switching devices, path cost calculation method, and path cost of a root port. For example:
<HUAWEI> display stp instance 0 interface gigabitethernet 1/0/1
-------[CIST Global Info][ Mode MSTP ]-------
CIST Bridge :32768.00e0-fc0e-a421
CIST Root/ERPC :32768.00e0-fc0e-a421 / 0
CIST RegRoot/IRPC :32768.00e0-fc0e-a421 / 0
----[Port3(GigabitEthernet1/0/1)] [ FORWARDING ]----
Port Role :CIST Designated Port
Port Priority :128
Port Cost(Dot1T) :Config=100 / Active=100
Desg. Bridge/Port :32768.00e0-fc0e-a421 / 128.1229
Port Edged :Config=disabled / Active=disabled
Port Stp Mode :MSTP
Port Protocol Type :Config=auto / Active= dot1s
BPDU Sent :0
BPDU Received :0
Run the display stp region-configuration command, and you can view configurations of an
activated MST region, including the region name, VLAN-to-instance mapping, and revision
number. For example:

<HUAWEI> display stp region-configuration

Oper Configuration:
Format selector :0
Region name :huawei
revision number :0
Instance Vlans Mapped
0 21 to 4094
1 1 to 10
2 11 to 20
Run the display stp region-configuration digest command, and you can view the digest
configurations of an activated MST region, including the region name, revision number and
digest. For example:
<HUAWEI> display stp region-configuration digest
Oper Configuration:
Format selector :0
Region name :huawei
Revision level :0
Digest :0x5F762D9A46311EFFB7A488A3267FCA9F
7.3 Configuring MSTP Multi-process

After an MSTP device binds its ports to different processes, the MSTP device performs the
MSTP calculation based on processes, and only relevant ports in each process take part in MSTP
calculation.

Before configuring MSTP multi-process, familiarize yourself with the applicable environment,
On the networking with both Layer 2 single-access rings and multi-access rings deployed,
switching devices bear both Layer 2 and Layer 3 services. To enable different rings to bear
different services, deploy MSTP multi-process. Spanning trees of different processes are
calculated independently and do not affect each other.
As shown in Figure 7-8, Routers A, B, and C are connected through Layer 2 links, and are all
enabled with MSTP. The CEs on the on rings support only STP/RSTP. Multiple access rings
exist and these rings access the MSTP region through different interfaces on Routers A and B.

Figure 7-8 Networking diagram of MSTP multi-process

RouterC
VPLS
PE2
PE1 RouterB
RouterA
CE CE
CE
CE
Instance1:VLAN1~100 Instance3:VLAN1~100
Process 1 Process 3
CE CE
Instance2:VLAN101~200
Process 2
Before configuring MSTP multi-process, complete the following task:
l Configuring basic MSTP functions
Data Preparation
To configure MSTP multi-process, you need the following data.
No. Data
1 IDs of MSTP processes
2 Priority of a switching device in an MSTI
7.3.2 Creating an MSTP Process

A process ID uniquely identifies an MSTP multi-process. After an MSTP device binds its ports
to different processes, the MSTP device performs the MSTP calculation based on processes, and
only relevant ports in each process take part in MSTP calculation.
Context
Do as follows on the devices connected to access rings:

Procedure
Step 1 Run:
system-view
Step 2 Run:
stp process process-id
An MSTP process is created and the MSTP process view is displayed.
Step 3 Run:
stp mode mstp
A working mode is configured for the MSTP process.
The default mode is MSTP.
NOTE
l After a device starts, there is a default MSTP process with the ID 0. MSTP configurations in the system
view and interface view belong to this process. The default working mode of this process is MSTP.
l To add an interface to an MSTP process with the ID of non-zero, run the stp process command and
then the stp binding process command.
----End
7.3.3 Adding an Interface to an MSTP Process - Access Links

The links connecting MSTP devices and access rings are called access links. After being added
to MSTP processes, interfaces on the access links can participate in MSTP calculation.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
The interface specified in this command must be a Layer 2 interface that connects a device and
an accessing ring.
Step 3 Run:
stp binding process process-id
The current interface is added to the MSTP process.

NOTE
If the interface added to the MSTP process has sub-interfaces configured with features other than MSTP
such as VPLS, run the stp vpls-subinterface enable command on the main interface. The main interface
can then notify its sub-interfaces to update MAC entries and ARP entries after receiving a TC-BPDU. This
prevents services from being interrupted. In addition, root protection needs to be configured on the main
interface.
----End
7.3.4 Adding an Interface to an MSTP Process - Share Link

The link shared by multiple access rings are called a share link. The interfaces on the share link
need to participate in MSTP calculation in multiple access rings in different MSTP processes.
After being added to MSTP processes, interfaces on the access links can participate in MSTP
calculation.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

The interface specified in this command must be an interface on the share link between the
devices configured with MSTP multi-process but not the interfaces that connect an access ring
and a device.
Step 3 Run:
stp binding process process-id [ to process-id ] link-share
The interface is added to multiple MSTP processes to complete MSTP calculation.

NOTE
For a process with share links, you must run the stp enable command globally. For an interface that is
added to the process in link-share mode, you must run the stp enable command in the interface view.
----End
7.3.5 Configuring Priorities and Root Protection in MSTP Multi-

process
You can configure priorities and root protection in MSTP multi-process to protect links over
access rings.
Context
To prevent loops over the access ring after the share links fails, configure priorities and root
protection in MSTP multi-process.

Root protection is configured on the access interface of a device with second highest priority.
l For detailed configuration of priorities in MSTP multi-process, see 7.2.4 (Optional)

Setting a Priority for a Switching Device in an MSTI.
l For detailed configuration of root protection in MSTP multi-process, see 7.5.4 Configuring
Root Protection on an Interface.
NOTE
The MSTP priority of a downstream device must be lower than that of a UPE.
7.3.6 Configuring TC Notification in MSTP Multi-process

After the TC notification function is configured for MSTP multi-process, the current MSTP
process can notify the MSTIs in other specified MSTP processes to refresh MAC address entries
and ARP entries after receiving a TC-BPDU. Nonstop services are ensured.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
The view of the created MSTP process is displayed.
Step 3 Run:
stp tc-notify process 0
TC notification is enabled in the MSTP process.
After the stp tc-notify process 0 command is run, the current MSTP process notifies the MSTIs
in MSTP process 0 to update MAC entries and ARP entries after receiving a TC-BPDU. This
prevents services from being interrupted.
----End

After MSTP multi-process is configured, check whether the configurations take effect.
Prerequisite
All configurations of MSTP multi-process are complete.

Procedure
Step 1 Run the display stp [ process process-id ] [ instance instance-id ] [ interface interface-type
interface-number | vsi vsi-name pw pw-name | slot slot-id ] [ brief ] command to view spanning-
tree status and statistics.
----End
Example
Run the display stp command, and you can view the working mode of the spanning tree and
port priority configured in an MSTP process. For example:
<HUAWEI> display stp process 2 interface GigabitEthernet 1/0/2
----[CIST][Port2(GigabitEthernet1/0/2)][FORWARDING]----
Port Priority :128
Desg. Bridge/Port :32768.00e0-0c1f-4100 / 128.1
Port Stp Mode :MSTP
TC or TCN send :1
BPDU Sent :2
BPDU Received :76
7.4 Configuring MSTP Parameters on an Interface

MSTP implements RSTP rapid convergence. To achieve rapid convergence, you need to
configure proper MSTP parameters.

Before configuring basic MSTP parameters, familiarize yourself with the applicable
In some specific networks, MSTP parameters will affect the speed of network convergence.
Configuring proper MSTP parameters is required.
NOTE
The default parameters also can be used to complete MSTP rapid convergence. Therefore, the configuration
procedures and steps in this command task are all optional.
Before configuring MSTP parameters, complete the following task:

Data Preparation
To configure MSTP parameters, you need the following data.
No. Data
1 Network diameter
2 Hello time, forwarding delay time, maximum aging time, and timeout period for
waiting for BPDUs from the upstream (3 x hello time x time factor)
3 Maximum hop count in an MST region
4 Link type of a port
5 Whether to Rapid transition mechanism
6 Whether to transition to the RSTP mode
7 Maximum number of sent BPDUs
8 Whether a port needs to be configured as an edge port
9 Whether auto recovery needs to be configured for an edge port being shut down
10 Whether a port needs to clear statistics of the spanning tree
11 Whether an edge port needs to be configured as a BPDU filter
7.4.2 Configuring System Parameters

MSTP parameters that may affect network convergence include the network diameter, hello
time, and timeout period for waiting for BPDUs from the upstream (3 x hello time x time factor).
Configure proper MSTP parameters to implement rapid network convergence.
Procedure
Step 1 Run:
system-view

The MSTP process view is displayed.

NOTE
This step is needed only when you perform configurations in an MSTP process with a non-zero ID. If you
perform configurations in the MSTP process 0, skip is step.
Step 3 Run:
stp bridge-diameter diameter
The network diameter is configured.

By default, the network diameter is 7.
l RSTP uses a single spanning tree instance on the entire network, which cannot prevent the
performance from deteriorating when the network scale grows. Therefore, the network
diameter cannot be larger than 7.
l It is recommended that you run the stp bridge-diameter diameter command to set the
network diameter. Then, the switching device calculates the optimal Forward Delay period,
Hello time, and Max Age period based on the set network diameter.
Step 4 Run:
stp timer-factor factor
The timeout period for waiting for BPDUs from the upstream of a switching device is set.
By default, the timeout period of a switching device is 9 times as long as the Hello time.
Step 5 (Optional) If the current device is at the edge of a network, run both or either of the following
commands as needed:
l To configure all ports on the devices as edge ports, run:
stp edged-port default
By default, a port is a non-edge port.

After ports on a network edge device are configured as edge ports, the ports no longer
participate in spanning tree calculation. This speeds up network topology convergence and
improves network stability.
l To configure all ports on the devices as BPDU filter ports, run:
stp bpdu-filter default
By default, a port is a non-BPDU filter port.

After ports on a network edge device are configured as BPDU filter ports, the ports no longer
process or send BPDUs.
WARNING
After the stp bpdu-filter default and stp edged-port default commands are run in the system
view, all ports on the device no longer actively send BPDUs or negotiate with directly-connected
ports; instead, all the ports are in the Forwarding state. This may lead to a loop on the network,
causing broadcast storms. Exercise caution when running these commands.
Step 6 (Optional) To set the Forward Delay period, Hello time, and Max Age period, perform the
following operations:
l Run the stp timer forward-delay forward-delay command to set the Forward Delay period
for a switching device.
The default Forward Delay period of a switching device is 1500, in centiseconds.
l Run the stp timer hello hello-time command to set the Hello time for a switching device.
The default Hello time of a switching device is 200, in centiseconds.
l Run the stp timer max-age max-age command to set the Max Age period for a switching
device.
The default Max Age period of a switching device is 2000, in centiseconds.

NOTE
The values of the Hello time, Forward Delay period, and Max Age period must comply with the following
formulas. Otherwise, networking flapping occurs.
l 2 × (Forward Delay - 1.0 second) >= Max Age
l Max Age >= 2 × (Hello Time + 1.0 second)
Step 7 Run:
stp max-hops hop
The maximum hop count is set for the MST region.
By default, the maximum hop count of the MST region is 20.
Step 8 Run:
stp mcheck
MCheck is enabled.
On a switching device running MSTP, if an interface is connected to a device running STP, the
interface automatically transitions to the STP mode.
Enabling MCheck on the interface is required because the interface may fail to automatically
transition to the MSTP mode in the following situations:

l The switching device running STP transitions to the MSTP mode.
NOTE
If you run the stp mcheck command in the system view, the MCheck operation is performed on all the
interfaces.
----End
7.4.3 Configuring Port Parameters

Port parameters that may affect MSTP topology convergence include the link type and maximum
number of sent BPDUs. Configure proper port parameters to implement rapid topology
convergence.
Procedure
Step 1 Run:
system-view
Step 2 Run:

portswitch

NOTE

stp point-to-point { auto | force-false | force-true }
The link type is configured for a port.

By default, a port automatically determines whether to connect to a P2P link. The P2P link
supports rapid network convergence.
l If the Ethernet port works in full-duplex mode, the port is connected to a P2P link. In this
case, force-true can be configured to implement rapid network convergence.
l If the Ethernet port works in half-duplex mode, you can configure stp point-to-point force-
true to forcibly set the link type to P2P to implement rapid network convergence.
Step 5 Run:
stp mcheck
MCheck is enabled.
On a switching device running MSTP, if an interface is connected to a device running STP, the
interface automatically transitions to the STP mode.
Enabling MCheck on the interface is required because the interface may fail to automatically
transition to the MSTP mode in the following situations:
l The switching device running STP transitions to the MSTP mode.
Step 6 Run:
stp transmit-limit packet-number
The maximum number of BPDUs sent by a port within each Hello time is set.
By default, the maximum number of BPDUs that a port sends within each Hello time is 147.
stp edged-port enable
The port is configured as an edge port.

If a device port is connected to a terminal, you can run this command to configure the port as
an edge port.
By default, the port is a non-edge port.
If the current port has been configured as an edge port, the port is still be able to send BPDUs.
This may cause BPDUs to be sent to other networks, leading to network flapping. To prevent
this problem, run the stp bpdu-filter command to configure the edge port as a BPDU filter port
and disable the port from processing or sending BPDUs.

WARNING
After the stp bpdu-filter command is run on a port, the port no longer processes or sends BPDUs.
The port will not negotiate with the directly-connected port to establish an STP connection.
Therefore, exercise caution when running this command.
Step 8 Run:
quit
----End
Follow-up Procedure
When the topology of a spanning tree changes, the forwarding paths to associated VLANs are
changed. Then, ARP entries corresponding to those VLANs on the switching device need to be
updated. MSTP processes ARP entries in either fast or normal mode.
l In fast mode, ARP entries to be updated are directly deleted.
l In normal mode, ARP entries to be updated are rapidly aged.
The remaining lifetime of ARP entries to be updated is set to 0. The switching device rapidly
processes these aged entries. If the number of ARP aging probe attempts is not set to 0,
ARP implements aging probe for these ARP entries.
In either fast or normal mode, MAC entries are directly deleted.
You can run the stp converge { fast | normal } command in the system view to configure the
MSTP convergence mode.
By default, the MSTP convergence is configured as normal.
NOTE
The normal mode is recommended. If the fast mode is adopted, ARP entries will be frequently deleted,
causing the CPU usage on the MPU or LPU to reach 100%. As a result, network flapping frequently occurs.

After MSTP parameters are configured, check whether the configurations take effect.
Prerequisite
The configurations of MSTP parameters are complete.
Procedure
l Run the display stp [ instance instance-id ] [ interface { interface-type interface-
----End
Example
Run the display stp command, and you can view values of MSTP parameters, including the
hello time, forwarding delay time, maximum aging time, maximum hop count, and maximum

number of BPDUs allowed to be sent within each hello time on a port. You can also view whether
the link connected to the port is a P2P link. For example:
Port Priority :128
Port Cost(Dot1T ) :Config=100 / Active=100
Port Stp Mode :MSTP
BPDU Sent :0
BPDU Received :0
7.5 Configuring MSTP Protection Functions

MSTP protection functions are as follows, and you can configure one or more functions as
required.

Before configuring MSTP protection functions, familiarize yourself with the applicable
MSTP provides the following protection functions, as listed in Table 7-7.

Table 7-7 MSTP protection

Protection


delete MAC entries and ARP device receives within the given time exceeds
resources. number of times. Excessive TC-BPDUs are
for once after the timeout period expires. This
protects the switching device from frequently
deleting MAC entries and ARP entries, thus
avoiding over-burden.
Root Due to incorrect To address this issue, the root protection

protection configurations or malicious function can be configured to protect the root
attacks on the network, a bridge by preserving the role of the
root bridge may receive designated port. With this function, when the
BPDUs with a higher designated port receives RST BPDUs with a
priority. Consequently, the higher priority, the port enters the Discarding
legitimate root bridge is no state and does not forward the BPDUs. If the
longer able to serve as the port does not receive any RST BPDUs with a
root bridge, and the network higher priority for a certain period (double the
topology is illegitimately Forward Delay), the port transitions to the
traffic congestion.


Protection
Loop A root port or an alternate The loop protection function can be used to
protection port will age if link prevent such network loops. If the root port
congestion or a one-way link or alternate port cannot receive RST BPDUs
failure occurs. After the root from the upstream switching device, the root
port ages, a switching device port is blocked and the switching device
may re-select a root port notifies the NMS that the port enters the
incorrectly and after the Discarding state. The blocked port remains in
alternate port ages, the port the Blocked state and no longer forwards
enters the Forwarding state. packets. This prevents loops on the network.
Loops may occur in such a The root port restores the Forwarding state
situation. after new RST BPDUs are received.
Share-link In the scenario where a Share-link protection can address such a

protection switching device is dual- problem. This function forcibly changes the
homed to a network, when working mode of the local switching device
the share link of multiple to RSTP. Share-link protection needs to be
processes fails, loops may used together with root protection to avoid
occur. network loops.
NOTE
l After a device normally starts, there is a default MSTP process with the ID 0. MSTP configurations in
the system view and interface view both belong to this process.
l For more information about MSTP multi-process configuration, see 7.3 Configuring MSTP Multi-
process.
Before configuring MSTP protection functions on a switching device, complete the following
task:
NOTE
Configuring an edge port on the switching device before configuring BPDU protection.
Data Preparation
To configure MSTP protection functions on a switching device, you need the following data.
No. Data
1 Number of the port on which root protection is to be enabled
2 Number of the port on which loop protection is to be enabled

7.5.2 Configuring BPDU Protection on a Switching Device

After BPDU protection is enabled on a switching device, the switching device shuts down an
edge port if the edge port receives a BPDU, and notifies the NMS of the shutdown event.
Context
Edge ports are directly connected to user terminals and normally, the edge ports will not receive
BPDUs. Some attackers may send pseudo BPDUs to attach the switching device. If the edge
ports receive the BPDUs, the switching device automatically sets the edge ports as non-edge
ports and triggers new spanning tree calculation. Network flapping then occurs. BPDU
protection can be used to protect switching devices against network attacks.
NOTE
Do as follows on a switching device having an edge port:
Procedure
Step 1 Run:
system-view

NOTE
Step 3 Run:
stp bpdu-protection
BPDU protection is enabled on the switching device.

By default, BPDU protection is not enabled on the switching device.
----End
7.5.3 Configuring TC Protection on a Switching Device

After TC protection is enabled, you can set the number of times for an MSTP process to process
TC-BPDUs within a given time. TC protection avoids frequent deletion of MAC address entries
and ARP entries, thereby protecting switching devices.
Context
An attacker may send pseudo TC-BPDUs to attack switching devices. Switching devices receive
a large number of TC BPDUs in a short time and delete entries frequently, which burdens system
processing and degrades network stability.
TC protection is used to suppress TC-BPDUs. The number of times that TC-BPDUs are
processed by a switching device within a given time period is configurable. If the number of
TC-BPDUs that the switching device receives within a given time exceeds the specified

threshold, the switching device handles TC-BPDUs only for the specified number of times.
Excessive TC-BPDUs are processed by the switching device as a whole for once after the timer
(that is, the specified time period) expires. This protects the switching device from frequently
deleting MAC entries and ARP entries, thus avoiding over-burdened.
Procedure
Step 1 Run:
system-view

NOTE
Step 3 Run:
stp tc-protection
TC protection is enabled for the MSTP process.
By default, TC protection is not enabled on the switching device.
Step 4 Run:
stp tc-protection threshold threshold
The threshold of the number of times the MSTP process handles the received TC-BPDUs and
updates forwarding entries within a given time is set.
NOTE
The value of the given time is consistent with the MSTP Hello time set by using the stp timer hello hello-
time command.
----End
7.5.4 Configuring Root Protection on an Interface

The root protection function on a switching device protects a root bridge by preserving the role
of a designated port.
Context
Due to incorrect configurations or malicious attacks on the network, a root bridge may receive
BPDUs with a higher priority. Consequently, the legitimate root bridge is no longer able to serve
as the root bridge, and the network topology is illegitimately changed, triggering spanning tree
recalculation. This also may cause the traffic that should be transmitted over high-speed links
to be transmitted over low-speed links, leading to network congestion. The root protection
function on a switching device is used to protect the root bridge by preserving the role of the
designated port.

NOTE
Root protection is configured on a designated port. It takes effect only when being configured on the port
that functions as a designated port on all MSTIs. If root protection is configured on other types of ports, it
does not take effect.
Do as follows on a root bridge in an MST region:
Procedure
Step 1 Run:
system-view

Step 2 Run:

portswitch
NOTE

The port is bound to an MSTP process.
NOTE
This step is performed only when the interface needs to be bound to an MSTP process with a non-zero ID.
If the interface belongs to process 0, skip this step.
Step 5 Run:
stp root-protection
Root protection is configured on the switching device.

By default, root protection is disabled.
----End
7.5.5 Configuring Loop Protection on an Interface

The loop protection function suppresses the loops caused by link congestion.
Context
On a network running MSTP, a switching device maintains the root port status and status of
blocked ports by receiving BPDUs from an upstream switching device. If the switching device
cannot receive BPDUs from the upstream because of link congestion or unidirectional-link
failure, the switching device re-selects a root port. The original root port becomes a designated
port and the original blocked ports change to the Forwarding state. This may cause network
loops. To address such a problem, configure loop protection.

After loop protection is configured, if the root port or alternate port does not receive BPDUs
from the upstream switching device, the root port is blocked and the switching device notifies
the NMS that the port enters the Discarding state. The blocked port remains in the Blocked state
and no longer forwards packets. This prevents loops on the network. The root port restores the
Forwarding state after receiving new BPDUs.
NOTE
An alternate port is a backup port of a root port. If a switching device has an alternate port, you need to
configure loop protection on both the root port and the alternate port.
Do as follows on a root port and an alternate port on a switching device in an MST region:
Procedure
Step 1 Run:
system-view

Step 2 Run:

portswitch

NOTE

The port is bound to an MSTP process.

NOTE
This step is performed only when the interface needs to be bound to an MSTP process with a non-zero ID.
If the interface belongs to process 0, skip this step.
Step 5 Run:
stp loop-protection
Loop protection for the root port is configured on the switching device.
By default, loop protection is disabled.
----End
7.5.6 Configuring Share-Link Protection on a Switching Device

The share-link protection function on a switching device helps automatically transition to the
RSTP working mode. It can also be used together with root protection to avoid network loops.
Context
Share-link protection is used in the scenario where a switching device is dual homed to a network.

When a share link fails, share-link protection forcibly changes the working mode of a local
switching device to RSTP. This function can also be used together with root protection to avoid
network loops.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
stp link-share-protection
Share-link protection is enabled.
----End

After MSTP protection functions are configured, check whether the configurations take effect.
Prerequisite
All configurations of MSTP protection functions are complete.
Procedure
----End
Example
Run the display stp command, and you can view the BPDU protection status and configured
protection type on a switching device. For example:
-------[CIST Global Info][Mode MSTP]-------
BPDU-Protection :enabled
STP Converge Mode :Fast
Port Priority :128


Port Stp Mode :MSTP
BPDU Sent :43
BPDU Received :3
7.6 Configuring MSTP Interoperability Between Huawei

Devices and Non-Huawei Devices
To enable Huawei devices to interwork with non-Huawei devices, configure proper parameters
and functions, including the BPDU format, MSTP protocol packet format, and digest snooping
function, on the Huawei devices running MSTP.

Before configuring MSTP interoperability between Huawei devices and non-Huawei devices,
obtain the data required for the configuration. This will help you complete the configuration task
quickly and accurately.
On an MSTP network, inconsistent protocol packet formats and BPDU keys may lead to a
communication failure. Configuring proper MSTP parameters on Huawei devices ensures
interoperability between Huawei devices and non-Huawei devices.
Before configuring MSTP interoperability between Huawei devices and non-Huawei devices,
complete the following task:
Data Preparation
To configure MSTP interoperability between Huawei devices and non-Huawei devices, you
No. Data
1 BPDU format
2 MSTP protocol packet format

7.6.2 Configuring the BPDU Format on a Switching Device

To make a Huawei device interoperate with a non-Huawei device, set the BPDU format to Per
VLAN Spanning Tree (PVST).
Prerequisite
Basic VPLS functions have been configured before you can configure the BPDU format in the
PW template view.
Procedure
Step 1 Run:
system-view

Step 2 Enter the view to configure the BPDU format:
l Perform the following steps to enter the PW template view:
1. Run the vsi vsi-name [ auto | static ] command to create a VSI or enter the VSI view.
2. Run the pwsignal { bgp | ldp } command to configure a signaling mode for the VSI.
3. Run the vsi-id vsi-id command to set the VSI ID.
4. Run the peer peer-address [ negotiation-vc-id vc-id ] pw pw-name command to enter
the VSI-LDP-PW view.
l Run the interface interface-type interface-number command to enter the Ethernet interface
view. interface-type specifies the interface type. The interface types can be Ethernet, Eth-
Trunk, virtual Ethernet, and GigabitEthernet.
Step 3 Run:
stp bpdu-encapsulation { pvst | stp }
The BPDU format is configured on the switching device.

By default, the BPDU format is STP.
To make a Huawei device interoperate with a non-Huawei device, the PVST BPDU format needs
to be used.
----End
7.6.3 Configuring a Proposal/Agreement Mechanism

To enable Huawei Datacom devices to communicate with non-Huawei devices, configure a
proper rapid transition mechanism on Huawei devices according to the Proposal/Agreement
mechanism on non-Huawei devices.
Context
The rapid transition mechanism is also called the Proposal/Agreement mechanism. Switching
devices currently support the following modes:
l Enhanced mode: The current interface counts a root port when it computes the


connected to the upstream device as a root port and blocks all non-edge ports.
– The upstream device then sends an Agreement message to the downstream device. After
the downstream device receives the message, the root port transitions to the Forwarding
state.
– The downstream device then responds to the Proposal message with an Agreement
message. After receiving the message, the upstream device sets the port connected to
the downstream device as a designated port, and the designated port transitions to the
Forwarding state.
l Common mode: The current interface ignores the root port when it computes the
connected to the upstream device as a root port and blocks all non-edge ports. The root
port then transitions to the Forwarding state.
– The downstream device responds to the Proposal message with an Agreement message.
Forwarding state.
When Huawei Datacom devices are interworking with non-Huawei devices, select either mode
depending on the Proposal/Agreement mechanism on non-Huawei devices.
Procedure
Step 1 Run:
system-view
Step 2 Run:

The interface is bound to an MSTP process.
NOTE
This step binds an interface to an MSTP process with a non-zero ID. If the interface belongs to process 0,
skip this step.
Step 4 Run:
stp no-agreement-check
The common rapid transition mechanism is configured.
By default, the interface uses the enhanced rapid transition mechanism.
----End

7.6.4 Configuring the MSTP Protocol Packet Format on an Interface

MSTP protocol packets can be transmitted in auto, dot1s, or legacy mode. The default mode is
auto.
Context
MSTP protocol packets have two formats: dot1s (IEEE 802.1s standard packets) and legacy
(proprietary protocol packets). The auto mode is introduced to allow an interface to automatically
use the format of MSTP protocol packets sent from the remote interface. In this manner, the two
interfaces use the same MSTP protocol packet format.
Do as follows on a switching device in an MST region:
Procedure
Step 1 Run:
system-view
Step 2 Run:

portswitch
NOTE

NOTE
skip this step.
Step 5 Run:
stp compliance { auto | dot1s | legacy }
The MSTP protocol packet format is configured on the interface.
The auto mode is used by default.
NOTE
If the format of MSTP packets is set to dot1s on one end and legacy on the other end, the negotiation fails.
----End

7.6.5 Binding VLANs for an Interface to an MSTP Process

Non-Huawei devices do not recognize MSTP processes on Huawei datacom devices, which
causes a communication failure between them. To address this problem, bind VLANs for an
interface to MSTP processes. This allows Huawei devices to interoperate with non-Huawei
devices.
Context
If a Huawei device needs to interoperate with a non-Huawei device, the two devices cannot
properly communicate because the non-Huawei device cannot recognize the MSTP process on
the Huawei device. To address this problem, bind VLANs for interfaces to MSTP processes.
The non-Huawei device distinguishes MSTP processes based on associated VLAN IDs and
communicates with the Huawei device.
Do as follows on the device where VLANs for an interface need to be bound to MSTP processes:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
stp binding process process-id serve-vlan { vlan-id1 [ to vlan-id2 ] } &<1-10>
[ bpdu-vlan vlan-id ]
VLANs for the interface are bound to an MSTP process.

After VLANs for an interface are bound to an MSTP process, the interface determines the ID
carried in an MSTP packet to be sent based on whether BPDU-VLAN is set:
l If BPDU-VLAN is set, the MSTP packet carries the BPDU-VLAN ID but not the MSTP
process ID.
l If BPDU-VLAN is not set, the MSTP packet carries the MSTP process ID but not the BPDU-
VLAN ID.
NOTE
BPDU-VLAN must be a configured VLAN.
Before running the stp binding process serve-vlan command, ensure that the interface has
joined specified VLANs; otherwise, the command cannot take effect.
----End
7.6.6 Enabling the Digest Snooping Function

When a Huawei device is connected to a non-Huawei device, if the region names, revision
numbers, and VLAN-to-instance mappings configured on the two devices are consistent but the
BPDU keys are different, the two devices cannot communicate. To address this problem, enable
the digest snooping function on the Huawei device.

Context
Do as follows on a switching device in an MST region:
Procedure
Step 1 Run:
system-view

Step 2 Run:

NOTE
skip this step.
Step 4 Run:
stp config-digest-snoop
The digest snooping function is enabled.
----End

After MSTP parameters are configured for the interoperability between Huawei devices and
non-Huawei devices, check whether the configurations take effect.
Prerequisite
All the configurations for the interoperability between Huawei devices and non-Huawei devices
are complete.
Procedure
----End
Example
Run the display stp command, and you can view the spanning-tree working mode, BPDU format
and MSTP protocol packet format configured on the switching device, and configuration of the
digest snooping function. For example:


Port Priority :128
Config-digest-snoop:snooped=false
Port Stp Mode :MSTP
BPDU Sent :0
BPDU Received :0
7.7 Maintaining MSTP

MSTP maintenance includes resetting MSTP statistics.
7.7.1 Clearing MSTP Statistics

You can run the reset commands to reset MSTP statistics to 0.
Context
CAUTION
MSTP statistics cannot be restored after you clear them. Therefore, exercise caution when using
the reset commands.
After you confirm that MSTP statistics need to be cleared, run the following command in the
user view.
Procedure
Step 1 Run the reset stp [ interface interface-type interface-number ] statistics command to clear
spanning-tree statistics.
----End


This section shows typical usage scenarios of MSTP by describing networking requirements,
configuration roadmap, and data preparation, and provides related configuration files.
7.8.1 Example for Configuring Basic MSTP Functions

This example shows how to configure basic MSTP functions.
situation.
entries.
MSTP can be deployed to eliminate loops. MSTP blocks redundant links on a Layer 2 network
and trims the network into a loop-free tree.
As shown in Figure 7-9, to load balance traffic of VLANs 1 to 10 and traffic of VLANs 11 to
20, multiple MSTIs are created. MSTP defines a VLAN mapping table in which VLANs are
associated with spanning tree instances. In addition, MSTP divides a switching network into
multiple regions, each of which has multiple independent spanning tree instances.
As shown in Figure 7-9, RouterA, RouterB, SwitchC, and SwitchD all run MSTP.

Figure 7-9 Networking diagram of configuring basic MSTP functions
Network
RG1
RouterA RouterB
GE1/0/2 GE1/0/2
GE1/0/1 GE1/0/1
GE1/0/3 GE1/0/3
SwitchC GE1/0/2 GE1/0/2 SwitchD
GE1/0/1 GE1/0/1
PC1 PC2
VLAN1~10 MSTI1
VLAN11~20 MSTI2
MSTI1:
Root Bridge:RouterA
Blocked port
MSTI2:
Root Bridge:RouterB
Blocked port
1. Configure basic MSTP functions:

(1) Configure an MST region and create multiple MSTIs to implement load balancing.
(2) In the MST region, configure a primary root bridge and secondary root bridge for each
MSTI.
(3) Set path costs for ports to be blocked in each MSTI.
(4) Enable MSTP to eliminate loops, including:
l Enable MSTP globally.
l Enable MSTP on all the interfaces except the interfaces connected to terminals.
NOTE
MSTP is not required on the interfaces connected to terminals because these interfaces do not
need to participate in MSTP calculation.
By default, MSTP is enabled on a Layer 2 interface but not enabled on a Layer 3 interface.
2. Configure MSTP protection functions, for example, configure root protection on a
designated port of a root bridge in each MSTI.
3. Configure the Layer 2 forwarding function on devices.
Data Preparation
l Region name RG1
l MSTIs, MSTI 1 and MSTI 2
l GE interface numbers
l Primary and secondary root bridges of MSTI 1 (RouterA and RouterB respectively) and
primary and secondary root bridges of MSTI 2 (RouterB and RouterA respectively)
l Path costs of the ports to be blocked (20000)
l VLAN IDs (1 to 20)
l VLAN to which PC1 belongs (VLAN 10) and VLAN to which PC2 belongs (VLAN 20)
Procedure
Step 1 Configure basic MSTP functions.
1. Add RouterA, RouterB, SwitchC, and SwitchD to MST region RG1, and create two MSTIs,
MSTI 1 and MSTI 2.
# Add RouterA to RG1.
[RouterA] stp region-configuration
[RouterA-mst-region] region-name RG1
[RouterA-mst-region] instance 1 vlan 1 to 10
[RouterA-mst-region] instance 2 vlan 11 to 20
[RouterA-mst-region] active region-configuration
[RouterA-mst-region] quit
# Add RouterB to RG1.

[RouterB] stp region-configuration
[RouterB-mst-region] region-name RG1
[RouterB-mst-region] instance 1 vlan 1 to 10
[RouterB-mst-region] instance 2 vlan 11 to 20
[RouterB-mst-region] active region-configuration
[RouterB-mst-region] quit

# Add SwitchC to RG1.

[SwitchC] stp region-configuration
[SwitchC-mst-region] region-name RG1
[SwitchC-mst-region] instance 1 vlan 1 to 10
[SwitchC-mst-region] instance 2 vlan 11 to 20
[SwitchC-mst-region] active region-configuration
[SwitchC-mst-region] quit
# Add SwitchD to RG1.

[HUAWEI] sysname SwitchD
[SwitchD] stp region-configuration
[SwitchD-mst-region] region-name RG1
[SwitchD-mst-region] instance 1 vlan 1 to 10
[SwitchD-mst-region] instance 2 vlan 11 to 20
[SwitchD-mst-region] active region-configuration
[SwitchD-mst-region] quit
2. In RG1, configure primary and secondary root bridges for MSTI 1 and MSTI 2.
l Configure primary and secondary root bridges for MSTI 1.
# Configure RouterA as a primary root bridge of MSTI 1.
[RouterA] stp instance 1 root primary
# Configure RouterB as a secondary root bridge of MSTI 1.

[RouterB] stp instance 1 root secondary
l Configure primary and secondary root bridges for MSTI 2.

# Configure RouterB as a primary root bridge of MSTI 2.
[RouterB] stp instance 2 root primary
# Configure RouterA as a secondary root bridge of MSTI 2.

[RouterA] stp instance 2 root secondary
3. Set the path costs of the ports to be blocked in MSTI 1 and MSTI 2 to be larger than the
default value.
NOTE
l Different calculation methods define different path costs. Use the Huawei proprietary calculation
method as an example to set the path costs of the ports to be blocked in MSTI 1 and MSTI 2 to
20000.
l All switching devices on a network must use the same calculation for path costs.
method.
method.
and set the path cost of GE 1/0/2 in MSTI 2 to 20000.
[SwitchC-GigabitEthernet1/0/2] stp instance 2 cost 20000
method and set the path cost of GE 1/0/2 in MSTI 1 to 20000.
[SwitchD] interface gigabitethernet 1/0/2

[SwitchD-GigabitEthernet1/0/2] stp instance 1 cost 20000

[SwitchD-GigabitEthernet1/0/2] quit
4. Enable MSTP to eliminate loops.

l Disable MSTP on interfaces connected to PCs.
# Disable MSTP on GE 1/0/1 of SwitchC.
# Disable MSTP on GE 1/0/1 of SwitchD.

[SwitchD-GigabitEthernet1/0/1] stp disable
l Enable MSTP globally.

# Enable MSTP on RouterA.
# Enable MSTP on RouterB.

[RouterB] stp enable
# Enable MSTP on SwitchC.

# Enable MSTP on SwitchD.

[SwitchD] stp enable
l Enable MSTP on all the interfaces except the interfaces connected to terminals.
# Enable MSTP on GE 1/0/1 of RouterA.
# Enable MSTP on GE 1/0/2 of RouterA.

# Enable MSTP on GE 1/0/1 of RouterB.

[RouterB-GigabitEthernet1/0/1] stp enable
# Enable MSTP on GE 1/0/2 of RouterB.

[RouterB-GigabitEthernet1/0/2] stp enable
# Enable MSTP on GE 1/0/2 of SwitchC.

# Enable MSTP on GE 1/0/3 of SwitchC.


# Enable MSTP on GE 1/0/2 of SwitchD.

[SwitchD-GigabitEthernet1/0/2] stp enable
# Enable MSTP on GE 1/0/3 of SwitchD.

[SwitchD-GigabitEthernet1/0/3] stp enable
Step 2 Configure MSTP protection functions, for example, configure root protection on a designated
port of a root bridge in each MSTI.
# Enable root protection on GE 1/0/1 of RouterA.
# Enable root protection on GE 1/0/1 of RouterB.

[RouterB-GigabitEthernet1/0/1] stp root-protection
Step 3 Configure the Layer 2 forwarding function on devices in the ring.

l Create VLANs 1 to 20 on RouterA, RouterB, SwitchC, and SwitchD.
# Create VLANs 1 to 20 on RouterA.
# Create VLANs 1 to 20 on RouterB.

# Create VLANs 1 to 20 on SwitchC.

[SwitchC] vlan batch 1 to 20
# Create VLANs 1 to 20 on SwitchD.

[SwitchD] vlan batch 1 to 20
l Add interfaces on the switching devices in the ring to VLANs.

# Add GE 1/0/1 on RouterA to VLANs.
[RouterA-GigabitEthernet1/0/1] port trunk allow-pass vlan 1 to 20
# Add GE 1/0/2 on RouterA to VLANs.

# Add GE 1/0/1 on RouterB to VLANs.

[RouterB-GigabitEthernet1/0/1] port trunk allow-pass vlan 1 to 20
# Add GE 1/0/2 on RouterB to VLANs.

# Add GE 1/0/2 on SwitchC to VLANs.

[SwitchC-GigabitEthernet1/0/2] port trunk allow-pass vlan 1 to 20

# Add GE 1/0/3 on SwitchC to VLANs.

[SwitchC-GigabitEthernet1/0/3] port trunk allow-pass vlan 1 to 20
# Add GE 1/0/2 on SwitchD to VLANs.

[SwitchD] interface gigabitEthernet 1/0/2
[SwitchD-GigabitEthernet1/0/2] port trunk allow-pass vlan 1 to 20
# Add GE 1/0/3 on SwitchD to VLANs.

[SwitchD-GigabitEthernet1/0/3] port trunk allow-pass vlan 1 to 20

After completing the previous configurations, run the following commands to verify the
configurations.
<RouterA> display stp brief
In MSTI 1, RouterA is a root bridge and thus GE 1/0/2 and GE 1/0/1 on RouterA are designated
ports. In MSTI 2, GE 1/0/1 on Switch A is a designated port and GE 1/0/2 is a root port.
# Run the display stp brief command on RouterB. The displayed information is as follows:
[RouterB] display stp brief
In MSTI 2, RouterB is a root bridge and thus GE 1/0/1 and GE 1/0/2 on RouterB are designated
ports. In MSTI 1, GE 1/0/1 of RouterB is a designated port and GE 1/0/2 is a root port.
# Run the display stp interface brief command on SwitchC. The displayed information is as
follows:
2 GigabitEthernet1/0/2 ALTE DISCARDING NONE
# Run the display stp interface brief command on SwitchD. The displayed information is as
follows:

[SwitchD] display stp interface gigabitethernet 1/0/3 brief

[SwitchD] display stp interface gigabitethernet 1/0/2 brief
GE 1/0/3 on SwitchD is a root port in both MSTI 1 and MSTI 2. GE 1/0/2 on SwitchD is blocked
in MSTI 1 but is calculated to be a designated port in MSTI 2.
----End
Configuration Files
stp root-protection
#
sysname
RouterA
#
vlan batch 1 to
20
#
stp instance 1 root
primary
stp instance 2 root
secondary
legacy
stp enable
#
stp region-
configuration
region-name
RG1
instance 1 vlan 1 to
10
20
active region-
configuration
#
interface
undo shutdown
portswitch
port trunk allow-pass vlan 1 to
20
stp root-
protection
#
interface
undo shutdown
portswitch
#
return

#
sysname
RouterB
#

vlan batch 1 to
20
#
stp instance 1 root
secondary
stp instance 2 root
primary
legacy
stp enable
#
stp region-
configuration
region-name
RG1
10
20
active region-
configuration
#
interface
undo shutdown
portswitch
20
stp root-
protection
#
interface
undo shutdown
portswitch
20
#
return

#
sysname
SwitchC
#
vlan batch 1 to
20
#
legacy
stp
enable
#
undo http server
enable
#
stp region-
configuration
region-name
RG1
10
20
active region-
configuration
#
interface

stp
disable
#
interface
20
stp instance 2 cost
20000
#
interface
20
#
return
l Configuration file of SwitchD

#
sysname
SwitchD
#
vlan batch 1 to
20
#
legacy
stp
enable
#
undo http server
enable
#
stp region-
configuration
region-name
RG1
10
20
#
interface
stp
disable
#
interface
20
stp instance 1 cost
20000
#
interface
20
#
return
7.8.2 Example for Configuring MSTP Multi-process

After MSTP multi-process is enabled, each MSTP process can manage some interfaces. Layer
2 interfaces are divided and managed by multiple MSTP processes. Each MSTP process runs
the standard MSTP. With the MSTP multi-process mechanism, spanning trees of different
processes are calculated independently and do not affect each other.

UPEs construct a ring at the aggregation layer. These UPEs are enabled with MSTP and belong
to the same MST region. Load balancing between different VLANs is carried out by creating
multiple MSTIs.
UPEs are respectively connected to two DSLAM rings at the access layer. The two rings need
to be independent of each other and use different spanning trees. This ensures that topology
change of one ring does not affect the other.
As shown in Figure 7-10, UPE1, UPE2, UPE3, and UPE4 construct a ring at the aggregation
layer. The UPEs are enabled with MSTP and belong to the same MST region named RG1. In
RG1, UPE4 is a CIST root and also a regional root of MSTI 1. UPE3 is a regional root in MSTI
2. Load balancing between traffic from different VLANs is carried out in the entire MST region.
UPE1 and UPE2 are connected to two DSLAM rings at the access layer. The two rings need to
be independent of each other.
In addition, to protect devices, UPE1 and UPE2 need to suppress TC-BPDUs.
NOTE
In the ring of MSTP multi-process, blocking the interface directly connected to the root protection-enabled
designated port is not recommended.

Figure 7-10 Networking for MSTP multi-process
Core
MPLS/IP Core
GE1/0/1 GE1/0/1 UPE3

UPE 4 GE2/0/1
Aggregation
GE2/0/1
MSTP
GE2/0/1 GE2/0/1
GE1/0/3 GE1/0/3
UPE1 UPE2
GE1/0/1 GE1/0/2 GE1/0/2 GE1/0/1
STP/RSTP
DSLAM DSLAM Access
DSLAM DSLAM
1. Configure basic MSTP functions, including:

(1) Add UPEs to an MST region and create multiple MSTIs to implement load balancing.
(2) Configure a regional root.
2. Configure MSTP multi-process, including:
(1) Create multiple MSTP processes and add interfaces to relevant processes.
(2) Configure a shared link.
3. Configure MSTP protection functions, including:
l Configure priorities of MSTP processes and enable root protection.
l Configure TC notification and protection.

Data Preparation
l Name of the MST region (RG1) and names of MSTIs (MSTI 1 and MSTI 2)
l VLAN IDs on UPEs (1 to 20)
l IDs of MSTP processes
Procedure
Step 1 Configure basic MSTP functions.
1. Add UPEs 1 to 4 to MST region RG1.
# Configure UPE1.
[UPE1] stp region-configuration
[UPE1-mst-region] region-name RG1
[UPE1-mst-region] instance 1 vlan 1 to 10
[UPE1-mst-region] active region-configuration
[UPE1-mst-region] quit
# Configure UPE2.
# Configure UPE3.
# Configure UPE4.
2. Configure a CIST root and a regional root in each MSTI.

# Set the priority of UPE4 to 0 in MSTI0 and MSTI 1 to ensure that UPE4 functions as a
CIST root and also a regional root of MSTI 1 in RG1.
[UPE4] stp instance 0 priority 0
# Set the priority of UPE3 to 0 in MSTI 2 to ensure that UPE3 functions as a regional root
of MSTI 2 in RG1.

3. Enable MSTP.
# Configure UPE1.
[UPE1] stp enable
# Configure UPE2.
[UPE2] stp enable
# Configure UPE3.
[UPE3] stp enable
# Configure UPE4.
[UPE4] stp enable
Step 2 Configure MSTP multi-process.

1. Create multiple MSTP processes and add interfaces to relevant processes.
# Configure UPE1.
[UPE1] stp process 1
[UPE1-stp-process-1] stp enable
[UPE1-stp-process-1] quit
# Configure UPE2.
# Add GE 1/0/1 and GE 1/0/2 on UPE1 to VLANs.

[UPE1-GigabitEthernet1/0/1] portswitch
[UPE1-GigabitEthernet1/0/1] stp binding process 1
# Add GE 1/0/1 and GE 1/0/2 on UPE2 to VLANs.

2. Configure a shared link.

# Configure UPE1.
[UPE1-GigabitEthernet1/0/1] stp binding process 1 to 2 link-share
# Configure UPE2.


[UPE2-GigabitEthernet1/0/1] stp binding process 1 to 2 link-share
Step 3 Configure MSTP protection functions.

# Configure UPE1.
[UPE1-stp-process-1] stp instance 0 root primary
[UPE1-stp-process-2] stp instance 0 root secondary
[UPE1-GigabitEthernet1/0/2] stp root-protection
# Configure UPE2.
[UPE2-stp-process-1] stp instance 0 root secondary
[UPE2-stp-process-2] stp instance 0 root primary
[UPE2-GigabitEthernet1/0/2] stp root-protection
NOTE
l Alternatively, you can run the stp [ instance instance-id ] priority priority command to configure
priorities for MSTP processes. Ensure that the MSTP process on UPE1 has the highest priority and
the MSTP process on UPE2 has the second highest priority.
l Root protection must be configured on a designated port of the MSTP process with the second
highest priority.
l Configure TC notification and suppression of TC-BPDUs for MSTP multi-process.
# Configure UPE1.
[UPE1] stp tc-protection
[UPE1-stp-process-1] stp tc-notify process 0
[UPE1-stp-process-1] stp tc-protection
# Configure UPE2.
[UPE2] stp tc-protection
Step 4 Create VLANs on UPEs and add UPE interfaces to VLANs.

# Create VLANs 1 to 20 on UPE1 and add GE 2/0/1 and GE 1/0/3 to the VLANs.
[UPE1] vlan batch 1 to 20

[UPE1-GigabitEthernet2/0/1] port trunk allow-pass vlan 1 to 20


l Run the display stp interface brief command on UPE1, and you can view the following
information:
# GE 2/0/1 is a root port in the CIST and MSTI 1 and a designated port in MSTI 2.
[UPE1] display stp interface gigabitethernet 2/0/1 brief
# GE 1/0/3 is a designated port in the CIST and MSTI 1 and a root port in MSTI 2.
# GE 1/0/1 is a designated port in the CIST of MSTP process 1.

[UPE1] display stp process 1 interface gigabitethernet 1/0/1 brief

information:
0 GigabitEthernet1/0/3 ROOT DISCARDING NONE
1 GigabitEthernet1/0/3 ROOT DISCARDING NONE


information:
# GE 1/0/1 is a designated port in the CIST and both MSTI 1 and MSTI 2.


information:
# GE 1/0/1 is a designated port in the CIST and both MSTI 1 and MSTI 2.
----End
Configuration Files
Only the configuration files of the UPEs are listed.

#
sysname UPE1
#
vlan batch 1 to 20
#
stp tc-protection
stp enable
#
region-name RG1
instance 1 vlan 1 to 10
#
stp process 1
stp instance 0 root primary
stp tc-protection
stp enable
stp converge normal
stp process 2
stp instance 0 root secondary
stp tc-protection
stp enable
stp converge normal
#
undo shutdown
portswitch
stp binding process 1
#
interface GigabiEthernet1/0/2
undo shutdown
portswitch
stp root-protection

#
undo shutdown
portswitch
stp binding process 1 to 2 link-share
#
undo shutdown
portswitch
#
return

#
sysname UPE2
#
vlan batch 1 to 20
#
stp tc-protection
stp enable
#
region-name RG1
#
stp process 1
stp tc-protection
stp enable
stp converge normal
stp process 2
stp tc-protection
stp enable
stp converge normal
#
undo shutdown
portswitch
#
undo shutdown
portswitch
stp root-protection
#
undo shutdown
portswitch
stp binding process 1 to 2 link-share
#
undo shutdown
portswitch
#
return

#
sysname UPE3
#
vlan batch 1 to 20
#
stp instance 2 priority 0
stp enable
#
region-name RG1
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return

#
sysname UPE4
#
vlan batch 1 to 20
#
stp enable
#
region-name RG1
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return
7.8.3 Example for Configuring MSTP Multi-process for Layer 2

Single-Access Rings and Layer 2 Multi-Access Rings
MSTP multi-process enables different Layer 2 access rings to carry different services.
On the networking with both Layer 2 single-access rings and multi-access rings deployed,
switching devices carry both Layer 2 and Layer 3 services. To enable different rings to carry
different services, deploy MSTP multi-process. Spanning trees of different processes are
calculated independently and do not affect each other.

As shown in Figure 7-11, both Layer 2 single-access rings and dual-access rings are deployed,
and routers carry both Layer 2 and Layer 3 services. In this networking, two routers connected
to dual-access rings are also connected to a single-access ring each. Ring 1 uses Router A as an
MSTP root bridge. Ring 2 uses Router B as an MSTP root bridge. Ring 3 uses Router A as an
MSTP root bridge.
Routers A, B, and C construct a VPLS network. Sub-interfaces are configured on the ring access
interfaces on Router A and Router B and are bound to VSIs for access to the rings.
NOTE
In the ring of MSTP multi-process, blocking the interface directly connected to the root protection-enabled
designated port is not recommended.
For detailed configurations of VPLS, see the HUAWEI NetEngine80E/40E Router

Configuration Guide - VPN.
Figure 7-11 Networking for MSTP multi-process for Layer 2 single-access rings and Layer 2
multi-access rings
RouterC
GE1/1/0
GE1/1/0
PE1 PE2
RouterA RouterB
CE CE
GE1/0/10 GE1/0/0 GE1/0/10
GE1/0/0
GE1/0/11 GE1/0/11
GE1/0/7 GE1/0/7
Ring1 Ring2
CE CE
Ring3
Instance 1:VLAN1~100 Instance 3:VLAN1~100
Process 1 Process 3
CE CE
Instance 2:VLAN101~200
Process 2
1. Configure basic MSTP functions, create multiple MSTP processes, add devices to MST
regions, and create MSTIs.
NOTE
l Each ring can belong to only one region.

l Each CE can join only one ring.
2. Add interfaces to MSTP processes and configure a share link.

3. Configure MSTP protection functions, including:

l Configure share-link protection.
Data Preparation
l Names of MST region (RG1, RG2, and RG3) and names of MSTIs (MSTI 1, MSTI 2, and
MSTI 3)
l VLAN IDs (1 to 200)
l IDs of MSTP processes
Procedure
Step 1 Configure basic MSTP functions, create multiple MSTP processes, add devices to MST regions,
and create MSTIs.
# Configure MSTP processes 1 and 2 on Router A.
[RouterA] stp process 1
[RouterA-stp-process-1] stp region-configuration
[RouterA-stp-process-1-region] region-name RG1
[RouterA-stp-process-1-region] instance 1 vlan 1 to 100
[RouterA-stp-process-1-region] active region-configuration
[RouterA-stp-process-1-region] quit
[RouterA-stp-process-1] quit
[RouterA-stp-process-2] stp region-configuration
[RouterA-stp-process-2-region] region-name RG2
[RouterA-stp-process-2-region] instance 2 vlan 101 to 200
[RouterA-stp-process-2-region] active region-configuration
[RouterA-stp-process-2-region] quit
# Configure MSTP processes 2 and 3 on Router B.

[RouterB] stp process 2
[RouterB-stp-process-2] stp region-configuration
[RouterB-stp-process-2-region] region-name RG2
[RouterB-stp-process-2-region] instance 2 vlan 101 to 200
[RouterB-stp-process-2-region] active region-configuration
[RouterB-stp-process-2-region] quit
[RouterB-stp-process-2] quit
[RouterB-stp-process-3] stp region-configuration
[RouterB-stp-process-3-region] region-name RG3
[RouterB-stp-process-3-region] instance 3 vlan 1 to 100
[RouterB-stp-process-3-region] active region-configuration
[RouterB-stp-process-3-region] quit
# Enable MSTP on Router A.

# Enable MSTP on Router B.

[RouterB] stp enable

Step 2 Add interfaces to MSTP processes and configure a share link.

1. Add interfaces to MSTP processes.
[RouterA-GigabitEthernet1/0/10] stp binding process 1
[RouterB-GigabitEthernet1/0/10] stp binding process 3
NOTE
If the interface added to the MSTP process has sub-interfaces configured with features other than
MSTP such as VPLS, run the stp vpls-subinterface enable command on the interface. The interface
then notifies its sub-interfaces to update MAC entries and ARP entries after receiving a TC-BPDU.
This ensures non-stop service transmission. In addition, root protection needs to be configured on
the interface.
2. Configure a share link.
[RouterA] interface gigabitethernet1/0/0
[RouterA-GigabitEthernet1/0/0] stp binding process 2 link-share
[RouterB] interface gigabitethernet1/0/0
[RouterB-GigabitEthernet1/0/0] stp binding process 2 link-share
3. Enable the MSTP function for MSTP multi-process.

[RouterA-stp-process-1] stp enable
[RouterA-stp-process-2] stp enable

[RouterB-stp-process-3] stp enable
[RouterB-stp-process-2] stp enable
Step 3 Configure MSTP protection functions.

[RouterA-stp-process-1] stp instance 0 root primary
[RouterB-stp-process-3] stp instance 0 root primary
[RouterB-stp-process-3] stp instance 3 root primary
[RouterB-stp-process-2] stp instance 0 root secondary
[RouterB-stp-process-2] stp instance 2 root secondary
[RouterB-GigabitEthernet1/0/7] stp root-protection
NOTE
l In each ring, the priority of the MSTP process on the downstream CE must be lower than the priority
of the MSTP process on the router.
l For Router A and Router B on the dual-access ring, you are recommended to configure them as
the primary root bridges of different MSTIs.
l A Layer 3 VPN can be bound to a primary root bridge but cannot be bound to a secondary root
bridge.
l Configure share-link protection.
[RouterA-stp-process-2] stp link-share-protection
[RouterB-stp-process-2] stp link-share-protection
Step 4 Create VLANs and add interfaces to the VLANs.

# Create VLANs 1 to 200 on Router A. Add GE 1/0/10 and GE 1/0/11 to VLANs 1 to 100, and
add GE 1/0/0 and GE 1/0/7 to VLANs 101 to 200.


# Create VLANs 1 to 200 on Router B. Add GE 1/0/10 and GE 1/0/11 to VLANs 1 to 100, and
add GE 1/0/0 and GE 1/0/7 to VLANs 101 to 200.

l Run the display stp interface brief command on Router A, and you can view the following
information:
[RouterA] display stp process 1 interface giabitethernet 1/0/10 brief

[RouterA] display stp process 2 interface giabitethernet 1/0/7 brief
l Run the display stp interface brief command on Router B, and you can view the following
information:
[RouterB] display stp process 3 interface giabitethernet 1/0/10 brief

[RouterB] display stp process 2 interface giabitethernet 1/0/7 brief
----End
Configuration Files
Only the MSTP-related configuration files are listed.
#
sysname RouterA
#

vlan batch 1 to 200

#
stp enable
stp converge normal
#
stp process 1
stp enable
stp converge normal
region-name RG1
stp process 2
stp enable
stp converge normal
region-name RG2
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
stp root-protection
#
undo shutdown
portswitch
stp binding process 2 link-share
#
return
#
sysname RouterB
#
vlan batch 1 to 200
#
stp enable
stp converge normal
#
stp process 2
stp enable
stp converge normal
region-name RG2

stp process 3
stp enable
stp converge normal
region-name RG3
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
stp root-protection
#
undo shutdown
portswitch
stp binding process 2 link-share
#
return
7.8.4 Example for Configuring E-STP - Inter-AS Option A (Martini

Mode)
When configuring STP over PW in inter-AS Martini VPLS OptionA, you need to configure
service VSIs in ASs, and create Layer 3 sub-interfaces between ASs to access the VSIs. In
addition, in the same AS, you need to configure the management VSI (mVSI) on two ASBRs
and enable STP on the mPW; between ASs, you need to enable STP on the inter-AS Layer 3
sub-interfaces.
Figure 7-12 shows the networking of inter-AS Option A in Martini mode. This type of
networking has the following features:
l Each PE is dual-homed to ASBRs, and links are backed up between ASs.

l A VPLS network in Martini mode is configured between each PE and each ASBR, and the
ASBR regards the inter-AS peer ASBR as its own CE.
This type of networking has the following problems:
l Each PE receives two copies of traffic sent by the peer PE.

l A loop may exist among ASBR1, ASBR2, ASBR3, and ASBR4.
You can adopt the following solutions to address the preceding problems:

You can configure a mPW between intra-AS ASBRs and enable Spanning Tree Protocol (STP)
on the mPW and the inter-AS Layer 3 main interfaces. Then, you can set STP priorities and cost
values to configure ASBR3 as the root bridge, ASBR4 as the backup root bridge, and the inter-
AS interface on ASBR2 to be blocked. In addition, the block of the inter-AS interface causes
the block of the VPLS services that are bound to Layer 3 sub-interfaces. In this case, the traffic
from CE1 passes along the path PE1-ASBR1-ASBR3-PE2 to reach CE2. This prevents the traffic
from being doubled or forming a loop.
Figure 7-12 Networking diagram of configuring E-STP - inter-AS Option A (Martini mode)
ASBR1 ASBR3
MPLS Backbone1 2 GE1/0/0
MPLS Backbone 2
GE1/0/0 2 PO
GE1/0/0.1 GE1/0/0.1 S3
/0/
/0 0/0 2
GE2/0/0 GE2/0/0 2 0
/
PE1 S1/0 OS3 STP PO
PO P S1 PE2
PW loop PW /0/
0
tunnel tunnel
PO POS 0
3/0/ /0
S2
/0/
3/0
/0 2 GE2/0/0 GE2/0/0 2
PO S
S2/0
0 5 GE1/0/0 GE1/0/0 5 PO
GE3/0/0.1 GE3/0/0.l
GE1/0/0.1 GE1/0/0.1
ASBR2 ASBR4
GE1/0/0 GE1/0/0
2 5 STP cost Blocked point

CE1 CE2

PE1 POS1/0/0: 100.1.1.1/24 PE2 POS1/0/0: 100.5.1.2/24
POS2/0/0: 100.1.2.1/24 POS2/0/0: 100.5.2.2/24
Loopback1: 1.1.1.1/32 Loopback1: 6.6.6.6/32
ASBR1 GE1/0/0: -- ASBR2 GE1/0/0: --
GE2/0/0: 100.8.1.1/24 GE2/0/0: 100.8.1.2/24
POS3/0/0: 100.1.1.2/24 POS3/0/0: 100.1.2.2/24
ASBR3 GE1/0/0: -- ASBR4 GE1/0/0: --
GE2/0/0: 100.9.1.1/24 GE2/0/0: 100.9.1.1/24
POS3/0/0: 100.5.1.1/24 POS3/0/0: 100.5.2.1/24
CE1 GE1/0/0: 10.1.1.1/24 CE2 GE1/0/0: 10.1.1.2/24
1. Run an IGP protocol on the backbone network to realize device connectivity within the
same AS.

2. Configure the basic MPLS capability on the MPLS network, including the following tasks:
l Set up dynamic LSPs between the PE and two ASBRs in the same AS.
l Set up a dynamic LSP between the two ASBRs in the same AS.
Set up the remote LDP session if the indirect connection(s) are established between the PE
and ASBRs or between ASBRs.
3. Establish VPLS connections between the PE and ASBRs in the same AS, including the
following tasks:
l Create service VSIs on the PE and two ASBRs in the same AS. These service VSIs are
used to exchange service packets.
l Create the mVSI on the two ASBRs in the same AS. The mVSI is used to send STP
packets through the mPW.
4. Configure STP, including the following tasks:
l Enable STP on the mPW of the ASBRs.
l Enable STP on the inter-AS physical link.
Configure relevant STP priorities to ensure that ASBR3 functions as the root bridge, and
ASBR4 as the backup root bridge.
Data Preparation
l Data for configuring OSPF
l IP addresses of remote peers
l MPLS LSR IDs of PEs and ASBRs
l VSI IDs
Procedure
Step 1 Assign IP addresses to the interfaces on the backbone network. The configuration details are not
mentioned here.
Step 2 Configure an IGP protocol on the backbone network. In the configuration example, OSPF is
configured. The configuration details are not mentioned here.
Step 3 Enable MPLS and configure LDP LSPs.
Configure the basic MPLS capability on the MPLS backbone network, and establish dynamic
LDP LSPs between the PE and ASBRs in the same AS.
Take ASBR1 as an example:
<ASBR1> display mpls ldp session
------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Step 4 Enable MPLS L2VPN on the PE and the ASBRs.

# Configure PE1.
[PE1] mpls l2vpn
# Configure ASBR1.
[ASBR1] mpls l2vpn
# Configure ASBR2.
[ASBR2] mpls l2vpn
The configurations of PE2, ASBR3, and ASBR4 are the same and not mentioned here.
Step 5 Configuring VPLS.
1. Configure the mVSI on the four NPEs, and establish the peer relationships between ASBR1
and ASBR2, and between ASBR3 and ASBR4.
# Configure ASBR1.
[ASBR1] vsi m1 static
[ASBR1-vsi-m1] pwsignal ldp
[ASBR1-vsi-m1-ldp] vsi-id 100
[ASBR1-vsi-m1-ldp] peer 3.3.3.3
[ASBR1-vsi-m1-ldp] quit
[ASBR1-vsi-m1] admin-vsi
[ASBR1-vsi-m1] quit
# Configure ASBR2.
[ASBR2-vsi-m1] quit
# Configure ASBR3.
[ASBR3-vsi-m1] quit
# Configure ASBR4.
[ASBR1-vsi-m1] quit
2. On PEs and ASBRs, configure service VSIs and bind the service VSIs to relevant interfaces.
# Configure PE1.
[PE1] vsi s1 static
[PE1-vsi-s1] pwsignal ldp
[PE1-vsi-s1-ldp] vsi-id 10
[PE1-vsi-s1-ldp] peer 2.2.2.2
[PE1-vsi-s1-ldp] quit
[PE1-vsi-s1] quit
[PE1-GigabitEthernet3/0/0.1] shutdown

[PE1-GigabitEthernet3/0/0.1] l2 binding vsi s1

# Configure ASBR1.
[ASBR1] vsi s1 static
[ASBR1-vsi-s1] pwsignal ldp
[ASBR1-vsi-s1-ldp] vsi-id 10
[ASBR1-vsi-s1-ldp] peer 1.1.1.1
[ASBR1-vsi-s1-ldp] quit
[ASBR1-vsi-s1] quit
[ASBR1] interface gigabitethernet 1/0/0
[ASBR1-GigabitEthernet1/0/0] undo shutdown
[ASBR1-GigabitEthernet1/0/0] quit
[ASBR1] interface gigabitethernet 1/0/0.1
[ASBR1-GigabitEthernet1/0/0.1] shutdown
[ASBR1-GigabitEthernet1/0/0.1] vlan-type dot1q 10
[ASBR1-GigabitEthernet1/0/0.1] l2 binding vsi s1
[ASBR1-GigabitEthernet1/0/0.1] undo shutdown
[ASBR1-GigabitEthernet1/0/0.1] quit
# Configure ASBR2.
[ASBR2-vsi-s1] quit
# Configure PE2.
[PE2] vsi s1 static
[PE2-vsi-s1] quit
# Configure ASBR3.
[ASBR3-vsi-s1] quit


# Configure ASBR4.
[ASBR4-vsi-s1] quit
Step 6 Enable STP.

Enable STP on the four PEs.
# Configure the Multiple Spanning Tree (MST) region of ASBR1, and then activate the MST
region configuration. Because the four ASBRs have the same MST region configurations, take
ASBR1 as an example.
[ASBR1] stp enable
[ASBR1] stp region-configuration
[ASBR1-mst-region] region-name RG1
[ASBR1-mst-region] active region-configuration
[ASBR1-mst-region] quit
# Configure the STP priority of ASBR3 as 0 in MSTI0 to ensure that ASBR3 functions as the
root bridge.
[ASBR3] stp instance 0 priority 0
# Configure the STP priority of ASBR4 as 4096 in MSTI0 to ensure that ASBR4 functions as
the backup root bridge.
[ASBR4] stp instance 0 priority 4096
Configure the STP priorities of ASBR1 and ASBR2 as the default STP priority, namely, 32768.
Step 7 Configure E-STP, including the following tasks:
On the ASBRs:
l Create the mPW and enter the mPW view, and then enable STP.
l Enable STP on the inter-AS physical link.
NOTE
When binding the service VSI to the management VSI, configure STP in the management VSI rather than
in the service VSI. In this manner, the status of the service VSI is associated with the status of the
management VSI.
# Configure ASBR1.
[ASBR1-vsi-m1-ldp] peer 3.3.3.3 pw pw1
[ASBR1-vsi-m1-ldp-pw-pw1] stp enable
[ASBR1-vsi-m1-ldp-pw-pw1] stp cost 2

[ASBR1-vsi-m1-ldp-pw-pw1] quit
[ASBR1-vsi] quit
[ASBR1-GigabitEthernet1/0/0] stp enable
[ASBR1-GigabitEthernet1/0/0] stp instance 0 cost 2
# Configure ASBR2.
[ASBR2-vsi] quit
# Configure ASBR3.
[ASBR3-vsi] quit
# Configure ASBR4.
[ASBR4-vsi] quit
# Configure CE1.
[CE1-GigabitEthernet1/0/0.1] shutdown
# Configure CE2.


l Run the display stp brief command on the four ASBRs. You can view STP information,
and find that only GE 1/0/0 on ASBR2 is in the discarding state. That is, only GE 1/0/0 is
blocked.
<ASBR1> display stp brief
0 m1-pw1 DESI FORWARDING NONE
0 m1-pw1 ROOT FORWARDING NONE
0 m1-pw1 DEST FORWARDING NONE
l Run the display vsi name s1 verbose command on ASBR1. You can find that a PW
connecting PE1 is established in the VSI named s1 that is in the Up state.
<ASBR1> display vsi name s1 verbose
***VSI Name : s1
VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
Multicast Fast Swicth : disable
VSI State : up
VSI ID : 10
VC Label : 19457
Peer Type : dynamic
Session : up
Tunnel ID : 0x2000
CKey : 6
NKey : 5
StpEnable : 0
PwIndex : 0

State : up
Last Up Time : 2009/02/25 11:15:37
**PW Information:

PW State : up

PW Type : label
Tunnel ID : 0x2000
Ckey : 0x6
Nkey : 0x5
Tnl Type : LSP
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2009/02/25 11:15:38
<ASBR2> display vsi name s1 verbose
***VSI Name : s1
VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
VSI State : up
VSI ID : 10
VC Label : 19457
Peer Type : dynamic
Session : up
Tunnel ID : 0x2004
CKey : 6
NKey : 5
StpEnable : 0
PwIndex : 0
Interface Name : Ethernet1/0/0.1

State : up
Last Up Time : 2009/02/25 11:17:20
**PW Information:

PW State : up
PW Type : label
Tunnel ID : 0x2004
Ckey : 0x6
Nkey : 0x5
Tnl Type : LSP
Stp Enable : 0
Mac Flapping : 0

PW Last Up Time : 2009/02/25 11:17:20

l In addition, CE1 and CE2 can ping each other successfully. Take the display on CE1 as an
example.
<CE1> ping 10.1.1.2
0.00% packet loss
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 2.2.2.2
peer 3.3.3.3
#
mpls ldp
#
interface POSl/0/0
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface POS2/0/0
undo shutdown
ip address 100.1.2.1 255.255.255.0
mpls
mpls ldp
#
undo shutdown
#
vlan-type dot1q 10
undo shutdown
l2 binding vsi s1
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
ospf 1
area 0.0.0.0
network 100.1.1.0 0.0.0.255
network 100.1.2.0 0.0.0.255
network 1.1.1.1 0.0.0.0

#
return
#
sysname PE2
#
mpls lsr-id 6.6.6.6
mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 4.4.4.4
peer 5.5.5.5
#
mpls ldp
#
interface POSl/0/0
undo shutdown
ip address 100.5.1.2 255.255.255.0
mpls
mpls ldp
#
interface POS2/0/0
undo shutdown
ip address 100.5.2.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
#
vlan-type dot1q 10
undo shutdown
l2 binding vsi s1
#
interface LoopBack1
ip address 6.6.6.6 255.255.255.255
#
ospf 1
area 0.0.0.0
network 100.5.1.0 0.0.0.255
network 100.5.2.0 0.0.0.255
network 6.6.6.6 0.0.0.0
#
return
l Configuration file of ASBR1
#
sysname ASBR1
#
stp enable
#
region-name RG1
#
mpls lsr-id 2.2.2.2
mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 1.1.1.1

#
vsi m1 static
pwsignal ldp
vsi-id 100
peer 3.3.3.3
peer 3.3.3.3 pw pw1
stp enable
stp cost 2
admin-vsi
#
mpls ldp
#
undo shutdown
stp enable
stp instance 0 cost 2
#
vlan-type dot1q 100
undo shutdown
l2 binding vsi s1
#
undo shutdown
ip address 100.8.1.1 255.255.255.0
mpls
mpls ldp
#
interface POS3/0/0
link-protocol ppp
undo shutdown
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ospf 1
area 0.0.0.0
network 100.8.1.0 0.0.0.255
network 2.2.2.2 0.0.0.0
network 100.1.1.0 0.0.0.255
#
return
#
sysname ASBR2
#
stp enable
#
region-name RG1
#
mpls lsr-id 3.3.3.3
mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 1.1.1.1
#
vsi m1 static
pwsignal ldp
vsi-id 100
peer 2.2.2.2

peer 2.2.2.2 pw pw1

stp enable
stp cost 2
admin-vsi
#
mpls ldp
#
undo shutdown
stp enable
#
vlan-type dot1q 10
undo shutdown
l2 binding vsi s1
#
undo shutdown
ip address 100.8.1.2 255.255.255.0
mpls
mpls ldp
#
interface POS3/0/0
link-protocol ppp
undo shutdown
ip address 100.1.2.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.3 255.255.252.0
#
ospf 1
area 0.0.0.0
network 100.8.1.0 0.0.0.255
network 3.3.3.3 0.0.0.0
network 100.1.2.0 0.0.0.255
#
return
#
sysname ASBR3
#
stp enable
#
region-name RG1
#
mpls lsr-id 4.4.4.4
mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 6.6.6.6
#
vsi m1 static
pwsignal ldp
vsi-id 100
peer 5.5.5.5
peer 5.5.5.5 pw pw1
stp enable
stp cost 2
admin-vsi

#
mpls ldp
#
undo shutdown
stp enable
#
vlan-type dot1q 10
undo shutdown
l2 binding vsi s1
#
undo shutdown
ip address 100.9.1.1 255.255.255.0
mpls
mpls ldp
#
interface POS3/0/0
link-protocol ppp
undo shutdown
ip address 100.5.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 4.4.4.4 255.255.255.255
#
ospf 1
area 0.0.0.0
network 100.9.1.0 0.0.0.255
network 100.5.1.0 0.0.0.255
network 4.4.4.4 0.0.0.0
#
return
#
sysname ASBR4
#
stp enable
#
region-name RG1
#
mpls lsr-id 5.5.5.5
mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 6.6.6.6
#
vsi m1 static
pwsignal ldp
vsi-id 100
peer 4.4.4.4
peer 4.4.4.4 pw pw1
stp enable
stp cost 2
admin-vsi
#
mpls ldp
#

undo shutdown
stp enable
#
vlan-type dot1q 10
undo shutdown
l2 binding vsi s1
#
undo shutdown
ip address 100.9.1.2 255.255.255.0
mpls
mpls ldp
#
interface POS3/0/0
link-protocol ppp
undo shutdown
ip address 100.5.2.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 5.5.5.5 255.255.255.255
#
ospf 1
area 0.0.0.0
network 100.9.1.0 0.0.0.255
network 100.5.2.0 0.0.0.255
network 5.5.5.5 0.0.0.0
#
return

#
sysname CE1
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10
ip address 10.1.1.1 255.255.255.0
#
return

#
sysname CE2
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10
ip address 10.1.1.2 255.255.255.0
#
return
7.8.5 Example for Configuring E-STP - Inter-AS PW Interconnection

(Martini Mode)
When configuring STP over PW based on inter-AS PW interconnection in Martini mode, you
need to configure service VSIs and the mVSI on inter-AS and intra-AS NPEs, and enable STP
on the mPW.

Figure 7-13 shows the networking of inter-AS PW interconnection in Martini mode. This type
of networking has the following features:
l Each UPE is dual-homed to NPEs, and links are backed up between ASs.
l The two ASs are connected through a Hierarchical VPLS (HVPLS) network. UPE1, NPE1,
and NPE3 form a basic H-VPLS network, and UPE1 is an UPE peer of NPE1.
l The service PWs between NPE1 and NPE3 and between NPE2 and NPE4 are Spoke PWs,
which do not comply with the principle of split horizon.
This type of networking has the following problem:
l Each UPE receives two copies of traffic sent by the peer UPE.
You can adopt the following solutions to address the preceding problems:
You can configure a mPW between inter-AS NPEs and intra-AS NPEs, and enable STP on the
mPW. Then, you can set STP priorities and cost values to configure NPE3 as the root bridge,
NPE4 as the backup root bridge, and the inter-AS mPW on NPE2 to be blocked. In addition, the
block of the management VSI causes the block of the service VSIs. In this case, the traffic from
CE1 passes along the path UPE1-NPE1-NPE3-UPE2 to reach CE2. This prevents the traffic
from being doubled or forming a loop.
Figure 7-13 Networking diagram of configuring E-STP - inter-AS PW interconnection (Martini

mode)
MPLS Backbone1 NPE1 GE1/0/0 GE1/0/0 NPE3 MPLS Backbone 2

Service PW
2 2
0 PO
3/0/ 2 Management 2
S3
/0/
S 0
PO GE2/0/0 PW
GE2/0/0 PO
UPE1 S1 UPE2
/ 0/0 Management Management /0/
O S1 PW PW
0
P
PO
0
S2 P
/0/ OS GE2/0/0 GE2/0/0 0 2/0/
/ S
0 3/0 2 2
S3/0 PO
GE3/0/0.1 /0 5 Management PW 5 PO GE3/0/0.l
Service PW
NPE2 GE1/0/0 GE1/0/0 NPE4
GE1/0/0 GE1/0/0

CE1 CE2

UPE1 POS1/0/0: 100.1.1.1/24 UPE2 POS1/0/0: 100.5.1.2/24
POS2/0/0: 100.1.2.1/24 POS2/0/0: 100.5.2.2/24
GE3/0/0.1: -- GE3/0/0.1: --

NPE1 POS2/0/0: 100.3.1.1/24 NPE2 POS2/0/0: 100.3.1.2/24

POS3/0/0: 100.1.1.2/24 POS3/0/0: 100.1.2.2/24
NPE3 POS2/0/0: 100.4.1.1/24 NPE4 POS2/0/0: 100.4.1.2/24
POS3/0/0: 100.5.1.1/24 POS3/0/0: 100.5.2.1/24
CE1 GE1/0/0: -- CE2 GE1/0/0: --
1. Run an IGP protocol on the backbone network to realize device connectivity within the
same AS.
2. Enable the basic MPLS capability on the backbone network, including the following tasks:
l Set up dynamic LSPs between the UPE and two NPEs in the same AS.
l Set up a dynamic LSP between the two NPEs in the same AS.
Establish remote LDP sessions for the indirect connection(s) between the UPE and NPEs
or between NPEs.
3. Establish the VPLS connections between the UPE and NPEs in the same AS, including the
following tasks:
l Create service VSIs on the UPE and two NPEs that are in the same AS. These service
VSIs are used to exchange service packets.
l Create the mVSI on the NPEs that are in the same AS. The mVSI is used to send STP
packets through the mPW.
l Configure the mVSI and service VSIs on the NPEs, with the mPW transmitting STP
packets, and service PWs transparently transmitting service packets. Meanwhile,
associate the status of service VSIs with the status of the mVSI.
4. Configure STP on the intra-AS mPW and inter-AS mPW.
By configuring STP priorities and costs, ensure that NPE3 functions as the root bridge,
NPE4 as the backup root bridge, and the PW between NPE2 and NPE4 as being blocked.
Data Preparation
l Data for configuring OSPF
l IP addresses of remote peers
l MPLS LSR IDs of UPEs and NPEs
l VSI IDs
l STP priorities and costs
Procedure
Step 1 Assign IP addresses to the interfaces on the MPLS backbone network. The configuration details
are not mentioned here.

Step 2 Configure an IGP protocol on the MPLS backbone network.

Configure an IGP protocol on the MPLS backbone network to realize the interconnection
between UPEs and NPEs. In the configuration example, OSPF is configured. The configuration
details are not mentioned here.
Configure the basic MPLS capability on the MPLS network, and establish dynamic LDP LSPs
between the UPE and NPEs in the same AS.
After this step, LSPs are established between the UPE and NPEs in the same AS.
Step 4 Enable MPLS L2VPN on the UPE and NPEs.
# Configure UPE1.
[UPE1] mpls l2vpn
# Configure NPE1.
[NPE1] mpls l2vpn
# Configure NPE2.
[NPE2] mpls l2vpn
The configurations of UPE2, UPE3, and NPE4 are similar and not mentioned here.
1. Configure the mVSI on the four NPEs, including the configurations of the mPW between
the intra-AS NPEs and mPW between the inter-AS NPEs.
# Configure NPE1.
[NPE1] vsi m1 static
[NPE1-vsi-m1] pwsignal ldp
[NPE1-vsi-m1-ldp] vsi-id 10
[NPE1-vsi-m1-ldp] peer 3.3.3.3
[NPE1-vsi-m1-ldp] quit
[NPE1-vsi-m1] admin-vsi
[NPE1-vsi-m1] quit
# Configure NPE2.
[NPE2-vsi-m1] quit
# Configure NPE3.
[NPE3-vsi-m1] quit
# Configure NPE4.


[NPE4-vsi-m1] quit
2. On UPEs, configure service VSIs and bind the service VSIs to relevant interfaces. On NPEs,
configure the Hierarchical VPLS (HVPLS) networking with the intra-AS UPEs, establish
ordinary peer relationships with the inter-AS NPEs, and bind service VSIs to the mVSI.
# Configure UPE1.
[UPE1] vsi s1 static
[UPE1-vsi-s1] pwsignal ldp
[UPE1-vsi-s1-ldp] vsi-id 100
[UPE1-vsi-s1-ldp] peer 2.2.2.2
[UPE1-vsi-s1-ldp] quit
[UPE1-vsi-s1] quit
[UPE1] interface gigabitethernet 3/0/0.1
[UPE1-GigabitEthernet3/0/0.1] shutdown
[UPE1-GigabitEthernet3/0/0.1] vlan-type dot1q 10
[UPE1-GigabitEthernet3/0/0.1] l2 binding vsi s1
[UPE1-GigabitEthernet3/0/0.1] undo shutdown
[UPE1-GigabitEthernet3/0/0.1] quit
# Configure NPE1.
[NPE1] vsi s1 static
[NPE1-vsi-s1] pwsignal ldp
[NPE1-vsi-s1-ldp] vsi-id 100
[NPE1-vsi-s1-ldp] peer 1.1.1.1 upe
[NPE1-vsi-s1-ldp] peer 4.4.4.4
[NPE1-vsi-s1-ldp] quit
[NPE1-vsi-s1] track admin-vsi m1
[NPE1-vsi-s1] quit
# Configure NPE2.
[NPE2-vsi-s1] quit
# Configure UPE2.
[UPE2] vsi s1 static
[UPE2-vsi-s1] pwsignal ldp
[UPE2-vsi-s1-ldp] vsi-id 100
[UPE2-vsi-s1-ldp] quit
[UPE2-vsi-s1] quit
[UPE2] interface gigabitethernet 3/0/0.1
[UPE2-GigabitEthernet3/0/0.1] shutdown
[UPE2-GigabitEthernet3/0/0.1] vlan-type dot1q 10
[UPE2-GigabitEthernet3/0/0.1] l2 binding vsi s1
[UPE2-GigabitEthernet3/0/0.1] undo shutdown
[UPE2-GigabitEthernet3/0/0.1] quit
# Configure NPE3.
[NPE3-vsi-s1] quit

# Configure NPE4.
[NPE34-vsi-s1] quit
Step 6 Enable STP.

Enable STP on the four NPEs.
# Configure the MST region of NPE1, and then activate the region configurations. Because the
four NPEs have the same region configurations, take NPE1 as an example.
[NPE1] stp enable
[NPE1] stp region-configuration
[NPE1-mst-region] region-name RG1
[NPE1-mst-region] active region-configuration
[NPE1-mst-region] quit
# Configure the priority of NPE3 as 0 in MSTI0 to ensure that NPE3 functions as the root bridge.
[NPE3] stp instance 0 priority 0
# Configure the priority of NPE4 as 4096 in MSTI0 to ensure that NPE4 functions as the backup
root bridge.
[NPE4] stp instance 0 priority 4096
Configure the STP priorities of NPE1 and NPE2 as the default STP priority, namely, 32768.
Step 7 Configure E-STP. Enable STP on the intra-AS mPW and inter-AS mPW, and configure STP
costs.
NOTE
management VSI.
# Configure NPE1.
[NPE1-vsi-m1-ldp] peer 3.3.3.3 pw pw1
[NPE1-vsi-m1-ldp-pw-pw1] stp enable
[NPE1-vsi-m1-ldp-pw-pw1] stp cost 2
[NPE1-vsi-m1-ldp-pw-pw1] quit
# Configure NPE2.

[NPE2-vsi] quit
# Configure NPE3.
[NPE3-vsi] quit
# Configure NPE4.
[NPE4-vsi] quit

# Configure CE1.
# Configure CE2.

l Check STP information.
[NPE1] display stp brief
0 m1-pw1 DESI FORWARDING NONE
[NPE2] display stp brief
0 m1-pw2 ALTE DISCARDING NONE
As shown in the command output, The PW named pw2 between NPE2 and NPE4 is blocked
and in the discarding state.
l Run the display vsi name s1 verbose command on NPE1 and NPE2. The command output
on NPE1 shows that the service VSI s1 has two PWs respectively connecting UPE1 and
UPE3, and both the service VSI s1 and the PWs are in the Up state. The command output on

NPE2 shows that the service VSI s1 have two PWs respectively connecting UPE1 and UPE4,
and the service VSI s1 and the PW connecting with UPE1 are in the Up state, but the PW
connecting NPE4 is in the backup state. For details, see the following table.
Device Status of the Status of the service PW
service VSI
NPE1 UP l The status of the PW between NPE1 and UPE1 is

Up.
l The status of the PW between NPE1 and NPE3 is
Up.
NPE2 UP l The status of the PW between NPE2 and UPE1 is

Up.
l The status of the PW between NPE2 and NPE4 is
backup.
<NPE1> display vsi name s1 verbose
***VSI Name : s1
VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
VSI State : up
VSI ID : 10
VC Label : 19459
Peer Type : dynamic
Session : up
Tunnel ID : 0x2000
CKey : 6
NKey : 5
StpEnable : 0
PwIndex : 0
VC Label : 19460
Peer Type : dynamic
Session : up
Tunnel ID : 0x201d
CKey : 6
NKey : 5
StpEnable : 0
PwIndex : 0
**PW Information:

PW State : up
PW Type : MEHVPLS
Tunnel ID : 0x2000
Ckey : 0x6
Nkey : 0x5
Tnl Type : LSP
OutInterface : POS3/0/0
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2009/02/25 07:46:06
PW State : up
PW Type : label
Tunnel ID : 0x201d
Ckey : 0x6
Nkey : 0x5
Tnl Type : LSP
Stp Enable : 1
Mac Flapping : 0
PW Last Up Time : 2009/02/25 07:46:06
<NPE2> display vsi name s1 verbose
***VSI Name : s1
VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
VSI State : up
VSI ID : 10
VC Label : 19458
Peer Type : dynamic
Session : up
Tunnel ID : 0x2004
CKey : 6
NKey : 5
StpEnable : 0
PwIndex : 0
VC Label : 19459
Peer Type : dynamic
Session : up

Tunnel ID : 0x2016
CKey : 6
NKey : 5
StpEnable : 0
PwIndex : 0
**PW Information:

PW State : up
PW Type : MEHVPLS
Tunnel ID : 0x2004
Ckey : 0x6
Nkey : 0x5
Tnl Type : LSP
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2009/02/24 20:33:18
PW State : backup
PW Type : label
Tunnel ID : 0x2016
Ckey : 0x6
Nkey : 0x5
Tnl Type : LSP
Stp Enable : 1
Mac Flapping : 0
PW Last Up Time : 2009/02/24 20:33:18
As shown in the command output, the service PW between NPE1 and NPE4 is blocked.
l CE1 and CE2 can ping each other successfully.
Take the display on CE1 as an example.
<CE1> ping 10.1.1.2
0.00% packet loss
----End
Configuration Files
#
sysname UPE1

#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 2.2.2.2
peer 3.3.3.3
#
mpls ldp
#
interface POS1/0/0
link-protocol ppp
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface POS2/0/0
link-protocol ppp
ip address 100.1.2.1 255.255.255.0
mpls
mpls ldp
#
undo shutdown
#
vlan-type dot1q 100
undo shutdown
l2 binding vsi s1
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
ospf 1
area 0.0.0.0
network 100.1.1.0 0.0.0.255
network 100.1.2.0 0.0.0.255
network 1.1.1.1 0.0.0.0
#
return
#
sysname UPE2
#
mpls lsr-id 6.6.6.6
mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 4.4.4.4
peer 5.5.5.5
#
mpls ldp
#
interface POS1/0/0
link-protocol ppp
ip address 100.5.1.2 255.255.255.0
mpls
mpls ldp
#
interface POS2/0/0
link-protocol ppp

ip address 100.5.2.2 255.255.255.0

mpls
mpls ldp
#
undo shutdown
#
vlan-type dot1q 100
undo shutdown
l2 binding vsi s1
#
interface LoopBack1
ip address 6.6.6.6 255.255.255.255
#
ospf 1
area 0.0.0.0
network 100.5.1.0 0.0.0.255
network 100.5.2.0 0.0.0.255
network 6.6.6.6 0.0.0.0
#
return
l Configuration file of NPE1
#
sysname NPE1
#
stp enable
#
region-name RG1
#
mpls lsr-id 2.2.2.2
mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 1.1.1.1 upe
peer 4.4.4.4
track admin-vsi m1
#
vsi m1 static
pwsignal ldp
vsi-id 100
peer 3.3.3.3
peer 3.3.3.3 pw pw1
stp enable
stp cost 2
peer 4.4.4.4
peer 4.4.4.4 pw pw2
stp enable
stp cost 2
admin-vsi
#
mpls ldp
#
undo shutdown
ip address 100.6.1.1 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 100.8.1.1 255.255.255.0
mpls

mpls ldp
#
interface POS3/0/0
link-protocol ppp
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ospf 1
area 0.0.0.0
network 100.8.1.0 0.0.0.255
network 2.2.2.2 0.0.0.0
network 100.1.1.0 0.0.0.255
network 100.6.1.0 0.0.0.255
#
return
#
sysname NPE2
#
stp enable
#
region-name RG1
#
mpls lsr-id 3.3.3.3
mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 1.1.1.1 upe
peer 5.5.5.5
track admin-vsi m1
#
vsi m1 static
pwsignal ldp
vsi-id 100
peer 2.2.2.2
peer 2.2.2.2 pw p1
stp enable
stp cost 2
peer 5.5.5.5
peer 5.5.5.5 pw p2
stp enable
stp cost 5
admin-vsi
#
mpls ldp
#
undo shutdown
ip address 100.7.1.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 100.8.1.1 255.255.255.0
mpls
mpls ldp
#
interface POS3/0/0

link-protocol ppp
ip address 100.1.2.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.3 255.255.252.0
#
ospf 1
area 0.0.0.0
network 100.8.1.0 0.0.0.255
network 3.3.3.3 0.0.0.0
network 100.1.2.0 0.0.0.255
network 100.7.1.0 0.0.0.255
#
return
#
sysname NPE3
#
stp enable
#
region-name RG1
#
mpls lsr-id 4.4.4.4
mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 6.6.6.6 upe
peer 2.2.2.2
track admin-vsi m1
#
vsi m1 static
pwsignal ldp
vsi-id 100
peer 2.2.2.2
peer 2.2.2.2 pw pw2
stp enable
stp cost 2
peer 5.5.5.5
peer 5.5.5.5 pw pw1
stp enable
stp cost 2
admin-vsi
#
mpls ldp
#
undo shutdown
ip address 100.6.1.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 100.9.1.1 255.255.255.0
mpls
mpls ldp
#
interface POS3/0/0
link-protocol ppp
ip address 100.5.1.1 255.255.255.0

mpls
mpls ldp
#
interface LoopBack1
ip address 4.4.4.4 255.255.255.255
#
ospf 1
area 0.0.0.0
network 100.9.1.0 0.0.0.255
network 4.4.4.4 0.0.0.0
network 100.6.1.0 0.0.0.255
network 100.5.1.0 0.0.0.255
#
return
#
sysname NPE4
#
stp enable
#
region-name RG1
#
mpls lsr-id 5.5.5.5
mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 6.6.6.6 upe
peer 3.3.3.3
track admin-vsi m1
#
vsi m1 static
pwsignal ldp
vsi-id 100
peer 3.3.3.3
peer 3.3.3.3 pw pw2
stp enable
stp cost 5
peer 4.4.4.4
peer 4.4.4.4 pw pw1
stp enable
stp cost 2
admin-vsi
#
mpls ldp
#
undo shutdown
ip address 100.7.1.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 100.9.1.2 255.255.255.0
mpls
mpls ldp
#
interface POS3/0/0
link-protocol ppp
ip address 100.5.2.1 255.255.255.0
mpls
mpls ldp

#
interface LoopBack1
ip address 5.5.5.5 255.255.255.255
#
ospf 1
area 0.0.0.0
network 100.9.1.0 0.0.0.255
network 5.5.5.5 0.0.0.0
network 100.7.1.0 0.0.0.255
network 100.5.2.0 0.0.0.255
#
return

#
sysname CE1
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10
ip address 10.1.1.1 255.255.255.0
#
return

#
sysname CE2
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10
ip address 10.1.1.2 255.255.255.0
#
return
7.8.6 Example for Configuring E-STP for CE Dual-Homing

When configuring STP over PW in the scenario where a CE is dual homed to PEs, you need to
enable STP on the physical links between CE1 and PE1 and between CE1 and PE2, and the
mPW between PE1 and PE2.
Figure 7-14 shows the VPLS networking where a CE is dual-homed to PEs. This type of
networking has the following problem:
l PE3 receives two copies of traffic sent by the peer CE1.
You can adopt the following solution to address the preceding problems:
You can configure a mPW between PE1 and PE2, and enable STP on the physical links between
CE1 and PE1, and between CE1 and PE2, and on the mPW between PE1 and PE2. Then, you
can set STP priorities and cost values to configure PE1 as the root bridge, PE2 as the backup
root bridge, and GE 2/0/0 of CE1 to be blocked. In this case, the traffic from the DSLAM passes
along the path CE1-PE1-PE3 to reach CE2. This prevents the traffic from being doubled or
forming a loop.

Figure 7-14 Networking diagram of configuring E-STP for CE dual-homing

PE1
MPLS Backbone
GE1/0/0
POS2/0/0
2 2
CE1 POS1/0/0
GE1/0/0 Serv
i cePW
2 STP Management PE3
5 loop
GE3/0/0 PW W
P
ce GE3/0/0
GE2/0/0 2 ervi
5 S
GE1/0/0 POS2/0/0 GE1/0/0
10.1.1.1/24 GE1/0/0 10.1.1.2/24
POS2/0/0
PE2
CE2
DSLAM
Device Interface and IP Address

PE1 GE1/0/0: --
POS2/0/0: 100.1.1.1/24
Loopback1: 1.1.1.1/32
PE2 GE1/0/0: --
POS2/0/0: 100.2.1.1/24
Loopback1: 2.2.2.2/32
PE3 POS1/0/0: 100.1.1.2/24
POS2/0/0: 100.2.1.2/24
GE3/0/0: --
Loopback1: 3.3.3.3/32
1. Run an IGP protocol on the backbone network to implement device connectivity within
the VPLS backbone network.
2. Configure the basic MPLS capability and establish LDP LSPs on the VPLS backbone
network.
3. Establish the VPLS connections between PEs, including the following tasks:
l Create service VSIs that are used to exchange service packets.
l Create the mVSI that is used to deliver STP packets through the mPW.
4. Configure STP, including the following tasks:
l Enable STP on the mPW between the PEs.
l Enable STP on the physical links between CEs and between the CE and PE.
Configure relevant STP priorities to ensure that PE1 functions as the root bridge, and PE2
as the backup root bridge.

Data Preparation
l IP addresses of the interfaces.
l Data for running IS-IS
l MPLS LSR ID of the MPLS peer
l MPLS LSR IDs of the UPE and PE3
l VSI name and VSI ID
l STP region name and priority
Procedure
Step 1 Assign IP addresses to the interfaces and configure an IGP protocol on the VPLS backbone
network. This implements the interconnection between PEs. In the configuration example, OSPF
is configured, and the configuration details are not mentioned here.
1. Enable the basic MPLS capability on the MPLS network, and establish dynamic LDP LSPs
between PEs
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
[PE1-Pos2/0/0] mpls
[PE1-Pos2/0/0] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2-Pos2/0/0] mpls
[PE2-Pos2/0/0] quit
# Configure PE3.
[PE3] mpls
[PE3-mpls] quit
[PE3] mpls ldp
[PE3-mpls-ldp] quit
[PE3-Pos1/0/0] mpls
[PE3-Pos1/0/0] quit
[PE3-Pos2/0/0] mpls
[PE3-Pos2/0/0] quit
2. # Configure the remote peer relationship between PE1 and PE2 to facilitate the creation of
the mPW.
# Configure PE1.


# Configure PE2.
Take PE3 as an example:

------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------

# Configure PE1.
[PE1] mpls l2vpn
# Configure PE2.
[PE2] mpls l2vpn
# Configure PE3.
[PE3] mpls l2vpn

1. Configure the mVSI.
# Configure PE1.
[PE1] vsi m1 static
[PE1-vsi-m1] pwsignal ldp
[PE1-vsi-m1-ldp] vsi-id 100
[PE1-vsi-m1-ldp] peer 2.2.2.2
[PE1-vsi-m1-ldp] quit
[PE1-vsi-m1] admin-vsi
[PE1-vsi-m1] quit
# Configure PE2.
[PE2] vsi m1 static
[PE2-vsi-m1-ldp] vsi-id 100
[PE2-vsi-m1-ldp] peer 1.1.1.1
[PE2-vsi-m1] admin-vsi
[PE2-vsi-m1] quit
2. Configure service VSIs.

# Configure PE1.
[PE1] vsi s1 static

[PE1-vsi-s1] quit
# Configure PE2.
[PE2] vsi s1 static
[PE2-vsi-s1] quit
# Configure PE3.
[PE3] vsi s1 static
[PE3-vsi-s1] quit
Step 5 Configure STP. Configure STP on PE1, PE2, and CE1.

1. # Configure the MST region of PE1, and then activate the region configuration.
# Configure PE1.
[PE1] stp enable
[PE1] stp region-configuration
[PE1-mst-region] region-name RG1
[PE1-mst-region] active region-configuration
[PE1-mst-region] quit
# Configure PE2.
[PE2] stp enable
[PE2] stp region-configuration
[PE2-mst-region] region-name RG1
[PE2-mst-region] active region-configuration
[PE2-mst-region] quit
# Configure CE1.
[CE1] stp enable
[CE1] stp region-configuration
[CE1-mst-region] region-name RG1
[CE1-mst-region] active region-configuration
[CE1-mst-region] quit
2. Configure STP priorities of the PEs and CEs, and ensure that PE1 functions as the root
bridge, and PE2 as the backup root bridge.
# Configure the STP priority of PE1 as 0 in MSTI0 to ensure that PE1 functions as the root
bridge.

[PE1] stp instance 0 priority 0
# Configure the STP priority of PE2 as 4096 in MSTI0 to ensure that PE2 functions as the
backup root bridge.
[PE2] stp instance 0 priority 4096
Configure the STP priority of CE1 as the default STP priority, namely, 32768.
Step 6 Configure E-STP.
l Enable STP on the mPW between PE1 and PE2.
l Enable STP on the physical interfaces between PE1 and CE1, and between PE2 and CE1.
NOTE
management VSI.
# Configure PE1.
[PE1] vsi m1 static
[PE1-vsi-m1-ldp] peer 2.2.2.2 pw pw1
[PE1-vsi-m1-ldp-pw-pw1] stp enable
[PE1-vsi-m1-ldp-pw-pw1] stp cost 2
[PE1-vsi-m1-ldp-pw-pw1] quit
[PE1-vsi] quit
[PE1-GigabitEthernet1/0/0] stp enable
[PE1-GigabitEthernet1/0/0] stp vpls-subinterface enable
[PE1-GigabitEthernet1/0/0] stp instance 0 cost 2
# Configure PE2.
[PE2] vsi m1 static
[PE2-vsi-m1-ldp] peer 1.1.1.1 pw pw1
[PE2-vsi-m1-ldp-pw-pw1] stp enable
[PE2-vsi-m1-ldp-pw-pw1] stp cost 2
[PE2-vsi-m1-ldp-pw-pw1] quit
[PE2-vsi] quit
[PE2-GigabitEthernet1/0/0] stp enable
[PE1-GigabitEthernet1/0/0] stp vpls-subinterface enable
[PE2-GigabitEthernet1/0/0] stp instance 0 cost 5
# Configure CE1.
[CE1] portswitch batch gigabitethernet 1/0/0 2/0/0 3/0/0
[CE1] vlan 10
[CE1-vlan10] port gigabitethernet 1/0/0 to 2/0/0 to 3/0/0
[CE1-vlan10] quit
[CE1-GigabitEthernet1/0/0] stp enable
[CE1-GigabitEthernet1/0/0] stp instance 0 cost 2
[CE1-GigabitEthernet2/0/0] stp enable
[CE1-GigabitEthernet2/0/0] stp instance 0 cost 5
Step 7 Configure the DSLAM device and CE2.

# Configure the DSLAM device.
[DSLAM] interface gigabitethernet 1/0/0.1
[DSLAM-GigabitEthernet1/0/0.1] shutdown

[DSLAM-GigabitEthernet1/0/0.1] vlan-type dot1q 10

[DSLAM-GigabitEthernet1/0/0.1] ip address 10.1.1.2 24
[DSLAM-GigabitEthernet1/0/0.1] undo shutdown
[DSLAM-GigabitEthernet1/0/0.1] quit
# Configure CE2.

Run the display vsi name s1 verbose command on PE3. You can find that PE3 establishes PWs
respectively with PE1 (1.1.1.1) and PE2 (2.2.2.2),
<PE3> display vsi name s1 verbose
***VSI Name : s1
VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
VSI State : up
VSI ID : 10
VC Label : 19459
Peer Type : dynamic
Session : up
Tunnel ID : 0x2000
CKey : 6
NKey : 5
StpEnable : 0
PwIndex : 0
VC Label : 19460
Peer Type : dynamic
Session : up
Tunnel ID : 0x201d
CKey : 6
NKey : 5
StpEnable : 0
PwIndex : 0

State : up
Last Up Time : 2009/02/25 11:15:37
**PW Information:

PW State : up
PW Type : label
Tunnel ID : 0x2000
Ckey : 0x6
Nkey : 0x5
Tnl Type : LSP
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2009/02/25 07:46:06
PW State : up
PW Type : label
Tunnel ID : 0x2001
Ckey : 0x6
Nkey : 0x5
Tnl Type : LSP
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2009/02/25 07:46:06
the link connecting CE1 to the backup root bridge PE2 is blocked,
<CE1> display stp brief
and the DSLAM device and CE2 can ping each other successfully.
Take the display on the DSLAM device as an example:
<DSLAM> ping 10.1.1.2
0.00% packet loss
----End
Configuration Files
#
sysname PE1
#
stp enable

#
region-name RG1
#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 3.3.3.3
#
vsi m1 static
pwsignal ldp
vsi-id 100
peer 2.2.2.2
peer 2.2.2.2 pw pw1
stp enable
stp cost 2
admin-vsi
#
mpls ldp
#
#
remote-ip 2.2.2.2
undo remote-ip pwe3
#
undo shutdown
stp enable
stp vpls-subinterface enable
#
vlan-type dot1q 10
undo shutdown
l2 binding vsi s1
#
interface POS2/0/0
link-protocol ppp
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
ospf 1
area 0.0.0.0
network 100.1.1.0 0.0.0.255
network 1.1.1.1 0.0.0.0
#
return
#
sysname PE2
#
stp enable
#
region-name RG1
#

mpls lsr-id 2.2.2.2

mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 3.3.3.3
#
vsi m1 static
pwsignal ldp
vsi-id 100
peer 1.1.1.1
peer 1.1.1.1 pw pw1
stp enable
stp cost 2
admin-vsi
#
mpls ldp
#
remote-ip 1.1.1.1
undo remote-ip pwe3
#
undo shutdown
stp enable
stp vpls-subinterface enable
#
vlan-type dot1q 10
undo shutdown
l2 binding vsi s1
#
interface POS2/0/0
link-protocol ppp
undo shutdown
ip address 100.2.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ospf 1
area 0.0.0.0
network 100.2.1.0 0.0.0.255
network 2.2.2.2 0.0.0.0
#
return
#
sysname PE3
#
mpls lsr-id 3.3.3.3
mpls
#
mpls l2vpn
#
vsi s1 static
pwsignal ldp
vsi-id 10
peer 1.1.1.1
peer 2.2.2.2
#
mpls ldp
#

interface POS1/0/0
undo shutdown
link-protocol ppp
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface POS2/0/0
undo shutdown
link-protocol ppp
ip address 100.2.1.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
#
vlan-type dot1q 10
undo shutdown
l2 binding vsi s1
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
ospf 1
area 0.0.0.0
network 100.1.1.0 0.0.0.255
network 3.3.3.3 0.0.0.0
network 100.2.1.0 0.0.0.255
#
return
l Configuration file of the DSLAM device
#
sysname DSLAM
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10
ip address 10.1.1.1 255.255.255.0
#
return
#
sysname CE1
#
vlan batch 10
#
stp enable
#
region-name RG1
#
undo shutdown
portswitch
#
undo shutdown
portswitch

#
undo shutdown
portswitch
#
return

#
sysname CE2
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10
ip address 10.1.1.2 255.255.255.0
#
return

Configuration Guide - LAN Access and MAN Access 8 BPDU Tunnel Configuration
8 BPDU Tunnel Configuration
About This Chapter
Bridge Protocol Data Units (BPDU) are usually used to transmit Spanning Tree Protocol (STP)
and Multiple Spanning Tree Algorithm and Protocol (MSTP) information. The path along which
BPDUs are transparently transmitted on the ISP network is known as a Layer 2 protocol tunnel
or a BPDU tunnel.
8.1 BPDU Tunnel Overview

BPDUs are Layer 2 protocol data units, encapsulated in IEEE802.3 frame format, and sent in
multicast mode.
8.2 Configuring Interface-based BPDU Tunnels
This section describes how to configure the BPDUs from different user networks to be
transparently transmitted on the ISP network when each interface on the user side of a PE is
connected to only one user network.
8.3 Configuring VLAN-based BPDU Tunnels
If the interface on the user side of a PE connects to multiple CEs, the BPDUs sent from the CEs
need to carry tags to differentiate user networks. To enable the BPDUs sent from user networks
to be transparently transmitted on the ISP network, you can configure VLAN-based BPDU
tunnels.
8.4 Configuring QinQ-based BPDU Tunnels
need to carry tags to differentiate user networks. To enable the BPDUs from user networks to
be transparently transmitted on the ISP network, and to save the VLAN ID resources of the ISP,
you can configure QinQ-based BPDU tunnels.
This section describes the typical application scenarios of various types of BPDU tunnels,
including networking requirements, configuration roadmap, and data preparation, and provides
related configuration files.

8.1 BPDU Tunnel Overview

BPDUs are Layer 2 protocol data units, encapsulated in IEEE802.3 frame format, and sent in
multicast mode.
8.1.1 Introduction to BPDU

The BPDU tunnel is a path along which BPDUs are transparently transmitted on the ISP network.
Brief Introduction to the BPDU Tunnel
The Bridge Protocol Data Unit (BPDU) packet is a type of Layer 2 protocol packets. As shown
in Figure 8-1, BPDU packets adopt the encapsulation format defined in IEEE802.3 and are
transmitted in the form of multicast.
BPDU packets are usually used to transmit the Spanning Tree Protocol (STP) and Multiple
Spanning Tree Algorithm and Protocol (MSTP) information. The path of BPDU packets used
for transparent transmission in the operator network is known as a Layer 2 protocol tunnel or a
BPDU tunnel.
Figure 8-1 Basic format of BPDU encapsulation

0 7 15 23 31
Destination address (0180-C200-0000)
Source address
Length
BPDU data
Table 8-1 Description of basic formats of fields in BPDU packets
Field Length Meaning
Destination 48 bit Destination MAC address. For general users, all destination
address MAC addresses are 0180-C200-0000.
Source address 48 bit Source MAC address.
Length 16 bit Length of BPDU data.

Background of the BPDU Tunnel

The following takes Figure 8-2 as an example to explain the introduction of BPDU tunnels.
Both user network1 and user network2 run MSTP. BPDUs of user network1 are required to
traverse the ISP network to reach user network2, thus, the STP function can be realized at the
same time. After PE1 of the ISP network receives the BPDUs from user network1, PE1 cannot
identify the BPDUs are sent from a user network or an ISP network because the destination
MAC addresses of the BPDUs are constantly 0180-C200-0000. Thus, PE1 delivers all the
BPDUs to the CPU for further processing and the spanning tree is calculated.
Thus, devices in user network 1 implement spanning tree computation together with PE1 instead
of devices in user network 2. This cannot ensure that BPDU packets in user network 1 can reach
user network 2.
Figure 8-2 Transparent transmission of BPDUs in an ISP network
ISP
network
PE1 PE2
CE1 CE2
User User
network1 network2
To ensure the BPDUs of user network1 can reach user network2, BPDUs must be transmitted
in the ISP network in transparent mode. To realize transparent transmission of BPDUs in the
ISP network, the following conditions must be satisfied:
l A branch network of a user network can receive the BPDUs destined for all branch networks
of the user network.
l The BPDUs of a user network cannot be processed by the CPU of the ISP network.
l BPDUs of different user networks must be isolated, so the BPDUs are freed from
interference.
A BPDU tunnel refers to the path in a Packet Switched Network (PSN) through which BPDUs
are transparently transmitted.
Through configuration of BPDU tunnels in the ISP network, branch networks of different user
networks can transparently transmit BPDUs among them through BPDU tunnels.
8.1.2 BPDU Tunnel Features Supported by the NE80E/40E

When each interface on the user side of a PE is connected to only one CE, and the BPDUs sent
from the user network do not carry tags, you can configure an interface-based BPDU tunnel to
enable the BPDUs to be transparently transmitted on the ISP network.
The NE80E/40E supports the following BPDU tunnels according to implementation methods:

l Interface-based BPDU tunnel

l VLAN-based BPDU tunnel
l QinQ-based BPDU tunnel
The description of implementation methods is as follows:
Interface-based BPDU Tunnel
Figure 8-3 Interface-based BPDU tunnels of different user networks
Port based Port based

VLAN 200 VLAN 200
LAN-B LAN-B
MSTP MSTP
ISP Network
PE1 BPDU Tunnel 200 PE2
BPDU Tunnel 300
Port based Port based

VLAN 300 VLAN 300
PE3 LAN-A
LAN-A
MSTP MSTP
Port based
VLAN 200
LAN-B
MSTP
As shown in Figure 8-3, each interface of the PE connects only one user network. The BPDUs
sent from a user network does not carry a tag. The PE must identify which user LAN the BPDUs
are from. Then the PE forwards the packets to the user network that connects the specified
interface. The BPDUs of LAN-A must be forwarded to another user network of LAN-A rather
than user network of LAN-B. In addition, BPDUs should not be processed by the ISP network
device.
To establish an interface-based BPDU tunnel, one way is to configure devices with different
roles as follows:
1. Configure the type of ISP devices to provider. Thus, the destination MAC addresses of the
BPDUs sent by the ISP network are changed to 01-80-C2-00-00-08 instead of the original
01-80-C2-00-00-00.
2. Configure the type of user network devices to customer. Thus, the destination MAC
addresses of the BPDUs sent by user networks are still 01-80-C2-00-00-00.
3. Add the interfaces that connect the same user network into a VLAN. After receiving the
BPDUs from the user networks, the PEs label the BPDUs with corresponding tags based
on the PVIDs of the interfaces.

4. The destination MAC addresses of the BPDUs sent by the user networks are 01-80-
C2-00-00-00 instead of 01-80-C2-00-00-08. Thus, the PEs (provider) do not consider the
BPDUs sent from user networks as BPDUs. The PEs choose corresponding BPDU tunnels
to forward the BPDUs based on PVIDs instead of delivering the BPDUs to the CPU.
In this way, the BPDUs can go across ISP's Layer 2 switching network.
As shown in Figure 8-3, the PE is configured with the interface-based BPDU tunnel. PE adds
a tag to the BPDUs from user networks according to the PVID of an interface. In this way, users
can be identified according to different public VLANs and packets are transmitted through
different BPDU tunnels. Traffic of LAN-A users travels through the BPDU tunnel of VLAN
300. Traffic of LAN-B users go through the BPDU tunnel of VLAN 200.
Another way is to configure devices with the same role, that is, configure all ISP devices and
user devices as customer. In this way, the difference is that the well-known destination MAC
address of the user BPDU is replaced by a dedicated multicast MAC address on the ISP device
and the ISP interface connected to the user device must be enabled with the BPDU tunnel
function.
VLAN-based BPDU Tunnel
Figure 8-4 VLAN-based BPDU tunnel
CE-VLAN 100 CE-VLAN 100

LAN-B
LAN-B
MSTP MSTP
PE 1 ISP Network PE 2
BPDU Tunnel
PE 3
CE-VLAN 100
LAN-A LAN-A
MSTP MSTP
LAN-B
MSTP
For most cases, the PE serves as a convergence node. The convergence interface on PE1 connects
both LAN-A and LAN-B, as shown in Figure 8-4. To identify the two different LANs, the
BPDUs sent by the CE must carry VLAN tags. In Figure 8-4, the VLAN ID of LAN-A is 200
and the VLAN ID of LAN-B is 100.
Currently, the packets sent by RSTP/MSTP are not encapsulated with a tag. When the control
plane receives the BPDUs carrying a tag, these packets are considered as error packets and

discarded. The PE must support BPDUs carrying a tag and is configured with the VLAN-based
BPDU tunnel. In this way, BPDUs can go across Layer 2 networks through different BPDU
tunnels and reach user networks.
To establish a VLAN-based BPDU tunnel, one way is to configure devices with different roles
as follows:
1. Configure the type of ISP devices to provider. Thus, the destination MAC addresses of the
BPDUs sent by the ISP network are changed to 01-80-C2-00-00-08 instead of the original
01-80-C2-00-00-00.
2. Configure the type of user network devices to customer. Thus, the destination MAC
addresses of the BPDUs sent by user networks are still 01-80-C2-00-00-00.
3. Configure the BPDUs from CEs to PEs to carry the specified VLAN IDs.
4. Configure the PE interfaces that connect with CEs to permit BPDUs with specified VLAN
ID. The destination MAC addresses of the BPDUs sent by the user networks are 01-80-
C2-00-00-00 instead of 01-80-C2-00-00-08. Thus, the PEs (provider) do not consider the
BPDUs sent from user networks as BPDUs. The PEs choose corresponding BPDU tunnels
to forward the BPDUs based on VLAN IDs instead of delivering the BPDUs to the CPU.
In this way, the BPDUs can go through ISP's Layer 2 switching network.
As shown in Figure 8-4, LAN-A sends BPDUs carrying the VLAN ID of 200. PE1 allows
BPDUs carrying tag 200 to go across the ISP network and through the BPDU tunnel specified
with VLAN ID of 200. Recognizing that the tag is 200, PE2 forwards the BPDUs to LAN-A
that connects PE2, realizing the STP function.
LAN-B sends BPDUs carrying the VLAN ID of 100. PE1 allows BPDUs carrying tag 100 to
go across the ISP network and through the BPDU tunnel specified with VLAN ID of 100.
Recognizing that the tag is 100, PE2 forwards the BPDUs to LAN-B that connects PE2, realizing
the STP function.
Another way is to configure devices with the same role, that is, configure all ISP devices and
user devices as customer. In this way, the difference is that the well-known destination MAC
address of the user BPDU is replaced by a dedicated multicast MAC address on the ISP device
and the ISP interface connected to the user device must be enabled with the BPDU tunnel
function.
QinQ-based BPDU Tunnel

l QinQ overview
The QinQ protocol is a Layer 2 tunnel protocol based on the IEEE 802.1Q technology.The
QinQ technology expands the VLAN space by adding an IEEE 802.1Q tag to a packet
already carrying an 802.1Q tag. As a result, private VLANs can transparently transmit
packets over the public network. This function is the same as the Layer 2 VPN. Packets
that are forwarded over the backbone network carry two 802.1Q tags, one for the public
network and the other for the private network. This is called 802.1Q-in-802.1Q, or QinQ
for short.
As shown in Figure 8-5, following the Source Address (SA), a tag is appended to QinQ
packets; while 802.1Q packets do not contain this tag. This tag is known as the outer tag
or public network tag used for carrying the VLAN ID of the public network. The inner tag
is usually known as the private tag used for carrying the VLAN ID of the private network.
NOTE
The QinQ function configured on a Layer 2 interfaces is called VLAN stacking.

Figure 8-5 IEEE 802.1Q encapsulation and QinQ encapsulation

802.1Q Encapsulation
DA SA ETYPE TAG LEN/ETYPE DATA FCS
6 Bytes 6 Bytes 2 Bytes 2 Bytes 2 Bytes 46 Byte~1500 Bytes 4 Bytes
QinQ
Encapsulation
DA SA ETYPE TAG ETYPE TAG LEN/ETYPE DATA FCS
6 Bytes 6 Bytes 2 Bytes 2 Bytes 2 Bytes 2 Bytes 2 Bytes 46 Byte~1500 Bytes 4 Bytes
0x8100 Priority CFI VLAN ID
l QinQ-based BPDU tunnel
Figure 8-6 QinQ-based BPDU tunnel
LAN-B LAN-B
MSTP MSTP
PE-VLAN20:CE-VLAN 100~199
PE 2
PE 1 ISP Network
CE-VLAN 100 BPDU Tunnel CE-VLAN 100

BPDU Tunnel
PE-VLAN30:CE-VLAN 200~299
LAN-A LAN-A
MSTP MSTP
In the case of many user networks are available, if BPDUs are still transmitted transparently
in the preceding VLAN-based mode, many ISP VLAN IDs are needed. This may result in
insufficient VLAN ID resources. To solve this problem, BPDUs can be forwarded in QinQ
mode on the ISP network.
As shown in Figure 8-6, configure the VLAN-based BPDU tunnel on the convergent
interface of the PE and assign different outer VLAN tags according to CE-VLAN.

1. Add the CE interface on the PE side to the VLAN and configure that the BPDUs sent
from the interface to the PE carry the tag information about the interface.
2. Enable the BPDU tunnel and QinQ functions at the incoming interface (on PE or UPE)
of the Layer 2 switch network.
3. The convergent incoming interface of the PE assigns outer VLAN tags, that is, the
VLAN IDs for the public network (or public VLAN IDs), according to user's VLAN
IDs.
4. The ISP device chooses a BPDU tunnel according to different outer VLAN tags and
forwards user's BPDUs over the public network.
5. Enable the BPDU tunnel and QinQ functions at the exit of the tunnel.
6. At the convergent outgoing interface, the PE removes the outer VLAN tag and decides
to which user network the packets are forwarded according to the user's inner VLAN
ID.
As shown in Figure 8-6, after receiving the BPDUs with the tags ranging from 100 to 199,
the PEs label the BPDUs with the outer tag 20, and then forward the BPDUs in the ISP
network; after receiving the BPDUs with the tags ranging from 200 to 299, the PEs label
the BPDUs with the outer tag 30, and then forward the BPDUs in the ISP network. In this
way, the BPDUs of different user networks can be transparently transmitted in the ISP
network; moreover, less VLAN IDs are occupied.
8.2 Configuring Interface-based BPDU Tunnels

This section describes how to configure the BPDUs from different user networks to be
transparently transmitted on the ISP network when each interface on the user side of a PE is
connected to only one user network.

Interfaces that BPDUs pass through must be Layer 2 interfaces.
An interface of the PE connected with the CE can connect only one user network. The BPDUs
sent from the user network have no VLAN tags.
To enable the BPDUs of the user network in different interfaces to transparently transmit the
ISP network, you can configure interface-based BPDU tunnel. In this way, the BPDUs pass
through the Layer 2 network through different BPDU tunnels, and thus the STP function is
implemented.
Before configuring interface-based tunnel of BPDUs, complete the following tasks:
l Interfaces that the BPDUs pass through must be correctly connected.

l Interfaces that the BPDUs pass through must be Layer 2 interfaces.

Data Preparation
To configure interface-based transparent transmission of BPDUs in a user network, you need
the following data.
No. Data
1 Interface type and interface number of the PE interfaces that connect the user network
2 PVID values of the PE interfaces connecting with each CE
3 VLAN range of the packets that are permitted on the PE interfaces that connect PSN
8.2.2 Enabling STP function on the PEs and the CEs

When the BPDUs sent form user network 1 to PE1 on the ISP network, PE1 cannot identify
where the BPDUs are from, and sends the BPDUs to the CPU for processing and performs STP
calculation.
Context
Do as follows on the PEs and CEs.
Procedure
Step 1 Run:
system-view

Step 2 Run:
stp enable
The STP function is enabled.
----End
8.2.3 Adding the Interfaces of the PE Connected with the CE to a

Specified VLAN
Each interface on a PE connects to one user network. The user networks belong to different
LANs. In this case, the BPDUs sent from the user networks to the PE do not carry tags. The PE,
however, needs to identify which LAN the BPDUs come from. Therefore, you need to configure
specified VLANs.
Context
Procedure
Step 1 Run:
system-view


Step 2 Run:
vlan vlan-id

The VLAN ID ranges from 1 to 4094. If the VLAN specified in the command exists, the VLAN
view is displayed.
Step 3 Run:
The specified Layer 2 interfaces are added to the VLAN.
NOTE
You can also use the port default vlan command to add the PE interfaces connected with the CE to the
VLAN in untagged mode.
----End
8.2.4 Configuring Interface-based BPDU Tunnel

According to the roles of a PE and a CE, you can configure interface-based BPDU tunnels
between devices with the same role or different roles. After the interface-based BPDUs are
successfully configured, the PE adds a tag based on the interface PVID to the received BPDU.
Then, the PE selects a BPDU tunnel according to the tag to transmit the BPDU. Different users
are thus isolated.
Context
According to the roles of the PEs and CEs, choose to configure Devices of Different Roles or
Devices of the Same Role.
Devices of different roles: indicate that CEs are bridges functioning as service customers, and
PEs and Ps are bridges functioning as service providers.
Device of the same role: indicate that CEs and PEs may play the same role as service customers.
Procedure
l Devices of Different Roles
The devices can play different roles; that is, CEs are bridges with the role as customer, and
the PE and P are bridges with the role as provider.
Do as follows on the PE and P.
1. Run:
system-view

2. Run:
bpdu-tunnel stp bridge role provider
The role of the PE is configured as provider.

3. Run:

The view of the PE interface on CE side is displayed.

4. (Optional)Run:
stp disable
The PE interface on CE side does not take part in the spanning tree calculation (STP).
The STP function is disabled.
NOTE
After the devices are configured with different roles, PEs can transparently transmit the BPDUs from
CEs without the BPDU tunnel function.
l Devices of the Same Role
CEs and PEs may play the same role as customer.
Do as follows on the PEs:
1. Run:
system-view

2. Run:
bpdu-tunnel stp group-mac group-mac
The MAC address of the BPDU is replaced with a multicast address.

The global well-known MAC address can be replaced only by the multicast MAC
address except the reserved MAC addresses ranging from 0180-C200-0000 to 0180-
C200-002F.
By default, the multicast destination MAC address of a BPDU is 0100-0ccd-cdd0.
3. Run:
The view of the PE interface on user side is displayed.

4. Run:
bpdu-tunnel enable
The function of transparent transmission of user-network BPDUs is enabled on the

PE interface.
5. Run:
stp disable
The PE interface on CE side does not take part in the STP. The STP function is
disabled.
NOTE
If the devices play the same role, PEs cannot transparently transmit the BPDUs from CEs without
the BPDU tunnel function.
In this scenario, no special configuration is required for the P.
----End
8.2.5 Configuring PE Interfaces Connecting PSNs to Permit Packets

with Specified Tags
Different users can communicate only when interfaces on PEs connecting to PSNs are configured
to allow packets with specified tags to pass through.

Context
Do as follows on the PEs.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the PE interface that connects the PSN is displayed.

Step 3 Run:
The PE interface that connects PSNs is configured to permit the packets with specified tags.
----End

After interface-based BPDU tunnels are successfully configured, you can view the roles of the
interfaces on CEs and whether STP is enabled on the interfaces.
Prerequisite
The configurations of interface-based BPDU tunnels function are complete.
Procedure
Step 1 Run the display stp [ brief ] command to check the information on the spanning tree.
----End
Example
Run the display stp [ brief ] command on the CEs, and you can view that STP is enabled on the
interface and the roles of the CE interfaces are correct: "Designated" or "Root". For example:
<CE1> display stp
-------[CIST Global Info] [Mode MSTP] -------
CIST Bridge :32768.00e0-fc9f-3257
CIST Root/ERPC :32768.00e0-fc9a-4315 / 199999
CIST RegRoot/IRPC :32768.00e0-fc9f-3257 / 0
Time since last TC received :0 days 2h:24m:36s
----[Port1(GigabitEthernet1/0/0)] [FORWARDING] ----
Port Role :CIST Root Port
Port Priority :128
Desg. Bridge/Port :32768.00e0-fc9a-4315 / 128.82


BPDU Sent :6
BPDU Received :4351
<CE2> display stp
CIST Bridge :32768.00e0-fc9a-4315
CIST RegRoot/IRPC :32768.00e0-fc9a-4315 / 0
Port Priority :128
BPDU Sent :4534
BPDU Received :6
8.3 Configuring VLAN-based BPDU Tunnels

need to carry tags to differentiate user networks. To enable the BPDUs sent from user networks
to be transparently transmitted on the ISP network, you can configure VLAN-based BPDU
tunnels.

When an interface of the PE is connected with multiple user VLANs, the BPDUs sent from the
CE must carry VLAN tags to distinguish different users. To realize the transparent transmission
of user-network BPDUs in an ISP network, you need to configure VLAN-based BPDU tunnels.
After the configuration, BPDUs of different user networks are transmitted through different
BPDU tunnels in an ISP network and then reach the destination network. The STP function is
realized at the same time.
Before configuring VLAN-based tunnel of BPDUs, complete the following tasks:


Data Preparation
To configure VLAN-based transparent transmission of BPDUs, you need the following data.
No. Data
1 Name of the interfaces of the CE on which the STP function is enabled
2 Tag values of the BPDUs sent from the CE to the PE
3 VLAN range of the packets that are permitted on the PE
8.3.2 Enabling the STP Function on CEs and PEs

BPDUs from different user networks are transmitted through different BPDU tunnels in an ISP
network and then reach the destination network. The STP calculation is thus performed.
Context
Do as follows on the PEs and CEs.
Procedure
Step 1 Run:
system-view

Step 2 Run:
stp enable
----End
8.3.3 Configuring BPDUs from CEs to PEs to Carry Specified Tags

When multiple user networks are connected to the same interface on a PE, the BPDUs that are
sent from the CEs to the PE need to carry specified VLAN IDs to differentiate the user networks
that the BPDUs come from.
Context
Do as follows on the CE.
Procedure
Step 1 Run:
system-view


Step 2 Run:
vlan vlan-id

The VLAN ID ranges from 1 to 4094.
To create more than one VLAN, repeat this step.
Step 3 Run:
quit

Step 4 Run:
The view of the CE interface that connects the PEs is displayed.

Step 5 Run:
The CE allows BPDUs of the specified VLANs to pass through.

Step 6 Run:
stp bpdu vlan vlan-id
The VLAN tag value of the BPDUs sent from the CE to the PE is configured.
The VLAN ID specified in the command must exist on the local CE.
NOTE
Ensure that the BPDU packets received by this interface also carry the specified tags.
----End
8.3.4 Configuring VLAN-based BPDU Tunnel

According to the roles of a PE and a CE, you can configure interface-based BPDU tunnels
between devices with the same role or different roles. After the interface-based BPDU tunnels
are successfully configured, the BPDUs are not sent to the CPU for processing. Instead, the
BPDUs cross the Layer 2 network along the BPDU tunnels, destined for user networks.
Context
Procedure
Do as follows on the PE and P:

1. Run:
system-view

2. Run:

3. Run:
The view of the PE interface that connects CEs is displayed.

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

5. Run:
VLAN range of the packets that are permitted on the PE is configured.

6. (Optional) Run:
stp disable
disabled.
NOTE
After the devices are configured with different roles, PEs can transparently transmit the BPDUs from
CEs without the BPDU tunnel function.
1. Run:
system-view

2. Run:
The MAC address of the BPDU is replaced.
C200-002F.

3. Run:

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

The function of transparent transmission of BPDUs with specified tags is enabled on

the PE interface.
5. Run:
VLAN range of the packets that are permitted on the PE is configured.

6. Run:
stp disable
disabled.
NOTE
If the devices play the same role, PEs cannot transparently transmit the BPDUs from CEs without
the BPDU tunnel function.
----End
8.3.5 Configuring PE Interfaces Connecting PSN to Permit Packets

with Specified Tags
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
The interface is a PE interface connected to PSN.
Step 3 Run:
----End

After the interface-based BPDU tunnels are successfully configured, you can view the
configuration of the BPDU tunnels on the interfaces, spanning tree information, and the roles
of the interfaces on CEs.

Prerequisite
The configurations of VLAN-based BPDU tunnels function are complete.
Procedure
l Run the display bpdu-tunnel interface config command to check the BPDU Tunnel
configuration in the interface view.
l Run the display bpdu-tunnel global config command to check the global configuration
of BPDU Tunnel.
l Run the display stp [ brief ] command to check information on the spanning tree.
NOTE
l The display bpdu-tunnel interface config command can be displayed in the system view only.
l The display bpdu-tunnel global config command can be displayed in the interface view only.
----End
Example
Run the display bpdu-tunnel global config command on PE. The role of the device on the
network and the multicast MAC addresses of the BPDUs generated by STP are displayed. For
example:
[HUAWEI] display bpdu-tunnel global config
BridgeRole customer
GroupMac 0100-0ccd-cdd0
Run the display bpdu-tunnel interface config command on the CE. The BPDUs sent out from
the CE are with a specific tag value. The interfaces of the PEs allow the BPDUs with specified
tag values to pass through. For example:
BpduTwoQStatus enable
EtherType 8100
Dot1qVlan
TwoQList 10
Run the display stp command on the CEs, and you can view that STP is enabled on the interface
and the roles of the CE interfaces are correct: "Designated" or "Root". For example:
<CE1> display stp
Port Priority :128


BPDU Sent :6
BPDU Received :4351
<CE2> display stp
Port Priority :128
BPDU Sent :4534
BPDU Received :6
8.4 Configuring QinQ-based BPDU Tunnels

need to carry tags to differentiate user networks. To enable the BPDUs from user networks to
be transparently transmitted on the ISP network, and to save the VLAN ID resources of the ISP,
you can configure QinQ-based BPDU tunnels.

When an interface of the PE is connected with multiple user VLANs, the BPDUs sent from the
CE must carry VLAN tags to distinguish different users.
At the same time, to save the VLAN ID of the public network, the PE adds another tag to the
BPDUs received from the CE. The ISP network assigns different BPDU tunnels for the users
according to the outer VLAN tag of the BPDUs. In this way, the BPDUs from different VLANs
traverse the ISP network to the peer VLAN through different BPDU tunnels.
Before configuring tunnel of BPDUs based on QinQ, complete the following tasks:


Data Preparation
To configure tunnel of BPDUs based on QinQ, you need the following data.
No. Data
1 Name of the interfaces on which the STP function is enabled
2 The VLAN tag value of the BPDUs sent from the CE to the PEs
3 VLAN IDs that the interface of the PE allows
4 The outer VLAN tag value that the PE adds to the BPDUs sent from the CE
8.4.2 Enabling the STP Function on CEs and PEs

BPDUs from different user networks are transmitted through different BPDU tunnels in an ISP
network and then reach the destination network. The STP calculation is thus performed.
Procedure
Step 1 Run:
system-view
Step 2 Run:
stp enable
----End
8.4.3 Configuring the BPDUs from CEs to PEs to Carry the Specified
Tags
When multiple user networks are connected to the same interface on a PE, the BPDUs that are
sent from the CEs to the PE need to carry specified VLAN IDs to differentiate the user networks
that the BPDUs come from.
Context
Do as follows on the CE.
Procedure
Step 1 Run:
system-view


Step 2 Run:
vlan vlan-id

The VLAN ID ranges from 1 to 4094.
To create more than one VLAN, repeat this step.
Step 3 Run:
quit

Step 4 Run:
The view of the CE interface that connects the PEs is displayed.

Step 5 Run:
The VLAN ID that the CE allows is configured.

Step 6 Run:
stp bpdu vlan vlan-id
The ID values of the BPDUs sent to the PE are configured.

The VLAN ID specified in the command must exist on the local CE.
NOTE
Ensure that the BPDU packets received by this interface also carry the specified tags.
----End
8.4.4 Configuring QinQ-based BPDU Tunnel

According to the roles of a PE and a CE, you can configure QinQ-based BPDU tunnels between
devices with the same role or different roles. After the QinQ-based BPDU tunnels are
successfully configured, the BPDUs are not sent to the CPU for processing. Instead, the BPDUs
cross the Layer 2 network along the BPDU tunnels, destined for user networks. At the same
time, the VLAN ID resources of the ISP are saved.
Context
Procedure

Do as follows on the PE and P.
1. Run:
system-view

2. Run:

3. Run:

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

5. Run:
port vlan-stacking vlan vlan-id1 [ to vlan-id2 ] stack-vlan vlan-id3
The BPDUs received on the PE are labeled with outer tags.

6. (Optional) Run:
stp disable
The PE interface on the CE side does not take part in the STP. The STP function is
disabled.
Do as follows on the PEs.
1. Run:
system-view

2. Run:
The MAC address of the BPDU is replaced.
C200-002F.

3. Run:

4. Run:
port vlan-stacking vlan vlan-id1 [ to vlan-id2 ] stack-vlan vlan-id3
The BPDUs received on the PE are labeled with outer tags.

5. Run:
bpdu-tunnel stp vlan vlan-id1 [ to vlan-id2 ]
The function of transparent transmission of BPDUs with specified tags is enabled on

the PE interface.
The VLAN tag range must contain the inner tag of the BPDU in Step 4, namely,
vlan.
6. Run:
stp disable
The PE interface on the CE side does not take part in the STP. The STP function is
disabled.
NOTE
----End
8.4.5 Configuring PE Interfaces Connecting PSNs to Permit the

Packets with Specified Tags
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
The view of the PE interface that connects the PSN is displayed.
Step 3 Run:
The configured tag value must be the same as the outer tag of the BPDU labeled by the PE.
----End

After the QinQ-based BPDU tunnels are successfully configured, you can view the configuration
of the BPDU tunnels on the interfaces, spanning tree information, and the roles of the interfaces
on CEs.

Prerequisite
The configurations of QinQ-based BPDU tunnels.
Procedure
l Run the display bpdu-tunnel interface config command to check the BPDU Tunnel
configuration in the interface view.
l Run the display bpdu-tunnel global config command to check the global configuration
of BPDU Tunnel.
l Run the display stp [ brief ] command to check the information on the spanning tree.
l Run the display vlan [ vlan-id [ verbose ] ] command to check the VLAN information.
NOTE
l The display bpdu-tunnel global config command can be displayed in the system view only.
l The display bpdu-tunnel interface config command can be displayed in the interface view only.
----End
Example
Run the display bpdu-tunnel global config command on PE. The role of the device on the
network and the multicast MAC addresses of the BPDUs generated by STP are displayed. For
example:
[HUAWEI] display bpdu-tunnel global config
BridgeRole customer
GroupMac 0100-0ccd-cdd0
Run the display bpdu-tunnel interface config command on the CE. The BPDUs sent out from
the CE are with a specific tag value. The interfaces of the PEs allow the BPDUs with specified
tag values to pass through. For example:
BpduTwoQStatus enable
EtherType 8100
Dot1qVlan
TwoQList 10
Run the display stp [ brief ] command on the CEs, and you can view that STP is enabled on the
interface and the roles of the CE interfaces are correct: "Designated" or "Root". For example:
<CE1> display stp
Port Priority :128


BPDU Sent :6
BPDU Received :4351
<CE2> display stp
Port Priority :128
BPDU Sent :4534
BPDU Received :6
Running the display vlan command, you can find whether VLAN is enabled with broadcast,
and whether VLAN and address learning are enabled.
For example:
VLAN ID : 2
VLAN Type : Common
Status : Enable
Broadcast : Enable
----------------
Untagged Port: Eth-Trunk1 Eth-Trunk2

This section describes the typical application scenarios of various types of BPDU tunnels,
including networking requirements, configuration roadmap, and data preparation, and provides
related configuration files.
NOTE

8.5.1 Example for Configuring Interface-based BPDU Tunnel

(Devices of Different Roles)
This example shows how to configure interface-based BPDU tunnels when CEs are configured
as Customer and PEs are configured as Provider.
As shown in Figure 8-7, the CEs are connected through the PEs. The BPDUs of the CEs are
required to traverse the ISP network between the PEs. For each interface of a PE, only one CE
accesses the PE. The BPDUs sent from CEs to PEs, therefore, do not require tags. In this situation,
interface-based BPDU tunnels can be configured to meet the networking requirements.
In this example, the CEs and the PEs are configured with different roles, and the PEs can
transparently transmit the BPDUs from the CEs.
l The role of CEs is configured as customer. The default MAC address of the BPDUs of the
CEs is 0180-C200-0000.
l The role of PEs is configured as provider. The default MAC address of the BPDUs of the
CEs is 0180-C200-0008.
Figure 8-7 Networking diagram of interface-based BPDU tunnels (devices of different roles)
VLAN100 VLAN100
CE1 CE2
GE 1/0/1 PE1 PE2 GE1/0/1
GE 1/0/3 ISP GE 1/0/3
GE 1/0/1 network GE 1/0/1
GE 1/0/2 GE 1/0/2
GE 1/0/1 GE 1/0/1 CE4
CE3
VLAN200
VLAN200
1. Enable the STP function on the CEs and the PEs.

2. Add the PE interfaces that connect CEs into the specified VLAN.
3. (Optional) Disable the STP function of the PE interfaces that connect CEs. Then the PE
interfaces that connect CEs do not participate in the calculation of the spanning tree.

Configure PEs as the bridge devices in Provider mode to transparently transmit BPDU
packets.
4. Configure the PE interfaces that connect PSNs permit the VLAN100 and VLAN200
packets.
Data Preparation
l ID of the VLAN to which the PE interfaces that connect CEs belong
l VLAN range of the packets that are permitted on the PE interfaces that connect PSN
Procedure
Step 1 Switch the PE interfaces and CE interfaces to Layer 2 interfaces.
NOTE
# Configure CE1.
# Configure CE2.
# Configure CE3.
# Configure CE4.
# Configure PE1.

# Configure PE2.
Step 2 Enable the STP function on the CEs and the PEs.
# Configure CE1.
[CE1] stp enable
# Configure CE2.
[CE2] stp enable
# Configure CE3.
[CE3] stp enable
# Configure CE4.
[CE4] stp enable
# Configure PE1.
[PE1] stp enable
# Configure PE2.
[PE2] stp enable
Step 3 Configure the role of the PEs as a provider.

# Configure PE1.
[PE1] bpdu-tunnel stp bridge role provider
# Configure PE2.
Step 4 Add GE 1/0/3 of PE1 and PE2 into VLAN100. Add GE 1/0/1 of PE1 and PE2 into VLAN200.
Disable the STP function of the PE interfaces that connect CEs.
# Configure PE1.
[PE1] vlan 100
[PE1-vlan100] port gigabitethernet 1/0/3
[PE1-vlan100] quit

[PE1] vlan 200

[PE1-vlan200] quit
[PE1-GigabitEthernet1/0/3] stp disable
# Configure PE2.
[PE2] vlan 100
[PE2-vlan100] quit
[PE2] vlan 200
[PE2-vlan200] quit
Step 5 Configure the PE interface that connects PSNs, namely, GE 1/0/2 to permit the VLAN100 and
VLAN200 packets.
# Configure PE1.
[PE1-GigabitEthernet1/0/2] port trunk allow-pass vlan 100 200
# Configure PE2.
Step 6 Check the configuration.

After the configuration, running the display stp command on CE1 and CE2, you can check the
MSTP root. CE1 and CE2 calculate the spanning tree. GE 1/0/1 on CE1 is the root port; GE
1/0/1 on CE2 is the designated port.
[CE1] display stp
Port Priority :128
BPDU Sent :6


BPDU Received :4351
[CE2] display stp
Port Priority :128
BPDU Sent :4534
BPDU Received :6
Running the display stp command on CE3 and CE4, you can check the MSTP root. CE3 and
CE4 calculate the spanning tree. GE 1/0/1 on CE3 is the root port; GE 1/0/1 on CE4 is the
designated port.
[CE3] display stp
CIST Bridge :32768.000b-0967-58a0
CIST Root/ERPC :32768.000b-0952-f13e / 199999
CIST RegRoot/IRPC :32768.000b-0967-58a0 / 0
Port Priority :128
Desg. Bridge/Port :32768.000b-0952-f13e / 128.82
BPDU Sent :114
BPDU Received :885
[CE4] display stp
CIST Bridge :32768.000b-0952-f13e
CIST RegRoot/IRPC :32768.000b-0952-f13e / 0


Port Priority :128
BPDU Sent :1834
BPDU Received :1
----End
Configuration Files
#
sysname CE1
#
stp enable
#
undo shutdown
portswitch
#
return

#
sysname CE2
#
stp enable
#
undo shutdown
portswitch
#
return

#
sysname CE3
#
stp enable
#
undo shutdown
portswitch
#
return

#
sysname CE4
#
stp enable
#
undo shutdown
portswitch
#

return

#
sysname PE1
#
vlan batch 100 200
#
#
stp enable
#
undo shutdown
portswitch
stp disalbe
#
undo shutdown
portswitch
#
undo shutdown
portswitch
stp disalbe
#
return

#
sysname PE2
#
vlan batch 100 200
#
#
stp enable
#
undo shutdown
portswitch
stp disalbe
#
undo shutdown
portswitch
#
undo shutdown
portswitch
stp disalbe
#
return
8.5.2 Example for Configuring Interface-based BPDU Tunnel

(Devices of the Same Role)
This example shows how to configure interface-based BPDU tunnels when CEs and PEs are
configured as Customer.

As shown in Figure 8-8, the CEs are connected through the PEs. The BPDUs of the CEs are
required to traverse the ISP network between the PEs. For each interface of a PE, only one CE
accesses the PE. The BPDUs sent from CEs to PEs, therefore, do not require tags. In this situation,
interface-based BPDU tunnels can be configured to meet the networking requirements.
The roles of the CEs and the PEs are configured as customer. The default MAC address of the
BPDUs is 0180-C200-0000. The PEs cannot transparently transmit the BPDUs received from
the CEs. Thus, to meet the networking requirements, the PE devices must be enabled with the
BPDU tunnel function.
Figure 8-8 Networking diagram of interface-based BPDU tunnels (device of the same role)
VLAN100 VLAN100
CE1 CE2
GE1/0/1 GE1/0/1
PE1 ISP PE2
GE1/0/3 network GE1/0/3
GE1/0/1 GE1/0/1
GE1/0/2 GE1/0/2
GE1/0/1
GE1/0/1 CE4
CE3
VLAN200
VLAN200
2. Add the PE interfaces that connect CEs into the specified VLAN.
3. Disable the STP function of the PE interfaces that connect CEs. Then the PE interfaces that
connect CEs do not participate in the calculation of the spanning tree. Enable the BPDU
tunnel function on PEs.
packets.
Data Preparation
l ID of the VLAN to which the PE interfaces that connect CEs belong

l VLAN range of the packets that are permitted on the PE interfaces that connect PSN
Procedure
NOTE
# Configure CE1.
# Configure CE2.
# Configure CE3.
# Configure CE4.
# Configure PE1.
# Configure PE2.


# Configure CE1.
[CE1] stp enable
# Configure CE2.
[CE2] stp enable
# Configure CE3.
[CE3] stp enable
# Configure CE4.
[CE4] stp enable
# Configure PE1.
[PE1] stp enable
# Configure PE2.
[PE2] stp enable
Step 3 Configure the PEs to replace the MAC addresses of the BPDUs received from the CEs.
# Configure PE1.
[PE1] bpdu-tunnel stp group-mac 0100-5e00-0011
# Configure PE2.
Step 4 Add GE 1/0/3 of PE1 and PE2 into VLAN100. Add GE 1/0/1 of PE1 and PE2 into VLAN200.
Disable the STP function of the PE interfaces that connect CEs.
# Configure PE1.
[PE1] vlan 100
[PE1-vlan100] quit
[PE1] vlan 200
[PE1-vlan200] quit
[PE1-GigabitEthernet1/0/3] bpdu-tunnel enable
# Configure PE2.
[PE2] vlan 100


[PE2-vlan100] quit
[PE2] vlan 200
[PE2-vlan200] quit
Step 5 Configure the PE interface that connects PSNs, namely, GE 1/0/2 to permit the VLAN100 and
VLAN200 packets.
# Configure PE1.
# Configure PE2.

MSTP root. CE1 and CE2 calculate the spanning tree. The GE1/0/1 on CE1 is the root port; the
GE1/0/1 on CE2 is the designated port.
[CE1] display stp
Port Priority :128
BPDU Sent :6
BPDU Received :4351
[CE2] display stp

Port Priority :128
BPDU Sent :4534
BPDU Received :6
CE4 calculate the spanning tree. The GE1/0/1 on CE3 is the root port; the GE1/0/1 on CE4 is
the designated port.
[CE3] display stp
CIST Bridge :32768.000b-0967-58a0
CIST RegRoot/IRPC :32768.000b-0967-58a0 / 0
Port Priority :128
BPDU Sent :114
BPDU Received :885
[CE4] display stp
CIST Bridge :32768.000b-0952-f13e
CIST RegRoot/IRPC :32768.000b-0952-f13e / 0
Port Priority :128


BPDU Sent :1834
BPDU Received :1
----End
Configuration Files
#
sysname CE1
#
stp enable
#
undo shutdown
portswitch
#
return

#
sysname CE2
#
stp enable
#
undo shutdown
portswitch
#
return

#
sysname CE3
#
stp enable
#
undo shutdown
portswitch
#
return

#
sysname CE4
#
stp enable
#
undo shutdown
portswitch
#
return

#
sysname PE1
#
vlan batch 100 200
#
bpdu-tunnel stp group-mac 0100-5e00-0011
#
stp enable

#
undo shutdown
portswitch
bpdu-tunnel enable
stp disalbe
#
undo shutdown
portswitch
#
undo shutdown
portswitch
bpdu-tunnel enable
stp disalbe
#
return

#
sysname PE2
#
vlan batch 100 200
#
#
stp enable
#
undo shutdown
portswitch
bpdu-tunnel enable
stp disalbe
#
undo shutdown
portswitch
#
undo shutdown
portswitch
bpdu-tunnel enable
stp disalbe
#
return
8.5.3 Example for Configuring VLAN-based Tunnel of BPDUs

In this example, PEs usually serve as convergence devices. The convergence interfaces on a PE
may receive packets from different users. To differentiate these users, each CE adds different
VLAN IDs to the packets of different users to implement VLAN-based BPDU tunnels.
As shown in Figure 8-9, the CEs are connected to the PEs. The BPDUs of the CEs are required
to traverse the ISP network between the PEs. The BPDUs sent from CEs to PEs must carry tags
because the PE interfaces are convergence interfaces. In this networking mode, configuring
VLAN-based BPDU tunnels can achieve the following results:

l All devices in VLAN100 can participate in the STP calculation.

The roles of the CEs and the PEs are configured as customer. The default MAC address of the
BPDUs is 0180-C200-0000. The PEs cannot transparently transmit the BPDUs received from
the CEs. Thus, to meet the networking requirements, the PE devices must be enabled with the
BPDU tunnel function.
Figure 8-9 Typical networking diagram of configuring VLAN-based transparent transmission

of BPDUs
PE1 P PE2
GE1/0/3 GE1/0/3
GE1/0/2 GE1/0/1
GE1/0/1 GE1/0/2 GE1/0/1 GE1/0/2
GE1/0/1 GE1/0/1 GE1/0/1 GE1/0/1

CE1 CE3 CE2 CE4
2. Configure the BPDUs from CEs to PEs to carry tags.
packets.
5. Configure the common Layer 2 forwarding function on the P. Permit the packets between
PEs can be transmitted in the ISP network.
Data Preparation
l Tag values of the BPDUs sent from the CEs to the PEs
l IDs of the VLANs to which the PE interfaces and the CE interfaces belong
Procedure
Using the portswitch command, you can switch all PE interfaces and CE interfaces in Figure
8-9 to Layer 2 interfaces.

NOTE
This step is not required for devices with Layer 2 interfaces.
Step 2 Enable the STP function on the CEs and PEs.

# Configure CE1
[CE1] stp enable
# Configure CE2
[CE2] stp enable
# Configure CE3
[CE3] stp enable
# Configure CE4
[CE4] stp enable
# Configure PE1
[PE1] stp enable
# Configure PE2
[PE2] stp enable
Step 3 Label the BPDUs sent from CE1 and CE2 to the PEs with tag 100. Label the BPDUs sent from
CE3 and CE4 to the PEs with tag 200.
# Configure CE1.
[CE1] vlan 100
[CE1-vlan100] quit
[CE1-GigabitEthernet1/0/1] stp bpdu vlan 100
# Configure CE2.
[CE2] vlan 100
[CE2-vlan100] quit
# Configure CE3.
[CE3] vlan 200
[CE3-vlan200] quit
# Configure CE4.
[CE4] vlan 200
[CE4-vlan200] quit
Step 4 Configure the PEs to replace the MAC addresses of the BPDUs received from the CEs.
# Configure PE1.

# Configure PE2.
Step 5 Configure the PE interfaces to transparently transmit BPDUs received from the CEs to the P.
# Configure PE1.
[PE1] vlan 100
[PE1-vlan100] quit
[PE1] vlan 200
[PE1-vlan200] quit
[PE1-GigabitEthernet1/0/1] bpdu-tunnel stp vlan 100
# Configure PE2.
[PE2] vlan 100
[PE2-vlan100] quit
[PE2] vlan 200
[PE2-vlan200] quit
Step 6 Configure the common Layer 2 forwarding function on the P. Configure the P to permit
VLAN100 packets and VLAN200 packets from the PEs.
[P] vlan 100
[P-vlan100] quit
[P] vlan 200
[P-vlan200] quit
[P-GigabitEthernet1/0/2] port trunk allow-pass vlan 100 200
[P-GigabitEthernet1/0/1] port trunk allow-pass vlan 100 200

[CE1] display stp
CIST Bridge :32768.000b-09f0-1b91


CIST Root/ERPC :32768.000b-09d4-b66c / 199999
CIST RegRoot/IRPC :32768.000b-09f0-1b91 / 0
----[Port17(GigabitEthernt1/0/1)][FORWARDING]----
Port Priority :128
Desg. Bridge/Port :32768.000b-09d4-b66c / 128.82
BPDU Sent :237
BPDU Received :9607
[CE2] display stp
CIST Bridge :32768.000b-09d4-b66c
CIST RegRoot/IRPC :32768.000b-09d4-b66c / 0
Port Priority :128
BPDU Sent :7095
BPDU Received :2
designated port.
[CE3] display stp
Port Priority :128


BPDU Sent :238
BPDU Received :9745
[CE4] display stp
Port Priority :128
BPDU Sent :7171
BPDU Received :2
----End
Configuration Files
#
sysname CE1
#
vlan batch 100
#
stp enable
#
undo shutdown
portswitch
stp bpdu vlan 100
#
return

#
sysname CE2
#
vlan batch 100
#
stp enable
#
undo shutdown

portswitch
stp bpdu vlan 100
#
return

#
sysname CE3
#
vlan batch 200
#
stp enable
#
undo shutdown
portswitch
stp bpdu vlan 200
#
return

#
sysname CE4
#
vlan batch 200
#
stp enable
#
undo shutdown
portswitch
stp bpdu vlan 200
#
Return

#
sysname PE1
#
vlan batch 100 200
#
#
stp enable
#
undo shutdown
portswitch
bpdu-tunnel stp vlan 100
stp disalbe
#
undo shutdown
portswitch
stp disalbe
#
undo shutdown
portswitch
#
return

l Configuration file of the P

#
sysname P
#
vlan batch 100 200
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
return

#
sysname PE2
#
vlan batch 100 200
#
#
stp enable
#
undo shutdown
portswitch
stp disalbe
#
undo shutdown
portswitch
stp disalbe
#
undo shutdown
portswitch
#
return
8.5.4 Example for Configuring Tunnel of BPDUs Based on QinQ

In this example, PEs usually serve as convergence devices. PEs may be connected to a large
number of user networks. To save the VLAN ID resources of the ISP and to differentiate users,
each CE adds different VLAN IDs to the packets of different users, and each PE adds different
outer VLAN IDs based on the inner VLAN IDs. QinQ-based BPDU tunnel is thus implemented.
As shown in Figure 8-10, the CEs are connected through the PEs. The BPDUs sent from CE1
and CE2 to the PEs carry tag 100. The BPDUs sent from CE3 and CE4 to the PEs carry tag 200.
In this networking mode, configuring the BPDU tunnel function on the PEs can achieve the
following results:


In addition, to save public VLAN IDs, VLAN stacking can be configured on the PEs. After the
configuration, the BPDUs with tag 100 and tag 200 sent from the CEs to the PEs are labeled
with outer tag 10 and then transmitted in the ISP network. The BPDUs transmitted in the ISP
network, thus, carry double tags.
In this example, the CEs and PEs are configured with different roles:
l The role of CEs is configured as customer. The default MAC address of the BPDUs of the
CEs is 0180-C200-0000.
l The role of PEs is configured as provider. The default MAC address of the BPDUs of the
CEs is 0180-C200-0008.
Figure 8-10 Networking diagram of QinQ-based BPDU tunnels
VLAN100
VLAN100
CE1 CE2
GE1/0/1 PE1 PE2 GE1/0/1

GE1/0/1
GE1/0/3 ISP GE1/0/3
GE1/0/1
network
GE1/0/2 GE1/0/2
GE1/0/1 GE1/0/1
CE3 CE4
VLAN200 VLAN200
2. Configure the BPDUs from CEs to PEs to carry tags.
4. Configure the VLAN stacking function on the Layer 2 interfaces of the PEs. Label the
BPDUs with different tag values sent from the CEs with outer tag 10 and before the BPDUs
are transmitted in the ISP network.
Data Preparation

l Inner tag values of the BPDUs sent from the CEs to the PEs
l Outer tag of the BPDUs added by the PEs
l IDs of the VLANs to which the PE interfaces and the CE interfaces belong
Procedure
Using the portswitch command, you can switch all PE interfaces and CE interfaces in Figure
8-10 to Layer 2 interfaces.
NOTE
This step is not required for devices with Layer 2 interfaces.
# Configure CE1.
[CE1] stp enable
# Configure CE2.
[CE2] stp enable
# Configure CE3.
[CE3] stp enable
# Configure CE4.
[CE4] stp enable
# Configure PE1.
[PE1] stp enable
# Configure PE2.
[PE2] stp enable
Step 3 Label the BPDUs sent from CE1 and CE2 to the PEs with tag 100. Label the BPDUs sent from
CE3 and CE4 to the PEs with tag 200.
# Configure CE1.
[CE1] vlan 100
[CE1-vlan100] quit
# Configure CE2.
[CE2] vlan 100
[CE2-vlan100] quit
# Configure CE3.
[CE3] vlan 200
[CE3-vlan200] quit


# Configure CE4.
[CE4] vlan 200
[CE4-vlan200] quit
Step 4 Configure the role of the PEs as provider.

# Configure PE1.
# Configure PE2.
Step 5 Configure the QinQ function of the PEs. Label the VLAN100 packets and VLAN200 packets
from the CEs with tag 10 before the packets are transmitted in the PSN network.
# Configure PE1.
[PE1] vlan 10
[PE1-Vlan10] quit
[PE1-GigabitEthernet1/0/1] port vlan-stacking vlan 100 stack-vlan 10
# Configure PE2.
[PE2] vlan 10
[PE2-Vlan10] quit

[CE1] display stp
CIST Bridge :32768.000b-09f0-1b91


CIST RegRoot/IRPC :32768.000b-09f0-1b91 / 0
Port Priority :128
BPDU Sent :237
BPDU Received :9607
[CE2] display stp
CIST Bridge :32768.000b-09d4-b66c
CIST RegRoot/IRPC :32768.000b-09d4-b66c / 0
Port Priority :128
BPDU Sent :7095
BPDU Received :2
designated port.
[CE3] display stp
Port Priority :128


BPDU Sent :238
BPDU Received :9745
[CE4] display stp
Port Priority :128
BPDU Sent :7171
BPDU Received :2
Running the display vlan command on the PEs, you can view information about QinQ.
Take PE1 as an example.
[PE1] display vlan 10 verbose
VLAN ID : 10
VLAN Type : Common
Status : Enable
Broadcast : Enable
----------------
Tagged Port: GigabitEthernet1/0/3
----------------
QinQ-stack Port: GigabitEthernet1/0/1 GigabitEthernet1/0/2
----End
Configuration Files
#
sysname CE1
#
vlan batch 100
#
stp enable
#
undo shutdown

portswitch
stp bpdu vlan 100
#
return

#
sysname CE2
#
vlan batch 100
#
stp enable
#
undo shutdown
portswitch
stp bpdu vlan 100
#
return

#
sysname CE3
#
vlan batch 200
#
stp enable
#
undo shutdown
portswitch
stp bpdu vlan 200
#
return

#
sysname CE4
#
vlan batch 200
#
stp enable
#
undo shutdown
portswitch
stp bpdu vlan 200
#
return

#
sysname PE1
#
#
stp enable
#
undo shutdown
portswitch
stp disalbe
#

undo shutdown
portswitch
stp disalbe
#
undo shutdown
portswitch
#
return

#
sysname PE2
#
#
stp enable
#
undo shutdown
portswitch
stp disalbe
#
undo shutdown
portswitch
stp disalbe
#
undo shutdown
portswitch
#
return

Configuration Guide - LAN Access and MAN Access 9 RRPP Configuration
9 RRPP Configuration
About This Chapter
The Rapid Ring Protection Protocol (RRPP) features fast convergence, because the convergence
time is irrelevant to the number of the nodes on the ring.
9.1 RRPP Introduction

To shorten the convergence time and reduce the impact of the network size on convergence
speed, Huawei has developed RRPP, which is a link layer protocol applied to an Ethernet ring.
9.2 Configuring RRPP Functions
Through RRPP, devices on an Ethernet ring are configured to be the nodes with different roles
on RRPP rings. The nodes on an RRPP ring detect the ring status and transmit topology changes
by sending and receiving RRPP protocol packets. The master node on an RRPP ring blocks or
opens secondary ports according to the ring status. In this manner, if a fault occurs on a node or
a link on the RRPP ring, traffic can be fast switched to the backup link and data loops can be
prevented.
9.3 Configuring the Monitoring Interface
A monitoring interface is used in the networking scheme where master and backup NPEs
connected to RRPP rings support fast switching of Layer 2 services. When the status of the
monitoring interface or the status of the BFD session changes, the node where the monitoring
interface resides clears the dynamic MAC entries, and meanwhile sends a COMMON-FLUSH-
FDB packet to notify other nodes on the RRPP ring to clear their dynamic MAC entries.
9.4 Configuring RRPP Snooping
RRPP Snooping is a technology through which changes on an RRPP ring can be notified to a
VPLS network. When RRPP Snooping is configured on sub-interfaces or VLANIF interfaces,
the VPLS network can transparently transmit RRPP protocol packets, detect the changes on the
RRPP rings, and upgrade the forwarding entries to ensure that traffic is switched in time to a
congestion-free path.
9.5 Maintaining RRPP
Commands of clearing statistics helps to locate the RRPP faults on a device.

This section describes the typical application scenario of RRPP, including networking
files.

9.1 RRPP Introduction

To shorten the convergence time and reduce the impact of the network size on convergence
speed, Huawei has developed RRPP, which is a link layer protocol applied to an Ethernet ring.
9.1.1 Overview of RRPP

RRPP is a link layer protocol applied to an Ethernet ring. RRPP features fast convergence and
can prevent broadcast storms caused by data loops.
For most MANs and LANs, the ring network is adopted to provide high reliability. A fault of
any single node on the ring, however, affects the service. In general, the technology of the ring
network is the Resilient Packet Ring (RPR) or Ethernet ring. A special hardware is required to
adopt RPR, which increases the costs. Therefore, increasing number of MANs and LANs are
moving towards adopting the Ethernet ring as it is technologically advanced and the costs
involved are comparatively less.
NOTE
RPR interfaces cannot be configured on the X1 and X2 models of the NE80E/40E.
The RSTP/MSTP and Rapid Ring Protection Protocol (RRPP) are generally adopted to address
the Layer 2 network loop. RSTP/MSTP is highly adaptable; however, the convergence time is
measured in seconds.
Compared with other Ethernet ring technologies, RRPP has the following features:
l Convergence time is less than 50 milliseconds (ms).
l Convergence time is not related to the number of nodes on a ring network. Thus, RRPP
can be applied to a large-scale network.
l RRPP can prevent broadcast storm caused by loops when an Ethernet ring network is
complete.
l On an Ethernet ring network, when a link is disconnected, a backup link immediately
resumes the normal communication between nodes.
9.1.2 RRPP Features Supported by the NE80E/40E

This part describes basic principles and application scenarios of RRPP in terms of RRPP basic
functions, Hello and Fail timers, monitoring interface and RRPP Snooping.
Basic Functions of RRPP

This section describes several RRPP concepts as shown in Figure 9-1.

Figure 9-1 Application of crossed RRPP rings in the MAN
SwitchA RRPP Domain

MasterNode
RouterB
Edge Node
Transit Node
RRPP Sub-Ring 1
RouterA
RRPP Major-Ring
Assistant Master Node
RouterC
Master Node
Node RRPP Sub-Ring 2
Transit Node
SwitchB
l RRPP domain
An RRPP domain is identified uniquely with the domain ID, which is an integer.
The RRPP domain comprises a group of switches that are connected and configured with
the same domain ID and control VLAN. One RRPP domain consists of elements such as
the RRPP major ring and sub-ring, control VLAN, master node, transit node, common port
and edge port, and primary port and secondary port.
l RRPP ring
One RRPP ring corresponds only to one Ethernet ring topology. An RRPP ring is a part of
the RRPP domain. An RRPP domain can consist of one RRPP ring or multiple crossed
RRPP rings.
l RRPP major ring and sub-ring
If an RRPP domain consists of multiple crossed RRPP rings, you can set one ring to be the
major ring and other rings to be sub-rings by specifying their levels.
In one RRPP domain, there is only one RRPP major ring.
The protocol packets of the sub-ring are transmitted as data packets in the major ring. The
packets of the major ring are transmitted only in the major ring.
l Control VLAN of RRPP
The control VLAN is a concept related to the data VLAN. In the RRPP domain, the control
VLAN is only used to transmit RRPP protocol packets. The control VLAN contains only
RRPP interfaces.

One RRPP domain is configured with two control VLANs, that is, the major control VLAN
and sub-control VLAN. During configuration, you must specify only the major control
VLAN, and set the VLAN whose ID is equal to the major control VLAN ID plus 1 to the
sub-control VLAN.
The data VLAN is used to transmit data packets as against the control VLAN. The data
VLAN can contain both the RRPP port and non-RRPP port.
l Master node
On the Ethernet ring, each switch is called a node. On each RRPP ring, there must be only
one master node.
l Transit node
On an RRPP major ring, all nodes are transit nodes except the master node.
The transit node monitors the status of its directly connected RRPP links. When the link
status is changed, the transit node informs the master node. The master node decides how
to process the change.
l Edge node and assistant edge node
A switch is an edge node or an assistant edge node on the sub-ring, and it is a transit node
on the major ring.
On an RRPP sub-ring, either of the two nodes crossing with the major ring can be specified
as the edge node. On one sub-ring, there must be only one edge node.
On an RRPP sub-ring, if one of the two nodes crossed with the major ring is specified as
the edge node, the other node is the assistant edge node.
l Primary port and secondary port
On both the master node and transit node, one of the two ports to the Ethernet ring is the
primary port, and the other is the secondary port. The role of a port is decided by the user
configuration.
l Common port and Edge port
On an edge node or an assistant edge node, the port shared by the sub-ring and major ring
is called the common port. The port only on the sub-ring is called the edge port.
Hello Timer and Fail Timer

When RRPP detects the link status of the Ethernet ring, the master node sends the Hello packet
according to the Hello timer. The master node then assesses whether the secondary port receives
the Hello packet according to the Fail timer.
l The value of the Hello timer specifies the period taken by the master node to send the Hello
packet from the primary port.
l The value of the Fail timer specifies the maximum period delayed by the Hello packet to
reach the secondary port from the primary port.
Monitoring Interface
As shown in Figure 9-2, Metro Ethernet RRPP networking solution can realize the switchover
of Network Provider Edge (NPE).

Figure 9-2 Networking diagram of Metro Ethernet RRPP solution

UPE Master: VLAN1-100
Backup: VLAN101-200
PE-AGG A NPE A
BFD
RRPP ring
VLAN:101-200
UPE Core network
BFD for VRRP
UPE
RRPP ring
VLAN:1-100 BFD
PE-AGG B NPE B
UPE Master: VLAN101-200
Backup: VLAN1-100
LANSwitch DSLAM
Track interface
DSLAM: Digital Subscriber Line Access Multiplexer PE-AGG: PE-Aggregation

UPE: Underlayer Provider Edge NPE: Network Provider Edge
BFD: Bidirectional Forwarding Detection VRRP: Virtual Router Redundancy Protocol
After monitoring interfaces are configured on PE-AGG nodes, RRPP rings can monitor the status
of the connections between PE-AGG nodes and NPEs. When the status of monitoring interfaces
or the status of bidirectional forwarding detection (BFD) on interfaces changes, each node on
RRPP rings updates its dynamic MAC address table. This ensures the continuity of the traffic
between master/backup NPEs and PE-AGG nodes.
RRPP Snooping
As shown in Figure 9-3, UPE A, UPE B, and NPE D comprise an RRPP ring. UPE A is the
master node, UPE B is the transit node, and VLAN 100 is the control VLAN.
The RRPP ring accesses the Virtual Private LAN Service (VPLS) network through sub-
interfaces GE 1/0/0.100 and GE 2/0/0.100 on NPE D. Sub-interfaces allow only the control
VLAN packets of the RRPP ring to pass through. In this manner, NPE D can transparently
transmit RRPP control packets through the sub-interfaces on both sides to ensure the structure
integrity of the RRPP ring. The RRPP protocol, however, is not run in NPE D.
NPE D transmits data packets of VLANs 10 to 20 on the RRPP ring through sub-interfaces GE
1/0/0.10 to GE 1/0/0.20, sub-interfaces GE 2/0/0.10 to GE 2/0/0.20, or the VLANIF interface.
Data packets in the RRPP ring are transparently transmitted to the upper layer network through
the VPLS network. For the details of access principles and transmission principles, refer to the
NPEs are connected through pseudo wires (PWs).

Figure 9-3 Networking diagram of RRPP and VPLS

NPE B
NPE A VPLS NPE C
GE1/0/0.100 GE2/0/0.100
NPE D
GE RRPP ring
Control VLAN:100
P User VLAN:10~20
UPE A UPE B
S
data packet P : primary port

hello packet S : secondary port
The VPLS network cannot sense the change of the RRPP ring status because NPE nodes cannot
respond to the RRPP control packets. When the RRPP ring topology changes, each node in the
VPLS network forwards downstream data according to the MAC address table generated before
the RRPP ring topology changes. As a result, the downstream traffic cannot be forwarded.
After the RRPP snooping is enabled on the sub-interfaces GE 1/0/0.100 and GE 2/0/0.100 of
NPE D, NPE D can respond to the RRPP control packets. Then, NPE D can synchronize the
change of the RRPP ring status and refresh the MAC address table of the virtual switching
instance (VSI). This ensures that downstream traffic is normally forwarded.
9.2 Configuring RRPP Functions

Through RRPP, devices on an Ethernet ring are configured to be the nodes with different roles
on RRPP rings. The nodes on an RRPP ring detect the ring status and transmit topology changes
by sending and receiving RRPP protocol packets. The master node on an RRPP ring blocks or
opens secondary ports according to the ring status. In this manner, if a fault occurs on a node or
a link on the RRPP ring, traffic can be fast switched to the backup link and data loops can be
prevented.

If you have already enabled RRPP on a port, you cannot enable STP on it. That is, the two
protocols cannot coexist on a port.

RRPP is used for the networking of the single-ring or multiple crossed rings. When configuring
RRPP, you must configure all nodes on the RRPP ring.
NOTE
The RRPP or the STP can not coexist on a port.

RRPP contains no auto election mechanism. Therefore, to ensure the detection and protection of the ring
network through RRPP, you must correctly configure each node on the ring.
Pre-Configuration Tasks
Before configuring RRPP functions, complete the following tasks:
l Establishing the ring topology
l Configuring the link attributes of the interface
Data Preparation
To configure RRPP functions, you need the following data.
No. Data
1 ID of the RRPP domain
2 ID of the control VLAN in the RRPP domain
3 IDs of all RRPP rings in the RRPP domain
4 Values of the Hello timer and Fail timer in the RRPP domain
5 Port name of the RRPP ring
9.2.2 Creating the RRPP Domain

A group of connected switches that have the same domain ID and the same control VLANs
constitute an RRPP domain. An RRPP domain mainly consists of RRPP rings, control VLANs,
and master nodes.
Context
Do as follows on all switches in the RRPP domain:
Procedure
Step 1 Run:
system-view

Step 2 Run:
rrpp domain domain-id
The RRPP domain is created.

When creating the RRPP domain, you must specify the domain ID. If the domain exists, the
domain view is directly displayed.
NOTE
The maximum number of RRPP rings that can be configured on a device is determined by the relevant
license. To purchase the License, you can contact the Huawei technical support personnel.
----End
9.2.3 Creating the Control VLAN

Each RRPP ring has two control VLANs. The major control VLAN transmits mainly the protocol
packets of the major ring; the sub-control VLAN transmits mainly the protocol packets of the
sub-rings.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
The domain view is displayed.
Step 3 Run:
control-vlan vlan-id
The control VLAN is created.
The control VLAN specified by vlan-id and the sub-control VLAN specified by vlan-id+1 must
be uncreated and not used in port trunk, mapping, or stacking mode.
After configuring the control VLAN, you cannot directly modify it. You can only delete the
control VLAN by deleting the domain, and then reconfigure the control VLAN. The sub-control
VLAN is also deleted when you delete the domain.
----End
9.2.4 (Optional) Setting the Values of RRPP Domain Timers

Two timers, that is, the Hello timer and the Fail timer are used when master nodes are sending
and receiving RRPP protocol packets. The Hello timer is used when primary ports are sending
Hello packets. The Fail timer is used when secondary ports are receiving the Hello packets sent
by the local node.
Context
Do as follows on the master node in the RRPP domain:

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
timer hello-timer hello-value fail-timer fail-value
The values of RRPP domain timers are set.

The value of the Fail timer is equal to or more than three times the value of the Hello timer.
The value of the Edge-hello timer defaults to half the value of the Hello timer of the master node
on the major ring.
Set consistent Hello timers and Fail timers on all the nodes in the same RRPP ring domain;
otherwise, the edge ports of the edge nodes might be unstable.
----End
9.2.5 Configuring the Ports on a RRPP Ring

The ports on an RRPP ring are called RRPP ports. RRPP ports have to allow the packets from
both control VLANs and data VLANs to pass through, so you can configure the type of the
RRPP ports as trunk or hybrid.
Context
WARNING
If the board where the ports reside is pulled out, all RRPP configurations on the port are lost and
cannot recover automatically. To restore the RRPP configurations on the ports, run all the
commands about RRPP again.
Do as follows at the port that needs to be added into RRPP ring.
Procedure
Step 1 Run:
system-view
The system view displayed.

Step 2 Run:

The Layer 2 ports supported by RRPP are Ethernet, GigabitEthernet, and Eth-Trunk on Layer
2.
Interfaces enabled with MSTP and Eth-Trunk member interfaces cannot be configured as RRPP
ports.
Step 3 Run:
portswitch
The port is switched to a switched port.

The port is configured as a trunk port.
By default, the port is a hybrid port.
The RRPP port should be set to a trunk or hybrid port because it allows packets from both the
control VLAN and the data VLAN to pass through.
Step 5 Run:
The RRPP port is configured to allow the data VLAN frames to pass through.
NOTE
l The control VLAN is specified by the control-vlan command in the RRPP domain view and
automatically becomes the VLAN that is allowed on all RRPP interfaces. Thus, you only need to specify
the data VLAN in this step.
l When RRPP ports are to be added to a VLAN, if VLANIF interfaces in this VLAN are enabled with
RRPP snooping, the RRPP ports cannot be added to the VLAN.
Step 6 Run:
stp disable
STP is disabled at the port.
By default, STP is enabled on all ports of the device. Before creating an RRPP ring, you need
to disable STP at all ports to be added to the RRPP ring.
----End
9.2.6 Creating the RRPP Ring

An RRPP ring physically corresponds to an Ethernet ring. An RRPP domain consists of one or
multiple crossed RRPP rings. In an RRPP domain, only one RRPP ring is the major ring and the
others are sub-rings. Whether a ring is a major ring or a sub-ring depends on the level specified
for that ring.
Context
NOTE
By default, STP is enabled on all interfaces of the device. Before creating the RRPP ring, therefore, you
need to use the stp disable command to disable the STP function on the interfaces to be added to the RRPP
ring.

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
ring ring-id node-mode { master | transit } primary-port interface-type interface-
number secondary-port interface-type interface-number level level-value
The RRPP ring is created.

RRPP can be used on the ports such as Ethernet, GigabitEthernet, Eth-Trunk.
The level 0 refers to the major ring, while level 1 refers to the sub-ring. In one domain, there
must be only one major ring. The sub-ring can be created only after creating the major ring.
NOTE
When a major ring and a sub-ring are intersectant, it is recommended that you configure the major ring
before configuring the sub-ring. If you configure the sub-ring first, the broadcast storm of the protocol
packets may easily occur. The protocol packets of the major ring are then discarded by a transit node. It
causes the secondary port to fail to receive the protocol packets and thus fail to be blocked. As a result, the
state of the RRPP ring is incorrect.
Step 4 Run:
ring ring-id node-mode { edge | assistant-edge } common-port interface-type
interface-number edge-port interface-type interface-number
The edge node and assistant edge node on the RRPP sub-ring are configured.
The common port of the edge node and assistant edge node must be on the major ring.
The system automatically sets the level of the ring where the edge node and assistant edge node
reside to 1.
NOTE
The maximum number of RRPP rings that can be created on a device or in a domain is determined by the relevant
license. To purchase the license, you can contact the Huawei technical support personnel.
----End
9.2.7 Enabling the RRPP Ring

The protocol packets of sub-rings are transmitted on the major ring as data packets; the protocol
packets of the major ring are transmitted on only the major ring. An RRPP ring can take effect
only when it is enabled.
Context
NOTE
l The RRPP ring can be activated only when both the RRPP ring and RRPP protocol are enabled.
l RRPP and RRPP snooping cannot be configured on the same interface.

Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
ring ring-id enable
The RRPP ring is enabled.
----End
9.2.8 Enabling RRPP

To activate an RRPP ring, you must enable RRPP and the RRPP ring.
Context
NOTE
The RRPP ring can be activated only when both the RRPP ring and RRPP protocol are enabled.
Procedure
Step 1 Run:
system-view
Step 2 Run:
rrpp enable
The RRPP protocol is enabled.
----End

After the basic RRPP functions are successfully configured, you can view the mode of the nodes
on the RRPP ring, RRPP protocol status, control VLAN, link recovery delay, and timer value.
Prerequisite
The configurations of RRPP function are complete.

Procedure
l Run the display rrpp brief command to check the brief information about the RRPP
domain.
l Run the display rrpp verbose domain domain-id [ ring ring-id ] command to check the
detailed information about the RRPP domain.
l Run the display rrpp statistics domain domain-id [ ring ring-id ] command to check the
packet statistics of the RRPP domain.
----End
Example
Run the display rrpp brief command. You can view information such as the node mode, RRPP
status, protected VLAN, control VLAN, Linkup Delay timer and values of Hello timer and Fail
timer. For example:
<HUAWEI> display rrpp brief
Abbreviations for Switch Node Mode :
M - Master , T - Transit , E - Edge , A - Assistant-Edge
RRPP Protocol Status: Enable

Number of RRPP Domains: 2
Domain Index : 1
Control VLAN : major 400 sub 401
Hello Timer : 1 sec(default is 1 sec) Fail Timer : 3 sec(default is 3 sec)
Ring Ring Node Primary/Common Secondary/Edge Is
ID Level Mode Port Port Enabled
---------------------------------------------------------------------------
1 0 M GigabitEthernet1/0/6 GigabitEthernet1/0/1 Yes
Domain Index : 2
Ring Ring Node Primary/Common Secondary/Edge Is
---------------------------------------------------------------------------
1 0 M GigabitEthernet1/0/3 GigabitEthernet1/0/4 No
2 1 E GigabitEthernet1/0/3 GigabitEthernet1/0/5 No
Run the display rrpp verbose command. You can view the detailed information such as the
control VLAN, timers, node mode, and port status. For example:
<HUAWEI> display rrpp verbose domain 2 ring 2
Domain Index : 2
RRPP Ring : 2
Ring Level : 1
Node Mode : Edge
Ring State : Unknown
Is Enabled : Disable Is Active : No
Common port : GigabitEthernet1/0/3 Port status: UNKNOWN
Edge port : GigabitEthernet1/0/5 Port status: UNKNOWN
Run the display rrpp statistics command. You can view the sending and receiving statistics of
all types of packets. For example:
<HUAWEI> display rrpp statistics domain 1 ring 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
Is Active : Yes
Primary port : GigabitEthernet1/0/0

Packet LINK COMMON COMPLETE EDGE MAJOR Packet

Direct HEALTH DOWN FDB FDB HELLO FAULT Total
-------------------------------------------------------------------------------
Send 5386 0 0 0 0 0 0
Rcv 0 0 0 0 0 0 0
Secondary port: GigabitEthernet1/0/1
Packet LINK COMMON COMPLETE EDGE MAJOR Packet
Direct HEALTH DOWN FDB FDB HELLO FAULT Total
-------------------------------------------------------------------------------
Send 0 0 0 0 0 0 0
Rcv 0 0 0 0 0 0 0
9.3 Configuring the Monitoring Interface

A monitoring interface is used in the networking scheme where master and backup NPEs
connected to RRPP rings support fast switching of Layer 2 services. When the status of the
monitoring interface or the status of the BFD session changes, the node where the monitoring
interface resides clears the dynamic MAC entries, and meanwhile sends a COMMON-FLUSH-
FDB packet to notify other nodes on the RRPP ring to clear their dynamic MAC entries.

The port that is configured as a monitoring interface supports hot swapping. Each time it is pulled
out or inserted, dynamic MAC entries start to be cleared on the RRPP ring. When the port that
is configured as a monitoring interface is pulled out and a different port is inserted, the original
configuration of the monitoring interface is cleared.
The monitoring interface is used for the networking of NPEs connecting to RRPP switchover.
Figure 9-4 Networking diagram of the applicable environment of monitoring interfaces
UPE
PE-AGG A NPE A
UPE
RRPP ring
UPE
RRPP ring
PE-AGG B NPE B
UPE Track interface

UPE
Before configuring an RRPP monitoring interface, complete the following task:

l Completing RRPP ring configuration with normal RRPP performance
Data Preparation
To configure an RRPP monitoring interface, you need the following data.
No. Data
1 RRPP domain ID
2 RRPP ring ID
3 Number of the monitoring interface
9.3.2 Configuring the Monitoring Interface

A monitoring interface can be configured on any node of an RRPP major ring or a sub-ring, but
it cannot be a port on an RRPP ring. Different RRPP rings can share one monitoring interface.
Context
Do as follows on the nodes connecting to NPE on the RRPP ring:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
ring ring-id track interface interface-type interface-number
Set the monitoring interface.

The monitoring interface cannot be a port on the RRPP ring.
The interface types are available as Ethernet interface, GigabitEthernet interface, Eth-Trunk
interface, Ethernet sub-interface, GigabitEthernet sub-interface, Eth-Trunk sub-interface, and
VLANIF interface.
When configuring Eth-Trunk as the monitoring interface, note that:
l If an Eth-Trunk interface is a monitoring interface, its member interface cannot be configured
as a monitoring interface.
l If a member interface of Eth-Trunk interface is configured as a monitoring interface, the Eth-
Trunk interface cannot be configured as a monitoring interface.
Repeat the process when you need to configure more than one monitoring interfaces. On an
RRPP ring, a maximum of 8 monitoring interfaces can be configured.

Different RRPP rings can share one monitoring interface.
NOTE
The maximum number of track interfaces that can be configured on a device is determined by the relevant
----End

After a monitoring interface is successfully configured, you can view information about the
monitoring interface in a specified RRPP domain.
Prerequisite
The configurations of the monitoring interface function are complete.
Procedure
Step 1 Run the display rrpp verbose domain domain-id [ ring ring-id ] command to check information
about the monitoring interface on the RRPP.
----End
Example
Run the display rrpp verbose command. You can view information about the monitoring
interface on the designated RRPP domain. For example:
# View the details of the main node on the RRPP of domain 1 and ring 1.
<HUAWEI> display rrpp verbose domain 1 ring 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
Ring State : Complete
Is Enabled : Enable Is Active : Yes
Primary port : GigabitEthernet1/0/0 Port status: UP
Secondary port: GigabitEthernet1/0/1 Port status: BLOCKED
Track interface: GigabitEthernet1/0/3
9.4 Configuring RRPP Snooping

RRPP Snooping is a technology through which changes on an RRPP ring can be notified to a
VPLS network. When RRPP Snooping is configured on sub-interfaces or VLANIF interfaces,
the VPLS network can transparently transmit RRPP protocol packets, detect the changes on the
RRPP rings, and upgrade the forwarding entries to ensure that traffic is switched in time to a


Before configuring RRPP Snooping, familiarize yourself with the applicable environment,
UPEs constructing an RRPP ring access the VPLS network where UPEs reside, you need to
configure the RRPP snooping on the NPE at the border of the RRPP ring and the VPLS network.
In this manner, the VPLS network between NPEs can sense the change of the RRPP ring
topology, and NPEs can timely update the MAC address table of the VSI. This ensures the
continuity of VPLS.
As shown in Figure 9-3, VPLS is run between NPEs, and RRPP is run among NPE D, UPE A,
and UPE B.
Figure 9-5 Networking diagram of RRPP and VPLS

NPE B
NPE A VPLS NPE C
GE1/0/0.100 GE2/0/0.100
NPE D
GE RRPP ring
Control VLAN:100
P User VLAN:10~20
UPE A UPE B
S
data packet P : primary port

hello packet S : secondary port
Before configuring the RRPP snooping, complete the following tasks:
l Configuring a VPLS network.

l Configuring an RRPP ring.
l Ensuring that the sub-interface or VLANIF interface enabled with the RRPP snooping
allows the control VLAN packets sent by the master node of RRPP to pass through.

Data Preparation
To configure the RRPP snooping, you need the following data.
No. Data
1 Name of the interface enabled with the RRPP snooping
2 Control VLAN ID of RRPP
3 (Optical) Name of the VSI associated with the RRPP snooping
9.4.2 Enabling RRPP Snooping

After being enabled with RRPP Snooping, an interface can detect the RRPP ring status through
RRPP control packets. In addition, when the RRPP ring status changes, the interface notifies the
bound VSI to update the MAC address table.
Context
NOTE
RRPP and RRPP snooping cannot be configured on the same interface.
Do as follows on the NPEs at the border of the RRPP ring and the VPLS network:
Procedure
Step 1 Run the system-view command to enter the system view.
Step 2 Choose one of the following commands to enter the view of the interface to be enabled with
RRPP snooping.
l Run the interface { ethernet | gigabitethernet | eth-trunk } interface-number.subinterface-
number command to enter the sub-interface view.
The sub-interface must be configured with the associated with VLAN of RRPP by using the
vlan-type dot1q command.
l Run the interface vlanif vlan-id command to enter the specified VLANIF interface view.
The number of the VLANIF interface must be consistent with to the control VLAN ID of
RRPP.For example, if the control VLAN ID of RRPP is 100, the VLANIF interface here
must be VLANIF 100.
Step 3 Run the rrpp snooping enable command to enable RRPP snooping.
This command can be run only after the sub-interface or VLANIF interface is bound to the VSI.
If the sub-interface or VLANIF interface is removed from the VSI, RRPP snooping is
automatically disabled on the interface.
After being enabled with RRPP snooping, the sub-interface or VLANIF interface is
automatically associated with the bound VSI.
A maximum of 32 interfaces of one device can be configured with RRPP snooping.

NOTE
The maximum number of interfaces that can be enabled with RRPP snooping is determined by the relevant
----End
9.4.3 (Optional) Configuring the VSI Associated with the RRPP

Snooping
This part describes how to associate the sub-interface or VLANIF interface enabled with RRPP
Snooping with other VSIs related to the device. Thus, the interface can inform the associated
VSIs of the change in the RRPP ring status so that the VSIs can upgrade their MAC address
tables accordingly.
Context
Do as follows on the NPE nodes at the border of an RRPP ring and a VPLS network:
Procedure
Step 1 Run the system-view command to enter the system view.
Step 2 Run either of the following commands to enter the view of the RRPP snooping-enabled interface:
l Run the interface { ethernet | gigabitethernet | eth-trunk } interface-number.subinterface-
number command to enter the sub-interface view.
The sub-interface in this step must be configured with the control VLAN of RRPP by using
the vlan-type dot1q command.
l Run the interface vlanif interface-number command to enter the specified VLANIF interface
view.
The VLANIF interface in this step must correspond to the control VLAN of RRPP.For
example, if the control VLAN ID of RRPP is 100, the VLANIF interface here must be
VLANIF 100.
----End

After the basic RRPP Snooping functions are successfully configured, you can view the interface
enabled with RRPP Snooping and the names of the VSIs that are associated with RRPP
Snooping.
Prerequisite
The configurations of RRPP snooping function are complete.
Procedure
l Run the display rrpp snooping enable { all | interface interface-type interface-number }
command to check the interface enabled with the RRPP snooping.
l Run the display rrpp snooping vsi { all | interface interface-type interface-number }
command to check the VSI associated with the RRPP snooping.
----End

Example
Run the display rrpp snooping enable command. If the interface enabled with the RRPP
snooping is displayed, it means that the configuration succeeds.For example:
<HUAWEI> display rrpp snooping enable all
Port VsiName Vlan
------------------------------------------------------------
GigabitEthernet1/0/1.1 name1 100
GigabitEthernet1/0/1.2 name2 200
Run the display rrpp snooping vsi command. If the name of the VSI associated with the RRPP
snooping is displayed, it means that the configuration succeeds.For example:
<HUAWEI> display rrpp snooping vsi all
Port VsiName
-----------------------------------------------
GigabitEthernet1/0/1.1 name1
9.5 Maintaining RRPP

Commands of clearing statistics helps to locate the RRPP faults on a device.
9.5.1 Clearing RRPP Running Information

You can run the reset command to reset the RRPP statistics before recollecting RRPP statistics.
Context
CAUTION
RRPP statistics cannot be restored once cleared. Therefore, confirm the action before you use
the command.
To clear the RRPP statistics, run the following reset command in the user view:
Procedure
Step 1 Run the reset rrpp statistics domain domain-id [ ring ring-id ] command to clear the statistics
of RRPP.
----End

This section describes the typical application scenario of RRPP, including networking
files.

NOTE
9.6.1 Example for Configuring a Single RRPP Ring

This part takes an example of the networking of a single RRPP ring to describe how to configure,
use, and apply basic RRPP functions.
As shown in Figure 9-6, RouterA, RouterB, and RouterC support the RRPP function. RouterA,
RouterB, and RouterC construct ring 1 in domain 1.
Figure 9-6 Networking diagram of configuring a single RRPP ring

RouterB
GE2/0/2
GE2/0/1 GE2/0/1
Ring 1
GE2/0/2
GE2/0/2 RouterC
GE2/0/1
RouterA
1. RouterA, RouterB, and RouterC construct ring 1 in domain 1.
2. Configure RouterA as the master node in ring 1, and RouterB and RouterC as transit nodes
in ring 1.
Data Preparation
l Number of the RRPP interface
l Control VLAN ID of ring 1
Procedure
Step 1 RouterA, RouterB, and RouterC construct ring 1 in domain 1.
l Create an RRPP domain and its control VLAN.
# Configure the domain of RouterA, the master node of ring 1, to be 1, and the ID of the
major control VLAN to be 20.


[RouterA] rrpp domain 1
[RouterA-rrpp-domain-region1] control-vlan 20
[RouterA-rrpp-domain-region1] quit
# Configure the domain of RouterB, a transit node of ring 1, to be 1, and the ID of the major
control VLAN to be 20.
[RouterB] rrpp domain 1
[RouterB-rrpp-domain-region1] control-vlan 20
[RouterB-rrpp-domain-region1] quit
# Configure the domain of RouterC, a transit node of ring 1, to be 1, and the ID of the major
[RouterC] rrpp domain 1
[RouterC-rrpp-domain-region1] control-vlan 20
[RouterC-rrpp-domain-region1] quit
l Disable the STP function on the interfaces to be added to the RRPP ring.
# Disable the STP function on the interfaces to be added to the RRPP ring on RouterA.
[RouterA-GigabitEthernet2/0/1] stp disable
# Disable the STP function on the interfaces to be added to the RRPP ring on RouterB.
[RouterB-GigabitEthernet2/0/1] stp disable
# Disable the STP function on the interfaces to be added to the RRPP ring on RouterC.
[RouterC-GigabitEthernet2/0/1] stp disable
Step 2 Configure RouterA as the master node in ring 1, and RouterB and RouterC as transit nodes in
ring 1.
l Create an RRPP ring.
# Configure RouterA as the master node of RRPP ring 1 and specify primary and secondary
interfaces.
[RouterA-rrpp-domain-region1] ring 1 node-mode master primary-port
gigabitethernet 2/0/1 secondary-port gigabitethernet 2/0/2 level 0

[RouterA-rrpp-domain-region1] ring 1 enable

# Configure RouterB as a transit node of RRPP major ring 1 and specify primary and
secondary interfaces.
[RouterB-rrpp-domain-region1] ring 1 node-mode transit primary-port
[RouterB-rrpp-domain-region1] ring 1 enable
# Configure RouterC as a transit node of RRPP ring 1 and specify primary and secondary
interfaces.
[RouterC-rrpp-domain-region1] ring 1 node-mode transit primary-port
[RouterC-rrpp-domain-region1] ring 1 enable
l Enable RRPP.
After configuring an RRPP ring, you need to enable RRPP on each node on the ring. In this
manner, the RRPP ring can be activated. The configuration procedure is as follows:
# Enable RRPP on RouterA.
[RouterA] rrpp enable
Warning: The global RRPP state will be changed. Continue? [Y/N]Y
Info: RRPP is enabled.
# Enable RRPP on RouterB.

[RouterB] rrpp enable
# Enable RRPP on RouterC.

[RouterC] rrpp enable

After the configuration, perform the following procedures to verify the previous configuration.
Take the display on RouterA as an example:
l On RouterA, run the display rrpp brief command. The following results are displayed.
[RouterA] display rrpp brief

Domain Index : 1
Ring Ring Node Primary Secondary/Edge Is
---------------------------------------------------------------------------
You can view that RRPP is enabled on RouterA. In domain 1, VLAN 20 is the major control
VLAN, VLAN 21 is the sub-control VLAN, and RouterA is the master node in major ring
1 with the primary interface and secondary interface respectively as GigabitEthernet 2/0/1
and GigabitEthernet 2/0/2.
l On RouterA, run the display rrpp verbose domain command. The following results are
displayed.

# View detailed information about RouterA in domain 1.

[RouterA] display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
----End
Configuration Files
#
sysname RouterA
#
vlan batch 20 to 21
#
rrpp enable
#
rrpp domain 1
control-vlan 20
ring 1 node-mode master primary-port GigabitEthernet 2/0/1 secondary-port
GigabitEthernet 2/0/2 level 0
ring 1 enable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
return

#
sysname RouterB
#
vlan batch 20 to 21
#
rrpp enable
#
rrpp domain 1
control-vlan 20
ring 1 node-mode transit primary-port GigabitEthernet 2/0/1 secondary-port
ring 1 enable
#
undo shutdown
portswitch
stp disable
#
undo shutdown

portswitch
stp disable
#
return

#
sysname RouterC
#
vlan batch 20 to 21
#
rrpp enable
#
rrpp domain 1
control-vlan 20
ring 1 enable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
return
9.6.2 Example for Configuring a Crossed RRPP Ring

A metro Ethernet adopts an architecture of two-level rings. One is the convergence layer and is
configured with an RRPP major ring; the other is the access layer and is configured with an
RRPP sub-ring. In this networking, the major ring and sub-ring have two intersection points
(two nodes), and there is no other node between the two nodes. The two intersection nodes can
be configured only as transit nodes. On a sub-ring, if one of the two transit nodes is configured
as an edge node, the other node must be configured as an assistant edge node.
As shown in Figure 9-7, RouterA, RouterB, RouterC, and RouterD support the RRPP function.
Configure RouterA, RouterB, and RouterD to be major Ring 1 in Domain 1. RouterA,
RouterC, and RouterD to be Sub-Ring 2 in Domain 1 are configured. Control VLAN ID is
10.This RRPP ring sends user data of VLAN 1 to VLAN 9.

Figure 9-7 Networking diagram of a crossed RRPP ring
GE1/0/2 GE1/0/3
RouterC
sub-ring RouterA
GE1/0/1
GE1/0/1 GE1/0/2
GE1/0/2
GE1/0/3 RouterD
major ring GE1/0/1
GE2/0/1
RouterB
GE2/0/2
1. The configuration roadmap is as follows:Configure RouterA, RouterB, and RouterD as the
major Ring 1 in domain 1.Major control VLAN ID is 10.The VLAN IDs whose service
traffic is allowed to pass through the major ring and sub-ring are VLAN 1 to VLAN 9.
2. Configure RouterA, RouterB, and RouterD as the Sub-ring 2 in domain 1.
3. Configure RouterB as the master node on the major ring and RouterA and RouterD as transit
nodes on the major ring.
4. Configure RouterC as the master node on the sub-ring. Configure RouterA as the edge node
on the sub-ring and RouterD as the assistant edge node on the sub-ring.
Data Preparation
To configure this, you need the following data:
l Number of the interfaces to be added to RRPP rings
l Control VLAN ID and data VLAN ID
Procedure
Step 1 Configure RouterB as the master node of the major ring.
# Create data VLAN 1 to VLAN 9 on RouterB.
# Configure Domain 1 on RouterB and set VLAN 10 to be the major control VLAN.
# Disable STP on the interfaces to be added to the RRPP ring, and set the RRPP port as trunk
port.


# Configure the primary port and secondary port of the master node on the RRPP major ring.
[RouterB-rrpp-domain-region1] ring 1 node-mode master primary-port gigabitethernet
2/0/1 secondary-port gigabitethernet 2/0/2 level 0
Step 2 Configure RouterC to be the master node of the sub-ring..

# Create data VLAN 1 to VLAN 9 on RouterC
[RouterC] vlan batch 1 to 9
# Configure Domain 1 on RouterC and set VLAN 10 to be the major control VLAN.
# Disable STP on the port to be added to the RRPP ring, and set the RRPP port as a trunk port.
[RouterC] interface gigabitethernet1/0/1
[RouterC-GigabitEthernet1/0/1] port trunk allow-pass vlan 1 to 9
[RouterC] interface gigabitethernet1/0/2
[RouterC-GigabitEthernet1/0/2] port trunk allow-pass vlan 1 to 9
# Configure the primary port and secondary port of the master node on the RRPP sub-ring.
[RouterC-rrpp-domain-region1] ring 2 node-mode master primary-port gigabitethernet
Step 3 Configure RouterA to be the transit node in the major ring and the edge node on the sub-ring
respectively.
# Create data VLAN 1 to VLAN 9 on RouterA.

# Configure Domain 1 on RouterA and set VLAN 10 to be the major control VLAN.
# Disable STP on the ports that will be added to RRPP ring, and set RRPP port as a trunk port.
# Configure the primary port and secondary port of the transit node on the RRPP major ring.
[RouterA-rrpp-domain-region1] ring 1 node-mode transit primary-port
# Configure the common port and edge port of the edge node on the RRPP sub-ring.
[RouterA-rrpp-domain-region1] ring 2 node-mode edge common-port gigabitethernet
1/0/2 edge-port gigabitethernet 1/0/3
Step 4 Configure RouterD to be the transit node on the major ring and the assistant edge node on the
sub-ring respectively.
# Create data VLAN 1 to VLAN 9 on RouterD.
[RouterD] vlan batch 1 to 9
# Configure Domain 1 on RouterD and set VLAN 10 to be the major control VLAN.
[RouterD] rrpp enable
[RouterD] rrpp domain 1
[RouterD-rrpp-domain-region1] control-vlan 10
[RouterD-rrpp-domain-region1] quit
# Disable STP on the port to be added to RRPP ring, and set the RRPP port as trunk port.
[RouterD] interface gigabitethernet1/0/1

[RouterD-GigabitEthernet1/0/1] port link-type trunk

[RouterD-GigabitEthernet1/0/1] port trunk allow-pass vlan 1 to 9
[RouterD-GigabitEthernet1/0/1] stp disable
# Configure the primary port and secondary port of the transit node on the RRPP major ring.
[RouterD-rrpp-domain-region1] ring 1 node-mode transit primary-port
[RouterD-rrpp-domain-region1] ring 1 enable
# Configure the common port and edge port of the assistant edge node on the RRPP sub-ring.
[RouterD-rrpp-domain-region1] ring 2 node-mode assistant-edge common-port
gigabitethernet 1/0/2 edge-port gigabitethernet 1/0/3
Step 5 Check the configuration

You can run the following commands to verify the previous configurations:
l On RouterB, run the display rrpp brief command. The configurations are displayed as
follows:
[RouterB] display rrpp brief
Domain Index : 1
------------------------------------------------------------------------------
You can view that RRPP on RouterB is enabled. The major control VLAN ID is 10, and the
sub control VLAN ID is 11. RouterB is the master node on the major ring with the primary
port and the secondary port as GE 2/0/1 and GE 2/0/2 respectively.
l On RouterB, run the display rrpp verbose domain command. The configuration is displayed
as follows:
[RouterB] display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master


You can view that the ring is in the Complete state and the secondary port of the master node
is blocked.
l On RouterC, run the display rrpp brief command. The configuration is displayed as follows:
[RouterC] display rrpp brief
Domain Index : 1
-------------------------------------------------------------------------
Here, RRPP on RouterC is enabled. The major control VLAN ID is 10, and the sub control
VLAN ID is 11. RouterC is the master node on the sub-ring, with the primary port and the
secondary port as GE 1/0/1 and GE 1/0/2 respectively.
l On RouterC, run the display rrpp verbose domain command. The configuration is
displayed as follows:
[RouterC] display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 2
Ring Level : 1
Node Mode : Master
You can view that the sub-ring is in the Complete state and the secondary port of the master
node on the sub-ring is blocked.
l On RouterA, run the display rrpp brief command. The configuration is displayed as follows:
[RouterA] display rrpp brief
Domain Index : 1
-------------------------------------------------------------------------
1 0 T GigabitEthernet1/0/2 GigabitEthernet1/0/1 Yes
2 1 E GigabitEthernet1/0/2 GigabitEthernet1/0/3 Yes
RRPP is enabled on RouterA. The major control VLAN ID is 10 and the sub control VLAN
ID is 11. RouterA is the transit node on the major Ring 1, with the primary port and secondary
port as GE 1/0/2 and GE 1/0/1 respectively.At the same time, RouterA is the edge node on
the sub-ring 2, the common port is GE 1/0/2, and the edge port is GE 1/0/3.
l On RouterA, run the display rrpp verbose domain command. The configuration is
[RouterA] display rrpp verbose domain 1
Domain Index : 1


RRPP Ring : 1
Ring Level : 0
Node Mode : Transit
Ring State : Linkup
Secondary port: GigabitEthernet1/0/1 Port status: UP
RRPP Ring : 2
Ring Level : 1
Node Mode : Edge
Ring State : Linkup
Common port : GigabitEthernet1/0/2 Port status: UP
Edge port : GigabitEthernet1/0/3 Port status: UP
l On RouterD, run the display rrpp brief command. The configuration is displayed as follows:
[RouterD] display rrpp brief
Domain Index : 1
-------------------------------------------------------------------------
2 1 A GigabitEthernet1/0/2 GigabitEthernet1/0/3 Yes
RRPP is enabled on RouterD. VLAN 10 is the major control VLAN and VLAN 11 is the
sub control VLAN. RouterD is the transit node on the major ring 1, with the primary interface
and secondary interface as GE 1/0/2 and GE 1/0/1 respectively. RouterD is the assistant edge
node on the sub-ring 2, with the common interface and edge interface as GE 1/0/2 and GE
1/0/3 respectively.
l On RouterD, run the display rrpp verbose domain command. The configuration is
[RouterD] display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Transit
Ring State : Linkup
RRPP Ring : 2
Ring Level : 1
Node Mode : Assistant-edge
Ring State : Linkup
----End
Configuration Files
#

sysname RouterA
#
vlan batch 1 to 11
#
rrpp enable
#
rrpp domain 1
control-vlan 10
ring 1 node-mode transit primary-port gigabitethernet 1/0/2 secondary-port
gigabitethernet 1/0/1 level 0
ring 1 enable
ring 2 node-mode edge common-port gigabitethernet 1/0/2 edge-port
gigabitethernet 1/0/3
ring 2 enable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
port trunk allow-pass vlan 1 to 9 11
stp disable
#
return
#
sysname RouterB
#
vlan batch 1 to 11
#
rrpp enable
#
rrpp domain 1
control-vlan 10
ring 1 node-mode master primary-port gigabitethernet 2/0/1 secondary-port
ring 1 enable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
return
#

sysname RouterC
#
vlan batch 1 to 11
#
rrpp enable
#
rrpp domain 1
control-vlan 10
ring 2 node-mode master primary-port GigabitEthernet1/0/1 secondary-port
GigabitEthernet1/0/2 level 1
ring 2 enable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
return
l Configuration file on RouterD

#
sysname RouterD
vlan batch 1 to 11
#
rrpp enable
#
rrpp domain 1
control-vlan 10
ring 1 node-mode transit primary-port GigabitEthernet1/0/2 secondary-port
ring 1 enable
ring 2 node-mode assistant-edge common-port GigabitEthernet1/0/2 edge-port
ring 2 enable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
return

9.6.3 Example for Configuring a Tangent RRPP Ring

In this networking, two tangent rings must belong to different RRPP domains. The tangency
point is configured in two domains. The master node on a ring can be the tangency point. For
multiple tangent RRPP rings, the failure of a ring does not affect other domains. The convergence
of RRPP rings in a domain is the same as the convergence of a single RRPP ring.
As shown in Figure 9-8, RouterA, RouterB, RouterC, RouterD, and RouterE support the RRPP
function. RouterA, RouterB, and RouterC construct ring 2 in domain 2. RouterC, RouterE, and
RouterD construct ring 1 in domain 1. RouterC is the tangent point of the two rings.
Figure 9-8 Networking diagram of configuring a tangent RRPP ring
Domain 2 Domain 1
RouterB GE2/0/2 GE1/0/1 RouterE
GE2/0/1 GE2/0/1 GE1/0/2

GE1/0/2
Ring 2 RouterC Ring 1
GE2/0/2 GE1/0/1
GE2/0/2 GE1/0/1
RouterA
GE2/0/1 GE1/0/2 RouterD
1. RouterC, RouterE, and RouterD construct ring 1 in domain 1.RouterA, RouterB, and
RouterC construct ring 2 in domain 2.
2. Configure RouterE as the master node in ring 1, and RouterC and RouterD as transit nodes
in ring 1.Configure RouterA as the master node in ring 2, and RouterB and RouterC as
transit nodes in ring 2.
Data Preparation
l Number of the RRPP interface

l Respective control VLAN IDs of ring 1 and ring 2

Procedure
Step 1 RouterC, RouterE, and RouterD construct ring 1 in domain 1.RouterA, RouterB, and RouterC
construct ring 2 in domain 2.
l Create an RRPP domain and its control VLAN.
# Configure the domain of RouterE, the master node of ring 1, to be 1, and the ID of the
[HUAWEI] sysname RouterE
[RouterE] rrpp domain 1
[RouterE-rrpp-domain-region1] control-vlan 10
[RouterE-rrpp-domain-region1] quit
# Configure the domain of RouterD, a transit node of ring 1, to be 1, and the ID of the major
[RouterD-rrpp-domain-region1] control-vlan 10
# Configure the domain of RouterA, the master node of ring 2, to be 2, and the ID of the
# Configure the domain of RouterB, a transit node of ring 2, to be 2, and the ID of the major
l Set the value of RRPP domain timers

NOTE
You can configure two timers for tangent points because two tangent rings reside in different domains.
# Configure a timer for the master node RouterE on ring 1.
[RouterE-rrpp-domain-region1] timer hello-timer 2 fail-timer 7
# Configure a timer for the transit node RouterC on ring 1.


[RouterC-rrpp-domain-region1] timer hello-timer 2 fail-timer 7
# Configure a timer for the transit node RouterD on ring 1.

[RouterD-rrpp-domain-region1] timer hello-timer 2 fail-timer 7
# Configure a timer for the master node RouterA on ring 2.

[RouterA-rrpp-domain-region2] timer hello-timer 3 fail-timer 10
# Configure a timer for the transit node RouterBon ring 2.

[RouterB-rrpp-domain-region2] timer hello-timer 3 fail-timer 10
# Configure a timer for the transit node RouterC on ring 2.

[RouterC-rrpp-domain-region2] timer hello-timer 3 fail-timer 10
l Disable the STP function on the interfaces to be added to the RRPP ring.
# Disable the STP function on the interfaces to be added to the RRPP ring on RouterA.
# Disable the STP function on the interfaces to be added to the RRPP ring on RouterB.
# Disable the STP function on the interfaces to be added to the RRPP ring on RouterC.


# Disable the STP function on the interfaces to be added to the RRPP ring on RouterE.
[RouterE] interface gigabitethernet 1/0/1
[RouterE-GigabitEthernet1/0/1] undo shutdown
[RouterE-GigabitEthernet1/0/1] portswitch
[RouterE-GigabitEthernet1/0/1] stp disable
[RouterE-GigabitEthernet1/0/1] quit
[RouterE] interface gigabitethernet 1/0/2
[RouterE-GigabitEthernet1/0/2] undo shutdown
[RouterE-GigabitEthernet1/0/2] portswitch
[RouterE-GigabitEthernet1/0/2] stp disable
[RouterE-GigabitEthernet1/0/2] quit
# Disable the STP function on the interfaces to be added to the RRPP ring on RouterD.
Step 2 Configure RouterE as the master node in ring 1, and RouterC and RouterD as transit nodes in
ring 1.Configure RouterA as the master node in ring 2, and RouterB and RouterC as transit nodes
in ring 2.
l Create an RRPP ring.
– Configure nodes on ring 1. The configuration procedure is as follows:
# Configure RouterE as the master node of RRPP ring 1 and specify primary and
[RouterE-rrpp-domain-region1] ring 1 node-mode master primary-port
[RouterE-rrpp-domain-region1] ring 1 enable
interfaces.
# Configure RouterD as a transit node of RRPP ring 1 and specify primary and secondary
interfaces.
[RouterD-rrpp-domain-region1] ring 1 node-mode transit primary-port
– Configure nodes on ring 2. The configuration procedure is as follows:

# Configure RouterA as the master node of RRPP ring 2 and specify primary and
[RouterA-rrpp-domain-region2] ring 2 node-mode master primary-port

# Configure RouterB as a transit node of RRPP ring 2 and specify primary and secondary
interfaces.
[RouterB-rrpp-domain-region2] ring 2 node-mode transit primary-port
interfaces.
l Enable RRPP.
After configuring an RRPP ring, you need to enable RRPP on each node on the ring. In this
manner, the RRPP ring can be activated. The configuration procedure is as follows:
# Enable RRPP on RouterA.
# Enable RRPP on RouterB.

# Enable RRPP on RouterC.

# Enable RRPP on RouterE.

[RouterE] rrpp enable
# Enable RRPP on RouterD.

[RouterD] rrpp enable

Take the display on RouterC as an example:
l On RouterC, run the display rrpp brief command. The following results are displayed.
[RouterC] display rrpp brief
Domain Index : 1
---------------------------------------------------------------------------
Domain Index : 2
---------------------------------------------------------------------------
You can view that RRPP is enabled on RouterC. In domain 1, VLAN 10 is the major control
VLAN, VLAN 11 is the sub-control VLAN, and RouterC is the transit node in major ring 1
with the primary interface and secondary interface respectively as GigabitEthernet 1/0/1 and
GigabitEthernet 1/0/2.

VLAN 20 is the major control VLAN of RouterC in domain 2, VLAN 21 is the sub-control
VLAN, and RouterC is the transit node in major ring 2 with the primary interface and
secondary interface respectively as GigabitEthernet 2/0/1 and GigabitEthernet 2/0/2.
l On RouterC, run the display rrpp verbose domain command. The following results are
displayed.
# View detailed information about RouterC in domain 1.
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Transit
Ring State : Linkup
# View detailed information about RouterC in domain 2.

Domain Index : 2
RRPP Ring : 2
Ring Level : 0
Node Mode : Transit
Ring State : Linkup
----End
Configuration Files
#
sysname RouterA
#
rrpp enable
#
rrpp domain 2
control-vlan 20
timer hello-timer 3 fail-timer 10
ring 2 enable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#

#
sysname RouterB
#

rrpp enable
#
rrpp domain 2
control-vlan 20
ring 2 enable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
return
#

#
sysname RouterC
#
rrpp enable
#
rrpp domain 1
control-vlan 10
ring 1 enable
#
rrpp domain 2
control-vlan 20
ring 2 enable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
return


#
sysname RouterD
#
rrpp enable
#
rrpp domain 1
control-vlan 10
ring 1 enable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
return
l Configuration file of RouterE

#
sysname RouterE
#
rrpp enable
#
rrpp domain 1
control-vlan 10
ring 1 enable
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
return
9.6.4 Example for Configuring a Crossed RRPP Ring to Connect

Dual NPE
In this networking, Layer 2 services can be fast switched between the master and backup NPEs.
When the status of the monitoring interface or the status of the BFD session changes, each node
on RRPP rings updates its dynamic MAC address table. This ensures that the traffic between
master/backup NPEs and PE-AGG nodes is not interrupted.
As shown in Figure 9-9:

l NPE A and NPE B balance the load of services of VLAN 1 to VLAN 200 through VRRP
load balancing.
– The NPE A works as the master device to process the services of VLAN 1 to VLAN
100, and the backup device for the traffic on VLAN 101 to VLAN 200.
– The NPE B works as the master device to process the services of VLAN 101 to VLAN
200, and the backup device for the traffic on VLAN 1 to VLAN 100.
l BFD session is created between NPE A and NPE B for VRRP fast switchover.
l BFD session is created between NPE and PE-AGG for detecting the connectivity. The PE-
AGG is associated with (sub-) interface to notify and apply the detection results.
l Configure a monitoring interface on the PE-AGG to support the MAC address table update
on all the nodes of RRPP ring with NPE switchover.
Figure 9-9 Networking diagram of configuring the monitoring interface

UPE A
GE2/0/0
GE2/0/0 Master: VLAN1~100
GE1/0/0 Backup: VLAN101~200
UPE B PE-AGG A BFD
NPE A
Major ring GE2/0/0
GE1/0/0 GE1/0/1 GE1/0/0
VLAN:101~200 GE3/0/0
GE1/0/0
GE2/0/0 VRRP BFD

GE1/0/0
Sub ring GE3/0/0 GE1/0/1 GE1/0/0
VLAN:1~100 NPE B
GE1/0/0 PE-AGG B
BFD Master: VLAN101~200
GE1/0/0 GE2/0/0 Backup: VLAN1~100
UPE C
UPE D GE2/0/0 Track interface
Common port
Major ring port
Sub ring port
1. Configure the RRPP ring.

(1) Configure the UPE A, UPE B, PE-AGG A, and PE-AGG B as the major ring 1 of
Domain 1.
(2) Configure the UPE C, UPE D, PE-AGG A, and PE-AGG B as the sub-ring 2 of Domain
1.
(3) Configure UPE A as the master node of the major ring. Configure the UPE B, PE-
AGG A, and PE-AGG B as the transit node of the major ring. GE 1/0/0 on nodes of
the major ring is the primary port and GE 2/0/0 is the secondary port.
(4) Configure UPE C as the master node of the sub-ring and UPE D as the transit node
of the sub-ring. PE-AGG A is the edge node of the sub-ring and PE-AGG B is the

assistant edge node of the sub-ring. GE 1/0/0 on nodes of the sub-ring is the primary
port and GE 2/0/0 is the secondary port.
2. Configure BFD.
(1) Create the one-hop BFD session between NPE A and NPE B. The BFD detects the
interface where the VRRR locates and notifies the result to VRRP, assistant in VRRP
switchover.
(2) Create the one-hop BFD session between NPE A and PE-AGG A. Apply default
multicast IP address as the peer IP address. Configure the status of BFD to be
associated with the status of the interface for fast notifying the detection.
(3) Create the one-hop BFD session between NPE B and PE-AGG B. Apply default
multicast IP address as the peer IP address. Configure the status of BFD to be
associated with the status of the interface for fast notifying the detection.
3. Establish VRRP backup group 201 between NPE A and NPE B to monitor the status of the
BFD sessions.
4. Configure GE 1/0/1 on PE-AGG A and GE 1/0/1 on PE-AGG B as the monitoring interface.
Data Preparation
Before configuring, you need the following data:
l Number of the interface to be added to the RRPP ring
l Control VLAN IDs and data VLAN IDs
l Number of the monitoring interface
l Default multicast IP address for BFD session
Different BFD sessions apply different default multicast IP address
Here, the default multicast IP address of NPE A and PE-AGG A is 224.0.0.108. The default
multicast IP address of NPE B and PE-AGG B is 224.0.0.109.
l Parameter of Detection Time of BDF session
l VRRP ID
l Respective IP addresses of the NPE devices that back up each other
l Backup ID according to which you can find the profile users belong to
CAUTION
Multiple BFDs provides failure checking for the RRPP ring switching between two NPEs. When
failure occurs, BFDs can detect in a specific order. For example, when failure occurs between
NPE and PE-AGG, the BFDs between the two must detect the failure first and the BFDs between
NPEs must detect the failure later. Otherwise, the NPE may locate the failure at another NPE.
So, the cycle of BFD session between NPEs must be longer than that between NPE and PE-
AGG.
You can adjust the minimal sending interval or detection time coefficient.
Procedure
Step 1 Configure UPE A as the master node on the major ring.

# Create data VLAN 101 to VLAN 200 on UPE A.

[HUAWEI] sysname UPE A
[UPE A] vlan batch 101 to 200
# Configure Domain 1 on UPE A and set VLAN 201 to be the major control VLAN.
[UPE A] rrpp enable
[UPE A] rrpp domain 1
[UPE A-rrpp-domain-region1] control-vlan 201
[UPE A-rrpp-domain-region1] quit
# Disable that STP on the interface of RRPP ring, and configure the VLAN of whose frames
that the RRPP port allows to pass through.
[UPE A] interface gigabitethernet1/0/0
[UPE A-GigabitEthernet1/0/0] undo shutdown
[UPE A-GigabitEthernet1/0/0] port link-type trunk
[UPE A-GigabitEthernet1/0/0] port trunk allow-pass vlan 101 to 200
[UPE A-GigabitEthernet1/0/0] stp disable
[UPE A-GigabitEthernet1/0/0] quit
[UPE A] interface gigabitethernet2/0/0
# Configure GE 1/0/0 as the primary port, GE 2/0/0 as the secondary port. Level 0 indicates the
major ring.
[UPE A-rrpp-domain-region1] ring 1 node-mode master primary-port gigabitethernet
[UPE A-rrpp-domain-region1] ring 1 enable
Step 2 Configure UPE B as the transit node on the major ring.
# Create data VLAN 101 to VLAN 200 on UPE B.

[HUAWEI] sysname UPE B
[UPE B] vlan batch 101 to 200
# Configure Domain 1 on UPE B and set VLAN 201 to be the major control VLAN.
[UPE B] rrpp enable
[UPE B] rrpp domain 1
[UPE B-rrpp-domain-region1] control-vlan 201
[UPE B-rrpp-domain-region1] quit
[UPE B] interface gigabitethernet1/0/0
[UPE B-GigabitEthernet1/0/0] undo shutdown
[UPE B-GigabitEthernet1/0/0] port link-type trunk
[UPE B-GigabitEthernet1/0/0] port trunk allow-pass vlan 101 to 200
[UPE B-GigabitEthernet1/0/0] stp disable
[UPE B-GigabitEthernet1/0/0] quit
[UPE B] interface gigabitethernet2/0/0

# Configure GE 1/0/0 as the primary port, and GE 2/0/0 as the secondary port. Level 0 indicates
the major ring.
[UPE B-rrpp-domain-region1] ring 1 node-mode transit primary-port gigabitethernet
[UPE B-rrpp-domain-region1] ring 1 enable
Step 3 Configure UPE C as the master node on the sub-ring.

# Create data VLAN 1 to VLAN 100 on UPE C.
[HUAWEI] sysname UPE C
[UPE C] vlan batch 1 to 100
# Configure Domain 1 on UPE C and set VLAN 201 to be the major control VLAN.
[UPE C] rrpp enable
[UPE C] rrpp domain 1
[UPE C-rrpp-domain-region1] control-vlan 201
[UPE C-rrpp-domain-region1] quit
[UPE C] interface gigabitethernet1/0/0
[UPE C-GigabitEthernet1/0/0] undo shutdown
[UPE C-GigabitEthernet1/0/0] port link-type trunk
[UPE C-GigabitEthernet1/0/0] port trunk allow-pass vlan 1 to 100
[UPE C-GigabitEthernet1/0/0] stp disable
[UPE C-GigabitEthernet1/0/0] quit
[UPE C] interface gigabitethernet2/0/0
[UPE C-GigabitEthernet2/0/0] undo shutdown
[UPE C-GigabitEthernet2/0/0] port link-type trunk
[UPE C-GigabitEthernet2/0/0] port trunk allow-pass vlan 1 to 100
[UPE C-GigabitEthernet2/0/0] stp disable
[UPE C-GigabitEthernet2/0/0] quit
sub-ring.
[UPE C] rrpp domain 1
[UPE C-rrpp-domain-region1] ring 2 node-mode master primary-port gigabitethernet
[UPE C-rrpp-domain-region1] ring 2 enable
[UPE C-rrpp-domain-region1] quit
Step 4 Configure UPE D as the transit node on the sub-ring.

# Create data VLAN 1 to VLAN 100 on UPE D.
[HUAWEI] sysname UPE D
[UPE D] vlan batch 1 to 100
# Configure Domain 1 on UPE D and set VLAN 201 to be the major control VLAN.
[UPE D] rrpp enable
[UPE D] rrpp domain 1
[UPE D-rrpp-domain-region1] control-vlan 201
[UPE D-rrpp-domain-region1] quit
that the RRPP port allows to pass though.
[UPE D] interface gigabitethernet1/0/0

[UPE D-GigabitEthernet1/0/0] undo shutdown

[UPE D-GigabitEthernet1/0/0] port link-type trunk
[UPE D-GigabitEthernet1/0/0] port trunk allow-pass vlan 1 to 100
[UPE D-GigabitEthernet1/0/0] stp disable
[UPE D-GigabitEthernet1/0/0] quit
[UPE D] interface gigabitethernet2/0/0
[UPE D-GigabitEthernet2/0/0] undo shutdown
[UPE D-GigabitEthernet2/0/0] port link-type trunk
[UPE D-GigabitEthernet2/0/0] port trunk allow-pass vlan 1 to 100
[UPE D-GigabitEthernet2/0/0] stp disable
[UPE D-GigabitEthernet2/0/0] quit
sub-ring.
[UPE D] rrpp domain 1
[UPE D-rrpp-domain-region1] ring 2 node-mode transit primary-port gigabitethernet
[UPE D-rrpp-domain-region1] ring 2 enable
[UPE D-rrpp-domain-region1] quit
Step 5 Configure PE-AGG A as the main transit node on the major ring and the edge node on the sub-
ring.
# Create data VLAN 1 to VLAN 200 on PE-AGG A.
[HUAWEI] sysname PE-AGG A
[PE-AGG A] vlan batch 1 to 200
# Configure Domain 1 on PE-AGG A and set VLAN 201 to be the major control VLAN.
[PE-AGG A] rrpp enable
[PE-AGG A] rrpp domain 1
[PE-AGG A-rrpp-domain-region1] control-vlan 201
[PE-AGG A-rrpp-domain-region1] quit
[PE-AGG A] interface gigabitethernet1/0/0
[PE-AGG A-GigabitEthernet1/0/0] undo shutdown
[PE-AGG A-GigabitEthernet1/0/0] portswitch
[PE-AGG A-GigabitEthernet1/0/0] port link-type trunk
[PE-AGG A-GigabitEthernet1/0/0] port trunk allow-pass vlan 1 to 200
[PE-AGG A-GigabitEthernet1/0/0] stp disable
[PE-AGG A-GigabitEthernet1/0/0] quit
# Configure GE 1/0/0 as the primary port, GE 2/0/0 as the secondary port on the major ring.
Level 0 indicates the major ring.
[PE-AGG A-rrpp-domain-region1] ring 1 node-mode transit primary-port
[PE-AGG A-rrpp-domain-region1] ring 1 enable

# Configure the edge node GE 1/0/0 on RRPP sub-ring as common port and GE 3/0/0 as edge
port.
[PE-AGG A-rrpp-domain-region1] ring 2 node-mode edge common-port gigabitethernet
1/0/0 edge-port gigabitethernet 3/0/0
[PE-AGG A-rrpp-domain-region1] ring 2 enable
Step 6 Configure PE-AGG B as the main transit node on the major ring and the assistant edge node on
the sub-ring.
# Create data VLAN 1 to VLAN 200 on PE-AGG B.
[HUAWEI] sysname PE-AGG B
[PE-AGG B] vlan batch 1 to 200
# Configure Domain 1 on PE-AGG B and set VLAN 201 to be the major control VLAN.
[PE-AGG B] rrpp enable
[PE-AGG B] rrpp domain 1
[PE-AGG B-rrpp-domain-region1] control-vlan 201
[PE-AGG B-rrpp-domain-region1] quit
[PE-AGG B] interface gigabitethernet1/0/0
[PE-AGG B-GigabitEthernet1/0/0] undo shutdown
[PE-AGG B-GigabitEthernet1/0/0] portswitch
[PE-AGG B-GigabitEthernet1/0/0] port link-type trunk
[PE-AGG B-GigabitEthernet1/0/0] port trunk allow-pass vlan 1 to 200
[PE-AGG B-GigabitEthernet1/0/0] stp disable
[PE-AGG B-GigabitEthernet1/0/0] quit
# Configure GE 1/0/0 as the primary transit port, GE 2/0/0 as the secondary port on the RRPP
major ring. Level 0 indicates the major ring.
[PE-AGG B-rrpp-domain-region1] ring 1 node-mode transit primary-port
[PE-AGG B-rrpp-domain-region1] ring 1 enable
# Configure the assistant edge node GE 1/0/0 on RRPP sub-ring as common port and GE 3/0/0
as edge port.
[PE-AGG B-rrpp-domain-region1] ring 2 node-mode assistant-edge common-port
gigabitethernet 1/0/0 edge-port gigabitethernet 3/0/0
[PE-AGG B-rrpp-domain-region1] ring 2 enable

Step 7 Configure VRRP.

# Configure the interface bound with VRRP on NPE A, that is, GigabitEthernet1/0/0.
[NPE A] interface gigabitethernet1/0/0.1
[NPE A-GigabitEthernet1/0/0.1] vlan-type dot1q 200
[NPE A-GigabitEthernet1/0/0.1] ip address 10.1.1.1 255.255.255.0
[NPE A-GigabitEthernet1/0/0.1] vrrp vrid 201 virtual-ip 10.1.1.10
[NPE A-GigabitEthernet1/0/0.1] vrrp vrid 201 priority 200
[NPE A-GigabitEthernet1/0/0.1] quit
# Configure the interface bound with VRRP on NPE B, that is, GigabitEthernet1/0/0.
[NPE B] interface gigabitethernet1/0/0.1
[NPE B-GigabitEthernet1/0/0.1] vlan-type dot1q 200
[NPE B-GigabitEthernet1/0/0.1] ip address 10.1.1.2 255.255.255.0
[NPE B-GigabitEthernet1/0/0.1] vrrp vrid 201 virtual-ip 10.1.1.10
[NPE B-GigabitEthernet1/0/0.1] vrrp vrid 201 priority 200
[NPE B-GigabitEthernet1/0/0.1] quit
# Verify the configuration.

[NPE A] display vrrp
state : Master
Master IP : 10.1.1.1
PriorityRun : 200
Timer : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-01c9
Check TTL : YES
Track BFD : 888 Priority increased : 30
BFD-Session State : UP
[NPE B] display vrrp
state : Backup
Master IP : 10.1.1.2
PriorityRun : 200
Timer : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-01c9
Check TTL : YES
Track BFD : 333 Priority increased : 30
BFD-Session State : UP
Step 8 Configure BFD sessions

# Configure a BFD session bfd1 (device-bfd) between NPE A and NPE B. 10.1.1.1 is the IP
address of NPE A and 10.1.1.2 is the IP address of NPE B. Increase the detection period by
adjusting the detection time multiplier that is set to 5 (by default, it is set to 3).
[NPE A] bfd
[NPE A-bfd] quit
[NPE A] bfd bfd1 bind peer-ip 10.1.1.2
[NPE A-bfd-session-bfd1] discriminator local 888
[NPE A-bfd-session-bfd1] discriminator remote 333
[NPE A-bfd-session-bfd1] detect-multiplier 5

[NPE A-bfd-session-bfd1] commit

[NPE A-bfd-session-bfd1] quit
[NPE B] bfd
[NPE B-bfd] quit
[NPE B] bfd bfd1 bind peer-ip 10.1.1.1
[NPE B-bfd-session-bfd1] discriminator local 333
[NPE B-bfd-session-bfd1] discriminator remote 888
[NPE B-bfd-session-bfd1] detect-multiplier 5
[NPE B-bfd-session-bfd1] commit
[NPE B-bfd-session-bfd1] quit
# Configure a BFD session bfd2 (link-bfd) between NPE A and PE-AGG A. The default
multicast IP address is used as the peer IP address. The detection time multiplier adopts the
default value 3 to ensure that BFD session bfd2 can detect faults faster than BFD session bfd1
between NPE A and NPE B.
[NPE A] interface gigabitethernet1/0/0
[NPE A-GigabitEthernet1/0/0] undo shutdown
[NPE A-GigabitEthernet1/0/0] portswitch
[NPE A-GigabitEthernet1/0/0] quit
[NPE A] bfd
[NPE A-bfd] default-ip-address 224.0.0.108
[NPE A-bfd] quit
[NPE A] bfd bfd2 bind peer-ip default-ip interface gigabitethernet1/0/0
[NPE A-bfd-session-bfd2] discriminator local 111
[NPE A-bfd-session-bfd2] discriminator remote 222
[NPE A-bfd-session-bfd2] commit
[NPE A-bfd-session-bfd2] quit
[PE-AGG A] bfd
[PE-AGG A-bfd] default-ip-address 224.0.0.108
[PE-AGG A-bfd] quit
[PE-AGG A] bfd bfd2 bind peer-ip default-ip interface gigabitethernet1/0/1
[PE-AGG A-bfd-session-bfd2] discriminator local 222
[PE-AGG A-bfd-session-bfd2] discriminator remote 111
[PE-AGG A-bfd-session-bfd2] commit
# After the status of the BFD session becomes Up, associate the status of the BFD session with
the interface status.
[PE-AGG A-bfd-session-bfd2] process-interface-status
[PE-AGG A-bfd-session-bfd2] commit
[PE-AGG A-bfd-session-bfd2] quit
# Configure VRRP on NPE A to be bound with bfd1 and bfd2.

[NPE A] interface gigabitethernet1/0/0.1
[NPE A-GigabitEthernet1/0/0.1] vrrp vrid 201 track bfd-session 888 peer
[NPE A-GigabitEthernet1/0/0.1] vrrp vrid 201 track bfd-session 111 link
[NPE A-GigabitEthernet1/0/0.1] quit
# Configure a BFD session bfd2 (link-bfd) between NPE B and PE-AGG B. The default multicast
IP address is used as the peer IP address. The detection time multiplier adopts the default value
3 to ensure that BFD session bfd2 can detect faults faster than BFD session bfd1 between NPE
A and NPE B.
[NPE B] interface gigabitethernet1/0/0
[NPE B-GigabitEthernet1/0/0] undo shutdown
[NPE B-GigabitEthernet1/0/0] portswitch
[NPE B-GigabitEthernet1/0/0] quit
[NPE B] bfd
[NPE B-bfd] default-ip-address 224.0.0.109
[NPE B-bfd] quit
[NPE B] bfd bfd2 bind peer-ip default-ip interface gigabitethernet1/0/0
[NPE B-bfd-session-bfd2] discriminator local 555
[NPE B-bfd-session-bfd2] discriminator remote 666
[NPE B-bfd-session-bfd2] commit
[NPE B-bfd-session-bfd2] quit
[PE-AGG B] bfd

[PE-AGG B-bfd] default-ip-address 224.0.0.109

[PE-AGG B-bfd] quit
[PE-AGG B] bfd bfd2 bind peer-ip default-ip interface gigabitethernet1/0/1
[PE-AGG B-bfd-session-bfd2] discriminator local 666
[PE-AGG B-bfd-session-bfd2] discriminator remote 555
[PE-AGG B-bfd-session-bfd2] commit
# After the status of the BFD session becomes Up, associate the status of the BFD session with
the interface status.
[PE-AGG B-bfd-session-bfd2] process-interface-status
[PE-AGG B-bfd-session-bfd2] commit
[PE-AGG B-bfd-session-bfd2] quit
# Configure VRRP on NPE B to be bound with bfd1 and bfd2.

[NPE B] interface gigabitethernet1/0/0.1
[NPE B-GigabitEthernet1/0/0.1] vrrp vrid 201 track bfd-session 333 peer
[NPE B-GigabitEthernet1/0/0.1] vrrp vrid 201 track bfd-session 555 link
[NPE B-GigabitEthernet1/0/0.1] quit
# Check the configuration.

[NPE A] display bfd session all
Total Static Session Number : 2, Dynamic Session Number: 0
--------------------------------------------------------------------------------
Local Remote Peer IP Address Interface Name State Type
--------------------------------------------------------------------------------
888 333 10.1.1.2 -- Up Static
111 222 224.0.0.108 GigabitEthernet1/0/1 Up Static
[PE-AGG A] display bfd session all verbose
Total Static Session Number : 1, Dynamic Session Number: 0
--------------------------------------------------------------------------------
Session MIndex : 263 (One Hop) State : Up Name : bfd2
--------------------------------------------------------------------------------
Session Detect Mode : --
BFD Bind Type : Interface(GigabitEthernet1/0/1)
Bind Peer Ip Address : 224.0.0.108
Bind Interface : GigabitEthernet1/0/1
Actual Tx Interval (ms): 1000 Actual Rx Interval (ms): 1000
Local Detect Multi : 3 Detect Interval (ms) : 3000
WTR Interval (ms) : -- Process PST : Disable
Proc interface status : Enable
Bind Application : IFNET
Session TX TmrID : -- Session Detect TmrID : --
Session Init TmrID : -- Session WTR TmrID : --
PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0
Session Description : --
--------------------------------------------------------------------------------
Step 9 Configure GE 1/0/1 on PE-AGG A as the monitoring interface. Ring ID 1 indicates the major
ring and ID 2 is for the sub-ring.
[PE-AGG A-rrpp-domain-region1] ring 1 track interface gigabitethernet1/0/1
[PE-AGG A-rrpp-domain-region1] ring 2 track interface gigabitethernet1/0/1

Step 10 Configure GE 1/0/1 on PE-AGG B as the monitoring interface. Ring ID 1 indicates the major
ring and ID 2 is for the sub-ring.
[PE-AGG B-rrpp-domain-region1] ring 1 track interface gigabitethernet1/0/1
[PE-AGG B-rrpp-domain-region1] ring 2 track interface gigabitethernet1/0/1

You can run the following commands to verify the previous configuration.
l On PE-AGG A, run the display rrpp brief command. The configurations are displayed as
follows:
[PE-AGG A] display rrpp brief
Domain Index : 1
Ring Ring Node Primary/Common Secondary/Edge
Is
ID Level Mode Port Port
Enabled
-------------------------------------------------------------------------------
--
1 0 T GigabitEthernet1/0/0 GigabitEthernet2/0/0
Yes
2 1 E GigabitEthernet1/0/0 GigabitEthernet3/0/0
Yes
You can view that RRPP is enabled on PE-AGG A. The major control VLAN ID is 201 and
the sub control VLAN ID is 202. PE-AGG A is the transit node on the major ring 1, with the
primary interface and secondary interface respectively as GigabitEthernet 1/0/0 and
GigabitEthernet 2/0/0 respectively.
In addition, PE-AGG A is the edge node on sub-ring 2, the common port is GigabitEthernet
1/0/0, and the edge port is GigabitEthernet3/0/0.
l On PE-AGG A, run the display rrpp verbose domain command. The configurations are
[PE-AGG A] display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Transit
Ring State : Linkup
RRPP Ring : 2
Ring Level : 1
Node Mode : Edge
Ring State : Linkup


You can view that the GE 1/0/1 on PE-AGG A serves as the monitoring interface for the
major ring and the sub-ring at the same time.
l On PE-AGG B, run the display rrpp brief command. The configurations are displayed as
follows:
[PE-AGG B] display rrpp brief
Domain Index : 1
Ring Ring Node Primary Secondary/Edge
Is
ID Level Mode Port Port
Enabled
-------------------------------------------------------------------------------
--
1 0 T GigabitEthernet1/0/0 GigabitEthernet2/0/0
Yes
2 1 A GigabitEthernet1/0/0 GigabitEthernet3/0/0
Yes
You can view that RRPP is enabled on PE-AGG B. The major control VLAN ID is 201 and
the sub control VLAN ID is 202. PE-AGG B is the transit node on the major ring 1, with the
primary interface and secondary interface respectively as GigabitEthernet 1/0/0 and
GigabitEthernet 2/0/0 respectively.In addition, PE-AGG B is the assistant edge node on sub-
ring 2, the common port is GigabitEthernet 1/0/0, and the edge port is GigabitEthernet 3/0/0.
l On PE-AGG B, run the display rrpp verbose domain command. The configurations are
[PE-AGG B] display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Transit
Ring State : Linkup
RRPP Ring : 2
Ring Level : 1
Node Mode : Assistant-edge
Ring State : Linkup
You can view that the GE 1/0/1 on PE-AGG B serves as the monitoring interface for the
major ring and the sub-ring at the same time.
----End

Configuration Files
l Configuration file of NPE A
#
sysname NPE A
#
bfd
default-ip-address 224.0.0.108
#
portswitch
undo shutdown
#
vlan-type dot1q 200
ip address 10.1.1.1 255.255.255.0
vrrp vrid 201 track bfd-session 888 peer
vrrp vrid 201 track bfd-session 111 link
#
bfd bfd1 bind peer-ip 10.1.1.2
detect-multiplier 5
commit
#
bfd bfd2 bind peer-ip default-ip interface GigabitEthernet1/0/0
commit
#
return
l Configuration file of NPE B

#
sysname NPE B
#
bfd
#
portswitch
undo shutdown
#
vlan-type dot1q 200
ip address 10.1.1.2 255.255.255.0
vrrp vrid 201 track bfd-session 333 peer
vrrp vrid 201 track bfd-session 555 link
#
bfd bfd1 bind peer-ip 10.1.1.1
detect-multiplier 5
commit
#
commit
#
return
l Configuration file of PE-AGG A

#
sysname PE-AGG A

#
vlan batch 1 to 202
#
rrpp enable
#
rrpp domain 1
control-vlan 201
ring 1 enable
ring 1 track interface Gigabitethernet1/0/1
ring 2 node-mode edge common-port GigabitEthernet1/0/0 edge-port
ring 2 enable
#
bfd
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
process-interface-status
commit
#
return
l Configuration file of PE-AGG B
#
sysname PE-AGG B
vlan batch 1 to 202
#
rrpp enable
#
rrpp domain 1
control-vlan 201
ring 1 enable
ring 2 node-mode assistant-edge common-port GigabitEthernet1/0/0 edge-port
ring 2 enable


#
bfd
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
#
undo shutdown
portswitch
stp disable
#
undo shutdown
portswitch
stp disable
#
process-interface-status
commit
#
return
l Configuration file of UPE A
#
sysname UPE A
#
#
rrpp enable
#
rrpp domain 1
control-vlan 201
ring 1 enable
#
undo shutdown
stp disable
#
undo shutdown
stp disable
#
return
l Configuration file of UPE B
#

sysname UPE B
#
#
rrpp enable
#
rrpp domain 1
control-vlan 201
ring 1 enable
#
undo shutdown
stp disable
#
undo shutdown
stp disable
#
return
l Configuration file of UPE C
#
sysname UPE C
#
vlan batch 1 to 100 201 to 202
#
rrpp enable
#
rrpp domain 1
control-vlan 201
ring 2 enable
#
undo shutdown
stp disable
#
undo shutdown
stp disable
#
return
l Configuration file of UPE D
#
sysname UPE D
#
vlan batch 1 to 100 201 to 202
#
rrpp enable
#
rrpp domain 1
control-vlan 201
ring 2 enable
#
undo shutdown


stp disable
#
undo shutdown
stp disable
#
return
9.6.5 Example for Configuring the RRPP Snooping

In this networking, RRPP snooping is configured on sub-interfaces or VLANIF interfaces. The
VPLS network can thus transparently transmit RRPP protocol packets, detect the change in the
RRPP ring status, and upgrade the forwarding entries to ensure that traffic is switched to a
As shown in Figure 9-10, UPE A, UPE B, NPE D, and NPE E comprise an RRPP ring. This
RRPP ring transmits data of VLANs 1 to 10 and the control VLAN is VLAN 20. NPE D and
NPE E transmit data packets of VLANs 1 to 10 through their respective sub-interfaces GE 2/0/0.1
to GE 2/0/0.10. In addition, sub-interfaces GE 2/0/0.1 to GE 2/0/0.10 are bound to VSIs 1 to 10
respectively.
UPE A is the master node, UPE B is a transit node, the RRPP ring accesses the VPLS network
through GE 2/0/0.20 of UPE D, and GE 2/0/0.20 of NPE E.
NPE D is connected to NPE E through a PW.
Enable the RRPP snooping on respective sub-interfaces GE 2/0/0.20 of NPE D and NPE E and
associate the sub-interfaces with other VSIs on the local device. In this manner, when a fault
occurs on the RRPP ring, NPEs in the VPLS network can synchronously clear the MAC address
table of the VSIs on the local node.
Figure 9-10 Networking diagram of configuring the RRPP snooping
NPE C
PW PW
VPLS
NPE D
PW NPE E
GE2/0/0.1 binding VSI 1 GE2/0/0.1 binding VSI 1
GE2/0/0.2 binding
.. VSI 2 GE2/0/0.2 binding VSI 2
..
. .
RRPP ring
Control VLAN:20
GE2/0/0 GE2/0/0
UPE A GE1/0/0 GE1/0/0 UPE B
VLAN 1~10 VLAN 1~10

1. Configure a VPLS
2. Create an RRPP domain and its control VLAN.
3. Disable the STP function on the interfaces to be added to the RRPP ring.
4. Create an RRPP ring.
5. Enable RRPP.
6. Configure the RRPP snooping.
7. Configure the VSI associated with the RRPP snooping.
Data Preparation
l Number of the sub-interfaces to be enabled with the RRPP snooping on NPE D and NPE
E
l Names of the VSIs associated with the sub-interfaces enabled with the RRPP snooping
l Control VLAN ID and data VLAN ID of the RRPP ring
l Names of the VSIs to be associated with the sub-interfaces enabled with the RRPP snooping
on NPE D and NPE E
Procedure
Step 1 Configure a VPLS
NOTE
This example describes only the configuration of the sub-interfaces through which NPE D and NPE E are
connected to the RRPP ring. For the configuration of the sub-interfaces between NPEs in a VPLS network,
refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN.
l Configure NPE D.
# Create VLANs 1 to 10 and VALN 20 on NPE D.
[HUAWEI] sysname NPE D
[NPE D] vlan batch 1 to 10 20
# Configure GE 2/0/0.1 of NPE D to allow the packets of VLAN 1 to pass through and bind
GE 2/0/0.1 to VSI 1.
[NPE D] interface gigabitethernet2/0/0.1
[NPE D-GigabitEthernet2/0/0.1] vlan-type dot1q 1
[NPE D-GigabitEthernet2/0/0.1] l2 binding vsi VSI1
[NPE D-GigabitEthernet2/0/0.1] undo shutdown
[NPE D-GigabitEthernet2/0/0.1] quit
# Configure GE 2/0/0.2 of NPE D to allow the packets of VLAN 2 to pass through and bind
GE 2/0/0.2 to VSI 2.

The configuration of sub-interfaces GE 2/0/0.3 to GE 2/0/0.10 is the same as that of sub-

interfaces GE 2/0/0.1 to GE 2/0/0.2. Detailed configurations are thus not mentioned here.
# Configure GE 2/0/0.20 of NPE D to allow the packets of VLAN 20 (the control VLAN of
RRPP) to pass through and bind GE 2/0/0.20 to VSI 20.
l Configure NPE E.
# Create VLANs 1 to 10 and VALN 20 on NPE E.
[HUAWEI] sysname NPE E
[NPE E] vlan batch 1 to 10 20
# Configure GE 2/0/0.1 of NPE E to allow the packets of VLAN 1 to pass through and bind
GE 2/0/0.1 to VSI 1.
[NPE E] interface gigabitethernet2/0/0.1
[NPE E-GigabitEthernet2/0/0.1] vlan-type dot1q 1
[NPE E-GigabitEthernet2/0/0.1] l2 binding vsi VSI1
[NPE E-GigabitEthernet2/0/0.1] undo shutdown
[NPE E-GigabitEthernet2/0/0.1] quit
# Configure GE 2/0/0.2 of NPE E to allow the packets of VLAN 2 to pass through and bind
GE 2/0/0.2 to VSI 2.
The configurations of sub-interfaces GE 2/0/0.3 to GE 2/0/0.10 are the same as those of sub-
interfaces GE 2/0/0.1 to GE 2/0/0.2. Detailed configurations are thus not mentioned here.
# Configure GE 2/0/0.20 of NPE E to allow the packets of VLAN 20 (the control VLAN of
RRPP) to pass through and bind GE 2/0/0.20 to VSI 20.
Step 2 Create an RRPP domain and its control VLAN.
# Create data VLANs 1 to 10 on UPE A.

[HUAWEI] sysname UPE A
[UPE A] vlan batch 1 to 10
# Configure the domain of UPE A, the master node of ring 1, to be 1, and the ID of the control
VLAN to be 20.
[UPE A-rrpp-domain-region1] control-vlan 20
# Create data VLANs 1 to 10 on UPE B.

[UPE B] vlan batch 1 to 10
# Configure the domain of UPE B, a transit node of ring 1, to be 1, and the ID of the control
VLAN to be 20.


[UPE B-rrpp-domain-region1] control-vlan 20
Step 3 Disable the STP function on the interfaces to be added to the RRPP ring.
# Disable the STP function on the interfaces to be added to the RRPP ring on UPE A.
[UPE A] interface gigabitethernet 1/0/0
[UPE A] interface gigabitethernet 2/0/0
# Disable the STP function on the interfaces to be added to the RRPP ring on UPE B.
[UPE B] interface gigabitethernet 1/0/0
[UPE B] interface gigabitethernet 2/0/0
[UPE B-GigabitEthernet2/0/0] portswitch
Step 4 Create an RRPP ring.

# Configure UPE A as the master node of RRPP ring 1 and specify primary and secondary
interfaces.
[UPE A-rrpp-domain-region1] ring 1 node-mode master primary-port gigabitethernet
[UPE A-rrpp-domain-region1] ring 1 enable
# Configure UPE B as a transit node of RRPP ring 1 and specify primary and secondary
interfaces.
[UPE B-rrpp-domain-region1] ring 1 node-mode transit primary-port gigabitethernet
[UPE B-rrpp-domain-region1] ring 1 enable
Step 5 Enable RRPP.

# Enable RRPP on UPE A.
[UPE A] rrpp enable
# Enable RRPP on UPE B.

[UPE B] rrpp enable
Step 6 Configure the RRPP snooping.

# Enable the RRPP snooping on GE 2/0/0.20 of NPE D.

[NPE D] interface gigabitethernet 2/0/0.20

[NPE D-GigabitEthernet2/0/0.20] rrpp snooping enable
# Enable the RRPP snooping on GE 2/0/0.20 of NPE E.

[NPE E] interface gigabitethernet 2/0/0.20
[NPE E-GigabitEthernet2/0/0.20] rrpp snooping enable
Step 7 Configure the VSI associated with the RRPP snooping.

# Configure VSI 2, VSI 5, and VSI 9, which are associated with GE 2/0/0.20 of NPE D.
[NPE D-GigabitEthernet2/0/0.20] rrpp snooping vsi VSI2
# Configure VSI 2, VSI 5, and VSI 9, which are associated with GE 2/0/0.20 of NPE E.
[NPE E-GigabitEthernet2/0/0.20] rrpp snooping vsi VSI2

Take the display on UPE A for example:
l On UPE A, run the display rrpp brief command. The following results are displayed:
[UPE A] display rrpp brief
Domain Index : 1
---------------------------------------------------------------------------
You can view that RRPP is enabled on UPE A. In domain 1, VLAN 20 is the major control
VLAN, VLAN 21 is the sub-control VLAN, and UPE A is the master node in major ring 1
with the primary interface and secondary interface respectively as GE 1/0/0 and GE 2/0/0.
l On UPE A, run the display rrpp verbose domain command. The following results are
displayed.
# View detailed information about UPE A in domain 1.
[UPE A] display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
# View information about the RRPP snooping enabled on GE 2/0/0.20 of NPE D.

[NPE D] display rrpp snooping enable interface gigabitethernet 2/0/0.20
Port VsiName Vlan
--------------------------------------------------------
GigabitEthernet2/0/0.20 VSI20 20

You can view that VSI 1 is associated with GE 2/0/0.20 and VLAN 20 is associated with GE
2/0/0.20.
# View information about other VSIs associated with GE 2/0/0.20 on NPE D.
[NPE D] display rrpp snooping vsi interface gigabitethernet2/0/0.20
Port VsiName
--------------------------------------------
GigabitEthernet2/0/0.20 VSI2
You can view that GE 2/0/0.20 is associated with four VSIs, namely, VSI 2, VSI 5, VSI 9,
and VSI 20.
----End
Configuration Files
l Configuration file of UPE A
#
sysname UPE A
#
vlan batch 1 to 10 20 21
#
rrpp enable
#
rrpp domain 1
control-vlan 20
ring 1 enable
#
undo shutdown
stp disable
#
undo shutdown
stp disable
#
rrpp enable
#
l Configuration file of UPE B

#
sysname UPE B
#
vlan batch 1 to 10 20 21
#
rrpp enable
#
rrpp domain 1
control-vlan 20
ring 1 enable
#
undo shutdown
stp disable

#
undo shutdown
stp disable
#
rrpp enable
#
return
#
l Configuration file of UPE D
#
sysname NPE D
#
vlan batch 1 to 10 20
#
undo shutdown
vlan-type dot1q 1
l2 binding vsi VSI1
#
undo shutdown
vlan-type dot1q 2
l2 binding vsi VSI2
#
undo shutdown
vlan-type dot1q 3
l2 binding vsi VSI3
#
undo shutdown
vlan-type dot1q 4
l2 binding vsi VSI4
#
undo shutdown
vlan-type dot1q 5
l2 binding vsi VSI5
#
undo shutdown
vlan-type dot1q 6
l2 binding vsi VSI6
#
undo shutdown
vlan-type dot1q 7
l2 binding vsi VSI7
#
undo shutdown
vlan-type dot1q 8
l2 binding vsi VSI8
#
undo shutdown
vlan-type dot1q 9
l2 binding vsi VSI9
#
undo shutdown
vlan-type dot1q 10
l2 binding vsi VSI10
#
undo shutdown

vlan-type dot1q 20
rrpp snooping enable
rrpp snooping vsi VSI2
#
return
l Configuration file of UPE E
#
sysname NPE E
#
vlan batch 1 to 10 20
#
undo shutdown
vlan-type dot1q 1
l2 binding vsi VSI1
#
undo shutdown
vlan-type dot1q 2
l2 binding vsi VSI2
#
undo shutdown
vlan-type dot1q 3
l2 binding vsi VSI3
#
undo shutdown
vlan-type dot1q 4
l2 binding vsi VSI4
#
undo shutdown
vlan-type dot1q 5
l2 binding vsi VSI5
#
undo shutdown
vlan-type dot1q 6
l2 binding vsi VSI6
#
undo shutdown
vlan-type dot1q 7
l2 binding vsi VSI7
#
undo shutdown
vlan-type dot1q 8
l2 binding vsi VSI8
#
undo shutdown
vlan-type dot1q 9
l2 binding vsi VSI9
#
undo shutdown
vlan-type dot1q 10
#
undo shutdown
vlan-type dot1q 20
rrpp snooping enable


#
return

Configuration Guide - LAN Access and MAN Access A Glossary
A Glossary
This appendix collates frequently used glossaries in this document.

Glossary Description
10 Base-T Twisted cable with the transmission speed as 10 Mbit/s and the
transmission distance as 100 m. It is described in the IEEE 802.3i.
100 Base-T Twisted cable with the transmission speed as 100 Mbit/s and the
transmission distance as 100 m. It is described in the IEEE 802.3u.
1000 BaseT Twisted cable with the transmission speed as 1000 Mbit/s and the
transmission distance as 100 m. It is described in the IEEE 802.3ab.
A
Active Interface In link aggregation, the interfaces that are responsible for
forwarding data in the active state are called active interfaces.
Active Link In link aggregation group, the links connected to active interfaces
are active links.
ARP A collection of features that provides a level of functionality
available to a user.
Automatic negotiation A function through which the two ends of a physical link choose
a operation mode including duplex mode, operation rate. After the
negotiation, the two ends work in the negotiated mode until the
system reboot.
B
backbone VLAN The backbone VLAN ID refers to the VLAN ID of the provider's
backbone network.
Backup links To improve the reliability of the link, link aggregation introduces
the mechanism of backup links. These backup links often act as
inactive links. Only when the current active interface fails, the
backup interface changes from inactive to active.

C
CE A CE device is a device that is directly connected with the service
provider. In a VPN based on MPLS, a CE device can be a router,
switch, or even a host.
Common port and edge On an edge node or an assistant edge node, a port shared by the
port sub-ring and major ring is called the common port. A port only on
the sub-ring is called the edge port.
Control VLAN A control VLAN in the RRPP domain is a VLAN only used to
transmit RRPP protocol packets.
CRC Cyclic redundancy check.
D
Data VLAN A VLAN that transmits only data packets.
E
Edge node and assistant On an RRPP sub-ring, if one of the two nodes crossed with the
edge node major ring is specified as the edge node, the other node is the
assistant edge node.
Ethernet A baseband LAN specification created by Xerox and developed
by Xerox, Intel, and Digital Equipment Corporation (DEC). This
specification is similar to IEEE802.3.
Ethernet_II An encapsulation format of the Ethernet frame. Ethernet_II that
contains a 16-bit protocol type field is the standard ARPA Ethernet
Version 2.0 encapsulation.
Ethernet_SNAP A encapsulation format of the Ethernet frame. The frame format
complies with RFC 1042 and enables the transmission of the
Ethernet frame on the IEEE 802.2 media.
F
FDB Forwarding database.
FE Fast Ethernet. A extension and enhancement on the traditional
Ethernet standard. In FE, the transmission speed increases to 100
Mbit/s. FE complies with the IEEE 802.3u.
Full-duplex A operation mode of the Ethernet port. In full-duplex mode, a port
can send and receive data simultaneously without interference.

G
GE Gigabit Ethernet. GE adopts the IEEE 802.3z. GE is compatible
with 10 Mbit/s and 100 Mbit/s Ethernet.
H
Half-duplex In half-duplex mode, a port can only send or receive data at a time.
I
IETF Internet Engineering Task Force. A organization that is devoted to
develop and design the TCP/IP suite and Internet.
Inactive Interface In link aggregation, the interfaces that do to forward data in the
inactive status are called inactive interfaces.
Inactive Link In link aggregation group, the links connected to inactive
interfaces are inactive links.
ISO International Standard Organization.
ISP Internet Service Provider.
L
Link Aggregation Link aggregation refers to a method of bundling a group of
Control Protocol physical interfaces together as a logical interface to increase the
bandwidth and reliability. For related protocols and standards,
refer to IEEE 802.3ad.
Link Aggregation Group The logical link that is created by bundling several physical links
together is called link aggregation group or trunk.
LACP Preemption In static LACP mode, when a link of active links fails, the system
chooses the link of the highest priority from slave links to replace
the faulty one. After a period, the replaced faulty link recovers, and
the priority of this link is higher than the link that replaces the faulty
one. In this case, the recovered link switches to the active state,
and the slave link returns to its original state. This is called LACP
Preemption.
LACP Preemption The LACP preemption delay refers to the period for triggering the
Delay preemption. The LACP preemption delay is set to prevent instable
data transmission of the Eth-Trunk due to frequent change of the
status of some links.
LAN Local Area Network. A network that comprises PCs and stations
located within several square kilometers. LAN features the high
speed and low error rate. Ethernet, FDDI, and token ring are three
major implementations.

LAN switch A multi-home switching device that works on the data link layer.
M
MAC Media Access Control. In the OSI model, the data link layer, which
is divided into the MAC and the Link Access Control (LAC), MAC
is nearer to the physical layer.
MAN Metropolitan Area Network. A network covers more than ten
square kilometers or a city.
Manual Load Balancing The manual load balancing mode is the most basic mode of link
Mode aggregation. In manual load balancing mode, you must manually
create the Eth-Trunk, add member interfaces to the Eth-Trunk, and
specify active interfaces. The Link Aggregation Control Protocol
Data Units (LACPDUs) are not involved. All the member
interfaces forward data and perform load balancing.
MTU Maximum Transmission Unit. The maximum unit of a packet that
an interface can process. It is measured in bytes.
P
P A backbone device that is located in the service provider network.
A P device is not directly connected with the CE devices. The P
devices only need the basic MPLS forwarding capability and do
not maintain information about a VPN.
PE A Provider Edge (PE) device is a device that is located in the
backbone network in the MPLS VPN structure. A PE device is
responsible for VPN user management, establishment of LSPs
between the PE devices and exchanges of routing information
between sites of the same VPN.A PE device performs the mapping
and forwarding of the packets from the private network to the
public-network tunnels and that in the reverse order. PE can be
further divided into UPE, SPE and NPE.
Packet Discarding It refers to the function to discard the packets from unknown
VLAN domain or broadcast packets. Packet Discarding is used to
prevent the situation where unknown packets or broadcast packet
utilize the bandwidth originally belonging to the links, improving
the reliability of service transmission.
PING A diagnostic tool that uses the ICMP Echo message to test whether
a certain device in an IP network is reachable.
port isolation The port isolation isolates the unidirectional or bidirectional Layer
2 communication between interfaces.
Primary port and On both the master node and transit node, one of the two ports that
secondary port access the Ethernet ring is the primary port, and the other is the
secondary port. The role of a port is decided by user configuration.

PWE3 A technology that bears Layer 2 services. PWE3 emulates services
such as ATM, FR, Ethernet, low-speed TDM circuit, and SONET/
SDH.
Q
QinQ A technology that expands the VLAN space by adding an IEEE
802.1Q tag to a packet already carrying an 802.1Q tag. As a result,
private VLANs can transparently transmit packets over the public
network. This function is the same as the Layer 2 VPN. Packets
that are forwarded over the backbone network carry two 802.1Q
tags, one for the public network and the other for the private
network. This is called 802.1Q-in-802.1Q, or QinQ for short.
QoS Quality of Service. A measurement used to evaluate the service
capability for forwarding packets in the IP network. The evaluated
elements include the delay, delay jitter, packet loss ratio.
R
RRPP domain An RRPP domain comprises of a group of switches that are
connected and configured with the same domain ID and control
VLAN.
RRPP ring An RRPP ring is a ring that physically corresponds to one Ethernet
ring topology.
S
SPE The SPE devices are core devices that are located within a VPLS
full-meshed network. The UPE devices that are connected with the
SPE devices are similar to the CE devices. The PWs set up between
the UPE devices and the SPE devices serve as the ACs of the SPE
devices. The SPE devices must learn the MAC addresses of all the
sites on UPE side and those of the UPE interfaces that are
connected with the SPE.SPE is sometimes called NPE.
split-horizon function The split-horizon function is used to prohibit traffic interchange
between PBB-TE tunnels on one device.
static LACP mode Static LACP mode refers to a link aggregation method of selecting
active and inactive interfaces by negotiating aggregation
parameters through LACPDUs. In static LACP mode, LACP
determines active and inactive links of the link aggregation group.
It is also called M:N mode, that is, M active links and N backup
links. The M:N mode provides higher reliability and load
balancing can be implemented among M links.

T
Transit Node Transit nodes are all the nodes except the master node on an RRPP
major ring.
U
UPE A PE device that is directly connected with the CE devices. UPE
supports routing and MPLS encapsulation. If a UPE is connected
with multiple CEs and possesses the basic bridge function, frame
forwarding is performed only on the UPE. This decreases the
burden of the SPE.
V
VLAN Virtual Local Area Network. A technology logically divides a
LAN according to different functions or departments without
considering their physical locations. Each VLAN is a broadcast
domain.
VLAN Mapping VLAN mapping is used to implement VLAN convergence by
mapping one or more downstream VLANs to an upstream VLAN.
The downstream VLAN is the VLAN that the interface at the user
side belongs to and is used to identify a user or a class of users.
The downstream VLAN is also called the Customer-VLAN (C-
VLAN). The upstream VLAN is specified by the Internet Service
Provider (ISP) at the network side and is used to identify a type of
service. The upstream VLAN is also called the Service-VLAN (S-
VLAN).
VLAN Stacking The VLAN stacking technology adds a layer of VLAN tag to the
incoming packet. The VLAN stacking technology implements
transparent transmission of C-VLANs in the ISP network to realize
the application of Layer 2 Virtual Private Network (VPN).
VPLS A service that is used to connect more than one Ethernet LAN
segment through the PSN and make them operate in an
environment similar to a LAN.
VPWS A technology that bears Layer 2 services. VPWS emulates services
such as ATM, FR, Ethernet, low-speed TDM circuit, and SONET/
SDH in a PSN.
VSI An instance through which the physical access links of VPLS can
be mapped to the virtual links. Each VSI provides independent
VPLS service. VSI has Ethernet bridge function and can terminate
PW.

WAN Wide Area Network. A network that comprises PCs and stations
in a large area such as a state or a county.

Configuration Guide - LAN Access and MAN Access B Acronyms and Abbreviations
B Acronyms and Abbreviations
This appendix collates frequently used acronyms and abbreviations in this document.
Acronyms and Description
Abbreviations
A
ARP Address Resolution Protocol
B
BPDU Bridge Protocol Data Unit
C
CE Customer Edge
CIST Common and Internal Spanning Tree
COS Class of Service
CRC Cyclic Redundancy Check
CSMA/CD Carrier Sense Multiple Access/Collision Detect
CST Common Spanning Tree
F
FE Fast Ethernet
FIFO First in First out
FS Forced Switch
FSC Frame Check Sequence


Abbreviations
G
GE Gigabit Ethernet
H
HEC Head Error Check
I
ISP Internet Service Provider
IST Internal Spanning Tree
L
LACP Link Aggregation Control Protocol
LACPDU Link Aggregation Control Protocol Data Unit
LAG Link Aggregation Group
LAN Local Area Network
M
MAC Medium Access Control
MP2MP Multipoint-to-Multipoint
MS Manual Switch
MST BPDU Multiple Spanning Tree Bridge Protocol Data Unit
MSTI Multiple Spanning Tree Instance
MSTP Multiple Spanning Tree Protocol
MTU Maximum Transmission Unit
N
NMS Network Management System
O
OSI Open Systems Interconnection


Abbreviations
P
P2P Point-to-Point
PE Provider Edge
PLL Partial Link Lost
PSN Packet Switched Network
Q
QinQ 802.1Q-in-802.1Q
QoS Quality of Service
R
RRPP Rapid Ring Protection Protocol
RSTP Rapid Spanning Tree Protocol
S
SONET Synchronous Optical Network
STP Spanning Tree Protocol
T
TC Topology Checksum
TOS Type of Service
TP Topology Protection
TPID Tag Protocol Identifier
TLL Total Link Lost
TTL Time to Live
U
URPF Unicast Reverse Path Forwarding
V
VLAN Virtual Local Area Network


Abbreviations
VPLS Virtual Private LAN Service
VSI Virtual Switch Instance
W
WTR Wait to Restore


Configuration Guide - LAN Access and MAN Access (V600R003C00 - 02)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Configuration Guide - LAN Access and MAN Access (V600R003C00 - 02)

Hochgeladen von

Copyright:

HUAWEI NetEngine80E/40E Router

Configuration Guide - LAN Access

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2011-09-10) Huawei Proprietary and Confidential i

About This Document

Product Name Version

HUAWEI NetEngine80E/40E V600R003C00

Issue 02 (2011-09-10) Huawei Proprietary and Confidential ii

Alerts you to a high risk hazard that could, if not avoided,

Alerts you to a medium or low risk hazard that could, if

Alerts you to a potentially hazardous situation that could,

NOTE Provides additional information to emphasize or

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

# A line starting with the # sign is comments.

Issue 02 (2011-09-10) Huawei Proprietary and Confidential iii

Changes in Issue 02 (2011-09-10)

Changes in Issue 01 (2011-06-30)

Issue 02 (2011-09-10) Huawei Proprietary and Confidential iv

About This Document.....................................................................................................................ii

2 Ethernet Interface Configuration.............................................................................................46

Issue 02 (2011-09-10) Huawei Proprietary and Confidential v

2.1.1 Introduction to Ethernet Interfaces..........................................................................................................47

3 Eth-Trunk Interface Configuration..........................................................................................74

Issue 02 (2011-09-10) Huawei Proprietary and Confidential vi

3.2.6 Checking the Configuration.....................................................................................................................85

Issue 02 (2011-09-10) Huawei Proprietary and Confidential vii

3.7.6 (Optional) Configuring a Load Balancing Mode for an Eth-Trunk Interface.......................................115

Issue 02 (2011-09-10) Huawei Proprietary and Confidential viii

Issue 02 (2011-09-10) Huawei Proprietary and Confidential ix

4.8.1 Establishing the Configuration Task.....................................................................................................251

Issue 02 (2011-09-10) Huawei Proprietary and Confidential x

5.3 Configuring Selective QinQ on a Layer 2 Interface.......................................................................................353

Issue 02 (2011-09-10) Huawei Proprietary and Confidential xi

5.9.2 Configuring the Interface Mode as the User-Termination Mode..........................................................386

Issue 02 (2011-09-10) Huawei Proprietary and Confidential xii

Issue 02 (2011-09-10) Huawei Proprietary and Confidential xiii

6.2.4 (Optional) Setting the Path Cost for a Port............................................................................................671

Issue 02 (2011-09-10) Huawei Proprietary and Confidential xiv

7.3.3 Adding an Interface to an MSTP Process - Access Links.....................................................................733

8 BPDU Tunnel Configuration..................................................................................................824

Issue 02 (2011-09-10) Huawei Proprietary and Confidential xv

8.2.2 Enabling STP function on the PEs and the CEs....................................................................................832

Issue 02 (2011-09-10) Huawei Proprietary and Confidential xvi

9.4 Configuring RRPP Snooping..........................................................................................................................893

Issue 02 (2011-09-10) Huawei Proprietary and Confidential xvii

1 MAC Address Table Configuration

About This Chapter

1.1 MAC Address Table Introduction

Issue 02 (2011-09-10) Huawei Proprietary and Confidential 1

1.1 MAC Address Table Introduction

1.1.1 MAC Address Table Overview

MAC address entries are classified into the following types:

1.1.2 MAC Addresses Learning Limit Supported by the NE80E/40E

1.2 Configuring the MAC Address Table Based on the

Issue 02 (2011-09-10) Huawei Proprietary and Confidential 2

1.2.1 Establishing the Configuration Task

1.2.2 Configuring MAC Address Entries

Issue 02 (2011-09-10) Huawei Proprietary and Confidential 3