Configuration Guide - Reliability (V600R003C00 - 02)

HUAWEI NetEngine80E/40E Router
V600R003C00
Configuration Guide - Reliability
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 - Reliability About This Document
About This Document
Purpose
With regard to functions, configuration methods, and maintenance and configuration examples,
this document describes the reliability configurations, which includes the reliability overview,
interface backup configuration, APS Configuration, VRRP configuration, BFD configuration,
GR Configuration, NSR Configuration, Ethernet OAM Configuration, Y.1731 configuration,
MPLS-TP OAM configuration, Multi-Device Backup configuration.
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 (Optional)

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 in Issue 02 (2011-09-10)
Second commercial release.
l APS Configuration
– The feature of APS 1+1 bidirectional protection switchover is supported so that the
command keyword and description about this feature is added in 3.2.4 (Optional)
Configuring a Working Mode for an APS Group and 3.3.4 Configuring a Working
Mode for an APS Group.
– The feature of low-priority signal failure code for a switching request carried in the K
byte on the protect interface is supported so that the command keyword and description
about this feature is added in 3.2.3 Configuring a Protection Interface in an APS
Group and 3.3.3 Configuring a Protection Interface in an APS Group.
l Y.1731 Configuration
– 9.10.12 Example for Configuring Y.1731 Statistics Based on QoS Simple Traffic
Classification is added in this chapter.
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Changes in Issue 01 (2011-06-30)

Initial commercial release.
Issue 02 (2011-09-10) Huawei Proprietary and Confidential iv

Configuration Guide - Reliability Contents
Contents
About This Document.....................................................................................................................ii

1 Reliability Overview.....................................................................................................................1
1.1 Introduction........................................................................................................................................................2
1.1.1 Overview of Reliability Technologies.......................................................................................................2
1.1.2 Indices of Reliability.................................................................................................................................2
1.1.3 Levels of Reliability Requirements...........................................................................................................3
1.1.4 Principles for High-Reliablity IP Networking...........................................................................................3
1.2 Reliability Technologies for IP Networks..........................................................................................................4
1.2.1 Failure Detection for IP Networks.............................................................................................................4
1.2.2 Protection Switching for IP Networks.......................................................................................................4
1.3 Reliability Technologies Supported by the NE80E/40E....................................................................................5
1.3.1 FRR (Fast ReRoute)..................................................................................................................................5
1.3.2 OAM (Operation Administration & Maintenance)...................................................................................7
1.3.3 VRRP (Virtual Router Redundancy Protocol)..........................................................................................7
1.3.4 BFD (Bidirectional Forwarding Detection)...............................................................................................8
1.4 Networking of Reliability over an IP Network..................................................................................................8
1.4.1 Failures on Intermediate Nodes or on the Link Between PEs - LDP FRR/TE FRR.................................8
1.4.2 Link Failure During Transmission............................................................................................................9
1.4.3 Failure on the Remote PE - VPN FRR....................................................................................................11
1.4.4 Failure of Downlink Interface on the PE - IP FRR.................................................................................12
2 Interface Backup Configuration...............................................................................................13

2.1 Introduction of Interface Backup......................................................................................................................14
2.1.1 Interface Backup Overview.....................................................................................................................14
2.1.2 Characteristics of the Interface Backup Supported by the NE80E/40E..................................................15
2.2 Configuring the Active/Standby Interface Backup...........................................................................................16
2.2.1 Establishing the Configuration Task.......................................................................................................16
2.2.2 Configuring a Standby Interface..............................................................................................................17
2.2.3 Configuring the Active/Standby Switchover Delay................................................................................18
2.2.4 Checking the Configuration.....................................................................................................................18
2.3 Configuring the Load Balancing Interface Backup..........................................................................................19
2.3.2 Configuring a Standby Interface..............................................................................................................20
Issue 02 (2011-09-10) Huawei Proprietary and Confidential v

2.3.3 Configuring the Percentage Thresholds for Load Balancing..................................................................21

2.3.4 (Optional) Configuring the Bandwidth and Flow Check Interval for the Active Interface.....................21
2.4 Maintaining the Interface Backup....................................................................................................................23
2.4.1 Monitoring Working Status of the Interface Backup..............................................................................23
2.5 Configuration Examples...................................................................................................................................23
2.5.1 Example for Configuring the Active/Standby Mode of Multiple Interfaces...........................................23
2.5.2 Example for Configuring Load Balancing on Multiple Standby Interfaces............................................27
3 APS Configuration......................................................................................................................31
3.1 APS Overview..................................................................................................................................................32
3.1.1 APS Overview.........................................................................................................................................32
3.1.2 APS Features Supported by the NE80E/40E...........................................................................................34
3.2 Configuring Single-Device APS......................................................................................................................35
3.2.2 Configuring a Working Interface in an APS Group................................................................................35
3.2.3 Configuring a Protection Interface in an APS Group..............................................................................36
3.2.4 (Optional) Configuring a Working Mode for an APS Group..................................................................37
3.2.5 (Optional) Configuring a Switching Mode for an APS Group................................................................38
3.2.6 (Optional) Setting the WTR Time for an APS Group.............................................................................39
3.2.7 Adding Members of an APS Group to a Trunk.......................................................................................39
3.3 Configuring E-APS...........................................................................................................................................41
3.3.2 Configuring a Working Interface in an APS Group................................................................................42
3.3.3 Configuring a Protection Interface in an APS Group..............................................................................43
3.3.4 Configuring a Working Mode for an APS Group...................................................................................44
3.3.5 (Optional) Configuring a Switching Mode for an APS Group................................................................45
3.3.6 (Optional) Setting the Interval for Sending APS Negotiation Messages and the Hold Time of an APS
Connection........................................................................................................................................................45
3.3.7 (Optional) Configuring the Authentication String for a PGP Message...................................................46
3.3.8 (Optional) Setting the WTR Time for an APS Group.............................................................................47
3.3.9 Adding Members of an APS Group to a Trunk.......................................................................................48
3.3.10 Checking the Configuration...................................................................................................................48
3.4 Configuration Examples...................................................................................................................................49
3.4.1 Example for Configuring TDM on the CPOS interfaces Configured with APS.....................................49
3.4.2 Example for Configuring APS on a CPOS-Trunk...................................................................................56
3.4.3 Example for Associating PW Redundancy with E-APS Working in 1:1 Mode.....................................59
4 VRRP Configuration...................................................................................................................73
4.1 VRRP Introduction...........................................................................................................................................75
4.1.1 VRRP Overview......................................................................................................................................75
4.1.2 VRRP Features Supported by the NE80E/40E........................................................................................75
4.2 Configuring the VRRP Backup Group.............................................................................................................79
Issue 02 (2011-09-10) Huawei Proprietary and Confidential vi


4.2.2 Creating a Backup Group and Configuring a Virtual IP Address...........................................................80
4.2.3 Configuring Priorities for Interfaces Where a Backup Group Is Created...............................................82
4.3 Configuring VRRP to Track the Status of an Interface....................................................................................85
4.3.2 Configuring VRRP to Track the Status of an Interface...........................................................................86
4.4 Configuring a Fast VRRP Switchover (in Common Mode).............................................................................89
4.4.2 Tracking the BFD Session Status............................................................................................................90
4.4.3 Tracking the BFD Session Status............................................................................................................93
4.4.4 Tracking the Status of the SPU Group....................................................................................................95
4.5 Configuring VRRP Fast Switchover (Using BFD Sampling)..........................................................................97
4.5.2 Binding the Service VRRP Backup Group to the mVRRP Backup Group.............................................99
4.5.3 Configuring an mVRRP Backup Group to Track the BFD Session Status...........................................100
4.5.4 Setting the Threshold for VRRP Fast Switchover.................................................................................101
4.5.5 Enabling the Association Between the mVRRP Backup Group Status and the Route.........................102
4.6 Configuring Ignorance of the Down of an Interface Where the mVRRP Backup Group Is Configured.......104
4.6.1 Establishing the Configuration Task.....................................................................................................104
4.6.2 Configuring the mVRRP Backup Group...............................................................................................106
4.6.3 Binding the Service VRRP Backup Group to the mVRRP Backup Group...........................................107
4.6.4 Configuring an mVRRP Backup Group to Track the BFD Session Status...........................................107
4.6.5 Setting the Threshold for VRRP Fast Switchover.................................................................................109
4.6.6 Enabling the Association Between the mVRRP Backup Group Status and the Route.........................109
4.7 Configuring VRRP Applications in VLANIF................................................................................................111
4.7.2 Configuring VRRP on VLANIF............................................................................................................112
4.7.3 (Optional) Configuring the Sending Mode of VRRP Packets in Super-VLAN....................................112
4.8 Configuring VRRP Security...........................................................................................................................114
4.8.2 Configuring the Authentication Mode of VRRP Packets......................................................................115
4.9 Configuring VRRP Smooth Switching...........................................................................................................116
4.9.2 Configuring VRRP Smooth Switching..................................................................................................117
Issue 02 (2011-09-10) Huawei Proprietary and Confidential vii

4.10 Adjusting and Optimizing VRRP.................................................................................................................119

4.10.1 Establishing the Configuration Task...................................................................................................119
4.10.2 Configuring the Interval for Sending VRRP Advertising Messages...................................................120
4.10.3 Configuring the Preemption Delay Time of Backup Group Router s.................................................121
4.10.4 Enabling the Reachability Test of the Virtual IP Address...................................................................123
4.10.5 Disabling a Router from Checking Number of Hops in VRRP Packets.............................................123
4.10.6 Configuring the Timeout Time of Sending Gratuitous ARP Packets by the Master router................124
4.10.7 Checking the Configuration.................................................................................................................125
4.11 Configuring mVRRP Backup Groups..........................................................................................................126
4.11.2 Configuring mVRRP Backup Group...................................................................................................128
4.11.3 (Optional) Configuring Member VRRP Backup Groups and Binding them to the mVRRP Backup Group
........................................................................................................................................................................129
4.11.4 (Optional) Binding Member Interface and Management Backup Group............................................130
4.11.5 (Optional) Binding the PW to the mVRRP Backup Group Through VPLS.......................................131
4.12 Configuring VRRP Version Upgrade...........................................................................................................132
4.12.2 Configuring VRRPv3..........................................................................................................................133
4.13 Maintaining VRRP.......................................................................................................................................134
4.13.1 Monitoring the VRRP Running...........................................................................................................134
4.14 Configuration Examples...............................................................................................................................135
4.14.1 Example for Configuring VRRP in Master/Backup Mode.................................................................135
4.14.2 Example for Configuring VRRP in Load Balancing Mode................................................................139
4.14.3 Example for Configuring the Multi-Instance VRRP...........................................................................143
4.14.4 Example for Configuring VRRP Fast Switchover..............................................................................149
4.14.5 Example for Configuring VRRP Fast Switchover (Using One-Arm Echo Function)........................153
4.14.6 Example for Configuring VRRP Fast Switchover (Using BFD Sampling)........................................160
4.14.7 Example for Configuring Ignorance of the Down of an Interface Where the mVRRP Backup Group Is
Configured......................................................................................................................................................179
4.14.8 Example for Configuring VRRP on VLANIF Interfaces....................................................................199
4.14.9 Example for Configuring VRRP on Sub-interfaces for QinQ VLAN Tag Termination to Reduce the
Number of Gratuitous ARP Packets to Be Sent.............................................................................................206
4.14.10 Example for Configuring VRRP for IPv6 on Sub-interfaces for QinQ VLAN Tag Termination to
Reduce the Number of ND Packets to Be Sent..............................................................................................214
4.14.11 Example for Configuring a VRRP6 Backup Group in Master/Backup Mode..................................222
4.14.12 Example for Configuring VRRP6 Backup Groups in Load Balancing Mode..................................227
5 BFD Configuration....................................................................................................................232
5.1 Introduction to BFD........................................................................................................................................234
5.1.1 BFD Overview.......................................................................................................................................234
5.1.2 BFD Features Supported by the NE80E/40E........................................................................................234
5.2 Configuring Single-hop BFD.........................................................................................................................242
Issue 02 (2011-09-10) Huawei Proprietary and Confidential viii


5.2.2 Enabling BFD Globally.........................................................................................................................242
5.2.3 Setting Up a BFD Session.....................................................................................................................243
5.3 Configuring the BFD Passive Echo Function.................................................................................................246
5.3.2 Configuring the BFD Passive Echo Function........................................................................................247
5.4 Configuring the Association Between the BFD Status and the Interface Status............................................248
5.4.2 Configuring the Association Between BFD Status and Interface Status...............................................249
5.5 Configuring the Association Between the BFD Status and the Sub-Interface Status....................................251
5.5.2 Configuring the Association Between BFD Status and Sub-Interface Status.......................................252
5.6 Configuring the BFD to Modify the PST.......................................................................................................254
5.6.2 Permitting the BFD to Modify the PST.................................................................................................255
5.7 Configuring the Multi-Hop BFD....................................................................................................................257
5.7.3 Setting Up a BFD Session.....................................................................................................................258
5.8 Configuring a BFD Session with Automatically Negotiated Discriminators.................................................261
5.8.3 Configuring a BFD Session with Automatically Negotiated Discriminators........................................262
5.9 Configuring the Delay of a BFD Session to Go Up.......................................................................................264
5.9.2 Configuring the Delay of a BFD Session to Go Up..............................................................................264
5.10 Configuring a BFD Session with the One-Arm Echo Function...................................................................266
5.10.2 Enable BFD Globally..........................................................................................................................267
5.10.3 Establishing a BFD Session.................................................................................................................267
5.11 Adjusting BFD Parameters...........................................................................................................................269
5.11.2 Modifying the Detection Time............................................................................................................270
Issue 02 (2011-09-10) Huawei Proprietary and Confidential ix

5.11.3 Configuring the BFD WTR.................................................................................................................270

5.11.4 Adding the Description of a BFD Session...........................................................................................271
5.12 Globally Configuring the Destination Port Number for the Multi-Hop BFD Control Packet.....................273
5.12.2 Globally Configuring the Destination Port Number............................................................................274
5.13 Configuring the TTL Globally.....................................................................................................................276
5.13.2 Configuring the TTL Globally............................................................................................................276
5.14 Configuring the Interval at Which Trap Messages Are Sent........................................................................278
5.14.2 Configuring the Interval at Which Trap Messages Are Sent...............................................................278
5.15 Maintaining BFD..........................................................................................................................................279
5.15.1 Clearing BFD Statistics.......................................................................................................................279
5.15.2 Monitoring BFD Status.......................................................................................................................280
5.16.1 Example for Configuring Single-hop BFD for a Layer 3 Physical Link.............................................281
5.16.2 Example for Configuring Single-hop BFD for an IP-Trunk Member Link........................................284
5.16.3 Example for Configuring Singe-hop BFD for an IP-Trunk Link........................................................289
5.16.4 Example for Configuring Single-hop BFD for a Layer 3 Eth-Trunk Member Link...........................295
5.16.5 Example for Configuring Single-hop BFD for a Layer 3 Eth-Trunk Link..........................................300
5.16.6 Example for Configuring Single-hop BFD for VLANIF Interfaces...................................................306
5.16.7 Example for Configuring the Association Between the BFD Status and the Interface Status............310
5.16.8 Example for Configuring the Association Between the BFD Status and the Sub-interface Status.....314
5.16.9 Example for Configuring Multi-Hop BFD..........................................................................................319
5.16.10 Example for Configuring the BFD Demand Mode...........................................................................322
5.16.11 Example for Configuring a BFD Session with the One-Arm Echo Function...................................325
5.16.12 Example for Configuring BFD for VPN Routes...............................................................................327
5.16.13 Example for Configuring Sub-interfaces for Dot1q VLAN Tag Termination to Support BFD.......332
5.16.14 Example for Configuring Sub-interfaces for QinQ VLAN Tag Termination to Support BFD.........339
5.16.15 Example for Configuring Single-hop BFD6 for a Layer 3 Physical Link.........................................347
5.16.16 Example for Configuring Multi-hop BFD6.......................................................................................350
6 GR Configuration......................................................................................................................354
6.1 GR Introduction..............................................................................................................................................355
6.1.1 HA Overview.........................................................................................................................................355
6.1.2 GR Features Supported in the NE80E/40E...........................................................................................362
6.2 Configuring the System-Level GR.................................................................................................................362
6.2.2 (Optional) Configuring the Default Slot Number for the SMB.............................................................363
Issue 02 (2011-09-10) Huawei Proprietary and Confidential x

6.2.3 Enabling the Automatic Synchronization of the AMB/SMB Configuration........................................364

6.2.4 Enabling the Force AMB/SMB Switchover..........................................................................................364
6.2.5 (Optional) Restarting the SMB..............................................................................................................365
6.3 Maintaining HA..............................................................................................................................................366
6.3.1 Monitoring the Running of HA.............................................................................................................366
6.4 Configuration Examples.................................................................................................................................366
6.4.1 Example for Configuring the System-Level GR...................................................................................366
7 NSR Configuration................................................................................................................... 371

7.1 NSR Overview................................................................................................................................................372
7.1.1 Introduction to NSR...............................................................................................................................372
7.1.2 NSR Features Supported by the NE80E/40E........................................................................................374
7.2 Configuring NSR............................................................................................................................................375
7.2.2 Enabling NSR........................................................................................................................................376
8 Ethernet OAM Configuration.................................................................................................377

8.1 Ethernet OAM Overview................................................................................................................................379
8.1.1 Introduction to Ethernet OAM..............................................................................................................379
8.1.2 Ethernet OAM Supported by the NE80E/40E.......................................................................................379
8.2 Configuring Basic EFM OAM.......................................................................................................................390
8.2.2 Enabling EFM OAM Globally..............................................................................................................390
8.2.3 Configuring the Working Mode of EFM OAM on an Interface...........................................................391
8.2.4 (Optional) Setting the Maximum Size of an EFM OAMPDU..............................................................392
8.2.5 (Optional) Setting the Timeout Period for Waiting for OAM PDUs....................................................392
8.2.6 Enabling EFM OAM on an Interface....................................................................................................393
8.3 Configuring EFM OAM Link Monitoring.....................................................................................................394
8.3.2 (Optional) Detecting Errored Frames of EFM OAM............................................................................395
8.3.3 (Optional) Detecting Errored Codes of EFM OAM..............................................................................396
8.3.4 (Optional) Detecting Errored Frame Seconds of EFM OAM...............................................................396
8.4 Testing the Packet Loss Ratio on the Physical Link......................................................................................398
8.4.2 Enabling EFM OAM Remote Loopback...............................................................................................399
8.4.3 Sending Test Packets.............................................................................................................................400
8.4.4 Checking the Statistics on Returned Test Packets.................................................................................401
8.4.5 (Optional) Manually Disabling EFM OAM Remote Loopback............................................................401
8.5 Associating EFM OAM with an Interface......................................................................................................403
Issue 02 (2011-09-10) Huawei Proprietary and Confidential xi


8.5.2 Associating EFM OAM with an Interface.............................................................................................404
8.6 Configuring Basic Ethernet CFM...................................................................................................................405
8.6.2 Switching IEEE 802.1ag Versions........................................................................................................407
8.6.3 Enabling Ethernet CFM Globally..........................................................................................................407
8.6.4 Creating an MD.....................................................................................................................................408
8.6.5 (Optional) Creating the Default MD.....................................................................................................408
8.6.6 Creating an MA.....................................................................................................................................409
8.6.7 Creating a MEP.....................................................................................................................................410
8.6.8 Creating an RMEP.................................................................................................................................411
8.6.9 (Optional) Setting the Rule for Creating a MIP....................................................................................412
8.6.10 Enabling CC Detection........................................................................................................................413
8.6.11 (Optional) Creating a VLAN...............................................................................................................414
8.7 Configuring Related Parameters of Ethernet CFM........................................................................................419
8.7.2 (Optional) Configuring the RMEP Activation Time.............................................................................420
8.7.3 (Optional) Configuring the Anti-Jitter Time During Alarm Restoration..............................................421
8.7.4 (Optional) Configuring the Anti-Jitter Time During Alarm Generation...............................................421
8.8 Fault Verification on the Ethernet..................................................................................................................422
8.8.2 (Optional) Implementing 802.1ag MAC Ping.......................................................................................423
8.8.3 (Optional) Implementing Gmac ping....................................................................................................424
8.9 Locating the Fault on the Ethernet.................................................................................................................424
8.9.2 (Optional) Implementing 802.1ag MAC Trace.....................................................................................425
8.9.3 (Optional) Implementing Gmac trace....................................................................................................426
8.10 Associating Ethernet CFM with an Interface...............................................................................................427
8.10.2 Associating Ethernet CFM with an Interface......................................................................................430
8.11 Associating EFM OAM with Ethernet CFM................................................................................................431
8.11.2 Associating Ethernet OAM with Ethernet OAM................................................................................432
8.12 Associating Ethernet CFM with VPLS........................................................................................................433
8.12.2 Configuring Ethernet CFM Based on the VPLS Between the PEs.....................................................434
8.12.3 Configuring Ethernet CFM Between the CE and Local PE................................................................435
8.12.4 Configuring Ethernet CFM Between the CE and Peer PE..................................................................437
Issue 02 (2011-09-10) Huawei Proprietary and Confidential xii


8.13 Associating Ethernet CFM with VLL (by Using Sub-interfaces for QinQ VLAN Tag Termination).........438
8.13.2 Configuring Ethernet CFM on PEs on a VLL.....................................................................................439
8.13.3 Configuring Ethernet CFM on the Switch and Local PE....................................................................441
8.13.4 Configuring Ethernet CFM on the Switch and Remote PE.................................................................443
8.14 Associating Ethernet CFM with VPLS (by Using Sub-interfaces for QinQ VLAN Tag Termination)
..............................................................................................................................................................................446
8.14.2 Configuring Ethernet CFM on PEs on a VPLS...................................................................................447
8.14.3 Configuring Ethernet CFM on the Switch and Local PE....................................................................448
8.14.4 Configuring Ethernet CFM on the Switch and Remote PE.................................................................449
8.15 Associating Ethernet OAM with MPLS OAM or BFD...............................................................................452
8.15.2 Configuring Ethernet OAM Functions................................................................................................453
8.15.3 Associating Ethernet OAM with MPLS OAM or BFD......................................................................453
8.16 Configuring Ethernet CFM and 1+1 Protection of Multicast VLANs.........................................................455
8.17 Maintaining Ethernet OAM..........................................................................................................................455
8.17.1 Clearing the Statistics on Error CCMs................................................................................................455
8.17.2 Monitoring the Running Status of Ethernet OAM..............................................................................455
8.18.1 Example for Configuring EFM OAM.................................................................................................456
8.18.2 Example for Testing the Packet Loss Ratio on the Link.....................................................................459
8.18.3 Example for Configuring Ethernet CFM.............................................................................................463
8.18.4 Example for Configuring the Default MD for Ethernet CFM.............................................................471
8.18.5 Example for Associating Ethernet CFM with an Interface.................................................................478
8.18.6 Example for Associating EFM OAM with Ethernet CFM..................................................................484
8.18.7 Example for Configuring VPLS Ethernet CFM..................................................................................488
8.18.8 Example for Configuring VPLS-based Ethernet CFM Through Sub-interfaces for QinQ VLAN Tag
Termination....................................................................................................................................................499
8.18.9 Example for Configuring VLL-based Ethernet CFM Through Sub-interfaces for QinQ VLAN Tag
Termination....................................................................................................................................................512
8.18.10 Example for Associating EFM OAM with MPLS OAM..................................................................521
8.18.11 Example for Configuring EFM OAM Extension for VRRP.............................................................531
8.18.12 Exmaple for Configuring EFM OAM Extension for Static Routes..................................................541
9 Y.1731 Configuration................................................................................................................552
9.1 Introduction....................................................................................................................................................554
9.1.1 Y.1731 Overview...................................................................................................................................554
9.1.2 Y.1731 Features Supported by the NE80E/40E....................................................................................557
9.2 Configuring Single-Ended Frame Loss Measurement on a VLL...................................................................558
Issue 02 (2011-09-10) Huawei Proprietary and Confidential xiii


9.2.2 Binding an MA to a VLL......................................................................................................................559
9.2.3 Configuring LMM Reception on a Remote MEP.................................................................................561
9.2.4 Enabling Single-Ended Frame Loss Measurement on a VLL...............................................................562
9.3 Configuring Dual-Ended Frame Loss Measurement on a VLL.....................................................................566
9.3.3 Enabling Dual-Ended Frame Loss Measurement on a VLL.................................................................569
9.4 Configuring One-Way Frame Delay Measurement on a VLL.......................................................................570
9.4.3 Configuring DM Frame Reception on the Remote Device...................................................................573
9.4.4 Enabling One-Way Frame Delay Measurement on a VLL...................................................................574
9.5 Configuring Two-Way Frame Delay Measurement on a VLL......................................................................577
9.5.3 Configuring DMM Reception on a Remote Device..............................................................................580
9.5.4 Enabling Two-Way Frame Delay Measurement on a VLL...................................................................581
9.6 Configuring Single-Ended Frame Loss Measurement on a VPLS Network..................................................584
9.6.2 Binding an MA to a VPLS Network.....................................................................................................586
9.6.3 Configuring LMM Reception on a Remote MEP.................................................................................586
9.6.4 Enabling Single-Ended Frame Loss Measurement on a VPLS Network..............................................587
9.7 Configuring Dual-Ended Frame Loss Measurement on a VPLS Network....................................................589
9.7.3 Enabling Dual-Ended Frame Loss Measurement on a VPLS Network................................................591
9.8 Configuring One-Way Frame Delay Measurement on a VPLS Network......................................................592
9.8.3 Configuring DM Frame Reception on a Remote Device......................................................................594
9.8.4 Enabling One-Way Frame Delay Measurement on a VPLS Network..................................................595
9.9 Configuring Two-Way Frame Delay Measurement on a VPLS Network.....................................................596
Issue 02 (2011-09-10) Huawei Proprietary and Confidential xiv

9.9.3 Configuring DMM Reception on a Remote MEP.................................................................................599

9.9.4 Enabling Two-Way Frame Delay Measurement on a VPLS Network..................................................599
9.10.1 Example for Configuring On-Demand Single-Ended Frame Loss Measurement on a VLL..............601
9.10.2 Example for Configuring Proactive Single-Ended Frame Loss Measurement on a VLL...................605
9.10.3 Example for Configuring Proactive Dual-Ended Frame Loss Measurement on a VLL.....................609
9.10.4 Example for Configuring On-Demand One-way Frame Delay Measurement on a VLL...................613
9.10.5 Example for Configuring Proactive One-Way Frame Delay Measurement on a VLL.......................617
9.10.6 Example for Configuring On-Demand Two-Way Frame Delay Measurement on a VLL..................621
9.10.7 Example for Configuring Proactive Two-Way Frame Delay Measurement on a VLL......................626
9.10.8 Example for Configuring On-Demand Single-Ended Frame Loss Measurement on a VPLS Network
........................................................................................................................................................................630
9.10.9 Example for Configuring Proactive Dual-Ended Frame Loss Measurement on a VPLS Network
........................................................................................................................................................................635
9.10.10 Example for Configuring On-Demand One-way Frame Delay Measurement on a VPLS Network
........................................................................................................................................................................641
9.10.11 Example for Configuring On-Demand Two-way Frame Delay Measurement on a VPLS Network
........................................................................................................................................................................647
9.10.12 Example for Configuring Y.1731 Statistics Based on QoS Simple Traffic Classification...............654
10 MPLS-TP OAM Configuration.............................................................................................662

10.1 Introduction..................................................................................................................................................663
10.1.1 MPLS-TP OAM Overview..................................................................................................................663
10.1.2 MPLS-TP OAM Features Supported by the NE80E/40E...................................................................663
10.2 Configuring MPLS-TP OAM for an LSP.....................................................................................................664
10.2.2 Creating an ME and Binding It to a Tunnel Interface.........................................................................666
10.2.3 (Optional) Configuring CC and CV for an LSP..................................................................................667
10.2.4 (Optional) Configuring LB for an LSP................................................................................................669
10.2.5 (Optional) Configuring LM for an LSP...............................................................................................669
10.2.6 (Optional) Configuring DM for an LSP..............................................................................................671
10.2.7 (Optional) Configuring AIS for an LSP..............................................................................................672
10.3 Configuring MPLS-TP OAM for a PW.......................................................................................................675
10.3.2 Creating an ME and Binding It to a PW..............................................................................................677
10.3.3 (Optional) Configuring CC and CV for a PW.....................................................................................678
10.3.4 (Optional) Configuring LB (to Be Performed at a Specified Time) for a PW....................................680
10.3.5 (Optional) Configuring LM for a PW..................................................................................................681
10.3.6 (Optional) Configuring DM for a PW.................................................................................................683
10.4.1 Example for Configuring CC and CV for an LSP...............................................................................687
Issue 02 (2011-09-10) Huawei Proprietary and Confidential xv

10.4.2 Example for Configuring LB for an LSP............................................................................................691

10.4.3 Example for Configuring LM for an LSP...........................................................................................694
10.4.4 Example for Configuring DM for an LSP...........................................................................................698
10.4.5 Example for Configuring AIS for an LSP...........................................................................................702
10.4.6 Example for Configuring CC and CV for a PW..................................................................................705
10.4.7 Example for Configuring LB for a PW...............................................................................................710
10.4.8 Example for Configuring LM for a PW..............................................................................................714
10.4.9 Example for Configuring DM for a PW..............................................................................................718
11 Multi-Device Backup Configuration...................................................................................723

11.1 Introduction..................................................................................................................................................724
11.1.1 Introduction to Multi-Device Backup..................................................................................................724
11.1.2 Multi-Device Backup Supported by the NE80E/40E..........................................................................724
11.2 Establishing the Multi-Device Backup Platform..........................................................................................726
11.2.2 Configuring VRRP..............................................................................................................................727
11.2.3 Configuring the Remote Backup Service............................................................................................728
11.2.4 Configuring a Remote Backup Profile................................................................................................729
11.3 Configuring Dual-Device ARP Hot Backup................................................................................................730
11.3.2 Configuring an RBP for ARP Service Backup....................................................................................731
11.3.3 Binding the Remote Backup Profile to the Interface...........................................................................731
11.4 Maintaining Multi-Device Backup...............................................................................................................733
11.4.1 Displaying Backup Information..........................................................................................................733
11.4.2 Clearing Backup Information..............................................................................................................733
11.5.1 Example for Configuring Dual-Device ARP Hot Backup..................................................................734
A Glossary......................................................................................................................................740
B Acronyms and Abbreviations.................................................................................................743
Issue 02 (2011-09-10) Huawei Proprietary and Confidential xvi

Configuration Guide - Reliability 1 Reliability Overview
1 Reliability Overview
About This Chapter
Reliability of a network can be improved mainly in two methods. One method is to use an
effective detection mechanism to implement FRR and the other is to provide a reliable
networking scheme.
1.1 Introduction
Reliability is a technology that can shorten traffic interruption time on a network and improve
network performance.
1.2 Reliability Technologies for IP Networks
This section describes two typical reliability technologies, failure detection and switchover.
1.3 Reliability Technologies Supported by the NE80E/40E
Reliability technologies for IP networks include failure detection technologies and protection
switching technologies.
1.4 Networking of Reliability over an IP Network
This section describes FRR applicable scenarios and FRR solutions.
Issue 02 (2011-09-10) Huawei Proprietary and Confidential 1

1.1 Introduction
Reliability is a technology that can shorten traffic interruption time on a network and improve
network performance.
1.1.1 Overview of Reliability Technologies

Reliability technologies are used to ensure high reliability on a network. Reliability technologies
cover system and hardware reliability design, software reliability design, reliability testing, and
IP network reliability design.
The reliability of a router involves the following aspects:
l System and hardware reliability design
l Software reliability design
l Test and authentication of reliability
l IP network reliability design
With the popularity of networks and diversification of applications, various value-added services
are deployed on networks. The bandwidth increases in index number. Therefore, even a short-
time interruption may impact a huge number of services critically and make an incredible loss.
For a fundamental network that bears services, its reliability is highlighted much more than ever.
This chapter focuses on reliability technologies applicable to the IP network over the Versatile
Routing Platform (NE80E/40E).
1.1.2 Indices of Reliability

Indices of reliability include MTTR, MTBF, and availability.
Generally, the reliability of a product or a system is evaluated based on two indices, namely,
Mean Time to Repair (MTTR) and Mean Time Between Failures (MTBF).
MTTR
The MTTR indicates the fault recovery capability. It is an index of maintainability. The MTTR
is the average time that a component or a device will take to recover from any failure. The MTTR,
in fact, is the fault-tolerance capability. In a broader sense, the MTTR also includes spare part
management and customer service. The MTTR is usually part of a maintenance contract.
The formula used to calculate the MTTR is as follows:
MTTR = Fault detection time + Board replacement time + System initialization time + Link
recovery time + Route coverage time + Forwarding recovery time
The smaller the addends are, the smaller the MTTR is and the higher the availability a device
offers.
MTBF
The MTBF indicates the probability of faults. It is an index of reliability. The MTBF is the
predicted elapsed time between inherent failures of a system during operation, usually in hours.

Availability
The availability identifies the utility of a system. You can improve the device availability by
increasing the MTBF and decreasing the MTTR.
In the telecommunication industry, 99.999% availability means that service interruption caused
by device failures must be less than 5 minutes each year.
In actual networking, network faults and service interruption are inevitable. Therefore, providing
technologies to enable device to recover from failures rapidly becomes very important. Such
technologies can improve device availability by reducing MTTR.
1.1.3 Levels of Reliability Requirements

The objective and implementation method of the reliability vary with the level of reliability
requirements.
Table 1-1 lists three requirement levels and describes their objectives and implementation
methods.
Table 1-1 Levels of reliability requirements

Level Objective Implementation Method
1 Less faults in the l Hardware: simplified design, standardized circuits,

software and hardware reliable application of components, reliability
of a system control over purchased components, reliable
manufacture, environment adaptability, and
reliability testing (HALT/HASS)
l Software: checklist for the software reliability design
2 No impact on a system l Redundancy design

when a default occurs l Switchover policy
l High availability of switchover
3 Rapid recovery from a l Fault detection

fault that affects the l Fault diagnosis
system
l Fault isolation
l Fault recovery
1.1.4 Principles for High-Reliablity IP Networking

Technologies for reliable networking cover the hierarchy networking, redundancy technology,
and load balancing technology.
The principles for high-reliablity IP networking are as follows:
l Hierarchical networking: A network is divided into three layers, core layer, convergence
layer, and edge layer. According to the current service status and future service prediction,
redundancy backup is required on a device connected to access nodes on the edge layer.
The active and standby nodes connect to convergence nodes. Devices of convergence layer
are dual-homed to single node multi-device of the upper layer or to multi-node device of

convergence layer and core layer alternatively. Devices of core layer are enabled with full
interconnection or half interconnection. In this manner, two devices are reachable to each
other with one route at a fast traffic rate, avoiding multi-interconnection.
l On the same layer, multi-interconnection is recommended; multi-device is applicable to a
single node.
l The lower-layer devices are dual-homed or multi-homed to single nodes or multiple nodes
of devices on the upper layer.
l Adjustment should be taken according to traffic.
1.2 Reliability Technologies for IP Networks

This section describes two typical reliability technologies, failure detection and switchover.
1.2.1 Failure Detection for IP Networks

Fault detection technologies are divided into special detection technologies and common
detection technologies.
l Special fault detection technologies include:
– Automatic Protection Switching (at the transport layer)
– Eth-OAM (at the link layer)
– MPLS OAM (for MPLS)
l Common fault detection technologies include the Bidirectional Forwarding Detection
(BFD) that detects faults at all layers, such as the data link layer and the network layer.
The fault detection mechanism is available to each layer of the TCP/IP reference module,
including:
l Transport/Physical layer: Automatic Protection Switching (APS)
l Data link layer: MPLS OAM, Eth-OAM, STP, RSTP, MSTP, and RRPP
l Network layer: Hello mechanism for protocols, VRRP, and GR
l Application layer: Heartbeat mechanism and retransmission mechanism for protocols
Fault detection has the following modes:
l Asynchronous mode: Detection packets are sent periodically.
l Query mode: A series of packets for confirmation are sent.
l Echo mode: The received packet is sent back to the sender without any change.
1.2.2 Protection Switching for IP Networks

The standard time of protection switching on a data communication network is 50 ms. Link
redundancy is a basis of protection switching.
Link protection involves:
l End-to-end protection: 1:1, 1+1, 1:N, and M:N
l Local protection: BFD trigger, FRR technology, and OAM technology
The trigger mode includes BFD trigger mode and Fast Reroute (FRR) trigger mode.

The protection switching has the following functions:
l Local request protection

l Local real-time protection
l Processing switchover signal latency
l Avoiding single-node switchover
l Coexistence and preemption of switchover requests
l Switchover recovery mode
1.3 Reliability Technologies Supported by the NE80E/40E

Reliability technologies for IP networks include failure detection technologies and protection
switching technologies.
1.3.1 FRR (Fast ReRoute)

FRR, classified into IP FRR, LDP FRR, MPLS TE FRR, and VPN FRR, is the most common
technology used to perform a fast switchover in case of a failure.
IP FRR
In the forwarding module, an interface status table is created to save information about working
status of every interface on a device. After an abnormality is detected, for example, the physical
link is unavailable or an interface is shut down manually, the interface status table is updated.
In addition, during packet forwarding, if the forwarding table contains load balancing entries,
that is, several next hops, the next hop is selected based on a certain rule and its outgoing interface
is detected in the interface status table. If the outgoing interface of one next hop is invalid, another
next hop is selected and its outgoing interface status is detected until the outgoing interface of
a next hop is valid.
When the last next hop is detected, the packet is forwarded directly without checking the
outgoing interface.
Because detecting and updating the interface status is much faster than route convergence, the
rerouting takes effect faster with the IP FRR technology. Moreover, the load balancing entries
in the forwarding table are checked that ensures highly-reliable forwarding.
The enhanced IP FRR technology supports the next hop of non-equivalence load balancer. An
active next hop is selected by the Interior Gateway Protocol (IGP) and a standby next hop is
configured manually. When a failure occurs, the fast switchover is performed.
LDP FRR
Conventional IP FRR cannot effectively protect traffic on a Multiprotocol Label Switching
(MPLS) network. The NE80E/40E provides MPLS networks with the LDP FRR for protection
at the interface level.
Compared with fast convergence in IGP, the LDP FRR calculates a secondary interface in
advance. Route calculation and re-establishment of an LSP after a failure take less time. As a
result, the switchover speeds up.

When LDP works in a mode of Downstream Unsolicited (DU) label distribution, ordered label
control and liberal label retention, a Label Switching Router (LSR) saves all label mapping
messages. Only the label mapping messages sent by the next hop corresponding to the
Forwarding Equivalence Class (FEC) can generate a label forwarding table.
With the preceding features, when a forwarding table is generated for mapping of liberal
retention label, this means that a bypass LSP is established. Normally, a packet is forwarded
through the primary LSP. When the outgoing interface of the primary LSP is Down, the packet
is forwarded along the bypass LSP. This ensures continuous traffic follow in the short period
before network convergence.
MPLS TE FRR
The MPLS TE FRR is a commonly used switchover technology to deal with a failure. The
solution is to create an end-to-end TE tunnel between Provider Edge (PE) devices and a bypass
Label Switched Path (LSP) for protecting a primary LSP. When the router detects that the
primary LSP is unavailable because of an intermediate node failure or link failure, the traffic is
switched to the bypass LSP.
In terms of principle, MPLS TE FRR can enable fast switchover to respond to link failures and
node failures between two PEs that serve as the start node and end node of a TE tunnel
respectively.
Nevertheless, MPLS TE FRR cannot deal with the failure of PEs that serves as the start node
and end node on a TE tunnel. When a PE fails, the traffic can resume by end-to-end route
convergence and LSP convergence. The time of convergence relates closely to the number of
routes of the MPLS VPN and the number of hops of the bearer network. Generally, the
convergence takes about 5s in typical networking, longer than 1s that is required for the end-to-
end traffic convergence when a node fails.
VPN FRR
Based on the VPN fast route switching technology, VPN FRR sets a switchover forwarding
entry that is destined for the primary PE and backup PE on a remote PE. With VPN FRR and
the technology of fast sense of PE failures, on an MPLS VPN where Costumer Edge (CE) devices
are dual-homed to PEs, the time of end-to-end service convergence is shortened and the time of
PE failure recovery cannot be affected by the number of private network routes. When a PE
node fails, the convergence of end-to-end service takes less than 1s.
On a PE device configured with VPN FRR, proper VPNv4 routes are selected by the matching
policy. For these routes, in addition to the routing information sent by the preferential next hop
(including forwarding prefix, inner tag, and selected outer LSP tunnel), information about the
inferior priority next hop (including forwarding prefix, inner tag, and selected outer LSP tunnel)
are also contained in the forwarded entry.
When preferential next hop node fails, through BFD and MPLS OAM, the PE detects that the
outer tunnel connecting the PE to the preferential node is unavailable. The PE sets a
corresponding flag in the LSP tunnel status table to indicates the outer LSP is unavailable and
delivers the flag to the forwarding engine. When the forwarding engine selects a forwarding
entry, it checks the LSP tunnel status corresponding to this forwarding entry. If the LSP tunnel
is unavailable, the engine uses the route of a inferior priority carried in this forwarding entry to
forward packets.

1.3.2 OAM (Operation Administration & Maintenance)

The OAM technology can simplify the network operation and test the network performance at
any time, which helps you to cut the network operation cost. This section describes only the
MPLS OAM technology.
MPLS is a key bearer technology applied to the extendable next generation network (NGN),
supporting multiple services guaranted by QoS. A unique network layer is introduced to MPLS
and this layer may lead to faults. Therefore, MPLS must be competent with OAM.
MPLS supports different Layer 2 and Layer 3 protocols, such as IP, FR, ATM, and Ethernet.
MPLS offers an OAM mechanism entirely independent from upper and lower layers, enabling
the following features on the MPLS user plane:
l Detecting the TE LSP connectivity
l Performing switchover when a link fails to provide services according to Service Level
Agreements (SLAs)
With the MPLS OAM mechanism, the router can detect, identify, and locate a fault of MPLS
layer effectively. Then, the fault is reported and processed. In addition, when a failure occurs,
the protection switching mechanism can be triggered.
1.3.3 VRRP (Virtual Router Redundancy Protocol)

VRRP groups multiple routers into one virtual router, and sets the address of the default gateway
as the IPv6 address of the virtual router.
Generally, all hosts of a LAN are configured with the same default route to the gateway, for
example, Router A in Figure 1-1. In this manner, the hosts can communicate with external
networks. When the gateway fails, the communication between hosts and external networks is
interrupted.
Figure 1-1 LAN default gateway

Ethernet
IP Address:10.0.0.2/24
Gateway:10.0.0.1 RouterA
10.0.0.1/24
Gateway:10.0.0.1 Network
Gateway:10.0.0.1
The common method to improve the system reliability is to deploy multiple egress gateways.
In addition, the problem of selecting routes among these gateways should be solved. The Virtual
Router Redundancy Protocol (VRRP) is a fault-tolerant protocol defined in RFC 3768. VRRP
solves the problem of route selection among egress gateways by separating the physical devices
from logical devices.

On Ethernet enabled with multicast or broadcast, VRRP offers logical gateways to ensure highly
available link. This solves the problem that services are interrupted because of a gateway
router failure, without changing the configuration of routing protocol.
1.3.4 BFD (Bidirectional Forwarding Detection)

As a unified detection mechanism on an entire network, BFD can fast detect network faults,
minimize the impact of device faults on services, and improve availability of a network.
BFD is a set of entire-network applicable detection mechanisms. It is used to detect and monitor
the connectivity of a link or an IP route during forwarding packets. To improve the network
performance, a communication failure between adjacent systems must be detected quickly and
the standby channel must be created faster for communication recovery.
The BFD features are as follows:
l Detecting channel failures between adjacent forwarding engines with light load in a short
time
l Detecting any media and any protocol layer with single mechanism in real time and
supporting different detection time and costs
1.4 Networking of Reliability over an IP Network

This section describes FRR applicable scenarios and FRR solutions.
1.4.1 Failures on Intermediate Nodes or on the Link Between PEs -

LDP FRR/TE FRR
In LDP or TE FRR, when transmission devices exist between P devices, BFD or OAM can be
used to detect links that transmit traffic.
Figure 1-2 Networking diagram of LDP/TE FRR application
PE1 P1 P2 P3 PE3
PE2 PE4
As shown in Figure 1-2, LDP LSP serves as a public network tunnel and TE is enabled with
QoS between P devices. This network deployment enhances the QoS across the entire network

and simplifies the TE deployment in changing PE devices. Without transmission devices, if a

failure occurs on the link between P1 and P2, or P2 fails on a non-broadcast network, the LDP
FRR performs switching on PE1 and ensures that the switching takes no more than 50 ms.
The premise of preceding application is that no transmission device exists, since the switching
performed by the TE FRR/LDP FRR depends on the detection of the interface status through
signals or optical signals. If transmission devices exist and a link fails, the router cannot detect
the interrupt of optical signals, and the switching cannot be performed. Then, another mechanism
is required to detect the link between transmission devices, namely, BFD or OAM.
1.4.2 Link Failure During Transmission

BFD or OAM can detect the links between both ends of a session and VRRP can implement fast
link switching.
OAM
The OAM is a unidirectional detection mechanism. Bidirectional OAM can be configured for
bidirectional protection. The detection end of OAM sends a packet to detect the link. If the link
works normally, the other end can receive the detection packet timely.
If the receiver cannot receive the detection packet within a specified period, a link-interrupt
packet is sent through a reverse path to report the link failure to the detection end. Then, the
detection end responds to the failure with a series of actions, one of which is the switchover of
the OAM protection group.
In an OAM protection group, a primary tunnel and a bypass tunnel are created to form a
protection group. When one tunnel of the protection group is available, the primary tunnel is
available logically. Normally, a packet is forwarded through the primary tunnel, that is, the
working tunnel. When the primary tunnel is Down and the bypass tunnel is available, the tunnel
is iterated to the primary tunnel logically. In fact, the bypass tunnel, also named protection tunnel,
works.
With fast detection performed by the OAM, the protection group is listed in the forwarding table
with its primary tunnel entry and bypass tunnel entry. This enables fast switchover after a failure
is detected, providing high reliability for network connectivity.

Figure 1-3 Networking diagram of MPLS OAM protecting switchover

P1
PE1 P2 PE2
MPLS TE
Tunnel
P3
As shown in Figure 1-3, two TE tunnels are created between the ingress PE1 and egress PE2,
forming a protection group. A TE tunnel is created between PE2 and PE1 through P1 as a reverse
channel, advertising a failure to ingress PE1.
BFD
BFD and OAM are similar because both of them define a set of mechanisms including detection,
failure report, and switchover. For BFD and OAM, the detection is carried out by sending fast
detection packets through a preset path to detect the link status. If the detection packets cannot
pass through the link, the packets are dropped. To avoid the jitters, the number of detection
packets is specified. When the number of the lost detection packets reaches the set value, the
link is considered as interrupted.
BFD is a bidirectional detection mechanism, and its detection packets are sent bidirectionally.
If one end does not receive the detection packets within a specified period, the end assumes that
the link is interrupted and reports to related modules to perform switchover.

Figure 1-4 Networking diagram of BFD for VRRP

Switch1 PE1
BFD for VRRP VRRP Backbone
Switch2 PE2
As shown in Figure 1-4, PE1 and PE2 form a VRRP master and backup group, serving as the
backup for each other. The VRRP backup group monitors BFD session. For example, when PE1
serves as the primary PE and the link between Switch1 and PE1 fails, the failure is fast detected
through BFD and reported to VRRP. The VRRP master and backup group performs switchover
fast and then PE2 becomes the primary PE.
1.4.3 Failure on the Remote PE - VPN FRR

In VPN FRR, BFD can detect connectivity faults between PEs.
Figure 1-5 Networking diagram of VPN FRR application
PE1 P1 P2 P3 PE3
PE2 P4 P5 P6 PE4
As shown in Figure 1-5, PE3 and PE4 access the VPN. If the user network on the left of PE1
needs to communicate with the user network on the right of PE3, PE1 can access the user network
on the right through PE3 and PE4. In this case, PE3 and PE4 serve as the backup for each other,
through which PE1 sends packets. This is how VPN FRR works.
Similar to other FRR technologies, in the VPN FRR, an available bypass path is reserved for
fast switchover before the primary path fails. For VPN FRR, two next hops (PEs) are reserved

for the local device to access the private network. One is the active PE and the other is the standby
PE. The active and standby PEs are configured manually.
As shown in Figure 1-5, PE1 reserves two next hops, that is, PE3 and PE4, to access the remote
VPN. PE1 can select either of them as the active next hop and the standby next hop.
l Without the VPN FRR, only an active next hop entry is delivered from the control plane
to the forwarding plane. When the active next hop becomes invalid, the standby next hop
entry is delivered to the forwarding plane. As a result, the switchover is slow.
l After the configuration of VPN FRR, both next hop entries are delivered from the control
plane to the forwarding plane. When the active next hop becomes invalid, the standby next
hop can be applied quickly to the forwarding plane. The switchover speeds up.
After BFD detects that the PE of the active next hop fails, switchover is performed within a very
short period, which ensures high reliability.
1.4.4 Failure of Downlink Interface on the PE - IP FRR

In IP FRR, when a primary path between a CE and a PE fails, traffic can be switched to a backup
path.
Figure 1-6 Networking diagram of IP FRR application
PE1
MPLS-VPN
Backbone
CE
PE2
As shown in Figure 1-6, the traffic to the CE is forwarded by PE1 (the active PE). If the link
between PE1 and the CE fails, IP FRR switches the traffic from the link between PE1 and the
CE to the link between PE2 to the CE.
The principle of FRR is to retain a bypass path on the forwarding plane for fast switchover.
Similarly, with IP FRR, two paths exist between PE1 and CE. For one path, packets are
transmitted through direct route. For the other path, packets are transmitted from PE1 to PE2
and then forwarded to CE.
Generally, PE accesses the Layer 3 Virtual Private Network (L3VPN). IP FRR is applied to a
private network. Then, the private network neighbor relationship between PE1 and PE2 needs
to be created, and the primary and bypass paths are created for PE1 accessing CE.

Configuration Guide - Reliability 2 Interface Backup Configuration
2 Interface Backup Configuration
About This Chapter
After a standby interface is configured for the active interface, the standby interface can take
over traffic when the active interface fails.
2.1 Introduction of Interface Backup

In the interface backup mechanism, interfaces are classified into the active interface and standby
interface. The interfaces work in active/standby mode or load balancing mode.
2.2 Configuring the Active/Standby Interface Backup
Interface backup in active/standby mode means that in normal situation, the active interface
transmits all services, while the standby interface does not transmit services.
2.3 Configuring the Load Balancing Interface Backup
Interface backup in load balancing mode means that traffic is balanced between the active
interface and the standby interface.
2.4 Maintaining the Interface Backup
This section describes how to maintain the interface backup function.
2.5 Configuration Examples
Interface backup is performed in active/standby mode or load balancing mode. Familiarize
yourself with the configuration procedures against the networking diagram. Each configuration
example consists of the networking requirements, configuration roadmap, configuration
procedures, and configuration files.

2.1 Introduction of Interface Backup

In the interface backup mechanism, interfaces are classified into the active interface and standby
interface. The interfaces work in active/standby mode or load balancing mode.
2.1.1 Interface Backup Overview

Interface backup refers to the backup relationship between interfaces on the same device. When
an interface fails, traffic can be quickly switched to its standby interface.
The router plays an important role in the network. When an interface on a router fails, a key
method to ensure the security and smooth functioning of the service is to rapidly switch the
service on the interface to other normal interfaces.
Interface backup means that interfaces on a router serve as the backup for each other. Usually,
a single interface undertakes services while the other interfaces are in the backup state.
Figure 2-1 shows the interface backup.
Figure 2-1 Interface backups
if1
if2 if4
LAN
if3
Interfaces if1, if2, and if3 are backed up for each other. For example, if2 transmits services. if1
and if3 are in the backup state and have their respective backup priorities.
The router traces the status of each interface. When if2 fails, the router enables the standby
interface with a higher priority to replace if2. This ensures smooth and reliable transmission of
services.
The interface backup mechanism divides interfaces into the active interface and the standby
interface according to their roles in the service transmission process.
NOTE
POS and ATM interfaces cannot be configured on the X1 and X2 models of the NE80E/40E.
Active Interface
The active interface undertakes service transmission and is backed up by other interfaces, such
as if2 in Figure 2-1.
Any physical interface or sub-interface like POS ,Ethernet or ATM interface serves as an active
interface on a router. An active interface with larger bandwidth provides a higher transmission
rate.

Standby Interface
The standby interface does not transmit services and is often in the standby mode. The standby
interface backs up the active interface, such as if1 and if3 in Figure 2-1.
Any physical interface (POS , AUX Ethernet or ATM interface for example) on a router serves
as a standby interface.
NOTE
l An active interface is backed up by several standby interfaces. When the active interface fails, the
standby interface with the highest priority takes over services from the active interface.
l The same standby interface backs up only one active interface.
l ISDN BRI/PRI interfaces that have multiple physical channels provide backup for multiple active
interfaces through the Dialer route in the Dial Control Center (DCC) configuration.
2.1.2 Characteristics of the Interface Backup Supported by the

NE80E/40E
Interface backup can be performed in active/standby mode or load balancing mode.
Active/Standby Mode
Figure 2-2 shows that if2 serves as the active interface.
Figure 2-2 Active/standby mode
if1
100% if2 if4
LAN
if3
In the active/standby mode, only one interface transmits services transmission all the time.
l When the active interface works normally, all traffic flows pass through the active interface;
the standby interfaces like if1 and if3 remain in the standby mode even if the active interface
is overloaded.
l The standby interface with the highest priority takes over the work of the active interface
and transmits all traffic flows only when the active interface fails.
l When the failed active interface is restored, it transmits traffic again.
Load-Balancing Mode
In the load-balancing mode, the interfaces share the flow.
l When the data flow of the active interface reaches the specified upper limit, the router
automatically enables an available standby interface with the highest priority. Both
interfaces undertake the transmission together and share the load.

l When the flows of these two interfaces reach the highest threshold again, the router enables
another available interface with the second highest priority for balancing the load among
these interfaces, and so on.
l When the data flow of the active interface reaches the pre-defined lower limit, the router
disables the standby interface with the lowest priority that is taking part in load balancing
until the active interface can undertake the flow on its own.
Figure 2-3 Load-balancing mode
A%
if1
B% if2 if4
LAN
C%
if3
A%+B%+C%=100%
NOTE
The working mode is selected depending on configuration of the percentage threshold of load balancing
by the users. If the percentage threshold is configured, the router uses the load-balancing mode.
Alternatively, the router uses the active/standby mode.
2.2 Configuring the Active/Standby Interface Backup

Interface backup in active/standby mode means that in normal situation, the active interface
transmits all services, while the standby interface does not transmit services.
2.2.1 Establishing the Configuration Task

Before configuring interface backup in active/standby mode, 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
The interface backup can be configured for multiple devices to improve their reliability through
standby interfaces.
In the active/standby mode, the active interface undertakes all the services, whereas the standby
interfaces are in the standby state and do not undertake services.
Switchover delay is an important parameter in the active/standby mode. An appropriate delay

not only ensures timely switchover but also prevents frequent switching.
Pre-configuration Tasks
Before configuring the active/standby interface backup, complete the following tasks:
l Configuring physical parameters for interfaces

l Configuring link layer attributes for interfaces

l Configuring IP addresses for interfaces

l Configuring a static route to the destination network segment through the active/standby
interface
NOTE
Configure these parameters on the active interface and standby interfaces. To efficiently use IP addresses,
you can borrow the address of the active interface for the standby interface.
Data Preparation
To configure the active/standby interface backup, you need the following data.
No Data
1 Standby interfaces that serve as backup for the active interface
2 Priorities of standby interfaces
3 Delay time of the active/standby switchover
2.2.2 Configuring a Standby Interface

After a standby interface is configured for the active interface, the standby interface can take
over network traffic when the active interface fails.
Context
Do as follows on the router that needs to be configured with the active/standby interface backup:
Procedure
Step 1 Run:
system-view
The system view is displayed.

Step 2 Run:
interface interface-type interface-number
The interface view is displayed.

Step 3 Run:
standby interface interface-type interface-number [ priority ]
A standby interface and its priority are configured.
NOTE
l If multiple standby interfaces need to be configured for a main interface, run the standby interface
command for several times to configure all the standby interfaces.
l A main interface can be configured with a maximum of three standby interfaces. In addition, a standby
interface can be configured only for one main interface.
l A maximum of 10 main interfaces can exist at the same time.
----End

2.2.3 Configuring the Active/Standby Switchover Delay

By configuring the switchover delay time, you can prevent the frequent switchover between the
active interface and the standby interface due to the unstable interface status.
Context
To avoid frequent interface switching due to unstable interface status, the system does not switch
traffic from the active interface to the standby interface until a pre-set delay after the active
interface changes from Up to Down.
l If the active interface is still in the Down state when the delay period expires, the system
switches traffic from the active interface to the standby interface.
l If the active interface restores within the delay, switching does not occur.
Do as follows on the router that needs to be configured with the active/standby interface backup:
Procedure
Step 1 Run:
system-view
Step 2 Run:
The active interface view is displayed.
Step 3 Run:
standby timer delay enable-delay disable-delay
The switchover delay for the active/standby interfaces is configured.
When enable-delay and disable-delay are set to 0, the switching is performed immediately.
----End
2.2.4 Checking the Configuration

By viewing the status of the active and standby interfaces, you can check whether the
configurations are successful.
Prerequisite
The configurations of the active/standby interface backup function are complete.
Procedure
Step 1 Run the display standby state command to check the status of the active or the standby interface.
----End

Example
Running the display standby state command, you can view information about the status of the
active and standby interfaces as follows:
<HUAWEI> display standby state
Interface Interfacestate Backupstate Backupflag Pri Loadstate
GigabitEthernet3/0/0 UP MUP MU
GigabitEthernet3/0/0 STANDBY STANDBY BU 20
Backup-flag meaning:
M---MAIN B---BACKUP V---MOVED U---USED
D---LOAD P---PULLED G---LOGICCHANNEL
As shown in the command output, GE 3/0/0 serves as an active interface and is in the Up state.
GE 3/0/4 serves as a standby interface and is in the Standby state and its priority is 20.
2.3 Configuring the Load Balancing Interface Backup

Interface backup in load balancing mode means that traffic is balanced between the active
interface and the standby interface.

Before configuring interface backup in load balancing mode, familiarize yourself with the
The interface backup can be configured for multiple devices to improve their reliability through
standby interfaces.
In the load-balancing mode, if the flows on the active interface exceed the threshold, the
router automatically enables an available standby interface to undertake the transmission.
Two important parameters in the load-balancing mode are:
l Percentage threshold of load balancing

l Bandwidth of the active interface
The two parameters affect the service throughput on each interface. Meanwhile, the bandwidth
of the active interface is preferentially used.
Before configuring the load balancing interface backup, you need to complete the following
tasks:

l Configuring IP addresses for interfaces
l Configuring static routes to the destination network segment on the active interface and
standby interfaces

NOTE
The preceding parameters are required on both the active interface and the standby interfaces. To efficiently
use IP addresses, you can the address of the active interface for the standby interfaces .
Data Preparation
To configure the load balancing interface backup, you need the following data.
No Data
1 Standby interface and its priority
2 Percentage thresholds for enabling and disabling load balancing
3 Bandwidth of the active interface
4 Interval for checking the traffic on the active interface
2.3.2 Configuring a Standby Interface

After a standby interface is configured for the active interface, the standby interface and the
active interface can transmit traffic together.
Context
Do as follows on the router that needs to be configured with the load balancing interface backup:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
standby interface interface-type interface-number [ priority ]
A standby interface and its priority are configured.
NOTE
l You can use the standby interface command repeatedly to configure multiple standby interfaces for
an active interface.
l An active interface can be backed up by a maximum of three standby interfaces. One standby interface
can back up only one active interface.
l The NE80E/40E supports up to 10 active interfaces simultaneously.
----End

2.3.3 Configuring the Percentage Thresholds for Load Balancing

A percentage of traffic can be set for a standby interface so that the standby interface transmits
network traffic.
Context
Do as follows on the router that needs to be configured with the load balancing interface backup:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
standby threshold enable-threshold disable-threshold
The percentage threshold for load balancing is set.

By default, the system does not support the load-balancing mode, that is, no threshold percentage
is configured.
When the flow of the active interface reaches the pre-defined upper limit (enable-threshold),
the router automatically enables an available standby interface with the highest priority. This
standby interface undertakes the service transmission with the active interface.
When the flow of the active interface is less than the pre-defined lower limit (disable-
threshold), the router disables a standby interface with the lowest priority that transmits services
in load balancing mode.
----End
2.3.4 (Optional) Configuring the Bandwidth and Flow Check

Interval for the Active Interface
You can set the bandwidth of the active interface and the interval for detecting traffic as required.
Context
Do as follows on the router that needs to be configured the load balancing interface backup:
Procedure
Step 1 Run:
system-view

Step 2 Run:


Step 3 Run:
standby bandwidth size
The maximum bandwidth of the active interface is configured.

By default, on the active interface, its actual physical bandwidth is adopted as its maximum
available bandwidth.
Step 4 Run:
standby timer flow-check time
The flow check interval for the active interface is configured.

By default, the flow check interval is set to 30 seconds.
----End

By viewing the status of the active and standby interfaces or traffic statistics, you can check
whether the configurations are successful.
Prerequisite
The configurations of the load balancing interface backup function are complete.
Procedure
l Run the display standby flow command to check the flow statistics of the active interface
working in load-balancing mode.
l Run the display standby state command to check the status of the active and standby
interfaces.
----End
Example
After the configuration, you can run the display standby flow command to check the flow
statistics of the active interface working in load-balancing mode.
<HUAWEI> display standby state
GigabitEthernet 2/0/0 UP MUP MUD
GigabitEthernet 1/0/0 UP UP BU 40
GigabitEthernet 1/0/0 STANDBY STANDBY BU 20
After the configuration, you can run the display standby state command to check the status of
the active and standby interfaces.
<HUAWEI> display standby flow
Interfacename : GigabitEthernet 2/0/0
Flow-interval(s) : 30
LastInOctets : 5298
LastOutOctets : 398807420

InFlow(Octets) : 1038
OutFlow(Octets) : 78717892
BandWidth(b/s) : 40000000
UsedBandWidth(b/s) : 20991432
2.4 Maintaining the Interface Backup

This section describes how to maintain the interface backup function.
2.4.1 Monitoring Working Status of the Interface Backup

By monitoring the operation status of the interface backup function, you can view information
about related interfaces during the interface backup process.
Context
In routine maintenance, you can select to run the following commands in any view to view the
working status of the interface backup.
Procedure
l Run the display standby state command in any view to check the configuration and status
of the interface backups.
l Run the display standby flow command in any view to check statistics of the traffic on
the active interface in load balancing.
----End

Interface backup is performed in active/standby mode or load balancing mode. Familiarize
yourself with the configuration procedures against the networking diagram. Each configuration
example consists of the networking requirements, configuration roadmap, configuration
Context
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.
2.5.1 Example for Configuring the Active/Standby Mode of

Multiple Interfaces
In this example, by configuring the active/standby interface backup function, you can use the
standby interface to take over network traffic when the active interface fails.
Networking Requirements
NOTE
POS interfaces cannot be configured on the X1 and X2 models of the NE80E/40E.

As shown in Figure 2-4, Router A is connected to Router B.
The active/standby backup relationship exists between multiple interfaces on Router B:
l POS 2/0/0 serves as the active interface.

l POS 1/0/0 and POS 3/0/0 serve as standby interfaces of POS 2/0/0.
l POS 1/0/0 takes a higher priority than that of POS 3/0/0.
Figure 2-4 Networking diagram of configuring the active/standby interface backup

POS1/0/0 POS1/0/0
10.1.1.1/24 10.1.1.2/24
POS2/0/0 POS2/0/0
10.1.2.1/24 10.1.2.2/24
RouterA RouterB
GE3/1/0 GE3/1/0
POS3/0/0 POS3/0/0
10.10.1.2/24 10.1.3.1/24 10.1.3.2/24 10.20.1.2/24
HostA HostB
10.10.1.1/24 10.20.1.1/24
Configuration Roadmap
The configuration roadmap is as follows:
1. Configure POS 2/0/0 on Router B as the active interface to bear all the services.
2. Configure POS 1/0/0 and POS 3/0/0 in the interface view of POS 2/0/0 as the standby
interfaces without any service. POS 1/0/0 has a higher priority.
Data Preparation
To complete the configuration, you need to configure the priority of the standby interface.
Procedure
Step 1 Configure the network layer attributes.
# Configure IP addresses for routers as shown in Figure 2-4.
The configuration details are omitted here.
# Configure a static route to Host B network segment on Router A.

<RouterA> system-view
[RouterA] ip route-static 10.20.1.0 255.255.255.0 pos1/0/0
# Configure a static route to Host A network segment on Router B.

<RouterB> system-view
[RouterB] ip route-static 10.10.1.0 255.255.255.0 pos1/0/0
# Configure Host A and Host B to use Router A and Router B as their gateways respectively.
After the configuration, Host A and Host B can ping through each other.
Step 2 Configure the interface backup on Router B.
# Configure POS 2/0/0 as the active interface and POS 1/0/0 and POS 3/0/0 as the standby
interfaces. POS 1/0/0 has a higher priority. Immediate switching is adopted.
[RouterB] interface pos 2/0/0
[RouterB-Pos2/0/0] standby interface pos1/0/0 40
[RouterB-Pos2/0/0] quit
After the configuration, display the state of the active/standby interfaces, and you can find that
POS2/0/0 is UP, and POS 1/0/0 and POS 3/0/0 are STANDBY.
[RouterB] display standby state
Pos 2/0/0 UP MUP MU
Pos 1/0/0 STANDBY STANDBY BU 40
After the Tracert test of Host B address on Host A, you can view the packets reaches the
destination through the link layer of POS 2/0/0 on Router B.
C:\> tracert 10.20.1.1
traceroute to 10.20.1.1 (10.20.1.1), max hops: 30, packet length: 40, press CTRL_C
to break
1 60 ms 60 ms 50 ms 10.10.1.2
2 50 ms 40 ms 70 ms 10.1.2.2
3 70 ms 70 ms 60 ms 10.20.1.1
Trace complete.
Step 3 Verify the configuration.

# Run the shutdown command on POS 2/0/0 on Router B to simulate a fault.
[RouterB-Pos2/0/0] shutdown
# Display the state of the active and standby interfaces again, and you can find that POS 1/0/0
becomes UP and POS 3/0/0 is still STANDBY.
[RouterB] display standby state
Pos 2/0/0 DOWN MDOWN MU
Pos 1/0/0 UP UP BU 40
After the Tracert test of Host B address on Host A, you can display the packets reaching the
destination through POS 1/0/0 of the link layer on Router B.
C:\> tracert 10.20.1.1

traceroute to 10.20.1.1 (10.20.1.1), max hops: 30, packet length: 40, press CTRL_C
to break
1 60 ms 60 ms 50 ms 10.10.1.2
2 50 ms 40 ms 70 ms 10.1.1.2
3 70 ms 70 ms 60 ms 10.20.1.1
Trace complete.
----End
Configuration Files
l Configuration file of Router A
#
sysname RouterA
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.1.2.1 255.255.255.0
#
interface Pos3/0/0
link-protocol ppp
undo shutdown
ip address 10.1.3.1 255.255.255.0
#
interface GigabitEthernet4/0/0
undo shutdown
ip address 10.10.1.2 255.255.255.0
#
ip route-static 10.20.1.0 255.255.255.0 Pos1/0/0
#
return
l Configuration file of Router B

#
sysname RouterB
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.1.2.2 255.255.255.0
standby interface Pos1/0/0 40
#
interface Pos3/0/0
link-protocol ppp
undo shutdown
ip address 10.1.3.2 255.255.255.0
#
undo shutdown
ip address 10.20.1.2 255.255.255.0
#

#
return
2.5.2 Example for Configuring Load Balancing on Multiple Standby

Interfaces
In this example, by configuring the load balancing interface backup function, you can use the
active interface and standby interface together to transmit network traffic.
NOTE
As shown in Figure 2-5, Router A is connected to Router B.
The load balancing backup relationship exists among multiple interfaces on Router B. POS 2/0/0
serves as the active interface, and POS 1/0/0 and POS 3/0/0 serve as the load balancing interfaces
of POS 2/0/0.
The maximum transmission bandwidth of the active interface is configured to be 40 Mbit/s.

When the traffic of the active interface reaches 50% of the threshold, the interface POS 1/0/0 is
enabled for load balancing. Standby interfaces with low priority are disabled when the traffic of
the active interface is less than 30% of the threshold.
Figure 2-5 Networking diagram of Configuring Load Balancing interface backup

POS1/0/0 POS1/0/0
10.1.1.1/24 10.1.1.2/24
POS2/0/0 POS2/0/0
10.1.2.1/24 10.1.2.2/24
RouterA RouterB
GE3/1/0 GE3/1/0
POS3/0/0 POS3/0/0
10.10.1.2/24 10.1.3.1/24 10.1.3.2/24 10.20.1.2/24
HostA HostB
10.10.1.1/24 10.20.1.1/24
1. Configure POS 2/0/0 on Router B as the active interface.

2. Configure POS 1/0/0 and POS 3/0/0 in the interface view of POS 2/0/0 as the standby
interfaces. POS 1/0/0 has a higher priority.
3. Configure the threshold of the load balancing percentage and the active interface
bandwidth.

Data Preparation
To complete the configuration, you need the following data:
l The priority of the standby interface
l The threshold of the load balancing percentage and the active interface bandwidth
Procedure
Step 1 Configure the network layer attributes.
# Configure IP addresses of all interfaces as shown in Figure 2-5.
The configuration details are not mentioned here.
# Configure a static route to Host B network segment on Router A.
[RouterA] ip route-static 10.20.1.0 255.255.255.0 Pos3/0/0
# Configure a static route to Host A network segment on Router B.

# Configure Host A and Host B to use Router A and Router B as their gateways respectively.
After the configuration, Host A and Host B can Ping through each other.
Step 2 Configure the interface backup on Router B.
# Configure POS 2/0/0 as the active interface and POS 1/0/0 and POS 3/0/0 as the standby
interfaces with the priorities of 40 and 20 respectively.
# Configure the percentage threshold of load balancing and the bandwidth of the active interface.
[RouterB-Pos2/0/0] standby bandwidth 40000
[RouterB-Pos2/0/0] standby threshold 50 30

# Running the display standby state command on Router B, you can view information about
the status of active and standby interfaces. As shown in the command output, POS 2/0/0 is in
the Up state. POS 1/0/0 and POS 3/0/0 are in the Standby state. Also, you can run the display
standby flow command to view traffic changes on POS 2/0/0.
<RouterB> display standby state
Pos 2/0/0 UP MUP MU
<RouterB> display standby flow

Interfacename : Pos2/0/0
LastInOctets : 2494
# Router A sends great traffic to Host B, making the traffic on POS 2/0/0 exceeds 20 Mbit/s.
After 30 seconds, you can view the state of the active and standby interfaces on Router B again
and you can find that both POS 2/0/0 and POS 1/0/0 are Up.
<RouterB> display standby state
Pos 2/0/0 UP MUP MUD
Pos 1/0/0 UP UP BU 40
<RouterB> display standby flow
Interfacename : Pos2/0/0
LastInOctets : 5298
----End
Configuration Files
#
sysname RouterA
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.1.2.1 255.255.255.0
#
interface Pos3/0/0
link-protocol ppp
undo shutdown
ip address 10.1.3.1 255.255.255.0
#
undo shutdown
ip address 10.10.1.2 255.255.255.0
#
#
return

#
sysname RouterB
#

interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.1.2.2 255.255.255.0
standby threshold 50 30
standby bandwidth 40000
#
interface Pos3/0/0
link-protocol ppp
undo shutdown
ip address 10.1.3.2 255.255.255.0
#
undo shutdown
ip address 10.20.1.2 255.255.255.0
#
#
return

Configuration Guide - Reliability 3 APS Configuration
3 APS Configuration
About This Chapter
APS helps ensure nonstop communications by immediately switching services from a faulty
link to a functional link when an STM-N link in the SDH system fails.
3.1 APS Overview

The APS immediately switches services from a faulty link to a normal link by switching and
recovering linear multiplex sections.
3.2 Configuring Single-Device APS
Two devices that support APS can connect through two links. Link reliability can be improved
by configuring single-device APS.
3.3 Configuring E-APS
Inter-device APS switchback can be performed by configuring E-APS.
This section provides configuration examples of APS. Each configuration example consists of
the networking requirements, configuration precautions, configuration roadmap, configuration

3.1 APS Overview

The APS immediately switches services from a faulty link to a normal link by switching and
recovering linear multiplex sections.
3.1.1 APS Overview

The Automatic Protection Switching (APS) protocol uses the Multiplex Section Overhead
(MSOH) to transmit signals. APS works in either 1+1 or 1:N mode.
APS Principle
APS is an important feature of a Synchronous Digital Hierarchy (SDH) network. APS uses a
protect link to protect traffic on one or more working links. If a working link fails, services on
the working link automatically switches to the protect link, preventing user data loss and
improving network reliability.
Figure 3-1 shows an SDH network is a supporting network and allows the establishment of
large-scale data communications networks with high bandwidth. For example, data networks A
and B can communicate with each other by multiplexing services to SDH payloads and
transmitting the payloads over fibers. An APS-enabled router can protect traffic on a link to an
Add/Drop Multiplex (ADM) or a Radio Network Controller (RNC) of an SDH network that has
APS functions. Two APS-enabled routers can also protect traffic on direct links between them.

Figure 3-1 Networking diagram of APS
RNC
APS
MPLS/SDH/Ethernet
Node B
Node B
Node B Node B Node B
APS uses K1 and K2 bytes in the MSOH to carry information. K1 transmits Changeover Order
(COO) signals for a traffic switchover; K2 transmits Changeover Acknowledgement (COA)
signals for a traffic switchback. For information about meanings of K1 and K2 bytes, see the
chapter "APS" in the HUAWEI NetEngine80E/40E Router Feature Description - Reliability.
APS Working Modes

l When data is transmitted properly, APS is performed in either 1+1 or 1:N (1:1 is used as
an example) mode:
– 1+1: Two links work together. The sender sends traffic on both the working and protect
links and the receiver receives traffic from only the working link. The 1+1 mode allows

rapid traffic switching and provides high reliability. However, this mode has a low
channel usage at about 50%.
– 1:1: Two links are set up and only one link works. If the working link works properly,
traffic flows only through the working link. The 1:1 mode allows a high channel usage
but has poorer reliability than the 1+1 mode.
l If a working link fails, APS automatically switches data from a working link to a protect
link, and continues to take effect on data in either of the following modes:
– Switchback: If the working link recovers, APS switches traffic back to the working link
after the Wait-to-Restore (WTR) timer expires, and allows the protect link to protect
other working links.
– Non-switchback: If the working link recovers, APS does not switches traffic back to
the working link unless the protect link fails or a switchover request is received. A non-
switchback mode is not supported when APS works in 1+1 mode.
l If a link fails, either of the following switchovers is performed:
– Unidirectional switchover: If a working link fails, the sender sends data along both
working and protect links, and the receiver receives data only from the protect link. This
mode is available only when APS works in 1+1 mode.
– Bidirectional switchover: If a working link fails, the sender sends data only along the
protect link. This mode is available when APS works in either 1:1 or 1+1 node.
l APS provides protection at four levels. The first three levels apply to single-chassis APS
and the fourth applies to E-APS. The four levels are as follows:
– Interface level: Both a working interface and a protect interface reside on a single sub-
card of a board.
– Sub-card level: A working interface and a protect interface reside on two sub-cards of
a single board.
– Board level: A working interface and a protect interface reside on different boards of a
single router.
– Device level: A working interface and a protect interface are configured on different
routers. A working router is configured with the working interface, and a protect
router is configured with a protect interface. The working and protect routers exchange
control information using the Protect Group Protocol (PGP) over an out-band
management channel.
3.1.2 APS Features Supported by the NE80E/40E

The device supports the following APS features: protection switchover modes, working
interfaces under protection, and switchback modes.
At present, the NE80E/40E supports the following APS features:
l 1+1 unidirectional mode, 1:1 bidirectional mode, 1+1 bidirectional mode.

l Manual switching of APS groups.
l Forcible switching of APS groups.
l Locking of APS groups.
l APS implementation on interfaces.
l APS implementation on the same SIC or inter-SIC APS.
l E-APS.

l Adding the working and protection interfaces of an APS group to a trunk.

l Configuring services on a trunk.
3.2 Configuring Single-Device APS

Two devices that support APS can connect through two links. Link reliability can be improved
by configuring single-device APS.

Before configuring single-device APS, 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.
APS needs to be configured when the router is connected to a Radio Network Controller (RNC).
Pre-configuration Task
Before configuring APS, complete the following tasks:
l Configure an interface on the router and ensure that the link layer protocol between the
router and the RNC is Up.
Data Preparation
To configure APS, you need the following data.
No. Data
1 ID of an APS group
2 IDs of the working and protection interfaces in an APS group
3 (Optional) WTR time set for an APS group
3.2.2 Configuring a Working Interface in an APS Group

A working interface must be specified before configuring APS.
Context
Do as follows on the router that requires APS:
Procedure
Step 1 Run:
system-view


Step 2 Run:
or
controller cpos cpos-number
NOTE
Only ATM interfaces, and CPOS interfaces on the LPUF-10 support APS.
ATM interfaces cannot be configured on the X1 and X2 models of the NE80E/40E.
Step 3 Run:
aps group group-id
An APS group is created and an interface is added to the APS group.

Step 4 Run:
aps working
The interface added to the APS group is specified as a working interface.
----End
3.2.3 Configuring a Protection Interface in an APS Group

The protection and working interfaces must be added to the same APS group.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
or
NOTE
Step 3 Run:
aps group group-id
An APS group is created and an interface is added to this APS group.

CAUTION
The working and protection interfaces must be added to the same APS group.
Step 4 Run:
aps protect
The interface added to the APS group is specified as a protection interface.
Step 5 (Optional) Run:

aps signal-low-priority
The low-priority signal failure code for a switching request carried in the K byte is specified on
the protect interface.
An APS protect interface uses the K type in an APS packet to negotiate with the APS protect
interface on the remote end. By default, the high-priority signal failure code for a switching
request is used. If the low-priority code is used on the APS protect interface on the remote end,
the high-priority code on the APS protect interface on the local end must be changed to the low-
priority code.
----End
3.2.4 (Optional) Configuring a Working Mode for an APS Group

The APS auto protection switchover mode can be configured only on a protect interface in an
APS group.
Context
Do as follows on a protect interface in an APS group:
Procedure
Step 1 Run:
system-view
Step 2 Run:
or
Step 3 Run:
aps mode { one2one bidirection | one-plus-one unidirection | one-plus-one
bidirection }
A working mode is configured for the APS group. The configuration of APS mode takes effect
after the shutdown and undo shutdown commands are used on the protect interface
l one2one bidirection:

– Configures APS to work in 1:1 mode. Only the working link transmits traffic. The protect
link only carries traffic when the working link is faulty.
– Configures APS to work in bidirectional mode. If an interface fails, both the sender and
the receiver switch their traffic to the protect link.
l one-plus-one unidirection:
– Configures APS to work in 1+1 mode. Both the working link and the protect link transmit
traffic.
– Configures APS to work in unidirectional mode. If an optical fiber to an interface fails,
only the receiver switches its traffic to the protect link.
l one-plus-one bidirection:
– Configures APS to work in 1+1 mode. If an interface fails, both the working link and the
protect link transmit traffic.
----End
3.2.5 (Optional) Configuring a Switching Mode for an APS Group
Context
Do as follows on a protection interface in an APS group:
Procedure
Step 1 Run:
system-view
Step 2 Run:
or
The protection interface view of the APS group is displayed.
Step 3 Run:
aps switch-command { lockout | force | manual }
A switching mode is configured for the APS group.
l lockout: Initiates a locked APS request in an APS group, that is, locks traffic on the working
link.
l force: Initiates a forced APS request in an APS group, that is, forcibly switches traffic to the
protection link.
l manual: Initiates a manual APS request in an APS group, that is, manually switches traffic
to the protection link.
----End

3.2.6 (Optional) Setting the WTR Time for an APS Group

The switchback waiting time, also called WTR time, can only be configured on a protection
interface in an APS group.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
or

Step 3 Run:
aps revert wtr-time
The WTR time is set for the APS group.

wtr-time: The value ranges from 1 to 12 minutes.
When setting the WTR time, note the following items:
l In 1:1 mode, after the fault is rectified and the WTR time (5 minutes) expires, traffic is
automatically switched back to the working link.
l In 1+1 mode, after the fault is rectified, traffic is not automatically switched back to the
working interface. The aps revert wtr-time command can be used to set a WRT time before
an APS group switchback is performed. After the fault is rectified, data services will swtich
to the working interface after the configured WRT time expires.
----End
3.2.7 Adding Members of an APS Group to a Trunk

The working interface and the protection interface must be added to the same trunk link.
Context
Do as follows separately on the working and s of an APS group.
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface atm-trunk interface-number
An ATM-Trunk interface is created and the view of the ATM-Trunk interface is displayed.
NOTE
APS can be configured on the ATM interfaces, and CPOS interfaces. The corresponding trunk interfaces
are ATM-Trunk , and CPOS-Trunk. Take the configuration on the ATM-Trunk as an example.
Step 3 Run:
quit

Step 4 Run:

Step 5 Run:
atm-trunk trunk-id
The interface is added to a trunk.
CAUTION
The working and protection interfaces of an APS group must be added to the trunk with the same
trunk ID.
----End

After a single-device APS is configured, the APS group's working mode, working interface,
WTR time, and interface status can be viewed.
Procedure
Step 1 Run the display aps group group-id command to view configurations of an APS group.
Step 2 Run the commands below to view configurations of trunk interfaces.

NOTE

l Run the display atm-trunk trunk-id command to view configurations of the ATM-Trunk
interfaces.
l Run the display cpos-trunk trunk-id command to view configurations of the CPOS-Trunk
interfaces.
----End
Example
<HUAWEI> display aps group 1

APS Group 1: Atm1/0/1 working channel 1(Active)

Atm1/0/2 protection channel 0(Inactive)
Unidirectional, 1+1 mode, Revert time(10 minutes)
No Request on Both Working and Protection Side
------------------------------------------------------------------------
Group Work-Channel Protect-Channel Wtr W-State P-State Switch-Cmd Switch-
Result
------------------------------------------------------------------------
1 Atm1/0/1 Atm1/0/2 10 ok ok NA idle
------------------------------------------------------------------------
total entry: 1
<HUAWEI> display atm-trunk 1
Interface Atm-Trunk1's state information is:
Operate status: up Number Of Up Port In Trunk: 2
--------------------------------------------------------------------------------
PortName Status Active Status
Atm1/0/1 Up Active
Atm1/0/2 Up Inactive
Display configurations of CPOS-Trunk interfaces.

<HUAWEI> display cpos-trunk 1
Interface Cpos-Trunk1's state information is:,
--------------------------------------------------------------------------------
Cpos1/0/1 Up Active
Cpos1/0/2 Up Inactive
3.3 Configuring E-APS

Inter-device APS switchback can be performed by configuring E-APS.

Before configuring E-APS, 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.
E-APS can be configured when the router is connected to an RNC that is dual homed to the
router.
Pre-configuration Task
Before configuring E-APS, complete the following tasks:
l Configuring an interface on the router and ensuring that the link layer protocol between the
router and the RNC is Up
Data Preparation
To configure E-APS, you need the following data.
No. Data
1 ID of an APS group

No. Data
2 IDs of the working and protection interfaces in an APS group
3 (Optional) WTR time set for an APS group
4 (Optional) Authentication string configured for the PGP message
5 (Optional) Interval for sending APS negotiation messages between the working and
protection interfaces
6 (Optional) Hold time of an APS connection
3.3.2 Configuring a Working Interface in an APS Group

A working interface must be specified before configuring APS.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
or
NOTE
Step 3 Run:
aps group group-id
Step 4 Run:
aps working peer-ip local-ip
The interface added to the APS group is specified as a working interface.
l peer-ip: Indicates the IP address of the Router where the working interfaces that are in the
same APS group as the protect group is located. Usually, the value is the IP address of the
loopback interface on the Router.

l local-ip: Indicates the IP address of the local router . Usually, the value is the IP address of
the loopback interface on the router.
----End
3.3.3 Configuring a Protection Interface in an APS Group

The protection and working interfaces must be added to the same APS group.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
or
NOTE
Step 3 Run:
aps group group-id
CAUTION
The working and protection interfaces must be added to the same APS group.
Step 4 Run:
aps protect peer-ip local-ip
The interface added to the APS group is specified as a protection interface.

l peer-ip: Indicates the IP address of the Router where the working interfaces that are in the
same APS group as the protect group is located. Usually, the value is the IP address of the
loopback interface on the Router.
l local-ip: Indicates the IP address of the local router . Usually, the value is the IP address of
the loopback interface on the router.
aps signal-low-priority

The low-priority signal failure code for a switching request carried in the K byte is specified on
the protect interface.
An APS protect interface uses the K type in an APS packet to negotiate with the APS protect
interface on the remote end. By default, the high-priority signal failure code for a switching
request is used. If the low-priority code is used on the APS protect interface on the remote end,
the high-priority code on the APS protect interface on the local end must be changed to the low-
priority code.
----End
3.3.4 Configuring a Working Mode for an APS Group

The APS auto protection switchover mode can be configured only on a protect interface in an
APS group.
Context
Do as follows on a protect interface in an APS group:
Procedure
Step 1 Run:
system-view
Step 2 Run:
or
The protect interface view of the APS group is displayed.
Step 3 Run:
aps mode { one2one bidirection | one-plus-one { bidirection | unidirection } }
A working mode is configured for the APS group.
This configuration take effect after shutdown and undo shutdown the protect interface.
l one2one bidirection:
– Configures APS to work in 1:1 mode. Only the working link transmits traffic. The protect
link only carries when the working link is faulty.
l one-plus-one unidirection:
traffic.
– Configures APS to work in unidirectional mode. If an optical fiber to an interface fails,
only the receiver switches its traffic to the protect link.
l one-plus-one bidirection:

traffic.
NOTE
one-plus-one bidirection is not supported by the X1 or X2 models of the NE80E/40E.

NOTE
The E-APS 1+1 unidirectional mode is not supported.
----End
3.3.5 (Optional) Configuring a Switching Mode for an APS Group
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
or
Step 3 Run:
aps switch-command { lockout | force | manual }
A switching mode is configured for the APS group.
l lockout: Initiates a locked APS request in an APS group, that is, locks traffic on the working
link.
l force: Initiates a forced APS request in an APS group, that is, forcibly switches traffic to the
protection link.
l manual: Initiates a manual APS request in an APS group, that is, manually switches traffic
to the protection link.
----End
3.3.6 (Optional) Setting the Interval for Sending APS Negotiation

Messages and the Hold Time of an APS Connection
A holding time of at least 10s for the connection status of the APS working and protection
interfaces is recommended.

Context
Do as follows on both working and protection interfaces of an APS group:
Procedure
Step 1 Run:
system-view
Step 2 Run:
or
The working or the protection interface view is displayed.
Step 3 Run:
aps timers keep-alive-time hold-time
The interval for sending APS negotiation messages and the hold time of the APS connection
between the working and protection interfaces are set.
l keep-alive-time: Indicates the interval for sending APS negotiation messages from the local
end. The value is an integer ranging from 1 to 60, in seconds.
l hold-time: Indicates the hold time of the APS connection. The value is an integer ranging
from 3 to 300, in seconds. The hold time of the APS connection must be equal to or greater
than three times the interval for sending APS negotiation messages.
NOTE
hold-time whose values range from 1 to 300 can be set on the X1 or X2 models of the NE80E/40E. By
default, it is 180.
----End
3.3.7 (Optional) Configuring the Authentication String for a PGP

Message
Two devices configured with E-APS will use an authentication string for security inspection. A
normal PGP negotiation can only be established when the authentication strings on both ends
are identical. Otherwise, the negotiation fails.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
or
The working or protection interface view is displayed.

Step 3 Run:
aps authenticate string
The authentication string is configured for the PGP message.
CAUTION
You must specify either the working or protection interface before configuring an authentication
string for the PGP message.
A normal PGP negotiation can only be established when the authentication strings configured
on both protection and working interfaces are identical.
----End
3.3.8 (Optional) Setting the WTR Time for an APS Group

The switchback waiting time, also called WTR time, can only be configured on a protection
interface in an APS group.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
or

Step 3 Run:
aps revert wtr-time
The WTR time is set for the APS group.

wtr-time: The value ranges from 1 to 12 minutes.
When setting the WTR time, note the following items:

l In 1:1 mode, after the fault is rectified and the WTR time (5 minutes) expires, traffic is
automatically switched back to the working link.
l In 1+1 mode, after the fault is rectified, traffic is not automatically switched back to the
working interface. The aps revert wtr-time command can be used to set a WRT time before
an APS group switchback is performed. After the fault is rectified, data services will swtich
to the working interface after the configured WRT time expires.
----End
3.3.9 Adding Members of an APS Group to a Trunk

The working and protection interfaces must be added to the same trunk link.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface atm-trunk interface-number
An ATM-Trunk interface is created and the view of the ATM-Trunk interface is displayed.
NOTE
APS can be configured on CPOS interfaces, ATM interfaces and POS interfaces. The corresponding trunk
interfaces are CPOS-Trunk, ATM-Trunk and POS-Trunk. Use the configuration of the ATM-Trunk as an
example.
ATM and POS interfaces cannot be configured on the X1 and X2 models of the NE80E/40E.
Step 3 Run:
quit
Step 4 Run:
Step 5 Run:
atm-trunk trunk-id
The interface is added to a trunk.
----End

After E-APS is configured, the APS group's working mode, working interface, switchback time,
and interface status can be viewed.

Procedure
Step 1 Run the display aps group group-id command, to view configurations of an APS group.
Step 2 Run the commands below to view configurations of trunk interfaces.
NOTE
ATM interfaces and POS interfaces cannot be configured on the X1 and X2 models of the NE80E/40E.
l Run the display atm-trunk trunk-id command to view configurations of the ATM-Trunk
interfaces.
l Run the display pos-trunk trunk-id command to view configurations of the POS-Trunk
interfaces.
l Run the display cpos-trunk trunk-id command to view configurations of the CPOS-Trunk
interfaces.
----End
Example
After E-APS is configured, run the display aps group group-id command on the router where
the protection interface is located to view configurations of the APS group.
<HUAWEI> display aps group 1
APS Group 1: APS working channel is 72.72.72.72
PGP authentication string: 111
Bidirection, 1:1 mode, Revert time(1 minutes)
KeepAlive Timer: 1(seconds), Hold Timer: 3(seconds)
--------------------------------------------------------------------------------
Group Work-Channel Protect-Channel Wtr W-State P-State Switch-Cmd Switch-Result
--------------------------------------------------------------------------------
1 72.72.72.72 Atm1/0/1 1 ok ok NA idle
--------------------------------------------------------------------------------
<HUAWEI> display atm-trunk 1
--------------------------------------------------------------------------------
Atm1/0/1 Up Active

This section provides configuration examples of APS. Each configuration example consists of
the networking requirements, configuration precautions, configuration roadmap, configuration
Context
NOTE
3.4.1 Example for Configuring TDM on the CPOS interfaces

Configured with APS
This section gives a configuration example of APS-based TDM on a CPOS interface. A
networking diagram is shown to demonstrate the configuration procedure. The configuration

example includes the networking requirements, as well as the configuration roadmap, procedure,
and files.
TDMoPSN service can enable mobile operators to receive transparent transmission of 2G
services between BTSs and BSCs in the same city through TDM links in a Metro Ethernet (ME)
network. This simple and cost-reducing service can be essential, because usually, it requires one
to three E1 interfaces on a BTS to connect to a BSC on a 2G RAN, and some mobile operators
do not own fixed network infrastructure and have to rent E1 lines at high prices.
As shown in Figure 3-2, it is required that the BTS and PE1 be connected through two E1 links.
The BSC and PE2 should be connected through the CPOS interface, which are configured with
APS so as to increase reliability of data. The encapsulation protocol on the channelized serial
interface of the E1 links need to be configured as TDM. Finally, a PW needs to be set up between
PE1 and PE2 to transparently transmit TDM cells.
Figure 3-2 Networking diagram of configuring TDMoPSN
E12/0/1
E12/0/2 CPOS3/0/1
GE2/0/0 GE2/0/0
2×TDM E1
GE1/0/0 GE2/0/0
CPOS3/0/2
PE1 P PE2 BSC
PWE3 TDM
Transparent Cell Transport
BTS
Device Interface IP Address
PE1 GE 2/0/0 10.1.1.1/24
Loopback0 192.2.2.2/32
P GE 1/0/0 10.1.1.2/24
GE 2/0/0 10.2.1.1/24
Loopback0 192.4.4.4/32
PE2 GE 2/0/0 10.2.1.2/24
Loopback0 192.3.3.3/32
1. Run the IGP protocol on the backbone network so that devices can communicate with each
other.

2. Configure basic MPLS functions on the backbone network, as well as the MPLS L2VPN
functions on PE devices. Establish the remote MPLS LDP peer relationship between PEs
at both ends of the PW.
3. Configure parameters for the TDM interface.
4. Configure a PW template.
5. Establish MPLS L2VC connections on PEs.
6. Configure APS on PE2
Data Preparation
l L2VC IDs at both ends of the PW (must be the same)
l MPLS LSR IDs of the PEs and P device
l IP addresses of the remote peers of PEs
Procedure
Step 1 Run the IGP protocol on the backbone network so that devices can communicate with each other.
For detailed configurations, see the configuration file of this example.
Step 2 Configure basic MPLS functions on the backbone network, as well as the MPLS L2VPN
functions on PE devices. Then, establish the remote MPLS LDP peer relationship between PEs
at both ends of the PW. For detailed configurations, see the configuration file of this example.
The remote MPLS LDP peer relationship is only required for dynamic PWs.
Step 3 Configure APS.
Configure PE2.
CAUTION
The BSC device connected with PE2 must support APS.
[PE2] controller cpos 3/0/1

[PE2-Cpos3/0/1] aps group 1
[PE2-Cpos3/0/1] aps working
[PE2-Cpos3/0/1] quit
[PE2-Cpos3/0/2] aps group 1
[PE2-Cpos3/0/2] aps protect
[PE2-Cpos3/0/2] aps mode one-plus-one unidirection
[PE2] interface cpos-trunk 1
[PE2-cpos-trunk1] quit
[PE2-Cpos3/0/1] cpos-trunk 1
[PE2-Cpos3/0/2] cpos-trunk 1
Step 4 Configure parameters for the TDM interface.

1. Configure PE1.

# Configure the channelized mode for CE1 2/0/1 and CE1 2/0/2 on PE1.
[PE1] controller e1 2/0/1
[PE1-E1 2/0/1] using e1
[PE1-E1 2/0/1] quit
[PE1] controller e1 2/0/2
[PE1-E1 2/0/2] using e1
[PE1-E1 2/0/2] quit
2. Configure PE2.
# Set parameters for the CPOS-Trunk interface on PE2.
[PE2] interface cpos-trunk 1
[PE2-Cpos-trunk1] e1 1 unframed
[PE2-Cpos-trunk1] e1 2 unframed
Step 5 Configure the encapsulation protocol on the serial interface as TDM.

1. Configure PE1.
[PE1] interface serial2/0/1:0
[PE1-Serial2/0/1:0] link-protocol tdm
[PE1-Serial2/0/1:0] quit
[PE1-Serial2/0/2:0] link-protocol tdm
[PE1-Serial2/0/2:0] quit
2. Configure PE2.
[PE2] interface trunk-serial1/1:0
[PE2-Trunk-Serial1/1:0] link-protocol tdm
[PE2-Trunk-Serial1/1:0] quit
[PE2-Trunk-Serial1/2:0] link-protocol tdm
Step 6 Configuring PWs.

1. Configure PE1.
[PE1] pw-template 1to3
[PE1-pw-template-1to3] peer-address 192.3.3.3
[PE1-pw-template-1to3] jitter-buffer depth 20
[PE1-pw-template-1to3] tdm-encapsulation-number 40
[PE1-pw-template-1to3] quit
[PE1-Serial2/0/1:0] mpls l2vc pw-template 1to3 100
[PE1-Serial2/0/2:0] mpls l2vc pw-template 1to3 200
2. Configure PE2.
[PE2] pw-template 3to1
[PE2-pw-template-3to1] peer-address 192.2.2.2
[PE2-pw-template-3to1] jitter-buffer depth 20
[PE2-pw-template-3to1] tdm-encapsulation-number 40
[PE2-pw-template-3to1] quit
[PE2-Trunk-Serial1/1:0] mpls l2vc pw-template 3to1 100
[PE2-Trunk-Serial1/1:0] undo shutdown
[PE2-Trunk-Serial1/2:0] mpls l2vc pw-template 3to1 200
[PE2-Trunk-Serial1/2:0] undo shutdown
Simulate a fault on the side of PE2 connecting to the BSC.
# Run the shutdown command on CPOS3/0/1.


[PE2-Cpos3/0/1] shutdown
Run the display aps group and display cpos-trunk commands. You can view that the status of
the protection interface CPOS 3/0/2 becomes active.
[PE2] display aps group 1
APS Group 1: Cpos 3/0/1 working channel 1(Inactive)
Pos3/0/2 protection channel 0(Active)
Unidirection, 1+1 mode, No Revert mode
------------------------------------------------------------------------
------------------------------------------------------------------------
1 Cpos 3/0/1 Cpos 3/0/2 NA sf ok NA switch
------------------------------------------------------------------------
total entry: 1
<PE2> display cpos-trunk 1
Interface Cpos-Trunk1's state information is:,
--------------------------------------------------------------------------------
Cpos3/0/1 Down Inactive
Cpos3/0/2 Up Active
Run the display mpls l2vc command on PEs. You can view that the status of the PW is Up and
has not been influenced by the fault of CPOS 3/0/1.
Use the display on PE1 as an example:

<PE1> display mpls l2vc interface serial2/0/1:0
*client interface : Serial2/0/1:0 is up
session state : up
AC state : up
VC state : up
VC ID : 100
VC type : SAT E1 over Packet
destination : 192.3.3.3
local group ID : 0
remote group ID : 0
local VC label : 146432
remote VC label : 145287
TDM encapsulation number : 40
jitter-buffer : 20
idle-code : FF
rtp-header : disable
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 statuscode : 0x0
BFD for PW : unavailable
manual fault : not set
active state : active
forwarding entry : not exist
link state : up
local VC MTU : 1500
remote VC MTU : 1500
local VCCV : alert lsp-ping bfd
remote VCCV : none
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 : 0 tunnels/tokens
create time : 0 days, 4 hours, 48 minutes, 51 seconds
up time : 0 days, 4 hours, 02 minutes, 39 seconds
last change time : 0 days, 0 hours, 39 minutes, 29 seconds
VC last up time : 2008/12/26 12:02:49
VC total up time : 0 days, 4 hours, 02 minutes, 39 seconds
CKey : 11
NKey : 10
----End
Configuration Files
l Configuration file of PE1
#
sysname PE1
#
mpls lsr-id 192.2.2.2
mpls
#
mpls l2vpn
#
pw-template 1to3
peer-address 192.3.3.3
jitter-buffer depth 20
tdm-encapsulation-number 40
#
mpls ldp
#
mpls ldp remote-peer 192.3.3.3
remote-ip 192.3.3.3
#
controller e1 2/0/1
using e1
undo shutdown
#
controller e1 2/0/2
using e1
undo shutdown
#
interface serial2/0/1:0
link-protocol tdm
mpls l2vc pw-template 1to3 100
undo shutdown
#
interface serial2/0/2:0
link-protocol tdm
undo shutdown
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 192.2.2.2 255.255.255.255
#
ospf 1
area 0.0.0.0
network 192.2.2.2 0.0.0.0
network 10.1.1.0 0.0.0.255
#
return

#
sysname PE2
#
mpls
#
mpls l2vpn
#
pw-template 3to1
jitter-buffer depth 20
tdm-encapsulation-number 40
#
mpls ldp
#
remote-ip 192.2.2.2
#
cpos-trunk 1
e1 1 unframed
e1 2 unframed
#
interface serial1/1:0
link-protocol tdm
undo shutdown
#
interface serial1/2:0
link-protocol tdm
undo shutdown
#
undo shutdown
ip address 10.2.2.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 192.3.3.3 255.255.255.255
#
ospf 1
area 0.0.0.0
network 192.3.3.3 0.0.0.0
network 10.2.2.0 0.0.0.255
#
return
l Configuration file of P
#
sysname P
#
mpls
#
mpls ldp
#
undo shutdown
ip address 10.1.1.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 10.2.2.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0

ip address 192.4.4.4 255.255.255.255

#
ospf 1
area 0.0.0.0
network 192.4.4.4 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.2.2.0 0.0.0.255
#
return
3.4.2 Example for Configuring APS on a CPOS-Trunk

In this example, a CPOS-Trunk is configured on the router to aggregate multiple E1 links
connected to mid-range-and-low-end devices and identify devices with different timeslots. In
addition, APS is configured on the CPOS interfaces of the router to implement protection
switching. This example includes networking requirements, configuration roadmap, data
preparation, configuration procedure, and configuration files.
NOTE
The NE40E-X8 is used as an example. Link interface numbers and link types may be different from those
in real-world situations.
As shown in Figure 3-3, mid-range-and-low-end devices are connected to the transport network
through E1 links. These E1 links are aggregated into a CPOS-Trunk configured on Router A.
Router A uses timeslots to identify these devices. The CPOS-Trunk on Router A consists of two
CPOS interfaces. Single-chassis APS needs to be configured on the CPOS interfaces to improve
data transfer reliability.
In real-world situations, mid-range-and-low-end devices are usually connected to CPOS
interfaces over a multi-layer transport network. Therefore, relay devices and other transport
means are probably involved.
Figure 3-3 Networking diagram for configuring APS on a CPOS-Trunk
E1 ..
ADM
RouterA
CPOS 1/0/0
E1
ADM STM-4/16 ADM CPOS-Trunk 0 Internet
OC-3/STM-1 CPOS 2/0/0
ADM
nx E1 ..

1. Configure single-chassis APS on the two CPOS interfaces, and add the CPOS interfaces
to a CPOS-Trunk.
2. Bundle timeslots of E1 channels in the CPOS-Trunk to create Trunk-Serial interfaces, and
add the Trunk-Serial interfaces into a Global-MP-Group.
Data Preparation
l APS parameters
l CPOS-Trunk parameters
l Global-MP-Group interface number
Procedure
Step 1 Configure single-chassis APS.
1. Configure single-chassis APS on Router A.
<HUAWEI> system-view
[HUAWEI] sysname RouterA
[RouterA] controller cpos 1/0/0
[RouterA-Cpos1/0/0] undo shutdown
[RouterA-Cpos1/0/0] aps group 1
[RouterA-Cpos1/0/0] aps working
[RouterA-Cpos1/0/0] quit
[RouterA-Cpos2/0/0] undo shutdown
[RouterA-Cpos2/0/0] aps group 1
[RouterA-Cpos2/0/0] aps protect
[RouterA-Cpos2/0/0] aps mode one-plus-one unidirection
2. Create a CPOS-Trunk on Router A and add CPOS interfaces to the CPOS-Trunk.

[RouterA] interface cpos-trunk 0
[RouterA-Cpos-Trunk0] quit
[RouterA-Cpos1/0/0] cpos-trunk 0
[RouterA-Cpos2/0/0] cpos-trunk 0
Step 2 Configure the CPOS-Trunk.

1. Bundle timeslots of E1 channels in the CPOS-Trunk.
[RouterA] interface cpos-trunk 0
[RouterA-Cpos-Trunk0] e1 1 unframed
[RouterA-Cpos-Trunk0] e1 2 unframed
[RouterA-Cpos-Trunk0] quit
2. Create a Global-MP-Group.
[RouterA] interface global-mp-group 0
[RouterA-Global-Mp-Group0] shutdown
[RouterA-Global-Mp-Group0] quit
3. Add Trunk-Serial interfaces to the Global-MP-Group.

[RouterA] interface Trunk-Serial0/1:0
[RouterA-Trunk-Serial0/1:0] shutdown
[RouterA-Trunk-Serial0/1:0] link-protocol ppp
[RouterA-Trunk-Serial0/1:0] ppp mp-global global-mp-group 0
[RouterA-Trunk-Serial0/1:0] quit
[RouterA-Trunk-Serial0/2:0] shutdown
[RouterA-Trunk-Serial0/2:0] link-protocol ppp

[RouterA-Trunk-Serial0/2:0] ppp mp-global global-mp-group 0

4. Restart Trunk-Serial interfaces and the Global-MP-Group.

[RouterA] interface global-mp-group 0
[RouterA-Global-Mp-Group0] undo shutdown
[RouterA-Global-Mp-Group0] quit
[RouterA-Trunk-Serial0/1:0] undo shutdown
[RouterA-Trunk-Serial0/2:0] undo shutdown

# Run the display aps group command on Router A to view the APS configuration. The
command output shows the working interface, protection interface, and switchback WTR time.
[RouterA] display aps group 1
APS Group 1: Cpos1/0/0 working channel 1(Active)
Cpos2/0/0 protection channel 0(Inactive)
Unidirectional, 1+1 mode, Revert time(6 minutes)
------------------------------------------------------------------------
------------------------------------------------------------------------
1 Cpos1/0/0 Cpos2/0/0 6 ok ok NA idle
------------------------------------------------------------------------
total entry: 1
# Run the display cpos-trunk command to view the CPOS-Trunk configuration. The command
output shows the status of CPOS-Trunk member interfaces.
[RouterA] display cpos-trunk 0
Interface Cpos-Trunk0's state information is:
--------------------------------------------------------------------------------
Cpos1/0/0 Up Active
Cpos2/0/0 Up Inactive
# Run the display ppp mp-global command to view the Global-MP-Group configuration. The
command output shows the status of Trunk-Serial interfaces in the Global-MP-Group.
[RouterA] display ppp mp-global
Global-Mp-Group is Global-Mp-Group0
===========Sublinks status begin======
Trunk-Serial0/1:0 physical UP,protocol UP
Trunk-Serial0/2:0 physical UP,protocol UP
===========Sublinks status end========
----End
Configuration Files
#
Configuration file of Router A

#
sysname RouterA
#
controller Cpos1/0/0
undo shutdown
aps group 1
aps working

cpos-trunk 0
#
controller Cpos2/0/0
undo shutdown
aps group 1
aps protect
aps mode one-plus-one unidirection
cpos-trunk 0
#
interface Cpos-Trunk0
undo shutdown
e1 1 unframed
e1 2 unframed
#
interface Global-Mp-Group0
undo shutdown
#
interface Trunk-Serial0/1:0
undo shutdown
link-protocol ppp
ppp mp-global global-mp-group 0
#
interface Trunk-Serial0/2:0
undo shutdown
link-protocol ppp
ppp mp-global global-mp-group 0
#
return
3.4.3 Example for Associating PW Redundancy with E-APS

Working in 1:1 Mode
This section provides a configuration example for associating PW redundancy with E-APS
working in 1:1 mode. A networking diagram is provided to demonstrate the configuration
procedure. The configuration example includes networking requirements, configuration
roadmap, configuration procedure, and configuration files.
As shown in Figure 3-4, PE1 is dual-homed to PE2 and PE3 through two PWs. When a fault
occurs on the network side, the switchover of TE groups rather than PWs is performed. When
a fault occurs on the AC side, the switchover between the working interface and the protection
interface is performed on the AC side according to APS. This leads to the switchover of PWs
and thus avoids the loss of the network data.

Figure 3-4 Networking of the association between PW redundancy and APS

Loopback0 Loopback0
2.2.2.2 4.4.4.4
1
Loopback0 2/0
GE .2/24 P1 GE3/0/2 PE2
1.1.1.1 .1 104.1.1.1/24 AT
1.1 M1
10 /0/
/1 /24 GE3/0/2 1
2 / 0 .1 104.1.1.2/24 AT
GE 1.1.1 M2 CE2
0 GE1/0/2 /0/
1 TE 1
MPLS 106.1.1.1/24
PE1 E-APS
MPL GE1/0/2 2
G
ATM 1/0/0 1 E2/0 S TE 106.1.1.2/24 2 /0/
02
.1. 2
/ ATM
1.1 GE3/0/2 /2
/24 /0
105.1.1.2/24 M1
10 GE2 AT
2.1 GE3/0/2
ATM 1/0/0 .1. /0/2 PE3
2/2
4
P2 105.1.1.1/24
Loopback0 Loopback0
3.3.3.3 5.5.5.5
1. Configure the IP address and routing protocol to make PEs routable.
2. Configure MPLS TE.
3. Configure E-APS between PE2 and PE3 and single APS on CE2.
4. Configure primary and backup PWs on PE1 to be dual-homed to PE2 and PE3, configure
common PWs on PE2 and PE3, and configure a bypass PW between PE2 and PE3.
5. Configure a BFD session to detect a PW.
Data Preparation
l IP address of each interface
l MPLS TE of each PE
l Parameters necessary for configuring E-APS, such as the WTR time and authentication
string for the PGP message
l Parameters of PW.
l Parameters of BFD session to detect a PW.
Procedure
Step 1 Configure IP addresses and IGP to make PEs routable.
1. Configure IP addresses on the interfaces.
Assign the IP address and mask to each interface according to Figure 3-4. The configuration
details are not mentioned here.

2. Configure IGP. In this example, IS-IS is adopted.

# Configure PE1.
[PE1] isis 1
[PE1-isis-1] is-level level-1
[PE1-isis-1] network-entity 1111.1111.1111.1111.00
[PE1-isis-1] graceful-restart
[PE1-isis-1] cost-style wide-compatible
[PE1-isis-1] timer spf 1 1 50
[PE1-isis-1] traffic-eng level-1-2
[PE1-isis-1] quit
[PE1] interface gigabitEthernet 2/0/1
[PE1-GigabitEthernet2/0/1] isis enable 1
[PE1-GigabitEthernet2/0/1] quit
[PE1] interface loopback 0
[PE1-LoopBack0] isis enable 1
[PE1-LoopBack0] quit
# Configure P1.
[P1] isis 1
[P1-isis-1] is-level level-1
[P1-isis-1] network-entity 2222.2222.2222.2222.00
[P1-isis-1] graceful-restart
[P1-isis-1] cost-style wide-compatible
[P1-isis-1] timer spf 1 1 50
[P1-isis-1] traffic-eng level-1-2
[P1-isis-1] quit
[P1] interface gigabitEthernet 2/0/1
[P1-GigabitEthernet2/0/1] isis enable 1
[P1-GigabitEthernet2/0/1] quit
[P1] interface loopback 0
[P1-LoopBack0] isis enable 1
[P1-LoopBack0] quit
# Configure P2.
[P2] isis 1
[P2-isis-1] is-level level-1
[P2-isis-1] network-entity 3333.3333.3333.3333.00
[P2-isis-1] graceful-restart
[P2-isis-1] cost-style wide-compatible
[P2-isis-1] timer spf 1 1 50
[P2-isis-1] traffic-eng level-1-2
[P2-isis-1] quit
[P2] interface loopback 0
[P2-LoopBack0] isis enable 1
[P2-LoopBack0] quit
# Configure PE2
[PE2] isis 1


[PE2-isis-1] quit
# Configure PE3
[PE3] isis 1
[PE3-isis-1] quit
Step 2 Configure MPLS TE.

# Configure PE1.
[PE1] interface loopBack 0
[PE1-LoopBack0] ip address 1.1.1.1 32
[PE1] mpls lsr-id 1.1.1.1
[PE1] mpls
[PE1-mpls] mpls te
[PE1-mpls] quit
[PE1] interface gigabitethernet 2/0/1
[PE1-GigabitEthernet2/0/1] mpls
[PE1-GigabitEthernet2/0/1] mpls te
# Configure P1.
[P1] interface loopBack 0
[P1-LoopBack0] ip address 2.2.2.2 32
[P1-LoopBack0] quit
[P1] mpls lsr-id 2.2.2.2
[P1] mpls
[P1-mpls] mpls te
[P1-mpls] quit
[P1] interface gigabitethernet 2/0/1
[P1-GigabitEthernet2/0/1] mpls
[P1-GigabitEthernet2/0/1] mpls te

# Configure P2.
[P2] interface loopBack 0
[P2-LoopBack0] ip address 3.3.3.3 32
[P2-LoopBack0] quit
[P2] mpls lsr-id 3.3.3.3
[P2] mpls
[P2-mpls] mpls te
[P2-mpls] quit
# Configure PE2
[PE2] mpls
[PE2-mpls] mpls te
[PE2-mpls] quit
# Configure PE3
[PE3] mpls
[PE3-mpls] mpls te
[PE3-mpls] quit
2. Configure an explicit path of a tunnel.

# Configure PE1
[PE1] explicit-path path1
[PE1-explicit-path-path1] next hop 101.1.1.2
[PE1] explicit-path path2
#Configure PE2
[PE2] explicit-path path
[PE2-explicit-path-path] next hop 104.1.1.1
#Configure PE3
[PE3] explicit-path path


# Configure PE1
[PE1] interface tunnel 1/0/0
[PE1-Tunnel1/0/0] ip address unnumbered interface LoopBack0
[PE1-Tunnel1/0/0] tunnel-protocol mpls te
[PE1-Tunnel1/0/0] destination 4.4.4.4
[PE1-Tunnel1/0/0] mpls te tunnel-id 1
[PE1-Tunnel1/0/0] mpls te path explicit-path path1
[PE1-Tunnel1/0/0] mpls te reserved-for-binding
[PE1-Tunnel1/0/0] mpls te commit
[PE1-Tunnel1/0/0] quit
[PE1-Tunnel2/0/0] mpls te path explicit-path path2
[PE1] tunnel-policy ct1
[PE1-tunnel-policy-ct1] tunnel select-seq cr-lsp load-balance-number 1
[PE1-tunnel-policy-ct1] quit
[PE1] tunnel-policy ct2
[PE1-tunnel-policy-ct2] tunnel select-seq cr-lsp load-balance-number 1
[PE1-tunnel-policy-ct2] quit
# Configure PE2
[PE2-Tunnel1/0/0] mpls te path explicit-path path
[PE2] tunnel-policy ct
[PE2-tunnel-policy-ct] tunnel select-seq cr-lsp load-balance-number 1
[PE2-tunnel-policy-ct] quit
# Configure PE3
[PE3-Tunnel1/0/0] mpls te path explicit-path path
[PE3] tunnel-policy ct
[PE3-tunnel-policy-ct] tunnel select-seq cr-lsp load-balance-number 1
[PE3-tunnel-policy-ct] quit
Step 3 Configure E-APS

1. Configure APS on PE2, PE3, and CE2.
# Configure PE2.
[PE2] interface atm 1/0/1

[PE2-Atm1/0/1] undo shutdown

[PE2-Atm1/0/1] aps group 1
[PE2-Atm1/0/1] aps working 5.5.5.5 4.4.4.4
[PE2-Atm1/0/1] aps timers 1 180
[PE2-Atm1/0/1] quit
# Configure PE3.
[PE3-Atm1/0/2] aps group 1
[PE3-Atm1/0/2] aps protect 4.4.4.4 5.5.5.5
[PE3-Atm1/0/2] aps mode one2one bidirection
[PE3-Atm1/0/2] aps revert 5
[PE3-Atm1/0/2] aps timers 1 180
[PE3-Atm1/0/2] quit
# Configure CE2.
[HUAWEI] sysname CE2
[CE2] interface atm 2/0/1
[CE2-Atm2/0/1] aps group 1
[CE2-Atm2/0/1] aps working
[CE2-Atm2/0/1] quit
[CE2-Atm2/0/2] aps group 1
[CE2-Atm2/0/2] aps protect
[CE2-Atm2/0/2] aps mode one2one bidirection
[CE2-Atm2/0/2] aps revert 5
[CE2-Atm2/0/2] quit
2. Create an ATM-Trunk on PE2, PE3, and CE2 and add interfaces to the ATM-Trunk.
# Configure PE2.
[PE2] interface atm-trunk 1
[PE2-Atm-Trunk1] quit
[PE2-Atm1/0/1] atm-trunk 1
# Configure PE3.
[PE3] interface atm-trunk 1
[PE3-Atm-Trunk1] quit
[PE3-Atm1/0/2] atm-trunk 1
# Configure CE2.
[CE2] interface atm-trunk 1
[CE2-Atm-Trunk1] quit
[CE2-Atm2/0/1] atm-trunk 1
[CE2-Atm2/0/1] quit
[CE2-Atm2/0/2] atm-trunk 1
Step 4 Configure PWs.

# Configure PE1.
[PE1] mpls l2vpn
[PE1-l2vpn] quit
[PE1] pw-template pwt
[PE1-pw-template-pwt] control-word
[PE1-pw-template-pwt] quit
[PE1-Atm1/0/0] quit

[PE1] interface atm 1/0/0.1 p2p

[PE1-Atm1/0/0.1] atm cell transfer
[PE1-Atm1/0/0.1] pvc 1/100
[PE1-atm-pvc-Atm1/0/0.1-1/100] quit
[PE1-Atm1/0/0.1] mpls l2vc 4.4.4.4 pw-template pwt 1 tunnel-policy ct1
[PE1-Atm1/0/0.1] mpls l2vc 5.5.5.5 pw-template pwt 2 tunnel-policy ct2 secondary
[PE1-Atm1/0/0.1] mpls l2vpn redundancy independent
[PE1-Atm1/0/0.1] mpls l2vpn stream-dual-receiving
[PE1-Atm1/0/0.1] quit
# Configure PE2.
[PE2] mpls l2vpn
[PE2-l2vpn] quit
[PE2] interface atm-trunk 1.1 p2p
[PE2-Atm-Trunk1.1] pvc 1/100
[PE2-atm-pvc-Atm-trunk1.1-1/100] quit
[PE2-Atm-Trunk1.1] mpls l2vc 1.1.1.1 pw-template pwt 1 tunnel-policy ct
[PE2-Atm-Trunk1.1] mpls l2vc 5.5.5.5 3 bypass
[PE2-Atm-Trunk1.1] quit
# Configure PE3.
[PE3] mpls l2vpn
[PE3-l2vpn] quit
[PE3] interface atm-trunk 1.1 p2p
[PE3-Atm-Trunk1.1] pvc 1/100
[PE3-atm-pvc-Atm-trunk1.1-1/100] quit
[PE3-Atm-Trunk1.1] mpls l2vc 1.1.1.1 pw-template pwt 1 tunnel-policy ct
[PE3-Atm-Trunk1.1] mpls l2vc 4.4.4.4 3 bypass
[PE3-Atm-Trunk1.1] quit
The command output shows that PE1 has the primary PW and backup PW, which are in the
Active and Inactive states respectively.
Step 5 Configure a BFD session to detect a PW.
# Configure PE1.
[PE1] bfd
[PE1-bfd] quit
[PE1] bfd bfd1 bind pw interface atm 1/0/0 remote-peer 4.4.4.4 pw-ttl auto-calculate
[PE1-bfd-session-bfd1] discriminator local 222
[PE1-bfd-session-bfd1] discriminator remote 111
[PE1-bfd-session-bfd1] quit
[PE1] bfd bfd2 bind pw interface atm 1/0/0 remote-peer 5.5.5.5 pw-ttl auto-calculate
[PE1-bfd-session-bfd2] discriminator local 444
[PE1-bfd-session-bfd2] discriminator remote 333
[PE1-bfd-session-bfd2] quit
# Configure PE2.
[PE2] bfd
[PE2-bfd] quit
[PE2] bfd bfd bind pw interface atm 1/0/1 remote-peer 1.1.1.1 pw-ttl auto-calculate
[PE2-bfd-session-bfd] discriminator local 111
[PE2-bfd-session-bfd] discriminator remote 222
[PE2-bfd-session-bfd] quit
# Configure PE3.
[PE3] bfd
[PE3-bfd] quit

[PE3] bfd bfd bind pw interface atm 1/0/2 remote-peer 1.1.1.1 pw-ttl auto-calculate
[PE3-bfd-session-bfd] discriminator local 333
[PE3-bfd-session-bfd] discriminator remote 444
[PE3-bfd-session-bfd] quit

# Run the display aps group 1 command on PE2 and PE3 to view E-APS configurations.
APS Group 1: Atm1/1/1 working channel 1(Active)
APS protection channel is 5.5.5.5
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
1 Atm1/0/1 5.5.5.5 NA ok ok NA idle
--------------------------------------------------------------------------------
APS Group 1: APS working channel is 4.4.4.4
Bidirection, 1:1 mode, Revert time(1 minutes)
KeepAlive Timer: 1(seconds), Hold Timer: 3(seconds)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
1 4.4.4.4 Atm1/0/2 1 ok ok NA idle
--------------------------------------------------------------------------------
[PE2] display atm-trunk 1
--------------------------------------------------------------------------------
Atm1/0/1 Up Active
[PE3] display atm-trunk 1
--------------------------------------------------------------------------------
Atm1/0/2 Up Inactive
----End
Configuration File
l Configuration File on PE1.
#
sysname PE1
isis 1
is-level level-1
network-entity 1111.1111.1111.1111.00
graceful-restart
cost-style wide-compatible
timer spf 1 1 50
traffic-eng level-1-2
quit
#
interface gigabitEthernet 2/0/1
isis enable 1
mpls
mpls te
quit
isis enable 1
mpls
mpls te
quit

#
interface loopBack 0
ip address 1.1.1.1 32
quit
mpls lsr-id 1.1.1.1
mpls
mpls te
quit
#
explicit-path path1
next hop 101.1.1.2
next hop 104.1.1.2
next hop 4.4.4.4
quit
explicit-path path2
next hop 102.1.1.2
next hop 105.1.1.2
next hop 5.5.5.5
quit
#
interface tunnel 1/0/0
ip address unnumbered interface LoopBack0
tunnel-protocol mpls te
destination 4.4.4.4
mpls te tunnel-id 1
mpls te path explicit-path path1
mpls te reserved-for-binding
mpls te commit
quit
destination 5.5.5.5
mpls te tunnel-id 2
mpls te path explicit-path path2
mpls te commit
quit
tunnel-policy ct1
tunnel select-seq cr-lsp load-balance-number 1
quit
tunnel-policy ct2
quit
#
mpls l2vpn
quit
pw-template pwt
control-word
quit
interface atm 1/0/0
undo shutdown
quit
#
interface
Atm1/0/0.1
atm cell
transfer
pvc
1/100
mpls l2vc 4.4.4.4 pw-template pwt 1 tunnel-policy ct1
mpls l2vc 5.5.5.5 pw-template pwt 2 tunnel-policy ct2 secondary
mpls l2vpn redundancy
independent
mpls l2vpn stream-dual-
receiving
#
bfd
quit

bfd bfd1 bind pw interface atm 1/0/0 remote-peer 4.4.4.4 pw-ttl auto-
calculate
discriminator local 222
discriminator remote 111
quit
bfd bfd2 bind pw interface atm 1/0/0 remote-peer 5.5.5.5 pw-ttl auto-
calculate
quit
#
return
l Configuration File on P1.
isis 1
is-level level-1
network-entity 2222.2222.2222.2222.00
graceful-restart
timer spf 1 1 50
quit
#
isis enable 1
mpls
mpls te
quit
isis enable 1
mpls
mpls te
quit
quit
#
mpls lsr-id 2.2.2.2
mpls
mpls te
quit
#
return
l Configuration File on P2.
isis 1
is-level level-1
network-entity 3333.3333.3333.3333.00
graceful-restart
timer spf 1 1 50
quit
#
isis enable 1
mpls
mpls te
quit
isis enable 1
mpls
mpls te
quit
quit
#
mpls lsr-id 3.3.3.3
mpls

mpls te
quit
#
return
isis 1
is-level level-1
network-entity 4444.4444.4444.4444.00
graceful-restart
timer spf 1 1 50
quit
#
isis enable 1
mpls
mpls te
quit
isis enable 1
quit
quit
#
mpls lsr-id 4.4.4.4
mpls
mpls te
quit
#
explicit-path path
next hop 104.1.1.1
next hop 101.1.1.1
next hop 1.1.1.1
#
destination 1.1.1.1
mpls te tunnel-id 1
mpls te path explicit-path path
mpls te commit
quit
#
tunnel-policy ct
quit
#
interface atm 1/0/1
undo shutdown
aps group 1
aps working 5.5.5.5 4.4.4.4
aps timers 1 180
atm-trunk 1
quit
#
interface atm-trunk 1
quit
#
mpls l2vpn
quit
pw-template pwt
control-word
quit
#
interface atm-trunk 1.1 p2p
pvc 1/100

quit
mpls l2vc 1.1.1.1 pw-template pwt 1 tunnel-policy ct
mpls l2vc 5.5.5.5 3 bypass
quit
#
bfd
quit
bfd bfd bind pw interface atm 1/0/1 remote-peer 1.1.1.1 pw-ttl auto-calculate
quit
#
return
isis 1
is-level level-1
network-entity 5555.5555.5555.5555.00
graceful-restart
timer spf 1 1 50
quit
#
isis enable 1
mpls
mpls te
quit
isis enable 1
quit
quit
#
mpls lsr-id 5.5.5.5
mpls
mpls te
quit
#
explicit-path path
next hop 105.1.1.1
next hop 102.1.1.1
next hop 1.1.1.1
#
destination 1.1.1.1
mpls te tunnel-id 1
mpls te path explicit-path path
mpls te commit
quit
#
tunnel-policy ct
quit
#
interface atm 1/0/2
undo shutdown
aps group 1
aps aps protect 4.4.4.4 5.5.5.5
aps mode one2one bidirection
aps revert 5
aps timers 1 180
atm-trunk 1
quit
#

interface atm-trunk 1
quit
#
mpls l2vpn
quit
pw-template pwt
control-word
quit
#
interface atm-trunk 1.1 p2p
pvc 1/100
quit
mpls l2vc 1.1.1.1 pw-template pwt 1 tunnel-policy ct
mpls l2vc 4.4.4.4 3 bypass
quit
#
bfd
quit
bfd bfd bind pw interface atm 1/0/2 remote-peer 1.1.1.1 pw-ttl auto-calculate
quit
#
return

Configuration Guide - Reliability 4 VRRP Configuration
4 VRRP Configuration
About This Chapter
A VRRP backup group allows a backup to take over network traffic from a master if the master
fails.
4.1 VRRP Introduction

VRRP, a fault-tolerant technology, implements routing among multiple egress gateways by
separating physical devices from logical devices.
4.2 Configuring the VRRP Backup Group
By configuring the VRRP backup group in master/backup mode or load balancing mode, you
can implement the communication between hosts inside a LAN and external networks.
4.3 Configuring VRRP to Track the Status of an Interface
By configuring a VRRP backup group to track the interface status, you can implement the backup
function when the interface fails.
4.4 Configuring a Fast VRRP Switchover (in Common Mode)
By tracking the BFD session status or the EFM OAM session status, a VRRP backup group
implements VRRP switchovers rapidly.
4.5 Configuring VRRP Fast Switchover (Using BFD Sampling)
By configuring a BFD session in BFD sampling mode, you can address the problem that a link
BFD session fails to be set up between an NPE and a PE.
4.6 Configuring Ignorance of the Down of an Interface Where the mVRRP Backup Group Is
Configured
By configuring mVRRP with the function of ignoring the interface Down event, you can resolve
the problem that mVRRP and a peer BFD session cannot be configured between NPEs.
4.7 Configuring VRRP Applications in VLANIF
By configuring a VRRP backup group on VLANIF interfaces, you can perform the fast VRRP
switchover.
4.8 Configuring VRRP Security
On a network at security risks, by configuring an authentication mode of VRRP packets, you
can protect devices against attacks.
4.9 Configuring VRRP Smooth Switching

By configuring smooth VRRP switching, you can address the problem of traffic loss due to the
AMB/SMB switchover.
4.10 Adjusting and Optimizing VRRP
By adjusting parameters of a VRRP backup group, you can optimize the functions of the VRRP
backup group.
4.11 Configuring mVRRP Backup Groups
An mVRRP backup group can be bound to other member backup groups and determine the
status of member backup groups according to the bindings. This is applicable to the scenario
where a device is dual-homed to master and slave devices on a MAN.
4.12 Configuring VRRP Version Upgrade
After being upgraded from version 2 to version 3, VRRP can support both IPv6 and IPv4
networks.
4.13 Maintaining VRRP
This section describes how to maintain VRRP. Detailed operations include deleting VRRP
statistics, and monitoring the VRRP operation status.
The following sections provide several examples for configuring VRRP to improve reliability.
Familiarize yourself with the configuration procedures against the networking diagram. Each
configuration example consists of the networking requirements, configuration roadmap,
configuration procedures, and configuration files.

4.1 VRRP Introduction

VRRP, a fault-tolerant technology, implements routing among multiple egress gateways by
separating physical devices from logical devices.
4.1.1 VRRP Overview

The Virtual Router Redundancy Protocol (VRRP) groups multiple routers into one virtual router,
and sets the default gateway address as the IP address of the virtual router.
All hosts on a network are configured with the same default route to an egress gateway. These
hosts send all packets whose destination addresses are not on the local network segment to the
default egress gateway, such as Router A in Figure 4-1. The default egress gateway allows the
hosts and external networks to communicate. If the egress gateway is Down, all hosts using this
gateway fail to communicate with external networks.
Figure 4-1 LAN default gateway
Gateway:10.0.0.1
Gateway:10.0.0.1 10.0.0.1/24
IP Address:10.0.0.3/24 Network
Gateway:10.0.0.1 RouterA
Ethernet
A common method to improve the system reliability is to deploy multiple egress gateways. In
addition, a mechanism for selecting one of routes to these gateways is required.
VRRP is a fault-tolerant protocol defined in RFC 3768. VRRP allows the hosts to select one of
routes to multiple egress gateways by separating logical devices from physical devices.
On a LAN (for example, an Ethernet) with multicast and broadcast capabilities, VRRP uses
logical gateways to provide high availability for transmission links, preventing a gateway failure
from interrupting services, without changing the configuration of routing protocols.
4.1.2 VRRP Features Supported by the NE80E/40E

VRRP features include the VRRP backup group in master/backup mode, VRRP backup group
in load balancing mode, tracking of the interface status, fast VRRP switchover, ping of the virtual
IP address, VRRP security authentication, smooth VRRP switching, and Management Virtual
Router Redundancy Protocol (mVRRP).
Master/Backup Mode
In VRRP, it is the basic mode for the backup of IP addresses. In the master/backup mode, a
VRRP backup group consists of a master router and multiple backup routers. Different routers

have different priorities in this backup group. The router with the highest priority serves as the
master router.
l The master router undertakes all the services in normal condition.

l The backup routers undertake the services only when the master router fails.
Load Balancing Mode

In the load balancing mode, two or more backup groups are created. Multiple backup groups
undertake services at the same time.
In the load balancing mode, the VRRP backup groups have the following features:
l In the NE80E/40E, a router can join several VRRP backup groups and has different
priorities in different backup groups. Multiple virtual routers carry out load balancing.
l Each backup group consists of a master router and several backup routers.
l The master router of each backup group can be different.
Tracking the Interface Status

In the NE80E/40E, the interfaces can be tracked. When the interface status changes, the priority
of the router is automatically adjusted. The priorities of routers in the backup group change and
a new master router is elected.
VRRP Fast Switchover

l In the NE80E/40E, Bidirectional Forwarding Detection (BFD) is implemented to rapidly
detect and track the connectivity of network links or IP routes. VRRP implements fast
master/backup switchover by tracking the BFD session status. A maximum of eight BFD
sessions can be configured and the master/backup switchover is performed at millisecond
level. The VRRP master/backup switchover is accelerated because of tracking BFD
sessions.
The VRRP tracks the following types of BFD sessions:
– Normal BFD session
– Peer BFD session
– Link BFD session
The comparison of three types of BFD sessions tracked by VRRP are as follows:
– Similarity:
– These three types of BFD sessions can detect faults on a link or a device.
– The VRRP backup group can perform the switchover at millisecond level by tracking
BFD sessions.
– Differences:
– When VRRP tracks normal BFD sessions, the status of a VRRP backup group varies
according to its priority change. This function is similar to that of tracking interface
status, but it is faster. When the status of the tracked BFD session becomes Up, the
priority of the router in the backup group restores the original value. When the BFD
session is configured on a backup router, the BFD session should be on the same
interface with the VRRP backup group.

– When VRRP tracks peer BFD sessions and link BFD sessions, the status of the
backup group is changed and its priority is unchanged.
– The peer BFD session can detect faults of local and remote NPEs and the links. It
cannot distinguish whether the failure occurs locally or remotely. The link BFD
session can only detect the faults of local links or NPEs.
l VRRP can monitor EFM. On a Metro Ethernet (ME) network, Bidirectional Forwarding
Detection (BFD) is usually used to detect and protect the link between the master and
backup Network Provider Edges (NPEs), and the links between the Underlayer Provider
Edge (UPE) and both NPEs. If BFD cannot be configured on the UPE, the links between
the UPE and NPEs becomes vulnerable and you need a new link protection mechanism.
Ethernet in the First Mile (EFM), a slow link detection protocol that requires fewer
resources, can just be your choice, provided that EFM is configured on the UPE.
VRRP Fast Switchover Using BFD Sampling

Generally, the VRRP backup group implements fast master/backup switchover by tracking the
BFD session status. However, this method is not applicable in some special network
environments or when the device does not support the BFD function. In this case, you can use
the BFD sampling mode to implement fast master/backup switchover.
NOTE
In BFD sampling mode, the NPE establishes multiple link BFD sessions directly with each CE without
establishing the link BFD session with the PE.
Ignorance of Interface Down of the mVRRP Backup Group

VRRP defines three status types: Initialize, Master, and Backup. On being notified that the
interface where the VRRP backup group is configured is shut down, the VRRP backup group
switches its status to Initialize.
The mVRRP backup group is configured on two directly connected devices and Heartbeat
messages of the mVRRP backup group are transmitted over the direct link between the two
devices. When one device fails, the interface of its peer device goes Down and the status of the
mVRRP backup group on the interface becomes Initialize. As a result, the peer device also fails.
To prevent this, you can use the function of ignorance of the down of an interface where the
mVRRP backup group is configured to implement VRRP fast switchover, thus switching the
status of the mVRRP backup group to Master rather than Initialize.
Enable/Disable the Ping Function to the Virtual IP Address

To ping through virtual IP addresses that are used in the VRRP backup group, you can monitor
the operating status of the virtual routers but the VRRP backup group may suffer the ICMP
attack. In the NE80E/40E, you can run a command to enable the function to ping the virtual IP
address.
VRRP Security Functions

For different security levels of networks, you can set different authentication modes and
authentication keys in the header of VRRP packets.
In a secure network, you can adopt the default configuration. That is, the router does not
authenticate the VRRP packets to be sent and received. The router considers all the received
packets as real and valid VRRP packets. In this case, no authentication key is required.

VRRP provides simple text authentication and MD5 authentication for networks that are
vulnerable to attacks. In simple text authentication mode, a string of 1 to 8 characters can be
configured as the authentication key. In MD5 authentication mode, a string of 1 to 8 characters
in plain text or a string of 24 characters in encrypted text can be configured as the authentication
key.
VRRP Smooth Switching

On the network configured with a VRRP backup group, during the AMB/SMB switchover of
the master device, the backup device directly becomes the master one because the master device
and the backup device cannot communicate in time. After the AMB/SMB switchover of the
original master device, if its priority is higher than the current master device, it automatically
becomes the master device. During the AMB/SMB switchover, the system is busy processing
packets. Thus, the gratuitous ARP packets sent by the master device are blocked or processed
abnormally, and the system must refresh the MAC entries of the downstream switch through
subsequent packets. As a result, user packets are dropped in this period of time.
VRRP smooth switching can solve such a problem. After the AMB/SMB switchover takes place
on the master device and the new AMB is started, if the priority of the current backup device is
higher than that of the current master device, the backup device becomes the master device
automatically. At this time, VRRP saves the currently configured interval and adjusts the interval
for sending a VRRP Advertisement packet to the configured interval. After receiving a VRRP
Advertisement packet, the backup device learns the new interval carried in the packet. This
ensures the stability of the VRRP backup group during or after the AMB/SMB switchover of
the master device and prevents packet loss.
After VRRP smooth switching is enabled, the learning function takes precedence over the
preemption function. That is, if the interval carried in the received packet is inconsistent with
the current interval and the priority carried in the received packet is lower than the current
priority, VRRP performs the learning and timer resetting functions first, and then the preemption
function.
VRRP smooth switching also depends on the system. If the system is quite busy since the AMB/
SMB switchover and cannot schedule the operation on the VRRP module, VRRP smooth
switching cannot take effect.
mVRRP
Many VRRP backup groups run between routers for different services. If each VRRP backup
group needs to maintain its own state machine, a large number of VRRP packets are generated
between routers. To simplify the process and reduce the bandwidth occupied by protocol packets,
you can configure a VRRP backup group to be an mVRRP backup group and bind it to other
backup group members. Then, the status of the backup group member is determined by the status
of the bound mVRRP backup group.
NOTE
For the detailed configuration of the mVRRP, refer to Chapter 9 "VPLS Convergence Configuration" in
the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN.
VRRP6
VRRP for IPv6, also called VRRP6, is a fault-tolerant protocol functioning as an extension to
the VRRP protocol. VRRP6 groups multiple routers into one virtual router. When the next hop
of a host fails, VRRP6 can switch services to another router through a certain mechanism. This
thus ensures coherence and reliability of communications.

The following table shows the comparison between VRRP6 and VRRP for IPv4 based on
functions.
Function VRRP6 VRRP for IPv4
Master/backup mode Supported Supported
Load balancing mode Supported Supported
Interface status tracking Supported Supported
Fast VRRP switchover Supported Supported
Pinging a virtual IP address Supported Supported
Security authentication of VRRP Not supported Supported

backup groups
Smooth VRRP switching Not supported Supported
mVRRP Supported Supported
4.2 Configuring the VRRP Backup Group

By configuring the VRRP backup group in master/backup mode or load balancing mode, you
can implement the communication between hosts inside a LAN and external networks.

Before configuring a VRRP backup group, 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.
The VRRP backup group works in master/backup mode or load balancing mode.
l The master/backup switchover is a basic function provided by VRRP. The master/backup

mode is as follows:
– Only one backup group exist.
– The router with the highest priority in the backup group serves as the master router and
undertakes the services.
– Except for the master router, other routers in the backup group serve as the backup
routers and work in the Backup state.
– If the master router fails, backup routers select a new master router based on their
priorities to provide routing service.
l In the load balancing mode, multiple backup groups are created to share the traffic of a
network. One router can join different backup groups. The load balancing mode is as
follows:

– Router A serves as the master device in backup group 1 and the backup device in backup
group 2.
– Router B serves as the master device in backup group 2 and the backup device in backup
group 1.
– Some hosts on the network use backup group 1 as their gateway and others use backup
group 2 as their gateway.
In this case, they can back up each other and share the traffic.
NOTE
The GigabitEthernet,Ethernet, virtual Ethernet (VE),Eth-Trunk, VLANIF and the GE sub-interface support
VRRP.
Before configuring the VRRP backup group, complete the following tasks:
l Configuring network layer attributes for the interface to connect the network
Data Preparation
To configure the VRRP backup group, you need the following data.
No. Data
1 Backup group ID
2 Virtual IP address of the backup group
3 Priorities of routers in the VRRP backup group
4.2.2 Creating a Backup Group and Configuring a Virtual IP

Address
By creating a VRRP backup group, you can use the default gateway address on a LAN to be the
IP address of the VRRP backup group.
Context
Do as follows on each router of a backup group:
Perform the following step as required to configure VRRP for IPv4 or VRRP for IPv6.
Procedure
l For VRRP for IPv4(VRRP), run the following commands:
1. Run:
system-view

2. Run:


3. Run:
vrrp vrid virtual-router-id virtual-ip virtual-address
A backup group is created and its virtual IP address is specified.
NOTE
l Virtual IP addresses of backup groups must be different.

l Both ends of the same backup group must be configured with the same virtual router IDs.
l Virtual router IDs on different interfaces can be the same.
When you assign the first virtual IP address to a VRRP backup group, the system
creates this backup group. Then, when you assign another virtual IP address to the
backup group, the system adds this address into the virtual IP address list of this backup
group.
For users who require equivalent VRRP reliability, a backup group can be configured
with multiple virtual IP addresses. Different addresses serve different user groups.
This is easy to manage and can prevent users' default gateway addresses from varying
with the VRRP configuration. A maximum number of 16 virtual IP addresses can be
configured for a backup group.
For a VRRP backup working in load balancing mode, you need to repeat the procedure
to configure multiple backup groups on an interface. At least two backup groups are
required on an interface. Backup groups are identified by VRIDs and their virtual IP
addresses cannot be identical.
NOTE
On the NE80E/40E, a maximum number of 255 backup groups can be configured on each
interface.
CAUTION
To configure VRRP and static ARP simultaneously on a device, note that when VRRP
is enabled on an interface such as a sub-interface for Dot1q VLAN tag termination, a
sub-interface for QinQ VLAN tag termination, or a VLANIF interface, you cannot
use the IP addresses mapping to static ARP entries related to these interfaces as the
VRRP virtual addresses. Otherwise, incorrect host routes are generated and abnormal
forwarding of the device may take place.
l For VRRP for IPv6(VRRP6), run the following commands:

1. Run:
system-view

2. Run:

3. Run:
vrrp6 vrid virtual-router-id virtual-ip virtual-ipv6-address [ link-
local ]

A VRRP6 backup group is configured and a virtual IPv6 address is assigned to the
VRRP6 backup group.
NOTE
l Virtual IPv6 addresses of VRRP6 backup groups must be different.

l Virtual router IDs on both ends of a VRRP6 backup group must be the same.
l Virtual router IDs on different interfaces can be the same.
link-local indicates the virtual IPv6 address assigned to a VRRP6 backup group is a
link local address. The link local address is an IPv6 address with the prefix being FE80.
The link local address takes effect only on a local link because it is used by neighboring
nodes along the link to communicate with each other. An IPv6 router never forwards
packets carrying link local addresses. To assign a virtual IPv6 address to a VRRP6
backup group, ensure that the first virtual IPv6 address is a link local address.
After the first virtual IPv6 address is assigned to a VRRP6 backup group, the system
creates the VRRP6 backup group. When another virtual IPv6 address is assigned to
the VRRP6 backup group, the system adds the virtual IPv6 address to the virtual IPv6
address list of the VRRP6 backup group.
In load balancing mode, you need to repeat this step to configure multiple VRRP6
backup groups. At least two VRRP6 backup groups need to be created and each
VRRP6 backup group is identified by a distinct VRID. In addition, virtual IPv6
addresses of VRRP6 backup groups must be different.
If the IP address owner is configured in the IPv6 VRRP configuration, configure

VRRP on the IP address owner first, and then on the peer device; otherwise, the IP
addresses may conflict. If IP address conflict occurs, perform the following
operations:
– Disable the IPv6 address conflict detection.
(1) Before configuring the IP address owner, run the ipv6 nd dad attempts
value command with the value being 0 to disable the IPv6 address conflict
detection.
(2) Configure the IP address owner.
(3) Run the ipv6 nd dad attempts value command with the value being 1 to
enable the IPv6 address conflict detect.
– Restart the interface.
(1) Run the shutdown command in the view of the IP address owner to shut down
the interface.
(2) Run the undo shutdown command in the view of the IP address owner to
enable the interface.
----End
4.2.3 Configuring Priorities for Interfaces Where a Backup Group

Is Created
Configuring priorities for interfaces on which a VRRP backup group is created allows the VRRP
status on an interface to become Master. The master device forwards network traffic.

Context
In master/backup mode, only one backup group is created. routers have different priorities in
this backup group. The router with the highest priority serves as the master and other routers are
backups.
In load balancing mode, two backup groups or more are created. Every router has different
priorities in different backup groups. Every router plays a role based on its priority in a specific
backup group. Different priorities are set for every router to allow that the masters of VRRP
backup groups are distributed on different routers.
Do as follows on the interface of each router in each backup group:
Perform the following step as required to configure VRRP for IPv4 (VRRPv4) or VRRP for
IPv6 (VRRPv6).
Procedure
l For VRRP for IPv4, run the following commands:
1. Run:
system-view

2. Run:

3. Run:
vrrp vrid virtual-router-id priority priority-value
The priority of the router in a VRRP backup group is configured.
By default, the priority is 100. Priority 0 is reserved for special purpose. Priority 255
is reserved for the IP address owner and this priority cannot be configured. A priority
ranges from 1 to 254.
1. Run:
system-view

2. Run:

3. Run:
vrrp6 vrid virtual-router-id priority priority-value
The priority of the router in a VRRPv6 backup group is configured.
By default, the priority is 100. Priority 0 is reserved for special use, and priority 255
is reserved for the IP address owner whose priority cannot be configured. The value
of a priority ranges from 1 to 254.
----End


By viewing the status of a VRRP backup group, you can check whether the configurations are
successful.
Prerequisite
The configurations of the VRRP backup group function are complete.
Procedure
l Run the display vrrp [ interface interface-type interface-number [ virtual-router-id ] ]
[ brief ] command to check the status of VRRP backup group.
l Run the display vrrp6 [ interface interface-type interface-number [ vrid virtual-router-
id ] ] [ brief ] command to check the status and the configurations of the VRRP6 backup
group.
----End
Example
In the master/backup mode, after the configuration, you can run the display vrrp command to
view the status of a VRRP backup group.
<HUAWEI> display vrrp
GigabitEthernet2/0/0 | Virtual Router 1
State : Master
Virtual IP : 10.1.1.111
Master IP : 10.1.1.1
PriorityRun : 120
PriorityConfig : 120
MasterPriority : 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
Config track link-bfd down-number : 0
Create time : 2010-06-22 17:32:56
Last change time : 2010-06-22 17:33:00
In the load balancing mode, after the configuration, you can run the display vrrp command to
view the status of a router in different backup groups.
State : Master
Virtual IP : 10.1.1.111
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES

Create time : 2010-06-21 17:32:56

Last change time : 2010-06-21 17:33:00
State : Backup
Virtual IP : 10.1.1.112
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0102
Check TTL : YES
Create time : 2010-06-18 17:32:56
Last change time : 2010-06-18 17:33:00
After the configuration, run the display vrrp6 command on the router, and you can view
information about the VRRP6 backup group.
<HUAWEI> display vrrp6
State : Master
Virtual IP : FE80::1:2
Master IP : FE80::218:82FF:FED3:2AF1
PriorityRun : 200
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Uncheck hop limit : YES
Accept Mode : ON
Track If : GigabitEthernet3/0/4 priority reduced : 70
IF State : UP
Create time : 2010-06-23 17:32:56
Last change time : 2010-06-23 17:33:00
4.3 Configuring VRRP to Track the Status of an Interface

By configuring a VRRP backup group to track the interface status, you can implement the backup
function when the interface fails.

Before configuring a VRRP backup group to track the interface status, familiarize yourself with
the applicable environment and complete the pre-configuration task of configuring a VRRP
backup group.
VRRP tracking interface status provides the backup function when the interface where the VRRP
backup group resides is faulty or when another interface on the router is faulty.
The method of tracking the status of the interface are as follows:

1. When the tracked interface is Down, the priority of the router in the backup group reduces
by a certain value automatically to be lower than that of other routers in the group.
2. The router with the highest priority becomes the master router and thus the master/backup
switchover of the VRRP backup group is complete.
Before configuring VRRP to track the status of an interface, complete the following tasks:
l Configuring network layer attributes for interfaces to connect the network

l Configuring a VRRP backup group
Data Preparation
To configure VRRP to track the status of an interface, you need the following data.
No. Data
1 Backup group ID
2 Interfaces to be tracked and the values by which the priority increases or decreases
4.3.2 Configuring VRRP to Track the Status of an Interface

By configuring a VRRP backup group to track the interface status, you can implement the fast
VRRP master/backup switchover.
Context
The backup is performed when other interfaces on a router are unavailable.
Do as follows on the router of the tracked interface:
Procedure
1. Run:
system-view

2. Run:

3. Run:
vrrp vrid virtual-router-id track interface interface-type interface-
number [ increased value-increased | reduced value-reduced ]
A interface to be tracked is specified.

– By default, when the tracked interface is Down, the priorities of routers in the
tracking backup group decrease by 10.
– increased value-increased: specifies the value by which the priority increases
when the tracked interface goes Down. The value ranges from 1 to 255. The
maximum value of the priority is 254 because 255 is reserved for only the IP
address owner.
– reduced value-reduced: specifies the value by which the priority decreases when
the tracked interface goes Down. The value ranges from 1 to 255. The lowest
priority is 0.. The priority 0 is reserved in the system for special use. When the
backup device receives a VRRP Advertisement packet with the priority 0, it
immediately switches to be the master device.
– When a VRRP backup group tracks BFD sessions and interfaces concurrently, the
allowable maximum number of tracked BFD sessions and interfaces is eight.
– When a BFD session or an interface tracked by the VRRP backup group goes
Down, the priority of the VRRP backup group may increase or reduce. If it is
configured that the priority always increases every time a BFD session or
interface goes Down, the priority of the VRRP backup group in the Backup
state can exceed that in the Master state when all the tracked BFD sessions or
interfaces go Down.
– If it is configured that the priority does not always increase every time a BFD
session or interface goes Down, as long as one or some BFD sessions or
interfaces go Down, the priority of the VRRP backup group in the Backup state
can exceed that in the Master state, thus triggering VRRP fast switchover. Thus,
the increase of the priority caused by the down of other BFD sessions or
interfaces has no impact on VRRP fast switchover.
NOTE
One router can track up to eight interfaces. When the router is the IP address owner, the
router cannot be configured to track the interface status. At present, the status of the loopback
interface, NULL interface, CPOS interface, and AUX interface cannot be tracked.
1. Run:
system-view

2. Run:

3. Run:
vrrp6 vrid virtual-router-id track interface interface-type interface-
number [ increased value-increased | reduced value-reduced ]
The status of the specified interface is tracked.

– By default, when the tracked interface goes Down, the priority of the tracking
VRRP backup group decreases by 10.
– increased value-increased specifies the value by which the priority increases when
the tracked interface goes Down. The value ranges from 1 to 255. The maximum
value of the priority is 254 because 255 is reserved for only the IP address owner.
– reduced value-reduced specifies the value by which the priority decreases when
the tracked interface goes Down. The value ranges from 1 to 255. The lowest

priority is 0.. The priority 0 is reserved in the system for special use. When the
backup device receives a VRRP Advertisement packet with the priority 0, it
immediately switches to be the master device.
– A VRRP6 backup group is configured to monitor the interface status. When the
monitored interface is configured with an IPv4 address and the status of IPv4
changes, the VRRP6 backup group re-elects the Master; if the monitored interface
is configured with an IPv6 address, when the status of IPv6 changes, the VRRP6
backup group does not re-elect the Master.
----End

By viewing the status of an interface tracked by a VRRP backup group, you can check whether
the configurations are successful.
Prerequisite
The configurations of enabling VRRP to track the status of an interface are complete.
Procedure
[ brief ] command to check the VRRP status.
id ] ] [ brief ] command to check the status and the configurations of a VRRP6 backup
group.
----End
Example
Run the display vrrp command or the display vrrp6 command, and you can view the Track
IF field and the IF State field. The Track IF field indicates the type and number of the tracked
interface, and the IF State field indicates the interface status, which is either Up or Down.
State : Master
Virtual IP : 10.1.1.111
PriorityRun : 130
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Track IF : GigabitEthernet2/0/1 priority reduced : 10
IF State : UP
Create time : 2010-06-22 17:32:56
Last change time : 2010-06-22 17:33:00
State : Master

PriorityRun : 200
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
IF State : UP
Create time : 2010-06-21 17:32:56
Last change time : 2010-06-21 17:33:00
4.4 Configuring a Fast VRRP Switchover (in Common

Mode)
By tracking the BFD session status or the EFM OAM session status, a VRRP backup group
implements VRRP switchovers rapidly.

Before configuring a fast VRRP switchover (in common mode), familiarize yourself with the
applicable environment and complete the tasks of pre-configuring a VRRP backup group and a
BFD session or EFM OAM.
VRRP tracks BFD sessions or EFM OAM. Any change in BFD or EFM sessions are notified to
the VRRP module to trigger a fast VRRP switchover.
A VRRP backup group tracks the following entities:
l Peer BFD session
l Link BFD session
l Normal BFD session
l Interface
A VRRP backup group tracks one peer or link BFD session, multiple normal BFD sessions, or
multiple interfaces.
If the VRRP backup group tracks several BFD sessions, a change in the status of a BFD session
does not affect other BFD sessions's status.
If one of normal BFD sessions tracked by a VRRP backup group changes in status, the master/
backup switchover is triggered by changing priorities of routers in the VRRP backup group.
After the tracked normal BFD session recovers, the priorities of routers in the VRRP backup
group are restored to original values. If either a peer BFD session or a link BFD session tracked
by a VRRP backup group changes in status, the status of the VRRP backup group is changed
directly without changes in priorities.

NOTE
l For detailed information about configuring EFM OAM, see the chapter "Ethernet OAM Configuration"
in the HUAWEI NetEngine80E/40E Router Configuration Guide - Reliability.
l For detailed information about configuring a VRRP backup group to track a peer BFD session, a link
BFD session, or an EFM session, see the chapter "VPLS Convergence Configuration" in the HUAWEI
NetEngine80E/40E Router Configuration Guide - VPN.
Before configuring a fast VRRP switchover, complete the following tasks:

l Configuring basic EFM OAM functions
l Configuring a VRRP backup group
l Configuring BFD sessions such as a normal BFD sessions, a link BFD session, or a peer
BFD session
Data Preparation
To configure a fast VRRP switchover, you need the following data.
No. Data
1 Backup group ID
4.4.2 Tracking the BFD Session Status

By tracking the status of a BFD session, a VRRP backup group can perform a fast VRRP
switchover if the BFD session status changes.
Context
Do as follows on the router that needs to perform a fast VRRP switchover:
NOTE
l Before configuring a fast VRRP switchover, if VRRP tracks a peer BFD session, you must configure
a peer BFD session on both the master router and the backup router in a VRRP backup group. Otherwise,
VRRP flapping occurs.
l If a VRRP backup group is bound to an mVRRP backup group, the VRRP backup group cannot perform
a fast switchover by tracking any BFD session, and the status of the VRRP backup group should be
consistent with the status of the mVRRP backup group.
l When configuring a VRRP backup group to track the status of a BFD session, note the following points:
l If the parameter session-name bfd-configure-name is specified, the VRRP backup group can track
the status of only static BFD sessions with automatically negotiated discriminators.
l If the parameter session-id is specified, the VRRP backup group can track the status of only static
BFD sessions.
Perform the following steps as required on a device enabled with VRRP for IPv4 or for VRRP
for IPv6.

Procedure
l For VRRP for IPv4:
1. Run:
system-view

2. Run:
interface interface-type interface-number[.subinterface-number ]
The view of the interface configured with a VRRP backup group is displayed.
3. Run:
– vrrp vrid virtual-router-id track bfd-session { session-name bfd-
session-id | bfd-configure-name } [ increased value-increased |
reduced value-reduced ]
A normal BFD session is tracked by the VRRP backup group.

increased value-increased: specifies the value by which the priority level increases
if the tracked BFD session goes Down. The value ranges from 1 to 255. The
maximum configurable value of the priority is 254 as 255 is reserved for the IP
address owner.
reduced value-reduced: specifies the value by which the priority level decreases
minimum value of the priority is 1. The priority 0 is reserved in the system for
special use. When the backup device receives a VRRP Advertisement packet with
the priority 0, it immediately becomes the master device. By default, if the tracked
BFD sessions go Down, the value of the priority level decreases by 10.
After configuring the value by which the priority level increases or decreases,
ensure that a backup device in a backup group has a higher priority level than a
master device after the master device's priority has been changed. In this manner,
the VRRP status switches rapidly.
A VRRP backup group can track a maximum of eight BFD sessions and eight
interfaces simultaneously.
state can exceed that in the Master state only when all the tracked BFD sessions
or interfaces go Down.
Or, run:
– vrrp vrid virtual-router-id track bfd-session { bfd-session-id |
session-name bfd-configure-name } [ peer | link ]
The status of a link or peer BFD session is tracked.

When one of the following link BFD sessions is set up, you must run the process-
pst command to allow the BFD session to modify the status in an interface status

table before configuring a VRRP backup group to track the BFD session status.
Otherwise, the link BFD session status tracked by mVRRP is not the same as the
actual session status.
– BFD for static LSP
– BFD for LDP LSP
– BFD for CR-LSP
– BFD for TE
1. Run:
system-view

2. Run:
The view of the interface configured with the VRRP backup group is displayed.
3. Run:
– vrrp6 vrid virtual-router-id track bfd-session { session-id | session-
name bfd-configure-name } [ increased value-increased | reduced value-
reduced ]
The normal BFD session is tracked.

increased value-increased: specifies the value by which the priority increases
when the tracked BFD session goes Down. It is an integer ranging from 1 to 255.
The maximum value of the priority is 254 because 255 is reserved for only the IP
address owner.
reduced value-reduced: specifies the value by which the priority decreases when
the tracked BFD session goes Down. The value is an integer ranging from 1 to
254. The minimum value of the priority is 1. The priority 0 is reserved in the system
for special use. When the backup device receives a VRRP Advertisement packet
with the priority 0, it immediately switches to be the master device. By default, the
value of the priority decreases by 10.
NOTE
When configuring the value by which the priority increases or decreases, note that if the
priority of the Backup router in a backup group is higher than that of the Master router
whose priority is changed, the fast switchover is performed.
name bfd-configure-name } [ peer | link ]

– BFD for LDP LSP
– BFD for CR-LSP
– BFD for TE
----End

4.4.3 Tracking the BFD Session Status

By tracking the status of a BFD session, a VRRP backup group can perform a fast VRRP
switchover if the BFD session status changes.
Context
Do as follows on the router that needs to perform a fast VRRP switchover:
NOTE
l Before configuring a fast VRRP switchover, if VRRP tracks a peer BFD session, you must configure
a peer BFD session on both the master router and the backup router in a VRRP backup group. Otherwise,
VRRP flapping occurs.
l If a VRRP backup group is bound to an mVRRP backup group, the VRRP backup group cannot perform
a fast switchover by tracking any BFD session, and the status of the VRRP backup group should be
consistent with the status of the mVRRP backup group.
BFD sessions.
Perform the following steps as required on a device enabled with VRRP for IPv4 or for VRRP
for IPv6.
Procedure
1. Run:
system-view

2. Run:
The view of the interface configured with a VRRP backup group is displayed.
3. Run:
– vrrp vrid virtual-router-id track bfd-session { session-name bfd-
session-id | bfd-configure-name } [ increased value-increased |
reduced value-reduced ]
A normal BFD session is tracked by the VRRP backup group.

increased value-increased: specifies the value by which the priority level increases
maximum configurable value of the priority is 254 as 255 is reserved for the IP
address owner.
reduced value-reduced: specifies the value by which the priority level decreases
minimum value of the priority is 1. The priority 0 is reserved in the system for
special use. When the backup device receives a VRRP Advertisement packet with
the priority 0, it immediately becomes the master device. By default, if the tracked
BFD sessions go Down, the value of the priority level decreases by 10.
After configuring the value by which the priority level increases or decreases,
ensure that a backup device in a backup group has a higher priority level than a

master device after the master device's priority has been changed. In this manner,
the VRRP status switches rapidly.
A VRRP backup group can track a maximum of eight BFD sessions and eight
interfaces simultaneously.
state can exceed that in the Master state only when all the tracked BFD sessions
or interfaces go Down.
Or, run:
– vrrp vrid virtual-router-id track bfd-session { bfd-session-id |
session-name bfd-configure-name } [ peer | link ]

– BFD for LDP LSP
– BFD for CR-LSP
– BFD for TE
1. Run:
system-view

2. Run:
The view of the interface configured with the VRRP backup group is displayed.
3. Run:
name bfd-configure-name } [ increased value-increased | reduced value-
reduced ]

increased value-increased: specifies the value by which the priority increases
when the tracked BFD session goes Down. It is an integer ranging from 1 to 255.
The maximum value of the priority is 254 because 255 is reserved for only the IP
address owner.
reduced value-reduced: specifies the value by which the priority decreases when
the tracked BFD session goes Down. The value is an integer ranging from 1 to

254. The minimum value of the priority is 1. The priority 0 is reserved in the system
for special use. When the backup device receives a VRRP Advertisement packet
with the priority 0, it immediately switches to be the master device. By default, the
value of the priority decreases by 10.
NOTE
When configuring the value by which the priority increases or decreases, note that if the
priority of the Backup router in a backup group is higher than that of the Master router
whose priority is changed, the fast switchover is performed.
name bfd-configure-name } [ peer | link ]

– BFD for LDP LSP
– BFD for CR-LSP
– BFD for TE
----End
4.4.4 Tracking the Status of the SPU Group

By tracking the status of the SPU group, you can enable VRRP to adjust the priorities according
to the status of the SPU group so that the master/backup switchover is performed.
Context
Do as follows on each router in a VRRP backup group.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
vrrp vrid virtual-router-id track spu-group spu-group-number reduced value-reduced
The status of the SPU group is tracked by VRRP.
----End


By viewing the status of a BFD session or an EFM OAM session tracked by a VRRP backup
group, you can check whether the configurations are successful.
Prerequisite
The configurations of the VRRP fast switchover function are complete.
Procedure
command to check the status of VRRP.
id ] ] [ brief ] command to view status and parameters of the VRRP6 backup group.
----End
Example
Run the display vrrp command, and you can view that the BFD session that is tracked by VRRP
is Up. The command output is as follows:
GigabitEthernet1/0/0.3 | Virtual Router 1
State : Backup
Virtual IP : 192.168.1.100
Master IP : 192.168.1.1
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Check TTL : YES
Track BFD : 1 Priority increased : 20
BFD-session state : Up
Create time : 2010-06-22 17:32:56
Last change time : 2010-06-22 17:33:00

State : Backup
Virtual IP : 192.168.2.254
Master IP : 192.168.2.1
PriorityRun : 100
Preempt : yes Delay time : 0
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Check TTL : YES
Config type : admin-vrrp
Track EFM : GigabitEthernet2/0/0
EFM state : up
Track BFD : 2 type : peer
BFD-session state : up
Create time : 2010-06-23 17:32:56
Last change time : 2010-06-23 17:33:00


State : Master
Virtual IP : 192.168.1.254
Master IP : 192.168.1.2
PriorityRun : 120
Preempt : yes Delay time : 0
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Check TTL : YES
Track BFD : 4 type : link
Create time : 2010-06-24 17:32:56
Last change time : 2010-06-24 17:33:00
State : Master
PriorityRun : 200
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
IF State : UP
BFD6-session state : up
Create time : 2010-06-25 17:32:56
Last change time : 2010-06-25 17:33:00
4.5 Configuring VRRP Fast Switchover (Using BFD

Sampling)
By configuring a BFD session in BFD sampling mode, you can address the problem that a link

Before configuring the fast VRRP switchover through BFD sampling, 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.
The VRRP backup group implements master/backup switchover by tracking the BFD session
status. However, this method does not work in some special network environments or when the
device does not support the BFD function.

As shown in Figure 4-2, the CE connects to the sub-interface for QinQ VLAN tag termination
of the NPE across the VPLS convergence network.
On the NPE, the mVRRP backup group and the service VRRP backup group are configured and
the mVRRP backup group implements VRRP fast switchover by tracking the BFD session.
Between NPE1 and NPE2, the peer BFD session is established. In this networking, however,
VRRP fast switchover does not work because of the following causes:
l The VPLS convergence network belongs to another operator, so the link BFD session
cannot be established between NPE1 and PE1 or between NPE2 and PE2.
l PE1 or PE2 does not support the BFD function.
In this case, you can use the BFD sampling mode to implement VRRP fast switchover.
In BFD sampling mode, the NPE establishes multiple link BFD sessions directly with each CE
rather than with the PE.
Thus, the mVRRP backup group can implement master/backup switchover by tracking multiple
link BFD sessions between the NPE and the CE, although it cannot track the BFD session
between the NPE and the PE.
Figure 4-2 Typical networking of VRRP fast switchover (using BFD sampling)
Access VPLS convergence

Core
network
IP:10.100.1.1/24
GW:10.100.1.200
Inner VLAN:110
Outer VLAN: 10
CE1
NPE1
CE2
IP:10.101.1.1/24
GW:10.101.1.200
Inner VLAN:210
PE1
Outer VLAN: 10 Link BFD Peer MPLS/IP Core
BFD
PE2
CE3
IP:10.102.1.1/24
GW:10.102.1.200
Inner VLAN:310 NPE2
Outer VLAN: 10
CE4
IP:10.103.1.1/24
GW:10.103.1.200
Inner VLAN:410
Outer VLAN: 10

Before configuring VRRP fast switchover using BFD sampling, complete the following tasks:
l Configuring network layer attributes for interfaces to ensure network connectivity
l Configuring VRRP backup groups, including service VRRP backup groups and mVRRP
backup groups
l Configuring BFD sessions, including link BFD sessions and peer BFD sessions (It is
required to configure BFD sessions between the PE and each CE.)
Data Preparation
To configure VRRP fast switchover using BFD sampling, you need the following data.
No. Data
1 Virtual Router IDs (VRIDs) and virtual IP addresses
2 Priorities of VRRP backup groups
3 Local and remote discriminators of BFD sessions
4.5.2 Binding the Service VRRP Backup Group to the mVRRP

Backup Group
Through the bindings between member VRRP backup groups and the mVRRP backup group,
the state machines of member VRRP backup groups can be consistent with the state machine of
the mVRRP backup group.
Context
Do as follows on the device that need perform VRRP fast switchover:
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the interface where the service VRRP backup group is configured is displayed.
Step 3 Run:
vrrp vrid virtual-router-id1 track admin-vrrp interface interface-type interface-
number vrid virtual-router-id2
The service VRRP backup group is bound to the mVRRP backup group.
After the binding, the state machine of the service VRRP backup group becomes dependent.
That is, the service VRRP backup group deletes the protocol timer and stops sending or receiving

VRRP packets. Alternatively, it implements its state machine by directly copying the status of
the mVRRP back group. A service VRRP backup group can be bound to only one mVRRP
backup group.
NOTE
Only a single member VRRP backup group can be configured on a single interface.
----End
4.5.3 Configuring an mVRRP Backup Group to Track the BFD

Session Status
By tracking the status of a BFD session, a VRRP backup group can perform the fast VRRP
switchover when the BFD session status changes.
Context
Do as follows on a router that needs the fast VRRP switchover:
NOTE
l When configuring a fast VRRP switchover, if VRRP monitors the peer BFD session, you must
configure peer BFD sessions on both the master router and the backup router. Otherwise, VRRP
flapping occurs.
l When a VRRP backup group is bound to the mVRRP backup group, the VRRP backup group cannot
perform the fast switchover bytracking any BFD session, and the status of the VRRP backup group
should be consistent with the status of the mVRRP backup group.
BFD sessions.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The view of the interface configured with VRRP backup group is displayed.
Step 3 Run the following commands are required:

l Run:
vrrp vrid virtual-router-id track bfd-session { bfd-session-id | session-name
bfd-configure-name } [ increased value-increased | reduced value-reduced ]

increased value-increased: specifies the value by which the priority increases each time the
tracked BFD session goes Down. The value ranges from 1 to 255. The maximum value of
the priority is 254. The value takes effect only when the status of the VRRP backup group
is Backup.

reduced value-reduced: specifies the value by which the priority decreases each time the
tracked BFD session goes Down. The value ranges from 1 to 255. The lowest priority is 1.
The default value is 10.
When configuring the value by which the priority increases or decreases, especially the
default value, ensure that the priority of the backup router in a backup group is higher than
that of the master router whose priority is changed. In this manner, the VRRP status can be
switched rapidly.
When a VRRP backup group monitors both BFD sessions and interfaces, the maximum
number of BFD sessions and interfaces is eight. If increased value-increased is specified,
the value of the increased VRRP backup group priority will exceed the priority of the master
VRRP backup group only when all the tracked BFD sessions or interfaces go Down.
Otherwise, if the VRRP backup group takes precedence of the peer because its priority is
increased when one or some tracked BFD sessions or interfaces go Down, the additional
increasing of the priority is of no significance when other BFD sessions or interfaces go
Down.
Or, run:
l vrrp vrid virtual-router-id track bfd-session { bfd-session-id | session-name

bfd-configure-name } [ peer | link ]

If one of the following types of link BFD is used, you must run the process-pst command
to allow the BFD session to modify the port status table (PST). Otherwise, the link BFD
session status monitored by mVRRP is not the same as the actual session status.
– BFD for LDP LSP
– BFD for CR-LSP
– BFD for TE
In this scenario, the NPEs establish the peer BFD session between each other but the NPE does
not establish the link BFD session with the PE; instead, the NPE establishes multiple link BFD
sessions directly with each CE. By tracking the BFD session status, the NPE implements fast
master/backup switchover.
----End
4.5.4 Setting the Threshold for VRRP Fast Switchover

The VRRP backup group can perform the fast switchover according to the set number of the
tracked link BFD sessions that go Down.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the interface where the mVRRP backup group is configured is displayed.
Step 3 Run:
vrrp vrid virtual-router-id track link-bfd down-number down-number
The threshold of VRRP fast switchover is set.

Among the link BFD sessions tracked by the mVRRP backup group, when the number of
sessions in the Down state reaches or exceeds this threshold, the mVRRP backup group performs
master/backup fast switchover.
----End
4.5.5 Enabling the Association Between the mVRRP Backup Group

Status and the Route
By configuring the association between the VRRP status and the route, you can address the
problem that uplink traffic is inconsistent with downlink traffic.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
Step 3 Run:
vrrp trigger route
The association between the mVRRP backup group status and the route is enabled.
At present, multiple VRRP backup groups can be configured on an interface and thus different
statuses of VRRP backup groups coexist. Hence, after the association between the VRRP backup
group status and the route is enabled, it is recommended that only one VRRP backup group be
configured on an interface to avoid the chaotic route status.

NOTE
In the scenario where the association between the VRRP backup group and the route is enabled:
l For the sub-interface for QinQ VLAN tag termination and VLANIF interface:
l When the status of the VRRP backup group becomes Initialize, the device deletes the network
segment route and remote host route of the interface where the VRRP backup group is configured.
l When the status of the VRRP backup group becomes Master, the device advertises the network
l For other types of interfaces:
segment route of the interface where the VRRP backup group is configured.
----End

By viewing the threshold of BFD sessions in the Down state tracked by an mVRRP backup
group and the switchover of VRRP backup groups, you can check whether the configurations
are successful.
Prerequisite
All configurations of VRRP fast switchover using BFD sampling are complete.
Procedure
command to view the status of the VRRP backup group.
----End
Example
Run the display vrrp command. The command output shows that the status of the BFD session
tracked by the mVRRP backup group is Up and the threshold of VRRP fast switchover is 2.
[HUAWEI] display vrrp interface gigabitethernet1/0/1.1
State : Master
Virtual IP : 10.1.1.1
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-010a
Check TTL : YES
Track BFD : link1 type: link
BFD-session state : UP
Track BFD : peer1 type: peer


Create time : 2010-06-22 17:32:56
Last change time : 2010-06-22 17:33:00
4.6 Configuring Ignorance of the Down of an Interface

Where the mVRRP Backup Group Is Configured
By configuring mVRRP with the function of ignoring the interface Down event, you can resolve
the problem that mVRRP and a peer BFD session cannot be configured between NPEs.

Before configuring mVRRP with the function of ignoring the interface Down event, 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.
VRRP defines three status types: Initialize, Master, and Backup. On being notified that the
interface is shut down, the VRRP backup group switches its status to Initialize.
the mVRRP backup group is responsible for tracking the BFD session to implement VRRP fast
switchover. Between NPE1 and NPE2, the peer BFD session is established. In this networking,
however, VRRP fast switchover may not work because of the following causes:
l In the VPLS convergence network, the PW is established only between PE1 and PE3 and
between PE2 and PE3. According to the VPLS split horizon rule, the mVRRP backup group
and the peer BFD session cannot be established between NPE1 and NPE2.
cannot be established between NPE1 and PE1 or between NPE2 and PE2.
In this scenario, you can use the function of ignorance of interface down of the mVRRP backup
group to implement VRRP fast switchover.
NPE1 and NPE2 establish the mVRRP backup group and peer BFD session through a direct link
rather than the VPLS convergence network.
Thus, when the interface where the mVRRP backup group is configured goes Down, the status
of the mVRRP backup group is switched to Master rather than Initialize.
NOTE
In practical networking, NPE1 and NPE2 establish the mVRRP backup group and peer BFD session through
the direct link rather than their respective interfaces connecting to the VPLS convergence network.
Therefore, the cross-board Eth-Trunk link is recommended between NPE1 and NPE2 to ensure the
reliability of the status of the mVRRP backup group and peer BFD session.

Figure 4-3 Typical networking of ignorance of the down of an interface where the mVRRP
backup group is configured
VPLS convergence
Access Core
network
CE1
Horizontal split
NPE1
CE2
PE1
PW Peer Admin MPLS/IP

BFD VRRP Core
PW
CE3
PE3
PE2
NPE2
CE4
Before configuring ignorance of the down of an interface where the mVRRP backup group is
configured, complete the following tasks:
l Configuring network layer attributes for interfaces to ensure network connectivity

l Configuring VRRP backup groups, including the service VRRP backup groups and the
mVRRP backup group
l Configuring BFD sessions, including the link BFD sessions and the peer BFD session (It
is required to configure Link BFD sessions between the PE and each CE.)
Data Preparation
To configure ignorance of the down of an interface where the mVRRP backup group is
configured, you need the following data.
No. Data
1 VRRP Virtual Router IDs (VRIDs) and virtual IP addresses
2 Priorities of VRRP backup groups

No. Data
3 Local and remote discriminators of BFD sessions
4.6.2 Configuring the mVRRP Backup Group

Context
Do as follows on the router where the mVRRP backup group is configured:
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface interface-type interface-number [.subinterface-number ]
Step 3 Run:
A VRRP backup group is created, and a virtual IP address is assigned to the VRRP backup group.
Step 4 Run:
The priority of the VRRP backup group is configured.
Step 5 Run:
admin-vrrp vrid virtual-router-id ignore-if-down
This VRRP backup group is configured as an mVRRP backup group.
In the scenario as shown in Figure 4-3, if NPE is not faulty, it is not recommended to shut down
the direct link between NPE1 and NPE2. Otherwise, the mVRRP backup groups on NPE1 and
NPE2 both become Master, causing service interruption.
In all networking environments except the scenario as shown in Figure 4-3, it is not
recommended to enable the function of ignorance of interface down of the mVRRP backup
group. Otherwise, the state machine of the VRRP backup group is inconsistent with that defined
in the RFC.
----End

4.6.3 Binding the Service VRRP Backup Group to the mVRRP

Backup Group
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
vrrp vrid virtual-router-id1 track admin-vrrp interface interface-type interface-
number vrid virtual-router-id2
The service VRRP backup group is bound to the mVRRP backup group.
After the binding, the state machine of the service VRRP backup group becomes dependent.
That is, the service VRRP backup group deletes the protocol timer and stops sending or receiving
VRRP packets. Alternatively, it implements its state machine by directly copying the status of
the mVRRP back group. A service VRRP backup group can be bound to only one mVRRP
backup group.
NOTE
----End
4.6.4 Configuring an mVRRP Backup Group to Track the BFD

Session Status
By tracking the status of a BFD session, a VRRP backup group can perform the fast VRRP
switchover when the BFD session status changes.
Context
Do as follows on a router that needs the fast VRRP switchover:

NOTE
l When configuring a fast VRRP switchover, if VRRP monitors the peer BFD session, you must
configure peer BFD sessions on both the master router and the backup router. Otherwise, VRRP
flapping occurs.
l When a VRRP backup group is bound to the mVRRP backup group, the VRRP backup group cannot
perform the fast switchover bytracking any BFD session, and the status of the VRRP backup group
should be consistent with the status of the mVRRP backup group.
BFD sessions.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the interface configured with VRRP backup group is displayed.
Step 3 Run the following commands are required:
l Run:
vrrp vrid virtual-router-id track bfd-session { bfd-session-id | session-name
bfd-configure-name } [ increased value-increased | reduced value-reduced ]

increased value-increased: specifies the value by which the priority increases each time the
tracked BFD session goes Down. The value ranges from 1 to 255. The maximum value of
the priority is 254. The value takes effect only when the status of the VRRP backup group
is Backup.
reduced value-reduced: specifies the value by which the priority decreases each time the
tracked BFD session goes Down. The value ranges from 1 to 255. The lowest priority is 1.
The default value is 10.
When configuring the value by which the priority increases or decreases, especially the
default value, ensure that the priority of the backup router in a backup group is higher than
that of the master router whose priority is changed. In this manner, the VRRP status can be
switched rapidly.
When a VRRP backup group monitors both BFD sessions and interfaces, the maximum
number of BFD sessions and interfaces is eight. If increased value-increased is specified,
the value of the increased VRRP backup group priority will exceed the priority of the master
VRRP backup group only when all the tracked BFD sessions or interfaces go Down.
Otherwise, if the VRRP backup group takes precedence of the peer because its priority is
increased when one or some tracked BFD sessions or interfaces go Down, the additional
increasing of the priority is of no significance when other BFD sessions or interfaces go
Down.
Or, run:
l vrrp vrid virtual-router-id track bfd-session { bfd-session-id | session-name
bfd-configure-name } [ peer | link ]


If one of the following types of link BFD is used, you must run the process-pst command
to allow the BFD session to modify the port status table (PST). Otherwise, the link BFD
session status monitored by mVRRP is not the same as the actual session status.
– BFD for LDP LSP
– BFD for CR-LSP
– BFD for TE
In this scenario, the NPEs establish the peer BFD session between each other but the NPE does
not establish the link BFD session with the PE; instead, the NPE establishes multiple link BFD
sessions directly with each CE. By tracking the BFD session status, the NPE implements fast
----End
4.6.5 Setting the Threshold for VRRP Fast Switchover

The VRRP backup group can perform the fast switchover according to the set number of the
tracked link BFD sessions that go Down.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
vrrp vrid virtual-router-id track link-bfd down-number down-number
The threshold of VRRP fast switchover is set.
Among the link BFD sessions tracked by the mVRRP backup group, when the number of
sessions in the Down state reaches or exceeds this threshold, the mVRRP backup group performs
master/backup fast switchover.
----End
4.6.6 Enabling the Association Between the mVRRP Backup Group

Status and the Route
By configuring the association between the VRRP status and the route, you can address the
problem that uplink traffic is inconsistent with downlink traffic.

Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
Step 3 Run:
vrrp trigger route
The association between the mVRRP backup group status and the route is enabled.
At present, multiple VRRP backup groups can be configured on an interface and thus different
statuses of VRRP backup groups coexist. Hence, after the association between the VRRP backup
group status and the route is enabled, it is recommended that only one VRRP backup group be
configured on an interface to avoid the chaotic route status.
NOTE
In the scenario where the association between the VRRP backup group and the route is enabled:
l For the sub-interface for QinQ VLAN tag termination and VLANIF interface:
l For other types of interfaces:
----End

By viewing the threshold of BFD sessions in the Down state tracked by an mVRRP backup
group and the switchover of VRRP backup groups, you can check whether the configurations
are successful.
Prerequisite
All configurations of VRRP fast switchover using BFD sampling are complete.
Procedure
command to view the status of the VRRP backup group.
----End

Example
Run the display vrrp command. The command output shows that the status of the BFD session
tracked by the mVRRP backup group is Up and the threshold of VRRP fast switchover is 2.
[HUAWEI] display vrrp interface gigabitethernet1/0/1.1
State : Master
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Check TTL : YES
Create time : 2010-06-22 17:32:56
Last change time : 2010-06-22 17:33:00
4.7 Configuring VRRP Applications in VLANIF

By configuring a VRRP backup group on VLANIF interfaces, you can perform the fast VRRP
switchover.

Before configuring a VRRP backup group on VLANIF interfaces, familiarize yourself with the
VLANIF supports VRRP functions.
Before configuring VRRP on the VLANIF interface, complete the followings tasks:

l Configuring sub-VLAN
l Configuring super-VLAN

Data Preparation
To configure VRRP on the VLANIF interface, you need the following data.
No. Data
1 Super-VLAN ID
2 Sub-VLAN ID
3 Backup group ID
4.7.2 Configuring VRRP on VLANIF

By creating a VRRP backup group on VLANIF interfaces, you can use the standby VLANIF
interface to take over network traffic when the active VLANIF interface goes Down.
Context
Do as follows on a router on which VRRP runs on the VLANIF interface:
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface vlanif vlan-id
The VLANIF interface view is displayed.
Step 3 Run:
Step 4 Run:
The priority of the router in the backup group is configured.
----End
4.7.3 (Optional) Configuring the Sending Mode of VRRP Packets

in Super-VLAN
You can configure the sending mode of VRRP advertisement packets for a super VLAN on
VLANIF interfaces as required.

Context
Do as follows on a VRRP router that is configured with a super-VLAN:
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface vlanif vlan-id
The VLAN interface view is displayed.

Step 3 Run:
vrrp advertise send-mode { sub-vlan-id | all }
The sending mode of VRRP advertising messages is configured.

By default, the super-VLAN does not send advertisement messages to its sub-VLANs.
----End

successful.
Prerequisite
The configurations of the VRRP applications in VLANIF are complete.
Procedure
Step 1 Run the display vrrp [ interface interface-type interface-number [ virtual-router-id ] ]
----End
Example
After the configuration, run the display vrrp interface vlanif command, and you can view the
VRRP status on the VLANIF interface.
<HUAWEI> display vrrp interface vlanif 40
Vlanif40 | Virtual Router 1
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

Create time : 2010-06-22 17:32:56
Last change time : 2010-06-22 17:33:00
4.8 Configuring VRRP Security

On a network at security risks, by configuring an authentication mode of VRRP packets, you
can protect devices against attacks.

Before configuring VRRP security authentication, familiarize yourself with the applicable
environment and complete pre-configuration task of configuring a VRRP backup group.
In a secure network, by default, the router considers received and sent VRRP packets real and
valid without authenticating them. In this case, you need not configure an authentication key.
VRRP provides simple text authentication and MD5 authentication for networks that are
vulnerable to attacks. In simple text authentication mode, a string of 1 to 8 characters can be
configured as the authentication key. In MD5 authentication mode, a string of 1 to 8 characters
in plain text or a string of 24 characters in encrypted text can be configured as the authentication
key.
The process of simple text authentication is as follows:

l Device that sends packets adds the authentication key into VRRP packets.
l Device that receives packets compares the received authentication key with the local
authentication key. If they are the same, VRRP packets are valid. Otherwise, the router
discards the received VRRP packets and sends a Trap packet to the Network Management
System (NMS).
The process of MD5 authentication is as follows:

l The router adds the authentication key to the VRRP packet.
l The receiver generates a summary based on the locally configured authentication key and
compares the summary of the received VRRP packet with the locally generated summary.
If they are the same, the receiver considers the received VRRP packet valid. Otherwise,
the receiver considers the received VRRP packet illegal and discards it, and then reports a
trap message to the network management system.
Before configuring the VRRP security function, complete the following tasks:

l Configuring the VRRP backup group
Data Preparation
To configure the VRRP security function, you need the following data.

No. Data
1 Backup group ID
3 Authentication key of the VRRP packet
4.8.2 Configuring the Authentication Mode of VRRP Packets

VRRP packets can be authenticated in simple text mode or MD5 mode.
Context
Do as follows on the router that needs to be configured with an authentication mode for VRRP
packets:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:

Step 4 (optional) Run:
The priority of the router in the backup group is configured.

Step 5 Run:
vrrp vrid virtual-router-id authentication-mode { simple key | md5 md5-key }
The authentication mode for VRRP packets is configured.

The authentication key on the master device must be the same as the authentication key on the
backup device.
The devices in a VRRP backup group must be configured with the same authentication mode;
otherwise, the negotiation between the master and backup routers cannot succeed.
Characters ^#^# and $@$@ are used to identify passwords with variable lengths. Characters
^#^# are the prefix and suffix of a new password, and characters $@$@ are the prefix and suffix
of an old password. Neither of them can be both configured at the beginning and end of a plain
text password.
----End


By viewing the authentication mode and authentication key of VRRP packets, you can check
Prerequisite
The configurations of the VRRP security function are complete.
Procedure
----End
Example
After the configuration, run the display vrrp command, and you can view the mode of the packet
authentication.
State : Master
Virtual IP : 10.1.1.111
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : MD5 Auth key : >6M*PO438G/Q=^Q`MAF4<1!!
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Create time : 2010-06-22 17:32:56
Last change time : 2010-06-22 17:33:00
According to the preceding command output, the Auth Type field displays MD5, and the Auth
key field displays >6M*PO438G/Q=^Q`MAF4<1!!. That is, VRRP backup group 1 adopts
MD5 authentication, and the authentication key is >6M*PO438G/Q=^Q`MAF4<1!!.
4.9 Configuring VRRP Smooth Switching

By configuring smooth VRRP switching, you can address the problem of traffic loss due to the
AMB/SMB switchover.

Before configuring VRRP smooth switching, 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.

In the network where VRRP backup groups are configured, the backup router switches to the
master router because the original master router and backup router cannot communicate in time
when the original master router performs the AMB/SMB switchover. After the AMB/SMB
switchover, the original master router preempts to be the master router again because its priority
is higher than the priority of the original backup router.
Because the system is too busy during the switchover, the master router cannot send Hello
packets normally and the backup router cannot receive packets timely. In this case, the backup
router preempts to be the master router. Then, the link switchover is performed and this causes
packet loss.
Enabling VRRP smooth switching on a router can optimize the VRRP performance and reduce
the impact on the user traffic.
None.
Data Preparation
To configure VRRP smooth switching, you need the following data.
No. Data
1 Interval for the master router to send VRRP packets during VRRP smooth switching
4.9.2 Configuring VRRP Smooth Switching

After being enabled with smooth switching, a VRRP backup group performs the learning
function prior to the preemption function. This avoids switching the VRRP backup group status,
and thus traffic cannot be affected.
Context
Do as follows on the router of a VRRP backup group:
Procedure
Step 1 Run:
vrrp timer-advertise learning enable
The function of learning the interval for receiving VRRP packets is enabled.
By default, this function is enabled.
Step 2 Run:
vrrp smooth-switching timer timer-value
VRRP smooth switching is enabled, and the interval carried in the VRRP packet during VRRP
smooth switching is configured.

By default, VRRP smooth switching is enabled, and the interval carried in the VRRP packet is
100 seconds.
Before running the command, you must enable the function of learning the interval for receiving
VRRP packets. When the learning function is disabled, VRRP smooth switching is also disabled.
NOTE
l If the interval set by the master router for sending VRRP broadcast packets is much greater than the
interval set by the backup router, the backup router resets the "masterdown" time after the backup
router is restarted and the interface recovers. The master router may not send packets after the
"masterdown" time of the backup router expires. In this case, the backup router becomes the master
router. As a result, two master routers exist.
l During the AMB/SMB switchover, the master router sends VRRP smooth switching packets at the
configured interval. If the time configured by the master router for VRRP smooth switching, such as
1s, is shorter than the configured interval for sending VRRP broadcast packets, such as 10s, VRRP
packets are sent at the interval of 10s, and the interval carried in the VRRP packet is 1s. As a result,
the status of the backup router continuously flaps.
----End

successful.
Prerequisite
The configurations of the VRRP smooth switching function are complete.
Procedure
command to check the status of the VRRP backup group.
----End
Example
After configuring VRRP smooth switching, perform the AMB/SMB switchover on the device.
During the AMB/SMB switchover, the status of the VRRP backup group does not switch, and
thus the user traffic is not affected. After the AMB/SMB switchover, all VRRP configurations
of the new AMB are consistent with those of the original AMB.
State : Master
Virtual IP : 10.10.10.158
Master IP : 10.10.10.1
PriorityRun : 180
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES

Create time : 2010-06-22 17:32:56

Last change time : 2010-06-22 17:33:00
4.10 Adjusting and Optimizing VRRP

By adjusting parameters of a VRRP backup group, you can optimize the functions of the VRRP
backup group.

Before optimizing VRRP functions, familiarize yourself with the applicable environment and
complete pre-configuration task of configuring a VRRP backup group.
You can configure the related parameters of VRRP packets to optimize the functions of backup
groups.
l By increasing the interval for sending VRRP advertisement packets by the backup group,
you can reduce the network load caused by negotiation packets.
l In VRRP for IPv4, the members in a VRRP backup group are configured with the same
interval for sending VRRP packets, which prevents multiple backup routers from being
switched to master routers simultaneously in one VRRP backup group.
l Configurations of intervals for sending VRRP packets affect the master router election
differently in VRRP for IPv4 and VRRP6 as follows:
– In VRRP for IPv4, the members in a VRRP backup group are configured with the same
interval for sending VRRP packets, which prevents multiple backup routers from being
switched to master routers simultaneously in one VRRP backup group.
– In VRRP6, only can one master router work in a VRRP6 backup group in spite of the
fact that members are configured with different intervals for sending VRRP packets.
l By configuring the preemption mode and preemption delay time of the router in the backup
group, you can increase or reduce the speed of the master/backup switchover.
l By enabling the test on the reachability of the virtual IP address, you can ping the virtual
IP address to check the network connectivity.
l By prohibiting the system from checking number of hops in VRRP packets, you can
improve the compatibility of Huawei routers with different vendors' routers.
Before adjusting and optimizing VRRP, complete the following tasks:
l Configuring network layer attributes for interfaces to connect to the network

l Configuring the VRRP backup group
Data Preparation
To adjust and optimize VRRP, you need the following data.

No. Data
1 Interval for sending VRRP advertisement packets
2 Preemption delay of the routers in the backup group
3 Timeout period for the master to send gratuitous ARP packets
4.10.2 Configuring the Interval for Sending VRRP Advertising

Messages
By prolonging the interval for sending VRRP advertisement packets on a virtual router, you can
reduce the network load.
Context
The master router sends VRRP advertisement packets at intervals to other backup routers. If the
backup routers do not receive VRRP advertising messages when the timer times out, the backup
router with the highest priority becomes the master router automatically.
Do as follows on the router to adjust the interval for sending VRRP advertisement packets:
Procedure
1. Run:
system-view

2. Run:

3. Run:
The interval for sending VRRP advertisement packets is configured.
By default, the interval for sending VRRP advertisement packets is 1 second. When
multiple backup groups exist, sending VRRP advertisement packets at very short
intervals may lead to frequent VRRP switchover. In this case, you can increase the
interval.
l For VRRP6, run the following commands:
1. Run:
system-view

2. Run:


3. Run:
vrrp6 vrid virtual-router-id timer advertise advertise-interval
The interval for sending VRRP6 advertisement packets is configured for the master
router.
By default, the interval is 100 centiseconds, namely, 1 second.
----End
4.10.3 Configuring the Preemption Delay Time of Backup Group

Router s
By setting the preemption delay time of routers in a VRRP backup group, you can speed up or
slow the master/backup switchover.
Context
Do as follows on the VRRP backup router of which the latency of preemption needs to be
adjusted:
Procedure
1. Run:
system-view

2. Run:

3. Run:
vrrp vrid virtual-router-id preempt-mode timer delay delay-value
The preemption delay of routers in the backup group is configured.

By default, the preemption mode is adopted and the delay period is 0, indicating
immediate preemption. In immediate preemption mode, the backup router becomes
the new master router when its priority is higher than that of the current master
router. The original master router becomes a backup router. After the preemption delay
period is set, the backup router is delayed to preempt the master router.
Run the vrrp vrid virtual-router-id preempt-mode disable command to configure
routers in the backup group with the non-preemption mode. In the non-preemption
mode, if a router in the backup group becomes the master router and works normally,
other routers do not become the master router even if they are configured with higher
priorities later.
After the IP address owner recovers from a fault, it switches to be the master router
immediately in spite of the preemption delay. The preemption delay refers to a delay
period for the backup router to be switched to be the master router. The preemption

delay is unavailable for the IP address owner. For the VRRP backup group that needs
to support the preemption delay, the master virtual router cannot be configured as the
IP address owner.
Run the undo vrrp vrid virtual-router-id preempt-mode command to restore the
default preemption mode.
NOTE
On each router to be configured with a delay mode in a VRRP backup group, it is recommended
to configure backup routers with the immediate preemption mode (whose delay time is 0
seconds) and configure the master router with the preemption mode (whose delay time is
specified). Configuring the delay time for the master router can ensure that the original primary
link has enough time to restore and work stably, and then switch back. At the same time, the
backup link works normally. If the data is switched back to the original primary link, the
application is not affected.
l For VRRP6, run the following commands:
1. Run:
system-view

2. Run:

3. Run:
vrrp6 vrid virtual-router-id preempt-mode timer delay delay-value
The delay time of preemption is configured on the router in the VRRP6 backup group.
By default, the preemption mode is enabled and the delay time of preemption is 0
seconds, indicating immediate preemption. In immediate preemption mode, a backup
router becomes the master router when detecting that its priority is higher than the
priority of the master router. Then, the original master router becomes a backup router.
After the delay time of preemption is set, a backup router can be delayed for a specified
period to preempt the master router.
You can run the vrrp6 vrid preempt-mode disable command to adopt the non-
preemption mode on the router of the VRRP6 backup group. In non-preemption mode,
after a certain router becomes the master router in the backup group and works
normally, another router cannot preempt the master router even if its priority is set to
a value higher than that of the master router.
When the IPv6 address owner recovers from a fault, the router immediately becomes
the master router despite the set delay time. The preemption delay refers to a period
during which a backup router waits for preempting the master router, whereas an IPv6
address owner is irrelevant to the preemption delay. In a VRRP6 backup group that
needs to be configured with the preemption delay, the master router cannot be
configured as the IPv6 address owner.
You can run the undo vrrp6 vrid preempt-mode command to restore the default
preemption mode.

NOTE
To configure the preemption mode for each router in a VRRP6 backup group, you are
recommended to configure the immediate preemption mode on each backup router by setting
the delay time to 0 seconds, and configure the delayed preemption mode on the master router
by setting a delay time. This allows a transition period for the uplink status and the downlink
status to restore consistency on an unstable network, and thus prevents user devices from
learning the incorrect address of the master router due to dual master routers or frequent
preemption.
----End
4.10.4 Enabling the Reachability Test of the Virtual IP Address

By enabling the reachability test of a virtual IP address, you can use the ping function to detect
network reachability.
Context
In the NE80E/40E, you can ping the virtual IP address to check the following items:
l Whether the master router in the backup group is available.
l Whether the internal user can access external networks through the virtual IP address that
serves as the default gateway.
Do as follows on the router that needs to be enabled with a reachable virtual IP address:
Procedure
Step 1 Run:
system-view

Step 2 Run:
vrrp virtual-ip ping enable
Testing reachability of a virtual address is enabled.

By default, the ping function is enabled. The master router responds to ping packets to the virtual
IP address of this backup group.
Pinging a virtual address may cause ICMP attacks. To prevent this, you can run the undo vrrp
virtual-ip ping enable command to disable the function of testing reachability of a virtual IP
address.
----End
4.10.5 Disabling a Router from Checking Number of Hops in VRRP

Packets
By prohibiting the check of TTLs in VRRP packets, you can improve compatibility between
devices of different vendors.
Context
Defined in RFC 3768, the system detects number of hops in received VRRP packets. The packets
whose number of hops is not 255 are discarded.

In certain networking environments where Huawei devices and non-Huawei devices work
together, checking the number of hops in VRRP packets may result in discarding VRRP packets
incorrectly. You can disable the system from checking the number of hops in VRRP packets.
Do as follows on the router that is prohibited from checking the number of hops of VRRP packets:
Perform the following step as required to configure VRRP for IPv4 or VRRP6.
Procedure
l For VRRP for IPv4,
1. Run:
system-view

2. Run:

3. Run:
vrrp un-check ttl
Checking TTLs in VRRP packets is disabled.

By default, TTLs in VRRP packets are detected. You can run the undo vrrp un-check
ttl command to enable the router to check TTLs in VRRP packets.
l For VRRP6,
1. Run:
system-view

2. Run:

3. Run:
vrrp6 un-check hop-limit
Checking the hop limit in VRRP6 packets is disabled.

By default, the hop limit in VRRP6 packets is checked. You can run the undo vrrp6
un-check hop-limit command to enable the router to check the hop limit in VRRP6
packets.
----End
4.10.6 Configuring the Timeout Time of Sending Gratuitous ARP

Packets by the Master router
By adjusting the interval for sending gratuitous ARP packets on the master device, you can
reduce the number of VRRP packets on the network.
Context
Do as follows on the router to send gratuitous ARP packets:

Procedure
Step 1 Run:
system-view

Step 2 Run:
vrrp gratuitous-arp timeout time
The timeout period is configured for the master router to send gratuitous ARP packets.
The master router sends the ARP packets with the virtual MAC address. By default, the Master
sends a gratuitous ARP packet every 120 seconds.
Run the undo vrrp gratuitous-arp timeout command in the system view to restore the default
timeout period of sending gratuitous ARP packets.
Run the vrrp gratuitous-arp timeout disable command in the system view to disable the master
router to send gratuitous ARP packets.
----End

By viewing the adjusted parameters of a VRRP backup group, you can check whether the
Prerequisite
The configurations of adjusting and optimizing VRRP function are complete.
Procedure
[ brief ] command to check the status of VRRP.
id ] ] [ brief ] command to check the status and configurations of the VRRP6 backup group.
----End
Example
Run the display vrrp command, and you can view the modified VRRP parameter. For example,
the TimerRun field and the TimerConfig field display 20. That is, the interval for sending the
VRRP advertisement packet is modified as 20 seconds. The default interval is 1 second.
State : Master
Virtual IP : 100.1.1.111
PriorityRun : 120
TimerRun : 20
TimerConfig : 20
Auth Type : NONE

Virtual Mac : 0000-5e00-0101

Check TTL : YES
Create time : 2010-06-22 17:32:56
Last change time : 2010-06-22 17:33:00
State : Master
PriorityRun : 200
TimerRun : 200
TimerConfig : 20
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
IF State : UP
Create time : 2010-06-23 17:32:56
Last change time : 2010-06-23 17:33:00
4.11 Configuring mVRRP Backup Groups

An mVRRP backup group can be bound to other member backup groups and determine the
status of member backup groups according to the bindings. This is applicable to the scenario
where a device is dual-homed to master and slave devices on a MAN.

Before configuring an mVRRP backup group, familiarize yourself with the applicable
Application Environment
Figure 4-4 mVRRP determines the dual-homing of the master and slave routeres
NPE1
mVRRP
UPE
NPE2

As shown in Figure 4-4, when the convergence layer of the Metro Ethernet (ME) dual NPEs
are deployed for high reliability. The master and standby routeres are determined by mVRRP
between NPEs.
The mVRRP backup group is actually the ordinary VRRP backup group. The difference is that
the mVRRP backup group can be bound to other backup groups of different services. The status
of the backup group of related services depends on the binding relationship.
The mVRRP backup group can be bound to several backup group members. The mVRRP backup
group cannot be bound to other management backup groups.
According to different applications, the binding relationship of the mVRRP backup group is as
follows:
l The VRRP backup group is bound to the mVRRP backup group: UPEs are dual-homed to
NPEs. VRRP is run between NPEs. The master NPE and backup NPE are determined by
the configured priority of VRRP. Multiple VRRP backup groups run between NPEs with
different services.
If each VRRP backup group needs to maintain its own state machine, a huge number of
VRRP packets exist among NPEs. To simplify the process and decrease occupancy of
bandwidth, you can set one VRRP backup group as the mVRRP backup group. Other
backup group members are bound to the mVRRP backup group. The master and slave
routeres are determined directly by the binding relationship.
l The service interfaces are bound to the mVRRP backup group. If the UPEs are dual-homed
to NPEs through two physical links. You can bind the member interfaces to the mVRRP
backup group to determine the master member interfaces and the slave interfaces.
l PW is bound to the mVRRP backup group. If VPLS is run between UPEs and NPEs, the
UPEs are dual-homed to NPEs through two PWs. Then, you can bind the PW and the
mVRRP backup group to determine the master PW and the slave PW.
Before configuring mVRRP, complete the following tasks:
l Configuring attributes of network layer of interfaces for connectivity
Data Preparation
To configure mVRRP, you need the following data.
No. Data
1 ID of the mVRRP and IDs of VRRP backup group members
2 Virtual IP address of the mVRRP and virtual IP addresses of VRRP backup group
members
3 Priority of the mVRRP
4 Number of the member interface
5 PW peer IP address

4.11.2 Configuring mVRRP Backup Group

Each VRRP backup group needs to maintain its own state machine by sending VRRP packets.
Configuring an mVRRP backup group can reduce bandwidth consumption of VRRP packets.
Context
Do as follows on each router of an mVRRP backup group:
Procedure
1. Run:
system-view

2. Run:

3. Run:
A backup group is created and a virtual IP address is assigned to the backup group.
4. Run:
The priority of the VRRP backup group is configured.

5. Run:
admin-vrrp vrid virtual-router-id
This VRRP backup group is configured as an mVRRP backup group.

1. Run:
system-view

2. Run:

3. Run:
local ]
A VRRP6 backup group is created, and a virtual IPv6 address is assigned to the VRRP
backup group.
4. Run:
vrrp6 vrid virtual-router-id priority priority-value
The priority of the VRRP6 backup group is configured.

5. Run:
admin-vrrp6 vrid virtual-router-id [ ignore-if-down ]
This VRRP6 backup group is configured as an mVRRP6 backup group.

----End
4.11.3 (Optional) Configuring Member VRRP Backup Groups and

Binding them to the mVRRP Backup Group
Context
Do as follows on each router on which the member VRRP backup groups need to be bound to
an mVRRP backup group.
Procedure
1. Run:
system-view

2. Run:
The interface view of a VRRP member is displayed.

3. Run:
A backup group is created with a virtual IP address.

The status of the member VRRP backup group is determined by the mVRRP backup
group. Therefore, the member VRRP backup group needs not a priority.
4. Run:
vrrp vrid virtual-router-id1 track admin-vrrp interface interface-type
interface-number [ .subinterface-number ] vrid virtual-router-id2
The member VRRP backup group is bound to the mVRRP backup group.
After the member VRRP backup group is bound to the mVRRP backup group, the
state machine of the member VRRP backup group becomes dependent. That is, the
member VRRP backup group deletes the protocol timer, and no longer sends or
receives packets, and implements its state machine by directly copying the status of
the mVRRP backup group. The backup member can be bound to only one mVRRP.
NOTE
1. Run:
system-view


2. Run:
The interface view of a member VRRP6 backup group is displayed.

3. Run:
local ]
A member VRRP6 backup group is created, and a virtual IPv6 address is assigned to
the member VRRP6 backup group.
The status of the member VRRP6 backup group is determined by the mVRRP6 backup
group. Therefore, the member VRRP6 backup group does not need a priority.
4. Run:
vrrp6 vrid virtual-router-id1 track admin-vrrp6 interface interface-type
interface-number vrid virtual-router-id2
The member VRRP6 backup group is bound to the mVRRP6 backup group.
After the member VRRP6 backup group is bound to the mVRRP backup group, the
state machine of the member VRRP6 backup group becomes dependent. That is, the
member VRRP6 backup group deletes the protocol timer, and no longer sends or
receives packets, and implements its state machine by directly copying the status of
the mVRRP6 backup group. A member VRRP6 backup group can be bound to only
one mVRRP6 backup group.
NOTE
Only a single member VRRP6 backup group can be configured on a single interface.
----End
4.11.4 (Optional) Binding Member Interface and Management

Backup Group
An mVRRP backup group can perform fast master/slave switchover by tracking the interface
status.
Context
Do as follows on the routers that need to bind the member interface to the mVRRP backup group.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The member interface view is displayed.

Step 3 Run:
track admin-vrrp interface interface-type interface-number vrid virtual-router-id

The member interface is bound to the mVRRP backup group.
----End
4.11.5 (Optional) Binding the PW to the mVRRP Backup Group

Through VPLS
By configuring the binding of a PW and an mVRRP backup group, you can associate the PW
with the mVRRP backup group.
Context
Do as follows on the routers that need to bind the PW to the mVRRP backup group.
Procedure
Step 1 Run:
system-view
Step 2 Run:
vsi vsi-name static
The VSI view is displayed.
Step 3 Run:
pwsignal ldp
The VSI-LDP view is displayed.
Step 4 Run:
peer peer-address [ negotiation-vc-id vc-id ] track admin-vrrp interface interface-
type interface-number vrid virtual-router-id
The PW is bound to the VRRP backup group.
Before the PW is bound to the mVRRP backup group, the peer must exist.
For the configuration of the PW, refer to Chapter "VPLS Configuration" in the HUAWEI
----End

By viewing all bindings in an mVRRP backup group, you can check whether the configurations
are successful.
Prerequisite
The configurations of the mVRRP backup groups function are complete.

Procedure
l Run the display vrrp binding admin-vrrp [ interface interface-type interface-number ]
[ vrid virtual-router-id ] command to check all binding information about the mVRRP
backup group.
l Run the display vrrp binding admin-vrrp [ interface interface-type1 interface-
number1 ] [ vrid virtual-router-id ] member-vrrp [ interface interface-type2 interface-
number2 ] [ vrid virtual-router-id ] command to check the binding between the mVRRP
backup group and the member VRRP backup groups.
l Run the display vrrp binding admin-vrrp [ interface interface-type1 interface-
number1 ] [ vrid virtual-router-id ] member-interface [ interface interface-type2
interface-number2 ] command to check the binding between the mVRRP backup group
and member VRRP backup groups.
l Run the display vrrp6 binding admin-vrrp6 [ interface interface-type1 interface-
number1 ] [vrid virtual-router-id1 ] member-vrrp [ interface interface-type2 interface-
number2 ] [ vrid virtual-router-id2 ] command to check the binding between the mVRRP6
backup group and member VRRP6 backup groups.
l Run the following commands to check the binding between the mVRRP backup group and
the PW members.
– display vrrp binding admin-vrrp [ interface interface-type1 interface-number1 ]
[ vrid virtual-router-id ] member-pw
[ vrid virtual-router-id ] member-pw vc interface interface-type2 interface-number2
[ vrid virtual-router-id ] member-pw vsi vsi-name peer ip-address [ negotiation-vc-
id vc-id1 ]
[ vrid virtual-router-id ] member-pw vc switch-vc peer ip-address vc-id2
l Run the display vrrp admin-vrrp command to check the status of all mVRRP backup
groups in the current configuration.
----End
Example
After the configuration, you can run the display vrrp binding admin-vrrp command to view
all binding information about the member VRRP backup group, interface member, and PW
member.
<HUAWEI> display vrrp binding admin-vrrp
Interface: GigabitEthernet2/0/0, admin-vrrp vrid: 6, state: Master
Member-vrrp number: 1
Interface: GigabitEthernet2/0/0.1, vrid: 8, state: Master
Member-interface number: 1
Interface: GigabitEthernet2/0/0.2, state: Up
4.12 Configuring VRRP Version Upgrade

After being upgraded from version 2 to version 3, VRRP can support both IPv6 and IPv4
networks.


Before configuring VRRP version upgrade, familiarize yourself with the applicable
Currently, VRRPv2 is adopted. VRRP for IPv4 supports both VRRPv2 packets and VRRPv3
packets, whereas VRRP for IPv6 supports only VRRPv3 packets. You can undertake this
configuration task to upgrade the VRRP version as required.
Before configuring VRRP version upgrade, complete the following tasks:
l Installing the device and powering it on properly
l Ensuring that VRRPv2 is running on the device
Data Preparation
To configure VRRP version upgrade, you need the following data.
No. Data
1 VRRP version number
4.12.2 Configuring VRRPv3

After VRRPv3 is configured, VRRP backup groups can receive both VRRPv2 and VRRPv3
Advertisement packets.
Context
Do as follows on each router in a VRRP backup group.
Procedure
Step 1 Run:
system-view

Step 2 Run:
vrrp version v3
The VRRP version of the current device is set to VRRPv3.

vrrp version-3 send-packet-mode { v2-only | v3-only | v2v3-both }
The mode for sending Advertisement packets in VRRPv3 is set.

The default VRRP version is v2. If the VRRP version is switched to v3, the default mode for
sending advertisement packets is v3-only.
----End

You can view VRRP version information to check whether the configuration is successful.
Prerequisite
The configurations of VRRP version upgrade are complete.
Procedure
l Run the display vrrp protocol-information command to view VRRP version information.
----End
Example
After the configuration, run the display vrrp protocol-information command, and you can
view that the VRRP protocol version is v3 and the mode for sending Advertisement packets is
send v3 only.
<HUAWEI> display vrrp protocol-information
VRRP protocol information is shown as below:
VRRP protocol version : v3
Send advertisement packet mode : send v3 only
4.13 Maintaining VRRP

This section describes how to maintain VRRP. Detailed operations include deleting VRRP
statistics, and monitoring the VRRP operation status.
4.13.1 Monitoring the VRRP Running

By monitoring the VRRP operation status, you can view information about VRRP during the
operation.
Context
In routine maintenance, you can run the following command in any view to display the running
status of VRRP.
Procedure
[ brief ] command in any view to check the current running status and parameters of VRRP.
id ] ] [ brief ] command in any view to check the status and configurations of the VRRP6
backup group.
----End


The following sections provide several examples for configuring VRRP to improve reliability.
Context
NOTE
4.14.1 Example for Configuring VRRP in Master/Backup Mode

In this example, by configuring a VRRP backup group in master/backup mode, you can use the
master device of the VRRP backup group to transmit all network traffic.
NOTE
As shown in Figure 4-5, Host A accesses Host B through the default gateway.
The requirements are as follows:
l Router A and Router B form a VRRP backup group that serves as the default gateway for
Host A.
l Normally, Router A serves as the gateway. When Router A fails, Router B serves as the
gateway.
l Router A continues to function as the master router within 20 seconds after it recovers.
Figure 4-5 Networking diagram of configuring VRRP in the master/backup mode

Backup group 1
Virtual IP Address:
10.1.1.111
RouterA
Master
POS1/0/0
GE2/0/0 192.168.1.1/24
10.1.1.1/24
POS1/0/0
192.168.1.2/24
RouterC Eth3/0/0
HostA 20.1.1.1/24
10.1.1.100/24 POS2/0/0 HostB
192.168.2.2/24 20.1.1.100/24
GE2/0/0 POS1/0/0
10.1.1.2/24 192.168.2.1/24
Ethernet RouterB
Backup

1. Create the backup group 1 on the GE 2/0/0 on Router A and configure Router A with the
highest priority in the backup group to be the master router. Configure the preemption
mode.
2. Create backup group 1 on the GE 2/0/0 interface on Router B and use the default priority.
Data Preparation
l Virtual router ID and virtual IP address
l Priority of each router in the backup group
l Preemption mode
Procedure
Step 1 Configure network interconnection between devices.
# Configure the default gateway of Host A with 10.1.1.111 and the default gateway of Host B
with 20.1.1.1.
# Configure Router A, Router B and Router C to use OSPF for interconnection.
Step 2 Configure VRRP.
# On Router A, configure the IP address of the interface, create backup group 1 and configure
the priority of Router A in this group with 120 (as the master router).
[RouterA] interface gigabitethernet 2/0/0
[RouterA-GigabitEthernet2/0/0] undo shutdown
[RouterA-GigabitEthernet2/0/0] ip address 10.1.1.1 24
[RouterA-GigabitEthernet2/0/0] vrrp vrid 1 virtual-ip 10.1.1.111
[RouterA-GigabitEthernet2/0/0] vrrp vrid 1 priority 120
[RouterA-GigabitEthernet2/0/0] vrrp vrid 1 preempt-mode timer delay 20
[RouterA-GigabitEthernet2/0/0] quit
[RouterA] quit
# On Router B, configure the IP address of the interface, create backup group 1 and configure
the priority of Router B in this group with the default value 100 (as the backup router).
[RouterB] interface gigabitethernet 2/0/0
[RouterB-GigabitEthernet2/0/0] undo shutdown
[RouterB-GigabitEthernet2/0/0] ip address 10.1.1.2 24
[RouterB-GigabitEthernet2/0/0] vrrp vrid 1 virtual-ip 10.1.1.111
[RouterB] quit

l Check that the VRRP backup group can serve as a gateway.
After the previous configuration, Host A can ping through Host B.
Running the display vrrp command on Router A, you can view that the status of Router A
is Master. Running the display vrrp command on Router B, you can view that the Router
B is Backup.

<RouterA> display vrrp

state : Master
Virtual IP : 10.1.1.111
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
<RouterB> display vrrp
state : Backup
Virtual IP : 10.1.1.111
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 A and Router B, you can view a
direct route with the destination address being the virtual IP address on Router A, and an
OSPF route to the same destination on Router B.
The displays on Router A and Router B are as follows.
<RouterA> display ip routing-table
Route Flags: R - relied, D - download to fib
------------------------------------------------------------------------------
Routing Tables: Public
Destinations : 10 Routes : 10
Destination/Mask Proto Pre Cost Flags NextHop Interface
10.1.1.0/24 Direct 0 0 D 10.1.1.1
GigabitEthernet2/0/0
10.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0
20.1.1.0/24 OSPF 10 2 D 192.168.1.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
192.168.2.0/24 OSPF 10 2 D 10.1.1.2
<RouterB> display ip routing-table
------------------------------------------------------------------------------
10.1.1.111/32 OSPF 10 2 D 10.1.1.1 InLoopBack0
20.1.1.0/24 OSPF 10 2 D 192.168.2.2 Pos1/0/0
192.168.1.0/24 OSPF 10 2 D 10.1.1.1
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
l Check whether Router B can become the master when Router A fails.
To simulate the election of the master router when Router A fails, run the shutdown
command on the GE 2/0/0 on Router A.
Running the display vrrp command on Router B to view the VRRP status, you can view
that Router B is in the Master state. The command output is as follows:
state : Master
Virtual IP : 10.1.1.111
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
l Check that Router A can perform preemption after recovering.

Run the undo shutdown command on GE 2/0/0. On Router A, run the display vrrp
command to view VRRP status 20 seconds after GE 2/0/0 being Up. You can view that Router
A restores to be the master router.
----End
Configuration Files
#
sysname RouterA
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
vrrp vrid 1 virtual-ip 10.1.1.111
vrrp vrid 1 priority 120
vrrp vrid 1 preempt-mode timer delay 20
#
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 10.1.1.0 0.0.0.255
#
return

#
sysname RouterB
#
undo shutdown
ip address 10.1.1.2 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 10.1.1.0 0.0.0.255
#
return
l Configuration file of Router C

#
sysname RouterC
#
interface Ethernet3/0/0
undo shutdown
ip address 20.1.1.1 255.255.255.0
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.1.2 255.255.255.0
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 192.168.2.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
network 20.1.1.0 0.0.0.255
#
return
4.14.2 Example for Configuring VRRP in Load Balancing Mode

In this example, by configuring a VRRP backup group in load balancing mode, you can provide
the mutual backup function to devices in the VRRP backup group and balance network traffic
among these devices.
NOTE
As shown in Figure 4-6.

l Router A serves as the master router of backup group 1 and the backup router of backup
group 2.
l Router B serves as the master router of backup group 2 and the backup router of backup
group 1.
l Host A in the internal network takes backup group 1 as its gateway and Host C takes backup
group 2 as its gateway to share the traffic and backup each other.

Figure 4-6 Networking diagram of configuring VRRP in load balancing mode

Backup group 2
Virtual IP Address: RouterA
10.1.1.112 group 1:Master
group 2:Backup
POS1/0/0
192.168.1.1/24
GE2/0/0
10.1.1.1/24 POS1/0/0
HostA 192.168.1.2/24
10.1.1.100/24 Eth3/0/0
RouterC 20.1.1.1/24
POS2/0/0 HostB
192.168.2.2/24 20.1.1.100/24
HostC POS1/0/0
10.1.1.101/24 GE2/0/0 192.168.2.1/24
10.1.1.2/24 RouterB
Ethernet group 2:Master
Backup group 1 group 1:Backup
Virtual IP Address:
10.1.1.111
1. Create two backup groups on the GE 2/0/0 interface on Router A. Router A is the master
router in the backup group 1 and the backup in group 2.
2. Create two backup groups on the GE 2/0/0 interface on Router B. Router B is the backup
router in the backup group 1 and the master in backup group 2.
Data Preparation
Procedure
Step 1 Configure the network interconnection between devices.
# Configure the default gateway of Host A as the virtual IP address 10.1.1.111 in backup group
1, the default gateway of Host B as 20.1.1.1, and the default gateway of Host C as the virtual IP
address 10.1.1.112 in backup group 2.
# Configure Router A, Router B, and Router C to use OSPF for interconnection.
Step 2 Configure VRRP.
# On Router A, configure the IP address of the interface, create backup backup group 1 and
configure the priority of Router A in this backup group as 120 (as the master router). Create

backup group 2 and configure the priority of Router A in this backup group with the default
value 100 (as the backup router).
# On Router B, configure the IP address of the interface, create backup backup group 1 and
configure the priority of Router B in this backup group with the default value 100 (as the backup
router). Create backup group 2, and configure the priority of Router B in this backup group with
120 (as the master router).
[RouterB-GigabitEthernet2/0/0] vrrp vrid 2 priority 120
[RouterB-GigabitEthernet2/0/0] quit
After the previous configuration, Host A and Host C in the network can ping through Host B.
Tracert Host B from Host A and Host C. Packets from Host A to Host B pass through Router
A and Router C. Packets from Host C to Host B pass through Router A and Router C. That is,
the load balancing is enabled for Router A and Router B to share the internal traffic.
<HostA> tracert 20.1.1.100
traceroute to 20.1.1.100 (20.1.1.100), max hops: 30, packet length: 40, press
CTRL_C to break
1 10.1.1.1 120 ms 50 ms 60 ms
2 192.168.1.2 100 ms 60 ms 60 ms
3 20.1.1.100 130 ms 90 ms 90 ms
<HostC> tracert 20.1.1.100
traceroute to 20.1.1.100 (20.1.1.100), max hops: 30, packet length: 40, press
CTRL_C to break
1 10.1.1.2 30 ms 60 ms 40 ms
2 192.168.2.2 90 ms 60 ms 60 ms
3 20.1.1.100 70 ms 60 ms 90 ms
Running the display vrrp command on Router A, you can view that Router A serves as the
master router in backup group 1 and the backup router in backup group 2.
state : Master
Virtual IP : 10.1.1.111
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES

state : Backup
Virtual IP : 10.1.1.112
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0102
Check TTL : YES
----End
Configuration Files
#
sysname RouterA
#
undo shutdown
ip address 10.1.1.1 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 10.1.1.0 0.0.0.255
#
return

#
sysname RouterB
#
undo shutdown
ip address 10.1.1.2 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 10.1.1.0 0.0.0.255
#
return

#
sysname RouterC
#

undo shutdown
ip address 20.1.1.1 255.255.255.0
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.1.2 255.255.255.0
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 192.168.2.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
network 20.1.1.0 0.0.0.255
#
return
4.14.3 Example for Configuring the Multi-Instance VRRP

In this example, by configuring different default gateway addresses for CEs on different VPNs,
you can implement load balancing of a VRRP backup group and communication between hosts
of the same VPN.
NOTE
As shown in Figure 4-7, there are two VPN networks: VPN RED and VPN BLUE. Configure
MPLS and VRRP according to the requirements listed in Table 4-1.
Table 4-1 Networking requirements of the multi-instance VRRP

Item Networking Requirements
Backup groups l PE-A and PE-B are configured as VRRP backup group 1 and VRRP
backup group 2. In backup group 1, PE-A serves as the master device
and PE-B serves as the backup device. In backup group 2, PE-A
serves as the backup group and PE-B serves as the master device.
l CE-A uses the virtual IP address of VRRP backup group 1 as its
default gateway.
l CE-B uses the virtual IP address of VRRP backup group 2 as its
default gateway.
VPN instance that l CE-A and CE-D belong to the VPN-BLUE instances.
CE belongs to l CE-B and CE-C belong to the VPN-RED instances.

Item Networking Requirements
VPN instance that l The GE 1/0/0 interfaces on PE-A belong to the VPN-BLUE
the interface on PE instances. The GE 2/0/0 interfaces belong to VPN-RED instances.
belongs to l The GE 1/0/0 interfaces on PE-B belong to the VPN-BLUE
instances. The GE 2/0/0 interfaces belong to VPN-RED instances.
l The GE 1/0/0 interfaces on PE-C belong to the VPN-RED instances.
The GE 2/0/0 interfaces belong to VPN-BLUE instances.
Routing protocol l Configure the OSPF and enable the MPLS forwarding.
and MPLS l Configure default routes on CE-A and CE-B to exchange VPN
routing information with PE-A and PE-B.
l Establish BGP peer relationship among PE-A, PE-B and PE-C to
transmit all VPN routes.
Figure 4-7 Networking diagram of configuring VRRP multi-instance
HostA HostC
VPN BLUE
VPN RED
CE-A PE-A CE-C

GE1/0/0 Loopback1
GE1/0/0 Public GE1/0/0

Network
POS3/0/0
Backup group1 P POS3/0/0 GE1/0/0
0
0/
for VPN BLUE

/
POS1/0/0
E2
G Loopback1
G
E1
0
/
/0
Backup group2 / 0/ PE-C

S2
0 POS3/0/0
PO
for VPN RED Loopback1 GE2/0/0

POS3/0/0
GE2/0/0
GE1/0/0
GE1/0/0
Loopback1
PE-B CE-D
CE-B
HostD
VPN RED
HostB VPN BLUE
router Interface IP Address VPN-Instance

P POS 1/0/0 192.168.1.2/24 -
POS 2/0/0 192.168.2.2/24 -
POS 3/0/0 192.168.3.2/24 -
Loopback1 4.4.4.4/32 -

PE-A GE 1/0/0 10.1.1.1/24 VPN-BLUE

GE 2/0/0 20.1.1.1/24 VPN-RED
POS 3/0/0 192.168.1.1/24 -
Loopback1 1.1.1.1/32 -
PE-B GE 1/0/0 10.1.1.2/24 VPN-BLUE
GE 2/0/0 20.1.1.2/24 VPN-RED
POS 3/0/0 192.168.2.1/24 -
Loopback1 2.2.2.2/32 -
PE-C GE 1/0/0 10.2.1.1/24 VPN-RED
GE 2/0/0 20.2.1.1/24 VPN-BLUE
POS 3/0/0 192.168.3.1/24 -
Loopback1 3.3.3.3/32 -
CE-A GE 1/0/0 10.1.1.100/24 -
CE-B GE 1/0/0 20.1.1.100/24 -
CE-C GE 1/0/0 20.2.1.100/24 -
CE-D GE 1/0/0 10.2.1.100/24 -
1. PE-A and PE-B are configured as VRRP backup group 1 and VRRP backup group 2. In
backup group 1, PE-A serves as the master device and PE-B serves as the backup device.
In backup group 2, PE-A serves as the backup group and PE-B serves as the master device.
2. PE-A and PE-B share the traffic and back up each other.
Data Preparation
Procedure
Step 1 Configure OSPF on each PE and P for communication on the backbone network. Detailed
configuration procedures are not described.
Step 2 Configure MPLS basic functions and MPLS LDP on the MPLS backbone network and establish
LDP LSP (omitted).
Step 3 Configure VPN instances on PEs and enable CEs to access PEs (omitted).
Step 4 Configure MP-IBGP peer connections between PEs (omitted).
Step 5 Configure default routes on CE-A and CE-B (omitted).

For the configurations from Step 1 to Step 5, refer to Chapter "BGP MPLS IP VPN
Configuration" in the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN. You
can also refer to the following configuration files.

Step 6 Configure the multi-instance VRRP instance on PE-A and PE-B.
# On PE-A, create backup group 1, and configure the priority of PE-A in this group to 120 (as
the master router).
<PE-A> system-view
[PE-A] interface gigabitethernet 1/0/0
[PE-A-GigabitEthernet1/0/0] vrrp vrid 1 virtual-ip 10.1.1.111
[PE-A-GigabitEthernet1/0/0] vrrp vrid 1 priority 120
[PE-A-GigabitEthernet1/0/0] quit
# On PE-A, create backup group 2, and configure the priority of PE-A in this group to the default
value (as the backup router).
[PE-A] interface gigabitethernet 2/0/0
[PE-A-GigabitEthernet2/0/0] vrrp vrid 2 virtual-ip 20.1.1.111
[PE-A-GigabitEthernet2/0/0] quit
# On PE-B, create backup group 1, and configure the priority of PE-B in this group to the default
value (as the backup router).
<PE-B> system-view
[PE-B] interface gigabitethernet 1/0/0
[PE-B-GigabitEthernet1/0/0] vrrp vrid 1 virtual-ip 10.1.1.111
[PE-B-GigabitEthernet1/0/0] quit
# On PE-B, create backup group 2, and configure the priority of PE-B in this group to 120 (as
the master router).
[PE-B] interface gigabitethernet 2/0/0
[PE-B-GigabitEthernet2/0/0] vrrp vrid 2 virtual-ip 20.1.1.111
[PE-B-GigabitEthernet2/0/0] vrrp vrid 2 priority 120
[PE-B-GigabitEthernet2/0/0] quit
Running the display ip routing-table vpn-instance vpn-instance-name command on PE-A and

PE-B, you can view a route with the destination address being the virtual IP address in the VPN
routing table on PE-A. There is no such route on PE-B.
The display on PE-A is as follows:

<PE-A> display ip routing-table vpn-instance VPN-BLUE
------------------------------------------------------------------------------
Routing Tables: VPN-BLUE
10.1.1.0/24 Direct 0 0 D 10.1.1.2 GigabitEthernet1/0/0
10.1.1.111/32 Direct 0 0 D 127.0.0.1 InLoopBack0... ...
Run the ping command on PE-A and PE-B:

<PE-A> ping -vpn-instance VPN-BLUE 10.1.1.111
PING 10.1.1.111: 56 data bytes, press CTRL_C to break
Reply from 10.1.1.111: bytes=56 Sequence=1 ttl=255 time=6 ms
--- 10.1.1.111 ping statistics ---

5 packet(s) transmitted
5 packet(s) received

0.00% packet loss

round-trip min/avg/max = 1/2/6 ms
----End
Configuration Files
l Configure file of PE-A
#
sysname PE-A
#
ip vpn-instance VPN-BLUE
ipv4-family
route-distinguisher 100:1
vpn-target 100:1 export-extcommunity
vpn-target 100:1 import-extcommunity
#
ip vpn-instance VPN-RED
ipv4-family
#
mpls lsr-id 1.1.1.1
mpls
#
mpls ldp
#
undo shutdown
ip binding vpn-instance VPN-BLUE
ip address 10.1.1.1 255.255.255.0
#
undo shutdown
ip binding vpn-instance VPN-RED
ip address 20.1.1.1 255.255.255.0
#
interface Pos3/0/0
link-protocol ppp
undo shutdown
ip address 192.168.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
bgp 100
peer 3.3.3.3 as-number 100
peer 3.3.3.3 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
peer 3.3.3.3 enable
#
ipv4-family vpnv4
policy vpn-target
peer 3.3.3.3 enable
#
ipv4-family vpn-instance VPN-BLUE
import-route direct
import-route static
#
ipv4-family vpn-instance VPN-RED

import-route direct
import-route static
#
ospf 1
area 0.0.0.0
network 192.168.1.0 0.0.0.255
network 1.1.1.1 0.0.0.0
#
ip route-static vpn-instance VPN-BLUE 0.0.0.0 0.0.0.0 10.1.1.100
ip route-static vpn-instance VPN-RED 0.0.0.0 0.0.0.0 20.1.1.100
#
return
l Configuration file of PE-B
#
sysname PE-B
#
ip vpn-instance VPN-BLUE
ipv4-family
#
ip vpn-instance VPN-RED
ipv4-family
#
mpls lsr-id 2.2.2.2
mpls
#
mpls ldp
#
undo shutdown
ip binding vpn-instance VPN-BLUE
ip address 10.1.1.2 255.255.255.0
#
undo shutdown
ip binding vpn-instance VPN-RED
ip address 20.1.1.2 255.255.255.0
#
interface Pos3/0/0
link-protocol ppp
undo shutdown
ip address 192.168.2.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 3.3.3.3 enable
#
ipv4-family vpnv4
policy vpn-target
peer 3.3.3.3 enable
#
ipv4-family vpn-instance VPN-BLUE

import-route direct
import-route static
#
ipv4-family vpn-instance VPN-RED
import-route direct
import-route static
#
ospf 1
area 0.0.0.0
network 192.168.2.0 0.0.0.255
network 2.2.2.2 0.0.0.0
#
ip route-static vpn-instance VPN-BLUE 0.0.0.0 0.0.0.0 10.1.1.100
ip route-static vpn-instance VPN-RED 0.0.0.0 0.0.0.0 20.1.1.100
#
return
4.14.4 Example for Configuring VRRP Fast Switchover

In this example, by tracking BFD sessions, a VRRP backup group can use the backup device to
take over network traffic when the active interface or a link goes Down.
NOTE
As shown in Figure 4-8, Router A, Router B, Switch A, Switch B and Universal Medium
Gateway (UMG) compose a simple Next Generation Network (NGN) network.
l Connect UMG with Router A and Router B through Switch A and Switch B respectively.
l Run VRRP on Router A and Router B. Router A serves as the master router and Router B
serves as the backup router.
When Router A fails or the GE link between Router A and Router B fails, VRRP switchover
should be performed in less than one second to implement fast convergence in NGN.
Figure 4-8 Networking diagram of configuring VRRP fast switchover
Backbone
Network
POS1/0/0 POS1/0/0
RouterA 192.168.0.1/24192.168.0.2/24 RouterB
GE2/0/0 GE2/0/0
10.1.1.1/24 Backup group 10 10.1.1.2/24
Virtual IP address: 10.1.1.3/24
SwitchA SwitchB
VLAN
UMG

1. Configure BFD sessions on GE interfaces on Router A and Router B to monitor the link
Router A - Switch A - Switch B - Router B as well as Router A itself.
2. Enable VRRP to track BFD sessions on Router B so that once the sessions are Down, the
priority of Router B increases by 40 and then the switchover is enabled.
NOTE
l This example covers only configurations on Router A and Router B.

l If the switchover needs to be implemented only on Router A, configure BFD sessions on the POS
interface that is directly connected to Router A and Router B in Step 1. This configuration is not covered
in this example.
Data Preparation
l The local and remote BFD session identifier

Procedure
Step 1 Configure BFD.
# Configure a BFD session on Router A.

[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd atob bind peer-ip 10.1.1.2 interface gigabitethernet 2/0/0
[RouterA-bfd-session-atob] discriminator local 1
[RouterA-bfd-session-atob] discriminator remote 2
[RouterA-bfd-session-atob] min-rx-interval 50
[RouterA-bfd-session-atob] min-tx-interval 50
[RouterA-bfd-session-atob] commit
[RouterA-bfd-session-atob] quit
# Configure a BFD session on Router B.

[RouterB] bfd
[RouterB-bfd] quit
[RouterB] interface gigabitethernet2/0/0
[RouterB] bfd btoa bind peer-ip 10.1.1.1 interface gigabitethernet 2/0/0
[RouterB-bfd-session-btoa] discriminator local 2
[RouterB-bfd-session-btoa] discriminator remote 1
[RouterB-bfd-session-btoa] min-rx-interval 50
[RouterB-bfd-session-btoa] min-tx-interval 50
[RouterB-bfd-session-btoa] commit
[RouterB-bfd-session-btoa] quit

Running the display bfd session command on Router A and Router B, you can view that BFD
sessions are Up. Take the display on Router A as an example.
[RouterA] display bfd session all
--------------------------------------------------------------------------
Local Remote PeerIpAddr InterfaceName State Type
--------------------------------------------------------------------------
1 2 10.1.1.2 GigabitEthernet2/0/0 Up S_IP_IF
--------------------------------------------------------------------------
Total UP/DOWN Session Number : 1/0
Step 2 Configure VRRP fast switchover.

# Create a backup group 10 and configure Router A to be the master router with the priority as
160.
# Create a backup group 10 and configure Router B to be the backup router with the priority as
140.
# Track the BFD session on the backup router. If the BFD session is Down, the priority of Router
B increases by 40.
[RouterB-GigabitEthernet2/0/0] vrrp vrid 10 track bfd-session 2 increased 40
Running the display vrrpcommand on Route A or Router B, you can view that Router A is the
master and Router B is the backup. You can also view the tracked BFD session and its status on
Router B.
[RouterA] display vrrp
state : Master
PriorityRun : 160
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0110
Check TTL : YES
Create time : 2010-06-22 17:32:56
Last change time : 2010-06-22 17:33:00
[RouterB] display vrrp
state : Backup
PriorityRun : 140
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0110

Check TTL : YES

BFD-Session State : UP
Create time : 2010-06-22 17:33:00
Last change time : 2010-06-22 17:33:04
# Run the shutdowncommand on GE 2/0/0 on Router A to simulate a link fault.

[RouterA-GigabitEthernet2/0/0] shutdown
On Router B, VRRP fast switchover is performed after BFD fails.

%May 10 15:48:30 2006 RouterB BFD/5/BFD:Slot=1;IO(1) BFD Session(Discr:2) FSM
Change To Down(Detect)
%May 10 15:48:30 2006 RouterB VRRP/5/BfdWarning:
Virtual Router 10 | BFD-SESSION 2 : BFD_STATE_UP --> BFD_STATE_DOWN
%May 10 15:48:30 2006 RouterB VRRP/5/StateWarning:
GigabitEthernet2/0/0 | Virtual Router 10 : BACKUP --> MASTER
Running the display vrrp command on Router A, you can view that the status of Router A
changes to Initialize.
state : Initialize
PriorityRun : 160
MasterPriority : 0
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0110
Check TTL : YES
Create time : 2010-06-22 17:32:56
Last change time : 2010-06-22 17:33:06
Running the display vrrp command on Router B, you can view that Router B becomes the
master router and the BFD session when it is Down.
state : Master
PriorityRun : 180
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0110
Check TTL : YES
BFD-Session State : DOWN
Create time : 2010-06-22 17:33:00
Last change time : 2010-06-22 17:33:06
----End

Configuration Files
#
sysname RouterA
#
bfd
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
bfd atob bind peer-ip 10.1.1.2 interface gigabitethernet2/0/0
min-tx-interval 50
min-rx-interval 50
commit
#
return

#
sysname RouterB
#
bfd
#
undo shutdown
ip address 10.1.1.2 255.255.255.0
vrrp vrid 10 track bfd-session 2 increased 40
#
bfd btoa bind peer-ip 10.1.1.1 interface gigabitethernet2/0/0
min-tx-interval 50
min-rx-interval 50
commit
#
Return
4.14.5 Example for Configuring VRRP Fast Switchover (Using One-

Arm Echo Function)
In this example, creating a BFD session with the one-arm Echo function on a BFD-capable
device at one end of a link allows you to use BFD to rapidly detect and monitor the direct link
between the BFD-capable device and its BFD-incapable peer.
On a network shown in Figure 4-9, Router A and Router B support BFD but Router C does not.
BFD needs to be configured to fast detect the direct link between Router A and Router B and
the direct link between Router B and Router C. A BFD session with the one-arm Echo function
needs to be configured on Router A, detecting the direct link between Router A and Router C;
another BFD session with the one-arm Echo function needs to be configured on Router B,
detecting the direct link between Router B and Router C.

Figure 4-9 Typical networking of VRRP fast switchover (Using One-Arm Echo Function)
RouterA
Master
GE1/0/0 GE1/0/1
10.1.1.1/24 192.168.1.1/24
Backbone
Network
PC1 RouterC
GE1/0/0 GE1/0/1
10.1.1.2/24 192.168.2.1/24
RouterB
Backup
Backup group 1
10.1.1.100
1. Configure a BFD session with the one-arm Echo function on Router A for detecting direct
links between Router A and Router C and a second session on Router B for detecting direct
links between Router B and Router C. Configure a peer BFD session on Router A and
Router B for detecting direct links between Router A and Router B.
2. Configure a VRRP backup group on Router A and Router B. Router A functions as a master
device and Router B functions as a backup device. The VRRP backup group implements
a fast switchover by tracking the BFD session status.
Data Preparation
l Name of all BFD sessions
l Discriminators for all BFD sessions
l ID of the VRRP backup group
l Virtual IP addresses of the VRRP backup group
l Priority of all routers in the VRRP backup group
Procedure
Step 1 Configure OSPF to ensure connectivity between Router A, Router B, and Router C. These
configuration details are not detailed here.
Step 2 Assign IP addresses to interfaces connecting Router A and Router B.
# Assign an IP address to the interface on Router A.

# Assign an IP address to the interface on Router B.

[HUAWEI] sysname RouterB
Step 3 Configure a VLANIF interface on Router C.

[HUAWEI] sysname RouterC
[RouterC] interface gigabitethernet 1/0/0
[RouterC-GigabitEthernet1/0/0] undo shutdown
[RouterC-GigabitEthernet1/0/0] portswitch
[RouterC-GigabitEthernet1/0/0] quit
[RouterC-GigabitEthernet2/0/0] portswitch
[HUAWEIC] vlan 10
[HUAWEIC-vlan10] port gigabitethernet 1/0/0
[HUAWEIC-vlan10] port gigabitethernet 2/0/0
[HUAWEIC-vlan10] quit
[HUAWEIC] interface vlanif 10
[HUAWEIC-Vlanif10] ip address 10.1.1.3 24
[HUAWEIC-Vlanif10] quit
Step 4 Create a BFD session with the one-arm Echo function.
# Configure Router A.
[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd atoc bind peer-ip 10.1.1.3 interface gigabitEthernet1/0/0 one-arm-
echo
[RouterA-bfd-session-atoc] discriminator local 1
[RouterA-bfd-session-atoc] min-echo-rx-interval 100
[RouterA-bfd-session-atoc] commit
[RouterA-bfd-session-atoc] quit
# Configure Router B.
[RouterB] bfd
[RouterB-bfd] quit
[RouterB] bfd btoc bind peer-ip 10.1.1.3 interface gigabitEthernet1/0/0 one-arm-
echo
[RouterB-bfd-session-atoc] discriminator local 2
[RouterB-bfd-session-atoc] min-echo-rx-interval 100
[RouterB-bfd-session-atoc] commit
[RouterB-bfd-session-atoc] quit

# After the configurations are complete, run the display bfd session all verbose command on
Router A or Router B. You can see that the BFD session with the one-arm Echo function is Up.
Take the display on Router A as an example.
[RouterA] display bfd session all verbose
--------------------------------------------------------------------------------
Session MIndex : 256 (One Hop) State : Up Name : atob
--------------------------------------------------------------------------------
Local Discriminator : 1 Remote Discriminator : -
Session Detect Mode : Asynchronous Mode Without Echo Function

BFD Bind Type : Interface(GigabitEthernet1/0/0)
Bind Session Type : Static
Bind Peer IP Address : 10.1.1.3
NextHop Ip Address : 10.1.1.3
Bind Interface : GigabitEthernet1/0/0
FSM Board Id : 0 TOS-EXP : 7
Echo Rx Interval (ms) : 100
Actual Tx Interval (ms): 1000 Actual Rx Interval (ms): 100
Local Detect Multi : 3 Detect Interval (ms) : 3000
Echo Passive : Disable Acl Number : -
Destination Port : 3784 TTL : 255
Proc Interface Status : Disable Process PST : Disable
WTR Interval (ms) : - Local Demand Mode : Disable
Active Multi : 3
Last Local Diagnostic : Control Detection Time Expired
Bind Application : No Application Bind
Session TX TmrID : 87 Session Detect TmrID : 88
Session Init TmrID : - Session WTR TmrID : -
Session Echo Tx TmrID : -
PDT Index : FSM-0 | RCV-0 | IF-0 | TOKEN-0
Session Description : -
--------------------------------------------------------------------------------
Step 5 Configure peer BFD.

[RouterA] bfd peer bind peer-ip 10.1.1.2 interface gigabitEthernet1/0/0
[RouterA-bfd-session-peer] discriminator local 3
[RouterA-bfd-session-peer] discriminator remote 4
[RouterA-bfd-session-peer] commit
[RouterA-bfd-session-peer] quit
[RouterB] bfd peer bind peer-ip 10.1.1.1 interface gigabitEthernet1/0/0
[RouterB-bfd-session-peer] discriminator local 4
[RouterB-bfd-session-peer] discriminator remote 3
[RouterB-bfd-session-peer] commit
[RouterB-bfd-session-peer] quit
# After the configurations are complete, run the display bfd session all verbose command on
Router A or Router B. You can see that the peer BFD session is Up. Take the display on
Router A as an example.
--------------------------------------------------------------------------------
Session MIndex : 16384 (One Hop) State : Up Name : peer
------------------------------------------------------------------------------
Local Discriminator : 3 Remote Discriminator : 4


Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10
WTR Interval (ms) : -
Active Multi : 3
Session TX TmrID : - Session Detect TmrID : -
PDT Index : FSM-B030000 | RCV-0 | IF-B030000 | TOKEN-0
------------------------------------------------------------------------------
Step 6 Configure an mVRRP backup group.

# Configure backup group 1 on Router A. Set the priority of Router A in VRRP backup group
1 to 160, thus enabling Router A to function as a master device.
[RouterA-GigabitEthernet1/0/0] admin-vrrp vrid 1
# Configure backup group 1 on Router B. Set the priority of Router B in VRRP backup group
1 to 120, thus enabling Router B to function as a backup device.
[RouterB-GigabitEthernet1/0/0] admin-vrrp vrid 1
After the preceding configurations are complete, run the display vrrp command on Router A
or Router B. You can view that Router A functions as a master device and Router B functions
as a backup device.
State : Master
Virtual IP : 10.1.1.100
PriorityRun : 160
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
State : Backup
Virtual IP : 10.1.1.100
PriorityRun : 120
TimerRun : 1
TimerConfig : 1

Auth Type : NONE

Virtual Mac : 0000-5e00-0101
Check TTL : YES
Step 7 Configure the VRRP backup group to track the BFD session status.
[RouterA-GigabitEthernet1/0/0] vrrp vrid 1 track bfd-session 1 link
[RouterA-GigabitEthernet1/0/0] vrrp vrid 1 track bfd-session 3 peer
[RouterA-GigabitEthernet1/0/0] vrrp trigger route
[RouterA-GigabitEthernet1/0/0] vrrp vrid 1 track bfd-session 2 link
[RouterA-GigabitEthernet1/0/0] vrrp trigger route

Run the shutdown command on GE 1/0/0 of Router A to simulate a link failure.
Run the display vrrp command on Router A. You can see that the status of the VRRP backup
group becomes Initialize and the BFD session goes Down.
State : Initialize
Virtual IP : 10.1.1.100
PriorityRun : 160
MasterPriority : 0
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Track BFD : 1 Type : link
BFD-session state : DOWN
Track BFD : 3 Tpye : peer
Run the display vrrp command on Router B. You can see that the status of Router B in the
VRRP backup group becomes Master and the BFD session goes Down.
State : Master
Virtual IP : 10.1.1.100
PriorityRun : 170
TimerRun : 1
TimerConfig : 1
Auth Type : NONE

Virtual Mac : 0000-5e00-0101

Check TTL : YES
Track BFD : 2 Type : link
Track BFD : 4 Tpye : peer
----End
Configuration files
#
sysname RouterA
#
bfd
#
interface gigabitethernet 1/0/0
undo shutdown
ip address 10.1.1.1 255.255.255.0
admin-vrrp vrid 1
vrrp vrid 1 track bfd-session 1 link
vrrp vrid 1 track bfd-session 3 peer
vrrp trigger route
#
undo shutdown
ip address 192.168.1.1 255.255.255.0
#
bfd atoc bind peer-ip 10.1.1.3 interface gigabitEthernet1/0/0 one-arm-echo
min-echo-rx-interval 100
commit
#
bfd peer bind peer-ip 10.1.1.2 interface gigabitEthernet1/0/0
commit
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 192.168.1.0.0 0.0.0.255
#
return

#
sysname RouterB
#
bfd
#
undo shutdown
ip address 10.1.1.2 255.255.255.0
admin-vrrp vrid 1
vrrp vrid 1 track bfd-session 2 link
vrrp trigger route
#
undo shutdown

ip address 192.168.2.1 255.255.255.0

#
bfd btoc bind peer-ip 10.1.1.3 interface gigabitEthernet1/0/0 one-arm-echo
min-echo-rx-interval 100
commit
#
bfd peer bind peer-ip 10.1.1.1 interface gigabitEthernet1/0/0
commit
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 192.168.2.0.0 0.0.0.255
#
return

#
sysname RouterC
#
interface Vlanif10
ip address 10.1.1.3 255.255.255.0
#
portswitch
undo shutdown
port default vlan 10
#
portswitch
undo shutdown
4.14.6 Example for Configuring VRRP Fast Switchover (Using BFD

Sampling)
In this example, by configuring BFD in sampling mode, you can address the problem that a link
NOTE
the mVRRP backup group implements master/backup fast switchover by tracking the BFD
session. Between NPE1 and NPE2, the peer BFD session is established.
In this configuration example, the following restrictions are imposed on the network:
cannot be directly established between NPE1 and PE1 or between NPE2 and PE2.
l PE1 or PE2 does not support the BFD function.
In this case, you can use BFD sampling to implement VRRP fast switchover.

NOTE
With BFD sampling, the NPE establishes link BFD sessions with each CE.
For the NPE:

l NPE1 and NPE2 establish the mVRRP backup group, the service VRRP backup group,
and the peer BFD session through their respective interfaces GE 1/0/1 that connect to the
VPLS convergence network.
l NPE1 or NPE2 establishes four link BFD sessions with four CEs respectively through GE
1/0/1. The mVRRP backup group is responsible for tracking the status of the four BFD
sessions concurrently. When two or more link BFD sessions go Down, the mVRRP backup
group performs master/backup fast switchover.

Figure 4-10 Typical networking of VRRP fast switchover (using BFD sampling)
Aggregation
Access VPLS Network Core
#
interface GigabitEthernet1/0/1.1
ipaddress 10.1.1.254 255.255.255.0
v rrp v rid 10 v irtual-ip 10.1.1.1
admin-v rrp v rid 10
#
ipaddress 10.100.1.254 255.255.255.0
v rrpv rid 100 v irtual-ip10.100.1.200
#
ipaddress 10.101.1.254 255.255.255.0
IP:10.100.1.1/24 v rrpv rid 101 v irtual-ip10.101.1.200
GW:10.100.1.200 #
Inner VLAN:110 interface GigabitEthernet1/0/1.102
ipaddress 10.102.1.254 255.255.255.0
Outer VLAN: 10 v rrpv rid 102 v irtual-ip10.102.1.200
CE1 #
ipaddress 10.103.1.254 255.255.255.0
#
NPE1
CE2
IP:10.101.1.1/24
GW:10.101.1.200
Inner VLAN:210
PE1
Outer VLAN: 10 Link BFD Peer MPLS/IP Core
BFD
PE3 PE2
CE3
IP:10.102.1.1/24
GW:10.102.1.200
Inner VLAN:310 NPE2
Outer VLAN: 10
#
ipaddress 10.1.1.253 255.255.255.0
CE4 v rrp v rid 10 v irtual-ip 10.1.1.1
IP:10.103.1.1/24 #
GW:10.103.1.200 ipaddress 10.100.1.253 255.255.255.0
Inner VLAN:410 v rrpv rid 100 v irtual-ip10.100.1.200
Outer VLAN: 10 #
ipaddress 10.101.1.253 255.255.255.0
v rrp v rid101 v irtual-ip 10.101.1.200
#
ipaddress 10.102.1.253 255.255.255.0
#
ipaddress 10.103.1.253 255.255.255.0
#

1. Configure the sub-interface for QinQ VLAN tag termination on NPE1 and NPE2.
2. Configure the mVRRP backup group and service VRRP backup group on the sub-interfaces
for QinQ VLAN tag termination of NPE1 and NPE2 and bind the service VRRP backup
group with the mVRRP backup group.
3. Establish the BFD session between NPE1 and NPE2 and between the NPE and the CE.
4. Configure master/backup fast switchover of the mVRRP backup group using BFD
sampling.
Data Preparation
l Virtual Router IDs (VRIDs) and virtual IP addresses
l Priorities of VRRP backup groups
Procedure
Step 1 Configure the sub-interface for QinQ VLAN tag termination on NPE1 and NPE2.
NOTE
Only the configuration procedures of NPE1 and NPE2 are provided here. For the configuration procedures
of the BFD function of the CE as shown in Figure 4-10 and the VPLS convergence network, refer to the
HUAWEI NetEngine80E/40E Router Configuration Guide - Reliability and Configuration Guide - VPN.
# Configure NPE1.
[HUAWEI] sysname NPE1
[NPE1] interface gigabitethernet1/0/1
[NPE1-GigabitEthernet1/0/1] mode user-termination
[NPE1-GigabitEthernet1/0/1] undo shutdown
[NPE1-GigabitEthernet1/0/1] quit
[NPE1] interface gigabitethernet1/0/1.1
[NPE1-GigabitEthernet1/0/1.1] control-vid 1 qinq-termination
[NPE1-GigabitEthernet1/0/1.1] qinq termination pe-vid 10 ce-vid 1 to 100
[NPE1-GigabitEthernet1/0/1.1] ip address 10.1.1.254 24
[NPE1-GigabitEthernet1/0/1.1] arp broadcast enable
[NPE1-GigabitEthernet1/0/1.1] quit

# Configure NPE2.
NOTE
After the IP address is assigned to a sub-interface for QinQ VLAN tag termination, it is recommended to
run the arp broadcast enable command. Otherwise, the sub-interfaces for QinQ VLAN tag termination
fail to ping through each other.
# After the configuration, the sub-interfaces for QinQ VLAN tag termination in the same network
segment on NPE1 and NPE2 can ping through each other across the VPLS convergence network.
It indicates that the link between NPE1 and NPE2 works normally. Take the ping between NPE1
and NPE2 as an example.
The interfaces of NPE1 and NPE2 where the mVRRP backup group is configured can ping
through each other.
[NPE1] ping 10.1.1.253

0.00% packet loss
The interfaces of NPE1 and NPE2 where the service VRRP backup group is configured can ping
through each other.

[NPE1] ping 10.100.1.253

--- 10.100.1.253 ping statistics ---

0.00% packet loss
The NPE and the CE in the same network segment can ping through each other. It indicates that
the link between the NPE and the CE works normally. Take the ping between NPE1 and CE1
or between NPE2 and CE1 as an example.
[NPE1] ping 10.100.1.1

0.00% packet loss
[NPE2] ping 10.100.1.1


0.00% packet loss
Step 2 Configure basic VRRP functions on the sub-interfaces for QinQ VLAN tag termination of NPE1
and NPE2.
# On NPE1, configure the mVRRP backup group with VRID being 10 on GE 1/0/1.1 and
configure the service VRRP backup group on other sub-interfaces.
[NPE1-GigabitEthernet1/0/1.1] qinq vrrp pe-vid 10 ce-vid 100
[NPE1-GigabitEthernet1/0/1.1] vrrp vrid 10 virtual-ip 10.1.1.1
[NPE1-GigabitEthernet1/0/1.1] vrrp vrid 10 priority 120
[NPE1-GigabitEthernet1/0/1.1] admin-vrrp vrid 10

# On NPE2, configure the mVRRP backup group with VRID being 10 on GE 1/0/1.1 and
configure the service VRRP backup group on other sub-interfaces.
[NPE2-GigabitEthernet1/0/1.1] admin-vrrp vrid 10
After the previous configurations, run the display vrrp brief command on NPE1 and NPE2.
The command output is as follows:
On NPE1:
l For the VRRP backup group with the VRID being 10, State is Master and Type is Admin.
l For the VRRP backup group with the VRID not being 10, Type is Normal.
[NPE1] display vrrp brief
VRID State Interface Type Virtual IP
--------------------------------------------------------
10 Master GE1/0/1.1 Admin 10.1.1.1
100 Master GE1/0/1.100 Normal 10.100.1.200
101 Master GE1/0/1.101 Normal 10.101.1.200
102 Master GE1/0/1.102 Normal 10.102.1.200
103 Master GE1/0/1.103 Normal 10.103.1.200
On NPE2:
l For the VRRP backup group with the VRID being 10, State is Backup and Type is Admin.
l For the VRRP backup group with the VRID not being 10, Type is Normal.
--------------------------------------------------------
10 Backup GE1/0/1.1 Admin 10.1.1.1
100 Backup GE1/0/1.100 Normal 10.100.1.200
101 Backup GE1/0/1.101 Normal 10.101.1.200
102 Backup GE1/0/1.102 Normal 10.102.1.200
103 Backup GE1/0/1.103 Normal 10.103.1.200
Step 3 Bind the service VRRP backup group to the mVRRP backup group on NPE1 and NPE2.
# Configure NPE1.
[NPE1-GigabitEthernet1/0/1.100] vrrp vrid 100 track admin-vrrp interface

gigabitethernet1/0/1.1 vrid 10 unflowdown

# Configure NPE2.
On NPE1:
l For the VRRP backup group with the VRID not being 10, State is Master and Type is Member.
--------------------------------------------------------
10 Master GE1/0/1.1 Admin 10.1.1.1
100 Master GE1/0/1.100 Member 10.100.1.200
101 Master GE1/0/1.101 Member 10.101.1.200
102 Master GE1/0/1.102 Member 10.102.1.200
103 Master GE1/0/1.103 Member 10.103.1.200
On NPE2:
l For the VRRP backup group with the VRID not being 10, State is Backup and Type is
Member.
--------------------------------------------------------
10 Backup GE1/0/1.1 Admin 10.1.1.1
100 Backup GE1/0/1.100 Member 10.100.1.200
101 Backup GE1/0/1.101 Member 10.101.1.200
102 Backup GE1/0/1.102 Member 10.102.1.200
103 Backup GE1/0/1.103 Member 10.103.1.200

At that time, the service VRRP backup group is bound to the mVRRP backup group and their
respective status is normal.
Step 4 Configure basic BFD functions on NPE1 and NPE2.
# Configure the peer BFD session between NPE1 and NPE2; configure the link BFD session
between NPE1 and each CE and between NPE2 and each CE.
# Configure NPE1.
[NPE1] bfd
[NPE1-bfd] quit
[NPE1] bfd peer1 bind peer-ip 10.1.1.253 interface gigabitethernet1/0/1.1 source-ip
10.1.1.254 auto
[NPE1-bfd-session-peer1] commit
[NPE1-bfd-session-peer1] quit
[NPE1] bfd link1 bind peer-ip 10.100.1.1 interface gigabitethernet1/0/1.100 source-
ip 10.100.1.254 auto
[NPE1-bfd-session-link1] commit
[NPE1-bfd-session-link1] quit
ip 10.101.1.254 auto
ip 10.102.1.254 auto
ip 10.103.1.254 auto
# Configure NPE2.
[NPE2] bfd
[NPE2-bfd] quit
[NPE2] bfd peer1 bind peer-ip 10.1.1.254 interface gigabitethernet1/0/1.1 source-ip
10.1.1.253 auto
ip 10.100.1.253 auto
ip 10.101.1.253 auto
ip 10.102.1.253 auto
ip 10.103.1.253 auto
After the previous configurations are finished and the CE is correctly configured with the BFD
session, run the display bfd configuration all command on the NPE. The command output
shows that Commit is True.
# Take NPE1 as an example.
[NPE1] display bfd configuration all
--------------------------------------------------------------------------------
CFG Name CFG Type LocalDiscr MIndex SessNum Commit AdminDown
--------------------------------------------------------------------------------

peer1 S_AUTO_IF 8192 256 1 True False

link1 S_AUTO_IF 8193 257 1 True False
--------------------------------------------------------------------------------
Total Commit/Uncommit CFG Number : 5/0
Run the display bfd session all command. The command output shows that State is Up.
[NPE1] display bfd session all
--------------------------------------------------------------------------------
Local Remote PeerIpAddr State Type InterfaceName
--------------------------------------------------------------------------------
8192 8192 10.1.1.253 Up S_AUTO_IF GigabitEthernet1/0/1.1
--------------------------------------------------------------------------------
Step 5 Configure VRRP fast switchover using BFD sampling.

NOTE
Since the service VRRP backup group is bound to the mVRRP backup group, it is only required to configure
the mVRRP backup group on GE 1/0/1.1 of NPE1 and NPE2 to implement VRRP fast switchover using
BFD sampling.
# Configure NPE1.
[NPE1-GigabitEthernet1/0/1.1] vrrp vrid 10 track bfd-session session-name peer1
peer
[NPE1-GigabitEthernet1/0/1.1] vrrp vrid 10 track bfd-session session-name link1
link
link
link
link
[NPE1-GigabitEthernet1/0/1.1] vrrp vrid 10 track link-bfd down-number 2
[NPE1-GigabitEthernet1/0/1.1] vrrp trigger route
# Configure NPE2.
[NPE2-GigabitEthernet1/0/1.1] vrrp vrid 10 track bfd-session session-name peer1
peer
link
link
link
link
[NPE2-GigabitEthernet1/0/1.1] vrrp vrid 10 track link-bfd down-number 2
[NPE2-GigabitEthernet1/0/1.1] vrrp trigger route
After the previous configurations, run the display vrrp interface command on the NPE. The
command output shows that, the allowable maximum number of the link BFD sessions in the
Down state tracked by the mVRRP backup group is 2, the mVRRP backup group is bound to
one peer BFD session and four link BFD sessions, and the status of all BFD sessions is Up.

[NPE1] display vrrp interface gigabitethernet1/0/1.1

State : Master
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Check TTL : YES
Create time : 2010-06-22 17:33:00
Last change time : 2010-06-22 17:33:06
[NPE2] display vrrp interface gigabitethernet1/0/1.1
State : Backup
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Check TTL : YES
Create time : 2010-06-22 17:35:00
Last change time : 2010-06-22 17:35:06

On NPE1:
--------------------------------------------------------
10 Master GE1/0/1.1 Admin 10.1.1.1

100 Master GE1/0/1.100 Member 10.100.1.200

101 Master GE1/0/1.101 Member 10.101.1.200
102 Master GE1/0/1.102 Member 10.102.1.200
103 Master GE1/0/1.103 Member 10.103.1.200
On NPE2:
Member.
--------------------------------------------------------
10 Backup GE1/0/1.1 Admin 10.1.1.1
100 Backup GE1/0/1.100 Member 10.100.1.200
101 Backup GE1/0/1.101 Member 10.101.1.200
102 Backup GE1/0/1.102 Member 10.102.1.200
103 Backup GE1/0/1.103 Member 10.103.1.200
On NPE1, run the shutdown command on GE 1/0/1.100 to replicate the fault between NPE1
and CE1.
[NPE1-GigabitEthernet1/0/1.100] shutdown
The command output shows that the BFD session between NPE1 and CE1 goes Down.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
8193 0 10.100.1.1 Down S_AUTO_IF GigabitEthernet1/0/1.100
--------------------------------------------------------------------------------
In this configuration example, when two or more link BFD sessions go Down, the mVRRP
backup group performs master/backup fast switchover.
Currently, only one link BFD session is Down, so the mVRRP backup group does not perform
On NPE1:
l For the VRRP backup group with the VRID being 100, State is Initialize and Type is Member.
l For the VRRP backup group with the VRID not being 10 or 100, State is Master and Type
is Member.
--------------------------------------------------------
10 Master GE1/0/1.1 Admin 10.1.1.1
100 Initialize GE1/0/1.100 Member 10.100.1.200
101 Master GE1/0/1.101 Member 10.101.1.200
102 Master GE1/0/1.102 Member 10.102.1.200
103 Master GE1/0/1.103 Member 10.103.1.200
On NPE2:

Member.
--------------------------------------------------------
10 Backup GE1/0/1.1 Admin 10.1.1.1
100 Backup GE1/0/1.100 Member 10.100.1.200
101 Backup GE1/0/1.101 Member 10.101.1.200
102 Backup GE1/0/1.102 Member 10.102.1.200
103 Backup GE1/0/1.103 Member 10.103.1.200
and CE2.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
In this configuration example, the threshold for the number of link BFD sessions in the Down
state tracked by the mVRRP backup group is 2. That is, when two or more link BFD sessions
go Down, the mVRRP backup group performs master/backup fast switchover.
Currently, two link BFD sessions go Down, so the mVRRP backup group performs master/
backup switchover.
On NPE1:
l For the VRRP backup group with the VRID being 10, State is Initialize and Type is Admin.
l For the VRRP backup group with the VRID not being 10, State is Initialize and Type is
Member.
--------------------------------------------------------
10 Initialize GE1/0/1.1 Admin 10.1.1.1
On NPE2:
--------------------------------------------------------
10 Master GE1/0/1.1 Admin 10.1.1.1
100 Master GE1/0/1.100 Member 10.100.1.200
101 Master GE1/0/1.101 Member 10.101.1.200

102 Master GE1/0/1.102 Member 10.102.1.200

103 Master GE1/0/1.103 Member 10.103.1.200
On NPE1, run the undo shutdown command on GE 1/0/1.100 and GE1/0/1.101 to replicate the
recovery of the fault between NPE1 and CE1 or between NPE1 and CE2.
The command output shows that the BFD sessions between NPE1 and CE1 and between NPE1
and CE2 go Up.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
It indicates that the statuses of VRRP backup groups on NPE1 and NPE2 recover.
On NPE1:
--------------------------------------------------------
10 Master GE1/0/1.1 Admin 10.1.1.1
100 Master GE1/0/1.100 Member 10.100.1.200
101 Master GE1/0/1.101 Member 10.101.1.200
102 Master GE1/0/1.102 Member 10.102.1.200
103 Master GE1/0/1.103 Member 10.103.1.200
On NPE2:
Member.
--------------------------------------------------------
10 Backup GE1/0/1.1 Admin 10.1.1.1
100 Backup GE1/0/1.100 Member 10.100.1.200
101 Backup GE1/0/1.101 Member 10.101.1.200
102 Backup GE1/0/1.102 Member 10.102.1.200
103 Backup GE1/0/1.103 Member 10.103.1.200
----End
Configuration Files
l Configuration file of NPE1
#
sysname NPE1
#
bfd
#
undo shutdown
mode user-termination
#

control-vid 1 qinq-termination
qinq termination pe-vid 10 ce-vid 1 to 100
qinq vrrp pe-vid 10 ce-vid 100
ip address 10.1.1.254 255.255.255.0
admin-vrrp vrid 10
vrrp vrid 10 track bfd-session session-name link1 link
vrrp vrid 10 track bfd-session session-name peer1 peer
vrrp vrid 10 track link-bfd down-number 2
vrrp trigger route
arp broadcast enable
#
ip address 10.100.1.254 255.255.255.0
vrrp vrid 100 track admin-vrrp interface GigabitEthernet1/0/1.1 vrid 10
unflowdown
#
ip address 10.101.1.254 255.255.255.0
unflowdown
#
ip address 10.102.1.254 255.255.255.0
unflowdown
#
ip address 10.103.1.254 255.255.255.0
unflowdown
#
bfd link1 bind peer-ip 10.100.1.1 interface GigabitEthernet1/0/1.100 source-ip
10.100.1.254 auto
commit
#
10.101.1.254 auto
commit
#
10.102.1.254 auto
commit
#


10.103.1.254 auto
commit
#
bfd peer1 bind peer-ip 10.1.1.253 interface GigabitEthernet1/0/1.1 source-ip
10.1.1.254 auto
commit
#
return
#
sysname NPE2
#
bfd
#
undo shutdown
#
ip address 10.1.1.253 255.255.255.0
admin-vrrp vrid 10
vrrp trigger route
#
ip address 10.100.1.253 255.255.255.0
unflowdown
#
ip address 10.101.1.253 255.255.255.0
unflowdown
#
ip address 10.102.1.253 255.255.255.0
unflowdown
#

ip address 10.103.1.253 255.255.255.0

unflowdown
#
10.100.1.253 auto
commit
#
10.101.1.253 auto
commit
#
10.102.1.253 auto
commit
#
10.103.1.253 auto
commit
#
bfd peer1 bind peer-ip 10.1.1.254 interface GigabitEthernet1/0/1.1 source-ip
10.1.1.253 auto
commit
#
return
#
sysname PE1
#
mpls lsr-id 3.3.3.3
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 100
peer 4.4.4.4
peer 5.5.5.5
#
mpls ldp
#
undo shutdown
ip address 200.1.34.3 255.255.255.0
mpls
mpls ldp
#
undo shutdown
#
vlan-type dot1q 10
l2 binding vsi ldp1
#
undo shutdown
ip address 200.1.35.3 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
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 200.1.34.0 0.0.0.255

network 200.1.35.0 0.0.0.255
#
return
#
sysname PE2
#
mpls lsr-id 4.4.4.4
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 100
peer 3.3.3.3
peer 5.5.5.5
#
mpls ldp
#
undo shutdown
ip address 200.1.34.4 255.255.255.0
mpls
mpls ldp
#
undo shutdown
#
vlan-type dot1q 10
l2 binding vsi ldp1
#
undo shutdown
ip address 200.1.45.4 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 4.4.4.4 0.0.0.0
network 200.1.34.0 0.0.0.255
network 200.1.45.0 0.0.0.255
#
return
#
sysname PE3
#
mpls lsr-id 5.5.5.5
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 100
peer 3.3.3.3
peer 4.4.4.4
#
mpls ldp
#

undo shutdown
#
vlan-type dot1q 10
l2 binding vsi ldp1
#
undo shutdown
ip address 200.1.35.5 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 200.1.45.5 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 5.5.5.5 0.0.0.0
network 200.1.35.0 0.0.0.255
network 200.1.45.0 0.0.0.255
#
return
l Configuration file of CE
#
sysname CE1
#
bfd
#
undo shutdown
#
qinq termination pe-vid 10 ce-vid 110
ip address 10.100.1.1 255.255.255.0
#
ip address 10.101.1.1 255.255.255.0
#
ip address 10.102.1.1 255.255.255.0
#
ip address 10.103.1.1 255.255.255.0
#
bfd link11 bind peer-ip 10.100.1.254 interface GigabitEthernet1/0/1.100 source-
i
p 10.100.1.1 auto
commit
#
i

p 10.101.1.1 auto
commit
#
i
p 10.102.1.1 auto
commit
#
i
p 10.103.1.1 auto
commit
#
i
p 10.100.1.1 auto
commit
#
i
p 10.101.1.1 auto
commit
#
i
p 10.102.1.1 auto
commit
#
i
p 10.103.1.1 auto
commit
#
return
4.14.7 Example for Configuring Ignorance of the Down of an

Interface Where the mVRRP Backup Group Is Configured
In this example, by configuring mVRRP with the function of ignoring the interface Down event,
you can address the problem that an mVRRP backup group and a peer BFD session cannot be
configured between NPEs.
NOTE
As shown in Figure 4-11, the CE connects to the sub-interface for QinQ termination of the NPE
across the VPLS convergence network.
the mVRRP backup group implements master/backup fast switchover by tracking the BFD
session.
In this configuration example, the following restrictions are imposed on the network:
cannot be directly established between NPE1 and PE1 and between NPE2 and PE2.
l In the VPLS convergence network, the PW is established only between PE1 and PE3 and
between PE1 and PE2. According to the VPLS split horizon rule, the mVRRP backup group
or the peer BFD session cannot be established between NPE1 and NPE2.

In this scenario, you can use the function of ignorance of interface down to implement VRRP
fast switchover.
NOTE
l With BFD sampling, the NPE establishes link BFD sessions with each CE.
l ignore-if-down: If the status of the interface where the mVRRP backup group is configured is Down,
the status of the mVRRP backup group is switched to Master rather than Initialize.
For the NPE:

l NPE1 and NPE2 establish the mVRRP backup group and peer BFD session through their
respective interfaces Eth-Trunk1.
l NPE1 and NPE2 establish the service VRRP backup group through their respective
interfaces GE 1/0/1 that connect to the VPLS convergence network.
l NPE1 or NPE2 establishes four link BFD sessions respectively with four CEs through GE
1/0/1. The mVRRP backup group is responsible for tracking the status of the four BFD
sessions concurrently. When two or more link BFD sessions go Down, the mVRRP backup
group performs master/backup fast switchover.

Figure 4-11 Typical networking of ignorance of the down of an interface where the mVRRP
backup group is configured
Aggregation
Access VPLS Network Core
#
ipaddress 10.100.1.254 255.255.255.0
#
ipaddress 10.101.1.254 255.255.255.0
#
IP:10.100.1.1/24 interface GigabitEthernet1/0/1.102
ipaddress 10.102.1.254 255.255.255.0
GW:10.100.1.200 v rrpv rid 102 v irtual-ip10.102.1.200
Inner VLAN:110 #
#
Outer VLAN: 10 interface GigabitEthernet1/0/1.103
interface Eth-Trunk 1.1
ipaddress 10.103.1.254 255.255.255.0
CE1 v rrpv rid 103 v irtual-ip10.103.1.200 ipaddress 10.1.1.254 255.255.255.0
# v rrp v rid 10 v irtual-ip 10.1.1.1
#
NPE1
CE2
IP:10.101.1.1/24
GW:10.101.1.200
Inner VLAN:210 PW PE1
Outer VLAN: 10 Peer MPLS/IP
Link BFD
BFD Core
PW PE2
CE3
PE3
IP:10.102.1.1/24
GW:10.102.1.200
Inner VLAN:310
Outer VLAN: 10 NPE2
#
interface Eth-Trunk 1.1
# ipaddress 10.1.1.253 255.255.255.0
CE4 interface GigabitEthernet1/0/1.100 v rrp v rid 10 v irtual-ip 10.1.1.1
ipaddress 10.100.1.253 255.255.255.0 admin-v rrp v rid 10
IP:10.103.1.1/24 v rrpv rid 100 v irtual-ip10.100.1.200 #
GW:10.103.1.200 #
Inner VLAN:410 interface GigabitEthernet1/0/1.101
ipaddress 10.101.1.253 255.255.255.0
Outer VLAN: 10 v rrpv rid 101 v irtual-ip10.101.1.200
#
ipaddress 10.102.1.253 255.255.255.0
#
ipaddress 10.103.1.253 255.255.255.0
#

1. Configure the sub-interface for QinQ VLAN tag termination on NPE1 and NPE2.
2. Configure the mVRRP backup group and service VRRP backup group on the sub-interfaces
for QinQ VLAN tag termination of NPE1 and NPE2 and bind the service VRRP backup
group with the mVRRP backup group.
3. Establish the BFD session between NPE1 and NPE2 and between the NPE and the CE.
4. Configure master/backup fast switchover of the mVRRP backup group using BFD
sampling.
Data Preparation
l Virtual Router IDs (VRIDs) and virtual IP addresses
Procedure
Step 1 Configure the Eth-Trunk interface on NPE1 and NPE2.
NOTE
Only the configuration procedures of NPE1 and NPE2 are provided here. For the configuration procedures
of the BFD function of the CE as shown in Figure 4-10 and the VPLS convergence network, refer to the
HUAWEI NetEngine80E/40E Router Configuration Guide - Reliability and Configuration Guide - VPN.
# Configure NPE1.
[NPE1] interface Eth-Trunk 1
[NPE1-Eth-Trunk1] quit
[NPE1-GigabitEthernet1/0/2] eth-trunk 1
# Configure NPE2.
[NPE2] interface Eth-Trunk 1
Step 2 Configure the sub-interface for QinQ VLAN tag termination on NPE1 and NPE2.
# Configure NPE1.

[NPE1] interface eth-trunk 1

[NPE1-Eth-Trunk1] mode user-termination
[NPE1-Eth-Trunk1] undo shutdown
[NPE1] interface eth-trunk 1.1
[NPE1-Eth-Trunk1.1] control-vid 1 qinq-termination
[NPE1-Eth-Trunk1.1] qinq termination pe-vid 10 ce-vid 1 to 100
[NPE1-Eth-Trunk1.1] ip address 10.1.1.254 24
[NPE1-Eth-Trunk1.1] arp broadcast enable
[NPE1-Eth-Trunk1.1] quit
# Configure NPE2.
[NPE2] interface eth-trunk 1
[NPE2-Eth-Trunk1] mode user-termination
[NPE2-Eth-Trunk1.1] control-vid 1 qinq-termination
[NPE2-Eth-Trunk1.1] qinq termination pe-vid 10 ce-vid 1 to 100
[NPE2-Eth-Trunk1.1] ip address 10.1.1.253 24
[NPE2-Eth-Trunk1.1] arp broadcast enable


NOTE
After the IP address is assigned to a sub-interface for QinQ VLAN tag termination, it is recommended to
run the arp broadcast enable command. Otherwise, the sub-interfaces for QinQ VLAN tag termination
fail to ping through each other.
# After the configuration, the IP address of Eth-Trunk1.1 on NPE1 and the IP address of Eth-
Trunk1.1 of NPE2 can ping through each other. It indicates that the link between NPE1 and
NPE2 works normally. Take the ping between NPE1 and NPE2 as an example.
The interfaces where the mVRRP backup group is configured can ping through each other.
[NPE1] ping 10.1.1.253

0.00% packet loss
According to the split horizon rule of the VPLS convergence network, the interfaces of NPE1
and NP2 where the service VRRP backup group is configured cannot ping through each other.
Take GE 1/0/1.100 of NPE1 as an example:
[NPE1] ping 10.100.1.253
Request time out
Request time out
Request time out
Request time out
Request time out

100.00% packet loss
The NPE and the CE in the same network segment can ping through each other. It indicates that
the link between the NPE and the CE works normally. Take the ping between NPE1 and CE1
or between NPE2 and CE1 as an example.
[NPE1] ping 10.100.1.1

0.00% packet loss

[NPE2] ping 10.100.1.1


0.00% packet loss
Step 3 Configure basic VRRP functions on the sub-interfaces for QinQ VLAN tag termination of NPE1
and NPE2.
NOTE
l In this configuration example, you need to specify the keyword ignore-if-down in using the admin-
vrrp command. Thus, when the interface where the VRRP backup group is configured goes Down,
the status of the VRRP backup group is switched to Master.
l If unspecified, when Eth-Trunk1.1 on NPE1 goes Down because of a fault, Eth-Trunk1.1 on NPE2
goes Down accordingly and the status of the VRRP backup group configured on this interface is
switched from Backup to Initialize, thus failing to implement VRRP fast switchover.
l In the scenario as shown in Figure 4-11, if NPE1 is not faulty, it is not recommended to run the
shutdown command on Eth-Trunk1.1 on NPE1. Otherwise, the mVRRP backup groups on NPE1 and
NPE2 both become the Master status, causing service interruption.
l In all networking environments except the scenario as shown in , it is not recommended to use the
keyword ignore-if-down. Otherwise, the state machine of the VRRP backup group is inconsistent with
that defined in RFC.
# On NPE1, configure the mVRRP backup group with VRID being 10 on Eth-Trunk1.1 and
configure the service VRRP backup group on the sub-interfaces of GE 1/0/1.
[NPE1-Eth-Trunk1.1] qinq vrrp pe-vid 10 ce-vid 100
[NPE1-Eth-Trunk1.1] vrrp vrid 10 virtual-ip 10.1.1.1
[NPE1-Eth-Trunk1.1] vrrp vrid 10 priority 120
[NPE1-Eth-Trunk1.1] admin-vrrp vrid 10 ignore-if-down
# On NPE2, configure the mVRRP backup group with VRID being 10 on Eth-Trunk1.1 and
configure the service VRRP backup group on the sub-interfaces of GE 1/0/1.
[NPE2-Eth-Trunk1.1] qinq vrrp pe-vid 10 ce-vid 100
[NPE2-Eth-Trunk1.1] vrrp vrid 10 virtual-ip 10.1.1.1

[NPE2-Eth-Trunk1.1] admin-vrrp vrid 10 ignore-if-down

On NPE1:
l For the VRRP backup group with the VRID not being 10, State is Master and Type is Normal.
--------------------------------------------------------
10 Master Eth-Trunk1.1 Admin 10.1.1.1
100 Master GE1/0/1.100 Normal 10.100.1.200
101 Master GE1/0/1.101 Normal 10.101.1.200
102 Master GE1/0/1.102 Normal 10.102.1.200
103 Master GE1/0/1.103 Normal 10.103.1.200
On NPE2:
l For the VRRP backup group with the VRID not being 10, State is Master and Type is Normal.
--------------------------------------------------------
10 Backup Eth-Trunk1.1 Admin 10.1.1.1
100 Master GE1/0/1.100 Normal 10.100.1.200
101 Master GE1/0/1.101 Normal 10.101.1.200
102 Master GE1/0/1.102 Normal 10.102.1.200
103 Master GE1/0/1.103 Normal 10.103.1.200
NOTE
According to the split horizon rule of the VPLS convergence network, VRRP packets cannot be exchanged
between the service VRRP backup groups of NPE1 and NPE2. Hence, the status of the service VRRP
backup groups of NPE1 and NPE2 is Master.
Step 4 Bind the service VRRP backup group to the mVRRP backup group on NPE1 and NPE2.
# Configure NPE1.
[NPE1-GigabitEthernet1/0/1.100] vrrp vrid 100 track admin-vrrp interface eth-
trunk1.1 vrid 10 unflowdown


# Configure NPE2.
NPE2] interface gigabitethernet1/0/1.103
On NPE1:
--------------------------------------------------------
100 Master GE1/0/1.100 Member 10.100.1.200
101 Master GE1/0/1.101 Member 10.101.1.200
102 Master GE1/0/1.102 Member 10.102.1.200
103 Master GE1/0/1.103 Member 10.103.1.200
On NPE2:
Member.
--------------------------------------------------------
100 Backup GE1/0/1.100 Member 10.100.1.200
101 Backup GE1/0/1.101 Member 10.101.1.200
102 Backup GE1/0/1.102 Member 10.102.1.200
103 Backup GE1/0/1.103 Member 10.103.1.200
At that time, the service VRRP backup group is bound to the mVRRP backup group and their
status is normal.
NOTE
After the binding is finished, the service VRRP backup group no longer sends VRRP packets. The status
of the service VRRP backup group is the same as the status of the bound mVRRP backup group.

Step 5 Configure basic BFD functions on NPE1 and NPE2.

# Configure the peer BFD session between NPE1 and NPE2; configure the link BFD session
between NPE1 and each CE and between NPE2 and each CE.
# Configure NPE1.
[NPE1] bfd
[NPE1-bfd] quit
[NPE1] bfd peer1 bind peer-ip 10.1.1.253 interface eth-trunk 1.1 source-ip
10.1.1.254 auto
ip 10.100.1.254 auto
ip 10.101.1.254 auto
ip 10.102.1.254 auto
ip 10.103.1.254 auto
# Configure NPE2.
[NPE2] bfd
[NPE2-bfd] quit
[NPE2] bfd peer1 bind peer-ip 10.1.1.254 interface eth-trunk 1.1 source-ip
10.1.1.253 auto
ip 10.100.1.253 auto
ip 10.101.1.253 auto
ip 10.102.1.253 auto
ip 10.103.1.253 auto
After the previous configurations are finished and the CE is correctly configured with the BFD
session, run the display bfd configuration all command on the NPE. The command output
shows that Commit is True.
[NPE1] display bfd configuration all
--------------------------------------------------------------------------------
CFG Name CFG Type LocalDiscr MIndex SessNum Commit AdminDown
--------------------------------------------------------------------------------
peer1 S_AUTO_IF 8192 4096 1 True False


--------------------------------------------------------------------------------
Total Commit/Uncommit CFG Number : 5/0
Run the display bfd session all command on NPE1 to view the status of the BFD session. The
command output shows that State is Up.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
8192 8192 10.1.1.253 Up S_AUTO_IF Eth-Trunk1.1
--------------------------------------------------------------------------------
Step 6 Configure VRRP fast switchover using BFD sampling.

NOTE
Since the service VRRP backup group is bound to the mVRRP backup group, it is only required to configure
the mVRRP backup group on Eth-Trunk1.1 of NPE1 and NPE2 to implement VRRP fast switchover using
BFD sampling.
# Configure NPE1.
[NPE1-Eth-Trunk1.1] vrrp vrid 10 track bfd-session session-name peer1 peer
[NPE1-Eth-Trunk1.1] vrrp vrid 10 track bfd-session session-name link1 link
[NPE1-Eth-Trunk1.1] vrrp vrid 10 track link-bfd down-number 2
[NPE1-Eth-Trunk1.1] vrrp trigger route
# Configure NPE2.
[NPE2-Eth-Trunk1.1] vrrp vrid 10 track bfd-session session-name peer1 peer
[NPE2-Eth-Trunk1.1] vrrp vrid 10 track link-bfd down-number 2
[NPE2-Eth-Trunk1.1] vrrp trigger route
After the configuration, run the display vrrp interface command on NPE1 and NPE2. The
command output shows that the mVRRP backup group is bound to one peer BFD session and
four link BFD sessions and the BFD session status is Up.
[NPE1] display vrrp interface eth-trunk 1.1
Eth-Trunk1.1 | Virtual Router 10
State : Master
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : NONE

Check TTL : YES

Track BFD : link1 type : link
Track BFD : peer1 type : peer
Create time : 2010-06-22 17:33:00
Last change time : 2010-06-22 17:33:06
[NPE2] display vrrp interface eth-trunk 1.1
Eth-Trunk1.1 | Virtual Router 10
State : Backup
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Check TTL : YES
Track BFD : peer1 type : peer
Create time : 2010-06-22 17:35:00
Last change time : 2010-06-22 17:35:06
On NPE1:
--------------------------------------------------------
100 Master GE1/0/1.100 Member 10.100.1.200
101 Master GE1/0/1.101 Member 10.101.1.200
102 Master GE1/0/1.102 Member 10.102.1.200
103 Master GE1/0/1.103 Member 10.103.1.200
On NPE2:
Member.


--------------------------------------------------------
100 Backup GE1/0/1.100 Member 10.100.1.200
101 Backup GE1/0/1.101 Member 10.101.1.200
102 Backup GE1/0/1.102 Member 10.102.1.200
103 Backup GE1/0/1.103 Member 10.103.1.200
and CE1.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Currently, only one link BFD session is Down, so the mVRRP backup group does not perform
On NPE1:
l For the VRRP backup group with the VRID being 100, State is Initialize and Type is Member.
----------------------------------------------------------
101 Master GE1/0/1.101 Member 10.101.1.200
102 Master GE1/0/1.102 Member 10.102.1.200
103 Master GE1/0/1.103 Member 10.103.1.200
On NPE2:
Member.
--------------------------------------------------------
100 Backup GE1/0/1.100 Member 10.100.1.200
101 Backup GE1/0/1.101 Member 10.101.1.200
102 Backup GE1/0/1.102 Member 10.102.1.200
103 Backup GE1/0/1.103 Member 10.103.1.200

and CE2.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Currently, two link BFD sessions go Down, so the mVRRP backup group performs master/
backup switchover.
On NPE1:
l For the VRRP backup group with the VRID being 10, State is Initialize and Type is Admin.
l For the VRRP backup group with the VRID not being 10, State is Initialize and Type is
Member.
-----------------------------------------------------------
10 Initialize Eth-Trunk1.1 Admin 10.1.1.1
On NPE2:
----------------------------------------------------------
100 Master GE1/0/1.100 Member 10.100.1.200
101 Master GE1/0/1.101 Member 10.101.1.200
102 Master GE1/0/1.102 Member 10.102.1.200
103 Master GE1/0/1.103 Member 10.103.1.200
On NPE1, run the undo shutdown command on GE 1/0/1.100 and GE1/0/1.101 to replicate the
recovery of the fault between NPE1 and CE1 and between NPE1 and CE2.
[NPE1-GigabitEthernet1/0/1.100] undo shutdown
[NPE1-GigabitEthernet1/0/1.101] undo shutdown

The command output shows that the BFD sessions between NPE1 and CE1 and between NPE1
and CE2 go Up.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
It indicates that the statuses of the VRRP backup groups on NPE1 and NPE2 recover
respectively.
On NPE1:
--------------------------------------------------------
100 Master GE1/0/1.100 Member 10.100.1.200
101 Master GE1/0/1.101 Member 10.101.1.200
102 Master GE1/0/1.102 Member 10.102.1.200
103 Master GE1/0/1.103 Member 10.103.1.200
On NPE2:
l For the VRRP backup group with the VRID not being 10, State is and Type is Member.
--------------------------------------------------------
100 Backup GE1/0/1.100 Member 10.100.1.200
101 Backup GE1/0/1.101 Member 10.101.1.200
102 Backup GE1/0/1.102 Member 10.102.1.200
103 Backup GE1/0/1.103 Member 10.103.1.200
----End
Configuration Files
#
sysname NPE1
#
bfd
#
interface Eth-Trunk1
#
interface Eth-Trunk1.1
ip address 10.1.1.254 255.255.255.0
admin-vrrp vrid 10 ignore-if-down


vrrp trigger route
#
undo shutdown
#
ip address 10.100.1.254 255.255.255.0
vrrp vrid 100 track admin-vrrp interface Eth-Trunk1.1 vrid 10 unflowdown
#
ip address 10.101.1.254 255.255.255.0
#
ip address 10.102.1.254 255.255.255.0
#
ip address 10.103.1.254 255.255.255.0
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
10.100.1.254 auto
commit
#
10.101.1.254 auto
commit
#
10.102.1.254 auto
commit
#


10.103.1.254 auto
commit
#
bfd peer1 bind peer-ip 10.1.1.253 interface Eth-Trunk1.1 source-ip 10.1.1.254
auto
commit
#
return
#
sysname NPE2
#
bfd
#
#
interface Eth-Trunk1.1
ip address 10.1.1.253 255.255.255.0
admin-vrrp vrid 10 ignore-if-down
vrrp trigger route
#
undo shutdown
#
ip address 10.100.1.253 255.255.255.0
#
ip address 10.101.1.253 255.255.255.0
#
ip address 10.102.1.253 255.255.255.0
#

ip address 10.103.1.253 255.255.255.0

#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
10.100.1.253 auto
commit
#
10.101.1.253 auto
commit
#
10.102.1.253 auto
commit
#
10.103.1.253 auto
commit
#
bfd peer1 bind peer-ip 10.1.1.254 interface Eth-Trunk1.1 source-ip 10.1.1.253
auto
commit
#
return
#
sysname PE1
#
mpls lsr-id 3.3.3.3
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 100
peer 5.5.5.5
#
mpls ldp
#
undo shutdown
ip address 200.1.34.3 255.255.255.0
mpls
mpls ldp
#
undo shutdown
#
vlan-type dot1q 10
l2 binding vsi ldp1
#
undo shutdown
ip address 200.1.35.3 255.255.255.0
mpls
mpls ldp
#

interface LoopBack1
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 200.1.34.0 0.0.0.255
network 200.1.35.0 0.0.0.255
#
return
#
sysname PE2
#
mpls lsr-id 4.4.4.4
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 100
peer 5.5.5.5
#
mpls ldp
#
undo shutdown
ip address 200.1.34.4 255.255.255.0
mpls
mpls ldp
#
undo shutdown
#
vlan-type dot1q 10
l2 binding vsi ldp1
#
undo shutdown
ip address 200.1.45.4 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 4.4.4.4 0.0.0.0
network 200.1.34.0 0.0.0.255
network 200.1.45.0 0.0.0.255
#
return
#
sysname PE3
#
mpls lsr-id 5.5.5.5
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 100
peer 3.3.3.3
peer 4.4.4.4

#
mpls ldp
#
undo shutdown
#
vlan-type dot1q 10
l2 binding vsi ldp1
#
undo shutdown
ip address 200.1.35.5 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 200.1.45.5 255.255.255.0
mpls
mpls ldp
#
ip address 5.5.5.5 255.255.255.255
#
ospf 1
area 0.0.0.0
network 5.5.5.5 0.0.0.0
network 200.1.35.0 0.0.0.255
network 200.1.45.0 0.0.0.255
#
return
l Configuration file of CE
#
sysname CE1
#
bfd
#
undo shutdown
#
ip address 10.100.1.1 255.255.255.0
#
ip address 10.101.1.1 255.255.255.0
#
ip address 10.102.1.1 255.255.255.0
#
ip address 10.103.1.1 255.255.255.0
#
i
p 10.100.1.1 auto
commit

#
i
p 10.101.1.1 auto
commit
#
i
p 10.102.1.1 auto
commit
#
i
p 10.103.1.1 auto
commit
#
i
p 10.100.1.1 auto
commit
#
i
p 10.101.1.1 auto
commit
#
i
p 10.102.1.1 auto
commit
#
i
p 10.103.1.1 auto
commit
#
return
4.14.8 Example for Configuring VRRP on VLANIF Interfaces

In this example, by creating a VRRP backup group on VLANIF interfaces, you can implement
the fast VRRP switchover.
As shown in Figure 4-12, the networking requirements are as follows:
l Router A and Router B work in backup mode. Router A functions as the master and Router
B as the backup.
l Network 1 belongs to VLAN 10 and Network 2 belongs to VLAN 20. Both Router A and
Router B connect all networks through LAN switches.
l Network 1, Network 2, and Network 3 respectively correspond to the virtual IP addresses
10.1.1.1, 10.1.2.1, and 100.10.1.1 of the three backup groups.

Figure 4-12 Networking diagram of VRRP configured on VLANIF interfaces

Backup group 1
Virtual IP Address
10.1.1.1/24
VLAN10 RouterA
Network1 Master
GE1/0/1 GE3/0/
0
/2 VLAN30
/0
E1 Eth-Trunk1 Network3
GGE
1/
0/
1
GE1/0/2 GE3/0/0
VLAN20 RouterB
Slave
Network2 Backup group 3
Backup group 2
Virtual IP Address Virtual IP Address
100.10.1.1/24
10.1.2.1/24
Both Router A and Router B are connected to Network1, Network2, and Network3 through GE
1/0/1, GE 1/0/2, and GE 3/0/0.
Router A and Router B are connected through Eth-Trunk 1, including member interfaces GE
2/0/0 and GE 2/0/1.
1. Configure IP addresses for the interfaces of the physical interfaces and VLANIF interfaces.
2. Configure MSTP.
3. Create VRRP backup groups and set priorities.
Data Preparation
l IP addresses of physical interfaces and VLANIF interfaces
l Name of the domain RG 1 that Router A and Router B join
Procedure
Step 1 Configure IP addresses for the interfaces of Router A and Router B.
# Take Router A as an example: Create VLAN 10 and VLAN 20. Add GE 1/0/1 to VLAN 10
and GE 1/0/2 to VLAN 20.

[RouterA-GigabitEthernet1/0/1] portswitch
[RouterA-GigabitEthernet3/0/0] ip address 100.10.1.2 255.255.255.0
[RouterA] vlan 10
[RouterA-vlan10] port gigabitethernet 1/0/1
[RouterA-vlan10] interface vlanif10
[RouterA-vlanif10] ip address 10.1.1.2 255.255.255.0
[RouterA-vlanif10] quit
[RouterA] vlan 20
[RouterA-vlan20] interface vlanif20
[RouterA-vlanif20] ip address 10.1.2.2 255.255.255.0
# Configure Router A to connect Router B through an Eth-Trunk.

[RouterA] interface eth-trunk1
[RouterA-Eth-Trunk1] quit
[RouterA-GigabitEthernet2/0/0] eth-trunk1
[RouterA-GigabitEthernet2/0/1] eth-trunk1
[RouterA] interface eth-trunk1
[RouterA-Eth-Trunk1] portswitch
[RouterA-Eth-Trunk1] port link-type trunk
[RouterA-Eth-Trunk1] port trunk allow-pass vlan 10 20
The configurations of Router B are the same as those of Router A.

Step 2 Configure MSTP.
# Configure the MST region on Router A.
[RouterA] stp region-configuration
[RouterA-mst-region] region-name RG1
[RouterA-mst-region] instance 1 vlan 10
[RouterA-mst-region] instance 2 vlan 20
# Activate the MST region configuration.

[RouterA-mst-region] active region-configuration
[RouterA-mst-region] quit
# Configure the priority of Router A so that it functions as the root bridge.

[RouterA] stp instance 1 priority 0
# Activate the MST region configuration.

[RouterA] interface Eth-Trunk1
[RouterA-Eth-Trunk1] stp enable
[RouterA] interface GigabitEthernet1/0/1
[RouterA-GigabitEthernet1/0/1] stp enable


Step 3 Configure the backup groups for Router A and Router B.
# Take Router A as an example: Configure the VRRP backup groups on the interfaces of Router
A.
[RouterA] interface vlanif10
[RouterA-vlanif10] vrrp vrid 1 virtual-ip 10.1.1.1
[RouterA-vlanif10] vrrp vrid 1 priority 130
[RouterA-vlanif20] vrrp vrid 2 virtual-ip 10.1.2.1
[RouterA-vlanif20] vrrp vrid 2 priority 130

Run the display vrrp command on Router A and Router B to view information about the VRRP
backup groups.
State : Master
PriorityRun : 130
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0102
Check TTL : YES
Create time : 2010-06-22 17:33:00
Last change time : 2010-06-22 17:33:06
State : Master
PriorityRun : 130
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Create time : 2010-06-22 17:32:00
Last change time : 2010-06-22 17:33:06
State : Backup
PriorityRun : 100
TimerRun : 1

TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0102
Check TTL : YES
Create time : 2010-06-22 17:35:00
Last change time : 2010-06-22 17:35:06
State : Backup
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Create time : 2010-06-22 17:34:00
Last change time : 2010-06-22 17:34:06
# Run the shutdown command on VLANIF 10 of Router A to simulate a link fault.

[RouterA-Vlanif10] quit
At this time, run the display vrrp command on Router A, and you can view that the status of
Router A in back group 1 is Initialize.
State : Master
PriorityRun : 130
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0102
Check TTL : YES
Create time : 2010-06-22 17:33:00
Last change time : 2010-06-22 17:33:06
State : Initialize
PriorityRun : 130
MasterPriority : 0
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Create time : 2010-06-22 17:36:00
Last change time : 2010-06-22 17:36:06
Run the display vrrp command on Router B, and you can view that the status of Router B in
back group 1 is Master.


State : Backup
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0102
Check TTL : YES
Create time : 2010-06-22 17:35:00
Last change time : 2010-06-22 17:35:06
State : Master
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Create time : 2010-06-22 17:37:00
Last change time : 2010-06-22 17:37:06
----End
Configuration Files
#
sysname RouterA
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
ip address 100.10.1.2 255.255.255.0
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
interface Vlanif10
ip address 10.1.1.3 255.255.255.0


#
interface vlanif20
undo shutdown
ip address 10.1.2.2 255.255.255.0
#
return
#
interface eth-trunk1
undo shutdown
port link-type trunk
port trunk allow-pass vlan 10 20
#
stp region-configuration
region-name RG1
instance 1 vlan 10
instance 2 vlan 20
active region-configuration
#
Return
#
sysname RouterB
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
ip address 100.10.1.2 255.255.255.0
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
interface vlanif10
undo shutdown
ip address 10.1.1.3 255.255.255.0
#
interface vlanif20
undo shutdown
ip address 10.1.2.3 255.255.255.0
#
return
#
interface eth-trunk1
undo shutdown
port link-type trunk
port trunk allow-pass vlan 10 20
#

stp region-configuration
region-name RG1
instance 1 vlan 10
instance 2 vlan 20
active region-configuration
#
return
4.14.9 Example for Configuring VRRP on Sub-interfaces for QinQ

VLAN Tag Termination to Reduce the Number of Gratuitous ARP
Packets to Be Sent
The default gateway of VLAN users is a VRRP backup group. Reducing the number of gratuitous
ARP packets to be sent by the master device in the VRRP backup group lightens burden on the
master device.
As shown in Figure 4-13, VLAN 10 and VLAN 20 users access an ISP network through a default
gateway. The IP address of the default gateway is the virtual IP address of VRRP backup group
1. Router A is the master device. The sub-interface for QinQ VLAN tag termination on
Router A sends gratuitous ARP packets to all VLANs specified by outer VLAN IDs and inner
VLAN IDs. In this example, as one VLAN is specified in the outer tag and two VLANs (VLAN
10 and VLAN 20) are specified in the inner tag in each packet, two gratuitous ARP packets
carrying VLAN 10 and VLAN 20 respectively will be sent to refresh the VRRP backup group's
MAC address entry on a downstream switch. If a wide range of VLAN IDs is specified in the
inner tags, a large number of gratuitous ARP packets will be sent, thus exposing a heavy burden
on Router A. In this case, Router A needs to send one double-tagged gratuitous ARP packet
carrying only inner VLAN 10 to lighten burden on Router A.

Figure 4-13 Networking diagram of configuring VRRP on sub-interfaces for QinQ VLAN tag
termination to reduce the number of gratuitous ARP packets to be sent
MPLS/IP
backbone
POS1/0/0
192.168.2.2/24 POS1/0/1
192.168.1.2/24
POS1/0/0 RouterC POS1/0/0
192.168.2.1/24 192.168.1.1/24
RouterA RouterB
GE2/0/0.110.1.1.3/24 GE2/0/0.110.1.1.4/24
VRRP backup group 1
SwitchC
GE1/0/2 GE1/0/3
GE1/0/0 GE1/0/1
GE1/0/1
SwitchA GE1/0/1 SwitchB
GE1/0/0 GE1/0/0
VLAN10 VLAN20
Host1:10.1.1.1/24 Host2:10.1.1.2/24
1. Configure the interface mode on Router A and Router B as user termination.
2. Configure an IGP to ensure connectivity between Router A, Router B, and Router C.
3. Configure sub-interfaces for QinQ VLAN tag termination on Router A and Router B.
4. Configure VRRP backup group 1 on GE 2/0/0.1 of Router A and on GE 2/0/0.1 of
Router B, ensuring that Router A functions as the master device and Router B functions as
the backup device.
5. Configure QinQ on Switch C to enable Switch C to send double-tagged packets to
Router A and Router B.
6. Configure the Layer 2 forwarding function on each switch.
Data Preparation
l VRID of a VRRP backup group, virtual IP address, priority of each router in the VRRP
backup group

l Tag values of sub-interfaces for QinQ VLAN tag termination
Procedure
Step 1 Configure the interface mode as user termination.
[RouterA-GigabitEthernet2/0/0] mode user-termination
[RouterB-GigabitEthernet2/0/0] mode user-termination
Step 2 Configure an IGP to enable connectivity between Routers. In this example, OSPF is adopted.
[RouterA] interface pos 1/0/0
[RouterA-Pos1/0/0] undo shutdown
[RouterA-Pos1/0/0] ip address 192.168.2.1 24
[RouterA-Pos1/0/0] quit
[RouterA] interface gigabitethernet 2/0/0.1
[RouterA-GigabitEthernet2/0/0.1] undo shutdown
[RouterA-GigabitEthernet2/0/0.1] ip address 10.1.1.3 24
[RouterA-GigabitEthernet2/0/0.1] quit
[RouterA] ospf
[RouterA-ospf-1] area 0
[RouterA-ospf-1-area-0.0.0.0] network 192.168.2.0 0.0.0.255
[RouterA-ospf-1-area-0.0.0.0] quit
[RouterA-ospf-1] quit
[RouterB-Pos1/0/0] undo shutdown
[RouterB-Pos1/0/0] ip address 192.168.1.1 24
[RouterB] interface gigabitethernet 2/0/0.1
[RouterB-GigabitEthernet2/0/0.1] undo shutdown
[RouterB-GigabitEthernet2/0/0.1] ip address 10.1.1.4 24
[RouterB-GigabitEthernet2/0/0.1] quit
[RouterB] ospf
[RouterB-ospf-1] area 0
[RouterB-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255
[RouterB-ospf-1-area-0.0.0.0] quit
[RouterB-ospf-1] quit
# Configure Router C.
[RouterC] interface pos 1/0/0
[RouterC-Pos1/0/0] undo shutdown
[RouterC-Pos1/0/0] ip address 192.168.2.2 24
[RouterC-Pos1/0/0] quit


[RouterC-Pos1/0/1] ip address 192.168.1.2 24
[RouterC] ospf
[RouterC-ospf-1] area 0
[RouterC-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255
[RouterC-ospf-1-area-0.0.0.0] quit
[Router3-ospf-1] quit
After the preceding configuration, Router A and Router B obtain the routes to each other through
OSPF. In addition, they can successfully ping each other.

[RouterA] display ip routing-table
------------------------------------------------------------------------------
10.1.1.0/24 Direct 0 0 D 10.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.2/32 Direct 0 0 D 192.168.2.2 Pos1/0/0
Router A and Router B successfully ping each other.

[RouterA] ping 192.168.1.1
0.00% packet loss
Step 3 Configure VRRP on sub-interfaces for QinQ VLAN tag termination.
# Configure Router A, ensuring that Router A functions as the master device.

[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] qinq vrrp pe-vid 100 ce-vid 10
[RouterA-GigabitEthernet2/0/0.1] vrrp vrid 1 virtual-ip 10.1.1.100
[RouterA-GigabitEthernet2/0/0.1] vrrp vrid 1 priority 120
[RouterA-GigabitEthernet2/0/0.1] vrrp arp send-mode simple
# Configure Router B, ensuring that Router B functions as the backup device.

[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] qinq vrrp pe-vid 100 ce-vid 10
[RouterB-GigabitEthernet2/0/0.1] vrrp vrid 1 virtual-ip 10.1.1.100
[RouterB-GigabitEthernet2/0/0.1] vrrp arp send-mode simple

After the preceding configuration, GE 2/0/0.1 on Router A and GE 2/0/0.1 on Router B go Up,
and a route is generated on Router C to the network segment 10.1.1.0/24. Take the display on
Router C as an example:
[RouterC] display ip routing-table
------------------------------------------------------------------------------
10.1.1.0/24 OSPF 10 2 D 192.168.1.1 Pos1/0/1

10.1.1.100/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
Step 4 Configure the Layer 2 forwarding function.

# Configure Switch A.
[HUAWEI] sysname SwitchA
[SwitchA] vlan 10
[SwitchA-vlan10] port gigabitethernet 1/0/0
[SwitchA-vlan10] quit
[SwitchA] interface gigabitethernet 1/0/1
[SwitchA-GigabitEthernet1/0/1] port trunk allow-pass vlan 10
[SwitchA-GigabitEthernet1/0/1] undo shutdown
[SwitchA-GigabitEthernet1/0/1] quit
# Configure Switch B.
[HUAWEI] sysname SwitchB
[SwitchB] vlan 20
[SwitchB-vlan20] port gigabitethernet 1/0/0
[SwitchB-vlan20] quit
[SwitchB] interface gigabitethernet 1/0/1
[SwitchB-GigabitEthernet1/0/1] port trunk allow-pass vlan 20
[SwitchB-GigabitEthernet1/0/1] undo shutdown
[SwitchB-GigabitEthernet1/0/1] quit
Step 5 Configure QinQ on Switch C to enable Switch C to send double-tagged packets to Router A and
Router B.
# Configure Switch C.
[HUAWEI] sysname SwitchC
[SwitchC] vlan 100
[SwitchC-vlan100] quit
[SwitchC] interface gigabitethernet 1/0/0
[SwitchC-GigabitEthernet1/0/0] undo shutdown
[SwitchC-GigabitEthernet1/0/0] port vlan-stacking vlan 10 stack-vlan 100
[SwitchC-GigabitEthernet1/0/0] quit


[SwitchC-GigabitEthernet1/0/2] port trunk allow-pass vlan 100
NOTE
If Switch C does not support the port vlan-stacking command, use the port link-type dot1q-tunnel and
port default vlan commands to configure QinQ.

l After the preceding configuration, run the display vrrp command on Router A and then
Router B. You can view that Router A's VRRP status is Master and Router B's VRRP status
is Backup in VRRP backup group 1.
state : Master
Virtual IP : 10.1.1.100
PriorityRun : 120
Timer : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Create time : 2010-07-09 17:32:56
Last change time : 2010-07-09 17:33:00
state : Backup
Virtual IP : 10.1.1.100
PriorityRun : 100
Timer : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Config track link-bfd down-number 0
Create time : 2010-07-09 17:33:06
Last change time : 2010-07-09 17:33:10
l Check that Router B becomes the master device after Router A fails.
Run the shutdown command on GE 2/0/0.1 of Router A to simulate a fault.
Run the display vrrp command on Router A and then Router B. You can view that the VRRP
status of Router A is Initialize and the VRRP status of Router B is Master.
state : Initialize
Virtual IP : 10.1.1.100
PriorityRun : 120
MasterPriority : 0
Timer : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES


Create time : 2010-07-09 17:32:56
Last change time : 2010-07-09 17:33:30
state : Master
Virtual IP : 10.1.1.100
PriorityRun : 100
Timer : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Config track link-bfd down-number 0
Create time : 2010-07-09 17:33:06
Last change time : 2010-07-09 17:33:40
----End
Configuration Files
#
sysname RouterA
#
undo shutdown
#
undo shutdown
ip address 10.1.1.3 255.255.255.0
vrrp arp send-mode simple
#
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 10.1.1.0 0.0.0.255
#
return

#
sysname RouterB
#
undo shutdown
#
undo shutdown

ip address 10.1.1.4 255.255.255.0

vrrp arp send-mode simple
#
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 10.1.1.0 0.0.0.255
#
return
#
sysname RouterC
#
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 C
#
sysname SwitchC
#
vlan batch 100
#
undo shutdown
port vlan-stacking vlan 10 stack-vlan 100
#
undo shutdown
#
undo shutdown
port trunk allow-pass vlan 100
#
undo shutdown
#
return
l Configuration file of Switch A
#
sysname SwitchA
#
vlan batch 10
#
undo shutdown

#
undo shutdown
#
return
l Configuration file of Switch B

#
sysname SwitchB
#
vlan batch 20
#
undo shutdown
#
undo shutdown
#
return
4.14.10 Example for Configuring VRRP for IPv6 on Sub-interfaces

for QinQ VLAN Tag Termination to Reduce the Number of ND
Packets to Be Sent
The default gateway of VLAN users is a VRRP for IPv6 backup group. Commands are run to
reduce the number of ND packets to be sent by the master device in the VRRP for IPv6 backup
group, lightening the burden on the master device.
As shown in Figure 4-14, VLAN 10 and VLAN 20 users access an ISP network through a default
gateway. The IP address of the default gateway is the virtual IP address of VRRP for IPv6 backup
group 1. Router A is the master device. The sub-interface for QinQ VLAN tag termination on
Router A sends ND packets to all VLANs specified by outer VLAN IDs and inner VLAN IDs.
n this example, as one VLAN is specified in the outer tag and two VLANs (VLAN 10 and VLAN
20) are specified in the inner tag in each packet, two ND packets carrying VLAN 10 and VLAN
20 respectively will be sent to refresh the VRRP backup group's MAC address entry on a
downstream switch. If a wide range of VLAN IDs is specified in the inner tags, a large number
of ND packets will be sent, thus exposing a heavy burden on Router A. In this case, Router A
needs to send one double-tagged ND packet carrying only inner VLAN 10 to lighten burden on
Router A.

Figure 4-14 Networking diagram of configuring VRRP for IPv6 on sub-interfaces for QinQ
VLAN tag termination to reduce the number of ND packets to be sent
MPLS/IP
backbone
POS1/0/0
2001::2/64 POS1/0/1
2002::2/64
POS1/0/0 RouterC POS1/0/0
2001::1/64 2002::1/64
RouterA RouterB
GE2/0/0.1 2000::3/64 GE2/0/0.1 2000::4/64
VRRP6 backup
group 1
SwitchC
GE1/0/2 GE1/0/3
GE1/0/0 GE1/0/1
GE1/0/1
SwitchA GE1/0/1 SwitchB
GE1/0/0 GE1/0/0
VLAN10 VLAN20
Host1:2000::1/64 Host2:2000::2/64
1. Configure the interface mode on Router A and Router B as user termination.
4. Configure VRRP for IPv6 backup group 1 on GE 2/0/0.1 of Router A and on GE 2/0/0.1
of Router B. Ensure that Router A functions as the master device and Router B functions
as the backup device.
5. Configure QinQ on Switch C to enable Switch C to send double-tagged packets to
6. Configure the Layer 2 forwarding function on each switch.
Data Preparation
l VRID of a VRRP for IPv6 backup group, virtual IPv6 address, priority of each router in
the VRRP backup group

l Tag values of sub-interfaces for QinQ VLAN tag termination
Procedure
Step 2 Configure an IGP to enable connectivity between Routers. In this example, OSPFv3 is adopted.
[RouterA] ipv6
[RouterA] ospfv3
[RouterA-ospfv3-1] router-id 1.1.1.1
[RouterA-ospfv3-1] quit
[RouterA-Pos1/0/0] ipv6 enable
[RouterA-Pos1/0/0] ipv6 address 2001::1 64
[RouterA-Pos1/0/0] ospfv3 1 area 0
[RouterA-GigabitEthernet2/0/0.1] ipv6 enable
[RouterA-GigabitEthernet2/0/0.1] ipv6 address 2000::3 64
[RouterA-GigabitEthernet2/0/0.1] ospfv3 1 area 0
[RouterB] ipv6
[RouterB] ospfv3
[RouterB-ospfv3-1] router-id 2.2.2.2
[RouterB-ospfv3-1] quit
[RouterB-Pos1/0/0] ipv6 enable
[RouterB-Pos1/0/0] ipv6 address 2002::1 64
[RouterB-Pos1/0/0] ospfv3 1 area 0
[RouterB-GigabitEthernet2/0/0.1] ipv6 enable
[RouterB-GigabitEthernet2/0/0.1] 2000::4 64
[RouterB-GigabitEthernet2/0/0.1] ospfv3 1 area 0

[RouterC] ipv6
[RouterC] ospfv3
[RouterC-ospfv3-1] router-id 3.3.3.3
[RouterC-ospfv3-1] quit
[RouterC-Pos1/0/0] ipv6 enable
[RouterC-Pos1/0/0] 2001::2 64
[RouterC-Pos1/0/0] ospfv3 1 area 0
[RouterC-Pos1/0/1] ipv6 enable
[RouterC-Pos1/0/1] 2002::2 64
[RouterC-Pos1/0/1] ospfv3 1 area 0
After the preceding configuration, Router A and Router B obtain the routes to each other through
OSPFv3. In addition, they successfully ping each other.

[RouterA] display ospfv3 routing
OSPFv3 Process (1)
Destination Metric
Next-hop
2000::/64 1
directly connected, GigabitEthernet2/0/0.1
2001::/64 1
directly connected, Pos1/0/0
2002::/64 2
via FE80::217D:7E4B:5888:1, Pos1/0/1
[RouterA] ping ipv6 2002::2
PING 2002::2 : 56 data bytes, press CTRL_C to break
Reply from 2002::2
bytes=56 Sequence=1 hop limit=64 time = 14 ms
Reply from 2002::2
Reply from 2002::2
Reply from 2002::2
Reply from 2002::2
--- 2002::2 ping statistics ---

0.00% packet loss
Step 3 Configure VRRP for IPv6 on sub-interfaces for QinQ VLAN tag termination.
# Configure Router A. Ensure that Router A functions as the master device.

[RouterA-GigabitEthernet2/0/0.1] qinq termination pe-vid 100 ce-vid 10 to 20
[RouterA-GigabitEthernet2/0/0.1] vrrp6 vrid 1 virtual-ip FE80::1 link-local
[RouterA-GigabitEthernet2/0/0.1] vrrp6 vrid 1 virtua-ip 2000::100
[RouterA-GigabitEthernet2/0/0.1] vrrp6 vrid 1 priority 120
[RouterA-GigabitEthernet2/0/0.1] vrrp6 nd send-mode simple
# Configure Router B. Ensure that Router B functions as the backup device.


[RouterB-GigabitEthernet2/0/0.1] qinq termination pe-vid 100 ce-vid 10 to 20

[RouterB-GigabitEthernet2/0/0.1] vrrp6 vrid 1 virtual-ip FE80::1 link-local
[RouterB-GigabitEthernet2/0/0.1] vrrp6 vrid 1 virtua-ip 2000::100
[RouterB-GigabitEthernet2/0/0.1] vrrp6 nd send-mode simple
Step 4 Configure the Layer 2 forwarding function.

# Configure Switch A.
[HUAWEI] sysname SwitchA
[SwitchA] vlan 10
[SwitchA-vlan10] port gigabitethernet 1/0/0
[SwitchA-vlan10] quit
[SwitchA] interface gigabitethernet 1/0/1
[SwitchA-GigabitEthernet1/0/1] port trunk allow-pass vlan 10
[SwitchA-GigabitEthernet1/0/1] undo shutdown
[SwitchA-GigabitEthernet1/0/1] quit
# Configure Switch B.
[HUAWEI] sysname SwitchB
[SwitchB] vlan 20
[SwitchB-vlan20] port gigabitethernet 1/0/0
[SwitchB-vlan20] quit
[SwitchB] interface gigabitethernet 1/0/1
[SwitchB-GigabitEthernet1/0/1] port trunk allow-pass vlan 20
[SwitchB-GigabitEthernet1/0/1] undo shutdown
[SwitchB-GigabitEthernet1/0/1] quit
Step 5 Configure QinQ on Switch C to enable Switch C to send double-tagged packets to Router A and
Router B.
# Configure Switch C.
[HUAWEI] sysname SwitchC
[SwitchC] vlan 100
[SwitchC-vlan100] quit
NOTE
If Switch C does not support the port vlan-stacking command, use the port link-type dot1q-tunnel and
port default vlan commands to configure QinQ.

l After the preceding configuration, run the display vrrp6 command on Router A and then
Router B. You can view that Router A's VRRP status is Master and Router B's VRRP status
is Backup in VRRP for IPv6 backup group 1.

[RouterA] display vrrp6

State : Master
Virtual IP : FE80::1
2000::100
PriorityRun : 120
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
Create time : 2010-07-09 17:10:56
Last change time : 2010-07-09 17:11:00
[RouterB] display vrrp6
State : Backup
2000::100
PriorityRun : 100
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
Create time : 2010-07-09 17:11:24
Last change time : 2010-07-09 17:11:28
l Check that Router B becomes the master device after Router A fails.
# Run the shutdown command on GE 2/0/0.1 of Router A to simulate a fault.
Run the display vrrp6 command on Router A and then Router B. You can view that the
VRRP status of Router A is Initialize and the VRRP status of Router B is Master.
[RouterA] display vrrp6
State : Initialize
2000::100
PriorityRun : 120
MasterPriority : 0
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
Create time : 2010-07-09 17:10:56
Last change time : 2010-07-09 17:12:06
[RouterB] display vrrp6
State : Master
2000::100
PriorityRun : 100
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201


Accept Mode : ON
Create time : 2010-07-09 17:11:24
Last change time : 2010-07-09 17:12:34
----End
Configuration Files
#
sysname RouterA
#
ipv6
#
ospfv3 1
router-id 1.1.1.1
#
undo shutdown
#
undo shutdown
ipv6 enable
ipv6 address 2000::3/64
vrrp6 vrid 1 virtual-ip FE80::1 link-local
vrrp6 vrid 1 virtua-ip 2000::100
vrrp6 nd send-mode simple
ospfv3 1 area 0
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ipv6 enable
ospfv3 1 area 0
#
return

#
sysname RouterB
#
ipv6
#
ospfv3 1
router-id 2.2.2.2
#
undo shutdown
#
undo shutdown
undo shutdown
ipv6 enable
ipv6 address 2000::4 64/64
vrrp6 vrid 1 virtua-ip 2000::100

vrrp6 nd send-mode simple

ospfv3 1 area 0
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ipv6 enable
ospfv3 1 area 0
#
return
#
sysname RouterC
#
ipv6
#
ospfv3 1
router-id 3.3.3.3
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ipv6 enable
2001::2/64
ospfv3 1 area 0
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ipv6 enable
2002::2/64
ospfv3 1 area 0
#
return
l Configuration file of Switch C
#
sysname SwitchC
#
vlan batch 100
#
undo shutdown
#
undo shutdown
#
undo shutdown
#
undo shutdown
#
return
l Configuration file of Switch A
#
sysname SwitchA
#
vlan batch 10
#
undo shutdown

#
undo shutdown
#
return
l Configuration file of Switch B

#
sysname SwitchB
#
vlan batch 20
#
undo shutdown
#
undo shutdown
#
return
4.14.11 Example for Configuring a VRRP6 Backup Group in Master/

Backup Mode
Network Requirements
NOTE
As shown in Figure 4-15, Host A accesses Host B through the default gateway with the IPv6
address being 2000::100.
The networking is required as follows:
l Router A and Router B form backup group 1, and the IPv6 address of backup group 1 is
the default gateway address used by Host A.
l Normally, Router A functions as a gateway. When Router A fails, Router B becomes the
gateway.
l After Router A recovers from the fault, it can preempt the master router within 20 seconds.

Figure 4-15 Networking diagram of a VRRP6 backup group in master/backup mode

Backup group 1
Virtual IP Address
2000::100
RouterA
Master
POS1/0/0
2002::1/64
GE1/0/0
2000::1/64 POS1/0/0
2002::2/64
Eth3/0/0
RouterC
2003::2/64
HostA HostB
2000::3/64 POS2/0/0 2003::1/64
2001::2/64
POS1/0/0
GE1/0/0
2001::1/64
2000::2/64 RouterB
Etherent Backup
1. Create backup group 1 on GE 1/0/0 of Router A; configure Router A with the highest
priority to ensure that Router A is the master router; enable the preemption mode.
2. Create backup group 1 on GE 1/0/0 of Router B and configure Router B with the default
priority being 100 to ensure that Router B is the backup router.
Data Preparation
l IPv6 address of each interface
l ID and virtual IPv6 address of each VRRP6 backup group
l Priority of each router in each VRRP6 backup group
Procedure
Step 1 Configure each host. The configurations are not mentioned here.
Set the default gateway address used by Host A to 2000::100 and the default gateway address
used bt Host B to 2003::2.
Step 2 Enable OSPFv3 on Router A, Router B, and Router C to interwork them. The configurations
are not mentioned here.
Step 3 Configure a VRRP6 backup group.
# Assign an IPv6 address to GE 1/0/0 on Router A. Create VRRP6 backup group 1 on GE 1/0/0.
Configure Router A with the priority being 120 to ensure that Router A is the master router.

[RouterA] ipv6
[RouterA-GigabitEthernet1/0/0] ipv6 enable
[RouterA-GigabitEthernet1/0/0] ipv6 address 2000::1 64
[RouterA-GigabitEthernet1/0/0] vrrp6 vrid 1 virtual-ip FE80::1 link-local
[RouterA-GigabitEthernet1/0/0] vrrp6 vrid 1 virtual-ip 2000::100
[RouterA-GigabitEthernet1/0/0] vrrp6 vrid 1 priority 120
[RouterA-GigabitEthernet1/0/0] vrrp6 vrid 1 preempt-mode timer delay 20
# Assign an IPv6 address to GE 1/0/0 on Router B. Create VRRP6 backup group 1 on GE 1/0/0.
Configure Router B with the default priority being 100 to ensure that Router B is the backup
router.
[RouterB] ipv6
[RouterB-GigabitEthernet1/0/0] ipv6 enable
[RouterB-GigabitEthernet1/0/0] ipv6 address 2000::2 64
[RouterB-GigabitEthernet1/0/0] vrrp6 vrid 1 virtual-ip FE80::1 link-local
[RouterB-GigabitEthernet1/0/0] vrrp6 vrid 1 virtual-ip 2000::100
After the preceding configurations, Host A can ping Host B. Run the display vrrp6 command
on Router A. You can view that Router A is in the Master state in the VRRP6 backup group.
Run the display vrrp6 command on Router B. You can view that Router B is in the Backup
state in the VRRP6 backup group.
<RouterA> display vrrp6
State : Master
2000::100
PriorityRun : 120
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
<RouterB> display vrrp6
State : Backup
2000::100
PriorityRun : 100
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
# Run the shutdown command on GE 1/0/0 of Router A to simulate a fault.

Run the display vrrp6 command on Router A. You can view that Router A is in the Initialize
state in the VRRP6 backup group. Run the display vrrp6 command on Router B. You can view
that Router B is in the Master state in the VRRP6 backup group.
State : Initialize
2000::100
PriorityRun : 120
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
<RouterB> display vrrp6
State : Master
2000::100
PriorityRun : 100
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
# Run the undo shutdown command on GE 1/0/0 of Router A. After GE 1/0/0 goes Up, wait
20 seconds and then run the display vrrp6 command on Router A to view the status of the
VRRP6 backup group. You can view that Router A restores the Master state in the VRRP6
backup group.
State : Master
2000::100
PriorityRun : 120
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
----End
Configuration Files
#
sysname RouterA
#
ipv6
#
ospfv3 1

router-id 1.1.1.1
#
undo shutdown
ipv6 enable
vrrp6 vrid 1 virtual-ip 2000::100
vrrp6 vrid 1 priority 120
vrrp6 vrid 1 preempt-mode timer delay 20
ospfv3 1 area 0.0.0.0
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ipv6 enable
#
return
#
sysname RouterB
#
ipv6
#
ospfv3 1
router-id 2.2.2.2
#
undo shutdown
ipv6 enable
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ipv6 enable
#
return
#
sysname RouterC
#
ipv6
#
ospfv3 1
router-id 3.3.3.3
#
undo shutdown
ipv6 enable
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ipv6 enable
ipv6 address 2002::2
#

interface Pos2/0/0
link-protocol ppp
undo shutdown
ipv6 enable
#
return
4.14.12 Example for Configuring VRRP6 Backup Groups in Load

Balancing Mode
Network Requirements
NOTE
As shown in Figure 4-16,

l Router A is the master router in backup group 1 and the backup router in backup group 2.
l Router B is the master router in backup group 2 and the backup router in backup group 1.
l Host A of a LAN uses the virtual IPv6 address of backup group 1 as a default gateway
address and Host B uses that of backup group 2. This can implement data flow load
balancing and mutual backup between these two backup groups.
Figure 4-16 Networking diagram of VRRP6 backup groups in load balancing mode
Backup group 1
Virtual IP Address
2000::100 RouterA
group 1:Master
group 2:Backup
POS1/0/0
2002::1/64
GE1/0/0
2000::1/64 POS1/0/0
HostA 2002::2/64
2000::3/64 Eth3/0/0
RouterC
2003::2
HostC
POS2/0/0 2003::1/64
2001::2/64
POS1/0/0
HostB GE1/0/0 2001::1/64
2000::4/64 2000::2/64 RouterA
Etherent group 1:Backup
Backup group 2 group 2:Master
Virtual IP Address
2000::60

1. Create backup group 1 and backup group 2 on GE 1/0/0 of Router A. Router A is the master
router in backup group 1 and the backup router in backup group 2.
2. Create backup group 1 and backup group 2 on GE 1/0/0 of Router B. Router B is the backup
router in backup group 1 and the master router in backup group 2.
Data Preparation
l IPv6 address of each interface
l ID and virtual IPv6 address of each backup group
l Priority of each router in each VRRP6 backup group
Procedure
Step 1 Configure each host. The configurations are not mentioned here.
Configure the default gateway address used by Host A as backup group 1's virtual IPv6 address
being 2000::100. Configure the default gateway address of Host B as backup group 2's virtual
IPv6 address being 2000::60. Configure the default gateway address of Host C as 2003::2.
Step 2 Enable OSPFv3 on Router A, Router B, and Router C to interwork them. The configurations
are not mentioned here.
Step 3 Configure each VRRP6 backup group.
# Assign an IPv6 address to GE 1/0/0 on Router A. Create backup group 1 and backup group 2
on GE 1/0/0 of Router A. Configure Router A with the priority being 120 to ensure that
Router A functions as the master router in backup group 1. Configure Router A with the default
priority being 100 to ensure that Router A functions as the backup router in backup group 2.
[RouterA] ipv6
[RouterA-GigabitEthernet1/0/0] vrrp6 vrid 1 priority 120
# Assign an IPv6 address to GE 1/0/0 on Router B. Create backup group 1 and backup group 2
on GE 1/0/0 of Router B. Configure Router B with the default priority being 100 to ensure that
Router B is the backup router in backup group 1. Configure Router B with the priority being
120 to ensure that Router B is the master router in backup group 2.
[RouterB] ipv6


[RouterB-GigabitEthernet1/0/0] vrrp6 vrid 2 priority 120

After the preceding configurations, both Host A and Host B can ping Host C. Run the display
vrrp6 command on Router A. You can view that backup group 1 and backup group 2 are created.
Router A is the master router in backup group 1 and the backup router in backup group 2.
State : Master
2000::100
PriorityRun : 120
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
State : Backup
2000::60
PriorityRun : 100
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0102
Accept Mode : ON
Run the display vrrp6 command on Router B. You can view that backup group 1 and backup
group 2 are created. Router B is the backup router in backup group 1 and the master router in
backup group 2.
<Router>A display vrrp6
State : Backup
2000::100
PriorityRun : 100
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
State : Master
2000::60
PriorityRun : 120

TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0102
Accept Mode : ON
----End
Configuration Files
#
sysname RouterA
#
ipv6
#
ospfv3 1
router-id 1.1.1.1
#
undo shutdown
ipv6 enable
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ipv6 enable
#
return

#
sysname RouterB
#
ipv6
#
ospfv3 1
router-id 1.1.1.1
#
undo shutdown
ipv6 enable
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ipv6 enable

#
return

#
sysname RouterC
#
ipv6
#
ospfv3 1
router-id 3.3.3.3
#
undo shutdown
ipv6 enable
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ipv6 enable
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ipv6 enable
#
return

Configuration Guide - Reliability 5 BFD Configuration
5 BFD Configuration
About This Chapter
A BFD session rapidly detects a link fault on a network.
5.1 Introduction to BFD

BFD rapidly detects the communication faults between the local device and its neighbor, which
minimizes the impact of the faults on services.
5.2 Configuring Single-hop BFD
A single-hop BFD session rapidly detects faults in direct links over a network.
5.3 Configuring the BFD Passive Echo Function
By configuring the BFD passive Echo function, you can implement the interworking between
the devices that support the Echo function. This function is applicable to only single-hop BFD
sessions.
5.4 Configuring the Association Between the BFD Status and the Interface Status
By associating the BFD session status with the interface status, you can trigger fast route
convergence. This function is applicable to only the BFD session that uses the default multicast
IP address to detect the single-hop link.
5.5 Configuring the Association Between the BFD Status and the Sub-Interface Status
By associating the BFD session status with the sub-interface status, you can trigger fast route
convergence. This function is applicable to the single-hop BFD session that detects default
multicast IP addresses.
5.6 Configuring the BFD to Modify the PST
By configuring a BFD session to modify the PST, you can speed up link fault detection by the
BFD session. This function is applicable to only single-hop BFD sessions.
5.7 Configuring the Multi-Hop BFD
By configuring a multi-hop BFD session, you can fast detect and monitor multi-hop links of a
network.
5.8 Configuring a BFD Session with Automatically Negotiated Discriminators
A static BFD session with automatically negotiated discriminators is configured to check the
interworking between a device and another device on which a BFD session is dynamically
established. The static BFD session with automatically negotiated discriminators is applicable
to static routes.

5.9 Configuring the Delay of a BFD Session to Go Up

In special scenarios, the delay of a BFD session to go Up is configured to prevent traffic loss as
a route protocol becomes Up later than an interface.
5.10 Configuring a BFD Session with the One-Arm Echo Function
By configuring a BFD session with the one-arm Echo function, you can fast detect and monitor
a direct link between a BFD-capable device and a BFD-incapable device.
5.11 Adjusting BFD Parameters
Adjusting BFD parameters enables a BFD session to check links on a network effectively and
quickly.
5.12 Globally Configuring the Destination Port Number for the Multi-Hop BFD Control Packet
By configuring a global destination port number for multi-hop BFD control packets, you can
implement the interworking between the local device and a device running an earlier version,
and between a Huawei device and a non-Huawei device.
5.13 Configuring the TTL Globally
Configuring the TTL globally helps you connect the current device and a device running an early
version.
5.14 Configuring the Interval at Which Trap Messages Are Sent
The interval at which trap messages are sent is set, helping a device to suppress BFD trap
messages.
5.15 Maintaining BFD
This section describes how to maintain BFD by deleting BFD statistics, and monitoring BFD
operation.
The following sections provide several examples for configuring fast BFD link detection.

5.1 Introduction to BFD

BFD rapidly detects the communication faults between the local device and its neighbor, which
minimizes the impact of the faults on services.
5.1.1 BFD Overview

BFD, a uniform detection mechanism for an entire network, rapidly detects faults and monitors
the forwarding and connectivity of links or IP routes of the network.
On a network, a link fault is detected in either of the following methods:
l Hardware detection signals, such as in the Synchronous Digital Hierarchy (SDH) alarm
function, are used to detect a link fault rapidly.
l If the preceding method is unavailable, the Hello mechanism of a routing protocol is used
to detect a fault.
The following problems exist in the preceding methods:

l Hardware is used by only part of mediums to detect faults.
l The routing protocol-specific Hello mechanism takes more than 1 second to detect a fault.
If data is forwarded at gigabit rates, a large amount of data is dropped.
l On a small-scale Layer 3 network, if no routing protocol is deployed, the routing protocol-
specific Hello mechanism does not detect a fault. This means that a fault between the
interconnected systems is hard to locate.
BFD is developed to resolve the preceding problems.
BFD provides the following functions:
l Detects faults rapidly in paths between neighboring forwarding engines, with light loads
and high speeds.
l Uses a single mechanism to monitor any medium and protocol layer in real time. In addition,
the detection time and costs are variable.
5.1.2 BFD Features Supported by the NE80E/40E

The VRP supports BFD sessions establishment modes, two detection modes (single-hop BFD
and multi-hop BFD), BFD passive Echo function, association between the BFD session status
and the interface status, dynamic modification of parameters, binding a BFD session to a VPN
instance, BFD for VRRP, BFD for static route, BFD for routing protocols, BFD for FRR, BFD
for IS-IS, BFD for LSP, BFD for PW, BFD for VSI PW, and BFD for PIM.
BFD, a unified detection mechanism, is used by multiple protocols.
This section briefly describes applications provided by BFD.
BFD Session Establishment Supported by the NE80E/40E

BFD uses local and remote discriminators to differentiate multiple BFD sessions between a pair
of systems. The local and remote discriminators are set in various modes. Based on these modes,
the following types of BFD sessions are supported by the NE80E/40E:

l Static BFD sessions with manually specified discriminators

l Static BFD sessions with automatically negotiated discriminators
l Dynamic BFD sessions triggered by a protocol
Discriminators of a dynamic BFD session triggered by a protocol are created as follows:
l Dynamically allocating the local discriminator
l Self-learning the remote discriminator
NOTE
On the NE80E/40E, OSPF, BGP, IS-IS, MPLS, MPLS LDP, RSVP-TE, PWE3, and PIM dynamically
trigger the establishment of BFD sessions.
The following conditions must be satisfied to allow two ends of a BFD session to create
discriminators in different modes:
l If a static BFD session is established by manually specifying the discriminators on one end,
the static BFD session on the other end must also be established by manually specifying
discriminators.
l If a static BFD session is established by automatically negotiating the discriminators on
one end, the static BFD session on the other end is established by automatically negotiating
discriminators or a dynamic BFD session is established.
l If both a static BFD session with automatically negotiated discriminators and a dynamic
BFD session are established on one end, the following principles are applicable:
– If these two sessions share the same configurations (the source address, destination
address, outgoing interface, and VPN index), one BFD session works as both the
dynamic BFD session and the static BFD session with automatically negotiated
discriminators.
– If the dynamic BFD session named DYN_local-discriminator is configured prior to the
static BFD session, the dynamic BFD session's name is replaced with the static BFD
session's name.
– Minimum values between these two sessions are used by the shared session.
At present, one BFD session working as both a dynamic BFD session and a static BFD session
with automatically negotiated discriminators is supported by BFD for OSPF, BFD for IS-IS,
BFD for BGP, BFD for PIM, and BFD for RSVP-TE.
BFD Modes
The NE80E/40E supports the asynchronous mode.
Asynchronous mode:
Each system sends BFD Control packets at a negotiated interval. If a system does not receive
BFD Control packets from the peer within the detection time, it sets the session to Down.
Single-hop BFD and Multi-hop BFD

The NE80E/40E supports single-hop BFD and multi-hop BFD which check the reachability of
IP routes. This section describes single-hop BFD.
The NE80E/40E supports single-hop BFD for the following types of links:
NOTE
IP-Trunk cannot be configured on the X1 and X2 models of the NE80E/40E.

l Layer 3 physical interfaces

l Ethernet sub-interfaces (including Eth-Trunk sub-interfaces)
If a physical Ethernet interface has multiple sub-interfaces, BFD sessions are separately
set up on the physical Ethernet interface and every sub-interface.
l Sub-interfaces for Dot1q VLAN tag termination and sub-interfaces for QinQ VLAN tag
termination
l IP-Trunk
– IP-Trunk link
– IP-Trunk member link
Separate BFD sessions can be established to detect faults in an IP-Trunk interface and its
member interfaces.
l Eth-Trunk
– Layer 2 Eth-Trunk link
– Layer 2 Eth-Trunk member link
– Layer 3 Eth-Trunk link
– Layer 3 Eth-Trunk member link
Separate BFD sessions can be established to detect faults in an Eth-Trunk and its member
interfaces.
NOTE
l Both IP-Trunk and Eth-Trunk links are composed of member links, providing high bandwidth and
reliability.
l When the number of trunk member links that are Up reaches a certain value, the trunk link keeps Up.
l For information about the IP-Trunk configuration, refer to the HUAWEI NetEngine80E/40E Router
Configuration Guide - WAN Access; for information about the Eth-Trunk configuration, refer to the
HUAWEI NetEngine80E/40E Router Configuration Guide - LAN Access and MAN Access.
l VLANIF
– Ethernet member links in a VLAN
– VLANIF interface
BFD sessions are separately created on a VLANIF interface and its VLANIF member
interfaces to detect faults in the VLANIF and VLANIF member interfaces simultaneously.
One-arm Echo Function

If BFD-capable device is directly connected to a BFD-incapable device, a BFD session with the
one-arm Echo function is configured on the BFD-capable device to rapidly detect a fault in a
link between the two devices. The BFD-capable device initiates a request by sending a BFD
Echo packet to the BFD-incapable device. After receiving the packet, the BFD-incapable device
directly loops back the packet. This allows BFD to detect faults in the direct link between the
two devices.
NOTE
The one-arm Echo function is applicable to only single-hop BFD sessions.

Figure 5-1 Networking diagram of the one-arm Echo function
RouterA RouterB
BFD-capable BFD-incapable
On the network shown in Figure 5-1, Router A supports BFD but Router B does not. A BFD
session with the one-arm Echo function is configured on Router A, detecting the single-hop link
between Router A and Router B. After receiving a BFD Echo packet sent by Router A, Router
B loops back the packet at the IP layer, rapidly detecting the connectivity of the direct link
between Router A and Router B.
Association Between the BFD Status and the Interface Status

If a transmission device exists on a direct link, BFD detects a link fault faster than a fault detection
mechanism provided by a link protocol on an interface. The link protocol status of the trunk
interface or the VLAN interface depends on the link protocol status of member interfaces.
To help BFD more rapidly notify an application of detection results, a BFD status attribute is
added to the interface management module on every interface. This attribute indicates the status
of the BFD session that is bound to the interface (on a sub-interface, this attribute indicates the
status of the BFD session that is bound to the main interface). The system obtains the interface
status based on the link status, protocol status, and BFD status on the interface, and then notifies
the application of the result.
Association between the BFD status and the interface status means that if the BFD session status
changes, the BFD status on the interface in the IFNET module is modified. This function is
applicable only to a single-hop BFD session that is bound to the outgoing interface and uses the
default multicast address. Association is classified into the following modes:
l Association between the BFD status and the status of an interface to which BFD is bound
– If a BFD session goes Down, the BFD status on the interface to which the BFD session
is bound goes Down, and this status change is reported to an application on the interface.
If the BFD session on a trunk member interface or a VLAN member interface goes
Down, the link protocol status of the trunk or VLAN member interface also changes.
This accelerates the change in the link protocol status and the route convergence.
NOTE
On a trunk interface whose trunk member interfaces reside on different LPUs, when a BFD
session is created to detect faults in links between trunk member interfaces, the process-pst
command is used to associate the BFD session with the status of the interface. Otherwise, traffic
may be dropped in some situations. For example, an LPU where the trunk member interface
resides is restarted.
– When the BFD session is Up, the BFD status on the interface bound to the BFD session
also goes Up.

This function helps the BFD detection results be reported more rapidly to an application.
l Association between the BFD status and the status of a sub-interface of a main interface
bound to which the BFD session is bound
The BFD session must be bound to the main interface.
– If the BFD session goes Down, the BFD statuses on the bound interface and all sub-
interfaces go Down. The status change is reported to the application on the sub-interface.
The services such as L2VPN configured on the sub-interface use detection results of
the BFD session.
– If the BFD session goes Up, the BFD statuses on the interface to which the BFD session
is bound to and all the sub-interfaces also go Up.
This function saves the session resources in the system and provides reliability for more
applications. This function is typically used on the network where high reliability is required
and a great number of services are configured on the sub-interface, such as a large-scale
MAN Ethernet.
Changing Detection Parameters Dynamically

After a BFD session is set up, detection parameters can be changed, such as the minimum sending
interval, minimum receiving interval, or detecting mode, without affecting the current session
status.
Binding a VPN Instance

On the NE80E/40E, a BFD session is bound to a VPN instance, allowing BFD Control packets
to be forwarded in a specified VPN.
BFD for VRRP

BFD checks the reachability of links or IP routes on a network, triggering fast VRRP
switchovers.
NOTE
For the detailed configuration of BFD for VRRP, see the chapter "VRRP Configuration."
BFD for Static Route

Static routes do not have a detection mechanism. If a network fails, an administrator needs to
troubleshoot the fault.
BFD for static route allows a BFD session to detect the status of an IPv4 static route on the public
network. The routing management system determines whether or not the static route is available
based on the BFD session status.
NOTE
For the detailed configuration of BFD for static routes, refer to chapter "IP Static Route Configuration" in
the HUAWEI NetEngine80E/40E Router Configuration Guide - IP Routing.
BFD for Routing Protocols

BFD uses a local discriminator and a remote discriminator to identify multiple BFD sessions
between one pair of systems. BDF sessions for IS-IS are dynamically or statically created; BDF
sessions for BGP and OSPF are dynamically created.

A BFD session dynamically triggered by a routing protocol is implemented as follows:

l Dynamically allocating the local discriminator
l Self-learning the remote discriminator
After a routing protocol-specific neighbor relationship is established successfully, a routing
protocol triggers the establishment of a BFD session by using a routing management module
and the BFD session rapidly checks the protocol-specific neighbor relationship. Detection
parameters of BFD sessions are configured by a routing protocol.
If a BFD session detects a failure, the session goes Down, and BFD triggers route convergence
through a routing management module.
NOTE
A routing protocol implements second-level detection by using Hello messages based on the keepalive
mechanism, and BFD implements millisecond-level detection at intervals of 10 milliseconds with the
detection multiplier being 3. BFD advertises a protocol failure within 50 milliseconds, which speeds up
route convergence.
If a neighbor is unreachable, a routing protocol instructs BFD to delete the session by through
a routing management module.
BFD for Fast Reroute

l BFD for LDP FRR
MPLS uses software for forwarding. BFD detects faults in the protected interfaces. LDP
FRR switchover is triggered if a BFD session is Down.
l BFD for IP FRR and BFD for VPN FRR
On NE80E/40Es, IP FRR and VPN FRR switchovers are triggered only after detected faults
are reported to the control plane.
l BFD provides reliability for MPLS-based applications, such as VPN FRR, TE FRR, and
VLL FRR, to protect services.
BFD for IS-IS

On the NE80E/40E, a static BFD session is used to check the IS-IS neighbor relationship.
BFD detects a link fault between IS-IS neighbors, and rapidly reports it to IS-IS to trigger IS-
IS convergence rapidly.
NOTE
l As IS-IS sets up only single-hop IS-IS adjacencies, BFD is applicable only to single-hop IS-IS
adjacencies.
l For the detailed configuration of BFD for IS-IS, refer to the chapter "IS-IS Configuration" in the
HUAWEI NetEngine80E/40E Router Configuration Guide - IP Routing.
BFD for LSP

BFD detects failures in an MPLS LSP forwarding path on the data plane. As the format of BFD
packets is unchanged, the BFD packets are easily transmitted through hardware and traverse
through firewalls. The advantages of BFD for LDP LSP on the data plane are as follows:
l Only reachable IP routes are required for a backward link.
l Supports rapid detection.

l Supports large scale failure detection on LSPs.
Negotiation of a BFD session to detect LDP LSP connectivity is performed in either of two
modes:
l Static establishment of the BFD session: After the local and remote BFD discriminators
are set manually, the BFD session is established by using the negotiation mechanism.
l Dynamic establishment of the BFD session: The BFD session is established after
negotiation on the BFD Discriminator Type-Length-Value (TLV) carried in LSP Ping
messages.
On NE80E/40E, static BFD sessions detect the following types of LSPs:
l Static LSP
l LDP LSP
l TE: includes tunnel, static CR-LSP bound to the tunnel, and dynamic RSVP CR-LSP. BFD
detects faults in TE tunnels using signaling protocols (such as CE-static and RSVP-TE)
and a primary LSP bound to a TE tunnel.
Dynamic BFD sessions detect faults in the following forwarding paths:
l LDP LSP
l RSVP LSP
At present, a dynamic BFD session only detects faults in RSVP TE LSPs, not TE LSPs using
other signaling protocol nor TE tunnels.
If BFD works on unidirectional links like LSPs and TE tunnels, only a reachable IP route is
required for backward links which are IP links, LSPs, or TE tunnels.
NOTE
l For the configuration of BFD for static LSP and BFD for LDP LSP, refer to the chapter "Basic MPLS
Configuration" in the HUAWEI NetEngine80E/40E Router Configuration Guide - MPLS.
l For the configuration of BFD for MPLS TE, refer to the chapter "MPLS TE Configuration" in the
HUAWEI NetEngine80E/40E Router Configuration Guide - MPLS.
BFD for PW
BFD detects PW links between PEs. BFD supports VLL FRR, minimizing the impact of link
failures on services. The NE80E/40E supports BFD sessions for PW in either static
(discriminators are manually configured) or dynamic mode.
The NE80E/40E combines VCCV ping and BFD for checking PW connectivity dynamically,
which leads to rapid traffic switchovers for protecting upper-layer services.
NOTE
For the configuration of BFD for PW, refer to the chapter "PWE3 Configuration" in the HUAWEI
BFD for PIM

The NE80E/40E supports the dynamic creation of a BFD session between PIM neighbors, which
is used to detect faults in links between the PIM neighbors. If a fault occurs, BFD notifies PIM
of the fault.

NOTE
For the configuration of BFD for PIM, refer to the HUAWEI NetEngine80E/40E Router Configuration
Guide - IP Multicast.
CAUTION
l An outgoing interface is selected by LDP, TE, PIM, or a route in sequence before a BFD
session of a preceding type is configured on an LPU mapped to the selected outgoing
interface .
l If the outgoing interface is a logical interface configured with multiple interfaces, (such as
an Eth-trunk interface, which has multiple sub-interfaces on various LPUs), the BFD
session selects one LPU randomly.
l If an LPU with a BFD session but no service interface is removed, a service switchover is
triggered. Before removing an LPU, run the display bfd session all verbose command to
check sessions bound to the LPU. If BFD sessions are bound to the LPU, enter the BFD
session view and shut all sessions down before removing the board. After this, re-
established the BFD session.
BFD6
BFD for IPv6, also called BFD6, has similar functions to BFD for IPv4. Both of them rapidly
detect faults between systems and notify upper-layer applications of the faults.
The following table compares BFD for IPv6 to BFD for IPv4 based on functions.
Feature BFD6 BFD for IPv4
IP link Supported Supported
One-arm echo Not supported Supported
Static route Supported Supported
OSPF Not supported Supported
OSPFv3 Supported Not supported
BGP Supported Supported
IS-IS Supported Supported
PIM Supported Supported
PST Supported Supported
PIS Not supported Supported
PW Not supported Supported
TE Not supported Supported
LSP Not supported Supported

5.2 Configuring Single-hop BFD

A single-hop BFD session rapidly detects faults in direct links over a network.

Before configuring a single-hop BFD session, familiarize yourself with the applicable
To fast check directly-connected links, configure single-hop BFD.
Before configuring single-hop BFD, complete the following tasks:
l Connecting each interface correctly
l Configuring IP addresses for Layer 3 interfaces
Data Preparation
To configure single-hop BFD, you need the following data.
No. Data
1 BFD configuration name
2 Peer IP address, local interface type and number for the directly-connected link
detected by BFD, and default multicast address used by BFD if it checks the physical
layer status of the link
3 BFD session parameters: local and remote discriminators
5.2.2 Enabling BFD Globally

Enabling BFD globally is the prerequisite for BFD configurations.
Context
If single-hop BFD detection is performed on Layer 2 interfaces or Layer 3 physical interfaces
without IP addresses, a default multicast IP address is used.
Do as follows on both ends of a link to be checked:
Procedure
Step 1 Run:

system-view

Step 2 Run:
bfd
BFD is enabled globally and the BFD view is displayed.

default-ip-address ip-address
The default multicast IP address of BFD is configured.

By default, the multicast IP address used by BFD is 224.0.0.184.
NOTE
l Currently, multicast address detection is supported only in BFD for IPv4 but not BFD for IPv6.
Therefore, this command is applicable in only IPv4.
l If more than one BFD session is created for the same link, for example, a Layer 3 interface is connected
by BFD-enabled Layer 2 switches, various default multicast addresses need to be configured for the
switches, distinguishing one BFD session from others and ensuring that BFD packets are forwarded
correctly.
----End
5.2.3 Setting Up a BFD Session

Creating a BFD session on both ends of a direct link enables BFD to rapidly detect a fault in the
direct link.
Context
Do as follows on both ends of a link to be checked:
Procedure
Step 1 Run:
system-view

Step 2 Select one of the following steps based on the type of link checked by BFD:
l To use BFD to detect faults in an IPv4 link, run the following commands as required to
configure a BFD session:
– On a Layer 3 interface with an IP address, run:
bfd cfg-name bind peer-ip peer-ip [ vpn-instance vpn-instance-name ]
interface interface-type interface-number [ source-ip source-ip ]
– If a single-hop BFD session is to be set up on an interface for the first time, the interface
and its peer address must be bound to the BFD session. The bindings cannot be
modified after the BFD session is successfully created.
– During BFD configuration items are being created, the system checks only the format,
not the correctness, of an IP address. Either an incorrect peer or source IP address
leads to a failure in creating a BFD session.
– If BFD and Unicast Reverse Path Forwarding (URPF) are used together, as URPF
checks the source IP address of received packets, configure source-ip to specify a

correct source IP address for BFD packets during the creation of a BFD binding;
otherwise, BFD packets are discarded mistakenly.
– On a Layer 2 interface or a Layer 3 physical member interface without an IP address, run:
bfd cfg-name bind peer-ip default-ip interface interface-type interface-
number [ source-ip source-ip ]
l To use BFD to detect faults in an IPv6 link, run the following command to create a BFD6
session:
bfd cfg-name bind peer-ipv6 peer-ipv6 [ vpn-instance vpn-instance-name ]
interface interface-type interface-number [ source-ipv6 source-ipv6 ]
– If a single-hop BFD6 session is to be created for the first time, the peer IPv6 address and
local outbound interface need to be bound to the session. The bindings cannot be modified
after the BFD6 session is successfully created.
– When creating a BFD6 session, the system checks only the format, not the correctness,
of a peer IPv6 address. An incorrect peer or source IPv6 address leads to a failure in
creating a BFD6 session.
Step 3 Configure discriminators by running the following commands:

l To configure a local discriminator, run:
discriminator local discr-value
l To configure a remote discriminator, run:

discriminator remote discr-value
NOTE
l The local discriminator set on a device is equal to the remote discriminator set on a remote device, and
the remote discriminator set on the local device is equal to the local discriminator set on the remote
device. If the discriminators on the device and the remote device do not match, the session cannot be
created. After the local and remote discriminators are set successfully, they cannot be changed.
l In a BFD session to which a default multicast address is bound, its local and remote discriminators
must be different.
Step 4 Run:
commit
The configuration is committed.
NOTE
After necessary parameters, such as local and remote discriminators, are configured for a single-hop BFD
session, the commit command must be run to make the configuration take effect.
----End

By viewing the status and type of a BFD session, you can check whether the configurations are
successful.
Prerequisite
The configurations of a single-hop BFD session are complete.

Context
NOTE
Statistics about BFD sessions and detailed information about sessions can be queried only after BFD session
parameters have been set and BFD sessions have been set up.
Procedure
l Run the display bfd configuration { all | static [ name cfg-name ] | discriminator local-
discr-value | dynamic | peer-ip peer-ip [ vpn-instance vpn-instance-name ] } [ verbose ]
command to check BFD configurations.
l Run the display bfd configuration { all | static | peer-ipv6 peer-ipv6 [ vpn-instance vpn-
instance-name ] } [ verbose ] command to check BFD6 configurations.
l Run the display bfd interface [ interface-type interface-number ] command to check BFD
interfaces.
l Run the display bfd session { all | discriminator discr-value | dynamic | peer-ip peer-
ip [ vpn-instance vpn-instance-name ] | static } [ verbose ] [ slot slot-id ] command to
check information about a BFD session.
l Run the display bfd session { all | static | peer-ipv6 peer-ipv6 [ vpn-instance vpn-instance-
name ] } [ verbose ] [ slot slot-id ] command to check information about a BFD6 session.
l Run the display bfd statistics [ slot slot-id ] command to check the global statistics of the
BFD sessions.
l Run the display bfd statistics session { all | static | dynamic | discriminator discr-
value | peer-ip peer-ip [ vpn-instance vpn-instance-name ] } [ slot slot-id ] command to
check statistics about a BFD session.
l Run the display bfd statistics session {all | static | peer-ipv6 peer-ipv6 [ vpn-instance
vpn-instance-name ] } [ slot slot-id ] command to check statistics about a BFD6 session.
----End
Example
# After the configuration, run the display bfd session all verbose command, and you can view
information about a BFD session.
<HUAWEI> display bfd session all verbose
---------------------------------------------------------------------
Session MIndex : 256 (One Hop) State : Up Name : aa
---------------------------------------------------------------------
Bind Peer Ip Address : 224.0.0.184
Bind Peer Ip Address : 2001:1001:1002:1003:1004:1005:1006:1007
NextHop Ip Address : 2001:1001:1002:1003:1004:1005:1006:1007
Proc interface status : Disable Process PST : Disable
Active Multi : 3
Last Local Diagnostic : No Diagnostic


PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0
---------------------------------------------------------------------
A one-hop BFD session is established and is in the Up state.
5.3 Configuring the BFD Passive Echo Function

By configuring the BFD passive Echo function, you can implement the interworking between
the devices that support the Echo function. This function is applicable to only single-hop BFD
sessions.

Before configuring the BFD passive Echo function, familiarize yourself with the applicable
The BFD passive Echo function is applicable only to the one-hop BFD session.
If a device supports the Echo function in the network, the BFD passive Echo function needs to
be configured to be compatible with other devices.
Figure 5-2 Application scenario of the BFD passive Echo function

RouterA RouterB
Single-hop BFD
RouterA Supports BFD RouterB Supports BFD

Passive Echo Function Echo Function
As shown in Figure 5-2, the passive Echo function needs to be enabled on RouterA.
Before configuring the BFD passive Echo function, complete the following tasks:
l Enabling BFD globally
l (Optional) Setting up the ACL
NOTE
The BFD Echo packet is looped back through ICMP redirect at the remote end. In the IP packet that
encapsulates the BFD Echo packet, the destination address and the source address are the IP address of the
outgoing interface of the local end. Therefore, in the ACL rule, both the source addresses of the remote
end and the local end must be permitted.

Data Preparation
To configure the BFD passive Echo function, you need the following data.
No. Data
1 (Optional) ACL number
5.3.2 Configuring the BFD Passive Echo Function

In special scenarios that require interworking between a local device and the device that supports
the Echo function, you can configure the BFD passive Echo function.
Context
Do as follows on the router that is to be enabled with the passive Echo function:
Procedure
Step 1 Run:
system-view
Step 2 Run:
bfd
The BFD view is displayed.
Step 3 Run:
echo-passive { all | acl basic-acl-number }
The BFD passive Echo function is enabled.
l all: enables the passive Echo function of all the BFD sessions.
l acl: enables the passive Echo function of the BFD session that matches the ACL. In the ACL,
the source addresses of both the remote end and the local end must be permitted.
NOTE
If an ACL rule is created or changed after a BFD session goes Up through negotiations, this ACL rule can
take effect only after the BFD session goes Down and then Up or the parameters of the BFD session are
changed.
----End

By viewing the status, type, and Echo function status of a BFD session, you can check whether
the configurations are successful.
Prerequisite
The configurations of the BFD passive echo function are complete.

Procedure
Step 1 Run the display bfd session { all | static | dynamic | discriminator discr-value | peer-ip peer-
ip [ vpn-instance vpn-instance-name ] } verbose [ slot slot-id ] command to check information
about the BFD session.
----End
Example
# Display information about all the BFD sessions.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Actual Tx Interval (ms): 10 Actual Rx Interval (ms) : 10
Echo Passive : Enable Acl Number : --
WTR Interval (ms) : --
Active Multi : 3
Session TX TmrID : -- Session Detect TmrID : --
Session Init TmrID : -- Session WTR TmrID : --
Session Echo Tx TmrID : --
Session Description : --
--------------------------------------------------------------------------------
The command output shows that the Echo Passive field indicates Enable, which means that the
passive echo function is enabled for the BFD session. If the Echo Passive field indicates
Disable, this means that the passive echo function is disabled for the BFD session. The passive
echo function can be enabled for a BFD session only when the passive echo function is globally
enabled, the ACL rule (if configured) is matched, and the echo function is enabled on the peer.
5.4 Configuring the Association Between the BFD Status

and the Interface Status
By associating the BFD session status with the interface status, you can trigger fast route
convergence. This function is applicable to only the BFD session that uses the default multicast
IP address to detect the single-hop link.

Before associating the BFD session status with the interface status, familiarize yourself with the

When a transport device exists on the link and a fault occurs on a link, the routers on both ends
of the link need a long time to detect the fault. This is because although the two routers are
directly connected, the actual physical path is segmented by the transport device.
Figure 5-3 Networking diagram of devices between the both end routers
RouterA RouterB
To solve the problem, the NE80E/40E implements the association between BFD status and
interface status. The change of the BFD session status affects the protocol status of the interface.
Fast convergence of routes is thus triggered.
After the association between BFD status and interface status is configured, the BFD session
becomes Down when it detects a fault, and the corresponding interface status becomes
BFD_Down. When the interface is BFD_Down, the direct route of this interface is deleted from
the routing table; however, the forwarding of BFD packets is not affected.
Before configuring the association between BFD status and interface status, you need to
complete the task of 5.2 Configuring Single-hop BFD.
NOTE
Only the one-hop BFD session to which the default multicast IP address is bound can implement the
association between BFD status and interface status. You can run the bfd cfg-name bind peer-ip default-
ip interface interface-type interface-number [ source-ip source-ip ] command to set up a BFD session.
Data Preparation
To configure the association between BFD status and interface status, you need the following
data.
No. Data
5.4.2 Configuring the Association Between BFD Status and

Interface Status
By being associated with the interface status, a BFD session can affect the interface protocol
status after the BFD session status changes, which triggers fast route convergence.

Context
Do as follows on the NE80E/40E that needs to be configured with the association between BFD
status and interface status:
Procedure
Step 1 Run:
system-view
Step 2 Run:
bfd cfg-name
The BFD session view is displayed.
Step 3 Run:
process-interface-status
The status association between the current BFD session and the interface bound to the BFD
session is configured.
By default, the status of the current BFD session is not associated with the status of the interface.
That is, the change of the BFD session status does not affect the interface status.
Step 4 Run:
commit
NOTE
l When the process-interface-status command and the commit command are run in succession, the
BFD session may not be set up or the BFD session does not go Up through negotiation. Therefore, the
BFD session does not notify the interface of the BFD status immediately, avoiding that the BFD session
notifies the interface of incorrect status information that results in incorrect interface status change.
After the configuration is committed, the BFD sessions can notify the interface of the BFD status
change. In this manner, the BFD session status is associated with the interface status.
l If the process-interface-status command is saved in the configuration file, the BFD session that is
bound to the interface notifies the interface that the BFD session is Down when the NE80E/40E is
restarted, in view of the initial status of an interface being Down.
l Before the BFD status is associated with the interface status, the BFD configurations on the two NE80E/
40Es must be correct and symmetrical. If the BFD status on the local interface is Down, check whether
the BFD configuration on the peer is correct or whether the BFD session is shut down.
l If the networking requires that the BFD status must be synchronized with the interface status, you can
run the shutdown and undo shudown commands to change the status of the BFD session. When the
undo shutdown command is run, a timer to test the BFD session status is started. If the BFD session
goes Up through negotiation before the timer expires, the BFD session notifies the interface of the Up
state. Otherwise, the BFD session regards the link as failed and notifies the interface of the Down state
after the timer expires. In this manner, the BFD session status and the interface status are in real-time
synchronization.
----End

By viewing the association between a BFD session status and the interface status, you can check

Prerequisite
The configurations of the association between the BFD status and the interface status function
are complete.
Procedure
check the BFD session.
name ] } [ verbose ] [ slot slot-id ] command to check the BFD6 session.
----End
Example
After the configuration, running the display bfd session command, you can view that "Enable"
is displayed in the field of "Proc interface status" of corresponding sessions.
--------------------------------------------------------------------------------
Session MIndex : 256 (One Hop) State : Up Name : test
--------------------------------------------------------------------------------
Bind Interface : GigabiEthernet2/0/0
Actual Tx Interval (ms): 10 Actual Rx Interval (ms) : 10
Echo Passive : Disable Acl Number : --
Proc interface status : Enable Process PST : Disable
Active Multi : 3
--------------------------------------------------------------------------------
5.5 Configuring the Association Between the BFD Status

and the Sub-Interface Status
By associating the BFD session status with the sub-interface status, you can trigger fast route
convergence. This function is applicable to the single-hop BFD session that detects default
multicast IP addresses.


Before associating the BFD session status with the sub-interface status, familiarize yourself with
the applicable environment and complete pre-configuration task of configuring a single-hop
BFD session and data preparation.
In the networking in which high reliability is required and a great number of services are
configured on the sub-interface, you need to set up BFD sessions to verify the connectivity of
the main interface link. In addition, you need to configure the association between the BFD
status and the sub-interface status. Thus, you can enhance the reliability of the service on the
sub-interface and save session resources.
Before configuring the association between the BFD status and the sub-interface status, complete
the following tasks:
l Enabling BFD globally

l Setting up the one-hop BFD session, which is bound to the main interface and uses the
default multicast address for detection
l Setting up the BFD session and ensuring that the BFD session is Up
Data Preparation
To configure the association between the BFD status and the sub-interface status, you need the
following data.
No. Data
1 Name of the BFD session
5.5.2 Configuring the Association Between BFD Status and Sub-

Interface Status
By being associated with the sub-interface status, the BFD session can affect the interface
protocol status after the BFD session status changes, which triggers fast route convergence.
Context
Do as follows on the NE80E/40E that needs to rapidly detect the link fault:
Procedure
Step 1 Run:
system-view

Step 2 Run:
bfd cfg-name
Step 3 Run:
process-interface-status sub-if
The association between the BFD status and the sub-interface status is configured.
Step 4 Run:
commit
When the BFD session goes Down, the BFD statuses of the main interface bound to the BFD
session and its sub-interface also go Down.
NOTE
l When the process-interface-status command and the commit command are run in succession, the
BFD session may not be set up or the BFD session does not go Up through negotiation. Therefore, the
BFD session does not notify the interface of the BFD status immediately, avoiding that the BFD session
notifies the interface of incorrect status information that results in incorrect interface status change.
After the configuration is committed, the BFD sessions can notify the interface of the BFD status
change. In this manner, the BFD session status is associated with the interface status.
l If the networking requires that the BFD status must be synchronized with the interface status, you can
run the shutdown and undo shudown commands to change the status of the BFD session. When the
undo shutdown command is run, a timer to test the BFD session status is started. If the BFD session
goes Up through negotiation before the timer expires, the BFD session notifies the interface of the Up
state. Otherwise, the BFD session regards the link as failed and notifies the interface of the Down state
after the timer expires. In this manner, the BFD session status and the interface status are in real-time
synchronization.
l If the process-interface-status command is saved in the configuration file, the BFD session that is
bound to the interface notifies the interface that the BFD session is Down when the NE80E/40E is
restarted, in view of the initial status of an interface being Down.
l Before the BFD status is associated with the interface status, the BFD configurations on the two NE80E/
40Es must be correct and symmetrical. If the BFD status on the local interface is Down, check whether
the BFD configuration on the peer is correct or whether the BFD session is shut down.
----End

By viewing the identifier of the association between the BFD session status and the sub-interface
status, you can check whether the configurations are successful.
Prerequisite
The configurations of the association between the BFD status and the sub-interface status
function are complete.
Procedure
l Run the display bfd session { all | static | dynamic | discriminator discr-value | peer-ip
peer-ip [ vpn-instance vpn-instance-name ] } verbose [ slot slot-id ] command to check
information about the BFD session.

name ] } [ verbose ] [ slot slot-id ] command to check the BFD6 session.
----End
Example
Run the display bfd session all verbose command.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Proc interface status : Enable(Sub-If) Process PST : Disable
Active Multi : 3
Last Local Diagnostic : --
Bind Application : IFNET
--------------------------------------------------------------------------------
The preceding display shows that the value of the field Proc interface status is Enable(Sub-
If). This indicates that the status of the BFD session aa is associated with the status of the main
interface and the sub-interface.
5.6 Configuring the BFD to Modify the PST

By configuring a BFD session to modify the PST, you can speed up link fault detection by the
BFD session. This function is applicable to only single-hop BFD sessions.

Before configuring the modification of the PST through a BFD session, familiarize yourself with
the applicable environment and complete pre-configuration task of configuring the single-hop
BFD session and data preparation.
If the BFD can modify the Port State Table (PST), it modifies the corresponding entry in the
PST when it detects that an interface is Down. Through the PST, other upper application
protocols can acknowledge whether the interface has a fault.

Currently, for the NE80E/40E, LDP FRR and IP FRR based on BFD detection need to know
the BFD detection result through the PST.
You do not need to run the process-pst command on the applications that do not learn the BFD
results through the PST.
NOTE
l For the LDP FRR, refer to chapter "MPLS Basic Configuration"in the HUAWEI NetEngine80E/40E
Router Configuration Guide - MPLS.
l IP FRR works for the public network and for the private network. For information about the IP FRR
for the public network, refer to Chapter 10 "Routing Policy Configuration" in the HUAWEI
NetEngine80E/40E Router Configuration Guide - IP Routing.
l For information about the IP FRR for the private network, refer to Chapter 4 "BGP MPLS IP VPN
Configuration" in the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN.
Before configuring the BFD to modify the PST, complete the task of 5.2 Configuring Single-
hop BFD.
Data Preparation
To configure the BFD to modify the PST, you need the following data.
No. Data
1 Configuration name of the BFD session
5.6.2 Permitting the BFD to Modify the PST

By permitting a BFD session to modify the PST, you can sense the fault detected by the BFD
session through the PST.
Context
Do as follows on the router that learns the BFD results through the PST:
Procedure
Step 1 Run:
system-view

Step 2 Run:
bfd cfg-name

Step 3 Run:
process-pst
The BFD is permitted to modify the PST.

By default, the BFD does not modify the PST.
NOTE
After creating a BFD session, if you need to modify session parameters such as process-pst, process-
interface-status, min-tx-interval, min-rx-interval, detect-multiplier, tos-exp, wtr, and description,
you can directly run the corresponding commands without running the commit command, and the
modification takes effect immediately.
If the BFD session on the Trunk member interface or the VLAN member interface allows BFD
to modify the PST, and the main interface is configured with the BFD session, you must configure
the Wait to Recovery (WTR) for the BFD session that detects the main interface. This can prevent
the BFD session on the main interface from flapping when the member interface joins or exits
from the main interface.
For the configuration of the WTR for the BFD session, see "5.11.3 Configuring the BFD
WTR."
Step 4 Run:
commit
The configurations are committed.
----End

By viewing the enabling status of a PST, you can check whether the configurations are
successful.
Prerequisite
The configurations of the BFD to modify the PST function are complete.
Procedure
check the BFD session.
name ] } [ verbose ] [ slot slot-id ] command to check information about the BFD6 session.
----End
Example
After the configuration, running the display bfd session command, you can view that the field
of "Process PST" in the command output is "Enable".
--------------------------------------------------------------------------------
Session MIndex : 256 (One Hop) State : Up Name : test
--------------------------------------------------------------------------------


Proc interface status : Disable Process PST : Enable
Active Multi : 3
--------------------------------------------------------------------------------
5.7 Configuring the Multi-Hop BFD

By configuring a multi-hop BFD session, you can fast detect and monitor multi-hop links of a
network.

Before configuring a multi-hop BFD session, familiarize yourself with the applicable
environment and data preparation.
To rapidly detect the faults occur during IP router forwarding, configure the multi-hop BFD.
Before configuring the multi-hop BFD, complete the following tasks:
l Correctly connecting each interface and configuring IP addresses for them

l Configuring the routing protocol to ensure that the network layer is reachable
Data Preparation
To configure the multi-hop BFD, you need the following data.
No. Data
1 Remote IP address
3 BFD session parameters: local discriminator and remote discriminator
4 BFD mode: asynchronous mode or demand mode. If the demand mode is used, the
period of command should be set.


You can perform related BFD configurations only after enabling BFD globally.
Context
Do as follows on the router:
Procedure
Step 1 Run:
system-view

Step 2 Run:
bfd
----End
5.7.3 Setting Up a BFD Session

By creating a BFD session on both ends of a multi-hop link, you can fast detect the fault on the
multi-hop link.
Context
Procedure
Step 1 Run:
system-view

Step 2 Select the step based on the type of the link detected by BFD:
l For an IPv4 link:
Run the bfd cfg-name bind peer-ip peer-ip [ vpn-instance vpn-instance-name ] [ source-
ip source-ip ] command to configure a BFD session.
– When a BFD session is set up for the first time, you need to bind the peer IP address to
it. After the BFD session is set up, you cannot modify it.
– When the BFD configuration items are created, the system checks only the format of the
IP address rather than the correctness. The BFD session cannot be established if incorrect
peer IP address or source IP address is bound.
– When the BFD and URPF are used together, URPF checks the source IP address of the
received packets. Therefore, when creating a BFD binding, you need to specify the source
IP address of the BFD packet in case the BFD packet is incorrectly discarded.
l For an IPv6 link:
Run the bfd cfg-name bind peer-ipv6 peer-ipv6 [ vpn-instance vpn-instance-name ]
[ source-ipv6 ipv6-address ] command to configure a BFD6 session.

– When setting up a BFD6 session for the first time, you need to bind the peer IPv6 address
to the session. The binding cannot be modified once the BFD6 session is set up.
– If the specified peer IPv6 address is a link-local address, the outbound interface should
also be specified, that is, only the single-hop BFD6 session can be set up; otherwise, an
error prompt is displayed.
– When configuring the BFD6 session, the system checks only the validity of the format
of the IPv6 address rather than the correctness of the IPv6 address. The BFD6 session
cannot be set up if incorrect peer IPv6 address or source IPv6 address is bound.
Step 3 Run the bfd cfg-name bind peer-ip peer-ip [ vpn-instance vpn-instance-name ] [ source-ip
source-ip ] command to configure a BFD session.
l When a BFD session is set up for the first time, you need to bind the peer IP address to it.
After the BFD session is set up, you cannot modify it.
l When the BFD configuration items are created, the system checks only the format of the IP
address rather than the correctness. The BFD session cannot be established if incorrect peer
IP address or source IP address is bound.
l When the BFD and URPF are used together, URPF checks the source IP address of the
received packets. Therefore, when creating a BFD binding, you need to specify the source
IP address of the BFD packet in case the BFD packet is incorrectly discarded.
Step 4 Configure the discriminators.

l Run:
The local discriminator is configured.

l Run:
discriminator remote discr-value
The remote discriminator is configured.

NOTE
The local discriminator of the local device corresponds to the remote discriminator of the remote device,
and the remote discriminator of the local device corresponds to the local discriminator of the remote device.
The local discriminator of the local device needs to be the same with the remote discriminator of the remote
device. Otherwise, the session cannot be correctly set up. After the local discriminator and the remote
discriminator are configured, you cannot modify it.
Step 5 Run:
commit
The configurations are committed.
NOTE
When setting up a BFD session, you must run the commit command after configuring necessary
parameters, such as local and remote discriminators; otherwise, the session cannot be set up.
----End

By viewing the status and type of a BFD session, you can check whether the configurations are
successful.

Prerequisite
The configurations of the multi-hop BFD function are complete.
Context
NOTE
Only after the parameters of the session are set and the session is set up, you can view the information on
the session.
Procedure
command to check BFD configurations.
instance-name ] } [ verbose ] command to check BFD6 configurations.
ip [ vpn-instance vpn-instance-name ] | static } [ verbose ] [ slot slot-id ] to check the
BFD session.
name } [ verbose ] [ slot slot-id ] command to check information about the BFD6 session.
l Run the display bfd statistics [ slot slot-id ] to check the global statistics of the BFD session.
l Run the display bfd statistics session { all | static | discriminator discr-value | peer-ip
peer-ip [ vpn-instance vpn-instance-name ] } [ slot slot-id ] to check the statistics of the
BFD session.
vpn-instance-name ] } [ slot slot-id ] command to check statistics of the BFD6 session.
----End
Example
After the configuration, run the display bfd session all verbose command.
--------------------------------------------------------------------------------
Session MIndex : 256 (Multi Hop) State : Up Name : atoc
--------------------------------------------------------------------------------
BFD Bind Type : Peer Ip Address
Bind Interface : --
Active Multi : 3


--------------------------------------------------------------------------------
You can view that a multi-hop BFD session is established. The BFD session is Up.
5.8 Configuring a BFD Session with Automatically

Negotiated Discriminators
A static BFD session with automatically negotiated discriminators is configured to check the
interworking between a device and another device on which a BFD session is dynamically
established. The static BFD session with automatically negotiated discriminators is applicable
to static routes.

Before configuring a static BFD session with automatically negotiated discriminators,
familiarize yourself with the applicable environment, complete the pre-configuration tasks, and
obtain data required for the configuration. This will help you complete the configuration task
quickly and accurately.
If a dynamic BFD session is used by a remote device, a static BFD session with automatically
negotiated discriminators must be created on a local device to interwork with the remote device
and support a static route to track BFD.
Before configuring a BFD session with automatically negotiated discriminators, complete the
following tasks:
l Correctly connecting interfaces

l Correctly configuring the IP address of a Layer 3 interface
Data Preparation
To complete the configuration, you need the following data.
No. Data
1 Name of a BFD session
2 IP addresses of local and remote ends of a link checked by BFD, and name and
number of the local interface

You can perform related BFD configurations only after enabling BFD globally.

Context
Do as follows on the router on which a static BFD session with automatically negotiated
discriminators is used to detect faults in a link:
Procedure
Step 1 Run:
system-view

Step 2 Run:
bfd
----End
5.8.3 Configuring a BFD Session with Automatically Negotiated

Discriminators
A static BFD session with automatically negotiated discriminators is configured to rapidly detect
link faults.
Context
Do as follows on the router on which a static BFD session with automatically negotiated
discriminators is used to detect link faults:
Perform the following step as required to configure BFD for IPv4 or BFD for IPv6.
Procedure
l To configured BFD for IPv4,
1. Run:
system-view

2. Run:
bfd cfg-name bind peer-ip ip-address [ vpn-instance-name vpn-name ]
[ interface interface-type interface-number ] source-ip ip-address auto
A static BFD session with automatically negotiated discriminators is set up.
– The source IP address must be specified.

– The peer IP address must be specified, which cannot be a multicast IP address.
3. Run:
commit

l To configure BFD for IPv6,
1. Run:
system-view


2. Run:
bfd cfg-name bind peer-ipv6 peer-ipv6 [ vpn-instance vpn-instance-name ]
[ interface interface-type interface number ] source-ipv6 ipv6-address auto
A static BFD6 session with automatically negotiated discriminators is set up.
– The source IP address must be specified.

– The peer IPv6 address must be specified.
3. Run:
commit

----End

By viewing the type of a BFD session, you can check whether the configurations are successful.
Prerequisite
The configurations of a BFD session with automatically negotiated discriminators are complete.
Procedure
peer-ip [ vpn-instance vpn-instance-name ] } verbose [ slot slot-id ] command to check
l Run the display bfd session { all | static | peer-ipv6 peer-ipv6 [ vpn6-instance vpn6-
instance-namevpn-instance vpn-instance-name ] } [ verbose ] [ slot slot-id ] command to
check information about a BFD6 session.
----End
Example
# After the configuration, run the display bfd session all verbose command.
You can view that a BFD session with the type being Static_Auto has been established. The
local and remote discriminators of this BFD session are 8193 and 8192 respectively, which are
obtained by automatic negotiation.
--------------------------------------------------------------------------------
Session MIndex : 16385 (One Hop) State : Up Name : auto
--------------------------------------------------------------------------------
Bind Session Type : Static_Auto
Bind Source IP Address : 192.168.1.1



Bind Application : AUTO
--------------------------------------------------------------------------------
5.9 Configuring the Delay of a BFD Session to Go Up

In special scenarios, the delay of a BFD session to go Up is configured to prevent traffic loss as
a route protocol becomes Up later than an interface.

Before configuring the delay of a BFD session to go Up, 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.
If BFD is Up on a network, the interface bound to BFD goes Up, allowing traffic to switch back
to the interface. As a routing protocol goes Up later than the interface status, no route is available
for traffic to switch back. As a result, traffic is dropped. The time when the routing protocol goes
Up and the time when the interface goes Up must be synchronous.
Before configuring the delay of a BFD session to go Up, ensure that the router runs normally.
Data Preparation
No. Data
1 Delay time
5.9.2 Configuring the Delay of a BFD Session to Go Up

The delay of a BFD session to go Up is configured to prevent traffic loss in special scenarios.
Context
Do as follows on the routers on which the setup of the BFD session needs to be delayed:

Procedure
Step 1 Run:
system-view

Step 2 Run:
bfd

Step 3 Run:
delay-up seconds
The time the BFD session is delayed to go Up is set.

By default, the delay time is 0 seconds.
----End

By viewing the delay of a BFD session to go Up, you can check whether the configurations are
successful.
Prerequisite
The configurations of the delay of a BFD session to go Up are complete.
Procedure
Step 1 Run the display bfd statistics [ slot slot-id ] command to check statistics about global BFD.
----End
Example
# After the configuration, restart the router. After the restart, run the display bfd statistics
command.
The System Session Delay Up Timer field in the command output. This field displays the status
of the current system delay Up time. OFF indicates that the system is in the normal state; Xs
indicates that after X seconds, the system recovers, and the BFD session goes Up.
<HUAWEI> display bfd statistics
Current Display Board Number : Main ; Current Product Register Type:
IP Multihop Destination Port : 3784
Total Up/Down Session Number : 0/1
Current Session Number :
Static session : 0 Dynamic session : 0
E_Dynamic session : 0 STATIC_AUTO session : 1
LDP_LSP session : 0 STATIC_LSP session : 0
TE_TUNNEL session : 0 TE_LSP session : 0
PW session : 0 IP session : 1
--------------------------------------------------------------------------------
PAF/LCS Name Maxnum Minnum Create
--------------------------------------------------------------------------------
BFD_CFG_NUM 8192 1 1
BFD_IF_NUM 512 1 1

BFD_SESSION_NUM 8192 1 1
BFD_IO_SESSION_NUM 512 1 0
BFD_PER_TUNNEL_CFG_NUM 16 1 0
--------------------------------------------------------------------------------
IO Board Current Created Session Statistics Information :(slot/number)
--------------------------------------------------------------------------------
0 /0 1 /0 2 /1 3 /0 4 /0 5 /0 6 /0 7 /0
8 /0 9 /0 10/0 11/0 12/0 13/0 14/0 15/0
16/0 17/0 18/0 19/0 20/0 21/0 22/0 23/0
24/0 25/0 26/0 27/0 28/0 29/0 30/0 31/0
32/0 33/0 34/0 35/0 36/0 37/0
--------------------------------------------------------------------------------
Current Total Used Discriminator Num : 1
--------------------------------------------------------------------------------
IO Board Reserved Sessions Number Information :(slot/number)
--------------------------------------------------------------------------------
0 /0 1 /0 2 /0 3 /0 4 /0 5 /0 6 /0 7 /0
8 /0 9 /0 10/0 11/0 12/0 13/0 14/0 15/0
16/0 17/0 18/0 19/0 20/0 21/0 22/0 23/0
24/0 25/0 26/0 27/0 28/0 29/0 30/0 31/0
32/0 33/0 34/0 35/0 36/0 37/0
--------------------------------------------------------------------------------
BFD HA Information :
--------------------------------------------------------------------------------
Core Current HA Status : Normal
Shell Current HA Status : Normal
--------------------------------------------------------------------------------
BFD for LSP Information :
--------------------------------------------------------------------------------
Ability of auto creating BFD session on egress : Disable
Period of LSP Ping : 60
System Session Delay Up Timer : OFF
--------------------------------------------------------------------------------
5.10 Configuring a BFD Session with the One-Arm Echo

Function
By configuring a BFD session with the one-arm Echo function, you can fast detect and monitor
a direct link between a BFD-capable device and a BFD-incapable device.

Before configuring the BFD session with the one-arm Echo function, familiarize yourself with
This can help you complete the configuration task quickly and accurately.
On two directly-connected devices, one device supports BFD and the other does not. To fast
detect a link fault, you can create a BFD session with the one-arm Echo function on the BFD-
capable device. After the BFD-capable device sends a BFD Echo packet to the BFD-incapable
device, the BFD-incapable device directly loops back the packet, thus achieving fast detection
on the link.
Before configuring the BFD session with the one-arm Echo function, complete the following
tasks:

l Correctly connecting interfaces

l Correctly assigning an IP address to every Layer 3 interface
Data Preparation
To configure the BFD session with the one-arm Echo function, you need the following data.
No. Data
1 Name of a BFD session
2 Minimum interval at which BFD packets are received
5.10.2 Enable BFD Globally

BFD-associated configurations can be performed only after BFD has been enabled globally.
Context
Do as follows on the BFD-supported device at one end of a link:
Procedure
Step 1 Run:
system-view
Step 2 Run:
bfd
BFD is globally enabled and the BFD view is displayed.
----End
5.10.3 Establishing a BFD Session

By establishing a BFD session on a BFD-capable device, you can rapidly detect a direct link
between the BFD-capable device and its BFD-incapable peer.
Context
Do as follows on a BFD-capable device at one end of a link:
Procedure
Step 1 Run:
system-view

Step 2 Run:
bfd cfg-name bind peer-ip peer-ip [ vpn-instance vpn-instance-name ] interface
interface-type interface-number [ source-ip source-ip ] one-arm-echo
A BFD session with the one-arm Echo function is created.
NOTE
A BFD session with the one-arm Echo function can detect only single-hop links.
Step 3 Run:
The discriminator is set for the BFD session.
The one-arm Echo function can be configured only on the BFD-capable device at one end of a
link. A BFD session with this function must be configured with a local discriminator rather than
a remote discriminator.

min-echo-rx-interval
The minimum interval between receipt of BFD packets is set.
By default, the minimum interval between receipt of BFD packets is 10 milliseconds.
Step 5 Run:
commit
NOTE
After configuring the local discriminator parameter and any other required parameters for a BFD session
with the one-arm Echo function, you must run the commit command to make the configuration take effect.
----End

By viewing the type and status of a BFD session with the one-arm Echo function, you can check
whether the configurations are correct.
Prerequisite
The configurations of the one-arm Echo function are complete.
Procedure
command to check the configuration of a BFD session.
l Run the display bfd interface [ interface-type interface-number ] command to check
information about an interface configured with BFD.
check information about a BFD session.

value | peer-ip peer-ip [ vpn-instance vpn-instance-name ] } [ slot slot-id ] command to
check statistics about BFD sessions.
----End
Example
After a BFD session with the one-arm Echo function has been successfully configured, run the
display bfd session all verbose command, and you can view detailed information about the
session.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Session Detect Mode : Asynchronous One-arm-echo Mode
BFD Bind Type : Interface(gigabitEthernet1/0/0)
Bind Interface : EigabitEthernet1/0/0
Active Multi : 3
--------------------------------------------------------------------------------
The command output shows that a single-hop BFD session has been created and its status is Up.
5.11 Adjusting BFD Parameters

Adjusting BFD parameters enables a BFD session to check links on a network effectively and
quickly.

Before adjusting BFD parameters, familiarize yourself with the applicable environment and
complete pre-configuration task for a BFD session, and obtain data required for configuring the
BFD session.
After a BFD session is set up, the sending interval, the receiving interval, and the local detection
multiplier are adjusted on the basis of the network status and performance requirement.

The Wait to Recovery (WTR) time for a BFD session is set to prevent frequent master/slave
switchovers caused by BFD session flapping.
The description of a BFD session is added to describe a link monitored by a BFD session.
If none of the preceding parameters is set, the default configurations are used.
Before adjusting BFD parameters, you need to set up a BFD session.
Data Preparation
To adjust BFD parameters, you need the following data.
No Data
2 Local intervals at which BFD packets are sent and received
3 Local BFD detection multiplier
5.11.2 Modifying the Detection Time

Modifying the BFD detection time enables a BFD session to detect faults in links on a network
effectively.
Context
Follow-up Procedure
To efficiently use system resources, when detecting that a BFD session goes Down, the system
automatically adjusts the intervals at which BFD control packets are sent and received to a
random value larger than 1000 milliseconds. After the BFD session goes Up, the configured
intervals recover.
NOTE
To meet the requirement for fast detection, BFD draft defines that the sending interval and the receiving
interval are at microsecond level. On most devices, BFD detection is performed only at millisecond level,
and the processing inside the devices is at microsecond level.
5.11.3 Configuring the BFD WTR

The Wait to Recovery (WTR) time for a BFD session is used to prevent frequent master/slave
switchovers triggered by BFD session flapping.

Context
The WTR time for a BFD session is used to prevent frequent master/slave switchovers caused
by BFD session flapping. If a BFD session changes from Down to Up, BFD reports the change
to an upper-layer application after the WTR time expires.
Procedure
Step 1 Run:
system-view

Step 2 Run:
bfd cfg-name

Step 3 Run:
wtr wtr-value
The WTR is configured.

By default, the WTR is 0.
NOTE
l As a BFD session takes effect on a unidirectional path, the WTR time on both ends of the path must
be the same. If the WRT time on one end is different from that on the other end, applications on the
two ends detect different BFD status after the BFD status on one end changes.
l After a BFD session has been created, to modify a parameter, run a corresponding command (such as
process-pst, process-interface-status,min-tx-interval, min-rx-interval, detect-multiplier, tos-
exp, wtr, or description). The modification takes effect immediately without the commit command
configured.
----End
5.11.4 Adding the Description of a BFD Session

Descriptions of BFD sessions help you distinguish between various BFD sessions.
Context
NOTE
The description command takes effect only on statically configured BFD sessions not on BFD sessions
that are dynamically configured or BFD sessions that are created by using automatically-negotiated
discriminators.
Procedure
Step 1 Run:
system-view

Step 2 Run:
bfd cfg-name
Step 3 Run:
description description
The description of a BFD session is added.
description is a string of 1 to 51 characters.
By default, the description of the BFD session is Null.
You can run the undo description command to delete the description of a BFD session.
NOTE
After a BFD session has been created, to modify a parameter, run a corresponding command (such as
process-pst, process-interface-status,min-tx-interval, min-rx-interval, detect-multiplier, tos-exp,
wtr, or description). The modification takes effect immediately without the commit command configured.
----End

By viewing the adjusted BFD parameters, you can check whether the configurations are
successful.
Prerequisite
The configurations for BFD parameter adjustment are complete.
Context
NOTE
Information about a BFD session is viewed only after parameters of the BFD session have been set and
the session has been created.
Procedure
to check BFD configurations.
l Run the display bfd configuration { all | static | peer-ipv6 peer-ipv6 [ vpn6-instance
vpn6-instance-namevpn-instance vpn-instance-name ] } [ verbose ] command to check
BFD6 configurations.
ip [ vpn-instance vpn-instance-name ] | static } [ verbose ] [ slot slot-id ] to check
l Run the display bfd session { all | static | peer-ipv6 peer-ipv6 [ vpn6-instance vpn6-
instance-namevpn-instance vpn-instance-name ] } [ verbose ] [ slot slot-id ] command to
check information about a BFD6 session.
----End

Example
After the configuration, run the display bfd session all verbose command, and you can view
that Min Tx Interval is 500 milliseconds; Min Rx Interval is 500 milliseconds; WTR
Interval is 60000 milliseconds; Session Description is RouterA_to_RouterB.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
WTR Interval (ms) : 60000
Active Multi : 3
Session Description : RouterA_to_RouterB
--------------------------------------------------------------------------------
5.12 Globally Configuring the Destination Port Number for

the Multi-Hop BFD Control Packet
By configuring a global destination port number for multi-hop BFD control packets, you can
implement the interworking between the local device and a device running an earlier version,
and between a Huawei device and a non-Huawei device.

Before configuring a global destination port number for multi-hop BFD control packets,
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.
The BFD control packet is encapsulated in the UDP packet for transmission, using the source
port in the range of 49152 to 65535 and destination port 3784 or 4784. According to the BFD
draft, the destination port 4784 is used for the multi-hop BFD control packet. On the NE80E/
40E of the earlier version, however, destination port 3784 is used for the multi-hop BFD control
packet. The destination port number of the multi-hop BFD control packet can be configured
globally according to the requirements:

l To interwork with the device running the version earlier than the NE80E/40E, the device
running the NE80E/40E can be configured with destination port 3784 for the multi-hop
BFD control packet.
l To interwork with the non-Huawei device, the device running the NE80E/40E can be
configured with destination port 4784 for the multi-hop BFD control packet.
Before globally configuring the destination port number for the multi-hop BFD control packet,
complete the following tasks:
l Installing the device and turning it on properly

l Connecting interfaces correctly
Data Preparation
To globally configure the destination port number for the multi-hop BFD control packet, you
need the following data.
No. Data
1 Name of the device
5.12.2 Globally Configuring the Destination Port Number

You can configure a global destination port number for multi-hop BFD control packets according
to the specified devices running a distinct version or the specified vendor's devices.
Context
Do as follows on each device:
Procedure
Step 1 Run:
system-view
Step 2 Run:
bfd
BFD is enabled globally on the local node and the BFD view is displayed.
Step 3 Run:
multi-hop destination-port { 3784 | 4784 }
The destination port number is configured globally for the multi-hop BFD control packet.

NOTE
If destination port 3784 is used by the multi-hop BFD control packets on a router, the router can successfully
negotiate with the router on which destination port 4784 is used by the multi-hop BFD control packets. At
the same time, on the router that is configured with destination port 3784, destination port 3784 is
automatically updated to destination port 4784. To change the destination port number from 4784 to 3784,
run the shutdown command to terminate the BFD session on destination port 4784, then, run the multi-
hop destination-port 3784 command on destination ports 4784 and 3784, and finally run the undo
shutdown command to restore the BFD session.
----End

By viewing the destination port number and TTL in multi-hop BFD control packets, you can
check whether the configurations are successful.
Prerequisite
All global configurations of the destination port number of the multi-hop BFD control packet
are completed.
Context
NOTE
You can view information about the BFD session and its statistics only after only after BFD session
parameters are configured and the BFD session is set up successfully.
Procedure
view information about the BFD session.
l Run the display bfd statistics [ slot slot-id ] command to view information about statistics
of global BFD.
----End
Example
---------------------------------------------------------------------
Session MIndex : 16384 (Multi Hop) State : Up Name : test
---------------------------------------------------------------------
Min Tx Interval (ms) : 10 Min Rx Interval (ms) :10
Active Multi : 3


According to the preceding command output, you can view that destination port 3784 is used
for the multi-hop BFD control packet.
5.13 Configuring the TTL Globally

Configuring the TTL globally helps you connect the current device and a device running an early
version.

Before configuring the TTL globally, 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.
If devices running different versions interwork with each other, the TTL values and detection
modes on both ends of a BFD session are different, resulting in BFD packet loss. The TTL is
set globally to enable Huawei devices to interwork with Huawei devices running different
NE80E/40E versions and non-Huawei devices.
Before configuring the TTL globally, complete the following tasks:
l Connecting interfaces correctly
l Configuring the IP address of each Layer 3 interface correctly
Data Preparation
To configure the TTL globally, you need the following data.
No. Data
1 Name and number of each interface
5.13.2 Configuring the TTL Globally

The TTLs help you distinguish between a single-hop BFD session and a multi-hop BFD session
when a device interworks with a device running an early version.
Context

Procedure
Step 1 Run:
system-view
Step 2 Run:
bfd
BFD is enabled globally on the local device and the BFD view is displayed.
Step 3 Run:
peer-ip peer-ip mask-length ttl { single-hop | multi-hop } ttl-value
The TTL in BFD control packets is set.
NOTE
By default, in a static BFD session, the TTL for single-hop BFD packets is 255, and the TTL for multi-
hop BFD packets is 254; in a dynamic BFD session, the TTL for single-hop BFD packets is 255 and the
TTL for multi-hop BFD packets is 253.
----End

By viewing the global TTL in BFD control packets, you can check whether the configurations
are successful.
Prerequisite
The configurations of the global TTL are completed.
Procedure
view information about the BFD session.
l Run the display bfd ttl [ slot slot-id ] command to view information about the globally
configured TTL.
----End
Example
After the configurations are successful, run the display bfd ttl command, and you can view
information about the global TTL.
<HUAWEI> display bfd ttl
--------------------------------------------------------------------------
Peer IP Mask Type Value
---------------------------------------------------------------------------
1.1.1.0 24 Single-hop 255
---------------------------------------------------------------------------

5.14 Configuring the Interval at Which Trap Messages Are

Sent
The interval at which trap messages are sent is set, helping a device to suppress BFD trap
messages.

Before configuring the interval at which trap messages are sent, 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.
If BFD is enabled with the SNMP trap function, the NMS receives messages indicating that the
BFD session is Up or Down. If the BFD session flaps, the NMS will receive a large number of
trap messages. In this case, BFD trap messages need to be suppressed. Setting the interval at
which trap messages are sent prevents overflow of trap messages.
Before configuring the interval at which trap messages are sent, enable BFD globally.
Data Preparation
To configure the interval at which trap messages are sent, you need the following data.
No. Data
1 Interval at which trap messages are sent
5.14.2 Configuring the Interval at Which Trap Messages Are Sent

When BFD sessions flap, the NMS receives a great number of trap messages. The interval at
which trap messages are sent is set, helping a device suppress trap messages.
Context
Do as follows on the router that needs to be configured with the interval at which trap messages
are sent:
Procedure
Step 1 Run:
system-view

Step 2 Run:
bfd
BFD is enabled globally, and the global BFD view is displayed.
Step 3 Run:
snmp-agent bfd trap-interval interval
The interval at which trap messages are sent is set.
By default, the interval at which trap messages are sent is 120 seconds.
----End

By viewing the interval at which trap messages are sent, you can check whether the
Prerequisite
The configurations of the interval at which trap messages are sent are complete.
Procedure
l Run the display current-configuration configuration bfd command to view the
configuration of the BFD trap function.
----End
Example
Run the display current-configuration configuration bfd command, and you can view that
the interval at which trap messages are sent is 300 seconds.
<HUAWEI> display current-configuration configuration bfd
#
bfd
snmp-agent bfd trap-interval 300
#
return
5.15 Maintaining BFD

This section describes how to maintain BFD by deleting BFD statistics, and monitoring BFD
operation.
5.15.1 Clearing BFD Statistics

Deleting previous BFD statistics is recommended before BFD statistics within a specified period
of time are collected.

Context
CAUTION
BFD statistics cannot be restored after being deleted. Exercise caution when using the command.
Procedure
Step 1 Run the reset bfd statistics { all [ slot slot-id ] | discriminator discr-value } command in the
user view to delete BFD statistics.
----End
5.15.2 Monitoring BFD Status

Monitoring BFD status is to view information about BFD during the operation.
Context
The following commands are run in any view during routine maintenance to show the BFD
status.
Procedure
command in any view to check BFD configurations.
instance-name ] } [ verbose ] command in any view to check BFD6 configurations.
l Run the display bfd interface [ interface-type interface-number ] command in any view
to check information about an interface enabled with BFD.
peer-ip [ vpn-instance vpn-instance-name ] } [ verbose ] [ slot slot-id ] command in any
view to check information about a BFD session.
name ] } [ verbose ] [ slot slot-id ] command in any view to check information about a
BFD6 session.
l Run the display bfd statistics [ slot slot-id ] command in any view to check statistics about
global BFD.
value | peer-ip peer-ip [ vpn-instance vpn-instance-name ] } [ slot slot-id ] command in
any view to check statistics about a BFD session.
vpn-instance-name ] } [ slot slot-id ] command in any view to check statistics about a BFD6
session.
----End


Context
NOTE
In this example, interface numbers and link types on the NE40E-X8 are used. On existing networks, the
interface numbers and link types are different from those used in this example.
5.16.1 Example for Configuring Single-hop BFD for a Layer 3

Physical Link
In this example, a single-hop BFD session to detect faults in a Layer 3 physical link is configured
to rapidly check a direct link on a network.
NOTE
POS interfaces cannot be configured on the -X1 or -X2 models of NE80E/40Es.
On the network shown in Figure 5-4, BFD in asynchronous mode is used to detect a directly
connected link between Router A and Router B.
Figure 5-4 Networking diagram of singe-hop BFD

POS1/0/0 POS1/0/0
10.1.1.1/24 10.1.1.2/24
W
RouterA RouterB
1. Configure a BFD session on Router A to detect the directly-connected link between Router
A and Router B.
2. Configure a BFD session on Router B to detect the directly-connected link between Router
B and Router A.
Data Preparation
l Peer IP address for a BFD session

l Local interface sending and receiving BFD control packets

l Local and remote discriminators of a BFD session
NOTE
Default values of the minimum sending interval, minimum receiving interval, and local detection multiplier
for BFD control packets are used.
Procedure
Step 1 Configure IP addresses for directly-connected interfaces on Router A and Router B.
# Configure the IP address of the interface on Router A.
[RouterA-Pos1/0/0] ip address 10.1.1.1 24
# Configure the IP address of the interface on Router B.

[RouterB-Pos1/0/0] ip address 10.1.1.2 24
Step 2 Configure single-hop BFD.

# Enable BFD on Router A, create a BFD session between Router A and Router B, and bind
Router A's interface to the BFD session.
[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd atob bind peer-ip 10.1.1.2 interface pos 1/0/0
[RouterA-bfd-session-atob] wtr 5
# Enable BFD on Router B, set up the BFD session between Router B and Router A, and bind
Router B's interface to the BFD session.
[RouterB] bfd
[RouterB-bfd] quit
[RouterB] bfd btoa bind peer-ip 10.1.1.1 interface pos 1/0/0
[RouterB-bfd-session-btoa] wtr 5

After the configuration, run the display bfd session all verbose command on Router A and
Router B. You can view that a single-hop BFD session has been created and its status is Up.
Use the display on Router A as an example.
<RouterA> display bfd session all verbose
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


BFD Bind Type : Interface(Pos1/0/0)
Bind Interface : Pos1/0/0
Active Multi : 3
--------------------------------------------------------------------------------
----End
Configuration Files
#
sysname RouterA
#
bfd
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
bfd atob bind peer-ip 10.1.1.2 interface Pos1/0/0
wtr 5
commit
#
return

#
sysname RouterB
#
bfd
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
bfd btoa bind peer-ip 10.1.1.1 interface Pos1/0/0
wtr 5
commit
#
return

5.16.2 Example for Configuring Single-hop BFD for an IP-Trunk

Member Link
In this example, single-hop BFD sessions on IP-Trunk member interfaces are configured to
rapidly check direct links between IP-Trunk member interfaces.
NOTE
POS interfaces cannot be configured on the -X1 and -X2 models ofNE80E/40Es.
On the network shown in Figure 5-5, an IP-Trunk link composed of two POS links exists
BFD is performed on the IP-Trunk member POS 1/0/0.
Figure 5-5 Networking diagram of configuring single-hop BFD for an IP-Trunk member link
POS1/0/0 POS1/0/0
RouterA IP-Trunk1 IP-Trunk1 RouterB

POS2/0/0 100.1.1.1/24 100.1.1.2/24 POS2/0/0
1. Create an IP-Trunk interface.
2. Configure single-hop BFD for a member link.
Data Preparation
To configure single-hop BFD for an IP-Trunk member link, you need the following data:
l Peer IP address for a BFD session, which is the IP address of the peer IP-Trunk member
interface
NOTE
Procedure
Step 1 Configure an IP-Trunk interface.
# Configure an IP-Trunk interface on Router A and set the lower threshold of IP-Trunk member
links in the Up state to 1.


[RouterA] interface ip-trunk 1
[RouterA-Ip-Trunk1] undo shutdown
[RouterA-Ip-Trunk1] ip address 100.1.1.1 255.255.255.0
[RouterA-Ip-Trunk1] least active-linknumber 1
[RouterA-Ip-Trunk1] quit
[RouterA-Pos1/0/0] link-protocol hdlc
[RouterA-Pos1/0/0] ip-trunk 1
# Configure an IP-Trunk interface on Router B and set the lower threshold of IP-Trunk member
[RouterB] interface ip-trunk 1
[RouterB-Ip-Trunk1] undo shutdown
[RouterB-Ip-Trunk1] ip address 100.1.1.2 255.255.255.0
[RouterB-Ip-Trunk1] least active-linknumber 1
[RouterB-Ip-Trunk1] quit
[RouterB-Pos1/0/0] link-protocol hdlc
[RouterB-Pos1/0/0] ip-trunk 1
After the configurations, run the display interface ip-trunk command on Router A or Router
B. You can view that the status of the IP-Trunk link is Up.

[RouterA] display interface ip-trunk 1
Ip-Trunk1 current state : UP
Line protocol current state : UP
Last line protocol up time: 2007-11-12, 10:18:09
Description : Ip-Trunk1 Interface, Route Port
Route Port,Hash arithmetic : According to flow,Maximal BW: 5G, Current BW: 5G, T,he
Maximum Transmit Unit is 4470
Internet Address is 100.1.1.1/24 Link layer protocol is nonstandard HDLC
Physical is IP_TRUNK
Last 300 seconds input rate 192 bits/sec, 0 packets/sec
Last 300 seconds output rate 24 bits/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: 69 packets,13465 bytes,
0 errors,71 drops,
Output:45 packets,1170 bytes,
0 errors,0 drops
Input bandwidth utilization : 0.01%
Output bandwidth utilization : 0.01%
-----------------------------------------------------
PortName Status Weight
-----------------------------------------------------
Pos2/0/0 UP 1
Pos2/0/3 UP 1
-----------------------------------------------------

The Number of Ports in Trunk : 2

The Number of UP Ports in Trunk : 2
The IP-Trunk interfaces of 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
Step 2 Configure single-hop BFD for the IP-Trunk member link.

# Configure a BFD session on Router A and bind the member interface POS 1/0/0 to the BFD
session.
[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd to_Link1 bind peer-ip default-ip interface pos 1/0/0
[RouterA-bfd-session-to_Link1] discriminator local 10
[RouterA-bfd-session-to_Link1] discriminator remote 20
[RouterA-bfd-session-to_Link1] wtr 5
[RouterA-bfd-session-to_Link1] commit
[RouterA-bfd-session-to_Link1] quit
# Configure a BFD session on Router B and bind the member interface POS 1/0/0 to the BFD
session.
[RouterB] bfd
[RouterB-bfd] quit
[RouterB] bfd to_Link1 bind peer-ip default-ip interface pos 1/0/0
[RouterB-bfd-session-to_Link1] discriminator local 20
[RouterB-bfd-session-to_Link1] discriminator remote 10
[RouterB-bfd-session-to_Link1] wtr 5
[RouterB-bfd-session-to_Link1] commit
[RouterB-bfd-session-to_Link1] quit

After the configurations are complete, run the display bfd session all verbose command on
Router A or Router B. You can view that a single-hop BFD session has been set up and its status
is Up.
--------------------------------------------------------------------------------
Session MIndex : 256 (One Hop) State : Up Name : to_link1
--------------------------------------------------------------------------------


Active Multi : 3
--------------------------------------------------------------------------------
Run the shutdown command on POS 1/0/0 of Router A.

[RouterA-Pos1/0/0] shutdown
Run the display bfd session all verbose command and the display interface ip-trunk command
on Router A and Router B. You can view that the status of the BFD session is Down and the
status of the IP-Trunk link is still Up.
--------------------------------------------------------------------------------
Session MIndex : 256 (One Hop) State : Down Name : to_link1
--------------------------------------------------------------------------------
Active Multi : 3
--------------------------------------------------------------------------------
Route Port,Hash arithmetic : According to flow,Maximal BW: 5G, Current BW: 5G, The
0 errors,71 drops,
0 errors,0 drops

-----------------------------------------------------
-----------------------------------------------------
Pos1/0/0 DOWN 1
Pos2/0/0 UP 1
-----------------------------------------------------
----End
Configuration Files
#
sysname RouterA
#
bfd
#
interface Ip-Trunk1
undo shutdown
ip address 100.1.1.1 255.255.255.0
#
interface Pos1/0/0
link-protocol hdlc
undo shutdown
ip-trunk 1
#
interface Pos2/0/0
link-protocol hdlc
undo shutdown
ip-trunk 1
#
bfd to_Link1 bind peer-ip default-ip interface pos 1/0/0
wtr 5
commit
#
return

#
sysname RouterB
#
bfd
#
interface Ip-Trunk1
undo shutdown
ip address 100.1.1.2 255.255.255.0
#
interface Pos1/0/0
link-protocol hdlc
undo shutdown
ip-trunk 1
#
interface Pos2/0/0
link-protocol hdlc
undo shutdown
ip-trunk 1
#
bfd to_Link1 bind peer-ip default-ip interface pos 1/0/0
wtr 5
commit
#
return

5.16.3 Example for Configuring Singe-hop BFD for an IP-Trunk

Link
In this example, a single-hop BFD session is configured to rapidly check direct links between
two IP-Trunk interfaces.
NOTE
On the network shown in Figure 5-6, an IP-Trunk link composed of two POS links exists
Single-hop BFD is performed on an IP-Trunk link.
Figure 5-6 Networking diagram of single-hop BFD for an IP-Trunk link
POS1/0/0 POS1/0/0
RouterA POS2/0/0 IP-Trunk1 IP-Trunk1

POS2/0/0 RouterB
100.1.1.1/24 100.1.1.2/24
1. Create an IP-Trunk interface.

2. Configure single-hop BFD for an IP-Trunk link.
Data Preparation
To configure single-hop BFD for an IP-Trunk link, you need the following data:
l Peer IP address for a BFD session, which is the IP address of the peer IP-Trunk interface
NOTE
Procedure
Step 1 Configure an IP-Trunk interface.
# Create an IP-Trunk interface on Router A and set the lower threshold of IP-Trunk member

NOTE
By default, the lower threshold of IP-Trunk member links in the Up state is 1. It is configurable based on
networking environments.
[RouterA] interface ip-trunk 1
[RouterA-Ip-Trunk1] undo shutdown
[RouterA-Ip-Trunk1] ip address 100.1.1.1 255.255.255.0
[RouterA-Ip-Trunk1] least active-linknumber 1
[RouterA-Ip-Trunk1] quit
# Create an IP-Trunk interface on Router B and set the lower threshold of IP-Trunk member
[RouterB] interface ip-trunk 1
[RouterB-Ip-Trunk1] undo shutdown
[RouterB-Ip-Trunk1] ip address 100.1.1.2 255.255.255.0
[RouterB-Ip-Trunk1] least active-linknumber 1
[RouterB-Ip-Trunk1] quit
After the configurations, run the display interface ip-trunk command on Router A or Router
B. You can view that the status of the interface is Up.

0 errors,0 drops,
0 errors,0 drops

-----------------------------------------------------
-----------------------------------------------------
Pos1/0/0 UP 1
Pos2/0/0 UP 1
-----------------------------------------------------
The IP-Trunk interface of Router A and the IP-Trunk interface of Router B can ping each other.
0.00% packet loss
Step 2 Configure the one-hop BFD for the IP-Trunk.

# Enable BFD on Router A, configure a BFD session between Router A and Router B, and bind
Router A's IP-Trunk interface to the BFD session.
[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd atob bind peer-ip 100.1.1.2 interface ip-trunk 1
# Enable BFD on Router B, configure the BFD session between Router B and Router A, and
bind Router B's IP-Trunk interface to the BFD session.
[RouterB] bfd
[RouterB-bfd] quit
[RouterB] bfd btoa bind peer-ip 100.1.1.1 interface ip-trunk 1

After the configurations, run the display bfd session all verbose command on Router A or
Router B. You can view that a single-hop BFD session has been set up and its status is Up.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
BFD Bind Type : Interface(Ip-Trunk 1)

Bind Interface : Ip-Trunk 1

Active Multi : 3
--------------------------------------------------------------------------------
Run the shutdown command on the POS 1/0/0 of Router A.

on Router A and Router B. You can view that the status of the BFD session and that of the IP-
Trunk interface are Up.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Active Multi : 3
--------------------------------------------------------------------------------


0 errors,0 drops,
0 errors,0 drops
-----------------------------------------------------
-----------------------------------------------------
Pos1/0/0 DOWN 1
Pos2/0/0 UP 1
-----------------------------------------------------
Run the shutdown command on POS 2/0/0 of Router A to.

on Router A and Router B. You can view that the status of the BFD session and that of the IP-
Trunk interface are Down.
--------------------------------------------------------------------------------
Session MIndex : 256 (One Hop) State : Down Name : atob
--------------------------------------------------------------------------------
Active Multi : 3
--------------------------------------------------------------------------------
Ip-Trunk1 current state : Down
Line protocol current state : Down


0 errors,0 drops,
0 errors,0 drops
-----------------------------------------------------
-----------------------------------------------------
Pos1/0/0 DOWN 1
Pos2/0/0 DOWN 1
-----------------------------------------------------
----End
Configuration Files
#
sysname RouterA
#
bfd
#
interface Ip-Trunk1
undo shutdown
ip address 100.1.1.1 255.255.255.0
#
interface Pos1/0/0
link-protocol hdlc
undo shutdown
ip-trunk 1
#
interface Pos2/0/0
link-protocol hdlc
undo shutdown
ip-trunk 1
#
bfd atob bind peer-ip 100.1.1.2 interface ip-trunk 1
wtr 5
commit
#
return
l Configuration file Router B

#
sysname RouterB
#
bfd
#
interface Ip-Trunk1
undo shutdown
ip address 100.1.1.2 255.255.255.0
#
interface Pos1/0/0
link-protocol hdlc
undo shutdown
ip-trunk 1
#
interface Pos2/0/0
link-protocol hdlc
undo shutdown
ip-trunk 1
#
bfd btoa bind peer-ip 100.1.1.1 interface ip-trunk 1

wtr 5
commit
#
return
5.16.4 Example for Configuring Single-hop BFD for a Layer 3 Eth-

Trunk Member Link
In this example, a single-hop BFD session is configured to rapidly check direct links between
two Eth-Trunk sub-interfaces.
On a network shown in Figure 5-7, an Eth-Trunk link composed of two GE links exists between
BFD is performed on the member link GE 1/0/0.
Figure 5-7 Networking diagram of single-hop BFD for a Layer 3 Eth-Trunk member link
GE1/0/0 GE1/0/0
RouterA GE2/0/0 Eth-Trunk1 Eth-Trunk1 GE2/0/0 RouterB

100.1.1.1/24 100.1.1.2/24
1. Create an Eth-Trunk interface.

2. Configure single-hop BFD for a specified member link.
Data Preparation
To configure the one-hop BFD for Layer 3 Eth-Trunk member link, you need the following data:
l Peer IP address for a BFD session, which is the IP address of an Eth-Trunk member link
l Local member link interface sending and receiving BFD control packets
NOTE

Procedure
Step 1 Configure an Eth-Trunk interface.
# Create an Eth-Trunk interface on Router A.

[RouterA] interface eth-trunk 1
[RouterA-Eth-Trunk1] undo shutdown
[RouterA-Eth-Trunk1] ip address 100.1.1.1 24
[RouterA-Eth-Trunk1] least active-linknumber 1
[RouterA-GigabitEthernet1/0/0] eth-trunk 1
# Create an Eth-Trunk interface on Router B.

[RouterB] interface eth-trunk 1
[RouterB-Eth-Trunk1] undo shutdown
[RouterB-Eth-Trunk1] ip address 100.1.1.2 24
[RouterB-Eth-Trunk1] least active-linknumber 1
[RouterB-Eth-Trunk1] quit
[RouterB-GigabitEthernet1/0/0] eth-trunk 1
After the configurations, run the display interface eth-trunk command on Router A or Router
B. You can view that the status of the interface is Up.

[RouterA] display interface eth-trunk 1
Eth-Trunk1 current state : UP
Current system time: 2010-08-30 18:02:12
Description: Eth-Trunk1 Interface
Internet Address is 100.1.1.1/24
IP Sending Frames" Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc90-5851
Physical is ETH_TRUNK
Input: 0 packets,0 bytes
0 unicast,0 broadcast,0 multicast
0 errors,0 drops
Output:0 packets,0 bytes
0 errors,0 drops

-----------------------------------------------------
-----------------------------------------------------
GigabitEthernet1/0/0 UP 1
-----------------------------------------------------
The Eth-Trunk interfaces of Router A and Router B can ping each other.
[RouterA] ping -a 100.1.1.1 100.1.1.2
0.00% packet loss
Step 2 Configure single-hop BFD for a Layer 3 Eth-Trunk member link.

# Configure a BFD session on Router A and bind the member interface GE 1/0/0 to the BFD
session.
[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd to_link1 bind peer-ip default-ip interface gigabitethernet 1/0/0
[RouterA-bfd-session-to_link1] discriminator local 10
[RouterA-bfd-session-to_link1] discriminator remote 11
[RouterA-bfd-session-to_link1] wtr 5
[RouterA-bfd-session-to_link1] commit
[RouterA-bfd-session-to_link1] quit
# Configure the BFD session on Router B and bind the member link interface GE 1/0/0.
[RouterB] bfd
[RouterB-bfd] quit
[RouterB] bfd to_link1 bind peer-ip default-ip interface gigabitethernet 1/0/0
[RouterB-bfd-session-to_link1] discriminator local 11
[RouterB-bfd-session-to_link1] discriminator remote 10
[RouterB-bfd-session-to_link1] wtr 5
[RouterB-bfd-session-to_link1] commit
[RouterB-bfd-session-to_link1] quit

After the configurations, run the display bfd session all verbose command on Router A and
Router B. You can view that the single-hop BFD session has been set up and its status is Up.
Use the display on Route A as an example.
--------------------------------------------------------------------------------
Session MIndex : 256 (One Hop) State : Up Name : to_link1
--------------------------------------------------------------------------------


Active Multi : 3
--------------------------------------------------------------------------------
Run the shutdown command on GE 1/0/0 of Router A. You can view that the BFD session is
Down and the Eth-Trunk status is still Up.
--------------------------------------------------------------------------------
Session MIndex : 256 (One Hop) State : Down Name : to_link1
--------------------------------------------------------------------------------
Active Multi : 3
--------------------------------------------------------------------------------
0 errors,0 drops
0 errors,0 drops

-----------------------------------------------------
-----------------------------------------------------
GigabitEthernet1/0/0 DOWN 1
-----------------------------------------------------
----End
Configuration Files
#
sysname RouterA
#
bfd
#
undo shutdown
ip address 100.1.1.1 255.255.255.0
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
bfd to_link1 bind peer-ip default-ip interface GigabitEthernet 1/0/0
wtr 5
commit
#
return

#
sysname RouterB
#
bfd
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
bfd to_link1 bind peer-ip default-ip interface GigabitEthernet 1/0/0
wtr 5
commit
#
return

5.16.5 Example for Configuring Single-hop BFD for a Layer 3 Eth-

Trunk Link
In this example, single-hop BFD is configured to rapidly detect and monitor direct links between
two Eth-Trunk interfaces.
Networking requirements
On the network shown in Figure 5-8, an Eth-Trunk link composed of two GE links exists
BFD is performed on the Eth-Trunk link.
Figure 5-8 Networking diagram of configuring single-hop BFD for a Layer 3 Eth-Trunk link
GE1/0/0 GE1/0/0
RouterA GE2/0/0 Eth-Trunk1 Eth-Trunk1 GE2/0/0 RouterB

100.1.1.1/24 100.1.1.2/24
1. Create an Eth-Trunk interface.

2. Configure single-hop BFD for a Layer 3 Eth-Trunk link.
Data Preparation
To configure single-hop BFD for a Layer 3 Eth-Trunk link, you need the following data:
l Peer IP address for a BFD session, which is the IP address of the peer Eth-Trunk interface
NOTE
Procedure
Step 1 Configure an Eth-Trunk interface.
# Create an Eth-Trunk interface on Router A and set the lower threshold of Eth-Trunk member

NOTE
By default, the lower threshold of Eth-Trunk member links in the Up state is 1. It is configurable based on
networking environments.
[RouterA] interface eth-trunk 1
[RouterA-Eth-Trunk1] undo shutdown
[RouterA-Eth-Trunk1] ip address 100.1.1.1 24
[RouterA-Eth-Trunk1] least active-linknumber 1
# Create an Eth-Trunk interface on Router B and set the lower threshold of Eth-Trunk member
[RouterB] interface eth-trunk 1
[RouterB-Eth-Trunk1] undo shutdown
[RouterB-Eth-Trunk1] ip address 100.1.1.2 24
[RouterB-Eth-Trunk1] least active-linknumber 1
[RouterB-Eth-Trunk1] quit
After the configurations are complete, run the display interface eth-trunk command on Router
A or Router B. You can view that the status of the interface is Up.
0 errors,0 drops
0 errors,0 drops
-----------------------------------------------------
-----------------------------------------------------

-----------------------------------------------------
The Eth-Trunk interfaces of Router A and Router B can ping each other.
[RouterA] ping -a 100.1.1.1 100.1.1.2
0.00% packet loss
Step 2 Configure single-hop BFD for a Layer 3 Eth-Trunk link.

Router A's Eth-Trunk interface to the BFD session.
[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd atob bind peer-ip 100.1.1.2 interface eth-trunk 1
# Enable BFD on Router B, configure the BFD session between Router B and Router A, and
bind Router B's Eth-Trunk interface to the BFD session.
[RouterB] bfd
[RouterB-bfd] quit
[RouterB] bfd btoa bind peer-ip 100.1.1.1 interface eth-trunk 1

Router B. You can view that the single-hop BFD session has been set up and its status is Up.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
BFD Bind Type : Interface(Eth-Trunk1)
Bind Interface : Eth-Trunk1


Active Multi : 3
--------------------------------------------------------------------------------
Run the shutdown command on the GE 1/0/0 of Router A.

Run the display bfd session all verbosecommand and the display interface eth-trunk
command on Router A and Router B. You can view that both the BFD session and Eth-Trunk
interface are still Up.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Active Multi : 3
--------------------------------------------------------------------------------
0 errors,0 drops


0 errors,0 drops
-----------------------------------------------------
-----------------------------------------------------
-----------------------------------------------------
Run the shutdown command on GE 2/0/0 of Router A.
Run the display bfd session all verbose command and the display interface eth-trunk
command on Router A and Router B. You can view that both the BFD session and Eth-Trunk
interface become Down.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Active Multi : 3
--------------------------------------------------------------------------------
Eth-Trunk1 current state : Down
Line protocol current state : Down
0 errors,0 drops
0 errors,0 drops


-----------------------------------------------------
-----------------------------------------------------
-----------------------------------------------------
----End
Configuration Files
#
sysname RouterA
#
bfd
#
undo shutdown
ip address 100.1.1.1 255.255.255.0
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
bfd atob bind peer-ip 100.1.1.2 interface Eth-Trunk 1
wtr 5
commit
#
return

#
sysname RouterB
#
bfd
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
#
undo shutdown
eth-trunk 1
#
undo shutdown
eth-trunk 1
#
bfd btoa bind peer-ip 100.1.1.1 interface Eth-Trunk 1
wtr 5
commit
#
return

5.16.6 Example for Configuring Single-hop BFD for VLANIF

Interfaces
In this example, a single-hop BFD session is configured on VLANIF interfaces to rapidly check
direct links between the VLANIF interfaces.
On the network shown in Figure 5-9, an Ethernet link exists between Router A and Router B.
GE 1/0/0 on Router A and GE 1/0/0 on Router B belong to the same VLAN. A single-hop BFD
session needs to be set up to check the VLANIF interfaces.
Figure 5-9 Networking diagram of single-hop BFD for VLANIF interfaces
VLANIF10: 110.1.1.1/24 VLANIF10: 110.1.1.2/24

GE1/0/0 GE1/0/0
RouterA RouterB
Configuration Roadmaps
1. Configure a VLAN based on the interface.
2. Configure a single-hop BFD session between VLANIF interfaces.
Data Preparation
To configure single-hop BFD for VLANIF interfaces, you need the following data:
l Peer IP address for a BFD session, which is the IP address of the peer VLANIF interface
NOTE
Procedure
Step 1 Configure VLAN 10.
# Configure VLAN 10 on Router A.
[RouterA] vlan 10


[RouterA-vlan10] quit
[RouterA] interface vlanif 10
[RouterA-Vlanif10] undo shutdown
[RouterA-Vlanif10] ip address 110.1.1.1 24
[RouterA-Vlanif10] quit
# Configure VLAN 10 on Router B.

[RouterB-GigabitEthernet1/0/0] portswitch
[RouterB] vlan 10
[RouterB-vlan10] port gigabitethernet 1/0/0
[RouterB-vlan10] quit
[RouterB] interface vlanif 10
[RouterB-Vlanif10] undo shutdown
[RouterB-Vlanif10] ip address 110.1.1.2 24
[RouterB-Vlanif10] quit
After the configuration, run the display interface vlanif command on Router A or Router B.
You can view that the interface is Up.
[RouterA] display interface vlanif 10
Vlanif10 current state : UP
Description: Vlanif10 Interface
Route Port,The Maximum Transmit Unit is 1500
IP Sending Frames" Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc50-c43d
Physical is VLANIF
Input bandwidth utilization : --
Output bandwidth utilization : --
The VLANIF interfaces on Router A and Router B can ping each other.
[RouterA] ping -a 110.1.1.1 110.1.1.2
0.00% packet loss
Step 2 Configure single-hop BFD for VLANIF interfaces.

the VLANIF interface to the BFD session.
[RouterA] bfd

[RouterA-bfd] quit
[RouterA] bfd atob bind peer-ip 110.1.1.2 interface vlanif 10
# Enable BFD on Router B, configure a BFD session between Router B and Router A, and bind
the VLANIF interface to the BFD session.
[RouterB] bfd
[RouterB-bfd] quit
[RouterB] bfd btoa bind peer-ip 110.1.1.1 interface vlanif 10

Router B, You can view that a single-hop BFD session has been set up and its status is Up.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
BFD Bind Type : Interface(Vlanif10)
Bind Interface : Vlanif10
Active Multi : 3
--------------------------------------------------------------------------------
Run the shutdown command on the GE 1/0/0 of Router A.

Run the display bfd session all verbose command on Router A and Router B. You can view
that the status of the BFD session becomes Down.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


BFD Bind Type : Interface(Vlanif10)
Bind Interface : Vlanif10
Active Multi : 3
--------------------------------------------------------------------------------
----End
Configuration Files
#
sysname RouterA
#
vlan batch 10
#
bfd
#
interface Vlanif10
undo shutdown
ip address 110.1.1.1 255.255.255.0
#
undo shutdown
portswitch
#
bfd atob bind peer-ip 110.1.1.2 interface vlanif 10
commit
#
return

#
sysname RouterB
#
vlan batch 10
#
bfd
#
interface Vlanif10
undo shutdown
ip address 110.1.1.2 255.255.255.0
#
undo shutdown
portswitch


#
bfd btoa bind peer-ip 110.1.1.1 interface vlanif 10
commit
#
return
5.16.7 Example for Configuring the Association Between the BFD

Status and the Interface Status
In this example, association between the BFD session status and the interface status is configured
to trigger rapid route convergence.
On the network shown in Figure 5-10, transmission devices exist on a link. If a link between
transmission devices fails, Router A and Router B take a long time to detect the link failure. This
causes a long route aging time and long traffic interruption. In this case, you can configure the
association between the BFD sessions status and the interface status. The status of the BFD
session between GE 1/0/0 on Router A and GE 1/0/0 on Router B can affect the protocol status
of these interfaces, which triggers rapid route convergence.
Figure 5-10 Configuring the association between the BFD status and the interface status
GE1/0/0 GE1/0/0
RouterA RouterB
1. Configure a BFD session on Router A.

2. Configure a BFD session on Router B.
3. Configure the association between the BFD status and the interface status on Router A
when the BFD session is Up.
4. Configure the association between the BFD status and the interface status on Router B
when the BFD session is Up.
Data Preparation


NOTE
The default minimum sending interval, minimum receiving interval, and local detection multiplier for BFD
control packets are used.
Procedure
Step 1 Configure the IP addresses of the interfaces directly connecting Router A andRouter B.
# Configure the IP address of the interface on Router A.
# Configure the IP address of the interface on Router B.

Step 2 Configure a single-hop BFD session.

# On Router A, enable BFD and configure a BFD session between Router A and Router B.
[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd atob bind peer-ip default-ip interface gigabitethernet 1/0/0
# On Router B, enable BFD and configure a BFD session between Router B and Router A.
[RouterB] bfd
[RouterB-bfd] quit
[RouterB] bfd btoa bind peer-ip default-ip interface gigabitethernet 1/0/0
# After the configuration, run the display bfd session all verbose command on Router A and
Router B. You can view that a single-hop BFD session has been created and its status Up.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Active Multi : 3
--------------------------------------------------------------------------------
Step 3 Configure the association between the BFD status and the interface status.
# Configure the association between the BFD status and the interface status on Router A.
[RouterA] bfd atob
[RouterA-bfd-session-atob] process-interface-status
[RouterA-bfd-session-atob] process-pst
# Configure the association between the BFD status and the interface status on Router B.
[RouterB] bfd btoa
[RouterB-bfd-session-btoa] process-interface-status
[RouterA-bfd-session-atob] process-pst

Router B. You can view that the Proc interface status field displays Enable.
Take Router A as an example.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Active Multi : 3
Bind Application :IFNET
--------------------------------------------------------------------------------

Run the shutdown command on GE 1/0/0 of Router B. You can view that the BFD session goes
Down.
[RouterB-GigabitEthernet1/0/0] shutdown
Run the display bfd session all verbose and display interface gigabitethernet 1/0/0 commands
on Router A. You can view that the status of the BFD session is Down, and the status of GE
1/0/0 is UP (BFD status down).
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Active Multi : 3
Last Local Diagnostic : Neighbor Signaled Session Down
--------------------------------------------------------------------------------
[RouterA] display interface gigabitethernet 1/0/0
GigabitEthernet1/0/0 current state : UP
Line protocol current state : UP(BFD status down)
Last line protocol up time: 2008-10-16 09:25:17
Description : GigabitEthernet1/0/0 Interface, Route Port
The Maximum Transmit Unit is 1500 bytes
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fcc7-565a
The Vendor PN is HFBR-5710L
Port BW: 1G, Transceiver max BW: 1G, Transceiver Mode: MultiMode
WaveLength: 850nm, Transmission Distance: 550m
Loopback:none, full-duplex mode, negotiation: disable, Pause Flowcontrol:Send and
Receive Enable
Last physical up time : 2008-10-16 09:18:48
Last physical down time : 2008-10-16 09:18:42
Statistics last cleared:never
Last 300 seconds input rate: 56 bits/sec, 0 packets/sec
Last 300 seconds output rate: 88 bits/sec, 0 packets/sec
Input: 420904 bytes, 5802 packets
Output: 1250456 bytes, 13926 packets
Input:
Unicast: 461 packets, Multicast: 5331 packets
Broadcast: 10 packets, Jumbo: 0 packets
CRC: 3 packets, Symbol: 0 packets
Overrun: 0 packets, InRangeLength: 0 packets
LongPacket: 0 packets, Jabber: 0 packets, Alignment: 0 packets
Fragment: 0 packets, Undersized Frame: 0 packets

RxPause: 0 packets
Output:
Broadcast: 11 packets, Jumbo: 0 packets
Lost: 0 packets, Overflow: 0 packets, Underrun: 0 packets
TxPause: 0 packets
Unknown Vlan: 0 packets
----End
Configuration Files
#
sysname RouterA
#
bfd
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
bfd atob bind peer-ip default-ip interface GigabitEthernet1/0/0
wtr 5
process-pst
commit
#
return

#
sysname RouterB
#
bfd
#
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
bfd btoa bind peer-ip default-ip interface GigabitEthernet1/0/0
wtr 5
process-pst
commit
#
return
5.16.8 Example for Configuring the Association Between the BFD

Status and the Sub-interface Status
In this example, association between the BFD session status and the sub-interface status is
configured, improving reliability of service transmission on sub-interfaces.
On the large-scale MAN Ethernet network shown in Figure 5-11 that has high requirements for
reliability, a large number of services need to be configured on a sub-interface. BFD sessions
are configured to check the connectivity of the main interface link and the BFD status is

associated with the sub-interface status, improving the reliability of services on the sub-interface
and saving the session resources.
Figure 5-11 Association between the BFD status and the sub-interface status
GE1/0/0 GE1/0/0
GE1/0/0.1 GE1/0/0.1
RouterA RouterB
1. Configure a BFD session on Router A.
2. Configure a BFD session on Router B.
3. Associate the BFD status with the sub-interface status when the BFD session on Router A
is Up.
4. Associate the BFD status with the sub-interface status when the BFD session on Router B
is Up.
Data Preparation
To configure the association between the BFD status and the sub-interface status, you need the
following data:
l IP address of the main interface on the remote end of a BFD session

l Local discriminator and remote discriminator of the BFD session
NOTE
The minimum sending interval, the minimum receiving interval, and the local detection multiplier of the
BFD Control packet adopt the default values.
Procedure
Step 1 Configure the IP addresses of the main interfaces on Router A and Router B and create the sub-
interface.
# Configure the IP address of the interface on Router A and create the sub-interface.
[RouterA-GigabitEthernet1/0/0.1] vlan-type dot1q 10

# Configure the IP address of the interface on Router B and create the sub-interface.
[RouterB-GigabitEthernet1/0/0.1] vlan-type dot1q 10

# On Router A, enable BFD and configure a BFD session between Router A and Router B and
bind the session with the main interface.
[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd atob bind peer-ip default-ip interface gigabitethernet 1/0/0
# On Router B, enable BFD and configure a BFD session between Router B and Router A and
bind the session with the main interface.
[RouterB] bfd
[RouterB-bfd] quit
[RouterB] bfd btoa bind peer-ip default-ip interface gigabitethernet 1/0/0
# After the configuration is complete, run the display bfd session all verbose command on
Router A and Router B, and you can view that a one-hop BFD session is set up, and the session
status is Up.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Active Multi : 3


--------------------------------------------------------------------------------
Step 3 Configure the association between the BFD status and the sub-interface status.
# Configure the association between the BFD status and the sub-interface status on Router A.
[RouterA] bfd atob
[RouterA-bfd-session-atob] process-interface-status sub-if
# Configure the association between the BFD status and the sub-interface status on Router B.
[RouterB] bfd btoa
[RouterB-bfd-session-btoa] process-interface-status sub-if
# After the configuration is complete, run the display bfd session all verbose command on
Router A and Router B, and you can view that the field Proc interface status displays Enable
(Sub-If).

--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Proc interface status : Enable (Sub-If) Process PST : Disable
Active Multi : 3
--------------------------------------------------------------------------------
# Run the shutdown command on GE 1/0/0 of Router B. You can view that the BFD session
goes Down.
[RouterB-GigabitEthernet1/0/0] shutdown

# Run the display bfd session all verbose and display interface gigabitethernet1/0/0.1
commands on Router A, and you can view that the status of the BFD session is Down, and the
status of GE1/0/0.1 is UP (Main BFD status down).
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Active Multi : 3
Last Local Diagnostic : Neighbor Signaled Session Down
--------------------------------------------------------------------------------
[RouterA] display interface gigabitethernet 1/0/0.1
GigabitEthernet1/0/0.1 current state : UP
Line protocol current state : UP(Main BFD status down)
Route Port,The Maximum Transmit Unit is 1500 bytes
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fcc7-565a
Encapsulation dot1q Virtual LAN, Vlan number 1
Statistics last cleared:never
Last 300 seconds input rate 0 bytes/sec, 0 packets/sec
Last 300 seconds output rate 0 bytes/sec, 0 packets/sec
0 errors,0 drops
0 errors,0 drops
----End
Configuration Files
#
sysname RouterA
#
bfd
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
undo shutdown
vlan-type dot1q 10

ip address 11.1.1.1 255.255.255.0

#
bfd atob bind peer-ip 10.1.1.2 interface GigabitEthernet1/0/0
commit
#
return

#
sysname RouterB
#
bfd
#
undo shutdown
ip address 11.1.1.2 255.255.255.0
#
undo shutdown
vlan-type dot1q 10
ip address 10.1.1.2 255.255.255.0
#
bfd btoa bind peer-ip 10.1.1.1 interface GigabitEthernet1/0/0
commit
#
return
5.16.9 Example for Configuring Multi-Hop BFD

In this example, a BFD session is created on both ends of a multi-hop path to fast detect faults
in the multi-hop path.
NOTE
On the network shown in Figure 5-12, BFD in asynchronous mode is used to detect faults in
multi-hop routes between Router A and Router C.
Figure 5-12 Networking diagram of multi-hop BFD
POS1/0/0 POS1/0/0 POS2/0/0 POS1/0/0

10.1.1.1/24 10.1.1.2/24 10.2.1.1/24 10.2.1.2/24
RouterA RouterB RouterC

1. Configure a BFD session on Router A to detect faults in multi-hop routes between Router
A and Router C.
2. Configure a BFD session on Router C to detect faults in multi-hop routes between Router
C and Router A.
Data Preparation
NOTE
Procedure
Step 1 Configure reachable routes between Router A, Router B, and Router C.
In this example, static routes are used. The detailed configurations are not provided.
Step 2 Configure multi-hop BFD between Router A and Router C.
# Configure a BFD session between Router A and Router C.
The interface is not bound to the BFD session.
[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd atoc bind peer-ip 10.2.1.2
[RouterA-bfd-session-atoc] discriminator remote 20
[RouterA-bfd-session-atoc] wtr 10
# Configure a BFD session between Router C and Router A.

<RouterC> system-view
[RouterC] bfd
[RouterC-bfd] quit
[RouterC] bfd ctoa bind peer-ip 10.1.1.1
[RouterC-bfd-session-ctoa] discriminator local 20
[RouterC-bfd-session-ctoa] discriminator remote 10
[RouterC-bfd-session-ctoa] wtr 10
[RouterC-bfd-session-ctoa] commit
[RouterC-bfd-session-ctoa] quit

Router C. You can view that a multi-hop BFD session has been set up and its status is Up.
<RouterA> display bfd session all
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Bind Interface : --
Active Multi : 3
--------------------------------------------------------------------------------
----End
Configuration Files
#
sysname RouterA
#
bfd
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
bfd atoc bind peer-ip 10.2.1.2
wtr 10
commit
#
ip route-static 10.2.1.0 255.255.255.0 10.1.1.2
#
return

#
sysname RouterB
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.2.1.1 255.255.255.0
#
return

#
sysname RouterC

#
bfd
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.2.1.2 255.255.255.0
#
bfd ctoa bind peer-ip 10.1.1.1
wtr 10
commit
#
ip route-static 10.1.1.0 255.255.255.0 10.2.1.1
#
return
5.16.10 Example for Configuring the BFD Demand Mode

In this example, the demand mode for a BFD session is configured to prevent the system from
being affected by the cost of BFD packets that are sent periodically.
NOTE
On the network shown in Figure 5-13, BFD in demand mode is used to detect faults in multi-
hop routes between Router A and Router B.
Figure 5-13 Networking diagram of configuring demand mode of the BFD

POS1/0/0 POS1/0/0 POS2/0/0 POS1/0/0
10.1.1.1/24 10.1.1.2/24 10.2.1.1/24 10.2.1.2/24
1. Configure a BFD session on Router A to detect faults in multi-hop routes between Router
A and Router C.
2. Configure a BFD session on Router C to detect faults in multi-hop routes between Router
C and Router A.
NOTE
The configurations of the demand mode and the asynchronous mode are similar. The difference is that if
the demand mode is used, the demand command should be configured in the BFD session view.
Data Preparation


l Interval at which demand sequences are sent
Default values of the minimum sending interval, minimum receiving interval, and local detection
multiplier for BFD control packets are used.
Procedure
Step 1 Configure routes to Router A, Router B and Router C to be reachable.
In this configuration example, static routes are used. The detailed configurations are not
provided.
# Configure a BFD session with Router C on Router A.
[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd atoc bind peer-ip 10.2.1.2
# Configure the demand mode, and the demand sequence is sent every minute.
[RouterA-bfd-session-atoc] demand
[RouterA-bfd-session-atoc] demand timer 60000
# Configure a BFD session with Router A on Router C.

<RouterC> system-view
[RouterC] bfd
[RouterC-bfd] quit
[RouterC] bfd ctoa bind peer-ip 10.1.1.1
# Configure the demand mode.

[RouterC-bfd-session-ctoa] demand

After the configurations, run the display bfd session all verbose command. You can view that
a multi-hop BFD session has been set up and its status is Up. The detection mode is Demand
Mode Without Echo Function.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Session Detect Mode : Demand Mode Without Echo Function


Bind Interface : --
Active Multi : 3
--------------------------------------------------------------------------------
----End
Configuration Files
#
sysname RouterA
#
bfd
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
bfd atoc bind peer-ip 10.2.1.2
demand
demand timer 60000
commit
#
ip route-static 10.2.1.0 255.255.255.0 10.1.1.2
#
return

#
sysname RouterB
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.2.1.1 255.255.255.0
#
return

#
sysname RouterC

#
bfd
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.2.1.2 255.255.255.0
#
bfd ctoa bind peer-ip 10.1.1.1
demand
commit
#
ip route-static 10.1.1.0 255.255.255.0 10.2.1.1
#
return
5.16.11 Example for Configuring a BFD Session with the One-Arm

Echo Function
In this example, configuring the one-arm Echo function on a BFD-capable device on one end
of a link allows you to use BFD to rapidly detect and monitor the direct link between the BFD-
capable device and its BFD-incapable peer.
On the network shown in Figure 5-14, Router A supports BFD but Router B does not. A BFD
session with the one-arm Echo function needs to be configured on Router A to fast detect the
direct link between Router A and Router B. After receiving a BFD packet sent by Router A,
Router B directly loops back the packet, thus achieving fast detection over the link.
Figure 5-14 Networking diagram of the one-arm Echo function configuration
RouterA Single-hop RouterB

BFD session
GE1/0/0 GE1/0/0
10.1.1.1/24 10.1.1.2/24
BFD-capable BFD-incapable
1. Configure a BFD session on Router A to detect the direct link between Router A and
Router B.
Data Preparation

l Peer IP address to which a BFD session with the one-arm Echo function is bound
l Local discriminator of a BFD session with the one-arm Echo function
l The minimum interval between the receipt of BFD packets
Procedure
Step 1 Assign IP addresses to the interfaces directly connecting Router A and Router B.
# Assign an IP address to the interface on Router A.
# Assign an IP address to the interface on Router B.

Step 2 Configure a BFD session with the one-arm Echo function.

[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd atob bind peer-ip 10.1.1.2 interface gigabitEthernet1/0/0 one-arm-
echo
[RouterA-bfd-session-atob] min-echo-rx-interval 100

After the preceding configurations are complete, run the display bfd session all verbose
command on Router A. You can see that a single-hop BFD session has been created and its status
is Up.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Session Detect Mode : Asynchronous One-arm-echo Mode
BFD Bind Type : Interface(gigabitEthernet1/0/0)
Bind Interface : EigabitEthernet1/0/0
Active Multi : 3


--------------------------------------------------------------------------------
----End
Configuration files
#
sysname RouterA
#
bfd
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
bfd atob bind peer-ip 10.1.1.2 interface gigabitEthernet1/0/0 one-arm-echo
commit
#
return

#
sysname RouterB
#
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
return
5.16.12 Example for Configuring BFD for VPN Routes

In this example, a BFD session on interfaces of a VPN is configured to detect faults in VPN
routes.
NOTE
ATM interfaces cannot be configured on the -X1 and -X2 models ofNE80E/40Es.
Figure 5-15 shows a networking diagram of BFD for VPN routes.

l CE1 and CE2 belong to VPN-A. They access an MPLS backbone network through PE1
and PE2 respectively.
l GE 1/0/0 of PE1 and GE 1/0/0 of PE2 are bound to VPN-A.
l BFD in asynchronous mode is used to detect faults in the VPN route between PE1 and PE2.

Figure 5-15 Networking diagram of BFD for VPN routes
Loopback1 Loopback1 Loopback1

1.1.1.1/32 2.2.2.2/32 3.3.3.3/32
POS1/0/0 POS2/0/0
172.1.1.2/24 172.2.1.1/24
PE1 PE2
POS2/0/0 POS2/0/0
GE1/0/0 172.1.1.1/24 P 172.2.1.2/24 GE1/0/0
10.1.1.2/24 10.2.1.2/24
MPLS Backbone
AS:100
GE1/0/0 GE1/0/0
10.1.1.1/24 10.2.1.1/24
CE1 CE2
VPN-A VPN-A
AS:65410 AS:65420
1. Configure a BFD session on PE1 to detect faults in a multi-hop path from PE1 to PE2.
2. Configure a BFD session on PE2 to detect faults in a multi-hop path from PE2 to PE1.
Data Preparation
To configure BFD for VPN routes, you need the following data:
NOTE
Procedure
Step 1 Configure an MPLS backbone network to interconnect PE1 and PE2. The detailed configurations
are not provided.
Step 2 Configure a VPN instance. The detailed configurations are not provided.
Step 3 Configure a VPN route between PE1 and PE2 to be reachable. The detailed configurations are
not provided.
After the configuration is complete, PE1 can ping the IP address of GE 1/0/0 on PE2.
<PE1> ping -vpn-instance vpna 10.2.1.2


0.00% packet loss
Step 4 Configure BFD for the VPN route between PE1 and PE2.
# On PE1, configure a BFD session between PE1 and PE2 and bind the session to the VPN
instance.
<PE1> system-view
[PE1] bfd
[PE1-bfd] quit
[PE1] bfd 1to2_vpn bind peer-ip 10.2.1.2 vpn-instance vpna
[PE1-bfd-session-1to2_vpn] discriminator local 12
[PE1-bfd-session-1to2_vpn] discriminator remote 21
[PE1-bfd-session-1to2_vpn] wtr 5
[PE1-bfd-session-1to2_vpn] commit
# On PE2, configure a BFD session between PE2 and PE1 and bind the session to the VPN
instance.
<PE2> system-view
[PE2] bfd
[PE2-bfd] quit
[PE2] bfd 2to1_vpn bind peer-ip 10.1.1.2 vpn-instance vpna
[PE2-bfd-session-2to1_vpn] discriminator local 21
[PE2-bfd-session-2to1_vpn] discriminator remote 12
[PE2-bfd-session-2to1_vpn] wtr 5
[PE2-bfd-session-2to1_vpn] commit

After the configuration, run the display bfd session peer-ip command on PE1 and PE2. You
can view that a multi-hop BFD session has been set up, and its status is Up.
Use the display on PE1 as an example.
<PE1> display bfd session peer-ip 10.2.1.2 vpn-instance vpna verbose
--------------------------------------------------------------------------------
Session MIndex : 256 (Multi Hop) State : Up Name : 1to2_vpn
--------------------------------------------------------------------------------
Bind Interface : --
Vpn Instance Name : vpna
Active Multi : 3

--------------------------------------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
ip vpn-instance vpna
ipv4-family
#
mpls lsr-id 1.1.1.1
mpls
#
mpls ldp
#
bfd
#
undo shutdown
ip binding vpn-instance vpna
ip address 10.1.1.2 255.255.255.0
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 172.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
bfd 1to2_vpn bind peer-ip 10.2.1.2 vpn-instance vpna
wtr 5
commit
#
bgp 100
#
ipv4-family unicast
peer 3.3.3.3 enable
#
ipv4-family vpnv4
policy vpn-target
peer 3.3.3.3 enable
#
ipv4-family vpn-instance vpna
import-route direct
#
ospf 100
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 172.1.1.0 0.0.0.255
#
return


#
sysname PE2
#
ipv4-family
#
mpls lsr-id 3.3.3.3
mpls
#
mpls ldp
#
bfd
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 172.2.1.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
ip address 10.2.1.2 255.255.255.0
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
bfd 2to1_vpn bind peer-ip 10.1.1.2 vpn-instance vpna
wtr 5
commit
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.1 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.1 enable
#
ipv4-family vpn-instance vpn1
import-route direct
#
ospf 100
area 0.0.0.0
network 3.3.3.3 0.0.0.0
network 172.2.1.0 0.0.0.255
#
return
l Configuration file of the P

#
sysname P
#
mpls lsr-id 2.2.2.2
mpls
#
mpls ldp

#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 172.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 172.2.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ospf 100
area 0.0.0.0
network 172.1.1.0 0.0.0.255
network 172.2.1.0 0.0.0.255
network 2.2.2.2 0.0.0.0
#
Return
l Configuration file of CE1

#
sysname CE1
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
bgp 65410
#
ipv4-family unicast
import-route direct
peer 10.1.1.2 enable
#
return

#
sysname CE2
#
undo shutdown
ip address 10.2.1.1 255.255.255.0
#
bgp 65420
#
ipv4-family unicast
import-route direct
#
return
5.16.13 Example for Configuring Sub-interfaces for Dot1q VLAN

Tag Termination to Support BFD
On a typical network, sub-interfaces for dot1q VLAN tag termination are configured to support
BFD. In this manner, user packets with one tag can be reliably and stably sent over the network.

On the network shown in Figure 5-16, users of VLAN 10 access an ISP network through a
default gateway. GE 2/0/0.1 is a sub-interface for dot1q VLAN tag termination on Router A,
and GE 2/0/0.1 is a sub-interface for dot1q VLAN tag termination on Router B.
The networking requirements are as follows:
l A BFD session is configured on Router A and Router B to detect the link between
l VRRP backup group 1 is configured on Router A and Router B. Router A functions as a
master device and Router B functions as a backup device.
l VRRP backup group 1 on Router A and Router B to track the status of the BFD session.
Figure 5-16 Networking diagram of configuring sub-interfaces for dot1q VLAN tag termination
to support BFD
MPLS/IP
backbone
GE1/0/0 GE2/0/0
192.168.2.2/24 192.168.1.2/24
RouterC
GE1/0/0 GE1/0/0
192.168.2.1/24 192.168.1.1/24
RouterA RouterB
GE2/0/0.1 BFD session GE2/0/0.1

100.1.1.1/24 100.1.1.2/24
GE1/0/1 GE1/0/2
Switch
GE1/0/0
VLAN10
Host 100.1.1.3/24

1. Configure interface modes on Router A and Router B as user termination.

3. Configure the Layer 2 forwarding function on the switch.
4. Configure sub-interfaces for dot1q VLAN tag termination on Router A and Router B.
5. Configure a BFD session on Router A and Router B to detect the link between Router A
and Router B.
6. Configure VRRP backup group 1 on GE 2/0/0.1 of Router A and GE 2/0/0.1 of Router B.
Router A functions as a master device and Router B functions as a backup device.
Data Preparation
l Name of the BFD session
l ID and virtual IP address of the VRRP backup group
l Tag value of sub-interfaces for dot1q termination
Procedure
Step 2 Configure an IGP to ensure connectivity between devices.

Assign IP addresses to interfaces as shown in Figure 5-16. Configure an IGP on Router A,
Router B, and Router C. OSPF is adopted in this example.
[RouterA] ospf 1

[RouterB] ospf 1
[RouterC-GigabitEthernet1/0/0] ip address 192.168.2.2 24
[RouterC] ospf 1
[RouterC-ospf-1] quit
After the configuration, OSPF on Router A and Router B calculates the routes between
Router A and Router B. Router A and Router B can ping each other.
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------

192.168.2.0/24 Direct 0 0 D 192.168.2.1
192.168.1.0/24 OSPF 10 2 D 192.168.2.2
100.1.1.0/24 Direct 0 0 D 100.1.1.1
GigabitEthernet2/0/0.1
------------------------------------------------------------------------------

192.168.2.0/24 Direct 0 0 D 192.168.2.1
192.168.2.1/32 Direct 0 0 D 127.0.0.1
192.168.1.0/24 OSPF 10 2 D 192.168.2.2

100.1.1.0/24 Direct 0 0 D 100.1.1.1


0.00% packet loss
Step 3 Configure the Layer 2 forwarding function on the 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] undo shutdown
[Switch-GigabitEthernet1/0/1] port trunk allow-pass vlan 10
[Switch-GigabitEthernet1/0/1] quit
[Switch] interface gigabitethernet 1/0/2
[Switch-GigabitEthernet1/0/2] undo shutdown
[Switch-GigabitEthernet1/0/2] port trunk allow-pass vlan 10
[Switch-GigabitEthernet1/0/2] quit
Step 4 Configure sub-interfaces for dot1q VLAN tag termination.

[RouterA-GigabitEthernet2/0/0.1] control-vid 1 dot1q-termination
[RouterA-GigabitEthernet2/0/0.1] dot1q termination vid 10
[RouterB-GigabitEthernet2/0/0.1] control-vid 1 dot1q-termination
[RouterB-GigabitEthernet2/0/0.1] dot1q termination vid 10
Step 5 Configure a BFD session.

[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd atob bind peer-ip default-ip interface gigabitethernet 2/0/0.1
[RouterA-bfd-session-atob] dot1q vid 10
[RouterB] bfd
[RouterB-bfd] quit
[RouterB] bfd atob bind peer-ip default-ip interface gigabitethernet 2/0/0.1
[RouterB-bfd-session-atob] discriminator local 2
[RouterB-bfd-session-atob] discriminator remote 1
[RouterB-bfd-session-atob] dot1q vid 10

[RouterB-bfd-session-atob] commit
[RouterB-bfd-session-atob] quit
After the configuration, run the display bfd session all verbose command. You can view that
the BFD session is Up. Take the display on Router A as an example.
--------------------------------------------------------------------------------
------------------------------------------------------------------------------
BFD Bind Type : Interface(GigabitEthernet2/0/0.1)
Bind Interface : GigabitEthernet2/0/0.1
Active Multi : 3
------------------------------------------------------------------------------
Step 6 Configure VRRP backup group 1 to track the status of the BFD session.
[RouterA-GigabitEthernet2/0/0.1] dot1q vrrp vid 10
[RouterA-GigabitEthernet2/0/0.1] vrrp vrid 1 virtual 100.1.1.100
[RouterA-GigabitEthernet2/0/0.1] vrrp vrid 1 track bfd-session 1
[RouterA-GigabitEthernet2/0/0.1] arp broadcast enable
[RouterB-GigabitEthernet2/0/0.1] dot1q vrrp vid 10
[RouterB-GigabitEthernet2/0/0.1] vrrp vrid 1 virtual 100.1.1.100
[RouterB-GigabitEthernet2/0/0.1] vrrp vrid 1 track bfd-session 2
[RouterB-GigabitEthernet2/0/0.1] arp broadcast enable

Run the display vrrp command. You can view that the status of the BFD session tracked by
VRRP backup group 1 is Up. Take the display on Router A as an example.
State : Master
Virtual IP : 100.1.1.100
PriorityRun : 160

TimerRun : 1
TimerConfig : 1
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Track BFD : 1 Priority reduced : 10
----End
Configuration Files
#
sysname RouterA
#
bfd
#
interface GigabitEthernet 1/0/0
undo shutdown
ip address 192.168.2.1 24
#
undo shutdown
#
undo shutdown
control-vid 1 dot1q-termination
dot1q termination vid 10
dot1q vrrp vid 10
ip address 100.1.1.1 24
vrrp vrid 1 virtual 100.1.1.100
vrrp vrid 1 track bfd-session 1
#
bfd atob bind peer-ip default-ip interface gigabitethernet 2/0/0.1
dot1q vid 10
commit
#
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 RouterB
#
bfd
#
undo shutdown
ip address 192.168.1.1 24
#
undo shutdown
#
undo shutdown
control-vid 1 dot1q-termination

dot1q termination vid 10

dot1q vrrp vid 10
ip address 100.1.1.2 24
#
dot1q vid 10
commit
#
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 RouterC
#
bfd
#
undo shutdown
ip address 192.168.2.2 24
#
undo shutdown
ip address 192.168.1.2 24
#
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 the switch

#
sysname Switch
#
vlan batch 10
#
undo shutdown
#
undo shutdown
#
undo shutdown
#
return
5.16.14 Example for Configuring Sub-interfaces for QinQ VLAN

Tag Termination to Support BFD
On a typical network, sub-interfaces for QinQ VLAN tag termination are configured to support
BFD. In this manner, user packets with double tags can be reliably and stably sent over the
network.

On the network shown in Figure 5-17, users of VLAN 10 access an ISP network through a
default gateway. GE 2/0/0.1 is a sub-interface for QinQ VLAN tag termination on Router A,
and GE 2/0/0.1 is a sub-interface for QinQ VLAN tag termination on Router B.
The networking requirements are as follows:
l A BFD session is configured on Router A and Router B to detect the link between
l VRRP backup group 1 is configured on Router A and Router B. Router A functions as a
master device and Router B functions as a backup device.
l VRRP backup group 1 on Router A and Router B is configured to track the status of the
BFD session.
Figure 5-17 Networking diagram of configuring sub-interfaces for QinQ VLAN tag termination
to support BFD
MPLS/IP
backbone
GE1/0/0 GE2/0/0
192.168.2.2/24 192.168.1.2/24
RouterC
GE1/0/0 GE1/0/0
192.168.2.1/24 192.168.1.1/24
RouterA RouterB
GE2/0/0.1 BFD session GE2/0/0.1

100.1.1.1/24 100.1.1.2/24
GE1/0/1 GE1/0/2
GE1/0/0 Switch1
GE1/0/0
Switch2
GE2/0/0
VLAN10
Host 100.1.1.3/24

1. Configure interface modes on Router A and Router B as user termination.
3. Configure the Layer 2 forwarding function on Switch 2.
4. Configure QinQ on Switch 1.
6. Configure a BFD session on Router A and Router B to detect the link between Router A
and Router B.
7. Configure VRRP backup group 1 on GE 2/0/0.1 of Router A and GE 2/0/0.1 of Router B.
Ensure that Router A functions as a master device and Router B functions as a backup
device.
Data Preparation
l Name of the BFD session
l ID and virtual IP address of the VRRP backup group
l Tag values of sub-interfaces for QinQ termination
Procedure
Step 2 Configure an IGP to ensure connectivity between devices.

Assign IP addresses to interfaces as shown in Figure 5-17.Configure an IGP on Router A,
Router B, and Router C. OSPF is adopted in this example.
[RouterA] ospf 1

[RouterB] ospf 1
[RouterC] ospf 1
[RouterC-ospf-1] quit
After the configuration, OSPF on Router A and Router B calculates the route between Router
A and Router B. Router A and Router B can ping each other.
------------------------------------------------------------------------------

192.168.2.0/24 Direct 0 0 D 192.168.2.1
192.168.1.0/24 OSPF 10 2 D 192.168.2.2
100.1.1.0/24 Direct 0 0 D 100.1.1.1
------------------------------------------------------------------------------


192.168.2.0/24 Direct 0 0 D 192.168.2.1
192.168.2.1/32 Direct 0 0 D 127.0.0.1
192.168.1.0/24 OSPF 10 2 D 192.168.2.2
100.1.1.0/24 Direct 0 0 D 100.1.1.1

0.00% packet loss
Step 3 Configure the Layer 2 forwarding function on Switch 2.

[HUAWEI] sysname Switch2
[Switch2] vlan 10
[Switch2-vlan10] port gigabitethernet 2/0/0
[Switch2-vlan10] quit
[Switch2] interface gigabitethernet 1/0/0
[Switch2-GigabitEthernet1/0/0] undo shutdown
[Switch2-GigabitEthernet1/0/0] port trunk allow-pass vlan 10
[Switch2-GigabitEthernet1/0/0] quit
Step 4 Configure QinQ to allow Switch 2 to send packets with double tags to Router A and Router B.
[Switch1] vlan 100
[Switch1-GigabitEthernet1/0/0] port vlan-stacking vlan 10 stack-vlan 100
Step 5 Configure sub-interfaces for QinQ VLAN tag termination.
[RouterA-GigabitEthernet2/0/0.1] qinq termination pe-vid 100 ce-vid 10

[RouterB-GigabitEthernet2/0/0.1] qinq termination pe-vid 100 ce-vid 10
Step 6 Configure a BFD session.
[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd atob bind peer-ip default-ip interface gigabitethernet 2/0/0.1
[RouterA-bfd-session-atob] qinq pe-vid 100 ce-vid 10
[RouterB] bfd
[RouterB-bfd] quit
[RouterB] bfd atob bind peer-ip default-ip interface gigabitethernet 2/0/0.1
[RouterB-bfd-session-atob] discriminator local 2
[RouterB-bfd-session-atob] discriminator remote 1
[RouterB-bfd-session-atob] qinq pe-vid 100 ce-vid 10
[RouterB-bfd-session-atob] commit
[RouterB-bfd-session-atob] quit
After the configuration, run the display bfd session all verbose command. You can view that
the BFD session is Up. Take the display on Router A as an example.
--------------------------------------------------------------------------------
------------------------------------------------------------------------------
BFD Bind Type : Interface(GigabitEthernet2/0/0.1)
Bind Interface : GigabitEthernet2/0/0.1
Active Multi : 3
------------------------------------------------------------------------------
Step 7 Configure VRRP backup group 1 to track the status of the BFD session.
[RouterA-GigabitEthernet2/0/0.1] vrrp vrid 1 virtual 100.1.1.100
[RouterA-GigabitEthernet2/0/0.1] vrrp vrid 1 track bfd-session 1

[RouterA-GigabitEthernet2/0/0.1] arp broadcast enable

[RouterB-GigabitEthernet2/0/0.1] vrrp vrid 1 virtual 100.1.1.100
[RouterB-GigabitEthernet2/0/0.1] vrrp vrid 1 track bfd-session 2
[RouterB-GigabitEthernet2/0/0.1] arp broadcast enable

Run the display vrrp command. You can view that the status of the BFD session tracked by
VRRP backup group 1 is Up. Take the display on Router A as an example.
State : Master
Virtual IP : 100.1.1.100
PriorityRun : 160
TimerRun : 1
TimerConfig : 1
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Track BFD : 1 Priority reduced : 10
----End
Configuration Files
#
sysname RouterA
#
bfd
#
undo shutdown
ip address 192.168.2.1 24
#
undo shutdown
#
undo shutdown
ip address 100.1.1.1 24
#
qinq pe-vid 100 ce-vid 10
commit
#

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 RouterB
#
bfd
#
undo shutdown
ip address 192.168.1.1 24
#
undo shutdown
#
undo shutdown
ip address 100.1.1.2 24
#
qinq pe-vid 100 ce-vid 10
commit
#
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 RouterC
#
bfd
#
undo shutdown
ip address 192.168.2.2 24
#
undo shutdown
ip address 192.168.1.2 24
#
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
#
return
l Configuration file of Switch 2

#
sysname Switch2
#
vlan batch 10
#
undo shutdown
#
undo shutdown
#
return
5.16.15 Example for Configuring Single-hop BFD6 for a Layer 3

Physical Link
This example describes how to configure single-hop BFD6 for a Layer 3 physical link to monitor
and rapidly detect faults in the IPv6 link between two directly-connected devices.
On the network shown in Figure 5-18, BFD in asynchronous mode is set to detect faults in the
direct link between Router A and Router C.
Figure 5-18 Networking diagram of single-hop BFD6 for a Layer 3 physical link
RouterA RouterB
GE1/0/0 GE1/0/0
2001::1/64 2001::2/64
1. Configure a BFD6 session on Router A to detect faults in the directly connected link from
Router A to Router B.
2. Configure a BFD6 session on Router B to detect faults in the directly connected link from
Router B to Router A.

Data Preparation
l Peer IPv6 address bound to a BFD6 session
l IP address of the local interface sending and receiving BFD control packets
l Local and remote discriminators for a BFD6 session
NOTE
Procedure
Step 1 Assign IPv6 addresses to the interfaces directly connected Router A and Router B.
# Assign an IPv6 address to the interface on Router A.
[RouterA] ipv6
[RouterA] interface GigabitEthernet 1/0/0
# Assign an IPv6 address to the interface on Router B.

[RouterB] ipv6
[RouterB] interface GigabitEthernet 1/0/0
[RouterB-GigabitEthernet1/0/0] ipv6 address 2001:2 64

NOTE
You can also configure single-hop BFD on IP-Trunk, Eth-Trunk, or VLANIF interfaces. The configuration
procedures are the same as those described in this example.
# Enable BFD on Router A, create a BFD session to detect faults in the link from Router A
toRouter B, and bind an outbound interface to the BFD session.
[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd atob bind peer-ipv6 2001::2 interface GigabitEthernet 1/0/0
# Enable BFD on Router B, create a BFD session to detect faults in the link from Router B
toRouter A, and bind an outbound interface to the BFD session.
[RouterB] bfd
[RouterB-bfd] quit
[RouterB] bfd atob bind peer-ipv6 2001::1 interface GigabitEthernet 1/0/0


Router B. You can view that a single-hop BFD session has been set up and its status is Up.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Bind Peer Ip Address : 2001::2
NextHop Ip Address : 2001::2
Actual Tx Interval (ms): - Actual Rx Interval (ms): -
Local Detect Multi : 3 Detect Interval (ms) : -
--------------------------------------------------------------------------------
----End
Configuration Files
#
sysname RouterA
#
ipv6
#
bfd
#
undo shutdown
ipv6 enable
#
bfd atob bind peer-ipv6 2001::2 interface GigabitEthernet1/0/0
commit
#
return

#
sysname RouterB
#
ipv6
#

bfd
#
undo shutdown
ipv6 enable
#
bfd btoa bind peer-ipv6 2001::1 interface GigabitEthernet1/0/0
commit
#
return
5.16.16 Example for Configuring Multi-hop BFD6

This example describes how to configure a BFD6 session over a multi-hop path to monitor and
rapidly detect faults in links along the path.
On the network shown in Figure 5-19, BFD in asynchronous mode is used to detect faults in a
multi-hop link between Router A and Router C.
Figure 5-19 Networking diagram of multi-hop BFD6

GE1/0/0 GE1/0/0 GE2/0/0 GE2/0/0
2001::1/64 2001::2/64 2002::1/64 2002::2/64
1. Configure a BFD6 session on Router A to detect faults in a multi-hop link from Router A
toRouter C.
2. Configure a BFD6 session on Router C to detect faults in a multi-hop link from Router C
toRouter A.
Data Preparation
l Peer IPv6 address bound to a BFD6 session

l IP address of the local interface sending and receiving BFD control packets
l Local and remote discriminators for a BFD6 session
NOTE

Procedure
Step 1 Run OSPFv3 on Router A, Router B, and Router C to ensure intercommunication between them.
The detailed configurations are not provided.
Step 2 Assign IPv6 addresses to the interfaces connecting Router A, Router B, and Router C.
# Assign an IPv6 address to the interface on Router A.

[RouterA]ipv6
# Assign an IPv6 address to the interface on Router B.

[RouterB]ipv6
[RouterBA-GigabitEthernet1/0/0] quit
# Assign an IPv6 address to the interface on Router C.

[RouterC] ipv6
# Create a BFD session on Router A to detect faults in the link from Router A to Router C. Do
not bind the BFD session to an outbound interface.
[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd atoc bind peer-ipv6 2002::2
# Create a BFD session on Router C to detect faults in the link from Router C to Router A. Do
not bind the BFD session to an outbound interface.
[RouterC] bfd
[RouterC-bfd] quit
[RouterC] bfd ctoa bind peer-ipv6 2001::1


Router C. You can view that a multi-hop BFD session has been set up and its status is Up.
--------------------------------------------------------------------------------
Session MIndex : 256 (Multi Hop) State :Up Name : atoc
--------------------------------------------------------------------------------
Bind Peer Ip Address : 2002::2
Bind Interface : --
Actual Tx Interval (ms): - Actual Rx Interval (ms): -
Local Detect Multi : 3 Detect Interval (ms) : -
--------------------------------------------------------------------------------
----End
Configuration Files
#
sysname RouterA
#
ipv6
#
bfd
#
ospfv3 1
router-id 1.1.1.1
#
undo shutdown
ipv6 enable
#
bfd atoc bind peer-ipv6 2002::2
commit
#
return

#
sysname RouterB
#

ipv6
#
bfd
#
ospfv3 1
router-id 1.1.1.1
#
undo shutdown
ipv6 enable
#
undo shutdown
ipv6 enable
#
return

#
sysname RouterC
#
ipv6
#
bfd
#
ospfv3 1
router-id 1.1.1.1
#
undo shutdown
ipv6 enable
#
bfd ctoa bind peer-ipv6 2001::1
commit
#
return

Configuration Guide - Reliability 6 GR Configuration
6 GR Configuration
About This Chapter
Through the GR configurations, you can improve HA of a system.
6.1 GR Introduction
Defined as an extension of IP/MPLS by the IETF, GR ensures the uninterrupted forwarding
during the protocol restart, which limits the flapping of the control-plane protocols during the
AMB/SMB switchover.
6.2 Configuring the System-Level GR
System-level GR is a technology that combines redundancy backup, GR, and HSB together to
improve HA of devices.
6.3 Maintaining HA
This section describes how to maintain HA. The detailed operation include monitoring the
operations status of HA.
The following section provides an example for configuring GR. Familiarize yourself with the
configuration procedures against the networking diagram. The configuration example consists
of the networking requirements, configuration roadmap, configuration procedures, and
configuration files.

6.1 GR Introduction
Defined as an extension of IP/MPLS by the IETF, GR ensures the uninterrupted forwarding
during the protocol restart, which limits the flapping of the control-plane protocols during the
AMB/SMB switchover.
6.1.1 HA Overview
The technologies that implement HA include redundancy backup, HSB, and GR.
In practical network, the network may fail and the service may be interrupted because of
inevitable non-technical factors. To improve the system availability, it is feasible to improve the
fault-tolerance capability of the system, speed up recovery from faults, and reduce the impact
of faults on the service.
High availability (HA) indicates that a device has high reliability.
Generally, Mean Time to Repair (MTTR) and Mean Time Between Failures (MTBF) are used
to assess the reliability of a device.
l MTTR: indicates the average time that a component or a device takes to recover from a
failure.
In broader sense, MTTR refers to spare part management, customer service, and is an
important index to evaluate equipment maintenance.
The formula of MTTR is as follows:
MTTR = Fault detection time + Board replacement time + System initialization time + Link
recovery time + Route coverage time + Forwarding recovery time
The less the time is, the greater the MTTR is and the higher the device reliability is.
In the telecommunication industry, 99.999% availability means that service interruption caused
by device failures must be less than 5 minutes each year.
l MTBF: indicates the average time (usually in hours) when a component or a device works
without any failure.
AMB/SMB switchover is an important method to ensure the system availability when the system
fails.
Data may be lost during AMB/SMB switchover. Most lost data can be restored smoothly through
hot standby (HSB). The lost data that cannot be restored through HSB can be restored through
Graceful Restart (GR).
Redundancy Backup
Redundancy backup for the key components in the system is an important method to improve
the fault-tolerance capability of the system.
Redundancy backup is performed in the following modes:
l 1+1 backup: Two components must mirror each other. If the master component is Down,
the slave component takes over the previous component to ensure that the system service
is not interrupted.

l n+1 backup: If you need n similar components to provide services, another component is
necessary to act as the backup for all the n components. If one of the n components fails,
the backup component takes over the faulty component to ensure the smooth service.
At present, the router provides the following hardware backup functions:
l Fabric Board: 3+1 backup
l Main Control Unit (also named main board): 1+1 backup
l Service Process Unit (also named service board): 1+1 or n+1 backup
l Power Module: 1+1 backup
l Cool Fan: n+1 backup
The system performs the AMB/SMB switchover on the premise of 1+1 backup of the main
board, that is, two main boards.
HSB
HSB is a key technology providing hot backup.
The components and terms related to HSB are described as follows:
l Active Main Board (AMB): indicates the current active main board of the two main boards
on a router.
l Standby Main Board (SMB): indicates the backup main board of the two main boards on
a router.
l HA channel: indicates the communication channel between the AMB and SMB.
l Switchover: indicates the AMB is switched to the SMB. It is triggered by the commands
or by a serious fault. In the switchover, the original AMB is reset and becomes an SMB.
l Smooth: After the switchover is performed on a router, the SMB is switched to be the AMB,
but the data in different modules on the new AMB may be inconsistent. Thus, the data
needs to be synchronized on the new AMB.
The HSB can back up the static and dynamic configurations of the system from the AMB to the
SMB.
The AMB and SMB communicate as shown in Figure 6-1.

Figure 6-1 Basic mechanism of HSB
GR Capabiliby SMB
Negotiation to support AMB Routing / MPLS Protocol
Passive GR State Sync
RPA MPLS RPA MPLS
Socket /TCP Link
RIB RIB
IFnet Synchronize IFnet
Download FIB configuration FIB
FIB IPC and change
Heart Beat Check IPC
IPC Switch Fabric IPC
IO board FIB FIB FIB FIB
Interface
Incoming Packet Outcoming Packet
When the system is restarted, the AMB backs up its static configurations on the SMB and the
SMB re-execute the static configurations.
When the system runs normally, any data changes in the AMB, including static and dynamic
data changes, are backed up to the SMB. Note that the AMB can download the routing
information from the data plane to the interface board but the SMB cannot download the routing
information. In addition, the SMB cannot receive any information from the interface board.
After the switchover, the SMB switches itself to the AMB and runs smoothly. All data on the
AMB is backed up; therefore, the sessions with other routers are not affected and other routers
are not aware of the switchover. That is, the HSB switchover is "self-contained".
The requirements for the hardware and software to implement the HSB are as follows:
l Supporting two main boards that serve as the backup for each other
l Providing a physical communication channel between the AMB and the SMB
l Supporting AMB heart beat detection on hardware or software
The HSB performs the following functions:
l Supporting backup of static configuration data from the AMB to the SMB
l Supporting dynamic backup and update of protocol status data from the AMB to the SMB
l Supporting the protocol-level GR capability
l Supporting data smoothing between modules

GR
In IETF, protocols related to Internet Protocol/Multiprotocol Label Switching (IP/MPLS) such
as Open Shortest Path First (OSPF), Intermediate System-Intermediate System (IS-IS), Border
Gateway Protocol (BGP), Label Distribution Protocol (LDP), and Resource Reservation
Protocol (RSVP) are extended to ensure that the forwarding is not interrupted when the system
is restarted. This reduces the flapping of the protocols at the control plane when the system
performs the AMB/SMB switchover. This series of standards is called GR extension to each
protocol. Currently, GR has been widely applied to the AMB/SMB switchover and system
upgrade.
The system can perform GR on the condition that the forwarding plane is separated from control
plane. That is, the router has a main board and an Interface board, and the Interface board
forwards packets. When the system restarts the protocol or performs AMB/SMB switchover,
the interface board is not reset. The interface board continues forwarding packets; thus, packets
can be forwarded in the entire system without interruption. The prerequisite to uninterrupted
forwarding in the system is that the network topology and interface status do not change in the
GR period; otherwise, the system exits from the GR and the forwarding is interrupted.
The concepts related to the GR are as follows:
l Roles
– GR Restarter: indicates a router on which the routing protocol is enabled with the GR
capability. The router has dual main boards, and is capable of notifying the neighbor to
maintain the adjacency during AMB/SMB switchover.
– GR Helper: indicates the neighbor of the GR Restarter. The GR Helper should be able
to identify the GR signaling, maintain the adjacency with the GR Restarter during the
AMB/SMB switchover, and help the GR Restarter to restore the network topology.
NOTE
The GR Restarter and the GR Helper interact with each other. When the GR Helper is enabled with
the GR capability, the GR Restarter and the GR Helper can interchange.
l Session and timer
– GR session: indicates the session that has the GR capability. Through the session, the
GR Restarter and the GR Helper negotiate the GR capability.
– GR time: indicates the time of maintaining the undeleted routing information after the
GR Helper finds that the GR Restarter becomes Down. The GR time can be regarded
as the period between the start and end of the GR session.
NOTE
The mechanisms of implementing GR in each protocol are different. For the detailed value of the
GR time, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - IP Routing and
The administrator and the fault can trigger the restart and AMB/SMB switchover of the GR
Restarter.
The following describes the GR process during the AMB/SMB switchover.
NOTE
If the network topology or the interface status changes, the system exits from GR. In the following
description, it is assumed that the network topology and interface status do not change.
1. The GR Restarter and the GR Helper negotiate the GR capability and establish a session.

Figure 6-2 Setting up sessions between the GR Helper and the GR Restarter
RouterD GR Helper
RouterA GR Restarter
RouterB
RouterC
GR Helper GR Helper
Session with GR capability
Router A serves as the GR Restarter. Router B, Router C and Router D are GR Helpers
responding to Router A. A session with the GR capability is established between the GR
Restarter and each GR Helper.
2. The GR Restarter performs the AMB/SMB switchover.
Figure 6-3 AMB/SMB switchover of the GR Restarter
GR
RouterD
Helper
RouterA GR
Restarter
RouterB RouterC
GR GR
Helper Helper
Session with GR capability
The administrator restarts the GR
restarter,or the GR restarter itself fails
When the GR Helpers find that the GR Restarter fails, they maintain the adjacency with
the GR Restarter and retain the routing information related to the GR Restarter before the
GR time times out.
3. After the SMB is started, the GR Restarter sends signals to the neighbors.

Figure 6-4 GR Restarter sending signals to the neighbors after the AMB/SMB switchover
RouterD GR Helper
RouterB RouterC
GR Helper GR Helper
Signals sent to estabilish a GR Session
The SMB of the GR Restarter is restarted to sends signals to the GR Helpers, and re-
establish sessions.
4. The GR Restarter obtains topology information from neighbors.
Figure 6-5 GR Restarter obtaining topology information from neighbors
RouterD GR Helper
RouterB
RouterC
GR Helper GR Helper
GR restarter gets topology information
or routes from neighbors
After the GR Restarter obtains the topology information from its neighbors, it recalculates
the routing table and triggers the aging of the old routes.
Thus, the GR Restarter completes the AMB/SMB switchover during which packet
forwarding is not interrupted.

Comparison Between the GR and the HSB
Table 6-1 Comparison between the GR and the HSB
Name Advantage Drawback
GR l It is easy to implement and does not l Interoperability: Some of the GR

need great modifications to the specifications are still drafts and the
existing software. implementation varies with
l It does not need to back up the vendors.
protocol status information. l Concurrent collapse: If a GR router
l Few data needs to be backed up and its neighbor(s) collapse
from the AMB to the SMB. The concurrently, GR cannot work
data includes configuration normally.
modification, updated messages l Long convergence time: When a GR
and events, interface status change, router in the Down state cannot
and topology information and recover again, its neighbors assume
routing information from that the GR Restarter will restart, so
neighbors after restart. the neighbors do not delete the
l During the switchover, there is related routing and topology
little probability of service information before the Recovery
interruption. timer times out. Compared with the
common network in which the
l Normally, the network converges routers do not have the GR
rapidly. capability, this network takes a
longer period to converge.
l Dependence of the recovery process
on neighbor routers: Neighboring
routers must support the GR
capability, because GR is not "self-
contained".
HSB l The AMB/SMB switchover on the l More difficult to implement than

HSB router does not affect the GR: More information, including
service forwarding and routing the protocol status, the session, the
process. route, the policy, and the update,
l The routing information and needs to be backed up.
topology information are not lost l Usage of more communication
and the protocol session is not channel bandwidth: The HSB needs
interrupted during the switchover. to support the TCP backup between
l The switchover between the AMB the AMB and the SMB.
and SMB is self-contained. l Dependence on the hot backup of
l The neighbour routers do not need the BGP/LDP session on the TCP
to have the GR capability. connection. If you do not expect the
neighbors to be aware of the
l There is no problem of switchover, you must back up the
compatibility. continuously changing TCP link
l The switchover does not affect the status from the AMB to the SMB.
neighbors.
l The network convergence is faster
than the network with GR routers.

6.1.2 GR Features Supported in the NE80E/40E

The GR features include system-level GR. System-level GR is a technology that combines
redundancy backup, GR, and HSB to implement the uninterrupted forwarding during the AMB/
SMB switchover, which minimizes the impact on services and ensures HA for devices.
Currently, the NE80E/40E supports the following GR features:
l MPLS LDP (DU or DoD)

l OSPF (IPv4)
l IS-IS (IPv4/IPv6)
l BGP (IPv4/IPv6), VPNv4 BGP, and BGP with labelled routes
l RSVP
l PIM-SM and PIM-SSM
l OSPFv3
l RIP
l L3VPN
l Martini VLL, PWE3 VPLS, and Martini VPLS
The NE80E/40E integrates the advantages of the GR and the HSB to implement the HA as
follows:
l Provides the 1+1 backup through redundancy backup

l Backs up static configuration from the AMB to the SMB through HSB, and backs up the
status of the protocols that do not have the GR capability.
l Restores the session status of the protocol extended with the GR capability, with the help
of the neighbouring routers.
The HA feature that integrates dual main control boards, GR, and HSB is called system-level
GR. The function of the system-level GR is to decrease the impact of the AMB/SMB switchover
on the packet forwarding.
A router can perform the system-level GR on the following conditions:
l The router has dual main control boards.

l BGP, OSPF, IS-IS, and LDP support the GR function.
l The router supports HSB.
NOTE
When a router supports only GR rather than HSB, this router can be used as a GR Helper to support the
GR process of other routers.
6.2 Configuring the System-Level GR

System-level GR is a technology that combines redundancy backup, GR, and HSB together to
improve HA of devices.


Before configuring the system-level GR function, familiarize yourself with the applicable
The system-level GR function is used in the following situations:
l A system fault triggers the AMB/SMB switchover.
l When upgrading the software or maintaining the system, the administrator manually
triggers the AMB/SMB switchover.
To ensure that services are not affected during the switchover, configure information
synchronization between AMB and SMB. So far, there are two modes: automatic and manual.
Before configuring system level GR, you need to complete the following tasks:
l Configuring a protocol basic functions
l Configuring a protocol level GR capability
NOTE
For the detailed configurations of OSPF GR, IS-IS GR, and BGP GR, refer to the HUAWEI NetEngine80E/
40E Router Configuration Guide - IP Routing; for the detailed configurations of LDP GR, refer to the
Data Preparation
To configure the system-level GR, you need the following data.
No. Data
1 Default slot number of the SMB
6.2.2 (Optional) Configuring the Default Slot Number for the SMB
You can set the slot ID of the default SMB for the system restart.
Context
If both main boards are available, the system determines which one is to be the SMB when the
router restarts. Set the default slot number of the SMB using the command mentioned in this
section.
Do as follows on the GR Restarter:
Procedure
Step 1 Run:

system-view

Step 2 Run:
slave default slot-id
The default slot number for the SMB is configured.
----End
6.2.3 Enabling the Automatic Synchronization of the AMB/SMB

Configuration
You can enable the SMB to automatically synchronize configurations with the AMB when the
AMB is writing the configurations.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
slave auto-update config
The automatic synchronization of the AMB/SMB configuration is enabled.

If the save command is run on the AMB to save the configuration, the system automatically
updates the configuration on the SMB to synchronize the configurations on the AMB and the
SMB.
By default, the automatic synchronization of configuration data between AMB and SMB is
enabled.
To disable the automatic synchronization of configuration data between AMB and SMB, run
the undo slave auto-update config command.
----End
6.2.4 Enabling the Force AMB/SMB Switchover

The AMB and SMB can be switched to each other after the AMB/SMB switchover is enabled.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
slave switchover enable
The force AMB/SMB switchover is enabled.
After the configuration, you can run the slave switchover command to perform the force AMB/
SMB switchover manually.
By default, the force AMB/SMB switchover is enabled.
To disable the force AMB/SMB switchover, run the slave switchover disable command.
----End
6.2.5 (Optional) Restarting the SMB

After the software version on the SMB is upgraded, you can restart the SMB.
Context
During the on-line software upgrade, the SMB software is upgraded when the AMB works
normally. Then, the SMB must be restarted. After the SMB is ready, the AMB/SMB switchover
can be performed.
Procedure
Step 1 Run:
system-view
Step 2 Run:
slave restart
The SMB is restarted.
----End

By viewing the status of the AMB and SMB, you can check whether the configurations are
successful.
Prerequisite
The configurations of the system-level GR function are complete.
Procedure
Step 1 Run the display switchover state command to check the status of AMB and SMB.
----End

6.3 Maintaining HA
This section describes how to maintain HA. The detailed operation include monitoring the
operations status of HA.
6.3.1 Monitoring the Running of HA

By monitoring the operation status of HA, you can view information about HA during the
operation.
Context
In routine maintenance, you can run the following command in any view to display the running
of HA.
Procedure
Step 1 Run the display switchover state command in any view to display the backup status of the AMB
and the SMB according to the specified slot ID.
----End

The following section provides an example for configuring GR. Familiarize yourself with the
configuration procedures against the networking diagram. The configuration example consists
of the networking requirements, configuration roadmap, configuration procedures, and
Context
NOTE
6.4.1 Example for Configuring the System-Level GR

In this example, by being enabled with GR, a device can ensure the uninterrupted forwarding
during the AMB/SMB switchover after a fault occurs on the device.
NOTE
Figure 6-6 shows a networking diagram of configuring the system-level GR.
l In AS65009, OSPF is used as the IGP protocol; an EBGP connection is set up between
Router A and Router B; Router C is a non-BGP router in the AS.

l Router B has dual main control boards. The AMB and the SMB back up each other, and
support HSB. That is, the AMB and the SMB are configured with the HSB function.
l BGP GR is enabled on Router A; OSPF GR and BGP GR are enabled on Router B; and
OSPF GR is enabled on Router C.
When Router B performs the AMB/SMB switchover triggered by the system fault or the
administrator, it is required that the service is not interrupted, that is, the current network service
is not affected.
Figure 6-6 Networking diagram of configuring the system-level GR
GE1/0/0 POS2/0/0
10.1.4.1/24 10.1.1.1/24 GE2/0/0
POS1/0/0 10.1.3.1/24
10.1.2.1/24
RouterA POS1/0/0
POS2/0/0 RouterB 10.1.2.2/24 RouterC
AS 65008 10.1.1.2/24
AS 65009
1. Enable BGP GR on Router A; enable OSPF GR and BGP GR on Router B; enable OSPF
GR on Router C; configure GR parameters.
2. Configure the synchronization of the AMB/SMB configuration on Router B.
Data Preparation

l OSPF and BGP parameters
l GR parameters
Procedure
Step 1 Configure the IP address for each interface. The configuration details are not mentioned here.
Step 2 Configure basic OSPF and BGP functions. The configuration details are not mentioned here.
Step 3 Configure OSPF GR functions.

# Enable the link-local signaling and out-of-band synchronization capability of OSPF on Router
B. The configuration of Router C is the same as the configuration of Router B.
[RouterB] ospf 100
[RouterB-ospf-100] opaque-capability enable

# Enable the OSPF GR capability on Router B. The configuration of Router C is the same as the
configuration of Router B.
[RouterB-ospf-100] graceful-restart
[RouterB-ospf-100] graceful-restart period 600
Step 4 Configure BGP GR functions.

# Enable the BGP GR capability on Router B.
[RouterB] bgp 65009
[RouterB-bgp] graceful-restart
[RouterB-bgp] graceful-restart timer restart 600
[RouterB-bgp] graceful-restart timer wait-for-rib 600
# Enable the BGP GR capability on Router A.

[RouterA] bgp 65008
[RouterA-bgp] graceful-restart
[RouterA-bgp] graceful-restart timer restart 600
[RouterA-bgp] graceful-restart timer wait-for-rib 600
Step 5 Configure the parameters of the AMB/SMB switchover.

# Specify the default slot number of the SMB.
[RouterB] slave default 17
# Enable the force AMB/SMB switchover on Router B.

[RouterB] slave switchover enable
# Enable the automatic synchronization of the AMB/SMB configurations.

[RouterB] slave auto-update config
[RouterB] quit
<RouterB> save

# Perform the force AMB/SMB switchover on Router B.
[RouterB] slave switchover
Caution!!! Confirm switch slave to master[Y/N]?y
# Running the display fib command on Router C and Router A, you can view that the forwarding
entry related to Router B still exists. The forwarding is not interrupted and the service
transmission is not affected.
<RouterC> display fib
FIB Table:
Total number of Routes : 9
Destination/Mask Nexthop Flag TimeStamp Interface TunnelID
127.0.0.1/32 127.0.0.1 HU t[42] InLoop0 0x0
127.0.0.0/8 127.0.0.1 U t[42] InLoop0 0x0
10.1.2.2/32 127.0.0.1 HU t[561] InLoop0 0x0
10.1.2.0/24 10.1.2.2 U t[561] Pos1/0/0 0x0
10.1.2.1/32 10.1.2.1 HU t[561] Pos1/0/0 0x0
10.1.3.1/32 127.0.0.1 HU t[578] InLoop0 0x0
10.1.3.0/24 10.1.3.1 U t[578] GE1/0/0 0x0
3.3.3.3/32 127.0.0.1 HU t[724] InLoop0 0x0
10.1.4.0/24 10.1.2.1 DGU t[1422] Pos1/0/0 0x0
<RouterA> display fib
FIB Table:
Total number of Routes : 10
Destination/Mask Nexthop Flag TimeStamp Interface TunnelID

127.0.0.1/32 127.0.0.1 HU t[28] InLoop0 0x0

127.0.0.0/8 127.0.0.1 U t[28] InLoop0 0x0
10.1.4.1/32 127.0.0.1 HU t[28] InLoop0 0x0
10.1.4.0/24 10.1.4.1 U t[28] GE1/0/0 0x0
10.1.1.1/32 127.0.0.1 HU t[444] InLoop0 0x0
10.1.1.0/24 10.1.1.1 U t[444] Pos2/0/0 0x0
10.1.1.2/32 10.1.1.2 HU t[444] Pos2/0/0 0x0
10.1.2.0/24 10.1.1.2 DGU t[1402] Pos2/0/0 0x0
10.1.3.0/24 10.1.1.2 DGU t[1402] Pos2/0/0 0x0
1.1.1.1/32 127.0.0.1 HU t[2060] InLoop0 0x0
----End
Configuration Files
#
sysname RouterA
#
undo shutdown
ip address 10.1.4.1 255.255.255.0
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.1 255.255.255.0
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
bgp 65008
router-id 1.1.1.1
graceful-restart
graceful-restart timer restart 600
#
ipv4-family unicast
network 10.1.4.0 255.255.255.0
#
return

#
sysname RouterB
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.2 255.255.255.0
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.2.1 255.255.255.0
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
bgp 65009
router-id 2.2.2.2
graceful-restart
graceful-restart timer restart 600
#
ipv4-family unicast

import-route ospf 100
#
#
ospf 100
import-route bgp
opaque-capability enable
graceful-restart period 600
area 0.0.0.0
network 10.1.2.0 0.0.0.255
#
return

#
sysname RouterC
#
undo shutdown
ip address 10.1.3.1 255.255.255.0
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.2.2 255.255.255.0
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
ospf 100
opaque-capability enable
graceful-restart period 600
area 0.0.0.0
network 10.1.3.0 0.0.0.255
network 10.1.2.0 0.0.0.255
#
return

Configuration Guide - Reliability 7 NSR Configuration
7 NSR Configuration
About This Chapter
NSR improves the HA of the system.
7.1 NSR Overview

This section describes how to implement NSR and related technologies.
7.2 Configuring NSR
After NSR is configured, route processing and traffic forwarding are not interrupted during the
active/standby switchover of main control boards.

7.1 NSR Overview

This section describes how to implement NSR and related technologies.
7.1.1 Introduction to NSR

NSR is a type of reliability technology that keeps the neighbor relationships of a device during
the active/standby switchover of main control boards on the device.
Non-Stopping Forwarding (NSF) and Non-Stopping Routing (NSR) are two solutions to High
Availability (HA).
l NSF: ensures that forwarding services are not interrupted during the active/standby
switchover of main control boards by using the protocol-specific GR mechanism.
– When a fault occurs in the system, forwarding services are not interrupted during system
restart.
– After the device recovers, it can re-establish neighbor relationships with other devices,
and then rebuild the routing table based on the information obtained from its neighbors.
For details about the GR configuration, see the chapter "GR Configuration" in the HUAWEI
NetEngine80E/40E Router Configuration Guide - Reliability.
l NSR: ensures that route processing is not interrupted on the control plane and the
forwarding plane during the active/standby switchover of main control boards by using the
backup mechanism of a related protocol.
During the active/standby switchover of main control boards on a device, the route
processing is not interrupted because of the following factors:
– No neighbor or topology information is lost.
– No neighbor relationship goes Down.
The advantages of NSR are as follows:
– NSR on the local device does not depend on or affect the remote device. Therefore, the
local and remote devices can communicate properly.
– The route convergence speed of NSR is higher than that of NSF.

Table 7-1 Comparison between NSR and NSF

Feature Advantage Disadvantage
NSF l Less information needs to be l Interworking problem: Different

backed up from the active main vendors may use different methods
control board to the standby main to implement NSF due to immature
control board. Only the following standards.
information needs to be backed up: l Depending on neighbor status: A
– Changes of configuration device needs the help of its neighbor
information to complete GR. If all devices
– Interface status become faulty at the same time due
to a software defect, NSF cannot
– Information about neighbors, work properly.
protocol status, sending and
receiving of packets, routes, and l Low convergence speed: If an NSF-
topologies enabled device becomes faulty and
is no longer started, the remote
l During the active/standby device, however, mistakenly
switchover of main control boards, considers that the NSF device can be
the forwarding plane can still started after a while and does not
provide forwarding services. delete the routing information
– During the GR process of a learned from the NSF-enabled
protocol, topologies and routes device until the set recovery time
may change, causing expires. Therefore, routing
forwarding errors. The occasion information may be incorrect during
occurs with a very low this period of time.
probability.

Feature Advantage Disadvantage
NSR l When the control plane becomes l More bandwidths are required and
faulty, the forwarding plane can more system resources are
still provide forwarding services. consumed.
l During the active/standby
switchover of main control boards,
the route processing is not
interrupted because of the
following factors:
– No neighbor or topology
information is lost.
– No neighbor relationship goes
Down.
l The active/standby switchover of
main control boards is relevant to
only the local device.
– The active/standby switchover
of main control boards on the
local device does not depend on
or affect the remote device.
Therefore, the local device and
the remote device can
communicate properly.
– The route convergence speed of
NSR is higher than that of NSF.
NSR and GR
On the device that performs the active/standby switchover of main control boards, the system
supports two HA protection mechanisms: NSR and GR. NSR and GR are mutually exclusive.
That is, during the active/standby switchover of main control boards, the system can use either
NSR or GR for a specific protocol. When being deployed with NSR, a device can keep its
neighbor relationships so that the device can help its neighbor complete GR. This ensures the
HA of services on all nodes of a network to maximum extent.
7.1.2 NSR Features Supported by the NE80E/40E

This section lists the protocols that support NSR.
Currently, the protocols that support NSR are as follows:
l IS-IS
l OSPF
l OSPFv3
l BGP
l BGP4+
l PIM

l MSDP
l MVPN
l IPv4/IPv6 L3VPN
l RSVP
l LDP
l BFD
l VRRP
7.2 Configuring NSR

After NSR is configured, route processing and traffic forwarding are not interrupted during the

Before configuring system-level NSR, familiarize yourself with the applicable environment,
complete the pre-configuration tasks, and obtain the required data. This can help you complete
the configuration task correctly and quickly.
The system-level NSR function is used in the following situations:
l A system fault triggers the active/standby switchover of main control boards.

l When upgrading the software or maintaining the system, the administrator manually
triggers the active/standby switchover of main control boards.
NSR requires high system reliability. When the control plane of the system becomes faulty, the
system can switch entries on the faulty control plane to the backup control plane, which is
independent of the neighbor and does not interrupt route processing.
NSR has the following limitations:

l The switchover time is not strictly controlled, because the switchover time is not the key
performance index after the active/standby switchover of main control boards.
l Because the neighbor relationship is kept during the active/standby switchover of main
control boards on the local device, the remote device may consider that existing neighbor
relationships need to be re-established after the switchover. In this situation, the neighbors
of the device can sense the switchover. In addition, when neighbor relationships are
established, no Update packets are sent. Therefore, re-establishment of neighbor
relationships does not interrupt any service.
l NSR cannot ensure the high reliability of the system with only one main control board.
l If a fault occurs in the main process before the batch backup, the slave process, whose status
is unknown and is not switchable, cannot function as the main process.
l The system enabled with NSR does not support system-level GR.
None.

Data Preparation
None.
7.2.2 Enabling NSR

After NSR is enabled, route processing and service forwarding are not interrupted during the
Context
Do as follows on the device that requires high reliability:
Procedure
Step 1 Run:
system-view

Step 2 Run:
switchover mode nonstop-routing
NSR is enabled.
----End

By viewing routing information after the active/standby switchover of main control boards,
check whether the NSR configuration is successful.
Prerequisite
All configurations of NSR are complete.
Procedure
l Run the display ip routing-table [ verbose ] command to view the routing information
after the active/standby switchover of main control boards.
l Run the display fib verbose command to view the forwarding information after the active/
standby switchover of main control boards.
----End
Example
If the configurations succeed, you can obtain the following results by running the preceding
commands:
l The neighbor relationship on the standby main control board is Up not Init. In this case,
the neighbor information on the standby main control board is consistent with that on the
active main control board.
l Interface information, LSDB information, and routing information on the standby main
control board are consistent with those on the active main control board.

Configuration Guide - Reliability 8 Ethernet OAM Configuration
8 Ethernet OAM Configuration
About This Chapter
This chapter describes Ethernet OAM and its configurations, and how to implement link-level
Ethernet OAM detection and network-level Ethernet OAM detection to improve network
reliability. Ethernet OAM is applicable mainly to MANs.
8.1 Ethernet OAM Overview

Ethernet OAM is classified into the link-level Ethernet OAM and network-level Ethernet OAM.
8.2 Configuring Basic EFM OAM
By configuring basic EFM OAM functions, you can detect connectivity of the direct link between
devices.
8.3 Configuring EFM OAM Link Monitoring
By configuring EFM OAM detection for errored codes, errored frames, and errored frame
seconds, you can more effectively detect link layer faults.
8.4 Testing the Packet Loss Ratio on the Physical Link
By testing the packet loss ratio on a physical link, you can take effective measures to ensure
better performance of the link.
8.5 Associating EFM OAM with an Interface
After EFM OAM is associated with an interface, services may be greatly affected. For example,
all the Layer 2 and Layer 3 services may be blocked.
8.6 Configuring Basic Ethernet CFM
By configuring basic Ethernet CFM functions, you can implement end-to-end detection,
advertisement, verification, and location of connectivity faults.
8.7 Configuring Related Parameters of Ethernet CFM
By adjusting parameters of Ethernet CFM, you can detect connectivity of an Ethernet network
from end to end.
8.8 Fault Verification on the Ethernet
By sending detection packets and waiting for replies, you can test connectivity of the path
between devices.
8.9 Locating the Fault on the Ethernet

By sending test packets and waiting for a reply, you can test connectivity of the path between
devices and locate faults.
8.10 Associating Ethernet CFM with an Interface
The association between Ethernet CFM and an interface is used to detect faults of an active link
in the LACP static link aggregation group or in the manually-configured 1:1 active/standby link
aggregation group and then trigger the protection switchover.
8.11 Associating EFM OAM with Ethernet CFM
By configuring the association between EFM OAM and Ethernet CFM, you can implement the
bidirectional fault notification.
8.12 Associating Ethernet CFM with VPLS
By associating Ethernet CFM with the VPLS, you can implement end-to-end detection,
advertisement, verification, and location of connectivity faults in the VPLS scenario.
8.13 Associating Ethernet CFM with VLL (by Using Sub-interfaces for QinQ VLAN Tag
Termination)
In the scenario where PEs that send packets with double VLAN tags access a Virtual Leased
Line (VLL), you can configure sub-interfaces for QinQ VLAN tag termination on AC interfaces
of the PEs to bind L2VCs and then configure Ethernet CFM on the PEs.
8.14 Associating Ethernet CFM with VPLS (by Using Sub-interfaces for QinQ VLAN Tag
Termination)
In the scenario where PEs that send packets with double VLAN tags access a Virtual Private
LAN Service (VPLS) network, you can configure sub-interfaces for QinQ VLAN tag
termination on AC interfaces of the PEs to bind VSIs and then configure Ethernet CFM on the
PEs.
8.15 Associating Ethernet OAM with MPLS OAM or BFD
By associating Ethernet OAM with MPLS OAM or BFD, you can implement the fault
notification.
8.16 Configuring Ethernet CFM and 1+1 Protection of Multicast VLANs
Ethernet CFM can be used on working VLANs, detect connectivity faults of VLANs, and trigger
protection switchover, which can implement 1+1 multicast VLAN protection.
8.17 Maintaining Ethernet OAM
This section describes how to maintain Ethernet OAM. Detailed operations include deleting
CCM statistics, monitoring Ethernet OAM.

8.1 Ethernet OAM Overview

Ethernet OAM is classified into the link-level Ethernet OAM and network-level Ethernet OAM.
8.1.1 Introduction to Ethernet OAM

Ethernet OAM can effectively improve management and maintenance capabilities on Ethernet
networks, which ensures the stable network operation. Ethernet OAM is applicable mainly to
Ethernet networks.
Background
The Ethernet has developed as the major Local Area Network (LAN) technology because it
features easy implementation and low cost. Recently, along with the applications of Gigabit
Ethernet and the later 10-Gigabit Ethernet, Ethernet has been extended to the Metropolitan Area
Network (MAN) and Wide Area Network (WAN).
Compared with MANs and WANs, reliability and stability are not highly required for LANs.
Therefore, a mechanism for network Operations, Administration and Maintenance (OAM) is
always required for the Ethernet. The lack of the OAM mechanism prevents Ethernet from
effectively functioning as the Internet Service Provider (ISP) network. In this manner, Ethernet
OAM is becoming a trend.
Functions
Ethernet OAM has the following functions:
l Fault management
– Ethernet OAM can detect the network connectivity by sending detection messages
regularly or through manual triggering.
– Ethernet OAM can locate faults on the Ethernet by using means similar to the Packet
Internet Groper (ping) and traceroute tools on IP networks.
– Ethernet OAM can work with the Automatic Protection Switching (APS) to trigger
protection switching when detecting connectivity faults. This ensures service
interruption in no more than 50 ms to achieve carrier-class reliability.
l Performance management
Performance management is used to measure the packet loss ratio, delay, and jitter during
the transmission of packets. It also collects statistics on various kinds of traffic.
Performance management is implemented at the access point of users. By using the
performance management tools, the ISP can monitor the network status and locate faults
through the Network Management System (NMS). The ISP checks whether the forwarding
capacity of the network complies with the Service Level Agreement (SLA) signed with
users.
Ethernet OAM improves network management and maintenance capabilities on the Ethernet
and guarantees a steady network.
8.1.2 Ethernet OAM Supported by the NE80E/40E

Ethernet OAM includes EFM OAM, Ethernet CFM, fault association, and EFM OAM extension.

EFM OAM
Ethernet in the First Mile (EFM) defined in IEEE 802.3ah specifies the physical layer
specifications and Ethernet OAM of the Ethernet for user access networks. It is used to detect
the last mile of the Ethernet link. EFM OAM is OAM at the link level.
EFM OAM supported by the NE80E/40E provides the following functions:
l OAM discovery
When an interface on the NE80E/40E and the remote interface are both enabled with EFM
OAM, the interface and the remote interface send and respond with a slow protocol frame,
that is, an OAM Protocol Data Unit (OAMPDU) to determine whether the EFM OAM
configurations on both interfaces match. This is called OAM discovery. If the EFM OAM
configurations on both interfaces match, the two interfaces enter the EFM OAM Detect
state. In the Detect state, the two interfaces send OAMPDUs regularly to maintain
adjacencies. In normal situations, the interval for sending OAMPDUs is 1 second.
l Link monitoring
Link monitoring is a mechanism for an interface to notify the peer of the fault by sending
the event notification OAMPDU when the interface detects the errored frame event, errored
code event, or errored frame seconds event.
– The errored frame event means that the number of errored frames detected on an
interface reaches or exceeds the specified threshold within a set period.
– The errored code event means that the number of errored codes detected on an interface
reaches or exceeds the specified threshold within a set period.
– The errored frame seconds summary event means that the number of errored frame
seconds detected on an interface reaches or exceeds the specified threshold within a set
period.
An errored frame second is a one-second interval during which at least one errored frame
is detected.
l Fault notification
When a link event about a fault occurs on the local interface, the local interface notifies the
peer of the fault through OAMPDUs. The local interface then records the event in the log,
and reports the event to the NMS. This is called fault notification.
A link event can be one of the following:
– The system reboots.
– The Line Processing Unit (LPU) resets.
– A physical link fails.
– OAMPDUs time out.
– Errors transmitted by the OAM management module.
After receiving OAMPDUs, the peer records the event carried in OAMPDUs to the log and
reports it to the NMS.
l Remote loopback
When the local interface sends non-OAMPDUs to the peer, instead of forwarding non-
OAMPDUs based on their destination MAC addresses, the peer loops back non-
OAMPDUs to the local interface. This is called remote loopback. Remote loopback can be
used to locate faults and test link performance.

The working mode of EFM OAM is an attribute of the interface enabled with EFM OAM. The
working mode of EFM OAM on an interface is active or passive. OAM discovery and remote
loopback are initiated only by the interface in active mode.
Ethernet CFM
Connectivity Fault Management (CFM) defined in IEEE 802.1ag specifies the OAM functions
of connectivity check for Ethernet bearer networks. It includes the Continuity Check (CC),
Loopback (LB), and Linktrace (LT). Ethernet CFM applies to end-to-end scenarios on large-
scale networks. Ethernet CFM is OAM at the network level.
Currently, IEEE 802.1ag has two versions, that is, IEEE 802.1ag Draft 7 and IEEE Standard
802.1ag-2007. Table 8-1 shows the differences between these two versions.
Table 8-1 Differences between IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007
Feature IEEE 802.1ag Draft IEEE Standard Remarks
7 802.1ag-2007
Maintenance Domain Supported Supported Thefeatures

and
configurations
supported by
802.1ag Draft 7
and Standard
802.1ag-2007
are the same.
Default MD Not supported Supported -
Maintenance Supported Supported The features

Association and
configurations
supported by
802.1ag Draft 7
and Standard
802.1ag-2007
are the same.
Maintenance Supported Supported The features

association End Point and
configurations
supported by
802.1ag Draft 7
and Standard
802.1ag-2007
are the same.


7 802.1ag-2007
Remote Maintenance Supported Supported The features

association End Point and
configurations
supported by
802.1ag Draft 7
and Standard
802.1ag-2007
are the same.
Maintenance Supported Supported The MIP

association generation
Intermediate Point rules in both
802.1ag Draft 7
and Standard
802.1ag-2007
are classified
into the same
types, that is,
default,
explicit, and
none. The
difference
between the
MIP
generation
rules in
802.1ag Draft 7
and Standard
802.1ag-2007,
however, is as
follows:
l According
to 802.1ag
Draft 7, the
MIP is
created on
the basis of
the
interface.
l According
to Standard
802.1ag-20
07, the MIP
is created
on the basis
of the MD
or default
MD.


7 802.1ag-2007
Maintenance Point Supported Supported The features

and
configurations
supported by
802.1ag Draft 7
and Standard
802.1ag-2007
are the same.
l Basic concepts
– MD
A Maintenance Domain (MD) refers to the network or a part of the network where CFM
is performed. Devices in an MD are managed by a single ISP.
– Default MD
According to IEEE Standard 802.1ag-2007, each device can be configured with one
default MD. The default MD must be of a higher level than all MDs to which MEPs
configured on the local device belong. In addition, the default MD must be of the same
level as the high-level MD. The default MD transmits high-level CCMs and creates
MIPs to reply LTR packets.
– MA
A Maintenance Association (MA) is part of an MD. An MD can be divided into one or
multiple MAs. On the NE80E/40E, each MA is associated with a VLAN or a VSI.
Ethernet CFM maintains the connectivity of each MA separately.
– MEP
A Maintenance association End Point (MEP) is an edge point within an MA.
For the devices on the network enabled with Ethernet CFM, their MEPs are called local
MEPs. For the other devices in the same MA, their MEPs are called the Remote
Maintenance association End Points (RMEPs).
CAUTION
l One Trunk interface can be configured with only one MEP, regardless of how many
sub-interfaces the Trunk interface has.
l The system does not support hot swapping of boards.
– MIP
A Maintenance association Intermediate Point (MIP) is an intermediate point within an
MA.
According to IEEE 802.1ag Draft 7, MIPs reside on the interfaces of the device and are
automatically generated on the basis of the interface.
According to IEEE Standard 802.1ag-2007, MIPs are automatically generated on the
basis of the MD or default MD.

The MIP is automatically generated.

l Connectivity check
Ethernet CFM divides the network into one MD or multiple MDs. Each MD is further
divided into one MA or multiple MAs. Ethernet CFM can detect the connectivity between
MEPs within an MA by exchanging Continuity Check Messages (CCMs) periodically
between MEPs.
l Fault verification
– 802.1ag MAC ping
Similar to ping, 802.1ag MAC ping works by sending test packets and waiting for a
reply to test whether the destination device is reachable. 802.1ag MAC ping is initiated
by a MEP and destined for a MEP or MIP within an MA.
– GMAC ping
GMAC ping works similarly to 802.1ag MAC ping. A MEP, however, is not required
to initiate GMAC ping. The destination node does not need to be a MEP or a MIP.
GMAC ping can be implemented without configuring the MD, MA, or MEP on the
source device, the intermediate device, and the destination device.
– PBB-TE Ping
The Provider Backbone Bridging-Traffic Engineering (PBB-TE) ping operation is
performed to detect connectivity of the PBB-TE tunnel.
l Fault location
– 802.1ag MAC trace
Similar to traceroute or tracert, 802.1ag MAC trace works by sending test packets and
waiting for a reply to test the path between the local device and the destination device
and to locate faults. 802.1ag MAC trace is initiated by a MEP and destined for a MEP
or MIP within an MA.
– GMAC trace
GMAC trace works similarly to 802.1ag MAC trace. A MEP, however, is not required
to initiate GMAC trace. The destination node does not need to be a MEP or a MIP. That
is, GMAC trace can be implemented without configuring the MD, MA, or MEP on the
source device, the intermediate device, and the destination device. All the intermediate
devices can respond with a Linktrace Reply (LTR).
– PBB-TE MAC trace
PBB-TE MAC trace locates the connectivity fault on the PBB-TE tunnel. PBB-TE MAC
trace is initiated by one end of the PBB-TE tunnel and destined for the other end.
Fault Association
l Association between EFM OAM and an interface
When EFM OAM is associated with the current interface and detects a link fault through
the current interface, no other packets except EFM protocol packets can be forwarded on
the interface and Layer 2 and Layer 3 services are blocked. Therefore, the association of
EFM OAM and the current interface may greatly affect services. When the current interface
detects the link fault recovery through EFM OAM, all packets can be forwarded on the
interface and Layer 2 and Layer 3 services are unblocked.
Before configuring the association between EFM OAM and an interface, ensure that the
EFM OAM protocol on both ends of the link is in the detect state.
l Association between Ethernet CFM and an interface

When a MEP detects a connectivity fault between the MEP and a specified RMEP within
the same MA, the OAM management module performs the restart function, that is, shuts
down the interface on which the MEP resides for seven seconds and then starts it.
l Association between EFM OAM and the PBB-TE service instance (SI)
When the EFM OAM module detects a connectivity fault, the OAM management module
sends fault messages to the device at the other end through the PBB-TE tunnel to which
the SI that EFM OAM associates with is bound.
l Association between Ethernet CFM and the PBB-TE SI
When the Ethernet CFM module detects a connectivity fault, the OAM management
module sends fault messages to the device at the other end through the PBB-TE tunnel to
which the SI that Ethernet CFM associates with is bound.
l Association between Ethernet CFM and EFM OAM
When the Ethernet CFM module detects a fault in an MA, the OAM management module
sends fault messages to the peer device enabled with EFM OAM through the interface.
When the EFM OAM module detects a fault, the OAM management module sends fault
messages to the MA through the interface.
– Ethernet CFM sends fault messages to EFM OAM.
– EFM OAM sends fault messages to Ethernet CFM.
– Ethernet CFM and EFM OAM perform bidirectional transmission of fault messages.
l Association between Ethernet CFM and Ethernet CFM
sends fault messages to the MA at the other side through the binding relationship.
– Ethernet CFM at one side sends fault messages to Ethernet CFM at the other side.
– Ethernet CFMs at both sides perform bidirectional transmission of fault messages.
l Association between Ethernet CFM and Bidirectional Forwarding Detection (BFD)
sends fault messages to BFD at the other side through the binding relationship. When BFD
detects a fault, BFD sends fault messages to the MA through the binding relationship.
– Ethernet CFM sends fault messages to BFD.
– BFD sends fault messages to Ethernet CFM.
– Ethernet CFM and BFD perform bidirectional transmission of fault messages.
l Association between Ethernet CFM and Multiprotocol Label Switching (MPLS) OAM
sends fault messages to MPLS OAM through the binding relationship. When MPLS OAM
detects a fault, the OAM management module sends fault messages to the MA through the
binding relationship.
– Ethernet CFM sends fault messages to MPLS OAM.
– MPLS OAM sends fault messages to Ethernet CFM.
l Association between EFM OAM and BFD
messages to BFD at the other side through the interface. When BFD detects a fault, BFD
sends fault messages to EFM OAM through the interface.
– EFM OAM sends fault messages to BFD.
– BFD sends fault messages to EFM OAM.

– EFM OAM and BFD perform bidirectional transmission of fault messages.

l Association between EFM OAM and MPLS OAM
messages to MPLS OAM through the interface. When MPLS OAM detects a fault, the
OAM management module sends fault messages to EFM OAM through the interface.
– EFM OAM sends fault messages to MPLS OAM.
– MPLS OAM sends fault messages to EFM OAM.
EFM OAM Extension

Generally, a CE accesses an IP network by connecting the two PEs in master/slave mode. This
can ensure the reliability of IP services. To be specific, the CE usually accesses the two PEs in
a Router Redundancy Protocol (VRRP) backup group. The VRRP access, however, is originally
designed for PC terminals, and therefore cannot guarantee the carrier-class reliability and
performance.
Ethernet in the First Mile, Operation, Administration and Maintenance (EFM OAM), a link-
detecting technology operative either on Layer 3 networks, such as the IP and MPLS, or Layer
2 networks, such as Provider Backbone Transport-Traffic Engineering (PBT-TE), Transport
MPLS (T-MPLS), and Virtual Private LAN Service (VPLS), is currently supported on various
vendors' devices.
An EFM OAM extension Protocol Data Unit (PDU) carries the flag bit that indicates the link
state. The router that receives the PDU can control the status of the access link according to the
flag bit. By associating EFM OAM extension with interfaces or static routes, you can control
the traffic flow and achieve the primary/bypass link failover, which can ensure the carrier-class
reliability in network access.
l As shown in Figure 8-1.
Figure 8-1 Networking diagram of EFM OAM extension for VRRP
IP/MPLS
RouterA RouterB
interface IP VLANIF/VPLS interface IP
VRRP
UNI interface
link detection link detection

by EFM OAM by EFM OAM
extension extension
SoftX
Master link
Slave link

Router A functions as the master router and Router B functions as the backup router. The
SoftX uses two interface boards, namely, a master interface board and a slave interface
board, to respectively connect both routers. On the master and slave interface boards, the
interfaces that are respectively connected to Router A and Router B are configured with
the same IP address. Normally, the IP address of the interface on the master interface board
is valid.
The SoftX is dual homed to the gateways, that is, Router A and Router B. A VRRP backup
group is configured on VLANIF interfaces. The virtual IP address of the VRRP backup
group and the IP addresses of Router A and Router B are in the same network segment.
The downstream interfaces of Router A and Router B are common Ethernet interfaces.
The VRRP backup group is configured to track the traffic of the downstream interfaces in
reduce mode, and EFM OAM extension for VRRP is enabled.
In addition, the link between Router A and Router B can be configured in either of the
following modes:
– Configuring the link in VLANIF mode - To configure the link in VLANIF mode, you
need to perform the following steps:
– Configure VLANIF interfaces. Therefore, both routers are in one broadcast domain,
that is, a VLAN.
– Add the downstream interface (a Layer 2 interface) of each router into the VLAN.
– Configuring the link in VPLS mode - To configure the link in VPLS mode, you need
to perform the following steps:
– Set up a PW, and configure the downstream interfaces of both routers as the
attachment circuit (AC) interfaces to access the VPLS.
– Configure Layer 2 Virtual Ethernet (L2VE) interfaces between the routers, and bind
the L2VE interfaces and AC interfaces into the same virtual switching instance
(VSI).
– Configure the VRRP backup group on Layer 3 VE (L3VE) interfaces, and bind the
L3VE interfaces and the L2VE interfaces into the same VE group. In this manner,
you can configure Router A and Router B into the same broadcast domain.
All the preceding configurations ensure that the SoftX can detect the faults on the master
link and slave link based on EFM OAM extension and all devices can achieve EFM OAM
extension for VRRP.
Generally, the SoftX decides the link status based on relevant calculations, and then
advertises the link status information to the downstream interfaces of both routers by
sending EFM OAM extension PDUs.
As just mentioned, the VRRP backup group is configured to track the traffic of the
downstream interfaces in reduce mode, and EFM OAM extension for VRRP is enabled.
Therefore, after Router A receives the PDU indicating the link-down state, the VRRP
priority of Router A is reduced, and Router A becomes the backup router. Conversely,
after Router B receives the PDU indicating the link-up state, the VRRP priority of Router
B is increased, and Router B becomes the master router. This can ensure the consistency
between the VRRP master/slave status and the master/slave status of the downstream
interfaces.
In addition, if Router A is notified of a fault that is detected by EFM OAM extension,
Router A considers that the master link is faulty, and thus lowers its VRRP priority. The
SoftX then performs the master/slave failover, and sends the PDU indicating the link-up
state to Router B. The VRRP priority of Router B is thus increased, and Router B becomes
the master router. This can ensure the consistency between the master/slave status of the
SoftX and the master/slave status of both routers.

– Link Failover Between Downstream Interfaces: If a fault on the master link is detected
by EFM OAM extension, the SoftX performs the master/slave failover and sends the
gratuitous ARP packet and EFM OAM extension PDU to Router B.
1. If Router B receives the gratuitous ARP packet earlier than the EFM OAM
extension PDU, the procedure is as follows:
– Router B refreshes the MAC entries and ARP entries, creates the route destined
for the SoftX, and broadcasts the gratuitous ARP packet to Router A. Router
A also refreshes ARP entries and updates the status of its downstream interface.
In this manner, the downstream traffic from Router A to the SoftX is sent to
Router B, and Router B then forwards the traffic to the SoftX according to its
MAC table. At the moment, the downstream traffic is forwarded by Router B,
but the backup link between Router B and the SoftX is still Down. Therefore,
the downstream traffic is discarded.
– Then Router B receives the PDU indicating the link-up state. Consequently,
Router B advertises routes, increases the VRRP priority, and changes its link
to the master link. The downstream traffic is thus directly forwarded by Router
B.
– After Router A is informed of the fault detected by EFM OAM extension,
Router A deletes all routes, lowers its VRRP priority, and changes its link to
the backup link. Therefore, the upstream and downstream traffic through
Router A is blocked.
2. If Router B receives the PDU indicating the link-up state earlier than the gratuitous
ARP packet, the procedure is as follows:
– Router B advertises routes and unblocks its links. The VRRP priority of Router
B is increased, and the VRRP link between Router B and the SoftX is switched
into the master link. Then Router B forwards the upstream and downstream
traffic, and sends gratuitous ARP packets to Router A and the SoftX.
– After Router A is informed of the fault detected by EFM OAM extension,
Router A deletes all its routes, lowers its VRRP priority, and changes its VRRP
link to the backup link. At the same time, Router A blocks its downstream
interface. After the SoftX learns the gratuitous ARP packets sent by Router B,
the SoftX establishes a route to Router B. Then the downstream traffic is
forwarded by Router B.
When the faulty link between Router A and the SoftX recovers, the SoftX still
notifies Router A of keeping the current slave state. Therefore, no gratuitous ARP
packet is sent, and traffic is not switched from Router B to Router A.
– Link Failover Between Upstream Interfaces: When the upstream link of Router A fails,
the remote PE converges the route destined for Router A. Then both the downstream
traffic and upstream traffic are forwarded by Router B.
l Figure 8-2 shows EFM OAM extension for static routes.

Figure 8-2 Networking diagram of EFM OAM extension for static routes
IP/MPLS
RouterA RouterB
interface IP interface IP Traffic
Traffic
before the VRRP after the
failover failover
Link detection Link detection

UNI
performed by performed by
interface
EFM OAM EFM OAM
extension extension
SoftX
Master link
Slave link
Router A functions as the master router and Router B functions as the backup router. The
SoftX uses two interface boards, namely, a master interface board and a slave interface
board, to respectively connect both routers.
On the master and slave interface boards, the interfaces that are respectively connected to
Router A and Router B are configured with the same IP address. On Router A and Router
B, the interfaces that are connected to the SoftX are configured with the same IP address.
All the IP addresses are configured in the same network segment.
A service IP address is configured on the SoftX to transmit services, and either router is
configured with a static route destined for the service IP address. Router A and Router B,
both as PEs, are connected through Ethernet interfaces or Eth-Trunk interfaces. The
downstream interfaces of both routers are Ethernet interfaces.
EFM OAM extension is enabled on the SoftX, and the SoftX advertises the link-status
information to both routers; EFM OAM extension for static routes is enabled on both
routers. Router A advertises the static route destined for the service IP address on the SoftX,
and Router B does not advertise any route.
If EFM OAM extension detects a fault, the link failover between Router A and Router B
is performed. After route convergence is completed, the upstream and downstream traffic
flows through the new master link.
– Link Failover Between Downstream Interfaces:
When the master link fails, the SoftX performs the link failover, and sends the PDU
indicating the link-up state to Router B. After receiving the PDU, Router B changes
to the master router, and advertises the static route destined for the service IP address
on the SoftX. Router A, being informed of a fault detected by EFM OAM extension,
changes to the backup router, and deletes the route destined for the service IP address
on the SoftX.
When the faulty link between the SoftX and Router A recovers, the SoftX still notifies
Router A of keeping the current backup state. Therefore, the traffic is not switched from
Router B to Router A, and Router A does not advertise any route.

– Link Failover Between Upstream Interfaces: When the upstream link of Router A fails,
the remote PE converges the route destined for Router A. Then the downstream and
downstream traffic is forwarded by Router B.
8.2 Configuring Basic EFM OAM

By configuring basic EFM OAM functions, you can detect connectivity of the direct link between
devices.

Before configuring basic EFM OAM functions, familiarize yourself with the applicable
As shown in Figure 8-3, you can perform the configuration task to detect the connectivity
between two directly connected devices.
Figure 8-3 Diagram of configuring EFM OAM

EFM OAM
Interface 1 Interface 2
(Active) (Passive)
None.
Data Preparation
To configure EFM OAM, you need the following data.
No. Data
1 (Optional) Maximum size of an EFM OAMPDU
8.2.2 Enabling EFM OAM Globally

You must enable EFM OAM globally before configuring EFM OAM functions.
Context
Do as follows on the devices at both ends of the link:

Procedure
Step 1 Run:
system-view
Step 2 Run:
efm enable
EFM OAM is enabled globally.
By default, EFM OAM is disabled globally.
----End
8.2.3 Configuring the Working Mode of EFM OAM on an Interface

EFM OAM working mode is an attribute of an EFM OAM-enabled interface, and consists of
the active mode and the passive mode.
Context
NOTE
The working mode of EFM OAM on the interface can be configured only after EFM OAM is enabled
globally and before EFM OAM is enabled on the interface. The working mode of EFM OAM on the
interface cannot be modified after EFM OAM is configured on the interface.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The interface view of an interface at one end of the link is displayed.
Step 3 Run:
efm mode { active | passive }
The working mode of EFM OAM on the interface is configured.
By default, EFM OAM on an interface works in active mode.
At least one interface at both ends of the link must be configured to work in active mode. The
interface in active mode initiates OAM discovery after EFM OAM is enabled on the interface.
Instead of initiating OAM discovery, the interface in passive mode waits for an OAMPDU sent
from the interface in active mode. If both interfaces are configured to work in active mode, you
can implement link detection. If both interfaces are configured to work in passive mode, OAM
discovery fails.
----End

8.2.4 (Optional) Setting the Maximum Size of an EFM OAMPDU

You can configure the largest size of EFM OAMPDUs. On the current interface, the EFM
OAMPDUs whose sizes exceed the set size are regarded as illegal and thus discarded.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
efm packet max-size size
The maximum size of an EFM OAMPDU is set.

By default, the maximum size of an EFM OAMPDU on an interface is 128 bytes.
If the maximum size of an EFM OAMPDU on both interfaces of the link is configured
differently, the two interfaces negotiate and determine the value during the OAM discovery
process. The smaller maximum size of an EFM OAMPDU set on the local interface and the peer
is selected.
----End
8.2.5 (Optional) Setting the Timeout Period for Waiting for OAM
PDUs
To change the time required for link connectivity detection, you can set the timeout period for
waiting for OAM PDUs.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the interface on one end of a link is displayed.

Step 3 Run:
efm timeout timeout-value
The timeout period for waiting for OAM PDUs is set.

By default, the timeout period for waiting for OAM PDUs is 5000 ms.
Interfaces on both ends of a link must be configured with the same timeout period for waiting
for OAM PDUs. Otherwise, EFM session negotiation may fail, or the EFM session may flap.
NOTE
The timeout period for waiting for OAM PDUs can be set on an interface only when EFM OAM is globally
enabled and EFM OAM is not enabled on the interface.
----End
8.2.6 Enabling EFM OAM on an Interface

You can perform point-to-point EFM link detection only after enabling EFM OAM on interfaces
on both ends of a link.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
efm enable
EFM OAM is enabled on the interface.

By default, EFM OAM on an interface is disabled.
----End

By viewing EFM OAM configurations, you can check whether the configurations are successful.
Prerequisite
The configurations of the EFM OAM function are complete.
Procedure
l Run the display efm { all | interface interface-type interface-number } command to check
information about EFM OAM on an interface.
l Run the display efm session { all | interface interface-type interface-number } command
to check the status of the EFM OAM protocol on an interface.
----End

Example
Run the display efm command. You can view all the EFM OAM configurations on the local
interface and part of the EFM OAM configurations on the remote interface. For example:
<HUAWEI> display efm interface gigabitethernet2/0/1
Item Value
----------------------------------------------------
Interface: GigabitEthernet2/0/1
EFM Enable Flag: enable
Mode: active
OAMPDU MaxSize: 128
OAMPDU Timeout: 3000
ErrCodeNotification: disable
ErrCodePeriod: 1
ErrCodeThreshold: 1
ErrFrameNotification: disable
ErrFramePeriod: 1
ErrFrameThreshold: 1
ErrFrameSecondNotification: disable
ErrFrameSecondPeriod: 60
ErrFrameSecondThreshold: 1
Hold Up Time: 0
ThresholdEvtTriggerErrDown: disable
TriggerIfDown: disable
TriggerMacRenew: disable
Remote MAC: 00e0-fc7f-724f
Remote EFM Enable Flag: enable
Remote Mode: passive
Remote MaxSize: 128
Remote State: --
Run the display efm session command. If the EFM OAM protocol on the interface is in the
Detect state, it means that the configuration succeeds. The two interfaces succeed in negotiation
and enter the Detect state.
<HUAWEI> display efm session interface gigabitethernet2/0/1
Interface EFM State Loopback Timeout
--------------------------------------------------------------------
GigabitEthernet2/0/1 detect --
8.3 Configuring EFM OAM Link Monitoring

By configuring EFM OAM detection for errored codes, errored frames, and errored frame
seconds, you can more effectively detect link layer faults.

Before configuring the EFM OAM link monitoring function, familiarize yourself with the
Link monitoring can be used to detect and locate faults at the link layer in different scenarios.
It uses the event notification OAMPDU. When a link fails, the local link notifies the remote
OAM entity of the fault after detecting a fault through events.
Before configuring EFM OAM link monitoring, complete the following tasks:

l Configuring EFM OAM
Data Preparation
To configure EFM OAM link monitoring, you need the following data.
No. Data
1 (Optional) Period and threshold for detecting errored frames of EFM OAM
2 (Optional) Period and threshold for detecting errored codes of EFM OAM
3 (Optional) Period and threshold for detecting errored frame seconds of EFM OAM
8.3.2 (Optional) Detecting Errored Frames of EFM OAM

When an interface is enabled to detect errored frames, the NE80E/40E generates an errored
frame event and notifies the peer, if the number of errored frames reaches or exceeds the
threshold within a set period.
Context
Do as follows on the devices at one end or both ends of the link:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
efm error-frame period period
The period for detecting errored frames on the interface is set.
By default, the period for detecting errored frames on an interface is 1 second.
Step 4 Run:
efm error-frame threshold threshold
The threshold for detecting errored frames on the interface is set.
By default, the threshold for detecting errored frames on an interface is 1.
Step 5 Run:
efm error-frame notification enable
The interface is enabled to detect errored frames.

By default, an interface cannot detect errored frames.
----End
8.3.3 (Optional) Detecting Errored Codes of EFM OAM

When an interface is enabled to detect errored codes, the NE80E/40E generates an errored code
event and notifies the peer, if the number of errored codes reaches or exceeds the threshold within
a set period.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
efm error-code period period
The period for detecting errored codes on the interface is set.

By default, the period for detecting errored codes on an interface is 1 second.
Step 4 Run:
efm error-code threshold threshold
The threshold for detecting errored codes on the interface is set.

By default, the threshold for detecting errored codes on an interface is 1.
Step 5 Run:
efm error-code notification enable
The interface is enabled to detect errored codes.

By default, an interface cannot detect errored codes.
----End
8.3.4 (Optional) Detecting Errored Frame Seconds of EFM OAM

When an interface is enabled to detect errored frame seconds, the NE80E/40E generates an
errored frame seconds summary event and notifies the peer, if the number of errored frame
seconds reaches or exceeds the threshold within a set period.
Context
An errored frame second is a one-second interval during which at least one errored frame is
detected. It specifies the seconds when errored frames are deteced.

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
efm error-frame-second period period
The period for detecting errored frame seconds on the interface is set.
By default, the period for detecting errored frame seconds on an interface is 60 seconds.
Step 4 Run:
efm error-frame-second threshold threshold
The threshold for detecting errored frame seconds on the interface is set.
By default, the threshold for detecting errored frame seconds on an interface is 1.
Step 5 Run:
efm error-frame-second notification enable
The interface is enabled to detect errored frame seconds.

By default, an interface cannot detect errored frame seconds.
----End

By viewing EFM OAM configurations, you can check whether the configurations are successful.
Prerequisite
The configurations of the EFM OAM link monitoring function are complete.
Procedure
l Run the display efm { all | interface interface-type interface-number } command to check
information about EFM OAM on an interface.
to check the status of the EFM OAM protocol on an interface.
----End
Example
Run the display efm command. You can view information about link monitoring on the
interface. For example:

<HUAWEI> display efm interface gigabitethernet1/0/0

Item Value
----------------------------------------------------------
Mode: active
OAMPDU MaxSize: 128
ErrCodeNotification: enable
ErrCodePeriod: 1
ErrCodeThreshold: 1
ErrFrameNotification: enable
ErrFramePeriod: 1
ErrFrameSecondNotification: enable
Hold Up Time: 0
ThresholdEvtTriggerErrDown: enable
RemoteMAC 00e0-fc7f-7258
Remote EFM Enable Flag enable
Remote Mode passive
Remote MaxSize 128
Remote State: --
8.4 Testing the Packet Loss Ratio on the Physical Link

By testing the packet loss ratio on a physical link, you can take effective measures to ensure
better performance of the link.

Before testing the packet loss ratio on a physical link, 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.
CAUTION
Forwarding of service data is affected after EFM OAM remote loopback is enabled. Enable EFM
OAM remote loopback on the link that need not forward service data.
You can perform the configuration task to detect the packet loss ratio on a link.
As shown in Figure 8-4, enable EFM OAM on Router A and RouterB and enable remote
loopback on GE 1/0/1 on Router A. Send test packets from Router A to RouterB. You can get
the packet loss ratio on the link by observing the receiving of test packets on Router A.

Figure 8-4 Diagram of testing the packet loss ratio on the link
Test packets
EFM OAM
RouterA RouterB
GE1/0/1 GE2/0/1
(Active) (Passive)
Test packets data flow
Before testing the packet loss ratio on the link, complete the following tasks:
Data Preparation
To test the packet loss ratio on the link, you need the following data.
No. Data
1 Timeout period for remote loopback
2 Destination MAC address, VLAN ID, outbound interface, size, number, and sending
rate of test packets
8.4.2 Enabling EFM OAM Remote Loopback

You can configure the EFM OAM remote loopback function to locate faults on the remote end
and assess the link quality.
Context
EFM OAM remote loopback is a method of monitoring link performance. Its working process
is as follows:
1. An OAM entity working in active mode initiates a remote loopback request to the remote
OAM entity.
2. The remote loopback function is disabled manually or automatically.
Procedure
Step 1 Enable a device that initiates a request with the remote loopback function.
1. Run:
system-view

2. Run:

3. Run:
efm loopback start [ timeout timeout ]
The remote EFM OAM loopback function is enabled on the interface.

By default, the timeout period for remote loopback is 20 minutes. After the timeout period,
remote loopback is automatically disabled. You can set the timeout period to 0 for a link
to remain in the remote loopback state.
The following requirements must be met to implement remote loopback:
l The EFM OAM protocols on the local interface and the peer are in the Detect state.
l EFM OAM on the local interface works in active mode.
You can use the display efm session command to check whether the EFM OAM protocols
running on the local interface and the peer are in the Detect state.
4. Run:
efm loopback action discard
The interface is configured to discard the packets looped back.

By default, the interface discards the packets looped back.
----End
8.4.3 Sending Test Packets

The sent test packets are a type of Ethernet packets that are constructed for testing the packet
loss ratio on a link. This function can be used with the EFM OAM remote loopback function to
test the packet loss ratio on the link.
Context
Do as follows on the device with an active interface on the link:
Procedure
Step 1 Run:
system-view
Step 2 Run:
test-packet start [ mac mac-address ] [ vlan vlan-id ] { interface interface-type
interface-number | service-instance instance-name } [ -c count | -p speed | -s
size ] *
Test packets are sent.
By default, the size of a test packet is 64 bytes; the transmitting rate is 1 Mbit/s; the number of
test packets sent is 5.
The outbound interface for the test packets is the interface that connects the link to be tested.
----End

Follow-up Procedure
The parameter in this command cannot be modified when test packets are being sent.
Press Ctrl+C to stop sending test packets.
8.4.4 Checking the Statistics on Returned Test Packets

By viewing statistics of returned test packets, you can calculate the packet loss ratio.
Context
Procedure
Step 1 Run:
display test-packet result
Statistics of the returned test packets are displayed.

The displayed information includes:
l Number of sent test packets
l Number of received test packets
l Number of discarded test packets
l Total number of bytes of sent test packets
l Total number of bytes of received test packet
l Total number of bytes of discarded test packet
l Time to start the sending of test packet
l Time to end the sending of test packet
You can obtain the packet loss ratio on the link based on the preceding data.
----End
8.4.5 (Optional) Manually Disabling EFM OAM Remote Loopback

The EFM OAM remote loopback function can automatically time out or be disabled manually.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:


Step 3 Run:
efm loopback stop
Remote loopback is disabled on the interface.

If EFM OAM remote loopback is left enabled, the link fails to forward service data for a long
time. To prevent this, EFM OAM remote loopback on the NE80E/40E can be automatically
disabled after a timeout period. By default, the timeout period for remote loopback is 20 minutes.
After 20 minutes, remote loopback stops. If you need to disable remote loopback manually,
perform the preceding operation procedures.
----End

By viewing the status of the EFM OAM remote loopback function, you can check whether the
Prerequisite
The configurations of the Packet Loss Ratio on the Physical Link function are complete.
Procedure
Step 1 Run the display efm session { all | interface interface-type interface-number } command to
check the status of the EFM OAM protocol on an interface.
----End
Example
Run the display efm session command on the device with an active interface on the link. If the
EFM OAM protocol on the active interface is in the loopback (control) state, which indicates
that the active interface initiates remote loopback, it means that the configuration succeeds.
<RouterA> display efm session interface gigabitethernet 1/0/1
----------------------------------------------------------------------
GigabitEthernet1/0/1 Loopback(control) 20
Run the display efm session command on the device with a passive interface on the link. If the
EFM OAM protocol on the passive interface is in the loopback (be controlled) state, which
indicates that the passive interface responds to remote loopback, it means that the configuration
succeeds.
<RouterB> display efm session interface gigabitethernet 2/0/1
----------------------------------------------------------------------
GigabitEthernet2/0/8 Loopback(be controlled) --
Run the display efm session command on any of the devices on the link after remote loopback
is automatically or manually disabled, you can view that the EFM OAM protocol status on the
interface is no longer loopback (control) or loopback (be controlled).
<RouterA> display efm session interface gigabitethernet 1/0/1
----------------------------------------------------------------------

8.5 Associating EFM OAM with an Interface

After EFM OAM is associated with an interface, services may be greatly affected. For example,
all the Layer 2 and Layer 3 services may be blocked.

Before configuring the association between EFM OAM and an interface, 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.
As shown in Figure 8-5, EFM OAM is enabled on Router A and Router B. EFM OAM is
associated with GE 1/0/1 on Router A. When the EFM OAM module on Router A detects a
connectivity fault between Router A and Router B, no other packets except EFM protocol packets
can be forwarded on the interface GE 1/0/1 and Layer 2 and Layer 3 services are blocked.
Therefore, the association of EFM OAM and the current interface may greatly affect services.
When the current interface detects the link fault recovery through EFM OAM, all packets can
be forwarded on the interface and Layer 2 and Layer 3 services are unblocked.
Figure 8-5 Diagram of associating EFM OAM with an interface

EFM OAM
GE1/0/1 GE2/0/1
RouterA RouterB
The interface associated with EFM OAM
Before associating EFM OAM with an interface, complete the following tasks:
Data Preparation
To associate EFM OAM with an interface, you need the following data.
No. Data
1 Type and number of an interface
2 (Optional) Faulty-state hold timer

8.5.2 Associating EFM OAM with an Interface

By associating EFM OAM with a physical interface, you can use the OAM management module
to notify the bound interface management module of fault information after EFM OAM detects
a fault.
Context
After EFM OAM is enabled on an interface, the status of this interface changes when the interface
receives an OAM PDU control request packet with the Link Fault Status flag.
Procedure
l Associate an error event with an interface and set the interface to the blocking state when
the error event occurs.
Setting the interface to the blocking state is applicable to a scenario where traffic can be
switched back automatically after the faulty link recovers. After the associated interface is
blocked, all traffic is interrupted except EFM protocol packets.
1. Run:
system-view

2. Run:
The view of an interface at one end of the link is displayed.

3. Run:
efm trigger if-down
EFM OAM is associated with the interface.

By default, EFM OAM is not associated with an interface.
The efm trigger if-down command is valid in the interface view only after EFM OAM
is enabled on the interface with the efm enable command.
When EFM OAM is associated with the current interface and detects a link fault on
the current interface, no other packets except EFM protocol packets can be forwarded
on the interface and Layer 2 and Layer 3 services are blocked. Therefore, the
association between EFM OAM and an interface may greatly affect services. When
EFM OAM on an interface detects link fault recovery, all packets can be forwarded
on the interface and Layer 2 and Layer 3 services are unblocked.
Before configuring the association between EFM OAM and an interface, ensure that
the EFM OAM protocol on both ends of the link is in the detect state.
If Layer 2 and Layer 3 services are blocked due to a misoperation, you can run the
undo efm trigger if-down command in the interface view to restore services.
----End

By viewing the TriggerIfDown field, you can check whether the configurations are successful.

Prerequisite
The configurations of Associating EFM OAM with an Interface function are complete.
Procedure
Step 1 Run the display efm { all | interface interface-type interface-number } command to check the
EFM OAM configuration information on an interface.
----End
Example
Run the display efm command. If the item "TriggerIfDown" is displayed as "enable", it means
that the configuration succeeds.
<HUAWEI> display efm interface gigabitethernet 1/0/1
Item Value
----------------------------------------------------
Mode: active
OAMPDU MaxSize: 128

ErrCodePeriod: 1
ErrCodeThreshold: 1
ErrFramePeriod: 1
Hold Up Time: 0
ThresholdEvtTriggerErrDown: enable
TriggerIfDown: enable
Remote MAC: 0018-8200-0001
Remote MaxSize: 128
Remote State: --
8.6 Configuring Basic Ethernet CFM

By configuring basic Ethernet CFM functions, you can implement end-to-end detection,
advertisement, verification, and location of connectivity faults.

Before configuring basic Ethernet CFM functions, familiarize yourself with the applicable
CFM is mainly used to monitor the connectivity of end-to-end links or direct links.

As shown in Figure 8-6, CFM can be deployed on the Layer 2 network to monitor the link
connectivity between the CE and PE1, between PE1 and PE2, or between the CE and PE2.
Figure 8-6 Schematic diagram of the CFM function
CE PE1 P PE2 PE3
IP Core
CFM CFM
CFM
MEP
MIP
You need to ensure that the following conditions be met before implementing automatic end-
to-end connectivity detection on the Ethernet:
l MDs are classified based on the ISP that manages the devices. All the devices that are
managed by a single ISP and enabled with CFM can be configured in an MD.
One default MD can be configured on each device, that it transmits high-level CCMs and
generates MIPs to reply LTR packets.
l MAs are classified based on different SIs. An MA is associated with a VLAN. A VLAN
generally maps to an SI. When the MA is classified, fault detection in connectivity can be
carried out on the network where an SI is transmitted.
l You need to determine the interfaces on which devices are located at the edge of the MA,
that is, to determine that MEPs must be configured on the interfaces on which devices.
When implementing automatic connectivity detection on directly connected links, you also need
to ensure that:
l The devices at both ends must be configured in the same MA within an MD.
l An MA can be either associated with a VLAN or not.
l MEPs must be configured on the interfaces at both ends of the directly connected link.
None.
Data Preparation
To configure Ethernet CFM, you need the following data.
No. Data
1 Name and level of an MD
2 (Optional) Name and level of a default MD

No. Data
3 Name of an MA, ID of the VLAN associated with the MA
4 ID of a MEP, name of the interface on which the MEP resides, type of the MEP
5 (Optional) ID of an RMEP and MAC address of the interface where the RMEP resides
6 Rule for creating a MIP
7 Interval for a MEP sending or detecting CCMs in an MA
8 (Optional) ID of the specified VLAN
8.6.2 Switching IEEE 802.1ag Versions

A device can switch its Ethernet CFM version between IEEE 802.1ag Draft 7 and IEEE Standard
802.1ag-2007.
Context
By default, IEEE 802.1ag Draft 7 is enabled on the device. Do as follows on each NE80E/40E
that requires IEEE Standard 802.1ag-2007:
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm version { draft7 | standard }
The IEEE 802.1ag version is switched.
NOTE
All the devices on the network must be enabled with either IEEE 802.1ag Draft 7 or IEEE Standard
802.1ag-2007. IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007 cannot be enabled at the same time
on a network.
----End
8.6.3 Enabling Ethernet CFM Globally

You must enable Ethernet CFM globally before configuring and applying all CFM functions.
Context
Do as follows on the router that requires Ethernet CFM:

Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm enable
Ethernet CFM is enabled globally.

By default, Ethernet CFM on the router is disabled globally.
----End
8.6.4 Creating an MD
An MD refers to a network or a part of a network under the management of Ethernet CFM. One
MD is managed by a single ISP.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name [ format { no-md-name | dns dns-md-format-name | mac-address mac-md-
format-name | string string-md-format-name } ] [ level level ]
An MD is created and the MD view is displayed.

Parameters format, no-md-name, dns dns-md-format-name,mac-address mac-md-format-
name and string string-md-format-name can be used only on the device running IEEE Standard
802.1ag-2007.
By default, an MD is at level 0. Level 0 is the lowest level.
Repeat Step 2 to create more MDs. Up to 64 MDs can be created on the NE80E/40E.
NOTE
The 802.1ag packets from a lower-level MD are discarded when being transmitted through the same level
MD or a higher-level MD. The 802.1ag packets from a higher-level MD can be transmitted through a lower-
level MD.
----End
8.6.5 (Optional) Creating the Default MD

The default MD must be of a higher level than all MDs to which MEPs on the local device
belong. In addition, the default MD must be of the same level as the high-level MD. The high-
level CCMs are transmitted through the default MD.

Context
Do as follows on each NE80E/40E device that requires Ethernet CFM:
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm default md [ level level ]
The default MD is created and the default MD view is displayed.
By default, the default MD is at Level 7, the highest level.
Each device can create only one default MD.
NOTE
The default MD must be of a higher level than all MDs to which MEPs configured on the local device
belong. In addition, the default MD must be of the same level as the high-level MD. The default MD
transmits high-level CCMs and generates MIPs to reply LTR packets.
----End
8.6.6 Creating an MA
An MD can be divided into one or multiple MAs. Ethernet CFM detects connectivity of each
MA separately.
Context
Do as follows on the NE80E/40E that requires Ethernet CFM:
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
The MD view is displayed.
Step 3 Run:
ma ma-name [ format { icc-based iccbased-ma-format-name | string ma-format-name }]
An MA is created and the MA view is displayed.
On the NE80E/40E, up to 4k MAs can be created in an MD. On the NE80E/40E, up to 4k MAs

can be created.
One or multiple MA can map to one VLAN.

Step 4 Run:
map vlan vlan-id
Associate the MA with a VLAN.
By default, an MA is not associated with any VLAN.
Ethernet CFM maintains the connectivity of each MA separately. After an MA is associated

with a VLAN, Ethernet CFM can detect the connectivity fault on the network within the VLAN.
This step is optional. If an MA is classified to detect the connectivity fault between two directly
connected devices, the MA is not required to be associated with a VLAN. Otherwise, the MA
must be associated with a VLAN.
----End
Follow-up Procedure
An MA is associated with a VLAN only.
l If you need to create multiple MAs in an MD, repeat Step 3 and Step 4.
l If you need to create multiple MAs in multiple MDs, repeat Step 2 to Step 4.
8.6.7 Creating a MEP

A MEP is an edge node of an MA. It is configured on an interface manually.
Context
When creating a MEP in an MA, also note that:
l When an inward-facing MEP is created, the MA must be associated with a VLAN and the
interface on which the MEP resides must be added to the VLAN. The inward-facing MEP
then broadcasts the OAMPDUs in the VLAN associated with the MA. That is, the
inwarding-facing MEP sends the OAMPDUs out through all the interfaces excluding the
interface on which the MEP resides in the VLAN associated with the MAC.
l When the outward-facing MEP is created, the MA is not required to be associated with a
VLAN. However, if the MA is associated with a VLAN, the interface on which the MEP
resides must be added to the VLAN. The outward-facing MEP sends out the OAMPDUs
through the interface on which the MEP resides.
l When the VLAN-based MEP is created, the MA must be associated with a VLAN.
The following lists the requirements for the number and types of MEPs created in an MA:
l The inward-facing interface-based MEP and the outward-facing interface-based MEP

cannot coexist.
l Only one outward-facing interface-based MEP can be created. Multiple inward-facing
interface-based MEPs can be created. However, only one inward-facing interface-based
MEP can be created on an interface.
l Only one VLAN-based MEP can be created.

CAUTION
l One Trunk interface can be configured with only one MEP, regardless of how many sub-
interfaces the Trunk interface has.
l The system does not support hot swapping of boards.
Do as follows on the edge devices of an MA:
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name
The MA view is displayed.

Step 4 Run the following command as required.
l To create an interface-based MEP, run:
mep mep-id mep-id interface {interface-type interface-number | interface-type
interface-number. subnumber } [ vlan vlan-id ] { inward | outward }
l To create a VLAN-based MEP, run:

mep mep-id mep-id vlan
NOTE
On the NE80E/40E, the VLAN-based MEP is only used to detect connectivity faults in the multicast VLAN.
The interface-based MEP is used for other scenarios.
----End
Follow-up Procedure
l If you need to create multiple MEPs in an MA, repeat Step 4.
l If you need to create multiple MEPs in multiple MAs, repeat Step 3 and Step 4.
l If you need to create multiple MEPs in multiple MDs, repeat Step 2 to Step 4.
8.6.8 Creating an RMEP

For other devices in the same MA, their MEPs are RMEPs for the local device. By configuring
an RMEP, you can perform connectivity fault detection between the local MEP and the RMEP
in one MA.
Context
If you need to detect the connectivity between a device and an RMEP, you need to create the
RMEP first.

Do as follows on the edge devices of an MA:
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

Step 4 Run:
remote-mep mep-id mep-id [ mac mac-address ]
An RMEP in the current MA is created.
----End
Follow-up Procedure
l If you need to create multiple RMEPs in an MA, repeat Step 4.
l If you need to create multiple RMEPs in multiple MAs, repeat Step 3 and Step 4.
l If you need to create multiple RMEPs in multiple MDs, repeat Step 2 to Step 4.
8.6.9 (Optional) Setting the Rule for Creating a MIP

A MIP is a node inside an MA. MEPs periodically send multicast CCMs. A MIP needs to be
used to locate faults.
Context
Currently, IEEE 802.1ag has two versions, that is, IEEE 802.1ag Draft 7 and IEEE Standard
802.1ag-2007. The types of the MIP generation rule are the same in these two versions.
Differences of the MIP generation rules between these two versions, however, are as follows:
l According to IEEE 802.1ag Draft 7, MIPs are automatically generated on the basis of the
interface.
l According to IEEE Standard 802.1ag-2007, MIPs are automatically generated on the basis
of the MD or default MD.
Procedure
Step 1 Run:
system-view

Step 2 Choose the following commands to configure the MIP generation rule.
l To configure the MIP generation rule in accordance with IEEE 802.1ag Draft 7, run:
mip create-type { default | explicit | none } [ interface interface-type
interface-number ]
The MIP generation rule in accordance with IEEE 802.1ag Draft 7 is configured.
l To configure the MIP generation rule in accordance with IEEE Standard 802.1ag-2007,
choose one of the following commands to enter the proper view.
1. Run:
cfm md md-name

Or, run:
The default MD view is displayed.

2. Run:
mip create-type { default | explicit | none }
The MIP generation rule in accordance with IEEE Standard 802.1ag-2007 is configured.
By default, the rule for creating a MIP is set to none.
l default: MIPs can be generated on the interface, to which the MD or default MD belongs,
without a MEP of a higher level and a MIP of a lower level.
l explicit: MIPs can be generated on the interface, to which the MD or default MD belongs,
with a MEP of a lower level but without a MEP of a higher level or a MIP of a lower level.
l none: MIPs cannot be generated on the interface, to which the MD or default MD belongs.
If the rule for creating the MIP is default or explicit, the device generates the MIP automatically
according to the rule.
The level of a MIP depends on the level of the MD generating the MIP and the level generation
rule.
----End
8.6.10 Enabling CC Detection

Through the CC detection, Ethernet CFM can periodically send CCMs between MEPs to detect
connectivity between MEPs.
Context
Do as follows on the edge devices on which MEPs reside within MAs:
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name
Step 4 Run:
ccm-interval interval
The interval for the MEP sending or detecting CCMs within the local MA is set.
By default, the interval for the MEP sending or detecting CCMs within an MA is 1 second.
l The sending of CCMs is enabled by using the mep ccm-send enable command.
l The receiving of CCMs is enabled by using the remote-mep ccm-receive enable command.
If any of the preceding conditions is met in an MA, the interval for sending or detecting CCMs
in the MA cannot be modified. If you want to modify the interval for sending or detecting CCMs
in an MA, you must run the related undo commands to disable the sending or receiving of CCMs.
Step 5 Run:
mep ccm-send [ mep-id mep-id ] enable
The sending of CCMs is enabled on the MEP.
By default, a MEP is disabled to send CCMs.
If mep-id mep-id is not specified, all the MEPs in the MA are enabled to send CCMs.
Step 6 Run:
remote-mep ccm-receive [ mep-id mep-id ] enable
The receiving of CCMs from the RMEP within the same MA is enabled on the local MEP.
By default, the local MEP cannot receive CCMs from the RMEP.
When the local device is enabled to receive CCMs from an RMEP, and if connectivity faults are
detected between the local device and the RMEP through CC detection, the local device prompts
alarms of RMEP connectivity.
If mep-id mep-id is not specified, all the MEPs in the MA are enabled to receive CCMs from
all the RMEPs.
----End
Follow-up Procedure
l If you need to enable the CC detection in multiple MAs, repeat Step 3 to Step 6.
l If you need to enable the CC detection in multiple MDs, repeat Step 2 to Step 6.
8.6.11 (Optional) Creating a VLAN

Through the association between a VLAN and default MDs, all interfaces of the specified VLAN
can generate MIPs based on default MDs.
Context

Procedure
Step 1 Run:
system-view

Step 2 Run:
The default MD is created and the default MD view is displayed.

Step 3 Run:
vlan { vlan-id1 [ to vlan-id2 ] }&<1-10>
The specified VLAN is created.
----End

By viewing MDs, MAs, MEPs, and MIPs, you can check whether the configurations are
successful.
Prerequisite
The configurations of the Ethernet CFM function are complete.
Procedure
l Run the display cfm md [ md-name ] command to check the configuration information
about an MD.
l Run the display cfm ma [ md md-name [ ma ma-name ] ] command to check detailed
information about an MA.
l Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command
to check detailed information about a MEP.
l Run the display cfm remote-mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ]
command to check detailed information about an RMEP.
l Run the display mip create-type [ interface interface-type interface-number ] command
to check the rule for creating a MIP.
l Run the display cfm mip [ interface interface-type interface-number | level level ]
command to check information about a MIP.
l Run the display cfm default md command to check the configuration of the default MD.
l Run the display cfm error-info [ interface interface-type interface-number ] [ vlan
vlanid | vsi vsi-name ] [ error-type { ccm-interval-error | maid-error | mac-error | cfm-
leak } ] command to check information about incorrect configurations of the specified error
type.
l Run the display cfm mp-info [ interface interface-type interface-number [ level md-
level ] [ inward | outward ] [ vlan vlanid | vsi vsi-name | no-associated-vlan ] ]command
to check information about the CFM objects on the specified interface and VLAN or VSI.
l Run the display oam global configuration command to check the MP address model.
----End

Example
The output of the display cfm md command on the device running IEEE 802.1ag Draft 7 is
different from that on the device running IEEE Standard 802.1ag-2007.
Run the display cfm md command on the device running IEEE 802.1ag Draft 7. If information
about the MD and the MD level is displayed, it means that the MD is created successfully.
<HUAWEI> display cfm md
The total number of MDs is 2
MD-Name Level
--------------------------------------------------
md2 7
md3 3
Run the display cfm md command on the device running IEEE Standard 802.1ag-2007. If
information about the name of the MD, MD name format, MD level, MIP generation rule, and
sender ID TLV type is displayed, it means that the MD is created successfully.
<HUAWEI> display cfm md mdcustomer
The total number of MDs is : 1
------------------------------------------------
MD Name : md
MD Name Format : string
Level : 0
MIP Create-type : none
SenderID TLV-type : defer
MA list :
MA Name : ma
MA Name Format : string
Interval : 1000
Vlan ID : 2
VSI Name : --
L2VC ID : --
Run the display cfm ma command. If information about the MA is displayed, it means that the
configuration is successful.
<HUAWEI> display cfm ma md md1
The total number of MAs is 2:
MD Name : md1
Level : 7
SenderID TLV-type : Defer
MA Name : ma1
Interval : 10ms
Priority : 4
Vlan ID : 7
VSI Name : --
L2VC ID : --
MEP Number : 2
RMEP Number : 3
Suppressing Alarms : No
Sending Ais Packet : No
MD Name : md1
Level : 7
SenderID TLV-type : Defer
MA Name : ma2
Interval : 10ms
Priority : 5
Vlan ID : 8
VSI Name : --
L2VC ID : --

MEP Number :1
RMEP Number : 4
Run the display cfm mep command. If information about the MEP is displayed, it means that
the configuration is successful.
<HUAWEI> display cfm mep
The total number of MEPs is 2
MD Name : md2
Level : 7
MA Name : ma3
MEP ID : 40
Vlan ID : 10
VSI Name : --
Interface Name : GigabitEthernet1/0/1
CCM Send : enabled
Direction : outward
MD Name : md3
Level : 3
MA Name : ma1
MEP ID : 100
Vlan ID : 20
VSI Name : --
CCM Send : enabled
Direction : outward
Run the display cfm remote-mep command. If information about the RMEP is displayed, it
means that the configuration is successful.
<HUAWEI> display cfm remote-mep
The total number of RMEPs is 2
MD Name : md2
Level : 7
MA Name : ma3
RMEP ID : 110
Vlan ID : 20
VSI Name : --
MAC : 0000-0121-0222
CCM Receive : enabled
Trigger-If-Down : disabled
CFM Status : up
MD Name : md2
Level : 4
MA Name : ma3
RMEP ID : 30
Vlan ID : --
VSI Name : --
MAC : --
CFM Status : up
Run the display mip create-type command. If the MIP generation rule is correct, it means that
<HUAWEI> display mip create-type interface gigabitethernet1/0/1
Interface Name MIP Create-Type MIP Create-Type On Interface
---------------------------------------------------------------------------
GigabitEthernet1/0/1 none --
Run the display cfm mip command. If information about the MIP is displayed, it means that

<HUAWEI> display cfm mip

Interface Name Level MAC
--------------------------------------------------------
GigabitEthernet2/0/8 0 0018-82e2-377f
Run the display cfm default md command. If information about the level of the default MD,
MIP generation rule, sender ID TLV type, and VLAN chain associated with the default MD is
displayed, it means that the configuration is successful.
<HUAWEI> display cfm default md
Level MIP Create-type SenderID TLV-type VLAN List
----------------------------------------------------------------------------------
------
7 default Defer 100 to 200 2049
Run the display cfm error-info command. If information about the incorrect configuration of
the specified error type is displayed, it means that the configuration is successful.
<HUAWEI> display cfm error-info interface gigabitethernet1/0/2 error-type cfm-leak
The total number of Errors is : 1
----------------------------------------
Interface : gigabitethernet1/0/2
VLAN ID : 100
VSI Name : --
Error Type : ccm-interval-error cfm-leak
MD Name : md1
MA Name : ma1
Level : 3
MEP ID : 10
CCM-Interval : 20
MAC Address : 0018-8247-b977
Run the display cfm mp-info command. If information about the CFM objects of the specified
interface and VLAN or VSI is displayed, it means that the configuration is successful.
<HUAWEI> display cfm mp-info interface gigabitethernet 1/0/1 level 6 inward vlan
300
MD Name : md1
Level : 6
MA Name : ma1
MEP ID : 10
VLAN ID : 300
VSI Name : --
Interface Name : gigabitethernet 1/0/1
CCM Send : enable
Direction : inward
MAC Address : 0018-8247-b977
MEP Pe-vid : --
MEP Ce-vid : --
MEP Vid : --
Alarm Status : none
Run the display oam global configuration command. The command output shows that the
individual MP address model is configured.
<HUAWEI> display oam global configuration
global conf value
----------------------------------------------------------
cfm status enabled
ping mac status disabled
trace mac status disabled
cfm mac-tunnel mip trace status disabled
efm status disabled
cfm protocol standard
cfm mp-address-model individual

8.7 Configuring Related Parameters of Ethernet CFM

By adjusting parameters of Ethernet CFM, you can detect connectivity of an Ethernet network
from end to end.

Before configuring parameters of Ethernet CFM, familiarize yourself with the applicable
Application Environment
If Ethernet CFM is enabled, you can adjust related parameters according to your requirement.
In different application environments, you can adjust the following parameters:
l RMEP activation time

After the local device is enabled with the function of receiving CCMs from a certain RMEP,
the local device can display RMEP connectivity alarm in one of the following situations:
– If the CC detects a connectivity fault between the local MEP and the RMEP, then, the
local device displays the alarm of the RMEP connectivity fault..
– The physical link works normally between the local MEP and the RMEP. The peer
device is not configured with a MEP when the CC is performed; or, the MEP
configuration is performed after the CC is performed. In this case, if the local MEP does
not receive any CCMs from the RMEP in three consecutive sending intervals, the local
device considers that a connectivity fault occurs between the local MEP and the RMEP.
According to the preceding description, the RMEP connectivity fault alarm is incorrect.
To solve the problem, you can set the RMEP activation time.
If the local device is configured with the RMEP activation time and enabled with the
function of receiving CCMs from a certain RMEP, the local device can receive CCMs at
the set RMEP activation time. That is, the activation time for receiving CCMs from the
RMEP is the time reserved for configuring the RMEP.
At the set RMEP activation time, if the local MEP does not receive any CCMs in three
consecutive sending intervals, this means that a connectivity fault occurs between the local
MEP and the RMEP. In addition, the local device displays the alarm of the RMEP
connectivity fault.
l Anti-jitter time during alarm restoration
All the RMEPs of each MA use the following timers:
– Alarm generation timer: Its interval is set to the anti-jitter time during alarm generation.
– Alarm restoration timer: Its interval is set to the anti-jitter time during alarm restoration.
When the RMEP detects an alarm, the alarm generation timer is activated. After the timer
expires, the alarm is notified to the device. When the RMEP detects that the alarm is
restored, the alarm restoration timer is activated. After the timer expires, the alarm
restoration event is notified to the device.
If the RMEP frequently detects the alarm and alarm restoration signals, this means that
alarm flapping occurs.

To suppress alarm flapping, you can set the anti-jitter time during alarm generation.
l VLAN or VLAN chain
All interfaces of the specified VLAN generate MIPs according to the configured MIP
generation rule in the MD.
None.
Data Preparation
To adjust parameters of Ethernet CFM, you need the following data.
No. Data
1 (Optional) RMEP activation time
2 (Optional) Anti-jitter time during alarm restoration
3 (Optional) Anti-jitter time during alarm generation
8.7.2 (Optional) Configuring the RMEP Activation Time

The RMEP activation time is reserved for you to configure an RMEP. After the configuration
of the RMEP activation time, the local device can receive CCMs after the configured RMEP
activation time expires.
Context
Do as follows on each edge device in an MA:
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

Step 4 Run:
active time time
The RMEP activation time is configured.
----End

8.7.3 (Optional) Configuring the Anti-Jitter Time During Alarm

Restoration
By configuring the anti-jitter time during alarm restoration, you can suppress alarm flapping.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

Step 4 Run:
alarm finish time time
The anti-jitter time during alarm restoration is configured.
----End
8.7.4 (Optional) Configuring the Anti-Jitter Time During Alarm

Generation
By configuring the anti-jitter time during alarm restoration, you can suppress the alarm flapping.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

Step 4 Run:
alarm occur time time
The anti-jitter time during alarm generation is configured.
----End
8.8 Fault Verification on the Ethernet

By sending detection packets and waiting for replies, you can test connectivity of the path
between devices.

Before configuring the Ethernet fault verification function, familiarize yourself with the
To manually detect the connectivity between two devices, you can send test packets and wait
for a reply to test whether the destination device is reachable. There are the following scenarios
based on the type of the link to be tested:
l For the network where the MD, MA, and MEP are configured, you can implement 802.1ag
MAC ping to test the connectivity between MEPs at the same maintenance level or between
MEPs and MIPs at the same maintenance level.
l For the network where the MD, MA, and MEP are not configured, you can implement
Gmac ping to test the connectivity between two devices.
l You can implement PBB-TE MAC ping to test the connectivity on the PBB-TE tunnel.
Before implementing 802.1ag MAC ping, complete the following tasks:
l Configuring Ethernet CFM
No pre-configuration tasks are needed to implement Gmac ping and PBB-TE MAC ping.
Data Preparation
To detect the connectivity on the Ethernet, you need the following data.
No. Data
1 (Optional) Bridge MAC address of the device on which the destination MEP resides
or ID of the destination MEP
2 (Optional) Bridge MAC address of the device on which the destination MIP resides
3 (Optional) Number, size, timeout period, and outbound interface of LBMs

No. Data
4 (Optional) VLAN to which the destination node belongs
5 (Optional) Name of the PBB-TE tunnel
8.8.2 (Optional) Implementing 802.1ag MAC Ping

By performing the 802.1ag MAC ping, you can detect connectivity between MEPs or between
MEPs and MIPs within an MA.
Context
Similar to the ping operation, 802.1ag MAC ping checks whether the destination device is
reachable by sending test packets and receiving response packets. In addition, the ping operation
time can be calculated at the transmitting end for network performance analysis.
Procedure
Step 1 Do as follows on the router with a MEP at one end of the link to be tested.
1. Run:
system-view

2. Run:
cfm md md-name

3. Run:
ma ma-name

4. Run:
ping mac-8021ag mep mep-id mep-id mac mac-address | remote-mep mep-id mep-id }
[ -c count | interface interface-type interface-number | -s packetsize | -t
timeout ] *
The connectivity between a MEP and a MEP or a MIP on other devices is tested.
When implementing 802.1ag MAC ping, ensure that:
l The MA is associated with a VLAN.
l The MEP is configured in the MA.
l If the outbound interface is specified, it cannot be configured with an inward-facing
MEP. The interface must be added to the VLAN associated with the MA.
l If the destination node is a MEP, either mac mac-address or remote-mep mep-id mep-
id can be selected. If remote-mep mep-id mep-id is selected, the RMEP must already
be created with the remote-mep command and the MAC address of the RMEP.
l If the destination node is a MIP, select mac mac-address.
The intermediate device on the link to be tested only forwards LBMs and LBRs. In this
manner, the MD, MA, or MEP are not required to be configured on the intermediate device.
----End

8.8.3 (Optional) Implementing Gmac ping

By performing the Gmac ping, you can detect connectivity between devices.
Context
Perform Step 1 and Step 2 on the routers at both ends of the link to be tested. Perform Step 3 on
any of the routers.
Procedure
Step 1 Run:
system-view

Step 2 Run:
ping mac enable
Gmac ping is enabled globally.

By default, Gmac ping is disabled.
When Gmac ping is enabled:
l MAC ping can be implemented on the routers.
l The routers can respond to LBMs.
Step 3 Run:
ping mac mac-address vlan vlan-id [ interface interface-type interface-number | -c
count | -s packetsize |-t timeout | -p priority-value ] *
The connectivity between the router and the remote device is tested.
A MEP is not required to initiate Gmac ping. The destination node does not need to be a MEP
or a MIP. Gmac ping can be implemented without configuring the MD, MA, or MEP on the
source device, the intermediate device, and the destination device.
The two devices must be enabled with 802.1ag of the same version. If the local device is enabled
with IEEE 802.1ag Draft 7 and the peer is enabled with IEEE Standard 802.1ag-2007, the local
device cannot ping through the peer device when the ping mac command is run to detect
connectivity of the link between the local and peer devices.
----End
8.9 Locating the Fault on the Ethernet

By sending test packets and waiting for a reply, you can test connectivity of the path between
devices and locate faults.

Before configuring the Ethernet fault verification function, familiarize yourself with the

To locate the connectivity fault between two devices, you can send test packets and wait for
reply packets to test the path between the local device and the destination device and to locate
faults. There are the following scenarios based on what kind of link is being tested:
l For the network where the MD, MA, and MEP are configured, you can implement 802.1ag
MAC trace to locate the connectivity fault between MEPs at the same maintenance level
or between MEPs and MIPs at the same maintenance level.
l For the network where the MD, MA, and MEP are not configured, you can implement
Gmac trace to locate the connectivity fault between two devices.
l You can implement PBB-TE MAC trace to locate the connectivity fault on the PBB-TE
tunnel.
Before implementing 802.1ag MAC trace, complete the following tasks:
No pre-configuration tasks are needed to implement Gmac trace and PBB-TE MAC trace.
Data Preparation
To locate the connectivity fault on the Ethernet, you need the following data.
No. Data
1 (Optional) Bridge MAC address of the device on which the destination MEP resides
or ID of the destination MEP
2 (Optional) Bridge MAC address of the device on which the destination MIP resides
3 (Optional) Outbound interface of Linktrace Messages (LTMs)
4 (Optional) Timeout period for waiting for an LTR
5 (Optional) Time to Live (TTL) of LTMs
6 (Optional) VLAN to which the destination node belongs
7 (Optional) Name of the PBB-TE tunnel
8.9.2 (Optional) Implementing 802.1ag MAC Trace

By performing the 802.1ag MAC trace, you can detect connectivity between MEPs or between
MEPs and MIPs within an MA and locate faults.
Context
Similar to tracerout or tracert, 802.1ag MAC trace tests the path between the local device and a
destination device or locates failure points by sending test packets and receiving reply packets.

Procedure
Step 1 Do as follows on the router with a MEP at one end of the link to be tested.
1. Run:
system-view

2. Run:
cfm md md-name

3. Run:
ma ma-name

4. Run:
trace mac-8021ag mep mep-id mep-id { mac mac-address | remote-mep mep-id mep-
id }[interface interface-type interface-number | -t timeout | ttl ttl ] *
The connectivity fault between the localrouter and the remote router is located.
When implementing 802.1ag MAC trace, ensure that:
l The MA is associated with a VLAN.
l The MEP is configured in the MA.
l If the outbound interface is specified, it cannot be configured with an inward-facing
MEP. The interface must be added to the VLAN associated with the MA.
l If the destination node is a MEP, either mac mac-address or remote-mep mep-id mep-
id can be selected. If remote-mep mep-id mep-id is selected, the RMEP must already
be created with the remote-mep command and the MAC address where the RMEP
resides must be specified.
l If the destination node is a MIP, select mac mac-address.
l If the forwarding entry of the destination node does not exist in the MAC address table,
interface interface-type interface-number must be specified.
The intermediate device on the link to be tested only forwards LTMs and LTRs. In this
manner, the MD, MA, or MEP are not required to be configured on the intermediate device.
----End
8.9.3 (Optional) Implementing Gmac trace

By performing the GMAC trace, you can detect connectivity between devices and locate faults.
Context
You need to configure the routers at both ends and the intermediate router on the link to be tested.
Procedure
Step 1 Configuring the routers at both Ends and the Intermediate router
Do as follows on the routers at both ends and the intermediate router on the link to be tested:
1. Run:
system-view


2. Run:
trace mac enable
Gmac trace is enabled globally.

By default, Gmac trace is disabled.
The following can be performed only after Gmac trace is enabled:
l Gmac trace can be implemented on the router.
l The routers can respond to LTMs of Gmac trace.
Step 2 Implementing Gmac trace
Do as follows on the router at one end of the link to be tested:
1. Run:
system-view

2. Run:
trace mac mac-address vlan vlan-id [ interface interface-type interface-
number | -t timeout ] *
The connectivity fault between the router and the remote router is located.
A MEP is not required to initiate Gmac trace. The destination node does not need to be a
MEP or a MIP. Gmac trace can be implemented without configuring the MD, MA, or MEP
on the source device, the intermediate device, and the destination device.
The two devices must be enabled with 802.1ag of the same version. If the local device is
enabled with IEEE 802.1ag Draft 7 and the peer device is enabled with IEEE Standard
802.1ag-2007, the faulty node cannot be located when the trace mac command is run to
detect connectivity of the link between the local and peer devices.
----End
8.10 Associating Ethernet CFM with an Interface

The association between Ethernet CFM and an interface is used to detect faults of an active link
in the LACP static link aggregation group or in the manually-configured 1:1 active/standby link
aggregation group and then trigger the protection switchover.

Before configuring the association between Ethernet CFM and an interface, familiarize yourself
After Ethernet CFM is associated with an interface, when a MEP detects a connectivity fault
between the MEP and a specified RMEP within the same MA, the OAM management module
shuts down and then turns on the interface on which the MEP resides so that the other modules
can sense the fault.

Figure 8-7 Diagram of associating Ethernet CFM with an interface (1)

Ethernet CFM
GE1/0/1 GE2/0/1
RouterA RouterB
The interface associated with Ethernet CFM

Ethernet CFM
GE1/0/1 GE2/0/1 GE1/0/1 GE2/0/1

RouterA RouterC RouterB
The interface associated with Ethernet CFM
Ethernet CFM is used to detect a directly connected link shown in Figure 8-7, or a multi-hop
link shown in Figure 8-8. Configure Ethernet CFM on Router A and Router B; associate Ethernet
CFM with GE 1/0/1 on Router A. When the CFM OAM module on Router A detects a
connectivity fault between Router A and Router B, the OAM management module shuts down
GE 1/0/1 and then starts it so that the other interfaces on Router A can sense the fault.

Ethernet CFM
GE1/0/1 Link1 GE1/0/1
GE1/0/2 Link2 GE1/0/2 RouterB
RouterA
Link3
GE1/0/3 GE1/0/3
Active link
Inactive link MEPs in MA1
MEPs in MA2
Aggregation group in MEPs in MA3
static LACP mode
Configure the link aggregation group in static LACP mode on Router A and Router B. Enable
Ethernet CFM on Router A and Router B. Router A and Router B belong to the same MD.
Configure the MEP on all the member interfaces of the aggregation group. MEPs on the
interfaces of the same link are configured within the same MA. MEPs on the interfaces along
the same link belong to the same MA. MEPs on the interfaces on different links belong to
different MAs. Ethernet CFM detects the link connectivity by exchanging CCMs between MEPs
of the same link. You can then associate Ethernet CFM with the interfaces.
When a connectivity fault occurs on Link 1, the OAM management modules on Router A and
Router B shut down and then turn on their GE 1/0/1 interfaces respectively. In this manner, the

LACP module senses the connectivity fault on Link 1 and switches the service data forwarded
on Link 1 to the inactive Link 3. This implements protection switching in no more than 50 ms
to achieve carrier-class reliability.

RouterC
GE2/0/1 GE2/0/2
C M
F Ethe
t h ernet rn et C
F
GE1/0/1 E M GE1/0/1
Eth-Trunk1 Eth-Trunk1
RouterA RouterB
GE1/0/2 Ethe F M GE1/0/2
r net
CFM e r net C
Et h
GE2/0/1 RouterD GE2/0/2
Aggregation group in 1:1 Active link MEPs in MA1

active/standby mode Inactive link MEPs in MA2
MEPs in MA3
MEPs in MA4
Configure the link aggregation group in 1:1 active/standby mode on Router A and Router B.
Configure Ethernet CFM on Router A, Router B, Router C, and Router D respectively. Associate
Ethernet CFM with GE 1/0/1 and GE 1/0/2 on Router A and Router B.
Assume that a connectivity fault occurs on the link between Router A and Router C. The Ethernet
CFM module detects the fault and notifies the OAM management module of the fault. The OAM
management module shuts down and then starts GE 1/0/1. This allows the link aggregation group
to sense the fault and switch the service data to the inactive link. The procedure for processing
connectivity faults on the other links is similar to that for processing the link fault between Router
A and Router C. This implements protection switching in no more than 50 ms to achieve carrier-
class reliability.
Before associating Ethernet CFM with an interface, complete the following tasks:
l Configuring the link aggregation group
Data Preparation
To associate Ethernet CFM with an interface, you need the following data.
No. Data
1 Type and number of an interface
2 Name of an MD, MA, and ID of an RMEP

8.10.2 Associating Ethernet CFM with an Interface

Through the configured association between Ethernet CFM and an interface, a MEP in a
specified MA can detect a connectivity fault between the MEP and a specified RMEP within
the same MA. Then, the OAM module blocks and then unblocks the interface on which the MEP
resides so that other modules can sense the fault.
Context
Do as follows on the NE80E/40E configured with the link aggregation group in static LACP
mode:
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of a member interface of the link aggregation group is displayed.

Step 3 Run:
cfm md md-name ma ma-name remote-mep mep-id mep-id trigger if-down
Ethernet CFM is associated with an interface.

By default, an interface is not associated with Ethernet CFM.
It is required that outward-facing MEPs be created in the specified MA and the current interface
is configured with outward-facing MEPs before you use the cfm md md-name ma ma-name
remote-mep mep-id mep-id trigger if-down command.
An interface can be associated with an RMEP only. You need to delete the current configurations
to modify the mapping between the interface and the RMEP.
If multiple member interfaces exist in the link aggregation group, you should repeat Step 2 and
Step 3 to associate Ethernet CFM with all the member interfaces.
----End

By viewing the Trigger-If-down field, you can check whether the configurations are successful.
Prerequisite
The configurations of Associating Ethernet CFM with an Interface function are complete.
Procedure
Step 1 Run the display cfm remote-mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command
to check detailed information about an RMEP.
----End

Example
Run the display cfm remote-mep command. If the "Trigger If-down" field for the RMEP is
displayed as "enable", it means that the configuration succeeds.
The total number of RMEPs is : 1
The status of RMEPS : 0 up, 1 down, 0 disable
--------------------------------------------------
MD Name : md110
Level : 0
MA Name : ma110
RMEP ID : 2
Vlan ID : --
VSI Name : --
L2VC ID : 110 tagged
MAC : 0025-9eb1-bce6
CFM Status : down
Alarm Status : RemoteAlarm
8.11 Associating EFM OAM with Ethernet CFM

By configuring the association between EFM OAM and Ethernet CFM, you can implement the
bidirectional fault notification.

Before configuring the association between EFM OAM and Ethernet CFM, familiarize yourself
IEEE 802.3ah is designed for the last mile of the Ethernet to detect the direct link between a CE
and a PE. IEEE 802.1ag is designed for a group of services or some specific network devices to
detect faults on the network. It functions between the following devices:
l CE and CE
l PE and PE
l CE and PE
As shown in Figure 8-11, EFM OAM or Ethernet CFM runs between CE1 and PE1, and between
CE2 and PE2; Ethernet CFM runs between PE1 and PE2. Configure the association between
Ethernet OAMs. When a fault occurs on the link between CE1 and PE1, Ethernet CFM sends
alarms of the fault to CE2.
Figure 8-11 Diagram of associating Ethernet OAM with Ethernet OAM

CE1 PE1 PE2 CE2

Before associating Ethernet OAM with Ethernet OAM, complete the following tasks:

Data Preparation
To associate Ethernet OAM with Ethernet OAM, you need the following data.
No. Data
1 Number of the interfaces to be associated
2 Name of an MD and an MA
8.11.2 Associating Ethernet OAM with Ethernet OAM

You can configure the fault notification mode as required.
Context
Do as follows on the CEs:
Procedure
Step 1 Run:
system-view
Step 2 Run:
oam-mgr
The OAM management view is displayed.

l Run:
oam-bind cfm md md-name ma ma-name efm interface interface-type interface-number
The bidirectional transmission of fault messages between EFM OAM and Ethernet CFM is
configured.
l Run:
oam-bind ingress efm interface interface-type interface-number egress cfm md md-
name ma ma-name
EFM OAM is configured to send fault messages to Ethernet CFM.

l Run:
oam-bind ingress cfm md md-name ma ma-name egress efm interface interface-type
interface-number
Ethernet CFM is configured to send fault messages to EFM OAM.

l Run:
oam-bind ingress cfm md md-name1 ma ma-name1 egress cfm md md-name2 ma ma-name2
Ethernet CFM at one side is configured to send fault messages to Ethernet CFM at the other
side.
l Run:
oam-bind cfm md md-name1 ma ma-name1 cfm md md-name2 ma ma-name2
The bidirectional transmission of fault messages between Ethernet CFMs at both sides is
configured.
NOTE
After Ethernet OAM is associated with other functional modules, note the following:
l If EFM OAM is disabled on an interface, the association between EFM OAM and other functional
modules is deleted.
l If an MA or MD is deleted, the association between Ethernet CFM and other functional modules is
deleted.
----End

By viewing whether Ethernet CFM sends trap messages to advertise fault information to the
peer, you can check whether the configurations are successful.
Procedure
l After the preceding configuration, when Ethernet OAM running between CE1 and PE1
detects faults, Ethernet CFM notifies Ethernet OAM running between CE2 and PE2 of the
fault.
----End
8.12 Associating Ethernet CFM with VPLS

By associating Ethernet CFM with the VPLS, you can implement end-to-end detection,
advertisement, verification, and location of connectivity faults in the VPLS scenario.

Before associating Ethernet CFM with the VPLS, familiarize yourself with the applicable
As shown in Figure 8-12, VPLS runs between PE1 and PE2; CEs, CEs and PEs, and PEs belong
to different MAs. CFM OAM runs between CEs and between CEs and PEs. CCMs are exchanged
to detect the connectivity. MAC ping is performed to detect the reachability of the destination.
MAC trace is performed to locate the fault. VPLS OAM runs between the PEs to detect the
connectivity of the VPLS network.

Figure 8-12 Networking diagram of associating Ethernet CFM with VPLS
CE1 PE1 PE2 CE2

802.1ag 802.1ag
VPLS
Before associating Ethernet CFM with VPLS, complete the following tasks:
l Configuring the Martini VPLS

l Configuring basic Ethernet functions
Data Preparation
To associate Ethernet CFM with VPLS, you need the following data.
No. Data
1 Name and ID of the VSI
2 IP address of the peer and tunnel policy used for setting up the peer
3 Interfaces bound to a VSI
4 Types of detection packets
5 Name of an MD and MA
8.12.2 Configuring Ethernet CFM Based on the VPLS Between the

PEs
By configuring Ethernet CFM on the VPLS network between PEs, you can implement end-to-
end detection, advertisement, verification, and location of connectivity faults between PEs.
Context
NOTE
l If 802.1ag MAC trace needs to be implemented to locate the connectivity fault between the PEs, you
cannot specify the outbound interface for sending trace packets.
l The current MA must be associated with a VSI and the type of the MEP must be inward-facing.
Do as follows on the PEs:

Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name[ level level ]

Step 3 Run:
ma ma-name

Step 4 Run:
map vsi vsi-name
The MA is associated with a VSI.

Step 5 Run:
mep mep-id mep-id interface { interface-type interface-number | interface-type
interface-number.subnumber} inward
An inward-facing MEP is created.

Step 6 Run:
remote-mep mep-id mep-id[ mac mac-address ]
An RMEP in the MA is created.

Step 7 Run:
The MEPs are enabled to send CCMs.

Step 8 Run:
The local MEP is enabled to receive CCMs from the RMEP within the same MA.
----End
8.12.3 Configuring Ethernet CFM Between the CE and Local PE

By configuring Ethernet CFM between a CE and the local PE, you can implement end-to-end
detection, advertisement, verification, and location of connectivity faults between the CE and
the local PE.
Procedure
l Do as follows on the PEs:
NOTE
The MA configured on the PE must be associated with a VSI and the type of the MEP must be
outward-facing.
1. Run:
system-view


2. Run:
cfm md md-name [ level level ]

3. Run:
ma ma-name

4. Run:
map vsi vsi-name

5. Run:
mep mep-id mep-id interface { interface-type interface-number | interface-
type interface-number.subnumber} outward
An outward-facing MEP is created.

6. Run:

7. Run:
The MEPs are enabled to send CCMs on a MEP.

8. Run:
The local MEP is enabled to receive CCMs from the RMEP in a same MA.
l Do as follows on the CE:
NOTE
The MA configured on the CE must be associated with a VLAN and the type of the MEP must be
outward-facing.
1. Run:
system-view

2. Run:

3. Run:
ma ma-name

4. Run:
map vlan vlan-id
The MA is associated with a VLAN.

5. Run:
type interface-number.subnumber } outward

An outward-facing MEP is created.

6. Run:

7. Run:
The MEPs are enabled to send CCMs on a MEP.

8. Run:
The local MEP is enabled to receive CCMs from the RMEP in a same MA.
----End
8.12.4 Configuring Ethernet CFM Between the CE and Peer PE

By configuring Ethernet CFM between a CE and the remote PE, you can implement end-to-end
detection, advertisement, verification, and location of connectivity faults between the CE and
the remote PE.
Context
The configuration is similar to that in8.12.3 Configuring Ethernet CFM Between the CE and
Local PE.
NOTE
l The MA configured on the PE must be associated with a VSI and the type of the MEP must be inward-
facing.
l The MA configured on the CE must be associated with a VLAN and the type of the MEP must be
outward-facing.
l The rule for creating the MIP needs to be configured on transit nodes.

By viewing MDs, MAs, MEPs, and MIPs, you can check whether the configurations are
successful.
Procedure
l After the preceding configuration, run the display cfm mep command and the display cfm
remote-mep command on CE1, PE1, PE2, and CE2. You can view that the configuration
of Ethernet CFM succeeds. Ethernet CFM can fast detect faults between the PEs and
between the CEs and PEs, and can notify the NMS of the faults.
----End

8.13 Associating Ethernet CFM with VLL (by Using Sub-

interfaces for QinQ VLAN Tag Termination)
In the scenario where PEs that send packets with double VLAN tags access a Virtual Leased
Line (VLL), you can configure sub-interfaces for QinQ VLAN tag termination on AC interfaces
of the PEs to bind L2VCs and then configure Ethernet CFM on the PEs.

Before associating Ethernet CFM with VLL, you must check whether packets received on PEs
carry one VLAN tag or double VLAN tags. If PEs receive packets with one VLAN tag, PEs can
access a VLL through common sub-interfaces or the sub-interface for dot1q VLAN tag
termination. If PEs receive packets with double VLAN tags, you must bind sub-interfaces for
QinQ VLAN tag termination to L2VCs. The following describes the configuration in the
scenario where PEs receive packets with double VLAN tags.
As shown in Figure 8-13, MAs are configured between:
l PEs
l Switches and local PEs
l Switches and remote PEs
l Switches
MEPs within the same MA can detect the connectivity between themselves by exchanging
CCMs. Once a connectivity fault is detected, you can perform the MAC ping or MAC trace
operation to further locate the fault.
Figure 8-13 Networking diagram of associating Ethernet CFM with VLL
CE1 Switch1 PE1 PE2 Switch2 CE2

VLL
user user
network1 network2
802.1ag
802.1ag 802.1ag
802.1ag
802.1ag
MEP
MIP

PE1 and PE2 are connected through a VLL. PEs receive packets with double VLAN tags. To
check connectivity between PEs, you need to configure sub-interfaces for QinQ VLAN tag
termination on AC interfaces of the PEs to bind L2VCs and then configure Ethernet CFM on
the PEs.
Before associating Ethernet CFM with VLL by using sub-interfaces for QinQ VLAN tag
termination, complete the following tasks:
l Configuring a Martini VLL
For details, refer to the chapter "VLL Configuration" in the HUAWEI NetEngine80E/40E
Router Configuration Guide - VPN.
l Configuring sub-interfaces for QinQ VLAN tag termination to access the VLL
For details, refer to the chapter "QinQ Configuration" in the HUAWEI NetEngine80E/
40E Router Configuration Guide - LAN Access and MAN Access.
l 8.6 Configuring Basic Ethernet CFM
Data Preparation
To associate Ethernet CFM with VLL by using sub-interfaces for QinQ VLAN tag termination,
you need the following data.
No. Data
1 Destination address and VC ID of an L2VC
2 Name of an interface to which an L2VC is bound
3 Names of MDs and MAs
4 ID of a MEP, name of the interface on which the MEP resides, and type of the MEP
6 Interval for MEPs sending CCMs in an MA
8.13.2 Configuring Ethernet CFM on PEs on a VLL

Ethernet CFM provides end-to-end connectivity detection, fault notification, fault verification,
and fault location. Providing the preceding functions, Ethernet CFM can be used to detect the
connectivity of the entire network and locate faults. This helps improve the reliability of the
network.
Context
NOTE
l When performing 802.1ag MAC trace between PEs, you cannot specify the outbound interface for
sending trace packets.
l The current MA must be associated with an L2VC, and the type of the MEP must be inward-facing.

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
ma ma-name

Step 4 Run:
map mpls l2vc vc-id { raw | tagged }
The L2VC is associated with a MA.
NOTE
MA cannot be associated with backup VC in 802.1ag.
The interface of the raw type and the interface of the tagged type process packets in different
manners, as shown in Table 8-2 and Table 8-3.
Table 8-2 Packet processing on the inbound interface

Type of the raw Encapsulation (Ethernet tagged Encapsulation
Inbound Interface Encapsulation) (VLAN Encapsulation)
Dot1q sub-interface Strips one tag. Reserves the tag, and no action is
required.
Dot1q termination Strips one tag. Reserves the tag, and no action is
sub-interface required.
QinQ termination Strips the outer tag. Reserves the double tags, and no
sub-interface (in action is required.
symmetrical mode)
QinQ termination Strips the double tags. Strips two tags and then adds one
sub-interface (in tag.
asymmetrical mode)

Table 8-3 Packet processing on the outbound interface
Type of the raw Encapsulation (Ethernet tagged Encapsulation

Outbound Encapsulation) (VLAN Encapsulation)
Interface
Dot1q sub-interface Adds one tag. Replaces the tag with the tag that
is encapsulated on the outbound
interface.
Dot1q termination Adds one tag. Replaces the tag with the tag that
sub-interface is encapsulated on the outbound
interface.
QinQ termination Adds the outer tag. Replaces the outer tag with the
sub-interface (in tag that is encapsulated on the
symmetrical mode) outbound interface.
QinQ termination Adds double tags. Removes the outer tag and then
sub-interface (in adds two tags that are
asymmetrical mode) encapsulated
Step 5 Run:
interface-number.subnumber } pe-vid pe-vid ce-vid ce-vid inward
An inward-facing MEP is created on the sub-interface for QinQ VLAN tag termination of the
AC interface bound to the L2VC on the PE.
Step 6 Run:
An RMEP is created in the MA.

Step 7 Run:
A MEP is enabled to send CCMs.

Step 8 Run:
The MEP is enabled to receive CCMs from the RMEP in the same MA.
----End
8.13.3 Configuring Ethernet CFM on the Switch and Local PE

Run Ethernet CFM between the switch and local PE to check connectivity by exchanging CCMs.
Procedure
l Do as follows on the PE:
NOTE
The MA configured on the PE must be associated with an L2VC, and the type of the MEP must be
outward-facing.

1. Run:
system-view

2. Run:

3. Run:
ma ma-name

4. Run:
The L2VC is associated with a MA.
NOTE
The interface of the raw type and the interface of the tagged type process packets in
different manners, as shown in Table 8-4 and Table 8-5.
Table 8-4 Packet processing on the inbound interface
Type of the raw Encapsulation tagged Encapsulation

Inbound (Ethernet Encapsulation) (VLAN Encapsulation)
Interface
Dot1q sub- Strips one tag. Reserves the tag, and no

interface action is required.
Dot1q termination Strips one tag. Reserves the tag, and no

sub-interface action is required.
QinQ termination Strips the outer tag. Reserves the double tags, and
sub-interface (in no action is required.
symmetric mode)
QinQ termination Strips the double tags. Strips two tags and then adds
sub-interface (in one tag.
asymmetric mode)
Table 8-5 Packet processing on the outbound interface

Outbound (Ethernet Encapsulation) (VLAN Encapsulation)
Interface
Dot1q sub- Adds one tag. Replaces the tag with the tag
interface that is encapsulated on the
outbound interface.


Outbound (Ethernet Encapsulation) (VLAN Encapsulation)
Interface
Dot1q termination Adds one tag. Replaces the tag with the tag
sub-interface that is encapsulated on the
outbound interface.
QinQ termination Adds the outer tag. Replaces the outer tag with
sub-interface (in the tag that is encapsulated
symmetric mode) on the outbound interface.
QinQ termination Adds double tags. Removes the outer tag and
sub-interface (in then adds two tags that are
asymmetric mode) encapsulated
5. Run:
type interface-number.subnumber } pe-vid pe-vid ce-vid ce-vid outward
An outward-facing MEP is created on the sub-interface for QinQ VLAN tag

termination of the AC interface bound to the L2VC on the PE.
6. Run:

7. Run:

8. Run:
remote-mep ccm-receive [ mep-idmep-id ] enable
l For detailed configurations of the switch, refer to the related configuration guide of the
switch.
----End
8.13.4 Configuring Ethernet CFM on the Switch and Remote PE

Run Ethernet CFM between the switch and remote PE to check connectivity by exchanging
CCMs. In addition, MAC ping and MAC trace can be performed.
Context
The detailed configuration is similar to that in 8.13.3 Configuring Ethernet CFM on the Switch
and Local PE, and is not mentioned here.

NOTE
l The MA configured on the remote PE must be associated with an L2VC, and the type of the MEP must
be inward-facing.
l For detailed configurations of the switch, refer to the related configuration guide of the switch.
For the rule for creating the MIP, see 8.6.9 (Optional) Setting the Rule for Creating a MIP.

After Ethernet CFM is associated with VLL by using sub-interfaces for QinQ VLAN tag
termination, you can view information about the MEPs and REMPs in the specified MD and
MA, and the CFM status of different MAs.
Prerequisite
The configurations of associating Ethernet CFM and VLL by using sub-interfaces for QinQ
VLAN tag termination are complete.
Procedure
l Run the display cfm md [ md-name ] command to view detailed information about the
MD.
l Run the display cfm ma [ md md-name [ ma ma-name ] ] command to view detailed
information about the MA.
to view detailed information about the MEP.
command to view detailed information about the RMEP.
to view the rule for creating the MIP.
command to view information about the MIP.
NOTE
You can run the display mip create-type and display cfm mip commands to view detailed
information about a MIP only after the MIP is created.
----End
Example
In the IEEE Standard 802.1g-2007, run the display cfm md command. If the MD name, MD
name format, MD level, MIP generation rule, and type of the Sender ID TLV are displayed, it
means that the MD is created successfully.
MD Name : mdcustomer
Level : 2
MA list :
MA Name : mdcustomer1
Interval : 1000

Vlan ID : --
L2VC ID : 11
Run the display cfm macommand. If information about the MA is displayed, it means that the
configuration succeeds.
<HUAWEI> display cfm ma md mdcustomer
The total number of MAs is : 1
--------------------------------------------------
Level : 4
Interval : 1000
Priority : 6
Vlan ID : --
VSI Name : vsi1
L2VC ID : 11
MEP Number : 1
RMEP Number : 1
the configuration succeeds.
The total number of MEPs is : 1
--------------------------------------------------
Level : 4
MEP ID : 4
Vlan ID : --
L2VC ID : 11
Interface Name : GigabitEthernet1/0/2.1
CCM Send : enabled
Direction : inward
MAC Address : 0018-82a0-23a7
means that the configuration succeeds.
The status of RMEPS : 1 up, 0 down
--------------------------------------------------
Level : 4
RMEP ID : 3
Vlan ID : --
L2VC ID : 11
MAC : 0018-82aa-12ed
CFM Status : up

8.14 Associating Ethernet CFM with VPLS (by Using Sub-

interfaces for QinQ VLAN Tag Termination)
In the scenario where PEs that send packets with double VLAN tags access a Virtual Private
LAN Service (VPLS) network, you can configure sub-interfaces for QinQ VLAN tag
termination on AC interfaces of the PEs to bind VSIs and then configure Ethernet CFM on the
PEs.

Before associating Ethernet CFM with VPLS, you must check whether packets received on PEs
carry one VLAN tag or double VLAN tags. If PEs receive packets with one VLAN tag, PEs can
access a VPLS network through common sub-interfaces. If PEs receive packets with double
VLAN tags, you must bind sub-interfaces for QinQ VLAN tag termination to VSIs. The
following describes the configuration in the scenario where PEs receive packets with double
VLAN tags.
As shown in Figure 8-14, MAs are configured between:
l PEs
l Switches and local PEs
l Switches and remote PEs
l Switches
MEPs within the same MA can detect the connectivity between themselves by exchanging
CCMs. Once a connectivity fault is detected, you can perform the MAC ping or MAC trace
operation to further locate the fault.
Figure 8-14 Networking diagram of associating Ethernet CFM with VPLS
CE1 Switch1 PE1 PE2 Switch2 CE2
VPLS
user user
network1 network2
802.1ag
802.1ag 802.1ag
802.1ag
802.1ag
MEP
MIP

PE1 and PE2 are connected through a VPLS network. PEs receive packets with double VLAN
tags. To check connectivity between PEs, you need to configure sub-interfaces for QinQ VLAN
tag termination on AC interfaces of PEs to bind VSIs and then configure Ethernet CFM on PEs.
Before associating Ethernet CFM with VPLS by using sub-interfaces for QinQ VLAN tag
termination, complete the following tasks:
l Configuring a Martini VPLS network
For details, refer to the chapter "VPLS Configuration" in the HUAWEI NetEngine80E/
40E Router Configuration Guide - VPN.
l Configuring sub-interfaces for QinQ VLAN tag termination to access the VPLS network
For details, refer to the chapter "QinQ Configuration" in the HUAWEI NetEngine80E/
40E Router Configuration Guide - LAN Access and MAN Access.
l 8.6 Configuring Basic Ethernet CFM
Data Preparation
To associate Ethernet CFM with VPLS by using sub-interfaces for QinQ VLAN tag termination,
you need the following data.
No. Data
1 Name and ID of a VSI
2 Name of an interface to which a VSI is bound
3 Names of MDs and MAs
4 ID of an MEP, name of the interface on which the MEP resides, and type of the MEP
6 Interval for MEPs sending CCMs in an MA
8.14.2 Configuring Ethernet CFM on PEs on a VPLS

Context
NOTE
l If 802.1ag MAC trace needs to be implemented to locate the connectivity fault between the PEs, you
cannot specify the outbound interface for sending trace packets.
l The current MA must be associated with a VSI and the type of the MEP must be inward-facing.
Procedure
Step 1 Run:
system-view


Step 2 Run:

Step 3 Run:
ma ma-name

Step 4 Run:
map vsi vsi-name

Step 5 Run:
interface-number.subnumber } pe-vid pe-vid ce-vid ce-vid inward
An inward-facing MEP is created.

Step 6 Run:

Step 7 Run:
The MEPs are enabled to send CCMs.

Step 8 Run:
The local MEP is enabled to receive CCMs from the RMEP within the same MA.
----End
8.14.3 Configuring Ethernet CFM on the Switch and Local PE

Run Ethernet CFM between the switch and local PE to check connectivity by exchanging CCMs.
Procedure
l Do as follows on the PE:
NOTE
The MA configured on the PE must be associated with a VSI, and the type of the MEP must be
outward-facing.
1. Run:
system-view

2. Run:

3. Run:
ma ma-name

4. Run:
map vsi vsi-name

5. Run:
type interface-number.subnumber } pe-vid pe-vid ce-vid ce-vid outward
An outward-facing MEP is created on the sub-interface for QinQ VLAN tag

termination of the AC interface bound to the VSI on the PE.
6. Run:

7. Run:

8. Run:
l For detailed configurations of the switch, refer to the related configuration guide of the
switch.
----End
8.14.4 Configuring Ethernet CFM on the Switch and Remote PE

Run Ethernet CFM between the switch and remote PE to check connectivity by exchanging
CCMs. In addition, MAC ping and MAC trace can be performed.
Context
The detailed configuration is similar to that in 8.13.3 Configuring Ethernet CFM on the Switch
and Local PE, and is not mentioned here.
NOTE
l The MA configured on the remote PE must be associated with a VSI, and the type of the MEP must
be inward-facing.
l For detailed configurations of the switch, refer to the related configuration guide of the switch.
For the rule for creating the MIP, see 8.6.9 (Optional) Setting the Rule for Creating a MIP.

After Ethernet CFM is associated with VPLS by using sub-interfaces for QinQ VLAN tag
termination, you can view information about the MEPs and REMPs in the specified MD and
MA, and the CFM status of different MAs.

Prerequisite
The configurations of associating Ethernet CFM and VPLS by using sub-interfaces for QinQ
VLAN tag termination are complete.
Procedure
l Run the display cfm md [ md-name ] command to view detailed information about the
MD.
l Run the display cfm ma [ md md-name [ ma ma-name ] ] command to view detailed
information about the MA.
to view detailed information about the MEP.
command to view detailed information about the RMEP.
to view the rule for creating the MIP.
command to view information about the MIP.
NOTE
You can run the display mip create-type and display cfm mip commands to view detailed
information about a MIP only after the MIP is created.
----End
Example
In the IEEE Standard 802.1g-2007, run the display cfm md command. If the MD name, MD
name format, MD level, MIP generation rule, and type of the Sender ID TLV are displayed, it
means that the MD is created successfully.
Level : 2
MA list :
Interval : 1000
Vlan ID : --
VSI Name : vsi1
Run the display cfm ma command. If information about the MA is displayed, it means that the
configuration succeeds.
<HUAWEI> display cfm ma md mdcustomer
The total number of MAs is : 1
--------------------------------------------------
Level : 4
Interval : 1000
Priority : 6

Vlan ID : --
VSI Name : vsi1
L2VC ID : --
MEP Number : 1
RMEP Number : 1
the configuration succeeds.
--------------------------------------------------
Level : 4
MEP ID : 4
Vlan ID : --
VSI Name : vsi1
CCM Send : enabled
Direction : inward
MD Name : four
Level : 2
MA Name : four
MEP ID : 7
Vlan ID : --
VSI Name : vsi1
CCM Send : enabled
Direction : outward
means that the configuration succeeds.
--------------------------------------------------
Level : 4
RMEP ID : 3
Vlan ID : --
VSI Name : vsi1
MAC : 0018-82aa-12ed
CFM Status : down
MD Name : four
Level : 2
MA Name : four
RMEP ID : 8
Vlan ID : --
VSI Name : vsi1
MAC : 0018-828a-f7c4
CFM Status : up

8.15 Associating Ethernet OAM with MPLS OAM or BFD

By associating Ethernet OAM with MPLS OAM or BFD, you can implement the fault
notification.

Before associating Ethernet OAM with MPLS OAM or BFD, familiarize yourself with the
As shown in Figure 8-15, CEs access PEs in dual-homing mode. PEs communicate through the
MPLS network. To implement the end-to-end link detection, you can configure MPLS OAM or
BFD on the MPLS Label Switch Path (LSP) or Virtual Leased Line (VLL) between PEs. Ethernet
OAM runs between CEs and PEs. When detecting faults, MPLS OAM or BFD at the core side
notifies Ethernet OAM of the faults through PEs and the traffic is switched to the backup path
between CEs.
Figure 8-15 Diagram of associating Ethernet OAM with MPLS OAM or BFD
PE1 PE2
MPLS OAM / BFD

802.3ah 802.3ah
MPLS Core
CE1 CE2
PE3 PE4
Before associating Ethernet OAM with MPLS OAM or BFD, complete the following tasks:
l Configuring VLL Fast Reroute (FRR) in Martini mode
l Configuring the BFD session
l Configuring MPLS OAM
Data Preparation
To associate Ethernet OAM with MPLS OAM or BFD, you need the following data.
No. Data
1 Numbers of the interfaces to be associated

No. Data
2 Name of an MD and an MA
3 IP addresses of interfaces on each piece of equipment, names of tunnel interfaces,

and tunnel IDs
4 Types of detect packets sent
5 Ingresses and Egresses of the detected LSP and the backward tunnel
6 BFD names
7 Parameters of BFD sessions
8.15.2 Configuring Ethernet OAM Functions

You can configure Ethernet OAM between a CE and a PE to detect connectivity faults in
between.
Context
Configure Ethernet OAM to run between CEs and PEs. For details, see "Configuring EFM
OAM" and "Configuring Ethernet CFM"..
8.15.3 Associating Ethernet OAM with MPLS OAM or BFD

Ethernet OAM and MPLS OAM or BFD can send fault information to each other.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
oam-mgr
The OAM management view is displayed.

l Run:
oam-bind ingress cfm md md-name ma ma-name egress bfd-session bfd-session-id
Ethernet CFM is configured to send fault messages to BFD.

l Run:
oam-bind ingress bfd-session bfd-session-id egress cfm md md-name ma ma-name
BFD is configured to send fault messages to Ethernet CFM.

l Run:
oam-bind cfm md md-name ma ma-name bfd-session bfd-session-id
The bidirectional transmission of fault messages between Ethernet CFM and BFD is
configured.
l Run:
oam-bind ingress efm interface interface-type interface-number egress bfd-
session bfd-session-id
EFM OAM is configured to send fault messages to BFD.

l Run:
oam-bind ingress bfd-session bfd-session-id egress efm interface interface-type
interface-number
BFD is configured to send fault messages to EFM OAM.

l Run:
oam-bind efm interface interface-type interface-number bfd-session bfd-session-
id
The bidirectional transmission of fault messages between EFM OAM and BFD is configured.
l Run:
oam-bind ingress cfm md md-name ma ma-name egress mpls oam interface tunnel
tunnel-number
Ethernet CFM is configured to send fault messages to MPLS OAM.

l Run:
oam-bind ingress mpls oam { lsp-name lsp-name | lsr-id lsr-id tunnel-id tunnel-
id } egress cfm md md-name ma ma-name
MPLS OAM is configured to send fault messages to Ethernet CFM.

l Run:
oam-bind ingress efm interface interface-type interface-number egress mpls oam
interface tunnel tunnel-number
EFM OAM is configured to send fault messages to MPLS OAM.

l Run:
oam-bind ingress mpls oam { lsp-name lsp-name | lsr-id ingress-lsr-id tunnel-id
tunnel-id } egress efm interface interface-type interface-number
MPLS OAM is configured to send fault messages to EFM OAM.
----End

By viewing whether traffic on CEs is switched to a backup path, you can check whether the
Prerequisite
After the preceding configuration, when MPLS OAM or BFD enabled between PE1 and PE2
detects faults, EFM OAM and CFM notify CE1 of the faults and then traffic is switched to the
bypass tunnel for CE1.

8.16 Configuring Ethernet CFM and 1+1 Protection of

Multicast VLANs
Ethernet CFM can be used on working VLANs, detect connectivity faults of VLANs, and trigger
protection switchover, which can implement 1+1 multicast VLAN protection.
Context
For details, refer to the chapter "Layer 2 Multicast Configuration" in the the HUAWEI
NetEngine80E/40E Router Configuration Guide - IP Multicast.
8.17 Maintaining Ethernet OAM

This section describes how to maintain Ethernet OAM. Detailed operations include deleting
CCM statistics, monitoring Ethernet OAM.
8.17.1 Clearing the Statistics on Error CCMs

You are recommended to delete CCM statistics before collecting CCM statistics within a
specified period.
Context
CAUTION
Statistics on Error CCMs cannot be restored after you clear it. So, confirm the action before you
use the command.
Procedure
Step 1 Run the reset reset cfm error-packet receive statistics [ md md-name [ ma ma-name [ remote-
mep mep-id mep-id ] ] ] command in the user view to clear statistics of error CCMs.
----End
8.17.2 Monitoring the Running Status of Ethernet OAM

By monitoring the operation status of Ethernet OAM, you can view information about Ethernet
OAM.
Context
In routine maintenance, you can select to run the following commands in any view To check the
running status of Ethernet OAM.

Procedure
l Run the display oam global configuration command in any view to check the global
configurations of Ethernet OAM on the device.
l Run the display cfm error-packet statistics [ md md-name [ ma ma-name [ remote-mep
mep-id mep-id ] ] ] command in any view to check statistics of error CCMs received on
the device.
in any view to check information about a MEP.
command in any view to check information about a MIP.
l Run the display cfm remote-mep [ md md-name ma ma-name mep-id mep-id | [ md md-
name [ ma ma-name [ mep-id mep-id ] ] ] ] command in any view to check information
about an RMEP.
in any view to check information about the EFM OAM session between the specified
interface and the peer.
----End

Context
NOTE
8.18.1 Example for Configuring EFM OAM

In this example, by configuring EFM OAM on a CE and a UPE, you can detect link connectivity
in between.
NOTE
As shown in Figure 8-16, a user network is connected to an ISP network through Router A and
Router B. Router A acts as the CE device. Router B acts as the Underlayer Provider Edge (UPE)
device. It is required that the following be achieved:
l Automatic connectivity detection can be performed on the link between Router A and
Router B. After detecting connectivity faults, Router A and RouterB generate alarms.

l Router B monitors the errored frames, errored codes, and errored frame seconds on GE
2/0/1. When the number of errored frames, errored codes, and errored frame seconds exceed
the corresponding threshold, Router B generates alarms.
Figure 8-16 Diagram of configuring EFM OAM
RouterA RouterB
User ISP network
network
GE1/0/1 GE2/0/1
1. Enable EFM OAM on Router A and Router B globally.
2. Configure EFM OAM on GE 1/0/1 on Router A to work in passive mode.
3. Configure GE 2/0/1 on Router B to detect the errored frames, errored codes, and errored
frame seconds.
4. Enable EFM OAM on GE 2/0/1 on Router B. Enable EFM OAM on GE 1/0/1 on Router
A.
Data Preparation
l The period for detecting errored frames on GE 2/0/1 on Router B is five seconds and the
threshold is five.
l The period for detecting errored codes on GE 2/0/1 on Router B is five seconds and the
threshold is five.
l The period for detecting errored frame seconds on GE 2/0/1 on Router B is 120 seconds
and the threshold is five.
Procedure
Step 1 Enable EFM OAM globally.
# Enable EFM OAM globally on Router A.
[RouterA] efm enable
# Enable EFM OAM globally on Router B.


[RouterB] efm enable
Step 2 Configure EFM OAM on GE 1/0/1 on Router A to work in passive mode.

[RouterA-GigabitEthernet1/0/1] efm mode passive
Step 3 Configure GE 2/0/1 on Router B to detect the errored frames, errored codes, and errored frame
seconds.
# Configure GE 2/0/1 on Router B to detect the errored frames.
[RouterB-GigabitEthernet2/0/1] efm error-frame period 5
[RouterB-GigabitEthernet2/0/1] efm error-frame threshold 5
[RouterB-GigabitEthernet2/0/1] efm error-frame notification enable
# Configure GE 2/0/1 on Router B to detect the errored codes.

[RouterB-GigabitEthernet2/0/1] efm error-code period 5
[RouterB-GigabitEthernet2/0/1] efm error-code threshold 5
[RouterB-GigabitEthernet2/0/1] efm error-code notification enable
# Configure GE 2/0/1 on Router B to detect the errored frame seconds.

[RouterB-GigabitEthernet2/0/1] efm error-frame-second period 120
[RouterB-GigabitEthernet2/0/1] efm error-frame-second threshold 5
[RouterB-GigabitEthernet2/0/1] efm error-frame-second notification enable
Step 4 Enable EFM OAM on GE 2/0/1 on Router B. Enable EFM OAM on GE 1/0/1 on Router A.
# Enable EFM OAM on GE 1/0/1 on Router A.
[RouterA-GigabitEthernet1/0/1] efm enable
# Enable EFM OAM on GE 2/0/1 on Router B.

[RouterB-GigabitEthernet2/0/1] efm enable

# Run the display efm session command. If the EFM OAM state on the interface is Detect, it
means that the configuration succeeds. EFM OAM is correctly configured on Router A and
Router B, and GE 2/0/1 and GE 1/0/1 succeed in negotiation and enter the Detect state. For
example, the EFM OAM state on GE 2/0/1 on RouterB is displayed as follows:
[RouterB] display efm session interface gigabitethernet 2/0/1
--------------------------------------------------------------------
# Run the display efm command. If the EFM OAM configuration information on GE 2/0/1 on
Router B is displayed, it means that the configuration succeeds. The displayed information is as
follows:
[RouterB] display efm interface gigabitethernet 2/0/1
Item Value
-------------------------------------
Mode: active
OAMPDU MaxSize: 128
ErrCodeNotification: enable
ErrCodePeriod: 5
ErrCodeThreshold: 5

ErrFrameNotification: enable
ErrFramePeriod: 5
ErrFrameSecondNotification: enable
Hold Up Time: 0
ThresholdEvtTriggerErrDown: disable
Remote MAC: 0010-0010-0010
Remote MaxSize: 128
Remote State: --
----End
Configuration Files
#
sysname RouterA
#
efm enable
#
efm mode passive
efm enable
#
return

#
sysname RouterB
#
efm enable
#
efm enable
efm error-frame period 5
efm error-frame threshold 5
efm error-frame notification enable
efm error-frame-second period 120
efm error-frame-second threshold 5
efm error-frame-second notification enable
efm error-code period 5
efm error-code threshold 5
efm error-code notification enable
#
return
8.18.2 Example for Testing the Packet Loss Ratio on the Link
In this example, by configuring EFM OAM on a CE and a UPE, you can calculate the packet
loss ratio on a physical link and then take effective measures to ensure better performance of
the link.
Router B. Router A acts as the CE device. Router B acts as the UPE device. The link between
Router A and Router B is newly established. The ISP needs to test the packet loss ratio on the
link on Router B before using the link.

Figure 8-17 Diagram of testing the packet loss ratio on the link
RouterA RouterB
User ISP network
network
GE1/0/1 GE2/0/1
1. Enable EFM OAM on Router A and Router B. Configure EFM OAM on GE 1/0/1 on Router
A to work in passive mode.
2. Enable EFM OAM remote loopback on Router B.
3. Send test packets from RouterB to Router A.
4. Check the returning of test packets on Router B.
Data Preparation
l Timeout period for remote loopback
l Size, number, and sending rate of test packets
Procedure
Step 1 Configure EFM OAM.
# Enable EFM OAM globally on Router B.
# Enable EFM OAM globally on Router A.

# Configure EFM OAM on GE 1/0/1 on Router A to work in passive mode.

# Enable EFM OAM on GE 1/0/1 on Router A.

# Enable EFM OAM on GE 2/0/1 on Router B.


# Verify the configuration.

Run the display efm session command. If the EFM OAM protocol on the interface is in the
Detect state, it means that the configuration succeeds. EFM OAM is correctly configured on
Router A and Router B, and GE 2/0/1 and GE 1/0/1 succeed in negotiation and enter the Detect
state. For example, the EFM OAM state on GE 2/0/1 on Router B is displayed as follows:
[RouterB] display efm session interface gigabitethernet 2/0/1
--------------------------------------------------------------------
Step 2 Configure EFM OAM remote loopback.

# Enable remote loopback on Router B.
[RouterB-GigabitEthernet2/0/1] efm loopback start

Run the display efm session command on Router B. If the EFM OAM protocol on GE 2/0/1 is
in the loopback (control) state, that is, GE 2/0/1 initiates remote loopback, it means that the
configuration succeeds. The displayed information is as follows:
[RouterB] display efm session interface gigabitethernet2/0/1
----------------------------------------------------------------------
GigabitEthernet2/0/1 Loopback(control) 20
Run the display efm session command on Router A. If the EFM OAM protocol on GE 1/0/1 is
in the loopback (be controlled) state, that is, GE 1/0/1 responds to remote loopback, it means
that the configuration succeeds. The displayed information is as follows:
[RouterA] display efm session interface gigabitethernet1/0/1
----------------------------------------------------------------------
GigabitEthernet1/0/1 Loopback(be controlled) --
Run the display efm session command on RouterB. If the Loopback IgnoreRequest is no, that
is the GE1/0/1 responds to the remote loopback. The displayed information is as follows:
Item Value
----------------------------------------------------
Mode: active
OAMPDU MaxSize: 128

ErrCodePeriod: 1
ErrCodeThreshold: 1
ErrFramePeriod: 1
Hold Up Time: 0
ThresholdEvtTriggerErrDown: --

Remote MAC: 00e0-c97e-a500
Remote Mode: active
Remote MaxSize: 128
Remote State: --
Step 3 Send test packets from Router B to Router A.

[RouterB] test-packet start interface gigabitethernet 2/0/1
please waiting..
Info: The test is complete.
Step 4 Check the receiving of test packets on Router B.

[RouterB] display test-packet result
TestResult Value
--------------------------------------------------------
PacketsSend : 5
PacketsReceive : 5
PacketsLost : 0
BytesSend : 320
BytesReceive : 320
BytesLost : 0
StartTime : 07-06-2007 09:41:41
EndTime : 07-06-2007 09:41:41
You can obtain the packet loss ratio on the link based on the preceding data.
Step 5 Disable EFM OAM remote loopback.
# Disable EFM OAM remote loopback on Router B.
[RouterB-GigabitEthernet2/0/1] efm loopback stop
NOTE
By default, the timeout period for remote loopback is 20 minutes. After 20 minutes, remote loopback stops.
To disable remote loopback, you can perform the preceding steps.

Run the display efm session command after remote loopback is automatically or manually
disabled, you can view that the status of the EFM OAM protocol on the interface is no longer
loopback (control) or loopback (be controlled). For example, the EFM OAM status on GE 2/0/1
on RouterB is displayed as follows:
----------------------------------------------------------------------
----End
Configuration Files
#
sysname RouterA
#
efm enable
#
efm mode passive

efm enable
#
return

#
sysname RouterB
#
efm enable
#
efm enable
#
return
8.18.3 Example for Configuring Ethernet CFM

In this example, by configuring basic Ethernet CFM, you can implement end-to-end connectivity
fault detection.
The Ethernet shown in Figure 8-18 is managed by two ISPs. ISP 1 manages Router A, Router
B, and Router D. ISP 2 manages Router C, Router E, Router F, Router G, Router H, and Router
I. It is required that connectivity detection be implemented on the network.
Figure 8-18 Diagram of configuring Ethernet CFM
VLAN2
GE1/0/1
VLAN2
RouterA RouterE
GE1/0/0
RouterI GE1/0/1
GE1/0/0
GE1/0/2 RouterB RouterF
MD2
GE1/0/1 GE1/0/1
GE1/0/0
RouterD
GE1/0/0 RouterC GE1/0/2
RouterH MD1 RouterG
GE1/0/1 GE1/0/0
GE1/0/2
VLAN2 VLAN3
VLAN3
MD1 MD2
MEP of MA1 MEP of MA3
MEP of MA2

1. Create VLANs and add interfaces to the corresponding VLAN.
2. Create MD 1 at level 6 on all the routers.
3. Create MA 1 within MD 1 on all the routers except Router G. Associate MA 1 with VLAN
2.
4. Create MA 2 within MD 1 on all the routers except Router E and Router I. Associate MA
2 with VLAN 3.
5. Create MD 2 at level 4 on Router A, Router B, Router C, and Router D. Create MA 3 within
MD 2. Associate MA 3 with VLAN 4.
6. Create MEPs and RMEPs on Router I, Router H, and Router E in MA 1 within MD 1.
7. Create MEPs and RMEPs on Router H and Router G in MA 2 within MD 1.
8. Create MEPs and RMEPs on Router A, Router C, and Router D in MA 3 within MD 2.
9. Enable the sending and receiving of CCMs.
Data Preparation
l MD 1 at level 6
l MD 2 at level 4
Procedure
Step 1 Create VLANs and add interfaces to the corresponding VLAN. The detailed configuration is
not mentioned here.
Step 2 Create MD 1.
# Create MD 1 on Router A.
[RouterA] cfm enable
Info: Operation succeeded.
[RouterA] cfm md md1 level 6
# Create MD 1 on Router B, Router C, Router D, Router E, Router F, Router G, Router H, and

Router I.
The detailed configuration is not mentioned here. The configuration is similar to that on Router
A.
Step 3 Create and configure MA 1 within MD 1 on all the device except Router G.
# Create and configure MA 1 on Router A within MD 1.
[RouterA-md-md1] ma ma1
[RouterA-md-md1-ma-ma1] map vlan 2
[RouterA-md-md1-ma-ma1] quit
# Create and configure MA 1 on Router B, Router C, Router D, Router E, Router F, Router H,

and Router I within MD 1.

A.
Step 4 Create and configure MA 2 within MD 1 on all the device except Router E and Router I.
# Create and configure MA 2 on Router A within MD 1.
[RouterA-md-md1] quit
# Create and configure MA 2 on Router B, Router C, Router D, Router F, Router G, and Router
H within MD 1.
A.
Step 5 Create MD 2 on Router A, Router B, Router C, and Router D. Create and configure MA 3 within
MD 2.
# Create MD 2 on Router A. Create and configure MA 3 within MD 2.
# Create MD 2 on Router B, Router C, and RouterD. Create and configure MA 3 within MD 2.

A.
Step 6 Configure MEPs and RMEPs on Router E, Router H, and Router I in MA 1 within MD 1.
# Configure a MEP on Router E in MA 1 within MD 1.
[RouterE] cfm md md1
[RouterE-md-md1] ma ma1
[RouterE-md-md1-ma-ma1] mep mep-id 3 interface gigabitethernet 1/0/1 inward
# Configure a MEP on RouterH in MA 1 within MD 1.

[RouterH] cfm md md1
[RouterH-md-md1] ma ma1
[RouterH-md-md1-ma-ma1] mep mep-id 2 interface gigabitethernet 1/0/2 inward
# Configure a MEP on RouterI in MA 1 within MD 1.

[RouterI] cfm md md1
[RouterI-md-md1] ma ma1
[RouterI-md-md1-ma-ma1] mep mep-id 1 interface gigabitethernet 1/0/1 inward
# Configure an RMEP on RouterE in MA 1 within MD 1.

[RouterE-md-md1-ma-ma1] remote-mep mep-id 1
# Configure an RMEP on RouterH in MA 1 within MD 1.

[RouterH-md-md1-ma-ma1] remote-mep mep-id 1
# Configure an RMEP on RouterI in MA 1 within MD 1.

[RouterI-md-md1-ma-ma1] remote-mep mep-id 2

[RouterI-md-md1-ma-ma1] remote-mep mep-id 3
Step 7 Configure MEPs and RMEPs on Router H and Router G in MA 2 within MD 1.
# Configure a MEP on Router H in MA 2 within MD 1.

[RouterH] cfm md md1
[RouterH-md-md1] ma ma2
[RouterH-md-md1-ma-ma2] mep mep-id 1 interface gigabitethernet 1/0/1 inward
# Configure a MEP on Router G in MA 2 within MD 1.

[RouterG] cfm md md1
[RouterG-md-md1] ma ma2
[RouterG-md-md1-ma-ma2] mep mep-id 2 interface gigabitethernet 1/0/0 inward
# Configure an RMEP on Router H in MA 2 within MD 1.

# Configure an RMEP on Router G in MA 2 within MD 1.

[RouterG-md-md1-ma-ma2] remote-mep mep-id 1
Step 8 Configure MEPs and RMEPs on Router A, Router C, and Router D in MA 3 within MD 2.
# Configure a MEP on Router A in MA 3 within MD 2.

[RouterA] cfm md md2
[RouterA-md-md2-ma-ma3] mep mep-id 1 interface gigabitethernet 1/0/0 inward
# Configure a MEP on Router C in MA 3 within MD 2.

[RouterC] cfm md md2
[RouterC-md-md2] ma ma3
[RouterC-md-md2-ma-ma3] mep mep-id 2 interface gigabitethernet 1/0/1 outward
# Configure a MEP on Router D in MA 3 within MD 2.

[RouterD] cfm md md2
[RouterD-md-md2] ma ma3
[RouterD-md-md2-ma-ma3] mep mep-id 3 interface gigabitethernet 1/0/0 inward
# Configure an RMEP on Router A in MA 3 within MD 2.

[RouterA-md-md2-ma-ma3] remote-mep mep-id 2
# Configure an RMEP on Router C in MA 3 within MD 2.

[RouterC-md-md2-ma-ma3] remote-mep mep-id 1
# Configure an RMEP on Router D in MA 3 within MD 2.

[RouterD-md-md2-ma-ma3] remote-mep mep-id 1
[RouterD-md-md2-ma-ma3] remote-mep mep-id 2
Step 9 Enable the sending and receiving of CCMs.
# Enable the sending of CCMs on the MEP on Router A.

[RouterA-md-md2-ma-ma3] mep ccm-send enable
# Enable the receiving of CCMs from the RMEP on Router A.

[RouterA-md-md2-ma-ma3] remote-mep ccm-receive enable

# Enable the sending of CCMs on MEPs and the receiving of CCMs from RMEPs on Router B,
Router C, Router D, Router E, Router F, Router G, Router H, and Router I.
A.
----End
Configuration Files
#
sysname RouterA
#
vlan batch 2 to 4
#
cfm enable
#
portswitch
port trunk allow-pass vlan 2 to 4
#
portswitch
#
portswitch
#
cfm md md1 level 6
ma ma1
map vlan 2
ma ma2
map vlan 3
#
cfm md md2 level 4
ma ma3
map vlan 4
mep mep-id 1 interface gigabitethernet 1/0/0 inward
mep ccm-send mep-id 1 enable
remote-mep mep-id 2
remote-mep ccm-receive mep-id 2 enable
remote-mep mep-id 3
#
return

#
sysname RouterB
#
vlan batch 2 to 4
#
cfm enable
#
portswitch
#
portswitch
#
cfm md md1 level 6
ma ma1
map vlan 2

ma ma2
map vlan 3
#
cfm md md2 level 4
ma ma3
map vlan 4
#
return
#
sysname RouterC
#
vlan batch 2 to 4
#
cfm enable
#
portswitch
#
portswitch
#
cfm md md1 level 6
ma ma1
map vlan 2
ma ma2
map vlan 3
#
cfm md md2 level 4
ma ma3
map vlan 4
mep mep-id 2 interface gigabitethernet 1/0/0 outward
remote-mep mep-id 1
remote-mep mep-id 3
#
return
l Configuration file of Router D
#
sysname RouterD
#
vlan batch 2 to 4
#
cfm enable
#
portswitch
#
portswitch
#
cfm md md1 level 6
ma ma1
map vlan 2
ma ma2
map vlan 3
#
cfm md md2 level 4
ma ma3
map vlan 4

remote-mep mep-id 1
remote-mep mep-id 2
#
return
l Configuration file of Router E
#
sysname RouterE
#
vlan batch 2
#
cfm enable
#
portswitch
#
portswitch
#
cfm md md1 level 6
ma ma1
map vlan 2
remote-mep mep-id 1
remote-mep mep-id 2
#
return
l Configuration file of Router F
#
sysname RouterF
#
vlan batch 2 to 3
#
cfm enable
#
portswitch
#
portswitch
#
portswitch
#
cfm md md1 level 6
ma ma1
map vlan 2
ma ma2
map vlan 3
#
return
l Configuration file of Router G
#
sysname RouterG
#
vlan batch 3
#
cfm enable

#
portswitch
#
portswitch
#
cfm md md1 level 6
ma ma2
map vlan 3
remote-mep mep-id 1
#
return
l Configuration file of Router H
#
sysname RouterH
#
vlan batch 2 to 3
#
cfm enable
#
portswitch
#
portswitch
#
portswitch
#
cfm md md1 level 6
ma ma1
map vlan 2
remote-mep mep-id 1
remote-mep mep-id 3
ma ma2
map vlan 3
remote-mep mep-id 2
#
return
l Configuration file of Router I
#
sysname RouterI
#
vlan batch 2
#
cfm enable
#
portswitch
#

portswitch
#
cfm md md1 level 6
ma ma1
map vlan 2
remote-mep mep-id 2
remote-mep mep-id 3
#
return
8.18.4 Example for Configuring the Default MD for Ethernet CFM

In this example, you can configure the default MD on a device on which a lower-level MD
resides so that the higher-level MD can detect the topology change of the lower-level MD.
As shown in Figure 8-19, Router B and Router C are managed by ISP1, and Router A, Router
D, Router E, and Router F are managed by ISP2. To enable the CFM function, you can configure
the default MD on the device configured with an MD of a low level.
Figure 8-19 Networking diagram of configuring the default MD for Ethernet CFM
VLAN3
VLAN2 RouterC RouterE GE1/0/2

RouterB
G
E1
1
/0
0/
/0/1
GE1 /2
1/
GE1/0/3
GE
RouterF
GE1/0/1
RouterA RouterD GE1/0/3

GE1/0/2
GE1/0/1
VLAN3
VLAN2
MEP of MA1
MEP of MA2
MIP

1. Switch IEEE 802.1ag Draft 7 to IEEE Standard 802.1ag-2007.

2. Create a VLAN and add related interfaces to the VLAN.
3. Create MD1 at Level 6 on all the devices except for Router B and Router C.
Create MD2 at Level 4 on Router B and Router C.
4. Create the default MD at Level 6 on Router B and Router C, associate the default MD with
VLAN 2 and VLAN 3, and set the MIP generation rule to default.
5. Create and configure MA1 within MD1 on all the devices except for Router B and
Router C. (MA1 is associated with VLAN 2.)
Create and configure MA2 within MD1 on all the devices except for Router B and
Router C.. (MA2 is associated with VLAN 3.)
6. Create and configure MEPs and RMEPs on MA1 in MD1 of Router A and Router F.
Create and configure MEPs and RMEPs in MA2 within MD1 of Router A and Router E.
7. Enable the CCM transmission function.
Data Preparation
l Range of VLAN IDs to which interfaces belong
l MD1 at Level 6
l MD2 at Level 4
l Default MD at Level 6
Procedure
Step 1 Switch the IEEE 802.1ag version.
NOTE
By default, IEEE 802.1ag Draft 7 is enabled on the device.
# Switch IEEE 802.1ag Draft 7 to IEEE Standard 802.1ag-2007 on Router A.

[RouterA] cfm version standard
Warning: Warning:CFM will be disabled before the version of CFM is changed, and
all information about the MD will be deleted . Continue?[Y/N]:y
Info: Succeeded in changing the version of CFM.
# Switch IEEE 802.1ag Draft 7 to IEEE Standard 802.1ag-2007 on Router B, Router C,

Router D, Router E, and Router F.
The configurations on Router B, Router C, Router D, Router E, and Router F are the same as
the configurations on Router A, and are not mentioned here.
NOTE
All the devices on the network must be enabled with either IEEE 802.1ag Draft 7 or IEEE Standard
802.1ag-2007. IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007 cannot be enabled at the same time
on a network.
Step 2 Create a VLAN and add related interfaces to the VLAN. The configuration is not mentioned
here.
Step 3 Create MD1.
# Create MD1 on Router A.

Info: Enable the CFM successfully!
[RouterA] quit
# Create MD1 on Router D, Router E, and Router F.
The configurations on Router D, Router E, and Router F are the same as the configurations on
Router A, and are not mentioned here.
Step 4 Create MD2.
# Create MD2 on Router B.

[RouterB] cfm enable
Info: Enable the CFM successfully!
[RouterB] cfm md md2 level 4
[RouterB] quit
# Create MD2 on Router C.
The configurations on Router C are the same as the configurations on Router B, and are not
mentioned here.
Step 5 Create the default MD and associate the default MD with VLAN 2 and VLAN 3 on Router B
and Router C.
# Create the default MD and associate the default MD to VLAN 2 and VLAN 3 on Router C.
[RouterB] cfm default md level 6
[RouterB-default-md] vlan 2 to 3
[Router B-default-md] quit
Create the default MD and associate the default MD to VLAN 2 and VLAN 3 on Router C.
mentioned here.
Step 6 Set the MIP generation rule in the default MD on Router B and Router C.
# Set the MIP generation rule in the default MD on Router B.

[RouterB] cfm default md
[RouterB-default-md] mip create-type default
[RouterB-default-md] quit
# Set the MIP generation rule in the default MD on Router C.
mentioned here.
Step 7 Create and configure MA1 within MD1 on all the devices except for Router B and Router C.
# Create MA1 within MD1 on Router A.

# Create MA1 within MD1 on Router D and Router F.

The configurations on Router D and Router F are the same as the configurations on Router A,
and are not mentioned here.
Step 8 Create and configure MA2 within MD1 on all the devices except for Router B and Router C.
# Create MA2 within MD1 on Router A.
# Create MA2 within MD1 on Router D and Router E.

The configurations on Router D and Router E are the same as the configurations on Router A,
Step 9 Create and configure MEPs and RMEPs in MA1 within MD1 on Router A and Router F.
# Create and configure a MEP in MA1 within MD1 on Router A.
# Create and configure a MEP in MA1 within MD1 on Router F.

[RouterF] cfm md md1
[RouterF-md-md1] ma ma1
[RouterF-md-md1-ma-ma1] mep mep-id 1 interface gigabitethernet 1/0/1 inward
# Create and configure an RMEP in MA1 within MD1 on Router A.

# Create and configure an RMEP in MA1 within MD1 on RouterF.

[RouterF-md-md1-ma-ma1] remote-mep mep-id 2
Step 10 Create and configure MEPs and RMEPs in MA2 within MD1 on Router A and Router E.
# Create and configure a MEP in MA2 within MD1 on Router A.
# Create and configure a MEP in MA2 within MD1 on Router E.

[RouterE] cfm md md1
[RouterE-md-md1] ma ma2
[RouterE-md-md1-ma-ma2] mep mep-id 2 interface gigabitethernet 1/0/2 inward
# Create and configure an RMEP in MA2 within MD1 on Router A.

# Create and configure an RMEP in MA2 within MD1 on Router E.

Step 11 Enable the CCM transmission function.

# Enable the function of sending CCMs on all MEPs of Router A.
# Enable Router A with the function of receiving CCMs from the RMEP.

# Enable the function of sending CCMs on all MEPs of Router E and Router F, and enable the
function of receiving CCMs from all RMEPs on Router E and Router F.
The configurations on Router E and Router F are the same as the configurations on Router A,
After the preceding configurations are successful and the network converges, run the following
commands to verify the configuration. Take the display on Router B and Router A as an example:
l Run the display cfm default md command on Router B. You can view that the default MD
at Level 6 is configured and associated with VLAN 2 and VLAN 3. You can also view that
the MIP generation rule is set to default.
[RouterB] display cfm default md
Level MIP Create-type SenderID TLV-type VLAN List
-------------------------------------------------------------------------------
---------
6 default Defer 2 to 3
l Perform the 802.1ag MAC trace operation on Router A. You can view that the 802.1ag MAC
trace operation is successful and no connectivity fault occurs between Router A and
Router E
<RouterA> system
[RouterA--md-md1-ma-ma1] trace mac-8021ag mac aa99-6600-5600
Tracing the route to aa99-6600-5600 over a maximum of 255 hops:
Hops Mac Ingress Ingress Action
Relay Action
Forwarded Egress Egress Action
Ismep
1 2155-2201-3302 gigabitethernet1/0/3 IngOK
RlyFDB
Forwarded gigabitethernet1/0/1 EgrOK No
RlyFDB
Forwarded gigabitethernet1/0/2 EgrOk No
RlyFDB
RlyFDB
5 aa99-6600-5600 gigabitethernet1/0/1 IngOK
RlyHit
Not Forwarded
Yes
Info: Succeed in tracing the destination address aa99-6600-5600.
----End
Configuration Files
#
sysname RouterA
#
vlan batch 2 to 3
#
cfm version standard
cfm enable
#

undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
cfm md md1 level 6
ma ma1
map vlan 2
remote-mep mep-id 1
ma ma2
map vlan 3
remote-mep mep-id 2
#
return
#
sysname RouterB
#
vlan batch 2 to 3
#
cfm enable
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
cfm md md2 level 4
#
cfm default md level 6
mip create-type defaul
vlan 2 to 3
#
return
#
sysname RouterC
#
vlan batch 2 to 3
#
cfm enable
#
undo shutdown
portswitch


#
undo shutdown
portswitch
#
cfm md md2 level 4
#
cfm default md level 6
mip create-type defaul
vlan 2 to 3
#
return
#
sysname RouterD
#
vlan batch 2 to 3
#
cfm enable
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
cfm md md1 level 6
ma ma1
map vlan 2
ma ma2
map vlan 3
#
return
l Configuration file of Router E
#
sysname RouterE
#
vlan batch 3
#
cfm enable
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
cfm md md1 level 6
ma ma2
map vlan 3


remote-mep mep-id 1
#
return
l Configuration file of Router F

#
sysname RouterF
#
vlan batch 2
#
cfm enable
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
cfm md md1 level 6
ma ma1
map vlan 2
remote-mep mep-id 2
#
return
8.18.5 Example for Associating Ethernet CFM with an Interface

In this example, by associating Ethernet CFM with an interface, you can detect a fault on the
link between a CE and a UPE through LACP.
Router B. Router A acts as the CE device. Router B acts as the UPE device. It is required that
the following be achieved:
l The bandwidth for the user network to access the ISP network is 2000 Mbit/s and an inactive
link that serves as a backup is provided.
l When the active link between the user network and the ISP network fails, the LACP module
on the interface can sense the fault within 50 ms and stop forwarding data on the active
link.

Figure 8-20 Diagram of associating Ethernet CFM with an interface
ISP network
RouterB
GE1/0/3
GE1/0/1
GE1/0/2
GE1/0/2
GE1/0/1 GE1/0/3
RouterA
User
network 1
Active link
Inactive link
Link aggregation group in
static LACP mode
1. Configure the link aggregation group with three member interfaces on Router A and Router
B respectively. The three member interfaces are all GE interfaces.
2. Configure Ethernet CFM on Router A and Router B. To allow the LACP module to sense
the connectivity fault within 50 ms, set the interval for sending and detecting CCMs to 10
ms within each MA.
3. Associate Ethernet CFM with all the member interfaces of the aggregation groups in static
LACP mode on Router A and Router B.
Data Preparation
l The number of the aggregation groups in static LACP mode on Router A and Router B is
2.
l The three member interfaces of the aggregation group in static LACP mode on Router B
are GE 1/0/1, GE 1/0/2, and GE 1/0/3.
l The three member interfaces of the aggregation group in static LACP mode on Router A
are GE 1/0/1, GE 1/0/2, and GE 1/0/3.

Procedure
Step 1 Configure the aggregation group in static LACP mode.
The detailed configuration is not mentioned here. For details, refer to the HUAWEI
NetEngine80E/40E Router Configuration Guide - LAN Access and MAN Access.
Step 2 Configure Ethernet CFM.
# Enable Ethernet CFM globally on Router A.
# Create the MD, MA, MEP, and RMEP on Router A.

[RouterA-md-md1-ma-ma1] ccm-interval 10
[RouterA-md-md1-ma-ma1] mep mep-id 2 interface gigabitethernet 1/0/1 outward
# Enable Ethernet CFM globally on Router B.

# Create the MD, MA, MEP, and RMEP on Router B.

[RouterB] cfm md md1
[RouterB-md-md1] ma ma1
[RouterB-md-md1-ma-ma1] ccm-interval 10
[RouterB-md-md1-ma-ma1] mep mep-id 1 interface gigabitethernet 1/0/1 outward
[RouterB-md-md1-ma-ma1] remote-mep mep-id 2
[RouterB-md-md1-ma-ma1] mep ccm-send enable
[RouterB-md-md1-ma-ma1] remote-mep ccm-receive enable
[RouterB-md-md1-ma-ma1] quit
[RouterB-md-md1] quit
[RouterB] quit


Run the display cfm mep command and the display cfm remote-mep command. If information
about the MEP and RMEP is displayed, it means that the configuration succeeds. For example,
the detailed information on Router B is displayed as follows:
[RouterB] display cfm mep md md1
MD Name : md1
Level : 0
MA Name : ma1
MEP ID : 1
Vlan ID : --
VSI Name : --
CCM Send : enabled
Direction : outward
MD Name : md1
Level : 0
MA Name : ma2
MEP ID : 3
Vlan ID : --
VSI Name : --
CCM Send : enabled
Direction : outward
MD Name : md1
Level : 0
MA Name : ma3
MEP ID : 5
Vlan ID : --
VSI Name : --
CCM Send : enabled
Direction : outward
[RouterB] display cfm remote-mep md md1
--------------------------------------------------
MD Name : md1
Level : 0
MA Name : ma1
RMEP ID : 2
Vlan ID : --
VSI Name : --
MAC : --
CFM Status : up
MD Name : md1
Level : 0
MA Name : ma2
RMEP ID : 4
Vlan ID : --
VSI Name : --
MAC : --
CFM Status : up
MD Name : md1
Level : 0
MA Name : ma3
RMEP ID : 6

Vlan ID : --
VSI Name : --
MAC : --
CFM Status : up
Step 3 Associate Ethernet CFM with the member interfaces of the aggregation group in static LACP
mode.
# Associate Ethernet CFM with the member interfaces of Eth-Trunk 2 on Router A.
[RouterA] interface gigabitethernet1/0/1
[RouterA-GigabitEthernet1/0/1] cfm md md1 ma ma1 remote-mep mep-id 1 trigger if-down
# Associate Ethernet CFM with the member interfaces of Eth-Trunk 2 on Router B.

[RouterB-GigabitEthernet1/0/1] cfm md md1 ma ma1 remote-mep mep-id 2 trigger if-down

Run the display cfm remote-mep command. If the item of "Trigger-If-down" is displayed as
"enable", it means that the configuration succeeds. For example, the detailed information on
Router B is displayed as follows:
[RouterB] display cfm remote-mep md md1
MD Name : md1
Level : 0
MA Name : ma1
RMEP ID : 2
Vlan ID : --
VSI Name : --
MAC : --
Trigger-If-Down : enabled
CFM Status : up
MD Name : md1
Level : 0
MA Name : ma2
RMEP ID : 4
Vlan ID : --
VSI Name : --
MAC : --
CFM Status : up
MD Name : md1
Level : 0
MA Name : ma3
RMEP ID : 6
Vlan ID : --
VSI Name : --
MAC : --


CFM Status : up
----End
Configuration Files
#
sysname RouterA
#
cfm enable
#
portswitch
mode lacp-static
#
eth-trunk 2
cfm md md1 ma ma1 remote-mep mep-id 1 trigger if-down
#
eth-trunk 2
#
eth-trunk 2
#
cfm md md1
ma ma1
ccm-interval 10
mep mep-id 2 interface GigabitEthernet1/0/1 outward
remote-mep mep-id 1
ma ma2
ccm-interval 10
remote-mep mep-id 3
ma ma3
ccm-interval 10
remote-mep mep-id 5
#
return

#
sysname RouterB
#
lacp priority 100
#
cfm enable
#
portswitch
mode lacp-static
max bandwidth-affected-linknumber 2
#
eth-trunk 2
lacp priority 2000


#
eth-trunk 2
lacp priority 2000
#
eth-trunk 2
#
cfm md md1
ma ma1
ccm-interval 10
remote-mep mep-id 2
ma ma2
ccm-interval 10
remote-mep mep-id 4
ma ma3
ccm-interval 10
remote-mep mep-id 6
#
return
8.18.6 Example for Associating EFM OAM with Ethernet CFM

In this example, by configuring EFM OAM and Ethernet CFM, you can implement the fault
notification.
As shown in Figure 8-21, configure EFM OAM to run between Router A and Router B, and
between Router C and Router D; configure Ethernet CFM to run between Router B and Router
C. This implements end-to-end link detection. When a fault occurs on the link between Router
A and Router B, Ethernet CFM is triggered to send alarms of the fault to Router D.When a fault
occurs on the link between Router C and Router D, Ethernet CFM is triggered to send alarms
of the fault to Router A.
Figure 8-21 Diagram of associating EFM OAM with Ethernet CFM

RouterA RouterB RouterC RouterD
GE1/0/0 GE2/0/0 GE1/0/0
GE1/0/0 GE2/0/0 GE1/0/0

GE2/0/0 GE2/0/0
VLAN10 VLAN10

1. Create a VLAN and add interfaces to the VLAN.
2. Configure EFM OAM to run between Router A and Router B.
3. Configure Ethernet CFM to run between Router B and Router C.
4. Configure EFM OAM to run between RouterC and RouterD.
5. Associate EFM OAM with Ethernet CFM on Router B and Router C.
Procedure
Step 1 Create VLAN 10 and add interfaces to VLAN 10.
Step 2 Configure EFM OAM to run between Router A and Router B.
# Configure RouterB.
Step 3 Configure Ethernet CFM to run between Router B and Router C.

[RouterB] cfm md md1
[RouterB-md-md1-ma-ma1] map vlan 10
[RouterB-md-md1-ma-ma1] return
[RouterC] cfm enable
[RouterC] cfm md md1
[RouterC-md-md1] ma ma1
[RouterC-md-md1-ma-ma1] map vlan 10
[RouterC-md-md1-ma-ma1] mep mep-id 2 interface gigabitethernet 2/0/0 outward
[RouterC-md-md1-ma-ma1] mep ccm-send enable
[RouterC-md-md1-ma-ma1] remote-mep ccm-receive enable
[RouterC-md-md1-ma-ma1] return
Step 4 Configure EFM OAM to run between Router C and Router D.

[RouterC] efm enable


[RouterC-GigabitEthernet1/0/0] efm enable
# Configure Router D.
[RouterD] efm enable
[RouterD] interface gigabitethernet 1/0/0
[RouterD-GigabitEthernet1/0/0] efm mode passive
[RouterD-GigabitEthernet1/0/0] efm enable
[RouterD-GigabitEthernet1/0/0] quit
Step 5 Associate EFM OAM with Ethernet CFM.

# Associate EFM OAM running between Router A and Router B with Ethernet CFM running
between Router B and Router C.
[RouterB] oam-mgr
[RouterB-oam-mgr] oam-bind cfm md md1 ma ma1 efm interface gigabitethernet 1/0/0
# Associate Ethernet CFM running between RouterB and RouterC with EFM OAM running
between Router C and Router D.
[RouterC] oam-mgr
[RouterC-oam-mgr] oam-bind cfm md md1 ma ma1 efm interface gigabitethernet 1/0/0

After the preceding configuration, when EFM OAM running between Router A and Router B
detects faults, Ethernet CFM notifies EFM OAM running between Router C and Router D of
the faults.
----End
Configuration Files
#
sysname RouterA
#
vlan batch 10
#
efm enable
#
portswitch
efm mode passive
efm enable
#
portswitch
#
return

#
sysname RouterB
#
vlan batch 10
#
efm enable
#
cfm enable
#

portswitch
efm enable
#
portswitch
#
cfm md md1
ma ma1
map vlan 10
mep ccm-send enable
remote-mep mep-id 2
remote-mep ccm-receive enable
#
oam-mgr
oam-bind cfm md md1 ma ma1 efm interface gigabitethernet 1/0/0
#
return
#
sysname RouterC
#
vlan batch 10
#
efm enable
#
cfm enable
#
portswitch
efm enable
#
portswitch
#
cfm md md1
ma ma1
map vlan 10
mep ccm-send enable
remote-mep mep-id 1
remote-mep ccm-receive enable
#
oam-mgr
oam-bind cfm md md1 ma ma1 efm interface gigabitethernet 1/0/0
#
return
#
sysname RouterD
#
vlan batch 10
#
efm enable
#
portswitch
efm mode passive
efm enable
#
portswitch

#
return
8.18.7 Example for Configuring VPLS Ethernet CFM

In this example, by configuring VPLS Ethernet CFM, you can detect connectivity faults between
PEs.
As shown in Figure 8-22, Martini VPLS runs on the backbone network and LDP is used as
signaling to create Pseudo Wires (PWs). Configure VPLS Ethernet CFM on PEs to fast detect
VPLS connectivity between PEs.
Figure 8-22 Diagram of configuring VPLS Ethernet CFM
CE3
GE1/0/0.1
10.1.1.3/24
PE3 GE1/0/0.1
GE2/0/0 GE3/0/0
100.2.1.2/30 100.3.1.2/30
Loopback1
GE3/0/0 3.3.3.3/32 GE3/0/0
100.2.1.1/30 100.3.1.1/30
Loopback1 PE1 PE2

Loopback1
1.1.1.1/32 GE2/0/0 GE2/0/0 2.2.2.2/32
100.1.1.1/30 100.1.1.2/30 GE1/0/0.1
GE1/0/0.1
GE1/0/0.1 GE1/0/0.1
10.1.1.1/24 10.1.1.2/24
CE1 CE2
1. Run the Interior Gateway Protocol (IGP) on the backbone network. routers across the
backbone network then can communicate.
2. Configure the routing protocols on the backbone network to enable communication
between routers and basic functions of MPLS.
3. Set up LSP tunnels between PEs.
4. Enable MPLS L2VPN on PEs.
5. Create Virtual Switch Instances (VSIs) on PEs and bind VSIs to Attachment Circuit (AC)
interfaces.

6. Configure VPLS Ethernet CFM on PEs.
Data Preparation

l MPLS LSR ID of each PE
l VSI name and VSI ID of each PE
l Interfaces bound to the VSI
l Name and level of the MD, name of the MA, MEP ID, name of the interface on which the
MEP resides, and type of the MEP
Procedure
Step 1 Assign an IP address to each interface.
# Configure PE1.
[HUAWEI] sysname PE1
[PE1-GigabitEthernet2/0/0] ip address 100.1.1.1 30
[PE1-GigabitEthernet2/0/0] undo shutdown
# Configure PE2.
[PE2] interface LoopBack 1
# Configure PE3.

Step 2 Configure the IGP on the MPLS backbone network. The Open Shortest Path First (OSPF) is
used as the IGP protocol in this example.
NOTE
When configuring OSPF, advertise the 32-bit addresses of loopback interfaces on PEs.
# Configure PE1.
[PE1] ospf 1
[PE1-ospf-1] area 0
[PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0
[PE1-ospf-1-area-0.0.0.0] quit
[PE1-ospf-1] quit
# Configure PE2.
[PE2] ospf 1
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
# Configure PE3.
[PE3] ospf 1
[PE3-ospf-1] area 0
[PE3-ospf-1] quit
After the preceding configuration, PE1 and PE2, PE1 and PE3 can learn IP addresses of
loopback1 interfaces from each other through OSPF.
Take the display on PE1 as an example.
[PE1] display ip routing-table
------------------------------------------------------------------------------
2.2.2.2/32 OSPF 10 2 D 100.1.1.2 GigabitEthernet2/0/0
100.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0/0/0
OSPF 10 2 D 100.2.1.2 GigabitEthernet3/0/0
100.2.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0/0/0
Step 3 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
[PE1-GigabitEthernet2/0/0] mpls ldp
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2] interface gigabitethernet2/0/0
# Configure PE3.
[PE3] mpls
[PE3-mpls] quit
[PE3] mpls ldp
[PE3-mpls-ldp] quit
After the preceding configuration, LDP sessions are set up between PEs. Run the display mpls
ldp session command. You can view that the Status field displays Operational.

[PE1] display mpls ldp session
LDP Session(s) in Public Network
------------------------------------------------------------------------------
Peer-ID Status LAM SsnRole SsnAge KA-Sent/Rcv
------------------------------------------------------------------------------
2.2.2.2:0 Operational DU Passive 000:00:02 10/10
------------------------------------------------------------------------------
TOTAL: 2 session(s) Found.
LAM : Label Advertisement Mode SsnAge Unit : DDD:HH:MM
NOTE
If PEs are indirectly connected, you need to run the mpls ldp remote-peer command and the remote-ip
command to create remote LDP sessions between PEs.
Step 4 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 5 Create VSIs and specify LDP as the signaling protocol of VSIs.
# Configure PE1.
[PE1] vsi ldp1 static
[PE1-vsi-ldp1] pwsignal ldp
[PE1-vsi-ldp1-ldp] vsi-id 2
[PE1-vsi-ldp1-ldp] peer 2.2.2.2
# Configure PE2.
# Configure PE3.
Step 6 Bind VSIs to AC interfaces and connect CEs to PEs.

# Configure PE1.
[PE1] interface gigabitethernet 1/0/0.1
[PE1-GigabitEthernet1/0/0.1] vlan-type dot1q 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.
# Configure PE3.
# Configure CE1.
[CE1] interface gigabitethernet 1/0/0.1

[CE1-GigabitEthernet1/0/0.1] vlan-type dot1q 10

[CE1-GigabitEthernet1/0/0.1] ip address 10.1.1.1 24
[CE1-GigabitEthernet1/0/0.1] undo shutdown
[CE1-GigabitEthernet1/0/0.1] quit
# Configure CE2.
# Configure CE3.
After the preceding configuration, run the display vsi name ldp1 verbose command on PE1.
You can view that PWs are set up between PE1 and PE2, PE1 and PE3 by the VSI named ldp1.
The VSI is in the Up state.
[PE1] display vsi name bgp1 verbose
***VSI Name : ldp1
VSI Index : 0
PW Signaling : ldp
Member Discovery Style : static
PW MAC Learn Style : unqualify
Encapsulation Type : vlan
MTU : 1500
VSI State : up
VSI ID : 2
*Peer Router ID : 3.3.3.3
VC Label : 23552
Peer Type : dynamic
Session : up
Tunnel ID : 0x6002003,
*Peer Router ID : 2.2.2.2
VC Label : 23553
Peer Type : dynamic
Session : up
State : up
**PW Information:
*Peer Ip Address : 2.2.2.2
PW State : up
Local VC Label : 23553
Remote VC Label : 23552
PW Type : label
*Peer Ip Address : 3.3.3.3
PW State : up
Local VC Label : 23552
Remote VC Label : 23552
PW Type : label
Hosts attached to CE1, CE2, and CE3 can ping through each other.
Take CE1 as an example.

[CE1] ping 10.1.1.2

0.00% packet loss
[CE1] ping 10.1.1.3
0.00% packet loss
Step 7 Configure Ethernet CFM on PEs.
# Configure PE1.
[PE1] cfm enable
[PE1] cfm md md1
[PE1-md-md1] ma ma1
[PE1-md-md1-ma-ma1] ccm-interval 100
[PE1-md-md1-ma-ma1] map vsi ldp1
[PE1-md-md1-ma-ma1] mep mep-id 1 interface gigabitethernet 1/0/0.1 inward
[PE1-md-md1-ma-ma1] remote-mep mep-id 2
[PE1-md-md1-ma-ma1] mep ccm-send enable
[PE1-md-md1-ma-ma1] remote-mep ccm-receive enable
[PE1-md-md1-ma-ma1] quit
# Configure PE2.
[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1
# Configure PE3.
[PE3] cfm enable
[PE3] cfm md md1
[PE3-md-md1] ma ma1

After the preceding configuration, run the display cfm mep command and the display cfm
remote-mep command on PE1, PE2, and PE3. You can view that the configuration of Ethernet
CFM succeeds. Ethernet CFM can fast detect faults between PEs of VSIs and notify the NMS.
Take PE1 as an example.

[PE1] display cfm mep md md1
MD Name : md1
Level : 0
MA Name : ma1
MEP ID : 2
Vlan ID : --
VSI Name : --
CCM Send : enabled
Direction : inward
MD Name : md1
Level : 0
MA Name : ma1
MEP ID : 3
Vlan ID : --
VSI Name : --
CCM Send : enabled
Direction : inward
[PE1] display cfm remote-mep md md1
--------------------------------------------------
MD Name : md1
Level : 0
MA Name : ma1
RMEP ID : 2
Vlan ID : --
VSI Name : --
MAC : --
CFM Status : up
MD Name : md1
Level : 0
MA Name : ma1
RMEP ID : 3
Vlan ID : --
VSI Name : --
MAC : --
CFM Status : up
----End
Configuration Files
#
sysname PE1
#
cfm enable
#

mpls lsr-id 1.1.1.1

mpls
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 2
peer 2.2.2.2
peer 3.3.3.3
#
mpls ldp
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10
l2 binding vsi ldp1
#
undo shutdown
ip address 100.1.1.1 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 100.2.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
cfm md md1
ma ma1
ccm-interval 100
map vsi ldp1
mep mep-id 1 interface gigabitethernet 1/0/0.1 inward
remote-mep mep-id 2
remote-mep mep-id 3
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 100.1.1.0 0.0.0.3
network 100.2.1.0 0.0.0.3
#
return
#
sysname PE2
#
cfm enable
#
mpls lsr-id 2.2.2.2
mpls
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 2
peer 1.1.1.1
peer 3.3.3.3
#

mpls ldp
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10
l2 binding vsi ldp1
#
undo shutdown
ip address 100.1.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 100.3.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
cfm md md1
ma ma1
ccm-interval 100
map vsi ldp1
remote-mep mep-id 1
remote-mep mep-id 3
#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 100.1.1.0 0.0.0.3
network 100.3.1.0 0.0.0.3
#
return
#
sysname PE3
#
cfm enable
#
mpls lsr-id 3.3.3.3
mpls
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 2
peer 1.1.1.1
peer 2.2.2.2
#
mpls ldp
#
undo shutdown
#
undo shutdown
vlan-type dot1q 10
l2 binding vsi ldp1
#

undo shutdown
ip address 100.2.1.2 255.255.255.252
mpls
mpls ldp
#
undo shutdown
ip address 100.3.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
cfm md md1
ma ma1
ccm-interval 100
map vsi ldp1
remote-mep mep-id 1
remote-mep mep-id 2
#
ospf 1
area 0.0.0.0
network 3.3.3.3 0.0.0.0
network 100.2.1.0 0.0.0.3
network 100.3.1.0 0.0.0.3
#
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
#
sysname CE3
#
undo shutdown
#

undo shutdown
vlan-type dot1q 10
ip address 10.1.1.3 255.255.255.0
#
return
8.18.8 Example for Configuring VPLS-based Ethernet CFM

Through Sub-interfaces for QinQ VLAN Tag Termination
A PE receives a frame with double tags and then accesses a VPLS network. To improve reliability
of the network, a sub-interface for QinQ VLAN tag termination is configured on the AC interface
of each PE and is bound to a VSI to access the VPLS network. Then, CFM is enabled on the
sub-interface.
As shown in Figure 8-23, user VLAN 10 access the network where PEs reside through switches.
Switches send frames with double tags to PEs.
Martini VPLS runs on the backbone network and LDP is used as signaling to create PWs. To
help to improve reliability of the network, a sub-interface for QinQ VLAN tag termination on
the AC interface of each PE and is bound to a VSI, and then is enabled with VPLS-based Ethernet
CFM to fast detect connectivity of the VPLS between PEs.

Figure 8-23 Networking diagram of configuring VPLS-based Ethernet CFM
VPN1
VLAN10
CE3
GE1/0/0
10.1.1.3/24
GE1/0/1
Switch3
GE1/0/0
GE2/0/0.1
GE1/0/0 100.1.2.1/30
100.1.1.2/30 GE1/0/1
PE3
Loopback1
3.3.3.9/32
GE1/0/1 GE1/0/1
100.1.1.1/30 100.1.2.2/30
GE1/0/0 GE1/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
10.1.1.1/24 GE1/0/0.1
10.1.1.2/24
CE1 CE2
VPN1 VPN1
VLAN10 VLAN10
1. Configure the interface mode on each PE to the user termination mode.

2. Run an IGP to ensure connectivity of routers on the backbone network.
3. Enable a routing protocol on the backbone network to ensure connectivity of routers and
enable MPLS.
4. Set up an LSP tunnel between PEs.
5. Enable MPLS L2VPN on each PE.
6. Configure a sub-interface for QinQ VLAN tag termination on the AC interface of each PE.

7. Create a VSI on each PE and bind each sub-interface for QinQ VLAN tag termination to
the VSI.
8. Configure VPLS-based Ethernet CFM on each PE.
9. Enable Layer 2 forwarding and QinQ on each switch.
Data Preparation
l MPLS LSR ID of each PE
l VSI name and VSI ID on each router, that is, PE1, PE2, and PE3
l Name of the sub-interface for QinQ VLAN tag termination that is bound to the VSI
l Name and level of each MD, name of each MA, MEP ID, name of the interface on which
the MEP resides, and type of the MEP
Procedure
Step 1 Configure the interface mode on each PE to the user termination mode.
# Configure PE1.
[PE1-GigabitEthernet2/0/0] mode user-termination
# Configure PE2.
# Configure PE3.
Step 2 Enable an IGP on the MPLS backbone network. OSPF is adopted in this example.
Assign an IP address to each interface on each PE as shown in Figure 8-23. After OSPF is
enabled, the 32-bit loopback address of each PE must be advertised.
# Configure PE1.


[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure PE2.
[PE2] interface LoopBack 1
[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 configurations, after OSPF is enabled, loopback1 routes are reachable and ping
operations are successful between PE1 and PE2 and between PE1 and PE3.
<PE1> display ip routing-table
------------------------------------------------------------------------------


OSPF 10 2 D 100.1.3.2 GigabitEthernet1/0/0
<PE1> ping 100.1.2.2
0.00% packet loss
Step 3 Enable MPLS and LDP on the 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 preceding configurations, LDP sessions can be set up between PEs. Run the display
mpls ldp session command. You can view that the Status field is Operational in the command
output.
<PE1> display mpls ldp session
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
------------------------------------------------------------------------------
------------------------------------------------------------------------------
NOTE
If two PEs are not directly connected, you can run the mpls ldp remote-peer command and the remote-
ip command to set upa a remote LDP session between the PEs.
Step 4 Enable MPLS L2VPN on each PE.

# Configure PE1.
[PE1] mpls l2vpn
# Configure PE2.
[PE2] mpls l2vpn
# Configure PE3.
[PE3] mpls l2vpn
Step 5 Create a VSI and specify LDP as signaling.

# Configure PE1.
# Configure PE2.
# Configure PE3.
Step 6 Configure a sub-interface for QinQ VLAN tag termination on the AC interface of each PE and
bind the sub-interface to the VSI.
# Configure PE1.

[PE1-GigabitEthernet2/0/0.1] control-vid 1 qinq-termination

[PE1-GigabitEthernet2/0/0.1] qinq termination l2 symmetry
[PE1-GigabitEthernet2/0/0.1] qinq termination pe-vid 100 ce-vid 10
# Configure PE2.
# Configure PE3.
NOTE
When you run the qinq termination command on the same main interface, the ce-vid values must be
different if the pe-vid values of the two sub-interfaces are the same.
Step 7 Configure basic Ethernet CFM functions on each PE.

# Configure PE1.
[PE1] cfm enable
[PE1] cfm version standard
[PE1] cfm md md1
[PE1-md-md1] ma ma1
[PE1-md-md1-ma-ma1] mep mep-id 1 interface gigabitethernet 2/0/0.1 pe-vid 100 ce-
vid 10 inward
# Configure PE2.
[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1
vid 10 inward
# Configure PE3.
[PE3] cfm enable

[PE3] cfm md md1

[PE3-md-md1] ma ma1
vid 10 inward
Step 8 Enable QinQ on each switch so that switches can send frames with double tags to PEs.
# Configure Switch1.
[Switch1] vlan 100
[Switch1-GigabitEthernet1/0/1] port vlan-stacking outside-vlan 10 stack-vlan 100
[Switch2] vlan 100
[Switch1-GigabitEthernet1/0/0] portswitch
[Switch3] vlan 100
[Switch3-GigabitEthernet1/0/1] undo shutdonw
NOTE
If the port vlan-stacking command is not supported, you can run the port link-type dot1q-tunnel
command and the port default vlan command to enable QinQ on each interface.
# Assign an IP address to each sub-interface on each CE as shown in Figure 8-23 so that CEs
can send frames with one tag to switches.
# Configure CE1.

# Configure CE2.
# Configure CE3.

After the preceding configurations, run the display cfm mep command and the display cfm
remote-mep command on PE1, PE2, or PE3. You can view that Ethernet CFM is enabled.
Ethernet CFM can fast detect faults between PEs of VSIs and notify the NMS.
<PE1> display cfm mep md md1
--------------------------------------------------
MD Name : md1
Level : 0
MA Name : ma1
MEP ID : 1
Vlan ID : --
VSI Name : ldp1
L2VC ID : --
CCM Send : enabled
Direction : inward
MAC Address : 00e0-fc6e-bb11
MEP Pe-vid : 100
MEP Ce-vid : 10
MEP Vid : --
<PE1> display cfm remote-mep md md1
--------------------------------------------------
MD Name : md1
Level : 0
MA Name : ma1
RMEP ID : 2
Vlan ID : --
VSI Name : ldp1
L2VC ID : --
MAC : 00e0-0003-0003

CFM Status : up
MD Name : md1
Level : 0
MA Name : ma1
RMEP ID : 3
Vlan ID : --
VSI Name : ldp1
L2VC ID : --
MAC : --
CFM Status : up
----End
Configuration Files
#
sysname PE1
#
cfm enable
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 2
peer 2.2.2.9
peer 3.3.3.9
#
mpls ldp
#
undo shutdown
#
undo shutdown
qinq termination l2 symmetry
l2 binding vsi ldp1
#
interface Gigabitethernet1/0/0
undo shutdown
ip address 100.1.3.1 255.255.255.252
mpls
mpls ldp
#
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
#
cfm md md1
ma ma1
map vsi ldp1
ccm-interval 30

mep mep-id 1 interface gigabitethernet 2/0/0.1 pe-vid 100 ce-vid 10 inward

remote-mep mep-id 2
remote-mep mep-id 3
#
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
#
cfm enable
#
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
#
undo shutdown
ip address 100.1.3.2 255.255.255.252
mpls
mpls ldp
#
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
#
cfm md md1
ma ma1
map vsi ldp1
ccm-interval 30
remote-mep mep-id 1
remote-mep mep-id 3


#
ospf 1
area 0.0.0.0
network 2.2.2.9 0.0.0.0
network 100.1.2.0 0.0.0.3
network 100.1.3.0 0.0.0.3
#
return
#
sysname PE3
#
cfm enable
#
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
#
undo shutdown
ip address 100.1.1.2 255.255.255.252
mpls
mpls ldp
#
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
#
cfm md md1
ma ma1
map vsi ldp1
ccm-interval 30
remote-mep mep-id 1
remote-mep mep-id 2
#
ospf 1
area 0.0.0.0
network 3.3.3.9 0.0.0.0

network 100.1.2.0 0.0.0.3

network 100.1.1.0 0.0.0.3
#
return
l Configuration file of Switch1

#
sysname Switch1
#
vlan batch 100
#
undo shutdown
#
undo shutdown
port vlan-stacking outside-vlan 10 stack-vlan 100
#
return

#
sysname Switch2
#
vlan batch 100
#
undo shutdown
#
undo shutdown
#
return

#
sysname Switch3
#
vlan batch 100
#
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
8.18.9 Example for Configuring VLL-based Ethernet CFM Through

Sub-interfaces for QinQ VLAN Tag Termination
A PE receives a frame with two tags and then accesses a VLL network. To improve reliability
of the network, a sub-interface for QinQ VLAN tag termination is configured on the AC interface
of each PE and is bound to an L2VC interface to access the VLL network. Then, CFM is enabled
on the sub-interface.
As shown in Figure 8-24, GE 1/0/0.1 on a CE accesses a PE through a switch. QinQ is enabled
on each switch so that the switch can add Tag 100 to the frames sent by the CE. In this manner,
the IDs of VLANs on the public network are saved. Then, the switch sends user frames with
double tags to the PE. Martini VLL runs on the backbone network and LDP is used as signaling
to create PWs. To help to improve reliability of the network, a sub-interface for QinQ VLAN
tag termination on the AC interface of each PE is bound to an L2VC interface and then is enabled
with VLL-based Ethernet CFM to fast detect connectivity of VLL links between PEs.
Figure 8-24 Networking diagram of configuring VLL-based Ethernet CFM

1.1.1.9/32 2.2.2.9/32 3.3.3.9/32
GE1/0/0 GE1/0/0
100.1.1.1/24 100.1.2.2/24
PE1 PE2
GE1/0/0 GE2/0/0
GE2/0/0.1 100.1.1.2/24 P 100.1.2.1/24 GE2/0/0.1
GE1/0/0 GE1/0/0
Switch1 Switch2
GE1/0/1 GE1/0/1
GE1/0/0.1 GE1/0/0.1
10.1.1.1/24 10.1.1.2/24
CE1 CE2
VPN1 VPN1

1. Configure the interface mode on PE1 and PE2 to the user termination mode.
2. Run an IGP to ensure connectivity of routers on the backbone network
3. Enable MPLS on the backbone network and set up an LSP tunnel.
4. Set up the remote MPLS LDP peer relationship between PEs on both ends of the PW.
5. Configure a sub-interface for QinQ VLAN tag termination on the AC interface of each PE
6. Create an MPLS L2VC on each PE and bind each sub-interface for QinQ VLAN tag
termination to the L2VC interface.
7. Configure VLL-based Ethernet CFM on each PE.
8. Enable Layer 2 forwarding and QinQ on each switch.
Data Preparation
l Interface name of each PE connected to each CE
l L2VC IDs on both ends of the PW (They must be the same.)
l MPLS LSR ID of each PE and the P router
l IP address of the remote peer of each PE
l Tag value that is terminated on the sub-interface for QinQ VLAN tag termination
l Name and level of each MD, name of each MA, MEP ID, name of the interface on which
the MEP resides, and type of the MEP
Procedure
Step 1 Configure the interface mode on each PE to the user termination mode.
# Configure PE1.
# Configure PE2.
Step 2 Enable an IGP on the MPLS backbone network. OSPF is adopted in this example.
Assign an IP address to each interface on each PE and the P router as shown in Figure 8-24.
After OSPF is enabled, the 32-bit loopback addresses of PE1, P, and PE2 must be advertised.

# Configure PE1.
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1] quit
# Configure the P router.

[HUAWEI] sysname P
[P] interface LoopBack 1
[P-LoopBack1] ip address 2.2.2.9 32
[P-LoopBack1] quit
[P] interface gigabitethernet 1/0/0
[P-GigabitEthernet1/0/0] ip address 100.1.1.2 24
[P-GigabitEthernet1/0/0] undo shutdown
[P-GigabitEthernet1/0/0] quit
[P-GigabitEthernet2/0/0] ip address 100.1.2.1 24
[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] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1] quit
After the configurations, OSPF is enabled on PE1 and PE2, and loopback1 routes are reachable
and ping operations are successful between PE1 and PE2.

<PE1> display ip routing-table
------------------------------------------------------------------------------


<PE1> ping 100.1.2.2
0.00% packet loss
Step 3 Enable MPLS and LDP on the MPLS backbone network.

# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
# Configure the P router.

[P] mpls lsr-id 2.2.2.9
[P] mpls
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
[P] interface gigabitethernet1/0/0
[P-GigabitEthernet1/0/0] mpls
[P-GigabitEthernet1/0/0] mpls ldp
[P] interface gigabitethernet2/0/0
[P-GigabitEthernet2/0/0] mpls ldp
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
After the preceding configurations, LDP sessions can be set up between PE1 and the P router
and between the P router and PE2. Run the display mpls ldp session command. You can view
that the Status field is Operational in the command output.


------------------------------------------------------------------------------
------------------------------------------------------------------------------
2.2.2.9:0 Operational DU Active 0000:03:01 726/726
------------------------------------------------------------------------------
Step 4 Create a 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.
[PE2] mpls ldp remote-peer 1.1.1.9
[PE2-mpls-ldp-remote-1.1.1.9] remote-ip 1.1.1.9
[PE2-mpls-ldp-remote-1.1.1.9] quit
After the preceding configurations, an LDP session can be set up between PE1 and PE2. Run
the display mpls ldp session command. You can view that the Status field is Operational in
the command output.

------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Step 5 Enable MPLS L2VPN; create a VC link; configure the sub-interface for QinQ VLAN tag
termination.
# Configure PE1.
[PE1] mpls l2vpn
[PE1-l2vpn] quit
[PE1-GigabitEthernet2/0/0.1] mpls l2vc 3.3.3.9 101
# Configure PE2.
[PE2] mpls l2vpn
[PE2-l2vpn] quit
[PE2-GigabitEthernet2/0/0.1] mpls l2vc 1.1.1.9 101

NOTE
When you run the qinq termination command on the same main interface, the ce-vid values must be
different if the pe-vid values of the two sub-interfaces are the same.
Step 6 Configure basic Ethernet CFM functions on each PE.

# Configure PE1.
[PE1] cfm enable
[PE1] cfm md md1
[PE1-md-md1] ma ma1
[PE1-md-md1-ma-ma1] map mpls l2vc 101 tagged
vid 10 inward
# Configure PE2.
[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1
vid 10 inward
Step 7 Enable QinQ on each switch so that switches can send frames with double tags to PEs.
[Switch1] vlan 100
[Switch2] vlan 100


NOTE
If the port vlan-stacking command is not supported, you can run the port link-type dot1q-tunnel
command and the port default vlan command to enable QinQ on each interface.
# Assign an IP address to each sub-interface on each CE as shown in Figure 8-24 so that CEs
can send frames with one tag to switches.
# Configure CE1.
# Configure CE2.

After the preceding configuration, run the display cfm mep command and the display cfm
remote-mep command on PE1, PE2, or PE3. You can view that Ethernet CFM is enabled.
Ethernet CFM can fast detect faults between PEs of VSIs and notify the NMS.
<PE1> display cfm mep md md1
--------------------------------------------------
MD Name : md1
Level : 0
MA Name : ma1
MEP ID : 2
Vlan ID : --
VSI Name : --
CCM Send : enabled
Direction : inward
MAC Address : 00e0-fc6e-bb11
MEP Pe-vid : 100
MEP Ce-vid : 10
MEP Vid : --
[PE1] display cfm remote-mep md md1
--------------------------------------------------
MD Name : md1
Level : 0
MA Name : ma1
RMEP ID : 1
Vlan ID : --
VSI Name : --


MAC : 00e0-0003-0003
CFM Status : up
----End
Configuration Files
#
sysname PE1
#
cfm enable
#
mpls lsr-id 1.1.1.9
mpls
#
mpls l2vpn
#
remote-ip 3.3.3.9
#
undo shutdown
#
undo shutdown
mpls l2vc 3.3.3.9 101
#
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
#
cfm md md1
ma ma1
map mpls l2vc 101 tagged
ccm-interval 30
remote-mep mep-id 2
#
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 PE2
#
cfm enable
#

mpls lsr-id 3.3.3.9

mpls
#
mpls l2vpn
#
remote-ip 1.1.1.9
#
undo shutdown
#
undo shutdown
mpls l2vc 1.1.1.9 101
#
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
#
cfm md md1
ma ma1
ccm-interval 30
remote-mep mep-id 1
#
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
l Configuration file of the P router
#
sysname P
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
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.2.0 0.0.0.255
network 100.1.1.0 0.0.0.255
#
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 Switch1
#
vlan batch 100
#
undo shutdown
#
undo shutdown
#
return

#
sysname Switch2
#
vlan batch 100
#
undo shutdown
#
undo shutdown
#
return
8.18.10 Example for Associating EFM OAM with MPLS OAM

In this example, through the association between EFM OAM and MPLS OAM, the EFM OAM
sessions can send fault information to each other through Ethernet CFM.

On the provider network shown in Figure 8-25, NPEs and P are connected through Ethernet
links; UPEs and NPEs are connected through Ethernet links.
The requirements are as follows:
l Configuring MPLS OAM between NPEs

l Configuring EFM OAM between UPEs and NPEs
l Associating EFM OAM with MPLS OAM
This allows MPLS OAM to send fault messages detected by EFM OAM running between UPE1
and NPE1 to EFM OAM running between NPE2 and UPE2.
Figure 8-25 Diagram of associating EFM OAM with MPLS OAM

Loopback1
4.4.4.4/32
P
GE 1/0/0
100.3.1.2/30 GE2/0/0
100.4.1.2/30
Loopback1 Loopback1 Loopback1 Loopback1
1.1.1.1/32 2.2.2.2/32 3.3.3.3/32 5.5.5.5/32
GE 3/0/0 GE 3/0/0
100.3.1.1/30 100.4.1.1/30 GE 1/0/0
GE 1/0/0 100.5.1.2/30
100.1.1.1/30
GE 1/0/0 GE 2/0/0 GE 2/0/0 GE 1/0/0
100.1.1.2/30 100.2.1.1/30 100.2.1.2/30 100.5.1.1/30
UPE1 NPE1 NPE2 UPE2
1. Configure the IGP on the provider network so that devices can communicate.
2. Configure MPLS OAM between NPEs.
3. Configure EFM OAM between NPEs and UPEs.
4. Configure EFM OAM between UPE1 and NPE1 to send fault messages to MPLS OAM
and MPLS OAM then sends fault messages to EFM OAM between NPE2 and UPE2.
Data Preparation
l IP addresses of the interface on the routers, name of tunnel interfaces, and tunnel ID
l Type of the sent detection packets
l Parameters such as the mode of the backward tunnel

Procedure
Step 1 Configure IP addresses of the interfaces.
Configure the IP address and mask for each interface including each loopback interface as shown
in Figure 8-25. The detailed configuration is omitted here. For details, see "Configuration Files."
Step 2 Configure the IGP. The Intermediate System-to-Intermediate System (IS-IS) is used as the IGP
protocol in this example.
# Configure UPE1.
[UPE1] isis 1
[UPE1-isis-1] network-entity 00.0005.0000.0000.0001.00
[UPE1-isis-1] is-level level-2
[UPE1-isis-1] quit
[UPE1] interface gigabitethernet 1/0/0
[UPE1-GigabitEthernet1/0/0] isis enable 1
[UPE1-GigabitEthernet1/0/0] undo shutdown
[UPE1-GigabitEthernet1/0/0] quit
[UPE1] interface loopback 1
[UPE1-LoopBack1] isis enable 1
[UPE1-LoopBack1] quit
# Configure NPE1.
[NPE1] isis 1
[NPE1-isis-1] network-entity 00.0005.0000.0000.0002.00
[NPE1-isis-1] is-level level-2
[NPE1-isis-1] quit
[NPE1] interface gigabitethernet 1/0/0
[NPE1-GigabitEthernet1/0/0] isis enable 1
[NPE1] interface loopback 1
[NPE1-LoopBack1] isis enable 1
[NPE1-LoopBack1] quit
# Configure P.
[P] isis 1
[P-isis-1] network-entity 00.0005.0000.0000.0004.00
[P-isis-1] is-level level-2
[P-isis-1] quit
[P-GigabitEthernet1/0/0] isis enable 1
[P-GigabitEthernet2/0/0] isis enable 1
[P] interface loopback 1
[P-LoopBack1] isis enable 1
[P-LoopBack1] quit
# Configure NPE2.
[NPE2] isis 1
[NPE2-isis-1] network-entity 00.0005.0000.0000.0003.00

[NPE2-isis-1] is-level level-2

[NPE2-isis-1] quit
[NPE2] interface loopback 1
[NPE2-LoopBack1] isis enable 1
[NPE2-LoopBack1] quit
# Configure UPE2.
[UPE2] isis 1
[UPE2-isis-1] network-entity 00.0005.0000.0000.0005.00
[UPE2-isis-1] is-level level-2
[UPE2-isis-1] quit
[UPE2-GigabitEthernet1/0/0] isis enable 1
[UPE2-GigabitEthernet1/0/0] undo shutdown
[UPE2] interface loopback 1
[UPE2-LoopBack1] isis enable 1
[UPE2-LoopBack1] quit
After the preceding configuration, run the display ip routing-table command on each router.
You can view that the routers learn the routes from each other. Take the display on UPE1 as an
example.
[UPE1] display ip routing-table
------------------------------------------------------------------------------
2.2.2.9/32 ISIS 15 10 D 100.1.1.2 GigabitEthernet1/0/0
Step 3 Configure basic MPLS functions on NPEs and P; enable MPLS Traffic Engineering (TE),
Resource Reservation Protocol TE (RSVP-TE), and Constraint Shortest Path First (CSPF).
# Configure NPE1.
[NPE1] mpls lsr-id 2.2.2.2
[NPE1] mpls
[NPE1-mpls] mpls te
[NPE1-mpls] mpls rsvp-te
[NPE1-mpls] mpls te cspf
[NPE1-mpls] quit
[NPE1-GigabitEthernet2/0/0] mpls

[NPE1-GigabitEthernet2/0/0] mpls te
[NPE1-GigabitEthernet2/0/0] mpls rsvp-te
# Configure P.
[P] mpls lsr-id 4.4.4.4
[P] mpls
[P-mpls] mpls te
[P-mpls] mpls rsvp-te
[P-mpls] quit
[P-GigabitEthernet1/0/0] mpls te
[P-GigabitEthernet1/0/0] mpls rsvp-te
[P-GigabitEthernet2/0/0] mpls te
[P-GigabitEthernet2/0/0] mpls rsvp-te
# Configure NPE2.
[NPE2] mpls lsr-id 3.3.3.3
[NPE2] mpls
[NPE2-mpls] mpls te
[NPE2-mpls] mpls rsvp-te
[NPE2-mpls] mpls te cspf
[NPE2-mpls] quit
Step 4 Configure IS-IS TE on NPEs and P.
# Configure NPE1.
[NPE1] isis 1
[NPE1-isis-1] cost-style wide
[NPE1-isis-1] traffic-eng level-2
[NPE1-isis-1] quit
# Configure P.
[P] isis 1
[P-isis-1] cost-style wide
[P-isis-1] traffic-eng level-2
[P-isis-1] quit
# Configure NPE2.
[NPE2] isis 1
[NPE2-isis-1] cost-style wide
[NPE2-isis-1] traffic-eng level-2
[NPE2-isis-1] quit

Step 5 Use explicit paths to set up TE tunnels on NPEs.
# Configure NPE1.
[NPE1] explicit-path npe1-to-npe2
[NPE1-explicit-path-npe1-to-npe2] next hop 100.2.1.2
[NPE1-explicit-path-npe1-to-npe2] quit
[NPE1] interface tunnel 2/0/0
[NPE1-Tunnel2/0/0] ip address unnumbered interface loopback 1
[NPE1-Tunnel2/0/0] tunnel-protocol mpls te
[NPE1-Tunnel2/0/0] destination 3.3.3.3
[NPE1-Tunnel2/0/0] mpls te tunnel-id 100
[NPE1-Tunnel2/0/0] mpls te signal-protocol rsvp-te
[NPE1-Tunnel2/0/0] mpls te path explicit-path work
[NPE1-Tunnel2/0/0] mpls te commit
[NPE1-Tunnel2/0/0] quit
# Configure NPE2.
[NPE2] explicit-path npe2-to-npe1
[NPE2-explicit-path-npe2-to-npe1] next hop 100.4.1.2
[NPE2-explicit-path-npe2-to-npe1] quit
[NPE2] interface tunnel 3/0/0
[NPE2-Tunnel3/0/0] ip address unnumbered interface loopback 1
[NPE2-Tunnel3/0/0] tunnel-protocol mpls te
[NPE2-Tunnel3/0/0] destination 2.2.2.2
[NPE2-Tunnel3/0/0] mpls te tunnel-id 200
[NPE2-Tunnel3/0/0] mpls te signal-protocol rsvp-te
[NPE2-Tunnel3/0/0] mpls te path explicit-path work
[NPE2-Tunnel3/0/0] mpls te commit
[NPE2-Tunnel3/0/0] quit
After the preceding configuration, run the display interface tunnel command on each NPE.
You can view the tunnel interface is Up. Take the display on NPE1 as an example.
[NPE1] display interface tunnel
Tunnel2/0/0 current state : UP
Description : Tunnel2/0/0 Interface
The Maximum Transmit Unit is 1500 bytes
Internet Address is unnumbered, using address of LoopBack1(2.2.2.2/32)
Encapsulation is TUNNEL, loopback not set
Tunnel destination 3.3.3.3
Tunnel protocol/transport MPLS/MPLS, ILM is available,
primary tunnel id is 0x1002001, secondary tunnel id is 0x0
The tunnelIfIndex is 0xc000505
5 minutes output rate 0 bits/s, 0 packets/s
0 packets output, 0 bytes
0 packets output dropped
Step 6 Configure MPLS OAM on NPEs. NPE1 acts as the ingress and NPE2 acts as the egress.
# Configure NPE1.
[NPE1] mpls
[NPE1-mpls] mpls oam
[NPE1-mpls] quit
[NPE1] mpls oam ingress tunnel2/0/0 type ffd frequency 100
[NPE1] mpls oam ingress enable all
# Configure NPE2.
[NPE2] mpls
[NPE2-mpls] mpls oam
[NPE2-mpls] quit
[NPE2] mpls oam egress lsr-id 2.2.2.2 tunnel-id 100 auto-protocol backward-lsp
tunnel 3/0/0 private

After the preceding configuration, you can use the command to view the parameters and status
of MPLS OAM on the ingress NPE1 and egress NPE2. The command output shows that the
ingress and egress are in normal detection state.
Take the display on NPE2 as an example.
[NPE2] display mpls oam egress all verbose
-------------------------------------------------------------------------
Verbose information about the NO.1 oam at the egress
-------------------------------------------------------------------------
lsp basic information: oam basic information:
----------------------------------- -----------------------------------
Lsp name : -- Oam-Index : 256
Lsp signal status : Up Oam select board : 1
Lsp establish type : Rsvp lsp Enable-state : --
Lsp incoming Label : 3 Auto-protocol : Enable
Lsp ingress lsr-id : 2.2.2.2 Auto-overtime (s) : 300
Lsp tnl-id/lsp-id : 100/1 Ttsi/lsr-id : 2.2.2.2
Lsp Incoming-int : GigabitEthernet2/0/0 Ttsi/tunnel-id : 100
oam detect information: oam backward information:
------------------------------------ ----------------------------------
Type : FFD Tunnel name : Tunnel2/0/0
Frequency : 100 ms Share attribute : Private
Detect-state : Start Lsp signal status : Up
Defect-state : Non-defect Bdi-frequency : Detect-freq
Available state : Available
Unavailable time (s): 0
-------------------------------------------------------------------------
Total Oam Num: 1
Total Start Oam Num: 1
Total Defect Oam Num: 0
Total Unavaliable Oam Num: 0
Step 7 Configure EFM OAM on UPEs and NPEs.

# Configure UPE1.
[UPE1] efm enable
[UPE1-GigabitEthernet1/0/0] efm enable
# Configure NPE1.
[NPE1] efm enable
[NPE1-GigabitEthernet1/0/0] efm enable
# Configure UPE2.
[UPE2] efm enable
[UPE2-GigabitEthernet1/0/0] efm enable
# Configure NPE2.
[NPE2] efm enable
[NPE2-GigabitEthernet1/0/0] efm enable
After the preceding configuration, run the display efm session command on UPEs or NPEs.
You can view that the status of EFM OAM on GE 1/0/0 is detect. Take the display on UPE2 as
an example.
[UPE2] display efm session interface gigabitethernet 1/0/0


--------------------------------------------------------------------
Step 8 Associate EFM OAM with MPLS OAM on NPEs.

# Configure NPE1.
[NPE1] oam-mgr
[NPE1-oam-mgr] oam-bind ingress efm interface gigabitethernet 1/0/0 egress mpls oam
tunnel 2/0/0
# Configure NPE2.
[NPE2] oam-mgr
[NPE2-oam-mgr] oam-bind ingress mpls oam lsr-id 2.2.2.2 tunnel-id 200 egress efm
NOTE
When you create static LSPs, MPLS OAM instances created accordingly record LSR ID and tunnel ID
only, if lsr-id and tunnel-id are specified. In this manner, you must specify lsr-id and tunnel-id when
associating Ethernet OAM with MPLS OAM.

After the preceding configuration, when EFM OAM running between UPE1 and NPE1 detects
faults, the faults can be sent to EFM OAM running between UPE2 and NPE2 through MPLS
OAM.
----End
Configuration Files
l Configuration file of UPE1
#
sysname UPE1
#
efm enable
#
isis 1
is-level level-2
network-entity 00.0005.0000.0000.0001.00
#
undo shutdown
ip address 100.1.1.1 255.255.255.252
isis enable 1
efm enable
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
isis enable 1
#
return

#
sysname NPE1
#
efm enable
#
mpls lsr-id 2.2.2.2
mpls
mpls te
mpls rsvp-te
mpls oam

mpls te cspf
#
explicit-path npe1-to-npe2
next hop 100.2.1.2
#
isis 1
is-level level-2
cost-style wide
network-entity 00.0005.0000.0000.0002.00
traffic-eng level-2
#
undo shutdown
ip address 100.1.1.2 255.255.255.252
isis enable 1
efm enable
#
undo shutdown
ip address 100.2.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
undo shutdown
ip address 100.3.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
isis enable 1
#
interface Tunnel2/0/0
destination 3.3.3.3
mpls te tunnel-id 100
mpls te path explicit-path npe1-to-npe2
mpls te commit
#
mpls oam ingress Tunnel2/0/0 type ffd frequency 100
mpls oam ingress enable Tunnel2/0/0
#
oam-mgr
oam-bind ingress efm interface GigabitEthernet 1/0/0 egress mpls oam Tunnel
2/0/0
#
return
l Configuration file of P
#
sysname P
#
mpls lsr-id 4.4.4.4
mpls
mpls te
mpls rsvp-te
#
isis 1
is-level level-2
cost-style wide
network-entity 00.0005.0000.0000.0004.00
traffic-eng level-2
#

undo shutdown
ip address 100.3.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
undo shutdown
ip address 100.4.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface LoopBack1
ip address 4.4.4.4 255.255.255.255
isis enable 1
#
return
#
sysname NPE2
#
efm enable
#
mpls lsr-id 3.3.3.3
mpls
mpls te
mpls rsvp-te
mpls oam
mpls te cspf
#
explicit-path npe2-to-npe1
next hop 100.4.1.2
#
isis 1
is-level level-2
cost-style wide
network-entity 00.0005.0000.0000.0003.00
traffic-eng level-2
#
undo shutdown
ip address 100.5.1.1 255.255.255.252
isis enable 1
efm enable
#
undo shutdown
ip address 100.2.1.2 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
undo shutdown
ip address 100.4.1.1 255.255.255.252
isis enable 1
mpls
mpls te
mpls rsvp-te
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
isis enable 1
#


destination 2.2.2.2
mpls te path explicit-path npe2-to-npe1
mpls te commit
#
mpls oam egress lsr-id 1.1.1.1 tunnel-id 100 backward-lsp Tunnel3/0/0 private
#
oam-mgr
oam-bind ingress mpls oam lsr-id 2.2.2.2 tunnel-id 200 egress efm interface
GigabitEthernet 1/0/0
#
return
l Configuration file of UPE1

#
sysname UPE1
#
efm enable
#
isis 1
is-level level-2
network-entity 00.0005.0000.0000.0005.00
#
undo shutdown
ip address 100.5.1.2 255.255.255.252
isis enable 1
efm enable
#
interface LoopBack1
ip address 5.5.5.5 255.255.255.255
isis enable 1
#
return
8.18.11 Example for Configuring EFM OAM Extension for VRRP

In this example, by configuring EFM OAM on CEs and PEs and configuring a VRRP backup
group on the PEs, you can use the master device to transmit network traffic.
NOTE
As shown in Figure 8-26.

Figure 8-26 Networking diagram of configuring EFM OAM extension for VRRP
EFM OAM Extension
GE1/0/0 Loopback1
2.2.2.2/32
AS:100
Vlanif10:
10.1.1.1/24 PE1 PO
/0 100 S1/0/
Loopback1 3/0 .1.1 0
E .1/2 P Loopback1
1.1.1.1/32
G 4 1 OS1
GE2/0/0 0 0.1 /0 4.4.4.4/32
Vlanif10 .1.2 /0
100.3.1.1/24 /24
10.1.1.2/24
Loopback1
VRRP
Vlanif10 4.4.4.4/32
GE2/0/0 /0
CE1 10.1.1.3/24 S 2/0 24 PE3
100.3.1.2/24 P O /
(SoftX) . 2 .1.2
0
GE /0/0 10
VPNA 3/0 P OS1 .1/24
/0 .2.1
GE2/0/0 PE2 100
Vlanif10: Loopback1 MPLS
10.1.1.1/24 3.3.3.3/32 backbone
EFM OAM Extension
The master interface board of CE1 is connected to the master router, and the slave interface
board of CE1 is connected to the backup router. The interfaces on the master interface board
and slave interface board that are connected to PE1 and PE2 are configured with the same IP
address.
Normally, the IP address of the interface on the master interface board is valid. The SoftX is
dual homed to the gateways, that is, PE1 and PE2.
VLAN IF interfaces are configured to group PE1 and PE2 into a broadcast domain, that is, a
VLAN. Then the downstream interfaces (configured as a Layer 2 interfaces) of the two PEs are
added into the VLAN. Based on EFM OAM extension, the SoftX can detect the faults on the
links connecting the SoftX to PE1 and PE2.
1. Configure Intermediate System to Intermediate System (IS-IS) between PEs to implement
interworking between the PEs.
2. Establish MPLS Label Switched Paths (LSPs) between PEs.
3. Configure VPN instances on PEs and associate the interfaces that connect the PEs to the
CE with the corresponding VPN instances.
4. Configure Multiprotocol Interior Border Gateway Protocol (MP IBGP) between PEs to
exchange VPN routing information.
5. Enable EFM OAM extension between PE1 and CE1, and between PE2 and CE1. Then
associate EFM OAM extension with interfaces.
6. Create the VRRP backup group and enable EFM OAM extension to track the interface
status.

Data Preparation
l IP address of each interface, including the physical interface and VLANIF interface
l MPLS LSR IDs of PEs
l Names of the VPN instances, router distinguishers (RDs), and VPN targets on PEs
l Virtual IP address of the VRRP backup group and VRRP priorities of master and backup
routers
Procedure
Step 1 Assign IP addresses to interfaces on PE1, PE2, PE3, and CE1.
# Configure PE1. Create VLAN 10, and add GE 2/0/0 and GE 3/0/0 into VLAN 10.
<PE1> system-view
[PE1-GigabitEthernet2/0/0] portswitch
[PE1] vlan 10
[PE1-vlan10] port gigabitethernet 2/0/0
[PE1-vlan10] interface vlanif10
[PE1-vlanif10] ip address 10.1.1.2 255.255.255.0
[PE1-vlanif10] quit
# Configure PE2. Create VLAN 10, and add GE 2/0/0 and GE 3/0/0 into VLAN 10.
<PE2> system-view
[PE2] vlan 10
[PE2-vlan10] interface vlanif10
[PE2-vlanif10] ip address 10.1.1.3 255.255.255.0
[PE2-vlanif10] quit
# Configure CE1. Create VLAN 10, and add GE 1/0/0 and GE 2/0/0 into VLAN 10.
<CE1> system-view
[CE1] interface gigabitethernet 1/0/0
[CE1-GigabitEthernet1/0/0] portswitch
[CE1-GigabitEthernet1/0/0] quit
[CE1-GigabitEthernet2/0/0] portswitch
[CE1-vlan10] port gigabitethernet 1/0/0
[CE1-vlan10] port gigabitethernet 2/0/0
[CE1-vlan10] interface vlanif10
[CE1-vlanif10] ip address 10.1.1.1 255.255.255.0
[CE1-vlanif10] quit
Step 2 Configure IGP on the MPLS backbone network to implement device interworking on the
backbone network.
# Configure PE1.


[PE1] interface pos 1/0/0
[PE1-Pos1/0/0] ip address 100.1.1.1 24
[PE1-Pos1/0/0] isis enable
[PE1-Pos1/0/0] quit
[PE1] isis 1
[PE1-isis-1] is-level level-1-2
[PE1-isis-1] quit
# Configure PE2.
[PE2-Pos1/0/0] ip address 100.2.1.1 24
[PE2-Pos1/0/0] quit
[PE2] isis 1
[PE2-isis-1] quit
# Configure PE3.
[PE3-Pos1/0/0] ip address 100.1.1.2 24
[PE3-Pos1/0/0] quit
[PE3-Pos2/0/0] ip address 100.2.1.2 24
[PE3-Pos2/0/0] quit
[PE3] isis 1
[PE3-isis-1] quit
Step 3 Configure basic MPLS functions and MPLS Label Distribution Protocol (LDP) on the MPLS
backbone network and set up LDP LSPs.
# Configure PE1.
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-ldp] quit
[PE1-Pos1/0/0] mpls
[PE1-Pos1/0/0] mpls ldp
[PE1-Pos1/0/0] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-ldp] quit
[PE2-Pos1/0/0] mpls
[PE2-Pos1/0/0] quit

# Configure PE3.
[PE3] mpls
[PE3-mpls] quit
[PE3] mpls ldp
[PE3-ldp] quit
[PE3-Pos1/0/0] mpls
[PE3-Pos1/0/0] quit
[PE3-Pos2/0/0] mpls
[PE3-Pos2/0/0] quit
ldp session command. The command output shows that the Status field displays Operational.
Step 4 Configure VPN instances on PE1 and PE2 so that CE1 can access both PEs.
# Configure PE1.
[PE1] ip vpn-instance vpna
[PE1-vpn-instance-vpna] route-distinguisher 100:1
[PE1-vpn-instance-vpna] vpn-target 111:1 both
[PE1-vpn-instance-vpna] quit
[PE1] interface vlanif 10
[PE1-vlanif10] ip binding vpn-instance vpna
[PE1-vlanif10] ip address 10.1.1.2 24
[PE1-vlanif10] quit
# Configure PE2.
[PE2-vlanif10] ip binding vpn-instance vpna
[PE2-vlanif10] ip address 10.1.1.3 24
[PE2-vlanif10] quit
Step 5 Enable EFM OAM extension between PE1 and CE1, and between PE2 and CE1.
# Configure PE1.
[PE1] efm enable
[PE1-GigabitEthernet3/0/0] efm enable
[PE1-GigabitEthernet3/0/0] efm trigger if-down
# Configure PE2.
[PE2] efm enable
[PE2-GigabitEthernet3/0/0] efm trigger if-down
Step 6 Configure the static routes on PE1 and PE2 that are destined for CE1, and import the static routes
to the Border Gateway Protocol (BGP).
# Configure PE1.
[PE1] ip route-static vpn-instance vpna 1.1.1.1 32 10.1.1.1
[PE1] bgp 100
[PE1-bgp] ipv4-family vpn-instance vpna

[PE1-bgp-vpna] import-route direct

[PE1-bgp-vpna] import-route static
[PE1-bgp-vpna] quit
# Configure PE2.
[PE2] ip route-static vpn-instance vpna 1.1.1.1 32 10.1.1.1
[PE2] bgp 100
[PE2-bgp-vpna] quit
# Configure CE1. Configure the virtual IP address of the VRRP backup group as the gateway
address.
[CE1] ip route-static 0.0.0.0 0.0.0.0 10.1.1.111
Step 7 Set up MP-IBGP peer relationships between PE1, PE2, and PE3.
# Configure PE1.
[PE1] bgp 100
[PE1-bgp] peer 3.3.3.3 as-number 100
[PE1-bgp] peer 3.3.3.3 connect-interface loopback 1
[PE1-bgp] ipv4-family vpnv4
[PE1-bgp] peer 3.3.3.3 enable
[PE1-bgp] quit
# Configure PE2.
[PE2] bgp 100
[PE2-bgp] quit
# Configure PE3.
[PE3] bgp 100
[PE3-bgp] quit
Step 8 Configure the VRRP backup group on PE1 and PE2 to track the traffic of the downstream
interface.
# Configure PE1.
[PE1-vlanif10] vrrp vrid 1 virtual-ip 10.1.1.111
[PE1-vlanif10] vrrp vrid 1 track interface gigabitethernet 3/0/0 reduced 60
[PE1-vlanif10] quit
# Configure PE2.


[PE2-vlanif10] vrrp vrid 1 virtual-ip 10.1.1.111
[PE2-vlanif10] vrrp vrid 1 track interface gigabitethernet 3/0/0 reduced 60
[PE21-vlanif10] quit
After the configuration, run the display interface command on PE2 to check the status of the
backup interface. The command output shows that the protocol status of the backup interface is
DOWN (EFM down). That is, the backup interface is blocked, and cannot forward traffic.
[PE2] display interface GigabitEthernet 3/0/0
GigabitEthernet3/0/0 current state : UP
Line protocol current state : DOWN (EFM down)
Description: GigabitEthernet3/0/0 Interface
Switch Port,PVID : 10,The Maximum Transmit Unit is 1500
Internet protocol processing : disabled
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-0003-0003
The Vendor Name is AGILENT , The Vendor PN is HFCT-5710L
Transceiver BW: 1G, Transceiver Mode: Single Mode
WaveLength: 1310nm, Transmission Distance: 10km
Loopback:none, full-duplex mode, negotiation: disable, Pause Flowcontrol:Receive
Enable and Send Enable
Last physical up time : 2008-12-27 19:40:57

Last physical down time : 2008-12-27 19:40:56Statistics last cleared:2008-12-27
17:13:58
Last 300 seconds input rate: 520 bits/sec, 1 packets/sec
Last 300 seconds output rate: 592 bits/sec, 1 packets/sec
Input: 2041312 bytes, 15821 packets
Output: 591032 bytes, 9228 packets
Input:
Broadcast: 18 packets, JumboOctets: 0 packets
CRC: 0 packets, Symbol: 0 packets
Overrun: 0 packets, InRangeLength: 0 packets
LongPacket: 0 packets, Jabber: 0 packets, Alignment: 0 packets
Fragment: 0 packets, Undersized Frame: 0 packets
RxPause: 0 packets
Output:
Broadcast: 63 packets, JumboOctets: 0 packets
Lost: 0 packets, Overflow: 0 packets, Underrun: 0 packets
System: 0 packets, Overruns: 0 packets
TxPause: 0 packets
Unknown Vlan: 0 packets
Run the display vrrp command on PE1 and PE2 to check the status of the VRRP backup group.
The command output shows that the VRRP status of PE1 is Master, and the VRRP status of
PE2 is Backup. That is, PE1 functions as the master PE, and is responsible for forwarding traffic.
PE2 functions as the backup PE, and cannot forward traffic.
[PE1] display vrrp
State : Master
Virtual IP : 10.1.1.111
PriorityRun : 40
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES


IF State : Up
[PE2] display vrrp
State : Backup
Virtual IP : 10.1.1.111
PriorityRun : 40
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
IF State : DOWN
----End
Configuration Files
#
sysname PE1
#
vlan 10
#
#
mpls lsr-id 2.2.2.2
mpls
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0001.00
#
interface Vlanif10
ip address 10.1.1.2 255.255.255.0
vrrp vrid 1 track interface GigabitEthernet3/0/0 reduced 60
#
interface Pos1/0/0
link-protocol ppp
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#

bgp 100
#
ipv4-family unicast
peer 4.4.4.4 enable
peer 3.3.3.3 enable
#
ipv4-family vpnv4
policy vpn-target
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#
import-route direct
import-route static
#
ip route-static vpn-instance vpna 1.1.1.1 255.255.255.255 10.1.1.1
#
return
#
sysname PE2
#
vlan 10
#
#
mpls lsr-id 3.3.3.3
mpls
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0002.00
#
interface Vlanif10
ip address 10.1.1.3 255.255.255.0
vrrp vrid 1 track interface GigabitEthernet3/0/0 reduced 60
#
interface Pos1/0/0
link-protocol ppp
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
bgp 100


#
ipv4-family unicast
peer 4.4.4.4 enable
peer 2.2.2.2 enable
#
ipv4-family vpnv4
policy vpn-target
peer 2.2.2.2 enable
peer 4.4.4.4 enable
#
import-route direct
import-route static
#
ip route-static vpn-instance vpna 1.1.1.1 255.255.255.255 10.1.1.1
#
return
#
sysname PE3
#
mpls lsr-id 4.4.4.4
mpls
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0003.00
#
interface Pos1/0/0
link-protocol ppp
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface Pos2/0/0
link-protocol ppp
ip address 100.2.1.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 4.4.4.4 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 2.2.2.2 enable
peer 3.3.3.3 enable
#
ipv4-family vpnv4
policy vpn-target
peer 2.2.2.2 enable
peer 3.3.3.3 enable
#
return
#
sysname CE1
#

efm enable
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
ip route-static 0.0.0.0 0.0.0.0 10.1.1.111
#
return
8.18.12 Exmaple for Configuring EFM OAM Extension for Static

Routes
In this example, by configuring EFM OAM on CEs and PEs and configuring the PEs with static
routes to the CEs, you can implement the link protection switchover.
NOTE
Figure 8-27 shows the networking requirements:
Figure 8-27 Networking diagram of configuring EFM OAM extension for static routes
EFM OAM Extension Loopback1

AS:100
2.2.2.2/32
GE1/0/0
10.1.1.1/24 PE1 P
O
/0 100 S1/0
Loopback1 3 /0 .1.1 /0
GE .1/2 Loopback1
1.1.1.1/32 4 1 POS1
4 GE2/0/0 00.1 /0 4.4.4.4/32
1.2/
2 .1.2 /0
.1. 100.3.1.1/24 /24
10
10.2 GE2/0/0 0/0 PE3

CE1 . 1.2 S2/
(SoftX) /24 100.3.1.2/24 PO .1.2/24
.2
GE 0/0 100
VPNA 3/0 O S1/ /24
/0 P .1
GE2/0/0 00 .2.1
PE2 1
10.2.1.1/24 Loopback1 MPLS
3.3.3.3/32 backbone
EFM OAM Extension
The master interface board of CE1 (SoftX) is connected to the master router, and the slave
interface board of CE1 is connected to the backup router. The interfaces on the master interface

board and slave interface board that are connected to PE1 and PE2 are configured with the same
IP address.
Normally, the IP address of the interface on the master interface board is valid. The SoftX is
dual homed to the gateways, that is, PE1 and PE2.
On PE1 and PE2, static routes destined for CE1 are configured, and EFM OAM extension for
static routes are configured to realize link protection and failover.
1. Configure IS-IS between PEs to implement interworking between the PEs.
2. Establish MPLS LSPs between PEs.
3. Configure VPN instances on PEs and associate the interfaces that connect PEs to CEs with
the corresponding VPN instances.
4. Configure MP IBGP between PEs to exchange VPN routing information.
5. Enable EFM OAM extension between PE1 and CE1, and between PE2 and CE1.
6. Configure the static routes on PE1 and PE2 that are destined for CE1. Then configure EFM
OAM extension for static routes, and import the static routes to BGP.
Data Preparation
l IP address of each physical interface
l MPLS LSR IDs of the PEs
l Names of the VPN instances, RDs, and VPN targets on the PEs
Procedure
Step 1 Configure IGP on the MPLS backbone network to implement device interworking on the
backbone network.
# Configure PE1.
[PE1-Pos1/0/0] ip address 100.1.1.1 24
[PE1-Pos1/0/0] quit
[PE1] interface pos 20/0
[PE1-Pos2//0] ip address 100.3.1.1 24
[PE1-Pos20/0] quit
[PE1] isis 1
[PE1-isis-1] quit
# Configure PE2.


[PE2-Pos1/0/0] ip address 100.2.1.1 24
[PE2-Pos1/0/0] quit
[PE2] interface pos 20/0
[PE2-Pos2/0/0] ip address 100.3.1.1 24
[PE2-Pos2/0/0] quit
[PE2] isis 1
[PE2-isis-1] quit
# Configure PE3.
[PE3-Pos1/0/0] ip address 100.1.1.2 24
[PE3-Pos1/0/0] quit
[PE3-Pos2/0/0] ip address 100.2.1.2 24
[PE3-Pos2/0/0] quit
[PE3] isis 1
[PE3-isis-1] quit
After the configuration, IS-IS neighbor relationships are set up between PE1, PE2, and PE3.
Run the display ip routing-table command. The command output shows that the PEs learn the
Loopback1 route from each other.
Take the display on PE1 as an example:

[PE1] display ip routing-table
------------------------------------------------------------------------------

4.4.4.4/32 ISIS 15 10 D 100.1.1.2 POS1/0/0
10.1.1.0/24 Direct 0 0 D 10.1.1.2
100.1.1.0/24 Direct 0 0 D 100.1.1.1 POS1/0/0
ISIS 15 20 D 100.1.1.2 POS1/0/0
Step 2 Configure basic MPLS functions and MPLS LDP on the MPLS backbone network and set up
LDP LSPs.
# Configure PE1.


[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-ldp] quit
[PE1-Pos1/0/0] mpls
[PE1-Pos1/0/0] quit
[PE1-Pos2/0/0] mpls
[PE1-Pos2/0/0] quit
# Configure PE2.
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-ldp] quit
[PE2-Pos1/0/0] mpls
[PE2-Pos1/0/0] quit
[PE2-Pos2/0/0] mpls
[PE2-Pos2/0/0] quit
# Configure PE3.
[PE3] mpls
[PE3-mpls] quit
[PE3] mpls ldp
[PE3-ldp] quit
[PE3-Pos1/0/0] mpls
[PE3-Pos1/0/0] quit
[PE3-Pos2/0/0] mpls
[PE3-Pos2/0/0] quit
ldp session command. The command output shows that the LDP session status is
Operational.
Take the display on PE1 as an example:
[PE1] display mpls ldp session

------------------------------------------------------------------------------
Peer-ID Status LAM SsnRole SsnAge KA-Sent/Rcv
------------------------------------------------------------------------------
------------------------------------------------------------------------------
LAM : Label Advertisement Mode SsnAge Unit : DDD:HH:MM
Step 3 Configure VPN instances on PE1 and PE2 so that CE1 can access both PEs.
# Configure PE1.


[PE1-GigabitEthernet3/0/0] ip binding vpn-instance vpna
# Configure PE2.
[PE2-GigabitEthernet3/0/0] ip binding vpn-instance vpna
# Configure CE1. Note that the IP addresses of the interfaces on the master and slave interface
boards are the same.
[CE1-GigabitEthernet1/0/0] ip address 10.1.1.1 24
[CE1-GigabitEthernet2/0/0] ip address 10.1.1.1 24
After the configuration, run the display ip vpn-instance verbose command on PEs. The
command output shows the configurations of VPN instances. In addition, you can find that PE1
and PE2 can ping CE1 successfully.
Take PE1 and CE1 as an example:

[PE1] display ip vpn-instance verbose
Total VPN-Instances configured : 1
VPN-Instance Name and ID : vpna, 1

Create date : 2008/12/27 15:42:43
Up time : 0 days, 00 hours, 04 minutes and 15 seconds
Route Distinguisher : 100:1
Export VPN Targets : 111:1
Import VPN Targets : 111:1
Label policy : label per route
The diffserv-mode Information is : uniform
The ttl-mode Information is : pipe
Interfaces : GigabitEthernet3/0/0
[PE1] ping -vpn-instance vpna 10.1.1.1

0.00% packet loss
Step 4 Enable EFM OAM extension between PE1 and CE1, and between PE2 and CE1.
# Configure PE1.
[PE1] efm enable


# Configure PE2.
[PE2] efm enable
# Configure CE1.
[CE1] efm enable
Step 5 Configure the static routes on PE1 and PE2 that are destined for CE1. Then configure EFM
OAM extension for static routes, and import the static routes to BGP.
# Configure PE1.
[PE1] ip route-static vpn-instance vpna 1.1.1.1 32 10.1.1.1 track efm-state
gigabitethernet 3/0/0
[PE1] bgp 100
[PE1-bgp-vpna] quit
[UPE] interface gigabitethernet 1/0/3
[UPE-GigabitEthernet1/0/2] efm enable
[UPE-GigabitEthernet1/0/2] quit
# Configure PE2.
[PE2] ip route-static vpn-instance vpna 1.1.1.1 32 10.2.1.1 track efm-state
gigabitethernet 3/0/0
[PE2] bgp 100
[PE2-bgp-vpna] quit
Step 6 Set up MP-IBGP peer relationships between PE1, PE2, and PE3.
# Configure PE1.
[PE1] bgp 100
[PE1-bgp] quit
# Configure PE2.
[PE2] bgp 100


[PE2-bgp] quit
# Configure PE3.
[PE3] bgp 100
[PE3-bgp] quit
After the configuration, run the display bgp peer command on the PEs. The command output
shows that peer relationships are set up between the PEs and the status of the peer relationships
is Established.
[PE1] display bgp peer
BGP local router ID : 2.2.2.2

Local AS number : 100
Total number of peers : 2 Peers in established state : 2
Peer V AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv
4.4.4.4 4 100 205 202 0 03:05:25 Established 0

3.3.3.3 4 100 197 254 0 03:06:54 Established 0

# # Run the display ip routing-table vpn-instance command on the PEs. The command output
shows that the static route exists in the routing table of each PE.
[PE2] display ip routing-table vpn-instance vpna
------------------------------------------------------------------------------
Routing Tables: vpna
1.1.1.1/32 Static 60 0 RD 10.1.1.1

10.1.1.0/24 Direct 0 0 D 10.1.1.2
10.2.1.0/24 BGP 255 0 RD 3.3.3.9
10.3.1.0/24 BGP 255 0 RD 4.4.4.4 POS1/0/0
10.3.1.2/32 BGP 255 0 RD 4.4.4.4 POS1/0/0

------------------------------------------------------------------------------
1.1.1.1/32 BGP 255 0 RD 1.1.1.1

10.1.1.0/24 BGP 255 0 RD 1.1.1.1
10.2.1.0/24 Direct 0 0 D 10.2.1.2

10.3.1.0/24 BGP 255 0 RD 4.4.4.4 POS1/0/0
10.3.1.2/32 BGP 255 0 RD 4.4.4.4 POS1/0/0
If the master/slave failover occurs on the interface boards of CE1, the gateway of CE1 also
changes from PE1 to PE2. The routing information is displayed as follows:
------------------------------------------------------------------------------
1.1.1.1/32 BGP 255 0 RD 3.3.3.9

10.1.1.0/24 Direct 0 0 D 10.1.1.2
10.2.1.0/24 BGP 255 0 RD 3.3.3.9
10.3.1.0/24 BGP 255 0 RD 4.4.4.4 POS1/0/0
10.3.1.2/32 BGP 255 0 RD 4.4.4.4 POS1/0/0
------------------------------------------------------------------------------
1.1.1.1/32 Static 60 0 RD 10.2.1.1

10.1.1.0/24 BGP 255 0 RD 1.1.1.1
10.2.1.0/24 Direct 0 0 D 10.2.1.2
10.3.1.0/24 BGP 255 0 RD 4.4.4.4 POS1/0/0
10.3.1.2/32 BGP 255 0 RD 4.4.4.4 POS1/0/0
----End
Configuration Files
#
sysname PE1
#
efm enable
#
#
mpls lsr-id 2.2.2.2
mpls
#
mpls ldp

#
isis 1
network-entity 10.0000.0000.0001.00
#
ip address 10.1.1.2 255.255.255.0
efm enable
#
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.3.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 4.4.4.4 enable
peer 3.3.3.3 enable
#
ipv4-family vpnv4
policy vpn-target
peer 3.3.3.3 enable
peer 4.4.4.4 enable
#
import-route direct
import-route static
#
ip route-static vpn-instance vpna 1.1.1.1 255.255.255.255 10.1.1.1 track efm-
state gigabitethernet 3/0/0
#
return
#
sysname PE2
#
efm enable
#
#
mpls lsr-id 3.3.3.3
mpls
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0002.00
#

ip address 10.2.1.2 255.255.255.0

efm enable
#
interface Pos1/0/0
link-protocol ppp
ip address 100.2.1.1 255.255.255.0
mpls
mpls ldp
#
interface Pos2/0/0
link-protocol ppp
ip address 100.3.1.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
bgp 100
#
ipv4-family unicast
peer 4.4.4.4 enable
peer 2.2.2.2 enable
#
ipv4-family vpnv4
policy vpn-target
peer 2.2.2.2 enable
peer 4.4.4.4 enable
#
import-route direct
import-route static
#
ip route-static vpn-instance vpna 1.1.1.1 255.255.255.255 10.2.1.1 track efm-
state gigabitethernet 3/0/0
#
return
#
sysname PE3
#
mpls lsr-id 4.4.4.4
mpls
#
mpls ldp
#
isis 1
network-entity 10.0000.0000.0003.00
#
interface Pos1/0/0
link-protocol ppp
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface Pos2/0/0
link-protocol ppp
ip address 100.2.1.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 4.4.4.4 255.255.255.255
#

bgp 100
#
ipv4-family unicast
peer 2.2.2.2 enable
peer 3.3.3.3 enable
#
ipv4-family vpnv4
policy vpn-target
peer 2.2.2.2 enable
peer 3.3.3.3 enable
#
return

#
sysname CE1
#
efm enable
#
ip address 10.1.1.1 255.255.255.0
efm enable
#
ip address 10.2.1.1 255.255.255.0
efm enable
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
ip route-static 0.0.0.0 0.0.0.0 10.1.1.2
ip route-static 0.0.0.0 0.0.0.0 10.2.1.2
#
return

Configuration Guide - Reliability 9 Y.1731 Configuration
9 Y.1731 Configuration
About This Chapter
Y.1731 is an OAM protocol at the network layer. It provides fault detection the same as that
provided by IEEE802.1ag and performance monitoring, such as frame loss measurement, frame
delay measurement, and AIS.
9.1 Introduction
9.2 Configuring Single-Ended Frame Loss Measurement on a VLL
In VLL networking, if at least one of the MEPs at both ends of a link does not support the CC
function, single-ended frame loss measurement can be configured for the link.
9.3 Configuring Dual-Ended Frame Loss Measurement on a VLL
In VLL networking, if the connectivity of a link and packet loss need to be detected and the
MEPs at both ends of a link support the CC function, dual-ended frame loss measurement can
be configured for the link.
9.4 Configuring One-Way Frame Delay Measurement on a VLL
In VLL networking, one-way frame delay measurement can be configured to measure the delay
in unidirectional frame transmission on a link.
9.5 Configuring Two-Way Frame Delay Measurement on a VLL
In VLL networking, if the clocks of the MEPs at both ends of a link are not synchronized and
the requirement for delay measurement is not high, two-way frame delay measurement can be
configured for the link.
9.6 Configuring Single-Ended Frame Loss Measurement on a VPLS Network
In VPLS networking, if at least one of the MEPs at both ends of a link does not support the CC
9.7 Configuring Dual-Ended Frame Loss Measurement on a VPLS Network
In VPLS networking, if the connectivity of a link and packet loss need to be detected and the
9.8 Configuring One-Way Frame Delay Measurement on a VPLS Network
In VPLS networking, one-way frame delay measurement can be configured to measure the delay

9.9 Configuring Two-Way Frame Delay Measurement on a VPLS Network

In VPLS networking, if the clocks of peer MEPs are not synchronized and the requirement for
delay measurement is not high, two-way frame delay measurement can be configured.
This section describes the typical deployment scenario of Y.1731, including the networking
requirements, configuration roadmap, and data preparation, and provides related configuration
files.

9.1 Introduction
9.1.1 Y.1731 Overview

Y.1731 is an Operation, Administration and Maintenance (OAM) protocol defined by the ITU-
T. It is used to implement end-to-end connectivity detection, loopback detection, and link trace
on Metro Ethernets (MEs). It also provides the test diagnosis and performance monitoring
functions such as frame loss measurement, frame delay measurement, frame jitter measurement,
and throughput measurement.
Introduction
Originally, Ethernet was mainly used in Local Area Networks (LANs), and had a poor OAM
capability. In addition, Ethernet supports only the network element-level management system
that cannot meet network management requirements of most network operators. After Ethernet
is widely used in MANs, the requirement on OAM becomes increasingly high.
Hierarchical Ethernet OAM needs to be provided based on the network architecture:

l 802.3ah, also known as Ethernet in the First Mile (EFM), is used to detect the link
connection of the last file. 802.3ah is link-level OAM.
l IEEE 802.1ag, also known as Connectivity Fault Management (CFM), defines protocols
and practices for OAM. IEEE 802.1ag Ethernet CFM protocols comprise three protocols
that work together to help administrators debug Ethernet networks. These protocols are
continuity check (CC), link trace (LT) and loopback (LB). CFM is network-level OAM
and is applicable to large-scaled end-to-end networking.
l Y.1731 is an OAM protocol defined by the ITU-T. It covers the contents defined by
IEEE802.1ag and combinations of OAM messages, including Remote Defect Indication
(RDI), Locked Signal (LCK), Test Signal, Automatic Protection Switching (APS),
Maintenance Communication Channel (MCC), Experimental (EXP), and Vendor Specific
(VSP) for fault management and frame loss measurement (LM) and delay measurement
( DM) for performance monitoring.
Basic Concepts and Principle

l Single-ended frame loss measurement
Frame loss measurement is performed by sending frames with ETH-LM information to a
peer Maintenance association End Point (MEP) and receiving frames with ETH-LM
information from the peer MEP. As shown in Figure 9-1, the process of single-ended frame
loss measurement is as follows:
1. The local MEP sends an ETH-LMM (a frame containing ETH-LM request
information) to the remote MEP. The ETH-LMM carries a transmit counter indicating
the time at which the message is sent by the local end.
2. After receiving the ETH-LMM, the remote MEP replies with an ETH-LMR (a frame
containing ETH-LM response information).
3. After receiving the ETH-LMR, the local MEP obtains corresponding measurement
information based on message contents and calculates the frame loss ratio.

Figure 9-1 Networking diagram of single-ended frame loss measurement
ETH-LMM
ETH-LMR
CE CE
Y.1731 PE CE
PE
CE P
CE
CE
ETH-LMM
ETH-LMR
l Dual-ended frame loss measurement

Frame loss measurement is performed by sending frames with ETH-LM information to a
peer MEP and receiving frames with ETH-LM information from the peer MEP. As shown
in Figure 9-2, the process of dual-ended frame loss measurement is as follows:
1. Each MEP sends a frame containing ETH-LM request information to remote MEPs.
Here, the frame containing ETH-LM request information is called a Continuity Check
Message (CCM).
2. Each MEP processes the received CCMs and measures the number of frames lost on
both the local and remote ends.
3. Each MEP obtains corresponding measurement information based on contents in the
CCMs and calculates frame loss ratios.
Figure 9-2 Networking diagram of dual-ended frame loss measurement
ETH-CCM
ETH-CCM
CE CE
CE Y.1731 PE CE
PE
P
CE
CE
l One-way frame delay measurement

One-way frame delay measurement is performed on end-to-end MEPs. A MEP receives a
DM frame and returns a Delay Measurement Reply (DMR) to carry out the one-way frame
delay measurement. As shown in Figure 9-3, the process of one-way frame delay
measurement is as follows:

1. A MEP periodically sends DM frames carrying TxTimeStampf.

2. After receiving a DM frame, the remote MEP calculates the one-way frame delay
based on the following formula:
Frame delay = RxTimef - TxTimeStampf
The frame delay variation, namely, frame jitter, can be calculated based on the frame delay.
Jitter: is used as a measure of the variability over time of the frame delay across a network,
and is the absolute difference value between two delays.
Figure 9-3 Networking diagram of one-way frame delay measurement

1DM PDU
CE CE
Y.1731 PE CE
PE
CE P
CE
CE
l Two-way frame delay measurement

Two-way frame delay measurement is commonly performed on end-to-end MEPs. A MEP
receives a Delay Measurement Message (DMM) and returns a DMR to carry out two-way
frame delay measurement. As shown in Figure 9-4, the process of two-way frame delay
measurement is as follows:
1. A MEP periodically sends DMMs carrying TxTimeStampf.
2. After receiving a DMM, the remote MEP adds the RxTimeStampf value (the time of
receiving the DMM) to the DMM, generates a DMR with the TxTimeStampb value
(the time of sending the DMR), and sends the frame to the requesting MEP. Every
field in the DMM is copied to the DMR, except that the source and destination MAC
addresses are swapped and the message type is changed from DMM to DMR.
3. After receiving a DMR, the MEP that sends a DMM calculates the two-way frame
delay based on the following formula:
Frame delay = (RxTimeb - TxTimeStampf) - (TxTimeStampb - RxTimeStampf)
The frame delay variation, namely, frame jitter, can be calculated based on the frame delay.
Jitter: is used as a measure of the variability over time of the frame delay across a network,
and is the absolute difference value between two delays.

Figure 9-4 Networking diagram of two-way frame delay measurement

DMM
CE CE
PE1 PE2 CE
CE
Y.1731
CE
CE
DMR
9.1.2 Y.1731 Features Supported by the NE80E/40E

This section describes the Y.1731 features supported by the NE80E/40E in terms of functions
and deployment scenarios.
The Y.1731 features supported by the NE80E/40E include single-ended frame loss
measurement, dual-ended frame loss measurement, one-way frame delay measurement, two-
way frame delay measurement applied to Virtual Leased Line (VLL), Virtual Private LAN
Service (VPLS) networking. Table 9-1 lists the functions and deployment scenarios of these
features. Select a function as needed.
NOTE
l Loss measurement or delay measurement takes effect only on LDP LSPs and TE LSPs between PEs
on public networks.
l Loss measurement cannot be performed on an Eth-Trunk interface of a PW between PEs.
Table 9-1 Functions supported by Y.1731

Functi Single-Ended Dual-Ended One-Way Two-Way Frame
on Frame Loss Frame Loss Frame Delay Delay
Measurement Measurement Measurement Measurement
Descrip Checks the Checks the Checks the Checks the quality of
tion quality of a link quality of a link quality of a link a link by measuring
by measuring by measuring by measuring the the delay in
packet loss on the packet loss on the delay in bidirectional frame
MEP at either MEPs at both unidirectional transmission over the
end of the link. ends of the link. frame link between peers
transmission MEPs.
over the link
between peer
MEPs.

Functi Single-Ended Dual-Ended One-Way Two-Way Frame

on Frame Loss Frame Loss Frame Delay Delay
Measurement Measurement Measurement Measurement
Deploy Single-ended frame loss One-way frame delay measurement or

ment measurement or dual-ended frame two-way frame delay measurement can be
Scenari loss measurement can be used to used to measure the delay in frame
o measure frame loss on a link as transmission on a link or monitor the
needed. performance of a link as needed.
l If the connectivity of a link and l If the clocks of the MEPs at both ends
packet loss need to be detected of a link are synchronized and the
and the MEPs at both ends of a requirement for the delay in frame
link support the CC function, transmission is high, one-way frame
dual-ended frame loss delay measurement can be used.
measurement can be l If the clocks of the MEPs at both ends
implemented. of a link are not synchronized and the
l If at least one of the MEPs at both requirement for the delay in frame
ends of a link does not support the transmission is low, two-way frame
CC function, single-ended frame delay measurement can be used.
loss measurement can be
implemented.
9.2 Configuring Single-Ended Frame Loss Measurement on

a VLL
In VLL networking, if at least one of the MEPs at both ends of a link does not support the CC

Before configuring single-ended frame loss measurement on a VLL, familiarize yourself with
This will help you complete the configuration task quickly and efficiently.
As shown in Figure 9-5, When a user considers that the quality of purchased Ethernet tunnel
services deteriorates or when an operator needs to conduct regular SLA monitoring, the
following functions of Y.1731 can be used to detect links:

Figure 9-5 Networking diagram for performance monitoring

Services Access Metro
DSLAM PE1 P PE2 BRAS
Core
Y.1731 Y.1731 Y.1731

MEP
MIP
This section describes how to configure single-ended frame loss measurement on an AC and a
PW in VLL networking.
Before configuring single-ended frame loss measurement on a VLL, complete the following
tasks:
l Configuring single-ended frame loss measurement on an PW
– Completing VLL-related configurations on PEs
For details, see the chapter "VLL Configuration" in the NE80E/40E Configuration
Guide - VPN.
– Completing CFM-related configurations and configuring the MEP type as inward
Data Preparation
To configure single-ended frame loss measurement on a VLL, you need the following data.
No. Data
1 Names of an MD and an MA
2 ID and type of a MEP and name of the interface where the MEP is located
3 VC ID of the VLL bound to an MA
4 Interval for sending packets and the number of sent packets
9.2.2 Binding an MA to a VLL

Binding an MA to a VLL is a prerequisite for configuring single-ended frame loss measurement,
dual-ended frame loss measurement,one-way frame delay measurement, or two-way frame delay
measurement on the VLL.

Context
VLL-based performance monitoring is L2VC-specific. Therefore, when deploying Y.1731, bind
an MA to an L2VC, and then collect performance statistics of the MA. Then, performance
statistics about a specified PW or AC will be available.
l To make dual-ended frame loss measurement on a PW, do as follows on the PEs at both
ends of a VLL:
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
An L2VC is bound to the MA.
NOTE
Table 9-2 Packet processing on an inbound interface
Inbound Interface Raw Encapsulation Tagged Encapsulation

Type (Ethernet Encapsulation) (VLAN Encapsulation)
Dot1q sub-interface Removes one tag. Keeps the tag unchanged.
Dot1q termination Removes one tag. Keeps the tag unchanged.

sub-interface
QinQ termination Removes the outer tag. Keeps both inner and outer tags
sub-interface (in unchanged.
symmetry mode)
QinQ termination Removes both the inner and Removes both inner and outer
sub-interface (in outer tags. tags, and then adds one tag.
asymmetry mode)

Table 9-3 Packet processing on an outbound interface
Outbound Raw Encapsulation Tagged Encapsulation

Interface Type (Ethernet Encapsulation) (VLAN Encapsulation)
Dot1q sub-interface Adds one tag. Replaces the VLAN ID in the tag
contained in a packet with the
local VLAN ID.
Dot1q termination Adds one tag. Replaces the VLAN ID in the tag
sub-interface contained in a packet with the
local VLAN ID.
QinQ termination Adds an outer tag. Replaces the VLAN ID in the

sub-interface (in outer tag contained in a packet
symmetry mode) with the local VLAN ID.
QinQ termination Adds two tags. Removes the outer tag and then
sub-interface (in adds two tags.
asymmetry mode)
----End
9.2.3 Configuring LMM Reception on a Remote MEP

When single-ended frame loss measurement is performed on a link, Loss Measurement Message
(LMM) reception needs to be configured on a remote MEP.
Context
Frame loss measurement is performed by sending frames with ETH-LM information to a remote
MEP and receiving frames with ETH-LM information from the remote MEP. To collect
performance statistics on a link, LMM reception needs to be configured on the remote MEP.
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
loss-measure single-ended receive [ 8021p { 8021p-value } &<1–3> ]
LMM reception is configured on a remote MEP.

NOTE
If 8021p 8021p-value is specified, frame loss measurement based on a specified 802.1p priority is
performed on the receiving device. If 8021p 8021p-value is not specified, frame loss measurement based
on all priorities is performed on the receiving device.
----End
9.2.4 Enabling Single-Ended Frame Loss Measurement on a VLL

Single-ended frame loss measurement on a VLL includes on-demand single-ended frame loss
measurement and proactive single-ended frame loss measurement.
Context
On-demand OAM refers to OAM actions that are initiated by manual intervention for a limited
time to carry out diagnostics. On-demand OAM results in singular or periodic OAM actions
during the diagnostics time. Proactive OAM refers to OAM actions that are carried out
continuously to permit proactive reporting of faults or performance results. Single-ended frame
loss measurement on a VLL includes on-demand single-ended frame loss measurement and
proactive single-ended frame loss measurement.
l To implement singular or periodic frame loss measurement on a PW, configure on-demand
single-end frame loss measurement on a VLL.
l To implement continual frame loss measurement on a PW, configure proactive single-
ended frame loss measurement on a VLL.
802.1p priorities carried by packets on a network are used to differentiate services, and
therefore different policies can be deployed for services. As shown in Figure 9-6, the
802.1p priority values contained in traffic passing through the P on the VLL are 1 and 2.
Frame loss measurement is performed for the link between PE1 and PE2. Assume that
traffic (with the priority value of 2) that is not involved in frame loss measurement is sent
out after frame loss measurement is enabled. The traffic is forwarded preferentially because
its priority is high. As a result, the traffic (with the priority value of 1) that is involved in
frame loss measurement fails to reach PE2 in time, causing incorrect frame loss statistics.
802.1p-priority-based single-ended frame loss measurement can be configured for the VLL
for accurate proactive frame loss tests.
NOTE
The configuration of 802.1p priority mapping for AC-side packets allows flexible frame loss
measurement on PWs.
l Priority mapping based on simple traffic classification can map a traffic priority on one type of
network to that on another type of network. This enables traffic to be transmitted on another type
of network based on the previous priority or the priority configured by users. After receiving
packets, a PE maps external priorities to internal priorities and re-marks DiffServ CoS values
and colors. Before sending packets, the PE maps the internal priorities to external priorities.
l One-way frame loss measurement on a VLL can be configured based on simple traffic
classification. Priority mappings are set on PEs to change priorities in packets or re-classify the
packets. This allows flexible frame loss measurement.

Figure 9-6 Networking diagram for priority-based frame loss measurement on a VLL
CE1 P CE2
PE1 PE2
User User
Network Y.1731 Network
MEP
Priority 1
Priority 2
Procedure
l Enable on-demand single-ended frame loss measurement.
NOTE
Do as follows on the device that initiates on-demand single-ended frame loss measurement on a PW:
– Enable on-demand single-ended frame loss measurement on a PW.
1. Run:
system-view

2. Run:
cfm md md-name

3. Run:
ma ma-name

4. Run:
loss-measure single-ended mep mep-id mep-id [ mac mac-address | remote-
mep mep-id mep-id ] interval { 1000 | 10000 } count count-value
On-demand single-ended frame loss measurement is enabled on a PW.

NOTE
l If the local MEP has not learned the MAC address of the remote MEP, specify the
destination MAC address for the single-ended frame loss measurement.
l If the local MEP has learned the MAC address of the remote MEP or the remote MEP
has been bound to the MAC address of the local MEP, specify the remote MEP ID for
the single-ended frame loss measurement.
l Enable proactive single-ended frame loss measurement.
NOTE
Proactive single-ended frame loss measurement is PW-specific. Do as follows on the device that
initiates proactive single-ended frame loss measurement on a PW:

1. Run:
system-view

2. Run:
cfm md md-name

3. Run:
ma ma-name

4. Run:
loss-measure single-ended continual mep mep-id mep-id [ mac mac-address |
remote-mep mep-id mep-id ] interval 30000 [ 8021p { 8021p-value } &<1–3> ]
Proactive single-ended frame loss measurement is enabled on a PW.

If 8021p 8021p-value is specified, frame loss measurement based on a specified
802.1p priority is performed for the PW. If 8021p 8021p-value is not specified, frame
loss measurement based on all priorities is performed for the PW.
NOTE
l If the local MEP has learned the MAC address of the remote MEP or the remote MEP has
been bound to the MAC address of the local MEP, specify the remote MEP ID for the
single-ended frame loss measurement.
----End

After configuring single-ended frame loss measurement on a VLL, you can view statistics about
frame loss at one end of a link.
Prerequisite
The configurations of single-ended frame loss measurement on a VLL are complete.
Procedure
l Run the display y1731 statistic-type single-loss md md-name ma ma-name [ 8021p
{ 8021p-value } &<1–3> ] [ count count-value ] command to check Y.1731 performance
statistics.
NOTE
Currently, you can check the configuration of single-ended frame loss measurement on a VLL by
using the NMS that matches the current device version.
----End
Example
Run the display y1731 statistic-type command, and you can view information about single-
ended frame loss measurement.
<HUAWEI> display Y.1731 statistic-type single-loss md md1 ma ma1
Latest single-ended loss statistics:
Index Local-loss ratio Remote-loss ratio

1 20 50.0000% 30 75.0000%
2 20 50.0000% 30 75.0000%
3 20 50.0000% 30 75.0000%
4 20 50.0000% 30 75.0000%
5 20 50.0000% 30 75.0000%
6 20 50.0000% 30 75.0000%
7 20 50.0000% 30 75.0000%
8 20 50.0000% 30 75.0000%
9 20 50.0000% 30 75.0000%
10 20 50.0000% 30 75.0000%
11 20 50.0000% 30 75.0000%
12 20 50.0000% 30 75.0000%
13 20 50.0000% 30 75.0000%
14 20 50.0000% 30 75.0000%
<HUAWEI> display y1731 statistic-type single-loss md md1 ma ma1 8021p 1 2
Latest single-ended loss statistics of 802.1p 1:
1 20 50.0000% 30 75.0000%
2 20 50.0000% 30 75.0000%
3 20 50.0000% 30 75.0000%
4 20 50.0000% 30 75.0000%
5 20 50.0000% 30 75.0000%
6 20 50.0000% 30 75.0000%
7 20 50.0000% 30 75.0000%
8 20 50.0000% 30 75.0000%
9 20 50.0000% 30 75.0000%
10 20 50.0000% 30 75.0000%
11 20 50.0000% 30 75.0000%
12 20 50.0000% 30 75.0000%
13 20 50.0000% 30 75.0000%
14 20 50.0000% 30 75.0000%
15 20 50.0000% 30 75.0000%
16 20 50.0000% 30 75.0000%
17 20 50.0000% 30 75.0000%
18 20 50.0000% 30 75.0000%
19 20 50.0000% 30 75.0000%
20 20 50.0000% 30 75.0000%
21 20 50.0000% 30 75.0000%
22 20 50.0000% 30 75.0000%
23 20 50.0000% 30 75.0000%
24 20 50.0000% 30 75.0000%
25 20 50.0000% 30 75.0000%
26 20 50.0000% 30 75.0000%
27 20 50.0000% 30 75.0000%
28 20 50.0000% 30 75.0000%
29 20 50.0000% 30 75.0000%
30 20 50.0000% 30 75.0000%
Latest single-ended loss statistics of 8021p 2:
1 20 50.0000% 30 75.0000%
2 20 50.0000% 30 75.0000%
3 20 50.0000% 30 75.0000%
4 20 50.0000% 30 75.0000%
5 20 50.0000% 30 75.0000%
6 20 50.0000% 30 75.0000%
7 20 50.0000% 30 75.0000%
8 20 50.0000% 30 75.0000%
9 20 50.0000% 30 75.0000%
10 20 50.0000% 30 75.0000%
11 20 50.0000% 30 75.0000%
12 20 50.0000% 30 75.0000%
13 20 50.0000% 30 75.0000%
14 20 50.0000% 30 75.0000%
15 20 50.0000% 30 75.0000%
16 20 50.0000% 30 75.0000%
17 20 50.0000% 30 75.0000%
18 20 50.0000% 30 75.0000%
19 20 50.0000% 30 75.0000%
20 20 50.0000% 30 75.0000%

21 20 50.0000% 30 75.0000%
22 20 50.0000% 30 75.0000%
23 20 50.0000% 30 75.0000%
24 20 50.0000% 30 75.0000%
25 20 50.0000% 30 75.0000%
26 20 50.0000% 30 75.0000%
27 20 50.0000% 30 75.0000%
28 20 50.0000% 30 75.0000%
29 20 50.0000% 30 75.0000%
30 20 50.0000% 30 75.0000%
9.3 Configuring Dual-Ended Frame Loss Measurement on a

VLL
In VLL networking, if the connectivity of a link and packet loss need to be detected and the

Before configuring dual-ended frame loss measurement on a VLL, familiarize yourself with the
can help you complete the configuration task quickly and efficiently.

Core
Y.1731 Y.1731 Y.1731

MEP
MIP

This section describes how to configure dual-ended frame loss measurement on a PW in VLL
networking.
Before configuring dual-ended frame loss measurement on a VLL, complete the following tasks:
l Configuring dual-ended frame loss measurement on a PW
– Completing VLL-related configurations
Guide - VPN.
Data Preparation
To configure dual-ended frame loss measurement on a VLL, you need the following data.
No. Data
3 ID of a remote MEP and MAC address of the interface where the remote MEP is
located
4 Interval at which a MEP sends CCMs in an MA

Context
ends of a VLL:
Procedure
Step 1 Run:
system-view

Step 2 Run:

cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
NOTE


sub-interface
symmetry mode)
asymmetry mode)

local VLAN ID.
local VLAN ID.



asymmetry mode)
----End
9.3.3 Enabling Dual-Ended Frame Loss Measurement on a VLL

Dual-ended frame loss measurement on a VLL is implemented on the MEPs at both ends of the
VLL to measure frame loss and check the connectivity of the VLL.
Context
Proactive OAM refers to OAM actions that are carried out continuously to permit proactive
reporting of faults or performance results. Dual-ended frame loss measurement on a VLL is
proactive OAM.
l To make dual-ended frame loss measurement on a PW between PEs, do as follows on the
PEs:
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

Step 4 Run:
loss-measure dual-ended continual mep mep-id mep-id remote-mep mep-id mep-id
Dual-ended frame loss measurement is enabled on a VLL.

Frame loss measurement on a VLL is usually deployed on end-to-end MEPs. In Y.1731, frame
loss statistics are collected based on the transmit and receive counters carried by CCMs. Dual-
ended frame loss measurement on a VLL can be successfully performed only when the remote
MEP is in the Up state.
----End

After configuring dual-ended frame loss measurement on a VLL, you can view statistics about
frame loss at both ends of a link.

Prerequisite
The configurations of dual-ended frame loss measurement on a VLL are complete.
Procedure
l Run the display y1731 statistic-type dual-loss md md-name ma ma-name [ count count-
value ] command to check Y.1731 performance statistics.
NOTE
Currently, you can check the configuration of dual-ended frame loss measurement on a VLL by using
the NMS that matches the current device version.
----End
Example
Run the display y1731 statistic-type command, and you can view information about dual-ended
frame loss measurement.
<HUAWEI> display y1731 statistic-type dual-loss md md1 ma ma1
Latest dual-ended loss statistics:
1 4294967295 100.0000% 4294967295 100.0000%
2 4294967295 100.0000% 4294967295 100.0000%
3 4294967295 100.0000% 4294967295 100.0000%
4 4294967295 100.0000% 4294967295 100.0000%
5 4294967295 100.0000% 4294967295 100.0000%
6 4294967295 100.0000% 4294967295 100.0000%
7 4294967295 100.0000% 4294967295 100.0000%
8 4294967295 100.0000% 4294967295 100.0000%
9 4294967295 100.0000% 4294967295 100.0000%
10 4294967295 100.0000% 4294967295 100.0000%
11 4294967295 100.0000% 4294967295 100.0000%
9.4 Configuring One-Way Frame Delay Measurement on a

VLL
In VLL networking, one-way frame delay measurement can be configured to measure the delay

Before configuring one-way frame delay measurement on a VLL, familiarize yourself with the
will help you complete the configuration task quickly and efficiently.


Core
Y.1731 Y.1731 Y.1731

MEP
MIP
This section describes how to configure one-way frame delay measurement on a PW in VLL
networking.
Before configuring one-way frame delay measurement on a VLL, complete the following tasks:
l Configuring one-way frame delay measurement on a PW
Guide - VPN.
Data Preparation
To configure one-way frame delay measurement on a VLL, you need the following data.
No. Data
located


Context
ends of a VLL:
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
NOTE


sub-interface
symmetry mode)


asymmetry mode)

local VLAN ID.
local VLAN ID.

asymmetry mode)
----End
9.4.3 Configuring DM Frame Reception on the Remote Device

When one-way frame delay measurement is configured for a link, DM frame reception needs to
be configured on a remote device.
Context
l To make one-way frame delay measurement on a PW, do as follows on a remote PE:
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name


Step 4 Run the following commands as needed:
l To make proactive one-way frame delay measurement on a PW, run the delay-measure one-
way continual receive [ 8021p { 8021p-value } &<1–3> ] command to configure DM frame
reception on a remote device.
NOTE
If 8021p 8021p-value is specified, one-way delay measurement based on a specified 802.1p priority value
is performed on the receiving device. If 8021p 8021p-value is not specified, one-way delay measurement
based on all 802.1p priorities is performed on the receiving device.
l To make on-demand one-way frame delay measurement on a PW, run the delay-measure
one-way receive command to configure DM frame reception on a remote device.
----End
9.4.4 Enabling One-Way Frame Delay Measurement on a VLL

VLLs implements point-to-point VPNs. To make accurate statistics of the delay in unidirectional
frame transmission on a PW or an AC in VLL networking, configure one-way frame delay
measurement.
Context
continuously to permit proactive reporting of faults or performance results. One-way frame delay
measurement on a VLL includes on-demand one-way frame delay measurement and proactive
one-way frame delay measurement.
l To implement singular or periodic frame delay measurement on a PW in VLL networking,
configure on-demand one-way frame delay measurement.
l To implement continual frame delay measurement on a PW in VLL networking, configure
proactive one-way frame delay measurement.
802.1p priority values contained in traffic passing through the P on the VLL are 1 and 2.
One-way frame delay measurement is performed for the link between PE1 and PE2.
Assume that traffic (with the priority value of 2) that is not involved in frame delay
measurement is sent out after one-way frame delay measurement is enabled. The traffic is
forwarded preferentially, because its priority is high. As a result, the traffic (with the priority
value of 1) that is involved in frame delay measurement fails to reach PE2 in time, causing
incorrect frame delay statistics.
802.1p-priority-based one-way frame delay measurement can be configured for the VLL
for accurate proactive frame delay tests.

NOTE
The configuration of 802.1p priority mapping for AC-side packets allows flexible frame delay
measurement on PWs.
l One-way frame delay measurement on a VLL can be configured based on simple traffic
packets. This allows flexible frame delay measurement.
CE1 P CE2
PE1 PE2
User User
MEP
Priority 1
Priority 2
Procedure
l Enable on-demand one-way frame delay measurement.
NOTE
Do as follows on the device that initiates one-way frame delay measurement on a PW:
– Enable on-demand one-way frame delay measurement on a PW.
1. Run:
system-view

2. Run:
cfm md md-name

3. Run:
ma ma-name

4. Run:
delay-measure one-way mep mep-id mep-id { mac mac-address | remote-
mep mep-id mep-id } interval { 1000 | 10000 } count count-value
On-demand one-way frame delay measurement is enabled on a PW.

If the local MEP has not learned the MAC address of the remote MEP, specify the
destination MAC address for the one-way frame delay measurement.
If the local MEP has learned the MAC address of the remote MEP or the remote
MEP has been bound to the MAC address of the local MEP, specify the remote
MEP ID for the one-way frame delay measurement.
l Enable proactive one-way frame delay measurement.
NOTE
Proactive one-way frame delay measurement is PW-specific. Do as follows on the device that initiates
one-way frame delay measurement on a PW:
1. Run:
system-view

2. Run:
cfm md md-name

3. Run:
ma ma-name

4. Run:
delay-measure one-way continual mep mep-id mep-id { mac mac-address |
remote-mep mep-id mep-id } interval 1000 [ 8021p { 8021p-value } &<1–3> ]
Proactive one-way frame delay measurement is enabled on a PW.

If 8021p 8021p-value is specified, frame delay measurement based on a specified
802.1p priority is performed for a PW. The interval at which frame delay measurement
is performed is 3000 ms. If 8021p 8021p-value is not specified, frame delay
measurement based on all priorities is performed for the PW.
If the local MEP has learned the MAC address of the remote MEP or the remote MEP
has been bound to the MAC address of the local MEP, specify the remote MEP ID
for the one-way frame delay measurement.
----End

After one-way frame delay measurement is configured on a VLL, you can view statistics about
the delay in unidirectional frame transmission.
Prerequisite
The configurations of one-way frame delay measurement on a VLL are complete.
Procedure
l Run the display y1731 statistic-type oneway-delay md md-name ma ma-name [ 8021p
{ 8021p-value } &<1–3> ] [count value ] command to check Y.1731 performance statistics.

NOTE
Currently, you can check the configuration of one-way frame delay measurement on a VLL by using the
NMS that matches the current device version.
----End
Example
Run the display y1731 statistic-type command on the device where the MEP is located, and
you can view the configured delay and frame jitter.
<HUAWEI> display y1731 statistic-type oneway-delay md md1 ma ma1
Latest one-way delay statistics:

Index One-way delay(usec) Delay variation(usec)
1 20000 0
2 20000 0
3 20000 0
4 30000 10000
5 10000 20000
6 10000 0
7 10000 0
8 10000 0
9 20000 10000
10 20000 0
<HUAWEI>display y1731 statistic-type oneway-delay md md1 ma ma1 8021p 1 2
Latest one-way delay statistics of 802.1p 1:
1 0 0
2 0 0
3 20000 20000
4 10000 10000
5 20000 10000
6 10000 10000
7 20000 10000
8 10000 10000
9 20000 10000
10 10000 10000
11 20000 10000
---------------------------------------------------
Latest one-way delay statistics of 8021p 2:
1 20000 0
2 10000 10000
3 10000 0
4 20000 10000
5 10000 10000
6 20000 10000
7 10000 10000
8 20000 10000
9 10000 10000
10 20000 10000
11 10000 10000
9.5 Configuring Two-Way Frame Delay Measurement on a

VLL
In VLL networking, if the clocks of the MEPs at both ends of a link are not synchronized and
the requirement for delay measurement is not high, two-way frame delay measurement can be
configured for the link.


Before configuring two-way frame delay measurement on a VLL, familiarize yourself with the
will help you complete the configuration task quickly and efficiently.

Core
Y.1731 Y.1731 Y.1731

MEP
MIP
This section describes how to configure two-way frame delay measurement ona PW in VLL
networking.
Before configuring two-way frame delay measurement on a VLL, complete the following tasks:
l Configuring two-way frame delay measurement on a PW
Guide - VPN.
Data Preparation
To configure two-way frame delay measurement on a VLL, you need the following data.

No. Data
located

Context
ends of a VLL:
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

Step 4 Run:
NOTE



sub-interface
symmetry mode)
asymmetry mode)

local VLAN ID.
local VLAN ID.

asymmetry mode)
----End
9.5.3 Configuring DMM Reception on a Remote Device

Two-way frame delay measurement can work normally only when DMM reception is configured
on a remote device.
Context
Do as follows on the device where the remote MEP is located:

Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
delay-measure two-way receive [ 8021p { 8021p-value } &<1–3> ]
DMM reception is configured on a remote device.
If 8021p 8021p-value is specified, two-way delay measurement based on a specified 802.1p

priority value is performed on the receiving device. If 8021p 8021p-value is not specified, two-
way delay measurement based on all 802.1p priorities is performed on the receiving device.
----End
9.5.4 Enabling Two-Way Frame Delay Measurement on a VLL

VLLs implement point-to-point VPNs. To make accurate statistics of the delay in bidirectional
frame transmission on a PW or an AC, configure two-way frame delay measurement on a VLL.
Context
continuously to permit proactive reporting of faults or performance results. Two-way frame
delay measurement on a VLL includes on-demand two-way frame delay measurement and
proactive two-way frame delay measurement.
l To implement singular or periodic frame delay measurement on a PW, configure on-
demand two-way frame delay measurement on a VLL.
l To implement continual frame delay measurement on a PW, configure proactive two-way
frame delay measurement on a VLL.
802.1p priority values contained in traffic passing through the P are 1 and 2.
Two-way frame delay measurement is performed for the link between PE1 and PE2.
Assume that traffic (with the priority value of 2) that is not involved in frame delay
measurement is sent out after two-way frame delay measurement is enabled. The traffic is
forwarded preferentially, because its priority is high. As a result, the traffic (with the priority
value of 1) that is involved in frame delay measurement fails to reach PE2 in time, causing
incorrect frame delay statistics.

802.1p-priority-based two-way frame delay measurement can be configured for the VLL
for accurate proactive frame delay tests.
NOTE
The configuration of 802.1p priority mapping for AC-side packets allows flexible frame delay
measurement on PWs.
l One-way frame delay measurement on a VLL can be configured based on simple traffic
packets. This allows flexible frame delay measurement.
CE1 P CE2
PE1 PE2
User User
MEP
Priority 1
Priority 2
Procedure
l Enable on-demand two-way frame delay measurement.
NOTE
Do as follows on the device that initiates two-way frame delay measurement on a PW:
– 1. Run:
system-view

2. Run: cfm md md-name The MD view is displayed.
3. Run:
ma ma-name

4. Run:
delay-measure two-way mep mep-id mep-id { mac mac-address | remote-mep
mep-id mep-id } interval { 1000 | 10000 } count count-value
On-demand two-way frame delay measurement is enabled on a PW.

destination MAC address for the two-way frame delay measurement.
If the local MEP has learned the MAC address of the remote MEP or the remote
MEP has been bound to the MAC address of the local MEP, specify the remote
MEP ID for the two-way frame delay measurement.
l Configure proactive two-way frame delay measurement.
NOTE
Proactive two-way frame delay measurement is PW-specific. Do as follows on the device that initiates
two-way frame delay measurement on a PW:
1. Run:
system-view

2. Run:
cfm md md-name

3. Run:
ma ma-name

4. Run:
delay-measure two-way continual mep mep-id mep-id { mac mac-address |
remote-mep mep-id mep-id } interval 30000 [ 8021p { 8021p-value } &<1–3> ]
Proactive two-way frame delay measurement is enabled on a PW.

If 8021p 8021p-value, frame loss measurement based on a specified 802.1p priority
is performed for the PW. If 8021p 8021p-value is not specified, frame delay
measurement based on all priorities is performed for the PW.
If the local MEP has learned the MAC address of the remote MEP or the remote MEP
has been bound to the MAC address of the local MEP, specify the remote MEP ID
for the two-way frame delay measurement.
----End

After two-way frame delay measurement is configured on a VLL, you can view statistics of the
delay in bidirectional frame transmission.
Prerequisite
The configurations of two-way frame delay measurement on a VLL are complete.
Procedure
l Run the display y1731 statistic-type twoway-delay md md-name ma ma-name [ 8021p
{ 8021p-value } &<1–3> ] [ count value ]command to check Y.1731 performance statistics.

NOTE
Currently, you can check the configuration of two-way frame delay measurement on a VLL by using the
NMS that matches the current device version.
----End
Example
you can view information about two-way frame delay measurement and frame jitter.
<HUAWEI>display y1731 statistic-type twoway-delay md md1 ma ma1 8021p 2 3

Index Two-way delay(usec) Delay variation(usec)
1 0 0
2 0 0
3 0 0
4 0 0
---------------------------------------------------
1 0 0
2 0 0
3 0 0
4 0 0
<HUAWEI> display y1731 statistic-type twoway-delay md md1 ma ma1
Two-way delay measurement statistics:
1 20000 0
2 20000 0
3 10000 10000
4 20000 10000
5 10000 10000
6 20000 10000
7 10000 10000
8 10000 10000
9 20000 10000
10 10000 10000
11 20000 10000
12 20000 0
13 20000 0
14 30000 10000
15 20000 10000
16 20000 0
9.6 Configuring Single-Ended Frame Loss Measurement on

a VPLS Network
In VPLS networking, if at least one of the MEPs at both ends of a link does not support the CC

Before configuring single-ended frame loss measurement on a VPLS network, 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 efficiently.


Core
Y.1731 Y.1731 Y.1731

MEP
MIP
This section describes how to configure single-ended frame loss measurement a PW in VPLS
networking.
Before configuring single-ended frame loss measurement on a VPLS network, complete the
following tasks:
l Configuring single-ended frame loss measurement on an PW
– Completing VPLS-related configurations
For details, see the chapter "VPLS Configuration" in the NE80E/40E Configuration
Guide - VPN.
Data Preparation
To configure single-ended frame loss measurement on a VPLS network, you need the following
data.
No. Data

No. Data
3 Name of the VSI bound to an MA
4 Interval for sending packets and number of sent packets
9.6.2 Binding an MA to a VPLS Network

Binding an MA to a VPLS network is a prerequisite for configuring single-ended frame loss
measurement, dual-ended frame loss measurement, one-way frame delay measurement, or two-
way frame delay measurement on the VPLS network.
Context
VPLS-based performance monitoring function is VSI-specific. Therefore, when deploying Y.
1731, bind an MA to a specified VSI, and then collect performance statistics of the MA. Then,
performance statistics about a specified PW or AC will be available.
l To make single-ended frame loss measurement on a PW between PEs on a VPLS network,
do as follows on the PEs:
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
map vsi vsi-name
The MA is bound to a VSI.
----End
9.6.3 Configuring LMM Reception on a Remote MEP

When single-ended frame loss measurement is performed on a link, Loss Measurement Message
(LMM) reception needs to be configured on a remote MEP.

Context
Frame loss measurement is performed by sending frames with ETH-LM information to a remote
MEP and receiving frames with ETH-LM information from the remote MEP. To collect
performance statistics on a link, LMM reception needs to be configured on the remote MEP.
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

Step 4 Run:
loss-measure single-ended receive [ 8021p { 8021p-value } &<1–3> ]
LMM reception is configured on a remote MEP.
NOTE
If 8021p 8021p-value is specified, frame loss measurement based on a specified 802.1p priority is
performed on the receiving device. If 8021p 8021p-value is not specified, frame loss measurement based
on all priorities is performed on the receiving device.
----End
9.6.4 Enabling Single-Ended Frame Loss Measurement on a VPLS

Network
Single-ended frame loss measurement on a VPLS network is on-demand OAM.
Context
during the diagnostics time. To implement singular or periodic frame loss measurement on a
PW , configure on-demand single-end frame loss measurement on a VPLS network.
l To make single-ended frame loss measurement on a PW, do as follows on the PE that
initiates the frame loss measurement:
Procedure
l Enable on-demand single-ended frame loss measurement on a PW.
1. Run:
system-view


2. Run:
cfm md md-name

3. Run:
ma ma-name

4. Run:
loss-measure single-ended mep mep-id mep-id [ mac mac-address | remote-mep
mep-id mep-id ] interval { 1000 | 10000 } count count-value [ peer-ip peer-
ip [ vc-id vc-id ] ]
On-demand single-ended frame loss measurement is enabled on a PW.

NOTE
been bound to the MAC address of the local MEP, specify the remote MEP ID for the
single-ended frame loss measurement.
----End

After configuring single-ended frame loss measurement on a VPLS network, you can view
statistics about frame loss at one end of a link.
Prerequisite
The configurations of single-ended frame loss measurement on a VPLS network are complete.
Procedure
l Run the display y1731 statistic-type single-loss md md-name ma ma-name [ count count-
NOTE
Currently, you can check the configuration of single-ended frame loss measurement on a VPLS
network by using the NMS that matches the current device version.
----End
Example
Run the display y1731 statistic-type command, and you can view information about single-
ended frame loss measurement.
<HUAWEI> display Y.1731 statistic-type single-loss md md1 ma ma1
1 20 50.0000% 30 75.0000%
2 20 50.0000% 30 75.0000%
3 20 50.0000% 30 75.0000%
4 20 50.0000% 30 75.0000%
5 20 50.0000% 30 75.0000%
6 20 50.0000% 30 75.0000%
7 20 50.0000% 30 75.0000%

8 20 50.0000% 30 75.0000%
9 20 50.0000% 30 75.0000%
10 20 50.0000% 30 75.0000%
11 20 50.0000% 30 75.0000%
12 20 50.0000% 30 75.0000%
13 20 50.0000% 30 75.0000%
14 20 50.0000% 30 75.0000%
9.7 Configuring Dual-Ended Frame Loss Measurement on a

VPLS Network
In VPLS networking, if the connectivity of a link and packet loss need to be detected and the

Before configuring dual-ended frame loss measurement on a VPLS network, familiarize yourself
data. This will help you complete the configuration task quickly and efficiently.

Core
Y.1731 Y.1731 Y.1731

MEP
MIP

This section describes how to configure dual-ended frame loss measurement a PW in VPLS
networking.
Before configuring dual-ended frame loss measurement on a VPLS network, complete the
following tasks:
l Configuring dual-ended frame loss measurement on a PW
Guide - VPN.
Data Preparation
To configure dual-ended frame loss measurement on a VPLS network, you need the following
data.
No. Data
3 ID of a remote MEP and bridge MAC address of the device where the remote MEP
is located

Context
Procedure
Step 1 Run:
system-view


Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

Step 4 Run:
map vsi vsi-name
----End
9.7.3 Enabling Dual-Ended Frame Loss Measurement on a VPLS

Network
Dual-ended frame loss measurement on a VPLS network is implemented on the MEPs at both
ends of a link to measure frame loss and check the connectivity of the link.
Context
Proactive OAM refers to OAM actions that are carried out continuously to permit proactive
reporting of faults or performance results. Dual-ended frame loss measurement on a VPLS is
proactive OAM.
l To make dual-ended frame loss measurement on a PW between PEs on a VPLS network,
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

Step 4 Enable dual-ended frame loss measurement on a VPLS network.
l To enable dual-ended frame loss measurement on a PW, run the loss-measure dual-ended
continual mep mep-id mep-id remote-mep mep-id mep-id peer-ip peer-ip [ vc-id vc-id ]
command on the PEs at both ends of the PW.
----End


After configuring dual-ended frame loss measurement on a VPLS network, you can view
statistics about frame loss at both ends of a link.
Prerequisite
The configurations of dual-ended frame loss measurement on a VPLS network are complete.
Procedure
l Run the display y1731 statistic-type dual-loss md md-name ma ma-name [ count count-
NOTE
Currently, you can check the configuration of dual-ended frame loss measurement on a VPLS network by
using the NMS that matches the current device version.
----End
Example
Run the display y1731 statistic-type command, and you can view information about dual-ended
<HUAWEI> display y1731 statistic-type dual-loss md md1 ma ma1 peer-ip 1.1.1.1 vc-id
2
1 4294967295 100.0000% 4294967295 100.0000%
2 4294967295 100.0000% 4294967295 100.0000%
3 4294967295 100.0000% 4294967295 100.0000%
4 4294967295 100.0000% 4294967295 100.0000%
5 4294967295 100.0000% 4294967295 100.0000%
6 4294967295 100.0000% 4294967295 100.0000%
7 4294967295 100.0000% 4294967295 100.0000%
8 4294967295 100.0000% 4294967295 100.0000%
9 4294967295 100.0000% 4294967295 100.0000%
10 4294967295 100.0000% 4294967295 100.0000%
11 4294967295 100.0000% 4294967295 100.0000%
9.8 Configuring One-Way Frame Delay Measurement on a

VPLS Network
In VPLS networking, one-way frame delay measurement can be configured to measure the delay

Before configuring one-way frame delay measurement on a VPLS network, familiarize yourself
data. This will help you complete the configuration task quickly and correctly.


Core
Y.1731 Y.1731 Y.1731

MEP
MIP
This section describes how to configure one-way frame delay measurement on a PW in VPLS
networking.
Before configuring one-way frame delay measurement on a VPLS network, complete the
following tasks:
l Configuring one-way frame delay measurement on a PW

Guide - VPN.
Data Preparation
To configure one-way frame delay measurement on a VPLS network, you need the following
data.

No. Data
located

Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
map vsi vsi-name
----End
9.8.3 Configuring DM Frame Reception on a Remote Device

When one-way frame delay measurement is configured for a link, DM frame reception needs to
be configured on a remote device.

Context
l To make one-way frame delay measurement on a PW, do as follows on a remote PE:
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

l During the configuration of one-way frame delay measurement on a PW, run the delay-
measure one-way receive peer-ip peer-ip vc-id vc-id command to configure DM frame
reception.
----End
9.8.4 Enabling One-Way Frame Delay Measurement on a VPLS

Network
VPLS provides MP2MP VPNs so that there may be multiple PWs between devices configured
with the same VSI. To make accurate statistics of the delay in unidirectional frame transmission
over a PW, configure one-way frame delay measurement on a VPLS network.
Context
during the diagnostics time. One-way frame delay measurement on a VPLS network is on-
demand OAM. To implement singular or periodic frame delay measurement on a PW, configure
on-demand one-way frame delay measurement on a VPLS network.
l To make one-way frame delay measurement on a PW, do as follows on the PE that initiates
the frame delay measurement:
Procedure
l Enable on-demand one-way frame delay measurement on a PW.
1. Run:
system-view

2. Run:
cfm md md-name


3. Run:
ma ma-name

4. Run:
delay-measure one-way mep mep-id mep-id { mac mac-address | remote-mep
mep-id mep-id } interval { 1000 | 10000 } count count-value [ peer-ip peer-
ip [ vc-id vc-id ] ]
On-demand one-way frame delay measurement is enabled on a PW.

NOTE
been bound to the MAC address of the local MEP, specify the remote MEP ID for the one-
way frame delay measurement.
----End

After one-way frame delay measurement is configured on a VPLS network, you can view
statistics about the delay in unidirectional frame transmission.
Prerequisite
The configurations of one-way frame delay measurement on a VPLS network are complete.
Procedure
l Run the display y1731 statistic-type oneway-delay md md-name ma ma-name peer-ip
ip-address [ count count-value ]command to check Y.1731 performance statistics.
----End
Example
you can view the value of One-way delay and frame jitter.
<HUAWEI> display y1731 statistic-type oneway-delay md md1 ma ma1 peer-ip 1.1.1.1
1 10000 0
2 10000 0
3 10000 0
4 20000 10000
5 10000 10000
6 20000 10000
7 20000 0
9.9 Configuring Two-Way Frame Delay Measurement on a

VPLS Network
In VPLS networking, if the clocks of peer MEPs are not synchronized and the requirement for
delay measurement is not high, two-way frame delay measurement can be configured.


Before configuring two-way frame delay measurement on a VPLS network, familiarize yourself
data. This will help you complete the configuration task quickly and correctly.

Core
Y.1731 Y.1731 Y.1731

MEP
MIP
This section describes how to configure two-way frame delay measurement a PW in VPLS
networking.
Before configuring two-way frame delay measurement on a VPLS network, complete the
following tasks:
l Configuring two-way frame delay measurement on a PW

– Configuring Martini VPLS
Guide - VPN.

Data Preparation
To configure two-way frame delay measurement on a VPLS network, you need the following
data.
No. Data
located

Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
map vsi vsi-name
----End

9.9.3 Configuring DMM Reception on a Remote MEP

Two-way frame delay measurement can work properly only when DMM reception is configured
on a remote MEP.
Context
Do as follows on the device where a remote MEP is located.
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

l To detect a PW, run the delay-measure two-way receive peer-ip peer-ip vc-id vc-id
command to configure DMM reception on a remote MEP.
----End
9.9.4 Enabling Two-Way Frame Delay Measurement on a VPLS

Network
VPLS implements MP2MP VPNs so that there may be multiple PWs in the same VSI. To make
accurate statistics of the delay in bidirectional frame transmission over a PW, configure two-
way frame delay measurement on a VPLS network.
Context
during the diagnostics time. One-way frame delay measurement on a VPLS network is on-
demand OAM. To implement singular or periodic frame delay measurement on a PW, configure
on-demand two-way frame delay measurement on a VPLS network.
l To make frame delay measurement on a PW, do as follows on the device that initiates two-
way frame delay measurement:
Procedure
l Enable on-demand two-way frame delay measurement on a PW.
1. Run:
system-view


2. Run:
cfm md md-name

3. Run:
ma ma-name

4. Run:
delay-measure two-way mep mep-id mep-id { mac mac-address | remote-mep mep-
id mep-id } interval { 1000 | 10000 } count count-value [ peer-ip peer-ip
[ vc-id vc-id ] ]
On-demand two-way frame delay measurement is enabled on a PW.

The peer-ip peer-ip parameter or the vc-id vc-id parameter does not need to be
configured and CFM must be disabled if on-demand two-way frame delay
measurement is performed on PWs on a PBB VPLS network.
Perform the following steps to verify that CFM is disabled on a PBB VPLS network:
– Run the vsi vsi-name command to enter the I-VSI view.
– Run the display this command to check whether or not the cfm enable command
exists in the I-VSI view.
– If the command is displayed in the command output, run the undo cfm enable
command to disable CFM. If the command does not exists, no action is required.
NOTE
been bound to the MAC address of the local MEP, specify the remote MEP ID for the two-
way frame delay measurement.
----End

After two-way frame delay measurement is configured on a VPLS network, you can view
statistics of the delay in bidirectional frame transmission.
Prerequisite
The configurations of two-way frame delay measurement on a VPLS link are complete.
Procedure
l Run the display y1731 statistic-type twoway-delay md md-name ma ma-name peer-ip
ip-address [ count count-value ] command to check Y.1731 performance statistics.
----End
Example
you can view information about two-way frame delay measurement and frame jitter.
<HUAWEI> display y1731 statistic-type twoway-delay md md1 ma ma1 peer-ip 2.2.2.2

Latest two-way delay statistics:

Index Two-way delay(usec) Delay variation
1 30000 0
2 40000 10000
3 10000 30000
4 40000 30000
5 30000 10000
6 40000 10000
7 10000 30000
8 10000 0
9 0 10000
10 30000 30000
11 0 30000
12 10000 10000
13 0 10000
14 40000 40000

This section describes the typical deployment scenario of Y.1731, including the networking
files.
9.10.1 Example for Configuring On-Demand Single-Ended Frame

Loss Measurement on a VLL
This section provides an example showing how to configure on-demand single-end frame loss
measurement on a PW in VLL networking.
To ensure the reliability and stability of links between a user network and an operator network
and improve the operator's capability in monitoring links, Y.1731 must be configured on the
user network or the operator network.
Figure 9-16 Networking diagram for configuring Y.1731 on a VLL
PE1 PE2
GE1/0/2 GE1/0/2
VLL
GE1/0/1 GE1/0/1
GE1/0/1 GE1/0/1
CE1 CE2
User User
Network Network
This example shows how to configure on-demand single-ended frame loss measurement on a
PW in VLL networking.

l Configure on-demand single-ended frame loss measurement on a PW between PEs.
Data Preparation
l VC ID
l MD names and MA names of PE1 and PE2
Procedure
Step 1 Configure on-demand single-ended frame loss measurement on a PW between PEs.
1. Configure a VLL connection.
Configure a VLL connection between PE1 and PE2. The configuration details are not
provided here. For details, see the chapter "VLL Configuration" in the HUAWEI
NetEngine80E/40E Router Configuration Guide - VPN or configuration files in this
configuration example.
After the configuration, run the display mpls l2vc command on each PE to view
information about the VC and AC.
<PE1>display mpls l2vc

total LDP VC : 1 1 up 0 down
*client interface : GigabitEthernet1/0/1.1

Administrator PW : no
session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 2
VC type : VLAN
local VC label : 1027 remote VC label : 1025
control word : disable
forwarding entry : exist
local group ID : 0
link state : up
local VC MTU : 1500 remote VC MTU : 1500
traffic behavior name: --
VC last up time : 2010/10/13 15:02:23
CKey : 4
NKey : 3
AdminPw interface : --
AdminPw link state : --
2. Configure basic Ethernet CFM functions and specify the MEP type as inward.

Configure basic Ethernet CFM functions on each PE. Specify the Ethernet CFM protocol
in the version of IEEE Standard 802.1ag-2007. Create an MD named md1 and an MA
named ma1, and bind the MA to the VLL.
# Configure PE1.
[PE1] cfm enable
[PE1] cfm md md1
[PE1-md-md1] ma ma1
[PE1-md-md1-ma-ma1] mep mep-id 1 interface gigabitethernet1/0/1.1 inward
[PE1-md-md1-ma-ma1] mep ccm-send mep-id 1 enable
[PE1-md-md1-ma-ma1] remote-mep ccm-receive mep-id 2 enable
[PE1-md-md1] quit
# Configure PE2.
[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1
[PE2-md-md1] quit
3. Configure LMM reception on PE2.

# Configure PE2.
[PE2-md-md1-ma-ma1] loss-measure single-ended receive
4. Enable on-demand single-ended frame loss measurement on a PW.

# Configure PE1.
[PE1-md-md1-ma-ma1] loss-measure single-ended mep mep-id 1 mac 01-22-33
interval 1000 count 20
[PE1-md-md1] quit
5. Verify the configuration.

Run the display y1731 statistic-type command on PE1, and you can view information
about single-ended frame loss measurement.
<PE1>display y1731 statistic-type single-loss md md1 ma ma1
----End
Configuration Files
#
sysname PE1
#
cfm enable
#
mpls lsr-id 1.1.1.1
mpls

#
mpls l2vpn
#
mpls ldp
#
vlan-type dot1q 2
mpls l2vc 2.2.2.2 2
#
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md1
ma ma1
mep mep-id 1 interface GigabitEthernet1/0/1.1 inward
remote-mep mep-id 2
#
return
#
sysname PE2
#
cfm enable
#
mpls lsr-id 2.2.2.2
mpls
#
mpls l2vpn
#
mpls ldp
#
#
vlan-type dot1q 2
mpls l2vc 1.1.1.1 2
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 2.2.2.2 255.255.255.0
#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md1
ma ma1


remote-mep mep-id 1
loss-measure single-ended receive
#
return
9.10.2 Example for Configuring Proactive Single-Ended Frame Loss

Measurement on a VLL
This section provides an example showing how to configure proactive single-ended frame loss
PE1 PE2
GE1/0/2 GE1/0/2
VLL
GE1/0/1 GE1/0/1
GE1/0/1 GE1/0/1
CE1 CE2
User User
Network Network
This example shows how to configure proactive single-ended frame loss measurement on a PW
in VLL networking.
l Configure a VLL connection between PEs.

l Configure basic Ethernet CFM functions on a PW.
l Configure proactive single-ended frame loss measurement on a PW.
Data Preparation

l VC ID
l Names of MDs and MAs on PE1 and PE2, and names of MAs on PE1 and PE2
Procedure
Step 1 Configure a VLL connection.
Configure a VLL connection between PE1 and PE2. The configuration details are not provided
here. For details, see the chapter "VLL Configuration" in the HUAWEI NetEngine80E/40E
Router Configuration Guide - VPN or configuration files in this configuration example.
After the configuration, run the display mpls l2vc command on each PE to view information
about the VC and AC.


session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 2
VC type : VLAN
local group ID : 0
link state : up
VC last up time : 2010/10/13 15:02:23
CKey : 4
NKey : 3
Step 2 Configure basic Ethernet CFM functions and specify the MEP type as inward.
Configure basic Ethernet CFM functions on each PE. Specify the Ethernet CFM protocol in the
version of IEEE Standard 802.1ag-2007. Create an MD named md1 and an MA named ma1,
and bind the MA to the VLL.
# Configure PE1.
[PE1] cfm enable
[PE1] cfm md md1
[PE1-md-md1] ma ma1


[PE1-md-md1] quit
# Configure PE2.
[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1
[PE2-md-md1] quit
Step 3 Configure LMM reception on PE2.

# Configure PE2.
[PE2-md-md1-ma-ma1] loss-measure single-ended receive
Step 4 Enable proactive single-ended frame loss measurement on a VLL.

# Configure PE1.
[PE1-md-md1-ma-ma1] loss-measure single-ended continual mep mep-id 1 mac
0001-0001-0001 interval 30000
[PE1-md-md1] quit

Run the display y1731 statistic-type command on PE1, and you can view information about
one-ended frame loss measurement.
<PE1> display y1731 statistic-type single-loss md md1 ma ma1
----End
Configuration Files
#
sysname PE1
#
cfm enable
#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
mpls ldp
#
vlan-type dot1q 2
mpls l2vc 2.2.2.2 2
#

undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md1
ma ma1
remote-mep mep-id 2
loss-measure single-ended continual mep mep-id 1 mac 0001-0001-0001 interval
30000
#
return

#
sysname PE2
#
cfm enable
#
mpls lsr-id 2.2.2.2
mpls
#
mpls l2vpn
#
mpls ldp
#
#
vlan-type dot1q 2
mpls l2vc 1.1.1.1 2
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 2.2.2.2 255.255.255.0
#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md1
ma ma1
remote-mep mep-id 3
loss-measure single-ended receive
#
return

9.10.3 Example for Configuring Proactive Dual-Ended Frame Loss

This section describes how to configure proactive dual-end frame loss measurement on a PW
in VLL networking by using an example.
PE1 PE2
GE1/0/2 GE1/0/2
VLL
GE1/0/1 GE1/0/1
GE1/0/1 GE1/0/1
CE1 CE2
User User
Network Network
The configurations of proactive dual-ended frame loss measurement on a PW in VLL networking

are described in this example.
l Configure dual-ended frame loss measurement on a PW between PEs.
Data Preparation
l VC ID
l Names of MDs and MAs on PE1 and PE2
Procedure
Step 1 Configure dual-ended frame loss measurement on a PW between PEs.




session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 2
VC type : VLAN
local group ID : 0
link state : up
VC last up time : 2010/10/13 15:02:23
CKey : 4
NKey : 3
# Configure PE1.
[PE1] cfm enable
[PE1] cfm md md1
[PE1-md-md1] ma ma1
[PE1-md-md1] quit
# Configure PE2.
[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1


[PE2-md-md1] quit
3. Enable dual-ended frame loss measurement on a VLL.

# Configure PE1.
[PE1-md-md1-ma-ma1] loss-measure dual-ended continual mep mep-id 1 remote-mep
mep-id 2
[PE1-md-md1] quit
# Configure PE2.
[PE2-md-md1-ma-ma1] loss-measure dual-ended continual mep mep-id 2 remote-mep
mep-id 1
[PE2-md-md1] quit

about dual-ended frame loss measurement.
<PE1>display y1731 statistic-type dual-loss md md1 ma ma1
1 4294967295 100.0000% 4294967295 100.0000%
2 4294967295 100.0000% 4294967295 100.0000%
3 4294967295 100.0000% 4294967295 100.0000%
4 4294967295 100.0000% 4294967295 100.0000%
5 4294967295 100.0000% 4294967295 100.0000%
6 4294967295 100.0000% 4294967295 100.0000%
7 4294967295 100.0000% 4294967295 100.0000%
8 4294967295 100.0000% 4294967295 100.0000%
9 4294967295 100.0000% 4294967295 100.0000%
10 4294967295 100.0000% 4294967295 100.0000%
11 4294967295 100.0000% 4294967295 100.0000%
----End
Configuration Files
#
sysname PE1
#
cfm enable
#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
mpls ldp
#
vlan-type dot1q 2
mpls l2vc 2.2.2.2 2
#
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls

mpls ldp
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md
1 ma ma1
remote-mep mep-id 2
loss-measure dual-ended continual mep mep-id 1 remote-mep mep-id 2
#
return
#
sysname PE2
#
cfm version
standard
cfm
enable
#
mpls lsr-id
2.2.2.2
mpls
#
mpls
l2vpn
#
mpls
ldp
#
interface
vlan-type dot1q 2
mpls l2vc 1.1.1.1 2
#
interface
undo
shutdown
ip address 100.1.1.2
255.255.255.0
mpls
mpls
ldp
#
interface
LoopBack0
ip address 2.2.2.2
255.255.255.0
#
ospf
1
area
0.0.0.0
network 2.2.2.2
0.0.0.0
network 100.1.1.0

0.0.0.255
#
cfm md md1
ma ma1
remote-mep mep-id 1
loss-measure dual-ended continual mep mep-id 2 remote-mep mep-id 1
#
return
9.10.4 Example for Configuring On-Demand One-way Frame Delay

This section provides an example showing how to configure on-demand one-way frame delay
PE1 PE2
GE1/0/2 GE1/0/2
VLL
GE1/0/1 GE1/0/1
GE1/0/1 GE1/0/1
CE1 CE2
User User
Network Network
This example shows how to configure on-demand one-way frame delay measurement on a PW
in VLL networking.
l Configure on-demand one-way measurement on a PW between PEs.
Data Preparation

l VC ID
l Names of MDs and MAs on PE1 and PE2.
Procedure
Step 1 Configure on-demand one-way frame delay measurement on a PW between PEs.


session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 2
VC type : VLAN
local group ID : 0
link state : up
VC last up time : 2010/10/13 15:02:23
CKey : 4
NKey : 3
# Configure PE1.
[PE1] cfm enable
[PE1] cfm md md1
[PE1-md-md1] ma ma1


[PE1-md-md1] quit
# Configure PE2.
[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1
[PE2-md-md1] quit
3. Configure DMM reception on PE2.

# Configure PE2.
[PE2-md-md1-ma-ma1] delay-measure one-way receive
4. Enable on-demand one-way frame delay measurement on a PW.

# Configure PE1.
[PE1-md-md1-ma-ma1] delay-measure one-way mep mep-id 1 mac 1-1-1 interval 1000
count 20
[PE1-md-md1] quit

about one-way frame delay measurement.
<PE2>display y1731 statistic-type oneway-delay md md1 ma ma1
One-way delay measurement statistics:
1 30000 0
2 10000 20000
3 30000 20000
4 20000 10000
5 10000 10000
6 20000 10000
7 10000 10000
8 20000 10000
9 20000 0
10 10000 10000
11 10000 0
12 10000 0
13 30000 20000
14 10000 20000
15 30000 20000
----End
Configuration Files
#
sysname PE1
#

cfm enable
#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
mpls ldp
#
vlan-type dot1q 2
mpls l2vc 2.2.2.2 2
#
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md1
ma ma1
remote-mep mep-id 2
#
return
#
sysname PE2
#
cfm enable
#
mpls lsr-id 2.2.2.2
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.1
#
mpls ldp
#
#
vlan-type dot1q 2
mpls l2vc 1.1.1.1 2
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 2.2.2.2 255.255.255.0
#

ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md1
ma ma1
remote-mep mep-id 1
delay-measure one-way receive
#
return
9.10.5 Example for Configuring Proactive One-Way Frame Delay

This section provides an example showing how to configure proactive one-way frame delay
PE1 PE2
GE1/0/2 GE1/0/2
VLL
GE1/0/1 GE1/0/1
GE1/0/1 GE1/0/1
CE1 CE2
User User
Network Network
This example shows how to configure proactive one-way frame delay measurement on a PW in
VLL networking.
l Configure a PW between PEs.

l Complete basic CFM configurations.

l Enable proactive one-way frame delay measurement on a VLL.
Data Preparation
l VC ID
l Names of MDs and MAs on PE1 and PE2, and names of MAs on CE1 and PE1
Procedure


session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 2
VC type : VLAN
local group ID : 0
link state : up
VC last up time : 2010/10/13 15:02:23
CKey : 4
NKey : 3
# Configure PE1.

[PE1] cfm enable
[PE1] cfm md md1
[PE1-md-md1] ma ma1
[PE1-md-md1] quit
# Configure PE2.
[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1
[PE2-md-md1] quit
Step 3 Configure DMM reception on PE2.

# Configure PE2.
[PE2-md-md1-ma-ma1] delay-measure one-way continual receive
Step 4 Enable proactive one-way frame delay measurement on a VLL.

[PE1-md-md1-ma-ma1] delay-measure one-way continual mep mep-id 1 mac
0001-0001-0001 interval 1000
[PE1-md-md1] quit

one-way frame delay measurement.
----End
Configuration Files
#
sysname PE1
#
cfm enable
#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
mpls ldp

#
vlan-type dot1q 2
mpls l2vc 2.2.2.2 2
#
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md1
ma ma1
remote-mep mep-id 2
delay-measure one-way continual mep mep-id 1 mac 0001-0001-0001 interval
1000
#
return
#
sysname PE2
#
cfm enable
#
mpls lsr-id 2.2.2.2
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.1
#
mpls ldp
#
#
vlan-type dot1q 2
mpls l2vc 1.1.1.1 2
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 2.2.2.2 255.255.255.0
#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md1

ma ma1
remote-mep mep-id 1
delay-measure one-way continual receive
#
return
9.10.6 Example for Configuring On-Demand Two-Way Frame

Delay Measurement on a VLL
This section provides an example showing how to configure two-way frame delay measurement
on a PW in VLL networking.
and improve the operator's capability in monitoring links, Y.1731 can be configured on the user
network or the operator network.
PE1 PE2
GE1/0/2 GE1/0/2
VLL
GE1/0/1 GE1/0/1
GE1/0/1 GE1/0/1
CE1 CE2
User User
Network Network
This example shows how to configure two-way frame delay measurement on a PW in VLL
networking.
1. Configure two-way frame delay measurement on a PW between PEs.
Data Preparation
l VC ID

l MD names and MA names of PE1 and PE2.
Procedure
Step 1 Configure on-demand two-way frame delay measurement on a PW between PEs.


session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 2
VC type : VLAN
local group ID : 0
link state : up
VC last up time : 2010/10/13 15:02:23
CKey : 4
NKey : 3
# Configure PE1.
[PE1] cfm enable
[PE1] cfm md md1
[PE1-md-md1] ma ma1


[PE1-md-md1] quit
# Configure PE2.
[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1
[PE2-md-md1] quit

# Configure PE2.
[PE2-md-md1-ma-ma1] delay-measure two-way receive
[PE2-md-md1] quit
4. Enable two-way frame delay measurement on a PW.

# Configure PE1.
[PE1-md-md1-ma-ma1] delay-measure two-way mep mep-id 1 mac 1-1-1 interval 1000
count 60
[PE1-md-md1] quit

about two-way frame delay measurement.
<PE1> display y1731 statistic-type twoway-delay md md1 ma ma1Two-way delay
measurement statistics:
1 10000 0
2 10000 10000
3 20000 10000
4 10000 10000
5 10000 0
6 20000 10000
7 10000 10000
8 10000 0
9 10000 0
10 20000 10000
11 20000 0
12 10000 10000
13 20000 10000
14 10000 10000
15 20000 10000
----End
Configuration Files
#
sysname PE1
#
cfm version
standard

cfm
enable
#
mpls lsr-id
1.1.1.1
mpls
#
mpls
l2vpn
#
mpls
ldp
#
interface
undo
shutdown
#
interface
vlan-type dot1q
2
mpls l2vc 2.2.2.2
2
#
interface
undo
shutdown
255.255.255.0
mpls
mpls
ldp
#
interface
NULL0
#
interface
LoopBack0
ip address 1.1.1.1
255.255.255.0
#
ospf
1
area
0.0.0.0
network 1.1.1.1
0.0.0.0
network 100.1.1.0
0.0.0.255
#
cfm md
md1
ma ma1
map mpls l2vc 2
tagged
remote-mep mep-id 2
remote-mep ccm-receive mep-id 2
enable
#
return
#
sysname PE2

#
cfm version
standard
cfm
enable
#
mpls lsr-id
2.2.2.2
mpls
#
mpls
l2vpn
#
mpls
ldp
#
interface
vlan-type dot1q
2
mpls l2vc 1.1.1.1
2
#
interface
undo
shutdown
255.255.255.0
mpls
mpls
ldp
#
interface
LoopBack0
ip address 2.2.2.2
255.255.255.0
#
ospf
1
area
0.0.0.0
network 2.2.2.2
0.0.0.0
network 100.1.1.0
0.0.0.255
#
cfm md
md1
ma ma1
map mpls l2vc 2
tagged
remote-mep mep-id 1
enable
delay-measure two-way receive
#
return

9.10.7 Example for Configuring Proactive Two-Way Frame Delay

This section provides an example showing how to configure proactive two-way frame delay
PE1 PE2
GE1/0/2 GE1/0/2
VLL
GE1/0/1 GE1/0/1
GE1/0/1 GE1/0/1
CE1 CE2
User User
Network Network
This example shows how to configure proactive two-way frame delay measurement on a PW in
VLL networking.
l Configure a PW between PEs.

l Complete basic CFM configurations.
l Enable proactive two-way frame delay measurement on a VLL.
Data Preparation
l VC ID
l MD names and MA names of PE1 and PE2, and MA names of CE1 and PE1
Procedure



session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 2
VC type : VLAN
local group ID : 0
link state : up
VC last up time : 2010/10/13 15:02:23
CKey : 4
NKey : 3
# Configure PE1.
[PE1] cfm enable
[PE1] cfm md md1
[PE1-md-md1] ma ma1
[PE1-md-md1] quit
# Configure PE2.


[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1
[PE2-md-md1] quit
Step 3 Configure DMM reception on PE2.

# Configure PE2.
[PE2-md-md1-ma-ma1] delay-measure two-way receive
Step 4 Enable on-demand two-way frame delay measurement on a VLL.

[PE1-md-md1-ma-ma1] delay-measure two-way continual mep mep-id 1 mac 0001-0001-0001
interval 30000
[PE1-md-md1] quit

two-way frame delay measurement.
Two-way delay measurement statistics:
1 10000 0
2 30000 20000
3 10000 20000
4 20000 10000
----End
Configuration Files
#
sysname PE1
#
cfm enable
#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
mpls ldp
#
vlan-type dot1q 2
mpls l2vc 2.2.2.2 2
#
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp

#
interface LoopBack0
ip address 1.1.1.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md1
ma ma1
remote-mep mep-id 2
delay-measure two-way continual mep mep-id 1 mac 0001-0001-0001 interval
30000
#
return

#
sysname PE2
#
cfm enable
#
mpls lsr-id 2.2.2.2
mpls
#
mpls l2vpn
#
mpls ldp
#
#
vlan-type dot1q 2
mpls l2vc 1.1.1.1 2
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 2.2.2.2 255.255.255.0
#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md1
ma ma1
remote-mep mep-id 1
delay-measure two-way receive
#
return

9.10.8 Example for Configuring On-Demand Single-Ended Frame

Loss Measurement on a VPLS Network
This section provides an example showing how to configure on-demand single-end frame loss
measurement on a PW in VPLS networking.
This example shows how to configure on-demand single-ended frame loss measurement on a
PW in VPLS networking.
Figure 9-23 Networking diagram for configuring single-ended frame loss measurement on a
VPLS network
PE1 PE2
GE1/0/2 GE1/0/2
VPLS
GE1/0/1 GE1/0/1
GE1/0/1 GE1/0/1
CE1 CE2
User User
Network Network
l Configure on-demand single-ended frame loss measurement on a PW between PEs.
Data Preparation
l VSI name
l MD names and MA names of PE1 and PE2, and MA names of CE1 and PE1
Procedure
Step 1 Configure on-demand single-ended frame loss measurement on a PW between PEs.
1. Configure a VPLS connection.
Configure a VPLS connection between PE1 and PE2. The detailed configurations are not
provided here. For details, see the chapter "VPLS Configuration" in the HUAWEI


example.
After the configuration, run the display vsi name vsi-name verbose command on each PE
to view information about the related VSI and PW.
<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, 3 hours, 29 minutes, 53
seconds
VSI State :
up
VSI ID :
1
*Peer Router ID :
2.2.2.2
primary or secondary :
primary
ignore-standby-state :
no
VC Label :
1025
Peer Type :
dynamic
Session :
up
Tunnel ID :
0x800003
Broadcast Tunnel ID :
0x800003
Broad BackupTunnel ID :
0x0
CKey :
2
NKey :
1
StpEnable :
0
PwIndex :

Interface Name :
State :
up
Last Up Time : 2010/10/12
14:18:39
Total Up Time : 0 days, 1 hours, 2 minutes, 44
seconds
**PW
Information:
*Peer Ip Address :
2.2.2.2
PW State :
up
Local VC Label :
1025
Remote VC Label :
1025
PW Type :
label
Tunnel ID :
0x800003
0x800003
0x0
Ckey :
0x2
Nkey :
0x1
Main PW Token :
0x800003
Slave PW Token :
0x0
Tnl Type :
LSP
OutInterface :
Backup
OutInterface :
Stp Enable :
0
PW Last Up Time : 2010/10/12
14:19:55
PW Total Up Time : 0 days, 1 hours, 1 minutes, 28 seconds
named ma1, and bind the MA to the VSI.
# Configure PE1.
[PE1] cfm enable
[PE1] cfm md md1
[PE1-md-md1] ma ma1
[PE1-md-md1] quit

# Configure PE2.
[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1
[PE2-md-md1] quit
3. Configure LMM reception on PE2.

# Configure PE2.
[PE2-md-md1-ma-ma1] loss-measure single-ended receive peer-ip 1.1.1.1
4. Enable on-demand single-ended frame loss measurement on a VPLS network.

# Configure PE1.
[PE1-md-md1-ma-ma1] loss-measure single-ended mep mep-id 1 mac 01-22-33
interval 1000 count 10 peer-ip 2.2.2.2
[PE1-md-md1] quit
NOTE
When single-ended frame loss measurement is enabled on PE1, related configuration commands are
not displayed in the configuration file.
about single-ended frame loss measurement.
<PE1>display y1731 statistic-type single-loss md md1 ma ma1 peer-ip 2.2.2.2
1 20 50.0000% 30 75.0000%
2 20 50.0000% 30 75.0000%
3 20 50.0000% 30 75.0000%
4 20 50.0000% 30 75.0000%
5 20 50.0000% 30 75.0000%
6 20 50.0000% 30 75.0000%
7 20 50.0000% 30 75.0000%
8 20 50.0000% 30 75.0000%
9 20 50.0000% 30 75.0000%
10 20 50.0000% 30 75.0000%
11 20 50.0000% 30 75.0000%
12 20 50.0000% 30 75.0000%
13 20 50.0000% 30 75.0000%
14 20 50.0000% 30 75.0000%
----End
Configuration Files
#
sysname PE1
#
cfm enable
#
mpls lsr-id 1.1.1.1

mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 2.2.2.2
#
mpls ldp
#
vlan-type dot1q 1
l2 binding vsi ldp1
#
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md
ma ma1
map vsi ldp1
remote-mep mep-id 2
#
return
#
sysname PE2
#
cfm enable
#
mpls lsr-id 2.2.2.2
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp
vsi-id 1
peer 1.1.1.1
#
mpls ldp
#
#
vlan-type dot1q 2
l2 binding vsi ldp1
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0

ip address 2.2.2.2 255.255.255.0

#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md1
ma ma1
map vsi ldp1
remote-mep mep-id 1
loss-measure single-ended receive peer-ip 1.1.1.1
#
return
9.10.9 Example for Configuring Proactive Dual-Ended Frame Loss

Measurement on a VPLS Network
This section provides an example showing how to configure proactive dual-end frame loss
VPLS network
PE1 PE2
GE1/0/2 GE1/0/2
VPLS
GE1/0/1 GE1/0/1
GE1/0/1 GE1/0/1
CE1 CE2
User User
Network Network
This example shows how to configure proactive dual-ended frame loss measurement on a PW
in VPLS networking.

l Configure dual-ended frame loss measurement on a PW between PEs.
Data Preparation
l VSI name
Procedure
Step 1 Configure dual-ended frame loss measurement on a PW between PEs.
example.
<PE1>display vsi name ldp1 verbose
***VSI Name :
ldp1
Administrator VSI :
no
Isolate Spoken :
disable
VSI Index :
0
PW Signaling :
ldp
static
unqualify
vlan
MTU :
1500
Diffserv Mode :
uniform
Service Class :
--
Color :
--
DomainId :
255
Domain
Name :
Ignore AcState :
disable
seconds
VSI State :
up
VSI ID :
1
*Peer Router ID :
2.2.2.2

primary
no
VC Label :
1025
Peer Type :
dynamic
Session :
up
Tunnel ID :
0x800003
0x800003
0x0
CKey :
2
NKey :
1
StpEnable :
0
PwIndex :
0
Interface Name :
State :
up
14:18:39
seconds
**PW
Information:
*Peer Ip Address :
2.2.2.2
PW State :
up
Local VC Label :
1025
Remote VC Label :
1025
PW Type :
label
Tunnel ID :
0x800003
0x800003
0x0
Ckey :
0x2
Nkey :
0x1
Main PW Token :
0x800003
Slave PW Token :
0x0
Tnl Type :
LSP
OutInterface :
Backup
OutInterface :
Stp Enable :
0

14:19:55
# Configure PE1.
[PE1] cfm enable
[PE1] cfm md md1
[PE1-md-md1] ma ma1
[PE1-md-md1] quit
# Configure PE2.
[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1
[PE2-md-md1] quit
3. Enable proactive dual-ended frame loss measurement on a PW in a VPLS network.

# Configure PE1.
[PE1-md-md1-ma-ma1] loss-measure dual-ended enable mep mep-id 1 remote-mep mep-
id 2 peer-ip 2.2.2.2
[PE1-md-md1] quit
# Configure PE2.
[PE2-md-md1-ma-ma1] loss-measure dual-ended enable mep mep-id 2 remote-mep mep-
id 1 peer-ip 1.1.1.1
[PE2-md-md1] quit
NOTE
When dual-ended frame loss measurement is enabled on PE1, related configuration commands are
not displayed in the configuration file.
about dual-ended frame loss measurement.
<PE1>display y1731 statistic-type dual-loss md md1 ma ma1 peer-ip 2.2.2.2
1 4294967295 100.0000% 4294967295 100.0000%
2 4294967295 100.0000% 4294967295 100.0000%
3 4294967295 100.0000% 4294967295 100.0000%
4 4294967295 100.0000% 4294967295 100.0000%
5 4294967295 100.0000% 4294967295 100.0000%
6 4294967295 100.0000% 4294967295 100.0000%
7 4294967295 100.0000% 4294967295 100.0000%

8 4294967295 100.0000% 4294967295 100.0000%

9 4294967295 100.0000% 4294967295 100.0000%
10 4294967295 100.0000% 4294967295 100.0000%
11 4294967295 100.0000% 4294967295 100.0000%
----End
Configuration Files
#
sysname PE1
#
cfm enable
#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
vsi ldp1 static
pwsignal ldp1
vsi-id 1
peer 2.2.2.2
#
mpls ldp
#
vlan-type dot1q 1
l2 binding vsi ldp1
#
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md1
ma ma1
map vsi ldp1
remote-mep mep-id 2
loss-measure dual-ended continual mep mep-id 1 remote-mep mep-id 2 peer-ip
2.2.2.2
#
return
#
sysname PE2
#
cfm version
standard
cfm
enable

#
mpls lsr-id
2.2.2.2
mpls
#
mpls
l2vpn
#
vsi ldp1
static
pwsignal
ldp
vsi-id
1
peer
1.1.1.1
#
mpls
ldp
#
interface
vlan-type dot1q
2
l2 binding vsi
ldp1
#
interface
undo
shutdown
255.255.255.0
mpls
mpls
ldp
#
interface
LoopBack0
ip address 2.2.2.2
255.255.255.0
#
ospf
1
area
0.0.0.0
network 2.2.2.2
0.0.0.0
network 100.1.1.0
0.0.0.255
#
cfm md
md1
ma ma1
map vsi
ldp1
ccm-interval
10
remote-mep mep-id 1
loss-measure dual-ended continual mep mep-id 2 remote-mep mep-id 1 peer-ip
1
.
1.1.1

#
return
9.10.10 Example for Configuring On-Demand One-way Frame

Delay Measurement on a VPLS Network
This section provides an example showing how to configure on-demand one-way frame delay
VPLS network
PE1 PE2
GE1/0/2 GE1/0/2
VPLS
GE1/0/1 GE1/0/1
GE1/0/1 GE1/0/1
CE1 CE2
User User
Network Network
This example shows how to configure on-demand one-way frame delay measurement on a PW
in VPLS networking.
1. Configure on-demand one-way frame delay measurement on a PW between PEs.
Data Preparation
l VSI name
l Alarm threshold of one-way frame delay measurement

Procedure
Step 1 Configure one-way frame delay measurement on a PW between PEs.
example.
<PE1>display vsi name ldp1

verbose
***VSI Name :
ldp1
Administrator VSI :
no
Isolate Spoken :
disable
VSI Index :
0
PW Signaling :
ldp
static
unqualify
vlan
MTU :
1500
Diffserv Mode :
uniform
Service Class :
--
Color :
--
DomainId :
255
Domain
Name :
Ignore AcState :
disable
seconds
VSI State :
up
VSI ID :
1
*Peer Router ID :
2.2.2.2
primary
no
VC Label :
1025
Peer Type :
dynamic
Session :
up
Tunnel ID :
0x800003

0x800003
0x0
CKey :
2
NKey :
1
StpEnable :
0
PwIndex :
0
Interface Name :
State :
up
14:18:39
seconds
**PW
Information:
*Peer Ip Address :
2.2.2.2
PW State :
up
Local VC Label :
1025
Remote VC Label :
1025
PW Type :
label
Tunnel ID :
0x800003
0x800003
0x0
Ckey :
0x2
Nkey :
0x1
Main PW Token :
0x800003
Slave PW Token :
0x0
Tnl Type :
LSP
OutInterface :
Backup
OutInterface :
Stp Enable :
0
14:19:55
# Configure PE1.

[PE1] cfm enable

[PE1] cfm md md1
[PE1-md-md1] ma ma1
[PE1-md-md1] quit
# Configure PE2.
[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1
[PE2-md-md1] quit

# Configure PE2.
[PE2-md-md1-ma-ma1]delay-measure one-way receive peer-ip 1.1.1.1
4. Enable one-way frame delay measurement on a VPLS network.

Enable one-way frame delay measurement on PE1, and set the interval for sending packets
to 1s.
# Configure PE1.
[PE1-md-md1-ma-ma1]delay-measure one-way mep mep-id 1 mac 1-1-1 interval 1000
count 20 peer-ip 2.2.2.2
[PE1-md-md1] quit

about one-way frame delay measurement.
<PE2> display Y.1731 statistic-type oneway-delay md md1 ma ma1 peer-ip 1.1.1.1
1 10000 0
2 10000 0
3 20000 10000
4 20000 0
5 10000 10000
6 10000 0
7 20000 10000
8 20000 0
9 30000 10000
10 10000 20000
11 20000 10000
12 20000 0
13 10000 10000
14 20000 10000
15 20000 0
16 20000 0
17 20000 0
18 30000 10000
19 10000 20000
20 10000 0

21 10000 0
22 20000 10000
23 20000 0
24 20000 0
25 30000 10000
26 10000 20000
27 10000 0
28 10000 0
29 10000 0
30 50000 40000
31 10000 40000
32 10000 0
33 20000 10000
34 20000 0
35 20000 0
36 20000 0
37 10000 10000
38 20000 10000
39 20000 0
40 20000 0
----End
Configuration Files
#
sysname PE1
#
cfm version
standard
cfm
enable
#
mpls lsr-id
1.1.1.1
mpls
#
mpls
l2vpn
#
vsi ldp1
static
pwsignal
ldp
vsi-id
1
peer
2.2.2.2
#
mpls
ldp
#
interface
vlan-type dot1q
1
l2 binding vsi
ldp1
#
interface
undo
shutdown
255.255.255.0

mpls
mpls
ldp
#
interface
LoopBack0
ip address 1.1.1.1
255.255.255.0
#
ospf
1
area
0.0.0.0
network 1.1.1.1
0.0.0.0
network 100.1.1.0
0.0.0.255
#
cfm md
md1
ma ma1
map vsi
ldp1
ccm-interval
10
remote-mep mep-id 2
delay-measure one-way receive
#
return
#
sysname PE2
#
cfm version
standard
cfm
enable
#
mpls lsr-id
2.2.2.2
mpls
#
mpls
l2vpn
#
vsi ldp1
static
pwsignal
ldp1
vsi-id
1
peer
1.1.1.1
#
mpls
ldp
#
interface
vlan-type dot1q
2
l2 binding vsi
ldp1
#

interface
undo
shutdown
255.255.255.0
mpls
mpls
ldp
#
interface
LoopBack0
ip address 2.2.2.2
255.255.255.0
#
ospf
1
area
0.0.0.0
network 2.2.2.2
0.0.0.0
network 100.1.1.0
0.0.0.255
#
cfm md
md1
ma ma1
map vsi
ldp1
ccm-interval
10
remote-mep mep-id 1
loss-measure dual-ended enable mep mep-id 2 remote-mep mep-id 1 peer-ip
1.1.1.1
#
return
9.10.11 Example for Configuring On-Demand Two-way Frame

Delay Measurement on a VPLS Network
This section provides an example showing how to configure on-demand two-way frame delay

VPLS network
PE1 PE2
GE1/0/2 GE1/0/2
VPLS
GE1/0/1 GE1/0/1
GE1/0/1 GE1/0/1
CE1 CE2
User User
Network Network
This example shows how to configure on-demand two-way frame delay measurement on a PW
in VPLS networking.
1. Configure on-demand two-way frame delay measurement on a PW between PEs.
Data Preparation
l VSI name
l Alarm threshold of two-way frame delay measurement
Procedure
Step 1 Configure two-way frame delay measurement on a PW between PEs.
example.
<PE1>display vsi name ldp1

verbose
***VSI Name :
ldp1
Administrator VSI :

no
Isolate Spoken :
disable
VSI Index :
0
PW Signaling :
ldp
static
unqualify
vlan
MTU :
1500
Diffserv Mode :
uniform
Service Class :
--
Color :
--
DomainId :
255
Domain
Name :
Ignore AcState :
disable
seconds
VSI State :
up
VSI ID :
1
*Peer Router ID :
2.2.2.2
primary
no
VC Label :
1025
Peer Type :
dynamic
Session :
up
Tunnel ID :
0x800003
0x800003
0x0
CKey :
2
NKey :
1
StpEnable :
0
PwIndex :
0
Interface Name :
State :
up
14:18:39
seconds

**PW
Information:
*Peer Ip Address :
2.2.2.2
PW State :
up
Local VC Label :
1025
Remote VC Label :
1025
PW Type :
label
Tunnel ID :
0x800003
0x800003
0x0
Ckey :
0x2
Nkey :
0x1
Main PW Token :
0x800003
Slave PW Token :
0x0
Tnl Type :
LSP
OutInterface :
Backup
OutInterface :
Stp Enable :
0
14:19:55
# Configure PE1.
[PE1] cfm enable
[PE1] cfm md md1
[PE1-md-md1] ma ma1
# Configure PE2.
[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1


# Configure PE2.
[PE2-md-md1-ma-ma1] delay-measure two-way receive peer-ip 1.1.1.1
[PE2-md-md1] quit
4. Enable dual-ended frame delay measurement on a VPLS network.

# Configure PE1.
[PE1-md-md1-ma-ma1] delay-measure two-way mep mep-id 101 mac 1-1-1 interval
1000 count 20 peer-ip 2.2.2.2
[PE1-md-md1] quit

about two-way frame delay measurement.
<PE1> display y1731 statistic-type twoway-delay md md ma ma1 peer-ip 2.2.2.2
Latest two-way delay statistics:
1 30000 0
2 40000 10000
3 10000 30000
4 40000 30000
5 30000 10000
6 40000 10000
7 10000 30000
8 10000 0
9 0 10000
10 30000 30000
11 0 30000
12 10000 10000
13 0 10000
14 40000 40000
15 20000 20000
16 10000 10000
17 40000 30000
18 10000 30000
----End
Configuration Files
#
sysname PE1
#
cfm version
standard
cfm
enable
#
mpls lsr-id
1.1.1.1
mpls
#
mpls
l2vpn
#
vsi ldp1
static

pwsignal
ldp
vsi-id
1
peer
2.2.2.2
#
mpls
ldp
#
interface
vlan-type dot1q
1
l2 binding vsi
ldp1
#
interface
undo
shutdown
255.255.255.0
mpls
mpls
ldp
#
interface
LoopBack0
ip address 1.1.1.1
255.255.255.0
#
ospf
1
area
0.0.0.0
network 1.1.1.1
0.0.0.0
network 100.1.1.0
0.0.0.255
#
cfm md
md1
ma ma1
map vsi
ldp1
ccm-interval
10
remote-mep mep-id 2
enable
#
return
#
sysname PE2
#
cfm version
standard
cfm
enable
#
mpls lsr-id
2.2.2.2
mpls

#
mpls
l2vpn
#
vsi ldp1
static
pwsignal
ldp1
vsi-id
1
peer
1.1.1.1
#
mpls
ldp
#
interface
vlan-type dot1q
2
l2 binding vsi
ldp1
#
interface
undo
shutdown
255.255.255.0
mpls
mpls
ldp
#
interface
LoopBack0
ip address 2.2.2.2
255.255.255.0
#
ospf
1
area
0.0.0.0
network 2.2.2.2
0.0.0.0
network 100.1.1.0
0.0.0.255
#
cfm md
md1
ma ma1
map vsi
ldp1
ccm-interval
10
remote-mep mep-id 1
enable
delay-measure two-way receive peer-ip 1.1.1.1
#
return

9.10.12 Example for Configuring Y.1731 Statistics Based on QoS

Simple Traffic Classification
Priority mappings can be configured on PEs to change priorities of packets or re-classify the
packets. This allows flexible frame loss or delay measurement on PWs. This section provides
an example for configuring Y.1731 statistics based on QoS simple traffic classification,
including networking requirements, configuration roadmap, configuration procedure, and
NOTE
Among Y.1731 statistics functions, single-ended frame loss measurement and one- and two-way frame
delay measurement for VLL traffic can be performed based on QoS simple traffic classification.
In this example, proactive single-ended frame loss measurement on a VLL is configured. The configuration
is similar to that for one- or two-way frame delay measurement on a VLL.
On the network shown in Figure 9-27, priority mappings based on simple traffic classification
help a PE to map a traffic priority on one type of network to that on another type of network.
This enables traffic to be transmitted on another type of network based on the previous priority
or the priority configured by users. After receiving packets, a PE maps external priorities to
internal priorities. The internal priorities are QoS CoS values and colors. Before sending packets,
the PE maps the internal priorities to external priorities in the packets.
The router can perform frame loss or delay measurement based on a specified priority. If you
want to perform frame loss or delay measurement based on a specified priority on PWs, priority
mappings can be set on PEs to change priorities of packets or re-classify the packets. This allows
flexible frame loss or delay measurement on PWs.
Figure 9-27 Network diagram for Y.1731 on a VLL
PE1 PE2
GE1/0/2 GE1/0/2
VLL
GE1/0/1.1 GE1/0/1.1
CE1 CE2
User User
Network Network

l Configure priority mappings based on QoS simple traffic classification.

l Configure a VLL connection between PEs.
l Configure basic Ethernet CFM functions on a PW.
l Configure proactive single-ended frame loss measurement on a PW.
Data Preparation
l Priority mappings in a DS domain

l VC ID
l Names of MDs and MAs on PE1 and PE2, and names of MAs on PE1 and PE2
Procedure
Step 1 Map VLAN 802.1p priorities to QoS CoS values and colors.
For the configuration procedure, see Configuring Priority Mapping for VLAN Packets in the
HUAWEI NetEngine80E/40E Router Configuration Guide - QoS. For information on
configurations, see the configuration files.
NOTE
Apply a traffic policy to the sub-interfaces connected to AC links on PE1 and PE2.
An interface can be bound to a DS domain, but cannot perform 802.1p-based simple traffic classification.
The interface bound to the DS domain only maps IP DSCP values to QoS CoS values and colors.
Table 9-10 lists mappings from 802.1p priority values to CoS values in VLAN packets sent to
a network along an AC link in a DS domain.
Table 9-10 Mappings from 802.1p priority values to CoS values in VLAN packets sent to a
network along an AC link in a DS domain
802.1p Priority CoS Color
0 BE Green
1 BE Green
2 BE Green
3 AF2 Green
4 AF3 Green
5 AF4 Green
6 EF Green
7 BE Green
Table 9-11 lists mappings from CoS values and colors to 802.1p priority values in VLAN packets
sent to users along an AC link in a DS domain.

Table 9-11 Mappings from CoS values and colors to 802.1p priority values in VLAN packets
sent to users along an AC link in a DS domain
CoS Color 802.1p Priority
BE Green 0
AF1 Green, yellow, and red 1
AF2 Green 3
AF2 Yellow and red 2
AF3 Green 4
AF4 Green 5
EF Green 6
CS6 Green 6
CS7 Green 7
Step 2 Map MPLS EXP field values to QoS CoS values and colors.
For the configuration procedure, see Configuring Priority Mapping for MPLS Packets in the
HUAWEI NetEngine80E/40E Router Configuration Guide - QoS. For information about
configurations, see the configuration files.
NOTE
Bind the PW-side interface to a DS domain and enable simple traffic classification on PE1 and PE2.
Table 9-12 lists mappings from EXP field values to CoS values in MPLS packets sent to a
network along a PW in a DS domain.
Table 9-12 Mappings from EXP field values to CoS values in MPLS packets sent to a network
along a PW in a DS domain
EXP CoS Color
0 BE Green
1 AF1 Green
2 AF2 Green
3 AF3 Green
4 AF4 Green
5 EF Green
6 CS7 Green

EXP CoS Color
7 CS7 Green
Table 9-13 lists mappings from CoS values and colors to EXP field values in MPLS packets
sent to users along a PW in a DS domain.
Table 9-13 Mappings from CoS values and colors to EXP field values in MPLS packets sent to
users along a PW in a DS domain
CoS Color MPLS EXP
BE Green 0
EF Green 5
CS6 Green 6
CS7 Green 6

After completing the configuration, run the display mpls l2vc command on each PE to view


session state : up
AC status : up
VC state : up
Label state : 0
Token state : 0
VC ID : 2
VC type : VLAN
local group ID : 0
link state : up


VC last up time : 2010/10/13 15:02:23
CKey : 4
NKey : 3
# Configure PE1.
[PE1] cfm enable
[PE1] cfm md md1
[PE1-md-md1] ma ma1
[PE1-md-md1] quit
# Configure PE2.
[PE2] cfm enable
[PE2] cfm md md1
[PE2-md-md1] ma ma1
[PE2-md-md1] quit
Step 5 Configure LMM reception on PE2.
# Configure PE2.
[PE2-md-md1-ma-ma1] loss-measure single-ended receive 8021p 0
Step 6 Enable proactive single-ended frame loss measurement on a VLL.
# Configure PE1.
[PE1-md-md1-ma-ma1] loss-measure single-ended continual mep mep-id 1 mac
0001-0001-0001 interval 30000 8021p 0
[PE1-md-md1] quit

Run the display y1731 statistic-type command on PE1 to view information about one-ended
<PE1> display y1731 statistic-type single-loss md md1 ma ma1
Latest single-ended loss statistics of 802.1p 0:
1 20 50.0000% 30 75.0000%
2 20 50.0000% 30 75.0000%
3 20 50.0000% 30 75.0000%
4 20 50.0000% 30 75.0000%
5 20 50.0000% 30 75.0000%
6 20 50.0000% 30 75.0000%
7 20 50.0000% 30 75.0000%
8 20 50.0000% 30 75.0000%
9 20 50.0000% 30 75.0000%
10 20 50.0000% 30 75.0000%
11 20 50.0000% 30 75.0000%
12 20 50.0000% 30 75.0000%
13 20 50.0000% 30 75.0000%
14 20 50.0000% 30 75.0000%
15 20 50.0000% 30 75.0000%
16 20 50.0000% 30 75.0000%
17 20 50.0000% 30 75.0000%
18 20 50.0000% 30 75.0000%
19 20 50.0000% 30 75.0000%
20 20 50.0000% 30 75.0000%
----End
Configuration Files
#
sysname PE1
#
diffserv domain AC
8021p-inbound 1 phb be green
8021p-inbound 3 phb af2 green
8021p-inbound 6 phb ef green
8021p-outbound af2 green map 3
8021p-outbound ef green map 6
#
diffserv domain PW
8021p-outbound be green map 7
8021p-outbound cs7 green map 5
mpls-exp-inbound 6 phb cs7 green
mpls-exp-outbound cs7 green map 6
#
#
cfm enable
#

mpls lsr-id 1.1.1.1

mpls
#
mpls l2vpn
#
mpls ldp
#
vlan-type dot1q 2
mpls l2vc 2.2.2.2 2
trust upstream AC
trust 8021p
#
undo shutdown
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
trust upstream PW
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md1
ma ma1
remote-mep mep-id 2
loss-measure single-ended continual mep mep-id 1 mac 0001-0001-0001 interval
30000 8021p 0
#
return
#
sysname PE2
#
diffserv domain AC
8021p-inbound 6 phb ef green
8021p-outbound ef green map 6
#
diffserv domain PW
8021p-outbound be green map 7
8021p-outbound cs7 green map 5
mpls-exp-inbound 6 phb cs7 green

mpls-exp-outbound cs7 green map 6

#
cfm enable
#
mpls lsr-id 2.2.2.2
mpls
#
mpls l2vpn
#
mpls ldp
#
#
vlan-type dot1q 2
mpls l2vc 1.1.1.1 2
trust upstream AC
trust 8021p
#
undo shutdown
ip address 100.1.1.2 255.255.255.0
mpls
mpls ldp
trust upstream PW
#
interface LoopBack0
ip address 2.2.2.2 255.255.255.0
#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 100.1.1.0 0.0.0.255
#
cfm md md1
ma ma1
remote-mep mep-id 1
loss-measure single-ended receive 8021p 0
#
return

Configuration Guide - Reliability 10 MPLS-TP OAM Configuration
10 MPLS-TP OAM Configuration
About This Chapter
This section introduces the basic principles of Multiprotocol Label Switching Transport Profile
Operation, Administration&, and Maintenance (MPLS-TP OAM), describes how to configure
the continuity check (CC), connectivity verification (CV), loopback (LB), linktrace (LT), alarm
indication signal (AIS), remote defect indication (RDI), loss measurement (LM), and delay
measurement (DM) functions, and provides configuration examples.
10.1 Introduction
MPLS-TP OAM is used for MPLS-TP operation and maintenance.
10.2 Configuring MPLS-TP OAM for an LSP
MPLS-TP OAM configured on the NE80E/40E can monitor bidirectional LSPs.
10.3 Configuring MPLS-TP OAM for a PW
MPLS-TP OAM configured on the NE80E/40E can check a PW built over a bidirectional LSP.
This section describes the typical application scenarios of MPLS-TP OAM, networking
files.

10.1 Introduction
MPLS-TP OAM is used for MPLS-TP operation and maintenance.
10.1.1 MPLS-TP OAM Overview

MPLS-TP OAM can effectively detect, identify, and locate faults at the MPLS-TP user layer
and quickly switch traffic when links or nodes become defective or faulty. OAM is an effective
means to reduce network maintenance expenditure. MPLS-TP OAM is used for OAM at the
MPLS-TP layer.
Background
Along with network and service transformation and integration, various new services emerge,
such as triple play services, Next Generation Network (NGN) services, carrier Ethernet services,
and Fiber-to-the-x (FTTx) services. These services require more investment and OAM costs,
and high capabilities of QoS, full service access, and the expansibility, reliability, and
manageability of transport networks. Traditional transport network technologies such as Multi-
Service Transmission Platform (MSTP), Synchronous Digital Hierarchy (SDH), and
Wavelength Division Multiplexing (WDM) cannot meet these requirements because they lack
the control plane. MPLS-TP, however, can meet these requirements because its functions can
be used on both traditional transport networks and next-generation transport networks that are
capable to process packets.
Since traditional transport networks (for example, SDH or OTN networks) set high benchmarks
for reliability and maintenance, MPLS-TP needs to provide powerful OAM capabilities. MPLS-
TP OAM provides the following functions:
l Fault management
l Performance monitoring
l Protection switching
MPLS-TP OAM Functional Components

MPLS-TP OAM functions are performed on maintenance entities (MEs). An ME consists of a
pair of maintenance entity group end points (MEPs) (namely, the two ends of a link) and a group
of maintenance entity group intermediate points (MIPs) (namely, the intermediate nodes along
the link between the two ends).
The details of MPLS-TP OAM functional components are as follows:
10.1.2 MPLS-TP OAM Features Supported by the NE80E/40E

MPLS-TP OAM provides the performance monitoring and fault detection functions.
Fault Management
As shown in Table 10-1, MPLS-TP OAM supports the link fault detection and alarm suppression
functions.

Table 10-1 MPLS-TP OAM fault management functions

Function Description
Continuity Check Checks link connectivity periodically.

(CC)
Connectivity Detects forwarding faults continuously.

Verification (CV)
Loopback Function Performs loopback.

(LB)
Remote Defect Notifies remote defects.

Indication (RDI)
Alarm Indication Notifies alarms at the service layer.

Signal (AIS)
Performance Monitoring
As shown in Table 10-2, MPLS-TP OAM supports the packet loss measurement and delay
measurement functions.
Table 10-2 MPLS-TP OAM performance monitoring functions

Function Description
Loss Measurement Packet loss measurement

(LM) l Single-ended packet loss measurement
l Dual-ended packet loss measurement
Delay Measurement Delay and delay jitter measurement

(DM) l One-way delay and delay jitter measurement
l Two-way delay and delay jitter measurement
10.2 Configuring MPLS-TP OAM for an LSP

MPLS-TP OAM configured on the NE80E/40E can monitor bidirectional LSPs.

MPLS-TP OAM can be configured to monitor LSPs. Before you configure MPLS-TP OAM, an
LSP to be monitored must be created. Before configuring the MPLS-TP OAM monitoring
functions, familiarize yourself with the applicable environment, complete the pre-configuration
tasks, and obtain the data required for the configuration.

MPLS-TP has been widely used on transport networks. Since traditional transport networks,
such as SDH and OTN networks, set high benchmarks for reliability and maintenance, MPLS-
TP needs to provide powerful OAM capabilities.
MPLS-TP OAM can detect faults on bidirectional LSPs and collect performance statistics. On
the LSP shown in Figure 10-3, the ingress LER is the local MEP, the egress LER is the remote
MEP (RMEP), and the transit LERs are MIPs. MPLS-TP OAM runs on the MEPs and MIPs
and provide the functions listed in Table 10-3.
Figure 10-3 Networking diagram for a bidirectional LSP
Ingress LER Transit LER Transit LER Egress LER
LSP Maintenance End Point

Maintenance Intermediate Point
Table 10-3 MPLS-TP OAM functions supported by the NE80E/40E
Function Application Configuration Procedure

Scenario
Fault management Connectivity check CC: checks the continuous connectivity

between the ingress LER and egress LER
of a bidirectional LSP. If a link fault is
detected, an alarm will be generated and the
link status will change to Down.
LB: checks the continuous connectivity

between the ingress LER and egress LER
of a bidirectional LSP based on
requirements. Check results will be directly
displayed on a terminal.
CV: checks whether CC configurations on

the ingress LER and egress LER of a
bidirectional LSP are consistent and will
report alarms if any inconsistency is
detected.
Alarm suppression AIS: sends AISs to the upper-layer devices

if any LSP faults are detected.
Performance statistics Packet loss statistics LM: checks statistics about packets
dropped between the ingress LER and
egress LER of a bidirectional LSP.


Scenario
Delay and delay DM: checks statistics about the delay and
jitter measurement delay jitter between the ingress LER and
egress LER of a bidirectional LSP.
Before configuring MPLS-TP OAM for an LSP, complete the following task:
l Configuring a bidirectional LSP
l Enabling the packet statistics function on the LSP interfaces
Data Preparation
To configure MPLS-TP OAM for an LSP, you need the following data.
No. Data
1 MEG name
2 Name of the tunnel interface bound to the ME
3 (Optional) Interval of Continuity Check Message (CCM) transmissions and priority

of CCMs
4 (Optional) Interval and number of loss measurement message (LMM) transmissions

and priority of LMMs
4 (Optional) Interval and number of transmissions of delay measurement packets and

priority of the packets
5 (Optional) Interval between AIS PDU transmissions and priority of AIS PDUs
10.2.2 Creating an ME and Binding It to a Tunnel Interface

This section describes how to create an ME and bind it to a bidirectional LSP.
Context
RSVP tunnels for transmitting TE services are unidirectional, and TE services are transmitted
from the ingress node to the egress node of a tunnel. To transmit TE services from the egress
node to the ingress node of the tunnel, you can only use a route to forward services. This may
cause network congestion. If the path from the egress node to the ingress node is configured as
an RSVP tunnel, two tunnels are established between the ingress node and the egress node. When
a tunnel becomes faulty, but the other one does not receive the fault notification, services will
be interrupted. To solve the preceding problem, you can configure a static bidirectional LSP.
The following static bidirectional LSPs are supported.
l Static bidirectional co-routed LSP: similar to two LSPs in opposite directions. A
bidirectional co-routed LSP, however, is an integer. It maps two forwarding entries, and

goes Up only when the LSP is Up in the two directions. If the LSP is Down in one direction,
the LSP is in the Down state. The two forwarding entries are associated with each other.
With the IP forwarding capability, any intermediate node can send back a response packet
along the source path.
Static bidirectional co-routed LSPs supported by MPLS-TP can be monitored by TP OAM.
A MEG maps a static bidirectional co-routed LSP, which maps only one ME. The LSP
includes two MEPs at the ingress and egress nodes of the LSP.
l Static bidirectional associated LSP: composed of two opposite RSVP-TE LSPs that are
configured between the source and destination ends. On the source and destination ends,
the first node of one tunnel is bound to the end node of the other tunnel, forming a dynamic
bidirectional associated LSP. The dynamic bidirectional associated LSP can solve network
congestion. In addition, when one end goes faulty, the other end will be notified of the fault
and then the two ends can perform link switching at the same time, preventing service
interruption.
Static bidirectional associated LSPs supported by MPLS-TP can also be monitored by TP
OAM. The MEG mapping to a static bidirectional associated LSP includes two MEs. The
LSP includes two MEPs at the ingress and egress nodes of the LSP.
Two P2P LSPs in opposite directions are set up over a bidirectional co-routed transport path in
a MEG. This means that there is a single LSP in both directions between a MEP and its RMEP.
A single ME operates along this P2P LSP.
Perform the following steps on the MEP and RMEP:
Procedure
Step 1 Run:
system-view

Step 2 Run:
mpls-tp meg meg-name
A MEG is created, and the MEG view is displayed.

Step 3 Run:
me te interface interface-type interface-number mep-id mep-id remote-mep-id remote-
mep-id
An ME is created and bound to a bidirectional co-routed TE tunnel.
----End
10.2.3 (Optional) Configuring CC and CV for an LSP

The CC and CV functions provided by MPLS-TP OAM can be configured for an LSP to check
its continuous connectivity and forwarding correctness.
Context
CC and CV are two different MPLS-TP OAM functions. CC checks loss of continuity (LOC)
defects between two MEPs in a MEG. CV is used to detect consistency of configurations on two
MEPs in a MEG or in different MEGs. The purpose of CC greatly differs from that of CV. The
details are as follows:

In real world situations, CC and CV are usually used together. Therefore, these two functions
are integrated on the NE80E/40E. Perform the following steps on the MEP and RMEP:
Procedure
Step 1 Run:
system-view

Step 2 Run:
A MEG is created and the MEG view is displayed.

Step 3 (Optional) Run the following command as needed:
NOTE
Ensure that the same CCM transmission interval is set on the MEP and RMEP; otherwise, an alarm will be
generated.
l To configure the interval between CCM transmissions, run:
cc interval interval-value
CCM transmission intervals and their application scenarios are as follows:

– 3.3 ms: 300 frames are sent per second. This interval is recommended in protection
switching.
– 10 ms: 100 frames are sent per second.
– 100 ms: 10 frames are sent per second. This interval is recommended in performance
monitoring.
– 1000 ms: 1 frame is sent per second. This interval is recommended in fault management.
– 10000 ms: 6 frames are sent per minute.
– 60000 ms: 1 frame is sent per minute.
– 600000 ms: 6 frames are sent per hour.
Select a proper CCM transmission interval to suit the CC application requirement.
l To configure the priority of CCMs, run:
cc exp exp-value
If the MPLS-TP network is severely congested and the priority of CCMs is low, CCMs cannot
be sent. Therefore, a proper priority needs to be configured for CCMs based on network
conditions.
Step 4 Perform the following steps to enable CC and CV on the MEP and RMEP. This can prevent
MEPs from generating alarms mistakenly during enabling process.
1. On the MEP, run:
cc send enable
Sending CC/CV packets is enabled on the MEP.

2. On the RMEP, run:
cc send enable
Sending CC/CV packets is enabled on the RMEP.

3. On the MEP, run:
cc receive enable

Receiving CC/CV packets is enabled on the MEP.

cc receive enable
Receiving CC/CV packets is enabled on the RMEP.
----End
10.2.4 (Optional) Configuring LB for an LSP

LB is the most common tool used to detect connectivity of MPLS-TP links.
Context
LB is used to monitor the connectivity between a MEP and its RMEP. Unlike CC or CV that is
performed periodically, LB is performed at a specified time.
Commands can be run to trigger LB, and LB packets are used to check the following items:
l Availability of the remote device
l Round-trip delay in communication between two MEPs
l Loss of ping packets
Procedure
Step 1 Run:
ping meg meg-name [ -c count-value | -t timeout-value ]*
LB is enabled to monitor the connectivity of an MPLS-TP link.
NOTE
If the network speed is rather slow, timeout-value (a parameter specifies the period for waiting for a response
packet) can be set to a larger value when the ping meg command is configured.
----End
10.2.5 (Optional) Configuring LM for an LSP

This section describes how to configure single-ended or dual-ended packet loss measurement
(LM) to collect the reliability statistics of a bidirectional LSP.
Context
LM is an MPLS-TP performance monitoring (PM) function. Dual-ended LM is implemented
on two MEPs of an LSP. The measurement results are as follows:
l Near-end packet loss: indicates the number and percentage of dropped packets that are sent
from an RMEP to a MEP.
l Far-end packet loss: indicates the number and percentage of dropped packets that are sent
from a MEP to an RMEP.
The NE80E/40E supports two LM functions, namely, single-ended LM dual-ended LM. The
differences between them are listed in

The procedure for configuring single-ended or dual-ended LM is as follows:

NOTE
All the steps must be performed on the MEP and RMEP unless otherwise specified.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The MEG view is displayed.
Step 3 Choose one of the following sub-procedures as needed.

l Configure single-ended LM.
1. Run the lost-measure single-ended receive enable command to enable the RMEP to
receive the loss measurement messages (LMMs) from the local MEP.
2. Run the loss-measure single-ended [ interval interval-value | count count-value |
exp exp-value ]* command to enable single-ended LM on the local MEP.
l Configure dual-ended packet loss measurement.
1. (Optional) Run the cc interval interval-value command to configure the interval
between CCM transmissions.
Typical CCM transmission intervals and their application scenarios are as follows:
switching.
monitoring.
– 1000 ms: 1 frame is sent per second. This interval is recommended in fault
management.
2. (Optional) Run the cc exp exp-value command to configure the priority of CCMs.
NOTE
If the MPLS-TP network is severely congested and the priority of CCMs is low, CCMs cannot be sent.
Therefore, a proper priority needs to be configured for CCMs based on network conditions.
3. Run the cc send enable command on the local MEP to enable it to send CC/CV packets.
4. Run the cc send enable command on the RMEP to enable it to send CC/CV packets.
5. Run the cc receive enable command on the local MEP to enable it to receive CC/CV
packets.
6. Run the cc receive enable command on the RMEP to enable it to receive CC/CV
packets.
7. (Optional) Run the lost-measure dual-ended loss-ratio { threshold1 threshold1-
value | threshold2 threshold2-value } command to configure the alarm threshold for
packet loss measurement.
8. Run the lost-measure dual-ended enable command to enable dual-ended LM.
----End

10.2.6 (Optional) Configuring DM for an LSP

This section describes how to configure one-way and two way delay and delay jitter
measurement (DM) to collect reliability statistics of a bidirectional LSP.
Context
DM is another performance monitoring function provided by MPLS-TP. Based on delay
information, delay variation (jitter) can be known. At present, two DM modes are supported.
l One-way DM: In a point-to-point ME, a MEP sends DM packets to its RMEP to carry out
one-way DM.
NOTE
If the clocks of the two MEPs are synchronous, one-way DM can be conducted. If the clocks of the two
MEPs are asynchronous, only two-way DM can be conducted.
l Two-way DM: In a point-to-point ME, a MEP sends Delay Measurement Messages
(DMMs) to its RMEP and receives Delay Measurement Replies (DMRs) from the RMEP
to carry out two-way DM.
The differences between one-way DM and two-way DM are listed in

The procedure for configuring one-way and two-way DM is as follows:

NOTE
Procedure
Step 1 Run:
system-view

Step 2 Run:

l Configure one-way DM.
Run the delay-measure one-way [ interval interval-value | count count-value | exp exp-
value ]* command to enable one-way DM.
Run the following commands to query the one-way DM statistics in different situations:
– If the delay-measure one-way command is run on the local MEP, DM is performed in
the direction from the source end to the destination end. To view DM statistics, you must
run the display mpls-tp oam meg meg-name statistic-type delay-measure one-way
command on the RMEP.
– If the delay-measure one-way command is run on the RMEP, DM is performed in the
direction from the destination end to the source end. To view one-way DM statistics, you
can run the display mpls-tp oam meg meg-name statistic-type delay-measure one-
way command on the local MEP.
l Configure two-way DM.
Run the delay-measure two-way [ interval interval-value | count count-value | exp exp-
value | two-time-stamp ]* command to enable two-way DM.
----End
10.2.7 (Optional) Configuring AIS for an LSP

If faults occur on the under-layer link between the ingress LSR and egress LSR of an LSP, an
AIS-capable device on the LSP will periodically send AIS PDUs in the opposite direction to
other devices on the LSP to prevent upper-layer devices from generating alarms.
Context
On a traditional transport network, a circuit such as a T1 line usually spans multiple switching
devices. If a device or a link on the circuit becomes faulty, an alarm suppression message will
be generated immediately on the fault point and protection switching will be triggered. The
NE80E/40E uses AIS to suppress alarms on an MPLS-TP network.
The AIS mechanism works as follows:
l If the server layer where the MEG resides detects a fault, it will report an alarm to the NMS
and then inform the client layer of the fault. This can prevent higher-level network devices
from sending the same alarm to the NMS.

l If the RMEP receives no AIS packet within a period 3.5 times the interval between AIS
packet transmissions after an AIS fault is detected, it will resume its original state.
Procedure
Step 1 Run:
system-view
Step 2 Run the following command as needed:

l To enter the MEG view and enable AIS, run:
l To enter an interface view and enable AIS, run:


ais exp exp-value
The priority of AIS PDUs is configured.

ais interval interval-value
The interval between AIS PDU transmissions is set.
Step 5 Run:
ais enable
AIS is enabled.
----End

After configuring MPLS-TP OAM functions for an LSP, you can view performance statistics
and fault information about the LSP.
Prerequisite
All configurations of MPLS-TP OAM functions for an LSP are complete.
Procedure
l Run the display mpls-tp oam ais command to check the AIS configuration on a device.
l Run the display mpls-tp oam current-alarm command to check alarm information about
a MEG.
l Run the display mpls-tp oam me meg meg-name [ mep-id mep-id | remote-mep-id
remote-mep-id ] command to check ME information about the MEG.
l Run the display mpls-tp oam meg command to check MEG information on the device.
l Run the display mpls-tp oam statistic-type command to check MPLS-TP OAM
performance statistics.
----End

Example
Run the display mpls-tp oam ais command to view the AIS configuration on a device.
<HUAWEI> display mpls-tp oam ais meg test
--------------------------------------------------
Meg test
--------------------------------------------------
Ais Interval : 60000
Ais Exp : 0
Ais Timer : 0XFFFFFFFF
Ais Enable : YES
Run the display mpls-tp oam current-alarm command to view alarm information about a
MEG.
<HUAWEI> display mpls-tp oam current-alarm meg test
Alarm Name ab. Start Time Meg Name Sended
SD1 near-end SD1-NEAR 2011-01-24 10:24:41.410 test YES
SD1 far-end SD1-FAR 2011-01-24 17:31:15.320 test YES
Run the display mpls-tp oam me command to view ME information about the MEG.
<HUAWEI> display mpls-tp oam me meg test
--------------------------------------------------
MEG test
--------------------------------------------------
[ME 1]
index : 0
direction : dual
mep id : 8191
remote mep id : 8191
status board : 1
service type : te (cr-static-lsp)
tunnel-name : Tunnel1/0/0
lsp name :
state : UP
alarm indicate : SD1-NEAR, SD1-FAR, SD2-NEAR, SD2-FAR
Run the display mpls-tp oam meg command to view MEG information on the device.
<HUAWEI> display mpls-tp oam meg test
--------------------------------------------------
MEG abc
--------------------------------------------------
meg name : test
me count : 1
cc send : enable
cc receive : enable
cc interval : 1000
cc exp : 7
ais : enable
ais interval : 60000
ais exp : 0
lm single-end receive : disable
lm dual-end : enable
lm dual-end SD1 threshold: 1
[ME 1]
index : 0
direction : dual
mep id : 8191
status board : 1
lsp name :

state : UP
--------------------------------------------------
Run the display mpls-tp oam statistic-type command to view one-way delay statistics obtained
using MPLS-TP OAM.
<HUAWEI> display mpls-tp oam meg test statistic-type delay-measure one-way
One-way delay measure statistics
Index delay(us) delay variation(us)
----------------------------------------
1 4294827296 --
2 4294847296 20000
3 4294847296 0
4 4294827296 20000
5 4294847296 20000
6 4294847296 0
7 4294847296 0
8 4294847296 0
9 4294827296 20000
10 4294847296 20000
11 4294847296 0
12 4294847296 0
13 4294847296 0
14 4294827296 20000
15 4294827296 0
16 4294847296 20000
17 4294847296 0
18 4294847296 0
19 4294847296 0
20 4294847296 0
The Max delay:4294847296 The Max delay variation:20000
The Min delay:4294827296 The Min delay variation:0
The delay average:4294842296 The delay variation average:7368
The total number of the record is: 20
Run the display mpls-tp oam statistic-type command to view dual-ended packet loss statistics
obtained using MPLS-TP OAM.
<HUAWEI> display mpls-tp oam meg test statistic-type lost-measure dual-ended
Dual-end loss measurement statistics:
Index Near-end lost frames Loss ratio Far-end lost frames Loss ratio
1 10 12.50% 10 12.50%
Max near-end lost frames:10,frame loss ratio:12.50%
Min near-end lost frames:10,frame loss ratio:12.50%
Average near-end lost frames:10,frame loss ratio:12.50%
Max far-end lost frames:10,frame loss ratio:12.50%
Min far-end lost frames:10,frame loss ratio:12.50%
Average far-end lost frames:10,frame loss ratio:12.50%
10.3 Configuring MPLS-TP OAM for a PW

MPLS-TP OAM configured on the NE80E/40E can check a PW built over a bidirectional LSP.

MPLS-TP OAM can be configured to monitor PWs. Before you configure MPLS-TP OAM,
PWs to be monitored must be set up. Before configuring the MPLS-TP OAM monitoring
function, familiarize yourself with the applicable environment, complete the pre-configuration
tasks, and obtain the data required for the configuration.

MPLS-TP has been widely used on transport networks. Since traditional transport networks,
such as SDH and OTN networks, set high benchmarks for reliability and maintenance, MPLS-
TP needs to provide powerful OAM capabilities.
MPLS-TP OAM can detect faults on PWs that are built over bidirectional LSPs and collect
performance statistics. On the PW shown in Figure 10-4, the T-PEs are MEPs, and the S-PEs
are MIPs. MPLS-TP OAM runs on the MEPs and MIPs and provide the functions listed in Table
10-6.
Figure 10-4 Networking diagram for a PW built over a bidirectional LSP

T-PE S-PE S-PE T-PE
LSP Maintenance End Point

Maintenance Intermediate Point
Table 10-6 MPLS-TP OAM functions supported by the NE80E/40E

Scenario
Fault management Connectivity check Continuity check (CC): checks the

continuous connectivity between the T-PEs
of a PW built over a bidirectional LSP. If a
link fault is detected, an alarm will be
generated and the link status will change to
Down.
Loopback (LB): checks the continuous

connectivity between the T-PEs of a PW
built over a bidirectional LSP based on
requirements. Check results will be
displayed on a terminal.
Connectivity Verification (CV): checks

whether CC configurations on the ingress
LER and egress LER of a PW are consistent
and will report alarms if any inconsistency
is detected.
Performance statistics Packet loss statistics Loss Measurement (LM): checks

statistics about packets dropped between
the ingress LER and egress LER of a PW
built over a bidirectional LSP.


Scenario
Delay and delay Delay measurement (DM): collects

jitter measurement statistics about delay and delay jitters
between the T-PEs of a PW built over a
bidirectional LSP.
Before configuring MPLS-TP OAM for a PW, complete the following tasks:
l Setting up a PW based on a bidirectional LSP
l Enabling the packet measurement function on the access circuit (AC) interface of the LSP.
Data Preparation
To configure MPLS-TP OAM for a PW, you need the following data.
No. Data
1 MEG name
2 ID of the VC bound to the ME
3 (Optional) Interval of Continuity Check Message (CCM) transmissions and priority

of CCMs
4 (Optional) Interval and number of loss measurement message (LMM) transmissions

and priority of LMMs
4 (Optional) Interval and number of transmissions of delay measurement packets and

priority of the packets
5 (Optional) Interval between AIS PDU transmissions and priority of AIS PDUs
10.3.2 Creating an ME and Binding It to a PW

This section describes how to create an ME and bind it to a single-segment or multi-segment
PWE3 PW.
Context
If a transport path is a PW built over a bidirectional LSP, an ME created for the path must be
bound to the PW before MPLS-TP OAM is configured.
Procedure
Step 1 Run:

system-view

Step 2 Run:
A MEG is created, and the MEG view is displayed.

Step 3 Run:
me l2vc peer-ip peer-ip vc-id vc-id vc-type vc-type [ remote-peer-ip remote-peer-
ip | ttl ttl-number ] mep-id mep-id remote-mep-id remote-mep-id
An ME is created and bound to a single-segment or multi-segment PWE3 PW.

l If the PW is a single-segment PW, the OAM monitoring configurations are as follows:
– Run the me l2vc peer-ip peer-ip vc-id vc-id vc-type vc-type mep-id mep-id remote-
mep-id remote-mep-id command on the local MEP to create an ME and bind it to the
single-segment PWE3 PW.
– Run the me l2vc peer-ip peer-ip vc-id vc-id vc-type vc-type mep-id mep-id remote-
mep-id remote-mep-id command on the RMEP to create an ME and bind the ME to the
same single-segment PWE3 PW.
l Specify remote-peer-ip or ttl for monitoring a multi-segment PW.
– The procedure for binding an ME to a multi-segment PW by specifying remote-peer-
ip is as follows:
– Run the me l2vc peer-ip peer-ip vc-id vc-id vc-type vc-type remote-peer-ip remote-
peer-ip mep-id mep-id remote-mep-id remote-mep-id command on the local MEP
to create an ME, bind it to a multi-segment PWE3 PW, and specify the IP address of
the RMEP of the multi-segment PWE3 PW.
– Run the me l2vc peer-ip peer-ip vc-id vc-id vc-type vc-type remote-peer-ip remote-
peer-ip mep-id mep-id remote-mep-id remote-mep-id command on the RMEP to
create an ME, bind it to the same multi-segment PWE3 PW, and specify the IP address
of the RMEP of the multi-segment PWE3 PW.
– The procedure for binding an ME to a multi-segment PW by specifying ttl is as follows:
– Run the me l2vc peer-ip peer-ip vc-id vc-id vc-type vc-type ttl ttl-number mep-id
mep-id remote-mep-id remote-mep-id command on the local MEP to create an ME
and bind it to a multi-segment PWE3 PW.
– Run the me l2vc peer-ip peer-ip vc-id vc-id vc-type vc-type ttl ttl-number mep-id
mep-id remote-mep-id remote-mep-id command on the RMEP to create an ME and
bind it to the same multi-segment PWE3 PW.
----End
10.3.3 (Optional) Configuring CC and CV for a PW

The CC and CV functions provided by MPLS-TP OAM can be configured to check continuous
connectivity and forwarding correctness of a PW.
Context
Continuity check (CV) and connectivity verification (CV) are two different MPLS-TP OAM
functions. CC checks loss of continuity (LOC) defects between two MEPs in a MEG. CV is used
to detect consistency of configurations on two MEPs in a MEG or in different MEGs. In real

world situations, CC and CV are usually used together. Therefore, these two functions are
integrated on the NE80E/40E. The purpose of CC greatly differs from that of CV. The details
are as follows:
l CC is a pro-active OAM operation. It detects CCMs between the two MEPs (in a MEG) of
a PW built over a bidirectional LSP. A MEP sends CCMs to its RMEP at intervals. If the
RMEP does not receive CCMs within a period 3.5 times the specified interval, it considers
that the connectivity between the two MEPs is faulty and will report an alarm and enter the
Down state. Then, automatic protection switching (APS) will be triggered on both MEPs.
After receiving a CCM from the MEP, the RMEP will clear the alarm and exit from the
Down state.
l CV is also a pro-active OAM operation. It enables a MEP to report alarms when receiving
unexpected packets. For example, if a CV-enabled device receives a packet from a PW and
finds that this packet is mistakenly transmitted by the PW, the device will report an alarm
indicating a forwarding error.
Transport networks have strict requirements on data forwarding correctness. In addition,
MPLS-TP requires that the data plane be able to work without IP support, which means
that packet forwarding is based on label switching only. Therefore, the correctness of label-
based forwarding must be guaranteed.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 (Optional) Run the following command as needed:

NOTE
Ensure that the same CCM transmission interval is set on the MEP and RMEP; otherwise, CC and CV operations
will fail.
l Run the cc interval interval-value command to configure the interval between CCM
transmissions.
CCM transmission intervals and their application scenarios are as follows:
switching.
– 10 ms: 100 frames are sent per second.
monitoring.
– 1000 ms: 1 frame is sent per second. This interval is recommended in fault management.
– 10000 ms: 6 frames are sent per minute.
– 60000 ms: 1 frame is sent per minute.
– 600000 ms: 6 frames are sent per hour.
Select a proper CCM transmission interval to suit the CC application requirement.

l Run the cc exp exp-value command to configure the priority of CCMs.

If the MPLS-TP network is severely congested and the priority of CCMs is low, CCMs cannot
be sent. Therefore, a proper priority needs to be configured for CCMs based on network
conditions.
Step 4 Perform the following steps to enable CC and CV on the MEP and RMEP. This can prevent
MEPs from generating alarms mistakenly during enabling process.
1. On the MEP, run:
cc send enable
Sending CC/CV packets is enabled on the MEP.

cc send enable
Sending CC/CV packets is enabled on the RMEP.

3. On the MEP, run:
cc receive enable
Receiving CC/CV packets is enabled on the MEP.

4. On the RMEP, run: cc receive enable
Receiving CC/CV packets is enabled on the RMEP.
----End
10.3.4 (Optional) Configuring LB (to Be Performed at a Specified

Time) for a PW
LB is the most common tool used to detect connectivity of MPLS-TP links.
Context
LB can monitor the connectivity between two MEPs or between a MEP and a MIP. Unlike CC
or CV that is performed periodically, LB is performed at a specified time.
The ping meg command can be run to trigger LB, and LB packets are used to check the following
items:
l Availability of the remote device
l Round-trip delay in communication between two MEPs
l Loss of ping packets
Procedure
Step 1 Run:
ping meg meg-name [ -c count-value | -t timeout-value ]*
LB is enabled to monitor the connectivity of an MPLS-TP link.
NOTE
If the network speed is rather slow, timeout-value (a parameter that specifies the period for waiting for a response
packet) can be set to a larger value when the ping meg command is configured.
----End

10.3.5 (Optional) Configuring LM for a PW

This section describes how to configure single-ended or dual-ended packet loss measurement
(LM) to collect the reliability statistics of a PW built over a bidirectional LSP.
Context
LM is an MPLS-TP performance monitoring (PM) function. Dual-ended LM is performed on
the two MEPs of a PW. The measurement results are as follows:
l Near-end packet loss: indicates the number and percentage of dropped packets that are sent
from an RMEP to a MEP.
l Far-end packet loss: indicates the number and percentage of dropped packets that are sent
from a MEP to an RMEP.
The NE80E/40E supports two LM functions, namely, single-ended LM and dual-ended LM.
The differences between them are listed in

The procedure for configuring single-ended or dual-ended LM is as follows:

NOTE
Procedure
Step 1 Run:
system-view
Step 2 Run:

l Configure single-ended packet loss measurement.
1. Run the lost-measure single-ended receive enable command to allow the RMEP to
receive the loss measurement messages (LMMs) from the local MEP.
2. Run the loss-measure single-ended [ interval interval-value | count count-value |
exp exp-value ]* command to enable single-ended LM on the local MEP.
l Configure dual-ended LM.
1. (Optional) Run the cc interval interval-value command to configure the interval
between CCM transmissions.
Typical CCM transmission intervals and their application scenarios are as follows:
switching.
monitoring.
– 1000 ms: 1 frame is sent per second. This interval is recommended in fault
management.
2. (Optional) Run the cc exp exp-value command to configure the priority of CCMs.
NOTE
If the MPLS-TP network is severely congested and the priority of CCMs is low, CCMs cannot be sent.
Therefore, a proper priority needs to be configured for CCMs based on network conditions.
3. Run the cc send enable command on the local MEP to enable it to send CC/CV packets.
4. Run the cc send enable command on the RMEP to enable it to send CC/CV packets.
5. Run the cc receive enable command on the local MEP to enable it to receive CC/CV
packets.
6. Run the cc receive enable command on the RMEP to enable it to receive CC/CV
packets.
7. (Optional) Run the lost-measure dual-ended loss-ratio { threshold1 threshold1-
value | threshold2 threshold2-value } command to configure the alarm threshold for
packet loss measurement.
8. Run the lost-measure dual-ended enable command to enable dual-ended LM.
----End

10.3.6 (Optional) Configuring DM for a PW

This section describes how to configure one-way or two-way delay and delay jitter measurement
(DM) to collect reliability statistics of a PW built over a bidirectional LSP.
Context
DM is another performance monitoring function provided by MPLS-TP. Based on delay
information, delay variation (jitter) can be known. At present, two DM modes are supported.
l One-way DM: In a point-to-point ME, a MEP sends DM packets to its RMEP to carry out
one-way DM.
NOTE
If the clocks of the two MEPs are synchronous, one-way DM can be conducted. If the clocks of the two
MEPs are asynchronous, only two-way DM can be conducted.
l Two-way DM: In a point-to-point ME, a MEP sends Delay Measurement Messages
(DMMs) to its RMEP and receives Delay Measurement Replies (DMRs) from the RMEP
to carry out two-way DM.
The differences between one-way DM and two-way DM are listed in

The procedure for configuring one-way and two-way DM is as follows:

NOTE
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Choose one of the following sub-procedures as needed:

l Configure one-way packet delay measurement.
Run the delay-measure one-way [ interval interval-value | count count-value | exp exp-
value ]* command to enable one-way DM.
Run the following commands to query the one-way DM results in different situations:
– If the delay-measure one-way command is run on the local MEP, DM is performed in
the direction from the source end to the destination end. To view packet delay
measurement results, you must run the display mpls-tp oam meg meg-name statistic-
type delay-measure one-way command on the RMEP.
– If the delay-measure one-way command is run on the RMEP, DM is performed in the
direction from the destination end to the source end. To view delay measurement results,
you can run the display mpls-tp oam meg meg-name statistic-type delay-measure
one-way command on the local MEP.
l Configure two-way DM.
Run the delay-measure two-way [ interval interval-value | count count-value | exp exp-
value |two-time-stamp ]* command to enable two-way DM.
----End

After MPLS-TP OAM functions are configured for a PW, performance statistics and fault
detection information can be queried.
Prerequisite
All configurations of MPLS-TP OAM functions for a PW are complete.
Procedure
l Run the display mpls-tp oam ais command to check the AIS configuration on a device.
l Run the display mpls-tp oam current-alarm command to check alarm information about
a MEG.
l Run the display mpls-tp oam me meg meg-name [ mep-id mep-id [ remote-mep-id
remote-mep-id ] ] command to check ME information about the MEG.

l Run the display mpls-tp oam meg command to check MEG information on the device.
l Run the display mpls-tp oam statistic-type command to check MPLS-TP OAM
performance statistics.
----End
Example
Run the display mpls-tp oam ais command to view AIS configuration on a device.
<HUAWEI> display mpls-tp oam ais meg test
--------------------------------------------------
Meg test
--------------------------------------------------
Ais Interval : 60000
Ais Exp : 0
Ais Timer : 0XFFFFFFFF
Ais Enable : YES
Run the display mpls-tp oam current-alarm command to view alarm information about a
MEG.
<HUAWEI> display mpls-tp oam current-alarm meg test
Alarm Name ab. Start Time Meg Name Sended
Run the display mpls-tp oam me command to view ME information about the MEG.
<HUAWEI> display mpls-tp oam me meg test
--------------------------------------------------
MEG test
--------------------------------------------------
[ME 1]
index : 0
direction : dual
mep id : 8191
status board : 1
lsp name :
state : UP
Run the display mpls-tp oam meg command to view MEG information on the device.
<HUAWEI> display mpls-tp oam meg test
--------------------------------------------------
MEG abc
--------------------------------------------------
meg name : test
me count : 1
cc send : enable
cc receive : enable
cc interval : 1000
cc exp : 7
ais : enable
ais interval : 60000
ais exp : 0
[ME 1]
index : 0

direction : dual
mep id : 8191
status board : 1
lsp name :
state : UP
--------------------------------------------------
Run the display mpls-tp oam statistic-type command to view one-way delay statistics obtained
using MPLS-TP OAM.
<HUAWEI> display mpls-tp oam meg test statistic-type delay-measure one-way
One-way delay measure statistics
Index delay(us) delay variation(us)
----------------------------------------
1 4294827296 --
2 4294847296 20000
3 4294847296 0
4 4294827296 20000
5 4294847296 20000
6 4294847296 0
7 4294847296 0
8 4294847296 0
9 4294827296 20000
10 4294847296 20000
11 4294847296 0
12 4294847296 0
13 4294847296 0
14 4294827296 20000
15 4294827296 0
16 4294847296 20000
17 4294847296 0
18 4294847296 0
19 4294847296 0
20 4294847296 0
The Max delay:4294847296 The Max delay variation:20000
The Min delay:4294827296 The Min delay variation:0
The delay average:4294842296 The delay variation average:7368
The total number of the record is: 20
Run the display mpls-tp oam statistic-type command to view dual-ended packet loss statistics
obtained using MPLS-TP OAM.
<HUAWEI> display mpls-tp oam meg test statistic-type lost-measure dual-ended
1 10 12.50% 10 12.50%

This section describes the typical application scenarios of MPLS-TP OAM, networking
files.

10.4.1 Example for Configuring CC and CV for an LSP

LSRs are connected using a bidirectional LSP. CC and CV need to be configured to monitor the
continuous connectivity between LSRs and detect faults on the MPLS-TP network.
As shown in Figure 10-5, LSRA, LSRB, and LSRC are connected using a bidirectional LSP.
The following deployment is performed to guarantee the connectivity and correct packet
forwarding between LSRA and LSRC:
l LSRA and LSRC serve as MEPs.
l LSRB serves as a MIP.
Configure CC and CV on the MEPs.

l CC is a pro-active OAM operation. It detects connectivity between any two MEPs of a
bidirectional LSP in a MEG. A MEP sends CCMs to its RMEP at intervals. If the RMEP
does not receive CCMs within a period 3.5 times the specified interval, it considers that
the connectivity between the two MEPs is faulty and will report an alarm and enter the
Down state.
l CV is also a pro-active OAM operation. It enables a MEP to report alarms when the MEP
receives unexpected packets transmitted over bidirectional LSPs. For example, if a CV-
enabled device receives a packet from an LSP and finds that this packet is mistakenly
transmitted by the LSP, the device will report an alarm indicating a forwarding error.

1.1.1.1/32 2.2.2.2/32 3.3.3.3/32
POS1/0/0 POS1/0/0 POS2/0/0 POS1/0/0
2.1.1.1/24 2.1.1.2/24 3.2.1.1/24 3.2.1.2/24
LSRA LSRB LSRC
1. Create an ME and bind it to a bidirectional LSP.

2. Configure the interval between CCM transmissions and priority of CCMs.
3. Enable CC and CV.

Data Preparation
l MEG name
l Name of the TE tunnel bound to the ME
l Interval between CCM transmissions and priority of CCMs
Procedure
Step 1 Configure a bidirectional LSP.
For details about the bidirectional LSP that is built based on LSRs, see "Configuring a Static
Bidirectional LSP" in the HUAWEI NetEngine80E/40E Router Configuration Guide-MPLS or
information in the configuration files of this configuration example.
Step 2 Create an ME and bind it to a bidirectional LSP.
# Create an ME named test on LSRA and bind the ME to Tunnel 1/0/0.
[HUAWEI] sysname LSRA
[LSRA] mpls-tp meg test
[LSRA-mpls-tp-meg-test] me te interface tunnel 1/0/0 mep-id 1 rmep-id 2
# Create an ME named test on LSRC and bind the ME to Tunnel 2/0/0.

[HUAWEI] sysname LSRC
[LSRC] mpls-tp meg test
[LSRC-mpls-tp-meg-test] me te interface tunnel 2/0/0 mep-id 2 rmep-id 1
Step 3 Configure the interval between CCM transmissions and priority of CCMs.
NOTE
The same CCM transmission interval and priority of CCMs must be configured on the MEP and RMEP;
otherwise, alarms will be mistakenly reported.
# Set the CCM transmission interval to 100 ms and the priority of CCMs to 6 on LSRA.
[LSRA-mpls-tp-meg-test] cc interval 100
[LSRA-mpls-tp-meg-test] cc exp 6
# Set the CCM transmission interval to 100 ms and the priority of CCMs to 6 on LSRC.
[LSRC-mpls-tp-meg-test] cc interval 100
[LSRC-mpls-tp-meg-test] cc exp 6
Step 4 Enable CC and CV.

# Enable CC and CV on LSRA.
[LSRA-mpls-tp-meg-test] cc send enable
[LSRA-mpls-tp-meg-test] cc receive enable
[LSRA-mpls-tp-meg-test] return
# Enable CC and CV on LSRC.

[LSRC-mpls-tp-meg-test] cc send enable
[LSRC-mpls-tp-meg-test] cc receive enable
[LSRC-mpls-tp-meg-test] return

Run the display mpls-tp oam meg command on LSRA to view MEG information.
<LSRA> display mpls-tp oam meg test
--------------------------------------------------
MEG test

--------------------------------------------------
meg name : test
me count : 1
cc send : enable
cc receive : enable
cc interval : 100
cc exp : 6
ais : disable
ais interval : 1000
ais exp : 7
--------------------------------------------------
[ME 1]
index : 0
direction : dual
mep id : 1
remote mep id : 2
status board : 1
lsp name :
state : UP
alarm indicate : no alarm
--------------------------------------------------
----End
Configuration Files
l Configuration file of LSRA
#
sysname LSRA
#
mpls lsr-id 1.1.1.1
mpls
mpls te
#
bidirectional static-cr-lsp ingress Tunnel1/0/0
forward nexthop 2.1.1.2 out-label 20 bandwidth ct0 10000
backward in-label 20
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.1 255.255.255.0
mpls
mpls te
mpls te bandwidth max-reservable-bandwidth 100000
mpls te bandwidth bc0 100000
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
destination 3.3.3.3
mpls te signal-protocol cr-static
mpls te bidirectional
mpls te commit
#
ip route-static 2.2.2.2 255.255.255.255 2.1.1.2
ip route-static 3.3.3.3 255.255.255.255 2.1.1.2

#
mpls-tp meg test
me te interface Tunnel1/0/0 mep-id 1 remote-mep-id 2
cc interval 100
cc exp 6
cc send enable
cc receive enable
#
return
l Configuration file of LSRB
#
sysname LSRB
#
mpls lsr-id 2.2.2.2
mpls
mpls te
#
bidirectional static-cr-lsp transit lsp1
forward in-label 20 nexthop 3.2.1.2 out-label 40 bandwidth ct0 10000
backward in-label 16 nexthop 2.1.1.1 out-label 20 bandwidth ct0 10000
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.2 255.255.255.0
mpls
mpls te
#
interface Pos2/0/0
undo shutdown
ip address 3.2.1.1 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ip route-static 1.1.1.1 255.255.255.255 2.1.1.1
ip route-static 3.3.3.3 255.255.255.255 3.2.1.2
#
return
l Configuration file of LSRC
#
sysname LSRC
#
mpls lsr-id 3.3.3.3
mpls
mpls te
#
bidirectional static-cr-lsp egress lsp1
forward in-label 40 lsrid 1.1.1.1 tunnel-id 100
backward nexthop 3.2.1.1 out-label 16 bandwidth ct0 10000
#
interface Pos1/0/0
undo shutdown
ip address 3.2.1.2 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#


destination 1.1.1.1
mpls te passive-tunnel
mpls te binding bidirectional static-cr-lsp egress lsp1
mpls te commit
#
ip route-static 1.1.1.1 255.255.255.255 3.2.1.1
ip route-static 2.2.2.2 255.255.255.255 3.2.1.1
#
mpls-tp meg test
cc interval 100
cc exp 6
cc send enable
cc receive enable
#
return
10.4.2 Example for Configuring LB for an LSP

LSRs are connected using a bidirectional LSP. LB needs to be configured to monitor the
connectivity between LSRs and detect faults on the MPLS-TP network.
The following deployment is performed to guarantee the connectivity between LSRA and LSRC:
LB can be used to check the following items:

l Reachability of the REMP
l Round-trip delay in communication between the MEP and RMEP
l Loss of ping packets between the MEP and RMEP
NOTE
LB counts only the ping packets that are lost after being sent out, providing a rough packet loss ratio of
the link between MEPs. The LM function can be used to obtain the accurate packet loss ratio of the link
between MEPs.

1.1.1.1/32 2.2.2.2/32 3.3.3.3/32
POS1/0/0 POS1/0/0 POS2/0/0 POS1/0/0
2.1.1.1/24 2.1.1.2/24 3.2.1.1/24 3.2.1.2/24
LSRA LSRB LSRC

2. Enable LB.
Data Preparation
l MEG name
Procedure
For details about the bidirectional LSP built based on LSRs, see "Configuring a Static
Bidirectional LSP" in the <HUAWEI NetEngine80E/40E Router Configuration Guide-MPLS
or information in the configuration files of this configuration example.

Step 3 Enable LB.

NOTE
LB can be used to detect the connectivity between a MEP and its RMEP or a MIP. In this example, LB is used
to detect the connectivity between LSRA and LSRC.
Enable LB on LSRA.
<LSRA> ping meg test
PING test: 9 data bytes, press CTRL_C to break
Reply from vsi: bytes=9, Sequence=1 time=100 ms
--- ping statistics ---
0.00% packet loss
round-trip min/avg/max 90/96/100 ms
----End
Configuration Files
#
sysname LSRA

#
mpls lsr-id 1.1.1.1
mpls
mpls te
#
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.1 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
destination 3.3.3.3
mpls te commit
#
ip route-static 2.2.2.2 255.255.255.255 2.1.1.2
ip route-static 3.3.3.3 255.255.255.255 2.1.1.2
#
mpls-tp meg test
#
return
#
sysname Quidway
#
mpls lsr-id 2.2.2.2
mpls
mpls te
#
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.2 255.255.255.0
mpls
mpls te
#
interface Pos2/0/0
undo shutdown
ip address 3.2.1.1 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ip route-static 1.1.1.1 255.255.255.255 2.1.1.1
ip route-static 3.3.3.3 255.255.255.255 3.2.1.2

#
return

#
sysname LSRC
#
mpls lsr-id 3.3.3.3
mpls
mpls te
#
#
interface Pos1/0/0
undo shutdown
ip address 3.2.1.2 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
destination 1.1.1.1
mpls te commit
#
ip route-static 1.1.1.1 255.255.255.255 3.2.1.1
ip route-static 2.2.2.2 255.255.255.255 3.2.1.1
#
mpls-tp meg test
#
return
10.4.3 Example for Configuring LM for an LSP

LSRs are connected using a bidirectional LSP. LM needs to be configured to monitor packet
loss ratios between LSRs and provide performance statistics about the MPLS-TP network.
As a connection-oriented packet switching technology, MPLS-TP is designed to convert a
transport network from circuit switching to packet switching. The conversion aims to increase
the transmission rate on the transport network.
Link reliability must be guaranteed when MPLS-TP is used to increase bandwidth usage. For
example, users will not sense change in voice quality if the packet loss ratio on voice links is
lower than 10%. If the packet loss ratio is higher than 20%, voice quality will deteriorate
obviously.
NOTE
Percentage of dropped packets = Number of dropped packets/Number of packets sent during the specified
interval The number of dropped packets is the difference between the number of packets sent by the ingress
node and the number of packets received by the egress node on a P2P LSP.

LM can be used to collect packet loss statistics and evaluate link performance. LM is one of the
performance monitoring functions provided by MPLS-TP. It includes single-ended LM and
dual-ended LM.
NOTE
The section uses the configuration of dual-ended LM as an example. The configuration of single-ended LM is
the same as that of dual-ended LM except the configuration for querying packet loss statistics.
The following deployment is performed to ensure the connectivity between LSRA and LSRC:

1.1.1.1/32 2.2.2.2/32 3.3.3.3/32
POS1/0/0 POS1/0/0 POS2/0/0 POS1/0/0
2.1.1.1/24 2.1.1.2/24 3.2.1.1/24 3.2.1.2/24
LSRA LSRB LSRC
2. Enable CC on the MEP and RMEP.
3. Configure an alarm threshold for packet loss measurement.
4. Enable dual-ended LM.
Data Preparation
l MEG name
l Alarm threshold for packet loss measurement
Procedure
For details about how to configure a bidirectional LSP between T-PEs, see "Configuring a Static


Step 3 Enable CC on the MEP and RMEP.

# Enable CC on LSRA.
# Enable CC on LSRC.
Step 4 Configure an alarm threshold for packet loss measurement.

# Configure an alarm threshold for packet loss measurement on LSRA.
[LSRA-mpls-tp-meg-test] lost-measure dual-ended loss-ratio threshold1 50
# Configure an alarm threshold for packet loss measurement on LSRC.

[LSRC-mpls-tp-meg-test] lost-measure dual-ended loss-ratio threshold1 50
Step 5 Enable dual-ended LM.

# Enable dual-ended LM on LSRA.
[LSRA-mpls-tp-meg-test] lost-measure dual-ended enable
# Enable dual-ended LM on LSRC.

[LSRC-mpls-tp-meg-test] lost-measure dual-ended enable
[LSRC-mpls-tp-meg-test] return

Run the display mpls-tp oam command on LSRA to view statistics about packet loss ratios.
<LSRA> display mpls-tp oam meg test statistic-type lost-measure dual-ended
1 10 12.50% 10 12.50%
----End
Configuration Files
#
sysname LSRA
#
mpls lsr-id 1.1.1.1
mpls
mpls te
#


#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.1 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
destination 3.3.3.3
mpls te commit
#
ip route-static 2.2.2.2 255.255.255.255 2.1.1.2
ip route-static 3.3.3.3 255.255.255.255 2.1.1.2
#
mpls-tp meg test
cc send enable
cc receive enable
#
return
#
sysname Quidway
#
mpls lsr-id 2.2.2.2
mpls
mpls te
#
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.2 255.255.255.0
mpls
mpls te
#
interface Pos2/0/0
undo shutdown
ip address 3.2.1.1 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ip route-static 1.1.1.1 255.255.255.255 2.1.1.1
ip route-static 3.3.3.3 255.255.255.255 3.2.1.2
#
return

#
sysname LSRC
#
mpls lsr-id 3.3.3.3
mpls
mpls te
#
#
interface Pos1/0/0
undo shutdown
ip address 3.2.1.2 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
destination 1.1.1.1
mpls te commit
#
ip route-static 1.1.1.1 255.255.255.255 3.2.1.1
ip route-static 2.2.2.2 255.255.255.255 3.2.1.1
#
mpls-tp meg test
cc send enable
cc receive enable
#
return
10.4.4 Example for Configuring DM for an LSP

LSRs are connected using a bidirectional LSP. DM (including delay and delay jitter
measurement) needs to be configured to monitor the delay and delay jitters between LSRs and
provide performance statistics about the MPLS-TP network.
Link reliability must be guaranteed when MPLS-TP is used to increase bandwidth usage. This
configuration example uses voice services as an example. The coding and decoding of voice
packets plus the transmission delay cause the VoIP transmission delay to be much longer than
the delay in common circuit-switching-based voice transmission. If the delay is longer than 400
ms, voice quality is obviously affected. If the delay is longer than 2 seconds, VoIP services are
unavailable. In addition, if the delay jitter is longer than the transmission of a voice packet, voice
quality will drop greatly.

DM can be used to collect packet loss statistics and evaluate link performance. DM is a
performance monitoring function provided by MPLS-TP, including one-way DM and two-way
DM.
NOTE
The configuration of two-way DM is used as an example in this section. The configuration of one-way DM is
the same as that of two-way DM except the configuration for querying packet loss statistics.
Deploy the following items to guarantee the connectivity between LSRA and LSRC:

1.1.1.1/32 2.2.2.2/32 3.3.3.3/32
POS1/0/0 POS1/0/0 POS2/0/0 POS1/0/0
2.1.1.1/24 2.1.1.2/24 3.2.1.1/24 3.2.1.2/24
LSRA LSRB LSRC
3. Enable two-way DM.
Data Preparation
l MEG name
Procedure



Step 3 Enable two-way DM.

[LSRA-mpls-tp-meg-test] delay-measure two-way
Two-way delay measure statistics
delay(us): delay variation(us):
182 --
182 0
182 0
183 1
182 1
The Max delay:183, The Max delay variation:1
The Min delay:182, The Min delay variation:0
The delay average:182, The delay variation average:1
Total sent Packets Number:5, Total received Packets Number: 5
----End
Configuration Files
#
sysname LSRA
#
mpls lsr-id 1.1.1.1
mpls
mpls te
#
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.1 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
destination 3.3.3.3
mpls te commit
#
ip route-static 2.2.2.2 255.255.255.255 2.1.1.2
ip route-static 3.3.3.3 255.255.255.255 2.1.1.2
#
mpls-tp meg test
#
return


#
sysname Quidway
#
mpls lsr-id 2.2.2.2
mpls
mpls te
#
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.2 255.255.255.0
mpls
mpls te
#
interface Pos2/0/0
undo shutdown
ip address 3.2.1.1 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ip route-static 1.1.1.1 255.255.255.255 2.1.1.1
ip route-static 3.3.3.3 255.255.255.255 3.2.1.2
#
return

#
sysname LSRC
#
mpls lsr-id 3.3.3.3
mpls
mpls te
#
#
interface Pos1/0/0
undo shutdown
ip address 3.2.1.2 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
destination 1.1.1.1
mpls te commit
#

ip route-static 1.1.1.1 255.255.255.255 3.2.1.1

ip route-static 2.2.2.2 255.255.255.255 3.2.1.1
#
mpls-tp meg test
#
return
10.4.5 Example for Configuring AIS for an LSP

LSRs are connected using a bidirectional LSP. AIS needs to be configured to suppress alarm
generation.
On a traditional transport network, a circuit (such as a T1 line) spans multiple switching devices.
If a device or a link on the circuit becomes faulty, an alarm suppression message will be generated
immediately and protection switching will be triggered. The NE80E/40E uses AIS to suppress
alarms on an MPLS-TP network.
The ais enable command is run to enable AIS for the MEG. If the server layer where the MEG
resides detects a fault, it will report an alarm to the NMS and then inform the client layer of the
fault. This can prevent higher-level network devices from sending the same alarm to the NMS.

1.1.1.1/32 2.2.2.2/32 3.3.3.3/32
POS1/0/0 POS1/0/0 POS2/0/0 POS1/0/0
2.1.1.1/24 2.1.1.2/24 3.2.1.1/24 3.2.1.2/24
LSRA LSRB LSRC
Data Preparation
l MEG name
Procedure


Step 3 Enable AIS in the MEG view of LSRA.

[LSRA-mpls-tp-meg-test] ais enable

Run the display this command in the interface view on LSRB to view AIS information on LSRB.
[LSRA-mpls-tp-meg-test] display this
#
mpls-tp meg test
me te interface tunnel 1/0/0 mep-id 1 rmep-id 2
cc send enable
cc receive enable
ais enable
#
----End
Configuration Files
#
sysname LSRA
#
mpls lsr-id 1.1.1.1
mpls
mpls te
#
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.1 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255

#
destination 3.3.3.3
mpls te commit
#
ip route-static 2.2.2.2 255.255.255.255 2.1.1.2
ip route-static 3.3.3.3 255.255.255.255 2.1.1.2
#
mpls-tp meg test
cc send enable
cc receive enable
ais enable
#
return
#
sysname Quidway
#
mpls lsr-id 2.2.2.2
mpls
mpls te
#
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.2 255.255.255.0
mpls
mpls te
ais enable
#
interface Pos2/0/0
undo shutdown
ip address 3.2.1.1 255.255.255.0
mpls
mpls te
ais enable
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ip route-static 1.1.1.1 255.255.255.255 2.1.1.1
ip route-static 3.3.3.3 255.255.255.255 3.2.1.2
#
return
#
sysname LSRC
#
mpls lsr-id 3.3.3.3
mpls
mpls te
#

#
interface Pos1/0/0
undo shutdown
ip address 3.2.1.2 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
destination 1.1.1.1
mpls te commit
#
ip route-static 1.1.1.1 255.255.255.255 3.2.1.1
ip route-static 2.2.2.2 255.255.255.255 3.2.1.1
#
mpls-tp meg test
cc send enable
cc receive enable
#
return
10.4.6 Example for Configuring CC and CV for a PW

PEs are connected using a PW that is built over a bidirectional LSP. CC and CV are configured
to monitor the connectivity between PEs and detect faults on the MPLS-TP network.
As shown in Figure 10-10, PE1, PE2, and PE3 are connected using a PW bulit over a
bidirectional LSP. The following deployment is performed to guarantee the connectivity and
correct packet forwarding between PE1 and PE3:
l PE1 and PE3 serve as MEPs.
l PE2 serves as a MIP.
Configure CC and CV on the MEPs.

l CC is a pro-active OAM operation. It detects connectivity between the two MEPs of a
bidirectional LSP in a MEG. A MEP sends CCMs to its RMEP at intervals. If the RMEP
does not receives CCMs within a period 3.5 times the specified interval, it considers that
the connectivity between the two MEPs is faulty and will report an alarm and enter the
Down state.
l CV is also a pro-active OAM operation. It enables a MEP to report alarms when the MEP
receives unexpected packets transmitted over bidirectional LSPs. For example, if a CV-
enabled device receives a packet from a PW and finds that this packet is mistakenly
transmitted by the PW, the device will report an alarm indicating a forwarding error.


1.1.1.1/32 2.2.2.2/32 3.3.3.3/32
POS1/0/0 POS1/0/0 POS2/0/0 POS1/0/0
2.1.1.1/24 2.1.1.2/24 3.2.1.1/24 3.2.1.2/24
PE1 PE2 PE3
1. Create an ME and bind it to a PW.

2. Configure the interval between CCM transmissions and priority of CCMs.
3. Enable CC and CV.
Data Preparation
l MEG name
l ID of the VC bound to the ME
l Interval between CCM transmissions and priority of CCMs
Procedure
Step 1 Set up a PW over a bidirectional LSP.
For details about how to set up a PW (between LSRs) based on a bidirectional LSP, see see
"Configuring a PW" in the <HUAWEI NetEngine80E/40E Router Configuration Guide-MPLS
Step 2 Create an ME and bind it to a PW.
# Create an ME named test on PE1 and bind the ME to the PW.

[PE1] mpls-tp meg test
[PE1-mpls-tp-meg-test] me l2vc peer-ip 3.3.3.3 vc-id 30000 vc-type vlan mep-id 1
remote-mep-id 2

remote-mep-id 1

Step 3 Enable CC and CV.

# Enable CC and CV on PE1.
[PE1-mpls-tp-meg-test] cc send enable
[PE1-mpls-tp-meg-test] cc receive enable
[PE1-mpls-tp-meg-test] return
# Enable CC and CV on PE3.


Run the display mpls-tp oam meg command on PE1 to view MEG information.
<PE1> display mpls-tp oam meg test
--------------------------------------------------
MEG abc
--------------------------------------------------
meg name : test
meg level : 7
me count : 1
cc send : enable
cc receive : enable
cc interval : 1000
cc exp : 7
ais : disable
ais interval : 1000
ais exp : 7
lock : disable
lock interval : 1000
lock exp : 7
csf : disable
csf interval : 1000
csf exp : 7
lm single-end pro-active : enable
lm single-end SD1 threshold : 1
lm single-end SD2 threshold : 10
lm dual-end : disable
[ME 1]
index : 0
direction : dual
mep id : 1
remote mep id : 2
status board : 3
service type : vll-pw
peer ip : 1.1.1.1
remote peer ip :
2.2.2.2
vc id : 30000
vc type : VLAN
ttl : 2
state : UP
alarm indicate : no alarm
--------------------------------------------------
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.1

mpls
mpls te
#
mpls l2vpn
#
#
pw-template tpatoc
control-word
tnl-policy tpatoc
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.1 255.255.255.0
mpls
mpls te
#
interface POS1/0/0.1
vlan-type dot1q 1
mpls
mpls static-l2vc pw-template tpatoc 30000 transmit-vpn-label 101 receive-vpn-
label 101
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
destination 2.2.2.2
mpls te commit
#
ip route-static 2.2.2.2 255.255.255.255 2.1.1.2
ip route-static 3.3.3.3 255.255.255.255 2.1.1.2
#
tunnel-policy tpatoc
tunnel binding destination 2.2.2.2 te Tunnel1/0/0
#
mpls-tp meg test
me l2vc peer-ip 3.3.3.3 vc-id 30000 vc-type vlan mep-id 1 remote-mep-id 2
cc send enable
cc receive enable
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.2
mpls
mpls te
#
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.2 255.255.255.0
mpls

mpls te
ais enable
#
interface Pos2/0/0
undo shutdown
ip address 3.2.1.1 255.255.255.0
mpls
mpls te
ais enable
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ip route-static 1.1.1.1 255.255.255.255 2.1.1.1
ip route-static 3.3.3.3 255.255.255.255 3.2.1.2
#
return
#
sysname PE3
#
mpls lsr-id 3.3.3.3
mpls
mpls te
#
mpls l2vpn
#
#
pw-template tpctoa
control-word
tnl-policy tpctoa
#
interface Pos1/0/0
undo shutdown
ip address 3.2.1.2 255.255.255.0
mpls
mpls te
#
vlan-type dot1q 1
mpls static-l2vc pw-template tpctoa 30000 transmit-vpn-label 101 receive-vpn-
label 101
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
destination 1.1.1.1
mpls te commit
#
ip route-static 1.1.1.1 255.255.255.255 3.2.1.1
ip route-static 2.2.2.2 255.255.255.255 3.2.1.1

#
tunnel-policy tpctoa
#
mpls-tp meg test
cc send enable
cc receive enable
#
return
10.4.7 Example for Configuring LB for a PW

PEs are connected using a PW that is built over a bidirectional LSP. CC and CV are configured
to monitor the connectivity between PEs and detect faults on the MPLS-TP network.
As shown in Figure 10-11, PE1, PE2, and PE3 are connected using a PW over a bidirectional
LSP. The following deployment is performed to guarantee the connectivity and correct packet
forwarding between PE1 and PE3:
LB can be used to check the following items:
l Reachability of the REMP
l Round-trip delay in communication between the MEP and RMEP
l Loss of ping packets between the MEP and RMEP
NOTE
LB counts only the ping packets that are lost after being sent out, providing a rough packet loss ratio of
the link between MEPs. LM can be used to obtain an accurate packet loss ratios of the link between MEPs.

1.1.1.1/32 2.2.2.2/32 3.3.3.3/32
POS1/0/0 POS1/0/0 POS2/0/0 POS1/0/0
2.1.1.1/24 2.1.1.2/24 3.2.1.1/24 3.2.1.2/24
PE1 PE2 PE3
2. Enable LB.
Data Preparation

l MEG name
Procedure
"Configuring a PW" in the HUAWEI NetEngine80E/40E Router Configuration Guide-MPLS
remote-mep-id 2

remote-mep-id 1
Step 3 Enable LB.

NOTE
LB can be used to detect the connectivity between a MEP and its RMEP or a MIP. In this example, LB is used
to detect the connectivity between PE1 and PE2.
Enable LB on PE1.
<PE1> ping meg test
PING test: 9 data bytes, press CTRL_C to break
--- ping statistics ---
0.00% packet loss
round-trip min/avg/max 90/96/100 ms
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.1
mpls
mpls te
#
mpls l2vpn
#
#
pw-template tpatoc

control-word
tnl-policy tpatoc
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.1 255.255.255.0
mpls
mpls te
#
vlan-type dot1q 1
mpls
label 101
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
destination 2.2.2.2
mpls te commit
#
ip route-static 2.2.2.2 255.255.255.255 2.1.1.2
ip route-static 3.3.3.3 255.255.255.255 2.1.1.2
#
#
mpls-tp meg test
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.2
mpls
mpls te
#
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.2 255.255.255.0
mpls
mpls te
ais enable
#
interface Pos2/0/0
undo shutdown
ip address 3.2.1.1 255.255.255.0
mpls
mpls te

ais enable
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ip route-static 1.1.1.1 255.255.255.255 2.1.1.1
ip route-static 3.3.3.3 255.255.255.255 3.2.1.2
#
return

#
sysname PE3
#
mpls lsr-id 3.3.3.3
mpls
mpls te
#
mpls l2vpn
#
#
pw-template tpctoa
control-word
tnl-policy tpctoa
#
interface Pos1/0/0
undo shutdown
ip address 3.2.1.2 255.255.255.0
mpls
mpls te
#
vlan-type dot1q 1
label 101
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
destination 1.1.1.1
mpls te commit
#
ip route-static 1.1.1.1 255.255.255.255 3.2.1.1
ip route-static 2.2.2.2 255.255.255.255 3.2.1.1
#
#
mpls-tp meg test
#
return

10.4.8 Example for Configuring LM for a PW

PEs are connected using a PW that is built over a bidirectional LSP. LM needs to be configured
to monitor packet loss ratios between LSRs and provide performance statistics of the MPLS-TP
network.
Link reliability must be guaranteed when MPLS-TP is used to increase bandwidth usage. For
example, users will not sense change in voice quality if the packet loss ratio on voice links is
lower than 10%. If the packet loss ratio is higher than 20%, voice quality will deteriorate
obviously.
LM can be used to collect packet loss statistics and evaluate link performance. LM is one of the
performance monitoring functions provided by MPLS-TP. It includes single-ended LM and
dual-ended LM.
NOTE
The section uses the configuration of dual-ended LM as an example. The configuration of single-ended LM is
the same as that of dual-ended LM except the configuration for querying packet loss statistics.
As shown in Figure 10-12, PE1, PE2, and PE3 are connected using a PW over a bidirectional
LSP. The following deployment is performed to guarantee the connectivity between PE1 and
PE3:

1.1.1.1/32 2.2.2.2/32 3.3.3.3/32
POS1/0/0 POS1/0/0 POS2/0/0 POS1/0/0
2.1.1.1/24 2.1.1.2/24 3.2.1.1/24 3.2.1.2/24
PE1 PE2 PE3

3. Configure an alarm threshold for packet loss measurement.
4. Enable dual-ended LM.

Data Preparation
l MEG name
l Alarm threshold for packet loss measurement
Procedure
remote-mep-id 2

remote-mep-id 1
Step 3 Enable CC on the MEP and RMEP.

# Enable CC on PE1.
# Enable CC on PE3.
Step 4 Configure an alarm threshold for packet loss measurement.

# Configure an alarm threshold for packet loss measurement on PE1.
[PE1-mpls-tp-meg-test] lost-measure dual-ended loss-ratio threshold1 50
# Configure an alarm threshold for packet loss measurement on PE3.

[PE3-mpls-tp-meg-test] lost-measure dual-ended loss-ratio threshold1 50
Step 5 Enable dual-ended LM.

# Enable dual-ended LM on PE1.
[PE1-mpls-tp-meg-test] lost-measure dual-ended enable
# Enable dual-ended LM on PE3.

[PE3-mpls-tp-meg-test] lost-measure dual-ended enable

Run the display mpls-tp oam command on PE1 to view statistics about packet loss ratios.

<PE1> display mpls-tp oam meg test statistic-type lost-measure dual-ended

1 10 12.50% 10 12.50%
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.1
mpls
mpls te
#
mpls l2vpn
#
#
pw-template tpatoc
control-word
tnl-policy tpatoc
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.1 255.255.255.0
mpls
mpls te
#
vlan-type dot1q 1
mpls
label 101
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
destination 2.2.2.2
mpls te commit
#
ip route-static 2.2.2.2 255.255.255.255 2.1.1.2
ip route-static 3.3.3.3 255.255.255.255 2.1.1.2
#
#
mpls-tp meg test


cc send enable
cc receive enable
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.2
mpls
mpls te
#
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.2 255.255.255.0
mpls
mpls te
#
interface Pos2/0/0
undo shutdown
ip address 3.2.1.1 255.255.255.0
mpls
mpls te
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ip route-static 1.1.1.1 255.255.255.255 2.1.1.1
ip route-static 3.3.3.3 255.255.255.255 3.2.1.2
#
return
#
sysname PE3
#
mpls lsr-id 3.3.3.3
mpls
mpls te
#
mpls l2vpn
#
#
pw-template tpctoa
control-word
tnl-policy tpctoa
#
interface Pos1/0/0
undo shutdown
ip address 3.2.1.2 255.255.255.0
mpls
mpls te
#

vlan-type dot1q 1
label 101
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
destination 1.1.1.1
mpls te commit
#
ip route-static 1.1.1.1 255.255.255.255 3.2.1.1
ip route-static 2.2.2.2 255.255.255.255 3.2.1.1
#
#
mpls-tp meg test
cc send enable
cc receive enable
#
return
10.4.9 Example for Configuring DM for a PW

PEs are connected using a PW that is built over a bidirectional LSP. DM (including delay and
delay jitter measurement) needs to be configured to monitor delays and delay jitters between
PEs and provide performance statistics about the MPLS-TP network.
Link reliability must be guaranteed when MPLS-TP is used to increase bandwidth usage. This
configuration example uses voice services as an example. The coding and decoding of voice
packets plus the transmission delay cause the VoIP transmission delay to be much longer than
the delay in common circuit-switching-based voice transmission. If the delay is longer than 400
ms, voice quality is obviously affected. If the delay is longer than 2 seconds, VoIP services are
unavailable. In addition, if the delay jitter is longer than the transmission of a voice packet, voice
quality will drop greatly.
DM can be used to collect packet loss statistics and evaluate link performance. DM is a
performance monitoring function provided by MPLS-TP, including one-way DM and two-way
DM.
NOTE
The configuration of two-way DM is used as an example in this section. The configuration of one-way DM is
the same as that of two-way DM except the configuration for querying packet loss statistics.
As shown in Figure 10-13, PE1, PE2, and PE3 are connected using a PW built over a
bidirectional LSP. The following deployment is performed to guarantee the connectivity
between PE1 and PE3:



1.1.1.1/32 2.2.2.2/32 3.3.3.3/32
POS1/0/0 POS1/0/0 POS2/0/0 POS1/0/0
2.1.1.1/24 2.1.1.2/24 3.2.1.1/24 3.2.1.2/24
PE1 PE2 PE3

3. Enable two-way DM.
Data Preparation
l MEG name
Procedure

remote-mep-id 2

remote-mep-id 1
Step 3 Enable two-way DM.

<PE1> delay-measure two-way

Two-way delay measure statistics
delay(us): delay variation(us):
100 --
100 0
100 0
99 1
100 1
The Max delay:100, The Max delay variation:1
The Min delay:99, The Min delay variation:0
The delay average:100, The delay variation average:1
Total sent Packets Number:5, Total received Packets Number: 5
----End
Configuration Files
#
sysname PE1
#
mpls lsr-id 1.1.1.1
mpls
mpls te
#
mpls l2vpn
#
#
pw-template tpatoc
control-word
tnl-policy tpatoc
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.1 255.255.255.0
mpls
mpls te
#
vlan-type dot1q 1
mpls
label 101
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
destination 2.2.2.2
mpls te commit
#
ip route-static 2.2.2.2 255.255.255.255 2.1.1.2
ip route-static 3.3.3.3 255.255.255.255 2.1.1.2
#

#
mpls-tp meg test
#
return
#
sysname PE2
#
mpls lsr-id 2.2.2.2
mpls
mpls te
#
#
interface Pos1/0/0
undo shutdown
ip address 2.1.1.2 255.255.255.0
mpls
mpls te
ais enable
#
interface Pos2/0/0
undo shutdown
ip address 3.2.1.1 255.255.255.0
mpls
mpls te
ais enable
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
#
ip route-static 1.1.1.1 255.255.255.255 2.1.1.1
ip route-static 3.3.3.3 255.255.255.255 3.2.1.2
#
return
#
sysname PE3
#
mpls lsr-id 3.3.3.3
mpls
mpls te
#
mpls l2vpn
#
#
pw-template tpctoa
control-word
tnl-policy tpctoa
#
interface Pos1/0/0
undo shutdown
ip address 3.2.1.2 255.255.255.0
mpls
mpls te

#
vlan-type dot1q 1
label 101
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
destination 1.1.1.1
mpls te commit
#
ip route-static 1.1.1.1 255.255.255.255 3.2.1.1
ip route-static 2.2.2.2 255.255.255.255 3.2.1.1
#
#
mpls-tp meg test
#
return

Configuration Guide - Reliability 11 Multi-Device Backup Configuration
11 Multi-Device Backup Configuration
About This Chapter
The multi-device backup function allows you to back up Address Resolution Protocol (ARP)
entries from a master device to a slave device, improving service reliability.
11.1 Introduction
Two devices back up Address Resolution Protocol (ARP) entries from each other over a TCP
connection.
11.2 Establishing the Multi-Device Backup Platform
By setting up a multi-device backup platform, you can implement a fast service switchover
triggered by interface or link failures.
11.3 Configuring Dual-Device ARP Hot Backup
Dual-device ARP hot backup allows you to back up ARP entries from the master device to the
slave device, ensuring uninterrupted link forwarding when a master/backup VRRP switchover
occurs.
11.4 Maintaining Multi-Device Backup
By running the monitoring and statistics clearing commands, you can view backup information
and check the configuration.
This section provides configuration examples of multi-device backup. Each configuration
example consists of the networking requirements, configuration precautions, configuration
roadmap, configuration procedures, and configuration files.

11.1 Introduction
Two devices back up Address Resolution Protocol (ARP) entries from each other over a TCP
connection.
11.1.1 Introduction to Multi-Device Backup

In Multi-device backup, a VRRP backup group can be created to achieve dual-device ARP hot
backup and BRAS user information backup if RUI is supported. In this manner, services can be
flexibly controlled and managed.
NOTE
The X1 and X2 models of the NE80E/40E do not support the RUI protocol and therefore do not back up
BRAS user information.
l Dual-device ARP hot backup

Dual-device ARP hot backup synchronizes ARP entries from a master device to a slave
device in real time. This allows the new master device to take over traffic and forward it
to hosts without learning MAC addresses of users if a master/backup VRRP switchover
occurs.
11.1.2 Multi-Device Backup Supported by the NE80E/40E

The NE80E/40E supports multi-device backup through which ARP entries can be backed up.
RBS
The remote backup service (RBS) is separated from the RUI. The public RUI information is
saved into the RBS so that the RBS functions as a common backup module. The RBS uses the
TCP protocol. The RBS provides registration interfaces for other service modules and batch
backup and real-time backup.
Currently, RUI supports up to four TCP connections. When the multi-device backup feature is
enabled, the device with the greater IP address listens to the socket during the setup of the TCP
connection. The device with the smaller IP address, however, initiates the setup of the TCP
connection to the peer. After the TCP connection is set up successfully, the backup protocol is
used to transmit data in batch backup and real-time backup modes.
RBP
The remote backup profile (RBP) module provides a uniform user interface of multi-device
backup configuration, and applications of various types of multi-device backup configuration
are based on the RBP.
Real-Time Backup and Batch Backup

The user information is backed up between devices in real time or in batches. When a user goes
online, goes offline, the lease changes or expires, or the administrator disconnects the user, the
master router requests the slave router to add, delete, or modify the backup record in real time.
If a new backup device is added or the fault is rectified on the backup link, the router adopts the
batch backup mode to ensure the same information between devices.

Hot Backup and Warm Backup

After receiving the backup information, the slave router processes the information in hot backup
or warm backup mode.
l Hot backup
After receiving the backup information from the master router, the slave router immediately
generates user information and forwarding entries. When a fault occurs, the service terminal
can be switched fast.
l Warm backup
The slave router does not generate user information and forwarding entries after receiving
the backup information from the master router. Instead, the slave router stores the
information on the main control board. After the master/slave switchover is performed, the
slave router generates user information and forwarding entries. The warm backup mode is
applicable to N:1 backup, but the service terminal switching time is long. In practice, the
master router works in hot backup mode and the slave router works in ward backup mode.
Dual-Device ARP Hot Backup
Figure 11-1 Networking diagram for dual-device ARP hot backup
Router A
User 1
ARP
VRRP Internet
双机热备
User 2
User 3
Router B
On the network shown in Figure 11-1, dual-device ARP hot backup is used to back up ARP
entries from the master device to the slave device. If a master/backup VRRP switchover occurs,
the new master device can immediately take over traffic and forwards it to users, without learning
MAC addresses of users. Two devices usually run VRRP to determine the master and slave
statuses. If the master device works properly, the master device forwards traffic. If the master
device or the link between the master device and a switch fails, a master/backup VRRP
switchover is implemented to allow the slave device to become the new master device. The
master/backup VRRP switchover is not detected by users. The new master device advertises its
network segment routes to upstream devices and takes over network traffic. The new master
device, however, has no MAC address entry mapped to any user IP address and cannot forward
network traffic to users. Therefore, a large number of ARP Miss messages are generated. The
new master device can forward network traffic to users only after the new master device have
learned all users' MAC addresses.

The new master device, however, is slow in learning MAC addresses due to its own processing
capability and how fast users respond, and therefore cannot forward traffic to users in a timely
manner. Simply optimizing the ARP processing capability cannot resolve the problem.
To address this problem, dual-device ARP hot backup is developed to synchronizes ARP entries
from the master device to the slave device. After the master/backup VRRP switchover occurs,
the new master device can forward traffic to users without learning MAC addresses of users.
11.2 Establishing the Multi-Device Backup Platform

By setting up a multi-device backup platform, you can implement a fast service switchover
triggered by interface or link failures.

Before configuring a multi-device backup platform, learning the applicable environment, pre-
configuration tasks, and data preparation can help you rapidly and correctly finish the
configuration task.
When the NE80E/40E acts as an edge service device, it is directly connected to a convergence
device. The convergence device is connected to downstream DSLAMs and upstream NE80E/
40Es. When one or several master NE80E/40E fails, to switch over services to the backup device,
the NE80E/40Es need to work in N:1 redundancy mode, that is, multi-device backup.
Multi-device backup uses VRRP, which operates on Ethernet, to determine master/backup
devices. Other link detection protocols such as BFD, 802.1ag, and 802.1ah can cooperate with
VRRP to change the VRRP status.
During the backup, the RBS acts an a general backup module and uses TCP for transmission.
The RBS offers registration interfaces to other service modules, providing batch backup and
real-time backup. After a TCP connection is set up, the system performs data transmission of
batch backup and real-time backup through the backup protocol. Meanwhile, the RBP offers
user interfaces for configuring multi-device backup of the same style to users. The applications
of multi-device backup are all based on RBP.
Before establishing the multi-device backup platform, complete the following tasks:
l Configuring peer BFD, link BFD, or Ethernet OAM at the user side
l Configuring peer BFD at the network side
l Configuring a local or remote IP address pool (The IP address pools on the devices that
back up each other must be the same.)
Data Preparation
To establish the multi-device backup platform, you need the following data.
No. Data
1 VRRP backup group ID

No. Data
2 IP addresses of devices that back up each other
3 Backup ID, which is used together with the RBS to determine the RBP that the
user belongs to
4 IP address pool name
11.2.2 Configuring VRRP

By configuring VRRP, you can enable the backup device to share network loads when the master
device fails.
Context
NOTE
This section provides the basic configuration procedure of VRRP. For more information, see the chapter of
VRRP.
Do as follows on the devices that back up each other:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
vrrp vrid virtual-router-ID virtual-ip virtual-address
A backup group is created and a virtual IP address is assigned to the backup group.
Step 4 Run:
admin-vrrp vrid virtual-router-ID
The VRRP backup group is configured as the Management VRRP (mVRRP) backup group.
NOTE
The type of the VRRP backup group must be the mVRRP backup group.
The VRRP backup group IDs and virtual IP addresses of the two devices that back up each other must be
the same.
Step 5 Run:
The VRRP priority of the device is configured.

Different priorities need to be configured for two devices in the VRRP backup group, with the
device of a higher priority as the master device.
----End
11.2.3 Configuring the Remote Backup Service

To configure a remote backup service, you need to configure a TCP connection for a remote
server and a monitoring interface.
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
remote-backup-service service-name
The remote backup service view is displayed.
Step 3 Run:
peer peer-ip-address source source-ip-address port port-id
The TCP connection with the remote server is set up.
The peer-ip-address parameter specifies the IP address of the peer device; the local-ip-
address parameter specifies the IP address of the local device. The IP address of the peer device
must have been set on a main interface, sub-interface, or logical interface (such as a loopback
interface) of the peer device. Similarly, the IP address of the local device must have been set on
a main interface, sub-interface, or logical interface (such as a loopback interface) of the local
device. In addition, the two IP addresses can be pinged successfully. port-id specifies the number
of the interface that is listened to by the server. The numbers of the interfaces for the TCP
connection must be the same on the two devices that back up each other.
NOTE
The port with the number 6000 is preserved for other protocols and is currently unavailable.

batch-backup service-type { service-type | all } daily day-time
The data of all the configured services of the RBS is synchronized. Ensure that RUI entries on
the two devices are the same.

track interface interface-name
The RBS is configured to track the network-side interface status. In this manner, the NE80E/
40E can detect the fault occurrence or recovery of the TCP connection established by the RBS.

track bfd-session bfd-session

The RBS is configured to track the BFD session status so that the peer status can be fast detected.
NOTE
To implement fast detection, you are advised to perform this step. Before using the track bfd-session
command, you need to create the peer BFD session at the network side of master and slave devices.
----End
11.2.4 Configuring a Remote Backup Profile

The remote backup policy of the devices that back up each other must be configured with the
same backup ID.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
remote-backup-profile profile-name
The remote backup profile view is displayed.

Step 3 Run:
peer-backup { hot | warm }
Hot backup or warm backup of user information between devices is enabled.

By default, user information between devices is processed in hot backup mode.
Step 4 Run:
vrrp-id vrid interface interface-type interface-number
The VRRP backup group ID is bound to the RBP.

The vrid parameter specifies the ID of a VRRP backup group. The value of the vrid parameter
must be the same as the VRRP backup group ID configured on the interface.
Step 5 Run:
backup-id backup-id remote-backup-service name
The remote backup profile is associated with the RBS. backup-id specifies the remote backup
ID. The NE80E/40E can find the remote backup profile that the user belongs to according to the
backup ID and the RBS. The backup IDs associated with the remote backup profile on the devices
that back up each other must be the same.
----End

After the configuration succeeds, you can view the connection status of the remote server and
the configuration of the remote backup policy.

Context
Run the following commands to check the previous configuration.
Procedure
l Run the display remote-backup-profile profile-name command to check information
about the RBP.
l Run the display remote-backup-service [ service-name [verbose ]] command to check
information about the RBS.
----End
Example
<HUAWEI>display remote-backup-profile test
--------------------------------------------
Profile-Index : 0x802
Profile-Name : test
Service :
Remote-backup-service: test
Backup-ID : 10
track protocol : VRRP
VRRP-ID : 1
VRRP-Interface : GigabitEthernet1/0/0.2
Interface :
State : Master
Peer State : Slave
Backup mode : hot
Slot-Number : 1
Card-Number : 0
Port-Number : 0
<HUAWEI>display remote-backup-service test

-------------------------------------------------------
Service-Index : 0
Service-Name : test
TCP-State : Connected
Peer-ip : 88.88.88.88
Source-ip : 22.22.22.22
TCP-Port : 6000
Track-BFD : --
Track-interface0 : GigabitEthernet2/0/0
Track-interface1 : --
Last up time : 2009-11-2 16:15:8
Last down time : 2009-11-2 16:3:36
Last down reason : TCP closed for packet error.
Batch-backup : 03:05:00(Daily)
--------------------------------------------------
11.3 Configuring Dual-Device ARP Hot Backup

Dual-device ARP hot backup allows you to back up ARP entries from the master device to the
slave device, ensuring uninterrupted link forwarding when a master/backup VRRP switchover
occurs.

Before configuring dual-device ARP hot backup, familiarize yourself with the deployment
scenario, complete the pre-configuration tasks, and obtain the data required for the configuration.
This will help you complete the configuration task quickly and efficiently.

Dual-device ARP hot backup is configured on the master and slave devices. This improves
network reliability and shortens the interruption time after a master/backup VRRP switchover
occurs. On the control and forwarding planes, dual-device ARP hot backup synchronizes ARP
entries from the master device to the slave device in real time. This allows the new master device
to take over traffic and forward it to hosts without learning MAC addresses of users if a master/
backup VRRP switchover occurs.
Before configuring dual-device ARP hot backup, complete the following tasks:
l Establish the multi-device backup platform
l 4.2.3 Configuring Priorities for Interfaces Where a Backup Group Is Created
Data Preparation
None.
11.3.2 Configuring an RBP for ARP Service Backup

To enable dual-device ARP hot backup, specify a service type for backup.
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
The RBP view is displayed.

Step 3 Run:
service-type arp
The ARP service is specified to be backed up.
----End
11.3.3 Binding the Remote Backup Profile to the Interface

The remote backup policy bound to an interface must be created in the system view. Otherwise,
the binding fails.
Context

Procedure
Step 1 Run:
system-view

Step 2 Run:
The interface view is displayed. The interface is a VRRP-capable interface connected to the host.
NOTE
The interface must be the same as the interface specified in the vrrp-id vrid interface interface-type
interface-number run in the remote backup profile view.
Step 3 Run:
The remote backup profile is bound to the interface.
NOTE
The VRRP interfaces of the master and backup routers must be configured with the same VLAN ID.
Otherwise, ARP entries cannot be backed up. The details are as follows:
l If the master and backup router use common VLANs, the same VLAN ID must be set for the VLANs
using the vlan-typedot1q vlan-id command.
l If the master and backup routers use QinQ termination sub-interfaces, the same range of VLAN IDs
in tags of packets to be terminated must be set using the qinq termination pe-vid pe-vid [ to high-pe-
vid ] ce-vid { low-ce-vid [ to high-ce-vid ] | any } [ vlan-group group-id ] command.
----End

After the configuration succeeds, you can view the configuration of the remote backup policy
(RBP) and remote backup service (RBS).
Context
Run the following commands to check the previous configurations.
Procedure
l Run the display remote-backup-profile [ profile-name ] command to view information
about the RBP.
l Run the display remote-backup-service [ service-name [ verbose ]] command to view
information about the remote backup service (RBS).
----End
Example
<HUAWEI>display remote-backup-profile test
--------------------------------------------
Profile-Name : test
Service : arp
Remote-backup-service: test
Backup-ID : 10


VRRP-ID : 1
VRRP-Interface : GigabitEthernet1/0/0.2
Interface :
State : Master
Peer State : Slave
Backup mode : hot
Slot-Number : 1
Card-Number : 0
Port-Number : 0
<HUAWEI>display remote-backup-service test

-------------------------------------------------------
Service-Index : 0
Service-Name : test
Peer-ip : 88.88.88.88
Source-ip : 22.22.22.22
TCP-Port : 6000
Track-BFD : --
Last up time : 2009-11-2 16:15:8
Last down time : 2009-11-2 16:3:36
Batch-backup : 03:05:00(Daily)
--------------------------------------------------
11.4 Maintaining Multi-Device Backup

By running the monitoring and statistics clearing commands, you can view backup information
and check the configuration.
11.4.1 Displaying Backup Information

You can run certain commands to view whether the configuration succeeds.
Context
After the preceding configurations, run the following display commands to view backup
information and check the configurations. For detailed explanation of running information, refer
to the Command Reference.
Procedure
Step 1 Run the display remote-backup-profile [profile-name | {slot slot-id [profile-name]} | {slave
[profile-name ] } ] command to display information about the RBP.
Step 2 Run the display remote-backup-service [ service-name [verbose ]] command to display

information about the RBS.
----End
11.4.2 Clearing Backup Information

Clearing backup and information may affect services. You must execute this operation with
caution.

Context
CAUTION
Backup information cannot be restored after you clear it. So, confirm the action before you use
the command.
To clear the backup information, run the following reset commands in the system view.
Procedure
Step 1 Run the reset remote-backup-service service-name statistic command to clear the statistics
about the RBS.
----End

This section provides configuration examples of multi-device backup. Each configuration
example consists of the networking requirements, configuration precautions, configuration
roadmap, configuration procedures, and configuration files.
11.5.1 Example for Configuring Dual-Device ARP Hot Backup

This section provides a configuration example for dual-device ARP hot backup in a VRRP
backup group, including networking requirements, configuration roadmap, configuration
procedure, and configuration files. After dual-device ARP backup is configured and a master/
backup VRRP switchover occurs, the new master device takes over traffic and forward it to hosts
without learning MAC addresses of users.
On the network shown in Figure 11-2, users are connected to Router A and Router B through
a LAN switch (LSW). The two NE80E/40Es run VRRP to determine the master and slave
statuses. If the master device works properly, the master device learns and periodically updates
MAC addresses mapped to host IP addresses. The master device forwards all traffic based on
learned MAC addresses.
Dual-device ARP hot backup is configured on Router A and Router B. If the master device or
the link between the master device and the LSW fails, the slave device becomes a master device
and takes over traffic. Dual-device ARP hot backup synchronizes ARP entries from the master
device to the slave device. If a master/backup VRRP switchover occurs, the new master device
can immediately take over traffic and sends it to users , without learning MAC addresses of
users. This prevents packet loss if the new master device fails to obtain MAC addresses of users
in time.

Figure 11-2 Networking diagram for dual-device ARP hot backup
RouterA
GE1/0/0
100.0.0.1/24
GE2/0/0
User 1 11.0.0.2/24
Dual-Device
VRRP ARP Hot Internet
User 2 Backup
GE2/0/0
11.0.0.1/24
User 3
GE1/0/0
100.0.0.2/24
RouterB
Device Interface IP Address

RouterA GE 1/0/0 100.0.0.1/24
GE 2/0/0 11.0.0.2/24
Loopback1 22.22.22.22/32
RouterB GE 1/0/0 100.0.0.2/24
GE 2/0/0 11.0.0.1/24
Loopback1 88.88.88.88/32
1. Configure a routing protocol to achieve intercommunication between devices. For details,

refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - IP Routing.
2. Establish a multi-device backup platform.
3. Configure the RBP to back up ARP services.
4. Apply the RBP on VRRP interfaces to ensure that ARP entries are backed up in real time
on the VRRP devices.
Data Preparation
l VRRP backup group ID

l IP address of each router
l Backup ID, which together with the RBS determines the RBP for users
l Virtual IP address of the VRRP backup group
l Priority of every router in the VRRP backup group

Procedure
Step 1 In this example, the configuration procedure for establishing the multi-device backup platform
on Router A is provided. The configuration of Router B is similar to that of Router A.
NOTE
In this example, only the configuration procedure for user information backup is provided.
# Configure a BFD session on the access side to rapidly detect interface or link faults and trigger
a master/backup VRRP switchover when detecting a fault. Set the IP address of GE 1/0/0 on
Router B to 100.0.0.2.
[RouterA] bfd
[RouterA-bfd] quit
[RouterA] bfd bfd bind peer-ip 100.0.0.2
[RouterA-bfd-session-bfd] discriminator local 1
[RouterA-bfd-session-bfd] discriminator remote 2
[RouterA-bfd-session-bfd] commit
[RouterA-bfd-session-bfd] quit
# Bind GE 1/0/0 to the VRRP backup group. Configure VRRP to monitor the BFD session status
and network-side interface status.
[RouterA-GigabitEthernet1/0/0] vlan-type dot1q 200
[RouterA-GigabitEthernet1/0/0] ip address 100.0.0.1 255.255.255.0
[RouterA-GigabitEthernet1/0/0] admin-vrrp vrid 1
[RouterA-GigabitEthernet1/0/0] vrrp vrid 1 preempt-mode timer delay 600
[RouterA-GigabitEthernet1/0/0] vrrp vrid 1 track interface gigabitethernet 2/0/0
reduced 50
NOTE
To differentiate master and slave devices, set different VRRP priorities on the two devices. The device
with a higher VRRP priority is the master device.
# Configure the RBS.

[RouterA] remote-backup-service service1
[RouterA-rm-backup-srv-service1] peer 88.88.88.88 source 22.22.22.22 port 2046
[RouterA-rm-backup-srv-service1] track interface gigabitethernet 2/0/0
NOTE
The master and slave devices can successfully ping each other.
As an alternative of running the track interface command, the track-bfd-session command can be run in
the RBS view of the master and slave devices to track the status of the peer BFD session. In this manner,
the access side of the master and slave devices can be rapidly detected. In this example, the configuration
procedure is not provided.
# Configure an RBP.
[RouterA] remote-backup-profile profile1
[RouterA-rm-backup-prf-profile1] peer-backup hot
[RouterA-rm-backup-prf-profile1] vrrp-id 1 interface gigabitethernet 1/0/0
[RouterA-rm-backup-prf-profile1] backup-id 10 remote-backup-service service1
[RouterA-rm-backup-prf-profile1] service-type arp
[RouterA-rm-backup-prf-profile1] quit
Step 2 Bind the RBP to the user access interface. In this example, GE 1/0/0 is used and the configuration
of Router A is provided. The configuration of Router A is similar to that of Router B.
[RouterA-GigabitEthernet1/0/0] remote-backup-profile profile1


After configuring the RBP, view RBP information. The command output shows that the backup
service type is arp, the RBP profile1 is bound to GE 1/0/0, and the status of Router A is
Master.
<RouterA> display remote-backup-profile profile1
-----------------------------------------------
Profile-Name : profile1
Service : arp
Remote-backup-service: service1
Backup-ID : 10
VRRP-ID : 1
VRRP-Interface : GigabitEthernet1/0/0
Interface :
State : Master
Peer-state : Slave
Backup mode : hot
Slot-Number : 1
Card-Number : 0
Port-Number : 0
Nas logic-port : Gigabitethernet 1/0/0
Nas logic-ip : 1.2.3.4
Nas logic-sysname : huawei
Traffic interval : 10(minutes)
After configuring the RBS, view RBS information. The command output shows that the TCP
connection status is Connected.
<RouterA> display remote-backup-service service1
----------------------------------------------------------
Service-Index : 0
Service-Name : service1
Peer-ip : 88.88.88.88
Source-ip : 22.22.22.22
TCP-Port : 2046
Track-BFD : --
Last up time : 2009-11-2 16:15:8
Last down time : 2009-11-2 16:3:36
--------------------------------------------------------
----End
Configuration Files
#
sysname RouterA
#
bfd bfd bind peer-ip 100.0.0.2
commit
#
vlan-type dot1q 200
ip address 100.0.0.1 255.255.255.0

admin-vrrp vrid 1
vrrp vrid 1 preempt-mode timer delay 600
vrrp vrid 1 track interface gigabitethernet 2/0/0 reduced 50
#
remote-backup-service service1
peer 88.88.88.88 source 22.22.22.22 port 2046
track interface gigabitethernet 2/0/0
#
remote-backup-profile profile1
service-type arp
backup-id 10 remote-backup-service service1
peer-backup hot
vrrp-id 1 interface gigabitethernet 1/0/0
#
user-vlan 50
#
interface LoopBack1
ip address 22.22.22.22 255.255.255.255
#
ospf 1
area 0.0.0.0
network 11.0.0.0 0.0.0.255
network 22.22.22.22 0.0.0.0
#
return

#
sysname RouterB
#
bfd bfd bind peer-ip 100.0.0.1
commit
#
vlan-type dot1q 200
ip address 100.0.0.2 255.255.255.0
admin-vrrp vrid 1
vrrp vrid 1 track interface gigabitethernet 2/0/0 reduced 50
#
remote-backup-service service1
peer 22.22.22.22 source 88.88.88.88 port 2046
track interface gigabitethernet 2/0/0
#
service-type arp
backup-id 10 remote-backup-service service1
peer-backup hot
vrrp-id 1 interface gigabitethernet 1/0/0
#
user-vlan 50
#
interface LoopBack1
ip address 88.88.88.88 255.255.255.255
#
ospf 1
area 0.0.0.0
network 11.0.0.0 0.0.0.255
network 88.88.88.88 0.0.0.0
#

return

Configuration Guide - Reliability A Glossary
A Glossary
This appendix collates frequently used glossaries in this document.

Glossary Description
Numerics
802.1 ag MAC Trace Similar to traceroute or tracert, 802.1ag MAC trace works by
sending test packets and waiting for a reply to test the path between
the local device and the destination device and to locate faults.
802.1ag MAC trace is initiated by a MEP and destined for a MEP
or MIP at the same maintenance level within any MA.
802.1ag MAC Ping Similar to ping, 802.1ag MAC ping works by sending test packets
and waiting for a reply to test whether the destination device is
reachable. 802.1ag MAC ping is initiated by a MEP and destined
for an MEP or MIP at the same maintenance level within any MA.
A
AMB Active Main Board
B
BFD Bidirectional Forwarding Detection
BGP Border Gateway Protocol
C
CCM Termination CCMs are generated and also terminated by MEPs. A MEP
forwards received CCMs at a higher level but drops CCMs at a
lower level or at the same level. In this manner, CCMs from a low-
level MD are confined within the bounds of the MD.
D
DMTI Desired Min TX Interval
DM Detect Multiplier

E
Ethernet OAM at the Ethernet OAM at the link level, such as Ethernet in the First Mile
Link Level OAM (EFM OAM) defined in IEEE 802.3ah, provides the
following functions for the link between the two directly connected
devices: Link connectivity check, Link monitoring, Remote failure
indication, Remote loopback.
Ethernet OAM at the Ethernet OAM at the network level, such as Ethernet Connectivity
Network Level Fault Management (CFM) defined in IEEE 802.1ag, provides the
following functions for the network: Fault detection, Fault
notification, Fault verification, and Fault location.
F
FRR Fast ReRoute
G
GR Graceful Restart
H
HA High Availability
L
LSP Label Switched Path
M
MA A Maintenance Association (MA) is part of an MD. An MD can
be divided into one or multiple MAs.
MD The Maintenance Domain (MD) refers to the network or the part
of the network for which connectivity is managed by CFM. The
devices in an MD are managed by a single ISP.
MEP A Maintenance association End Point (MEP) is an end point within
an MA.
MEP Database There is a MEP database on each device enabled with Ethernet
CFM. Each MEP database contains the local MEPs and RMEPs.
MIP A Maintenance association Intermediate Point (MIP) is an
intermediate point within an MA.
MP Either a MEP or a MIP is called a Maintenance Point (MP).
MTBF Mean Time Between Failure
MTTR Mean Time to Repair

OAMPDU OAM Protocol Data Unit
R
RMEP For the other devices in the same MA, their MEPs are called the
Remote Maintenance association End Points (RMEPs).
RMTI Required Min TX Interval
S
SMB Second Main Board
SP service provider
U
URL universal resource locator
UMG Universal Media Gateway
V
VRRP Virtual Router Redundancy Protocol
W
working mode of EFM The working mode of EFM OAM is an attribute of the interface
OAM enabled with EFM OAM. EFM OAM has two working modes:
active mode and passive mode.
WTR Wait To Restore

Configuration Guide - Reliability B Acronyms and Abbreviations
B Acronyms and Abbreviations
This appendix collates frequently used acronyms and abbreviations in this document.
Acronyms and Description
Abbreviations
A
AMB Active Main Board
B
BFD Bidirectional Forwarding Detection
BGP Border Gateway Protocol
D
DMTI Desired Min TX Interval
DM Detect Multiplier
F
FRR Fast ReRoute
G
GR Graceful Restart
H
HA High Availability
L
LSP Label Switched Path

Configuration Guide - Reliability B Acronyms and Abbreviations
Acronyms and Description

Abbreviations
MPLS TE FRR MultiProtocol Label Switching Traffic Engineering Fast Reroute
MTBF Mean Time Between Failure
MTTR Mean Time to Repair
R
RMTI Required Min TX Interval
S
SMB Second Main Board
SP service provider
U
URL universal resource locator
UMG Universal Media Gateway
V
VRRP Virtual Router Redundancy Protocol
W
WTR Wait To Restore


Configuration Guide - Reliability (V600R003C00 - 02)

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Configuration Guide - Reliability (V600R003C00 - 02)

Diunggah oleh

Hak Cipta:

HUAWEI NetEngine80E/40E Router

Configuration Guide - Reliability

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

Command Conventions (Optional)

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 01 (2011-06-30)

Issue 02 (2011-09-10) Huawei Proprietary and Confidential iv

About This Document.....................................................................................................................ii

2 Interface Backup Configuration...............................................................................................13

Issue 02 (2011-09-10) Huawei Proprietary and Confidential v

2.3.3 Configuring the Percentage Thresholds for Load Balancing..................................................................21

Issue 02 (2011-09-10) Huawei Proprietary and Confidential vi

4.2.1 Establishing the Configuration Task.......................................................................................................79

Issue 02 (2011-09-10) Huawei Proprietary and Confidential vii

4.10 Adjusting and Optimizing VRRP.................................................................................................................119

Issue 02 (2011-09-10) Huawei Proprietary and Confidential viii

5.2.1 Establishing the Configuration Task.....................................................................................................242

Issue 02 (2011-09-10) Huawei Proprietary and Confidential ix

5.11.3 Configuring the BFD WTR.................................................................................................................270

Issue 02 (2011-09-10) Huawei Proprietary and Confidential x

6.2.3 Enabling the Automatic Synchronization of the AMB/SMB Configuration........................................364

7 NSR Configuration................................................................................................................... 371

8 Ethernet OAM Configuration.................................................................................................377

Issue 02 (2011-09-10) Huawei Proprietary and Confidential xi

8.5.1 Establishing the Configuration Task.....................................................................................................403

Issue 02 (2011-09-10) Huawei Proprietary and Confidential xii

8.12.5 Checking the Configuration.................................................................................................................437

Issue 02 (2011-09-10) Huawei Proprietary and Confidential xiii

9.2.1 Establishing the Configuration Task.....................................................................................................558

Issue 02 (2011-09-10) Huawei Proprietary and Confidential xiv

9.9.3 Configuring DMM Reception on a Remote MEP.................................................................................599

10 MPLS-TP OAM Configuration.............................................................................................662

Issue 02 (2011-09-10) Huawei Proprietary and Confidential xv

10.4.2 Example for Configuring LB for an LSP............................................................................................691

11 Multi-Device Backup Configuration...................................................................................723

Issue 02 (2011-09-10) Huawei Proprietary and Confidential xvi

About This Chapter

Issue 02 (2011-09-10) Huawei Proprietary and Confidential 1

1.1.1 Overview of Reliability Technologies

1.1.2 Indices of Reliability

Issue 02 (2011-09-10) Huawei Proprietary and Confidential 2

1.1.3 Levels of Reliability Requirements

Table 1-1 Levels of reliability requirements

1 Less faults in the l Hardware: simplified design, standardized circuits,

2 No impact on a system l Redundancy design

3 Rapid recovery from a l Fault detection

1.1.4 Principles for High-Reliablity IP Networking