Configuration Guide - Reliability(V600R001C00_03)[1]

HUAWEI NetEngine80E/40E RouterV600R001C00

Configuration Guide - Reliability

Issue 03

Date 2010-03-31

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 03 (2010-03-31) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeThis part describes the organization of this document, product version, intended audience,conventions, and update history.

Related VersionsThe following table lists the product versions related to this document.

Product Name Version

HUAWEI NetEngine80E/40E V600R001C00

Intended AudienceThis document is intended for:

l Commissioning Engineer

l Data Configuration Engineer

l Network Monitoring Engineer

l System Maintenance Engineer

OrganizationThis document is organized as follows.

Chapter Describes

1 Reliability Overview This chapter describes the reliability technology of the IPnetwork and the reliability networking solution.

2 Interface BackupConfiguration

This chapter the methods of backing up the interface. It alsoprovides related configuration examples.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability About This Document


iii

Chapter Describes

3 APS Configuration This chapter describes the basic principles, configurationprocedures, and configuration examples of APS.

4 VRRP Configuration This chapter describes the fundamentals, the configurationsof basic and advanced functions of VRRP as well as VRRPmaintenance.

5 BFD Configuration This chapter describes the fundamentals, configurations ofBFD basic functions and BFD for IS-IS, maintenance andprovides configuration examples.

6 GR Configuration This chapter describes the HA implementation, theconfigurations of protocol-level GR (BGP GR, OSPF GR,IS-IS GR and MPLS LDP GR), system-level GR as well asHA maintenance and provides configuration examples.

7 Ethernet OAMConfiguration

This chapter describes the basic principles and theimplementations of the Ethernet OAM. It also providesconfiguration examples.

8 Configuring ISSU This section describes the concepts, working mechanism,configuration procedures, and maintenance commands ofISSU, and provides configuration examples.

A Glossary This appendix collates frequently used glossaries in thisdocument.

B Acronyms andAbbreviations

This appendix collates frequently used acronyms andabbreviations in this document.

Conventions

Symbol ConventionsThe symbols that may be found in this document are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk that, ifnot avoided, will result in death or serious injury.

Indicates a hazard with a medium or low level of riskwhich, if not avoided, could result in minor ormoderate injury.

About This DocumentHUAWEI NetEngine80E/40E Router


iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

Symbol Description

Indicates a potentially hazardous situation that, ifnot avoided, could cause device damage, data loss,and performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem orsave your time.

Provides additional information to emphasize orsupplement important points of the main text.

General ConventionsThe general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

boldface Names of files, directories, folders, and users are inboldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

Command ConventionsThe command conventions that may be found in this document are defined as follows.


boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[ ] Items (keywords or arguments) in square brackets [ ] areoptional.

{ x | y | ... } Alternative items are grouped in braces and separated byvertical bars. One is selected.

[ x | y | ... ] Optional alternative items are grouped in square bracketsand separated by vertical bars. One or none is selected.

{ x | y | ... }* Alternative items are grouped in braces and separated byvertical bars. A minimum of one or a maximum of all canbe selected.



v


[ x | y | ... ]* Optional alternative items are grouped in square bracketsand separated by vertical bars. Many or none can beselected.

&<1-n> This parameter before the & sign can be repeated 1 to ntimes.

# A line starting with the # sign is comments.

GUI ConventionsThe GUI conventions that may be found in this document are defined as follows.


boldface Buttons, menus, parameters, tabs, windows, and dialogtitles are in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">"signs. For example, choose File > Create > Folder.

Keyboard OperationThe keyboard operations that may be found in this document are defined as follows.

Format Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means the three keys should be pressedconcurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A meansthe two keys should be pressed in turn.

Mouse OperationThe mouse operations that may be found in this document are defined as follows.

Action Description

Click Select and release the primary mouse button withoutmoving the pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

About This DocumentHUAWEI NetEngine80E/40E Router


vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

Action Description

Drag Press and hold the primary mouse button and move thepointer to a certain position.

Update HistoryUpdates between document versions are cumulative. Therefore, the latest document versioncontains all updates made to previous versions.

Updates in Issue 03 (2010-03-31)The document is released for the third time.

Updates in Issue 02 (2009-12-10)The document is released for the second time.

Updates in Issue 01 (2009-09-05)The document is released for the first time.



vii

Contents

About This Document...................................................................................................................iii

1 Reliability Overview.................................................................................................................1-11.1 Introduction.....................................................................................................................................................1-2

1.1.1 Technology of Reliability Overview......................................................................................................1-21.1.2 Indices of Reliability..............................................................................................................................1-21.1.3 Levels of Reliability Requirements........................................................................................................1-31.1.4 Principles of Highly-Reliable IP Networking........................................................................................1-3

1.2 Reliability Technologies for IP Network........................................................................................................1-41.2.1 Failure Detection for IP Network...........................................................................................................1-41.2.2 Protection Switching for IP Network.....................................................................................................1-4

1.3 Reliability Technologies Supported by the NE80E/40E.................................................................................1-51.3.1 FRR (Fast ReRoute)...............................................................................................................................1-51.3.2 OAM (Operation Administration & Maintenance)................................................................................1-71.3.3 VRRP (Virtual Router Redundancy Protocol).......................................................................................1-71.3.4 BFD (Bidirectional Forwarding Detection)........................................................................................... 1-8

1.4 Networking of Reliability over an IP Network...............................................................................................1-81.4.1 Failures on Intermediate Nodes or on the Link Between PEs - LDP FRR/TE FRR..............................1-81.4.2 Link Failure During Transimission........................................................................................................1-91.4.3 Failure on the Remote PE - VPN FRR.................................................................................................1-111.4.4 Failure of Downlink Interface on the PE - IP FRR..............................................................................1-12

2 Interface Backup Configuration..............................................................................................2-12.1 Introduction of Interface Backup.................................................................................................................... 2-2

2.1.1 Interface Backup Overview....................................................................................................................2-22.1.2 Characteristics of the Interface Backup Supported by the NE80E/40E.................................................2-3

2.2 Configuring the Active/Standby Interface Backup.........................................................................................2-42.2.1 Establishing the Configuration Task......................................................................................................2-42.2.2 Configuring a Standby Interface............................................................................................................2-52.2.3 Configuring the Active/Standby Switchover Delay...............................................................................2-52.2.4 Checking the Configuration...................................................................................................................2-6

2.3 Configuring the Load Balancing Interface Backup.........................................................................................2-72.3.1 Establishing the Configuration Task......................................................................................................2-72.3.2 Configuring a Standby Interface............................................................................................................2-8

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability Contents


ix

2.3.3 Configuring the Percentage Thresholds for Load Balancing.................................................................2-82.3.4 (Optional) Configuring the Bandwidth and Flow Check Interval for the Active Interface...................2-92.3.5 Checking the Configuration.................................................................................................................2-10

2.4 Maintaining the Interface Backup.................................................................................................................2-102.4.1 Monitoring Working Status of the Interface Backup...........................................................................2-11

2.5 Configuration Examples................................................................................................................................2-112.5.1 Example for Configuring the Active/Standby Mode of Multiple Interfaces........................................2-112.5.2 Example for Configuring Load Balancing on Multiple Standby Interfaces........................................2-14

3 APS Configuration.....................................................................................................................3-13.1 APS Overview.................................................................................................................................................3-2

3.1.1 Introduction to APS................................................................................................................................3-23.1.2 APS Features Supported by the NE80E/40E.........................................................................................3-2

3.2 Configuring Single-Chassis APS....................................................................................................................3-23.2.1 Establishing the Configuration Task......................................................................................................3-33.2.2 Configuring the Working Interface of an APS Group...........................................................................3-33.2.3 Configuring the Protection Interface of an APS Group.........................................................................3-43.2.4 (Optional) Configuring the Working Mode for an APS Group.............................................................3-53.2.5 (Optional) Setting the WTR Time for an APS Group............................................................................3-53.2.6 Adding Members of an APS Group to a Trunk.....................................................................................3-63.2.7 Checking the Configuration...................................................................................................................3-7

3.3 Configuring E-APS.........................................................................................................................................3-73.3.1 Establishing the Configuration Task......................................................................................................3-83.3.2 Configuring the Working Interface of an APS Group...........................................................................3-83.3.3 Configuring the Protection Interface of an APS Group.........................................................................3-93.3.4 Configuring the Working Mode for an APS Group.............................................................................3-103.3.5 (Optional) Setting the Interval for Sending APS Negotiation Messages and the Hold Time of an APSConnection....................................................................................................................................................3-113.3.6 (Optional) Configuring the Authentication String for the PGP Message............................................3-113.3.7 (Optional) Setting the WTR Time for an APS Group..........................................................................3-123.3.8 Adding Members of an APS Group to a Trunk...................................................................................3-123.3.9 Checking the Configuration.................................................................................................................3-13

3.4 Configuration Examples................................................................................................................................3-143.4.1 Example for Associating PW Redundancy with APS..........................................................................3-143.4.2 Example for Configuring TDM on the CPOS interfaces Configured with APS ................................3-31

4 VRRP Configuration.................................................................................................................4-14.1 VRRP Introduction..........................................................................................................................................4-3

4.1.1 VRRP Overview.....................................................................................................................................4-34.1.2 VRRP Features Supported by the NE80E/40E......................................................................................4-3

4.2 Configuring the VRRP Backup Group............................................................................................................4-64.2.1 Establishing the Configuration Task......................................................................................................4-74.2.2 Creating a Backup Group and Configuring a Virtual IP Address..........................................................4-84.2.3 Configuring the Priority of an Interface in a Backup Group..................................................................4-9

ContentsHUAWEI NetEngine80E/40E Router


x Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

4.2.4 Checking the Configuration.................................................................................................................4-104.3 Configuring VRRP to Track the Status of an Interface.................................................................................4-11

4.3.1 Establishing the Configuration Task....................................................................................................4-114.3.2 Configuring VRRP to Track the Status of an Interface........................................................................4-124.3.3 Checking the Configuration.................................................................................................................4-13

4.4 Configuring VRRP Fast Switchover (Common Mode)................................................................................4-134.4.1 Establishing the Configuration Task....................................................................................................4-144.4.2 Tracking the BFD Session Status.........................................................................................................4-154.4.3 Tracking EFM Session Status..............................................................................................................4-164.4.4 Checking the Configuration.................................................................................................................4-16

4.5 Configuring VRRP Fast Switchover (Using BFD Sampling).......................................................................4-174.5.1 Establishing the Configuration Task....................................................................................................4-184.5.2 Binding the Service VRRP Backup Group to the mVRRP Backup Group.........................................4-204.5.3 Configuring the mVRRP Backup Group to Track the BFD Session Status........................................4-204.5.4 Setting the Threshold for VRRP Fast Switchover...............................................................................4-224.5.5 Enabling the Association Between the mVRRP Backup Group Status and the Route........................4-224.5.6 Checking the Configuration.................................................................................................................4-23

4.6 Configuring Ignorance of the Down of an Interface Where the mVRRP Backup Group Is Configured.....4-244.6.1 Establishing the Configuration Task....................................................................................................4-244.6.2 Configuring the mVRRP Backup Group.............................................................................................4-264.6.3 Binding the Service VRRP Backup Group to the mVRRP Backup Group.........................................4-274.6.4 Configuring the mVRRP Backup Group to Track the BFD Session Status........................................4-274.6.5 Setting the Threshold for VRRP Fast Switchover...............................................................................4-294.6.6 Enabling the Association Between the mVRRP Backup Group Status and the Route........................4-294.6.7 Checking the Configuration.................................................................................................................4-30

4.7 Configuring VRRP Applications in VLANIF...............................................................................................4-314.7.1 Establishing the Configuration Task....................................................................................................4-314.7.2 Configuring VRRP on VLANIF..........................................................................................................4-324.7.3 (Optional) Configuring the Sending Mode of VRRP Packets in Super-VLAN..................................4-324.7.4 Checking the Configuration.................................................................................................................4-33

4.8 Configuring VRRP Security..........................................................................................................................4-334.8.1 Establishing the Configuration Task....................................................................................................4-334.8.2 Configuring the Authentication Mode of VRRP Packets....................................................................4-344.8.3 Checking the Configuration.................................................................................................................4-35

4.9 Configuring VRRP Smooth Switching.........................................................................................................4-364.9.1 Establishing the Configuration Task....................................................................................................4-364.9.2 Configuring VRRP Smooth Switching................................................................................................4-364.9.3 Checking the Configuration.................................................................................................................4-37

4.10 Adjusting and Optimizing VRRP................................................................................................................4-384.10.1 Establishing the Configuration Task..................................................................................................4-384.10.2 Configuring the Interval for Sending VRRP Advertising Messages.................................................4-394.10.3 Configuring the Preemption Delay Time of Backup Group Routers.................................................4-40



xi

4.10.4 Enabling the Reachability Test of the Virtual IP Address.................................................................4-414.10.5 Disabling a Router from Checking Number of Hops in VRRP Packets............................................4-414.10.6 Configuring the Timeout Time of Sending Gratuitous ARP Packets by the Master router...............4-424.10.7 Checking the Configuration...............................................................................................................4-42

4.11 Configuring mVRRP Backup Groups.........................................................................................................4-434.11.1 Establishing the Configuration Task..................................................................................................4-434.11.2 Configuring mVRRP Backup Group.................................................................................................4-454.11.3 (Optional) Configuring VRRP Backup Group Members and Binding them to the mVRRP Backup Group.......................................................................................................................................................................4-454.11.4 (Optional) Binding Member Interface and Management Backup Group...........................................4-464.11.5 (Optional) Binding the PW to the mVRRP Backup Group Through VPLS......................................4-474.11.6 Checking the Configuration...............................................................................................................4-47

4.12 Maintaining VRRP......................................................................................................................................4-484.12.1 Monitoring the VRRP Running..........................................................................................................4-48

4.13 Configuration Examples..............................................................................................................................4-494.13.1 Example for Configuring VRRP in Master/Backup Mode................................................................4-494.13.2 Example for Configuring VRRP in Load Balancing Mode...............................................................4-534.13.3 Example for Configuring the Multi-Instance VRRP..........................................................................4-574.13.4 Example for Configuring VRRP Fast Switchover.............................................................................4-624.13.5 Example for Configuring VRRP Fast Switchover (Using BFD Sampling).......................................4-674.13.6 Example for Configuring Ignorance of the Down of an Interface Where the mVRRP Backup Group IsConfigured.....................................................................................................................................................4-854.13.7 Example for Configuring VRRP on VLANIF Interfaces.................................................................4-105

5 BFD Configuration.....................................................................................................................5-15.1 BFD Introduction............................................................................................................................................5-3

5.1.1 BFD Overview.......................................................................................................................................5-35.1.2 BFD Features Supported by the NE80E/40E.........................................................................................5-3

5.2 Configuring the One-Hop BFD.......................................................................................................................5-95.2.1 Establishing the Configuration Task....................................................................................................5-105.2.2 Enabling the Global BFD.....................................................................................................................5-105.2.3 Setting Up a BFD Session....................................................................................................................5-115.2.4 Checking the Configuration.................................................................................................................5-12

5.3 Configuring the BFD Passive Echo Function...............................................................................................5-135.3.1 Establishing the Configuration Task....................................................................................................5-135.3.2 Configuring the BFD Passive Echo Function......................................................................................5-145.3.3 Checking the Configuration.................................................................................................................5-15

5.4 Configuring the Association Between the BFD Status and the Interface Status...........................................5-165.4.1 Establishing the Configuration Task....................................................................................................5-165.4.2 Configuring the Association Between BFD Status and Interface Status.............................................5-175.4.3 Checking the Configuration.................................................................................................................5-18

5.5 Configuring the Association Between the BFD Status and the Sub-Interface Status...................................5-195.5.1 Establishing the Configuration Task....................................................................................................5-195.5.2 Configuring the Association Between BFD Status and Sub-Interface Status......................................5-20



xii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

5.5.3 Checking the Configuration.................................................................................................................5-215.6 Configuring the BFD to Modify the PST......................................................................................................5-21

5.6.1 Establishing the Configuration Task....................................................................................................5-225.6.2 Permitting the BFD to Modify the PST...............................................................................................5-225.6.3 Checking the Configuration.................................................................................................................5-23

5.7 Configuring the Multi-Hop BFD...................................................................................................................5-245.7.1 Establishing the Configuration Task....................................................................................................5-245.7.2 Enabling BFD Globally........................................................................................................................5-255.7.3 Setting Up a BFD Session....................................................................................................................5-255.7.4 Checking the Configuration.................................................................................................................5-26

5.8 Configuring the BFD Session with Automatically Negotiated Discriminator..............................................5-275.8.1 Establishing the Configuration Task....................................................................................................5-275.8.2 Enabling BFD Globally........................................................................................................................5-285.8.3 Configuring the BFD Session with Automatically Negotiated Discriminator.....................................5-285.8.4 Checking the Configuration.................................................................................................................5-29

5.9 Configuring the Delay of the BFD Session to Be Up...................................................................................5-305.9.1 Establishing the Configuration Task....................................................................................................5-305.9.2 Configuring the Delay of the BFD Session to Be Up..........................................................................5-305.9.3 Checking the Configuration.................................................................................................................5-31

5.10 Adjusting BFD Parameters..........................................................................................................................5-325.10.1 Establishing the Configuration Task..................................................................................................5-325.10.2 Modifying the Detection Time...........................................................................................................5-335.10.3 Configuring the BFD WTR................................................................................................................5-345.10.4 Adding the Description of a BFD Session.........................................................................................5-345.10.5 Checking the Configuration...............................................................................................................5-35

5.11 Globally Configuring the Destination Port Number for the Multi-Hop BFD Control Packet....................5-365.11.1 Establishing the Configuration Task..................................................................................................5-365.11.2 Globally Configuring the Destination Port Number..........................................................................5-375.11.3 Checking the Configuration...............................................................................................................5-38

5.12 Configuring the TTL Globally....................................................................................................................5-385.12.1 Establishing the Configuration Task..................................................................................................5-395.12.2 Configuring the TTL Globally...........................................................................................................5-395.12.3 Checking the Configuration...............................................................................................................5-40

5.13 Configuring the Interval for Sending Trap Messages.................................................................................5-405.13.1 Establishing the Configuration Task..................................................................................................5-405.13.2 Configuring the Interval for Sending Trap Messages........................................................................5-415.13.3 Checking the Configuration...............................................................................................................5-41

5.14 Maintaining BFD.........................................................................................................................................5-425.14.1 Clearing the BFD Statistics................................................................................................................5-425.14.2 Monitoring the Running of BFD........................................................................................................5-42

5.15 Configuration Examples..............................................................................................................................5-435.15.1 Example for Configuring One-Hop BFD for Layer 3 Physical Link.................................................5-43



xiii

5.15.2 Example for Configuring the One-Hop BFD for IP-Trunk Member Link.........................................5-465.15.3 Example for Configuring One-Hop BFD for IP-Trunk..................................................................... 5-515.15.4 Example for Configuring One-Hop BFD for Layer 3 Eth-Trunk Member Link...............................5-575.15.5 Example for Configuring One-Hop BFD for Layer 3 Eth-Trunk......................................................5-615.15.6 Example for Configuring One-Hop BFD for VLANIF Interfaces.....................................................5-675.15.7 Example for Configuring the Association Between the BFD Status and the Interface Status...........5-715.15.8 Example for Configuring the Association Between the BFD Status and the Sub-Interface Status.......................................................................................................................................................................5-765.15.9 Example for Configuring Multi-Hop BFD.........................................................................................5-805.15.10 Example for Configuring the BFD for VPN Routes........................................................................5-83

6 GR Configuration.......................................................................................................................6-16.1 GR Introduction...............................................................................................................................................6-2

6.1.1 HA Overview.........................................................................................................................................6-26.1.2 GR Features Supported in the NE80E/40E............................................................................................6-9

6.2 Configuring the System-Level GR..................................................................................................................6-96.2.1 Establishing the Configuration Task....................................................................................................6-106.2.2 (Optional) Configuring the Default Slot Number for the SMB...........................................................6-106.2.3 Enabling the Automatic Synchronization of the AMB/SMB Configuration.......................................6-116.2.4 Enabling the Force AMB/SMB Switchover.........................................................................................6-116.2.5 (Optional) Restarting the SMB............................................................................................................ 6-126.2.6 Checking the Configuration.................................................................................................................6-12

6.3 Maintaining HA.............................................................................................................................................6-126.3.1 Monitoring the Running of HA............................................................................................................6-12

6.4 Configuration Examples................................................................................................................................6-136.4.1 Example for Configuring the System-Level GR..................................................................................6-13

7 Ethernet OAM Configuration..................................................................................................7-17.1 Ethernet OAM Overview................................................................................................................................7-3

7.1.1 Introduction to Ethernet OAM...............................................................................................................7-37.1.2 Ethernet OAM Supported by the NE80E/40E.......................................................................................7-4

7.2 Configuring Basic EFM OAM......................................................................................................................7-147.2.1 Establishing the Configuration Task....................................................................................................7-147.2.2 Enabling EFM OAM Globally.............................................................................................................7-157.2.3 Configuring the Working Mode of EFM OAM on an Interface..........................................................7-157.2.4 (Optional) Setting the Maximum Size of an EFM OAMPDU.............................................................7-167.2.5 Enabling EFM OAM on an Interface...................................................................................................7-167.2.6 Checking the Configuration.................................................................................................................7-17

7.3 Configuring EFM OAM Link Monitoring....................................................................................................7-187.3.1 Establishing the Configuration Task....................................................................................................7-187.3.2 (Optional) Detecting Errored Frames of EFM OAM...........................................................................7-187.3.3 (Optional) Detecting Errored Codes of EFM OAM.............................................................................7-197.3.4 (Optional) Detecting Errored Frame Seconds of EFM OAM..............................................................7-207.3.5 Checking the Configuration.................................................................................................................7-21



xiv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

7.4 Testing the Packet Loss Ratio on the Physical Link.....................................................................................7-217.4.1 Establishing the Configuration Task....................................................................................................7-227.4.2 Enabling EFM OAM Remote Loopback.............................................................................................7-237.4.3 Sending Test Packets............................................................................................................................7-237.4.4 Checking the Statistics on Returned Test Packets...............................................................................7-247.4.5 (Optional) Manually Disabling EFM OAM Remote Loopback..........................................................7-247.4.6 Checking the Configuration.................................................................................................................7-25

7.5 Associating EFM OAM with an Interface....................................................................................................7-267.5.1 Establishing the Configuration Task....................................................................................................7-267.5.2 Associating EFM OAM with an Interface...........................................................................................7-277.5.3 Checking the Configuration.................................................................................................................7-27

7.6 Configuring Basic Ethernet CFM.................................................................................................................7-287.6.1 Establishing the Configuration Task....................................................................................................7-297.6.2 Switching IEEE 802.1ag Versions.......................................................................................................7-307.6.3 Enabling Ethernet CFM Globally........................................................................................................7-307.6.4 Creating an MD....................................................................................................................................7-317.6.5 (Optional) Creating the Default MD....................................................................................................7-317.6.6 Creating an MA....................................................................................................................................7-327.6.7 Creating a MEP....................................................................................................................................7-337.6.8 Creating an RMEP...............................................................................................................................7-347.6.9 (Optional) Setting the Rule for Creating a MIP...................................................................................7-357.6.10 Enabling CC Detection.......................................................................................................................7-367.6.11 (Optional) Creating a VLAN..............................................................................................................7-377.6.12 Checking the Configuration...............................................................................................................7-37

7.7 Configuring Related Parameters of Ethernet CFM.......................................................................................7-417.7.1 Establishing the Configuration Task....................................................................................................7-417.7.2 (Optional) Configuring the RMEP Activation Time............................................................................7-427.7.3 (Optional) Configuring the Anti-Jitter Time During Alarm Restoration.............................................7-437.7.4 (Optional) Configuring the Anti-Jitter Time During Alarm Generation..............................................7-43

7.8 Fault Verification on the Ethernet.................................................................................................................7-447.8.1 Establishing the Configuration Task....................................................................................................7-447.8.2 (Optional) Implementing 802.1ag MAC Ping......................................................................................7-457.8.3 (Optional) Implementing Gmac ping...................................................................................................7-46

7.9 Locating the Fault on the Ethernet................................................................................................................7-467.9.1 Establishing the Configuration Task....................................................................................................7-477.9.2 (Optional) Implementing 802.1ag MAC Trace....................................................................................7-477.9.3 (Optional) Implementing Gmac trace...................................................................................................7-48

7.10 Associating Ethernet CFM with an Interface..............................................................................................7-497.10.1 Establishing the Configuration Task..................................................................................................7-497.10.2 Associating Ethernet CFM with an Interface.....................................................................................7-527.10.3 Checking the Configuration...............................................................................................................7-52

7.11 Associating EFM OAM with Ethernet CFM..............................................................................................7-53



xv

7.11.1 Establishing the Configuration Task..................................................................................................7-537.11.2 Associating Ethernet OAM with Ethernet OAM...............................................................................7-547.11.3 Checking the Configuration...............................................................................................................7-55

7.12 Associating Ethernet CFM with VPLS.......................................................................................................7-557.12.1 Establishing the Configuration Task..................................................................................................7-557.12.2 Configuring Ethernet CFM Based on the VPLS Between the PEs....................................................7-567.12.3 Configuring Ethernet CFM Between the CE and Local PE...............................................................7-577.12.4 Configuring Ethernet CFM Between the CE and Peer PE.................................................................7-597.12.5 Checking the Configuration...............................................................................................................7-59

7.13 Associating Ethernet OAM with MPLS OAM or BFD..............................................................................7-597.13.1 Establishing the Configuration Task..................................................................................................7-597.13.2 Configuring Ethernet OAM Functions...............................................................................................7-607.13.3 Associating Ethernet OAM with MPLS OAM or BFD.....................................................................7-617.13.4 Checking the Configuration...............................................................................................................7-62

7.14 Configuring Ethernet CFM and 1+1 Protection of Multicast VLANs........................................................7-627.15 Maintaining Ethernet OAM........................................................................................................................ 7-62

7.15.1 Clearing the Statistics on Error CCMs...............................................................................................7-627.15.2 Monitoring the Running Status of Ethernet OAM.............................................................................7-63

7.16 Configuration Examples..............................................................................................................................7-637.16.1 Example for Configuring EFM OAM................................................................................................7-647.16.2 Example for Testing the Packet Loss Ratio on the Link....................................................................7-677.16.3 Example for Configuring Ethernet CFM........................................................................................... 7-707.16.4 Example for Configuring the Default MD for Ethernet CFM............................................................7-787.16.5 Example for Associating Ethernet CFM with an Interface................................................................7-857.16.6 Example for Associating EFM OAM with Ethernet CFM................................................................ 7-917.16.7 Example for Configuring VPLS Ethernet CFM.................................................................................7-957.16.8 Example for Associating EFM OAM with MPLS OAM.................................................................7-1067.16.9 Example for Configuring EFM OAM Extension for VRRP............................................................7-1157.16.10 Exmaple for Configuring EFM OAM Extension for Static Routes...............................................7-125

8 Configuring ISSU.......................................................................................................................8-18.1 Introduction.....................................................................................................................................................8-2

8.1.1 Introduction to ISSU..............................................................................................................................8-28.1.2 ISSU Supported by the NE80E/40E.......................................................................................................8-2

8.2 Implementing ISSU.........................................................................................................................................8-38.2.1 Establishing the Configuration Task......................................................................................................8-48.2.2 (Optional) Configuring ISSU Precheck.................................................................................................8-48.2.3 (Optional) Configuring the Length of the ISSU Rollback Timer..........................................................8-58.2.4 Implementing ISSU................................................................................................................................8-58.2.5 Checking the Configuration...................................................................................................................8-8

8.3 Maintaining ISSU..........................................................................................................................................8-118.3.1 Monitoring the Running Status of ISSU..............................................................................................8-11

8.4 Configuration Examples................................................................................................................................8-12



xvi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

8.4.1 Example for Implementing ISSU.........................................................................................................8-12

A Glossary.....................................................................................................................................A-1

B Acronyms and Abbreviations.................................................................................................B-1



xvii

Figures

Figure 1-1 LAN default gateway..........................................................................................................................1-7Figure 1-2 Networking diagram of LDP/TE FRR application.............................................................................1-8Figure 1-3 Networking diagram of MPLS OAM protecting switchover...........................................................1-10Figure 1-4 Networking diagram of BFD for VRRP...........................................................................................1-11Figure 1-5 Networking diagram of VPN FRR application................................................................................ 1-11Figure 1-6 Networking diagram of IP FRR application.....................................................................................1-12Figure 2-1 Interface backups................................................................................................................................2-2Figure 2-2 Active/standby mode..........................................................................................................................2-3Figure 2-3 Load-balancing mode.........................................................................................................................2-4Figure 2-4 Networking diagram of configuring the active/standby interface backup........................................2-11Figure 3-1 Networking of the association between PW redundancy and APS..................................................3-14Figure 3-2 Networking diagram of configuring TDMoPSN..............................................................................3-32Figure 4-1 LAN default gateway..........................................................................................................................4-3Figure 4-2 Typical networking of VRRP fast switchover (using BFD sampling).............................................4-19Figure 4-3 Typical networking of ignorance of the down of an interface where the mVRRP backup group isconfigured............................................................................................................................................................4-25Figure 4-4 mVRRP determines the dual-homing of the master and slave routers.............................................4-43Figure 4-5 Networking diagram of configuring VRRP in the master/backup mode......................................... 4-49Figure 4-6 Networking diagram of configuring VRRP in load balancing mode...............................................4-54Figure 4-7 Networking diagram of configuring VRRP multi-instance..............................................................4-58Figure 4-8 Networking diagram of configuring VRRP fast switchover............................................................ 4-63Figure 4-9 Typical networking of VRRP fast switchover (using BFD sampling).............................................4-68Figure 4-10 Typical networking of ignorance of the down of an interface where the mVRRP backup group isconfigured............................................................................................................................................................4-87Figure 4-11 Networking diagram of VRRP configured on VLANIF interfaces..............................................4-106Figure 5-1 Application scenario of the BFD passive Echo function..................................................................5-13Figure 5-2 Networking diagram of devices between the both end routers.........................................................5-16Figure 5-3 Networking diagram of configuring the one-hop BFD.................................................................... 5-43Figure 5-4 Networking diagram of configuring one-hop BFD for IP-Trunk member link................................5-46Figure 5-5 Networking diagram of configuring one-hop BFD for IP-Trunk.....................................................5-51Figure 5-6 Networking diagram of configuring one-hop BFD for Layer 3 Eth-Trunk member link...............5-57Figure 5-7 Networking diagram of configuring one-hop BFD for Layer 3 Eth-Trunk......................................5-62Figure 5-8 Networking diagram of configuring one-hop BFD for VLANIF interfaces.................................... 5-67Figure 5-9 Configuring the association between the BFD status and the interface status.................................5-71

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability Figures


xix

Figure 5-10 Association between the BFD status and the sub-interface status..................................................5-76Figure 5-11 Networking diagram of the multi-hop BFD...................................................................................5-81Figure 5-12 Networking diagram of configuring the BFD for VPN routes.......................................................5-84Figure 6-1 Basic mechanism of HSB...................................................................................................................6-4Figure 6-2 Setting up sessions between the GR Helper and the GR Restarter.....................................................6-6Figure 6-3 AMB/SMB switchover of the GR Restarter.......................................................................................6-6Figure 6-4 GR Restarter sending signals to the neighbors after the AMB/SMB switchover...............................6-7Figure 6-5 GR Restarter obtaining topology information from neighbors...........................................................6-7Figure 6-6 Networking diagram of configuring the system-level GR...............................................................6-13Figure 7-1 Networking diagram of EFM OAM extension for VRRP................................................................7-10Figure 7-2 Networking diagram of EFM OAM extension for static routes.......................................................7-13Figure 7-3 Diagram of configuring EFM OAM.................................................................................................7-14Figure 7-4 Diagram of testing the packet loss ratio on the link.........................................................................7-22Figure 7-5 Diagram of associating EFM OAM with an interface......................................................................7-26Figure 7-6 Diagram of associating Ethernet CFM with an interface (1)............................................................7-50Figure 7-7 Diagram of associating Ethernet CFM with an interface (2)............................................................7-50Figure 7-8 Diagram of associating Ethernet CFM with an interface (3)............................................................7-50Figure 7-9 Diagram of associating Ethernet CFM with an interface (4)............................................................7-51Figure 7-10 Diagram of associating Ethernet OAM with Ethernet OAM.........................................................7-53Figure 7-11 Figure 6-11 Networking diagram of associating Ethernet CFM with VPLS.................................7-55Figure 7-12 Diagram of associating Ethernet OAM with MPLS OAM or BFD...............................................7-60Figure 7-13 Diagram of configuring EFM OAM...............................................................................................7-64Figure 7-14 Diagram of testing the packet loss ratio on the link.......................................................................7-67Figure 7-15 Diagram of configuring Ethernet CFM..........................................................................................7-70Figure 7-16 Networking diagram of configuring the default MD for Ethernet CFM........................................7-78Figure 7-17 Diagram of associating Ethernet CFM with an interface...............................................................7-86Figure 7-18 Diagram of associating EFM OAM with Ethernet CFM...............................................................7-91Figure 7-19 Diagram of configuring VPLS Ethernet CFM...............................................................................7-95Figure 7-20 Diagram of associating EFM OAM with MPLS OAM................................................................7-106Figure 7-21 Networking diagram of configuring EFM OAM extension for VRRP........................................7-116Figure 7-22 Networking diagram of configuring EFM OAM extension for static routes...............................7-125

FiguresHUAWEI NetEngine80E/40E Router


xx Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

Tables

Table 1-1 Levels of reliability requirements........................................................................................................1-3Table 3-1 Interfaces and IP address....................................................................................................................3-15Table 4-1 Networking requirements of the multi-instance VRRP.....................................................................4-57Table 6-1 Comparison between the GR and the HSB..........................................................................................6-8Table 7-1 Differences between IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007..................................7-5Table 8-1 Description of the issu check command output...................................................................................8-6Table 8-2 Description of the issu start command output....................................................................................8-7Table 8-3 Description of the issu abort command output...................................................................................8-8

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability Tables


xxi

1 Reliability Overview

About This Chapter

This chapter describes the technologies and indices of the reliability.

1.1 IntroductionThis section describes the technologies and indices of the reliability.

1.2 Reliability Technologies for IP NetworkThis section describes the common reliability technologies applied to IP networks.

1.3 Reliability Technologies Supported by the NE80E/40EThis section describes the common reliability technologies supported by the NE80E/40E.

1.4 Networking of Reliability over an IP NetworkThis section describes the typical networking schemes of IP network reliability.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability 1 Reliability Overview


1-1

1.1 IntroductionThis section describes the technologies and indices of the reliability.

1.1.1 Technology of Reliability Overview

1.1.2 Indices of Reliability

1.1.3 Levels of Reliability Requirements

1.1.4 Principles of Highly-Reliable IP Networking

1.1.1 Technology of Reliability OverviewThe reliability of a router is assessed in the following aspects:

l Principle of reliable system and hardware design

l Principle of reliable software design

l Test and authentication of reliability

l Reliable IP network design

With the popularity of networks and diversification of applications, various value-added servicesare deployed on networks. The bandwidth increases in index number. Therefore, even a short-time interrupt may impact a huge number of services critically and make an incredible loss.

For a fundamental network that bears various services, its reliability is highlighted much morethan ever.

This chapter focuses on reliability technologies applicable to the IP network over the VersatileRouting Platform (NE80E/40E).

1.1.2 Indices of ReliabilityGenerally, 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

MTTR: identifies the default recovery capability in terms of maintainability. The term refers toan average time that a component or a device takes to recover from a failure. In fact, it is thefault-tolerance capability. In a broader sense, the MTTR also includes spare part managementand customer service. The MTTR plays an important role in evaluating maintainability.

The formula of the MTTR is as follows:

MTTR = Fault detection time + Board replacement time + System initialization time + Linkrecovery time + Route coverage time + Forwarding recovery time

The smaller the addends are, the smaller the MTTR is and the higher the availability the deviceoffers.

1 Reliability OverviewHUAWEI NetEngine80E/40E Router


1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

MTBFMTBF identifies the probability of faults in terms of reliability. The term refers to the averagetime when a component or a device runs without any failure, usually in hours.

In the telecommunication industry, the availability of 99.999% means that the MTTR must beno more than five minutes each year.

AvailabilityAvailability identifies the utility of a system. The availability is improved when the MTBFincreases or the MTTR decreases.

In real networking, however, it may be inevitable to witness network faults and serviceinterruption for various causes. Therefore, a kind of technology to recover the device from thefault rapidly becomes even important. This technology can just improve the availability byreducing MTTR.

1.1.3 Levels of Reliability RequirementsTable 1-1 describes three requirement levels, their targets, and implementation methods.

Table 1-1 Levels of reliability requirements

Level Target Implementation

1 Less faults on thesoftware and hardwareof a system

l Hardware: simplified design, standardized circuits,reliable application of components, reliability controlin purchased components, reliable manufacture,environment endurability, and reliability experiment(HALT/HASS)

l Software: checklist of reliable software design

2 No impact on a systemwhen a default occurs

l Redundancy design

l Switchover policy

l High availability of switchover

3 Rapid recovery when afault occurs and affectsthe system

l Fault detection

l Diagnosis

l Isolation

l Recovery

1.1.4 Principles of Highly-Reliable IP NetworkingThe principles of reliable IP networking are as follows:

l Hierarchical networking: A network is divided into three layers, that is, core layer,convergence layer, and edge layer. According to the current and future services, redundancybackup is configured on a device connects to access nodes on the edge layer. The activeand 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



1-3

convergence layer and core layer alternatively. Devices of core layer are enabled with fullinterconnection or half interconnection. In this manner, two devices are reachable to eachother with one route at a fast traffic rate, avoiding multi-interconnection.

l On the same layer, multi-interconnection is applicable; multi-device is applicable to a singlenode.

l The lower-layer devices are dual-homed or multi-homed to single nodes or multiple nodesof devices on the upper layer.

l Adjustment should be taken according to traffic.

1.2 Reliability Technologies for IP NetworkThis section describes the common reliability technologies applied to IP networks.

1.2.1 Failure Detection for IP Network

1.2.2 Protection Switching for IP Network

1.2.1 Failure Detection for IP NetworkIn terms of implementation range, fault detection technologies include special detectiontechnology and common detection technology.

l Special fault detection technologies include:– APS (on transport layer)

– RPR OAM, Eth-OAM (on link layer)

– MPLS OAM (for MPLS)

l Common fault detection technology includes the Bidirectional Forwarding Detection(BFD) that detects faults on all layers.

The fault detection mechanism is available on each layer of the TCP/IP reference module. Thefault detection mechanisms are as follows:

l Transport/Physical layer: APS

l Data link layer: RPR OAM, MPLS OAM, Eth-OAM, STP, RSTP, MSTP, and RRPP

l Network layer: Hello mechanism in different protocols, VRRP, and GR

l Application layer: heartbeat mechanism and re-forwarding mechanism of various protocols

The modes of fault detection are as follows:

l Asynchronous mode: The detection packet is sent periodically.

l Query mode: A series of packets for confirmation are sent.

l Echo mode: The received packet is sent back to the peer without any change.

1.2.2 Protection Switching for IP NetworkOn data communication networks, 50 ms is a standard time for performing the protectionswitching. The protection switching takes place based on the link redundancy.

The protection modes are as follows:




Issue 03 (2010-03-31)

l End-to-end protection: 1:1, 1+1, 1:N, and M:N

l Local protection: FRR

The trigger mode includes BFD trigger mode and Fast Reroute (FRR) trigger mode.

The protection switching functions are as follows:

l Local request protection

l Local real-time protection

l Latency of switchover signal processing

l Anti-switching of a single node

l Coexistence and preemption of switchover request

l Switchover recovery mode

1.3 Reliability Technologies Supported by the NE80E/40EThis section describes the common reliability technologies supported by the NE80E/40E.

1.3.1 FRR (Fast ReRoute)

1.3.2 OAM (Operation Administration & Maintenance)

1.3.3 VRRP (Virtual Router Redundancy Protocol)

1.3.4 BFD (Bidirectional Forwarding Detection)

1.3.1 FRR (Fast ReRoute)

IP FRR

In the forwarding module, an interface status table is created to save information about workingstatus of every interface on a device. After an abnormality is detected, for example, the physicallink is unavailable or an interface is shut down manually, the interface status table is updated.

At the same time, when a packet is forwarded to a next hop listed in a forwarding table thatcontains load balancing entries, that is, several next hops, the next hop is selected by certainrules and its outgoing interface is detected in the interface status table. If the outgoing interfaceof one next hop is invalid, another next hop is selected and its outgoing interface status is detecteduntil the outgoing interface of a next hop is valid.

When the last next hop is detected, the packet is forwarded directly without checking theoutgoing interface.

Because detecting and updating the interface status is much faster than route convergence, thererouting takes effect faster with the IP FRR technology. Moreover, the load balancing entriesin the forwarding table are checked that ensures highly-reliable forwarding.

The enhanced IP FRR technology supports the next hop of non-equivalence load balancer. Anactive next hop is selected by the Interior Gateway Protocol (IGP) and a standby next hop isconfigured manually. When a failure occurs, the fast switchover is performed.



1-5

LDP FRRConventional IP FRR cannot effectively protect traffic on a Multiprotocol Label Switching(MPLS) network. The NE80E/40E provides MPLS networks with the LDP FRR for protectionat the interface level.

Compared with fast convergence in IGP, the LDP FRR calculates a secondary interface inadvance. Route calculation and re-establishment of an LSP after a failure take less time. As aresult, the switchover speeds up.

When LDP works in a mode of Downstream Unsolicited (DU) label distribution, ordered labelcontrol and liberal label retention, a Label Switching Router (LSR) saves all label mappingmessages. Only the label mapping messages sent by the next hop corresponding to theForwarding Equivalence Class (FEC) can generate a label forwarding table.

With the preceding features, when a forwarding table is generated for mapping of liberalretention label, this means that a bypass LSP is established. Normally, a packet is forwardedthrough the primary LSP. When the outgoing interface of the primary LSP is Down, the packetis forwarded along the bypass LSP. This ensures continuous traffic follow in the short periodbefore network convergence.

MPLS TE FRRThe MPLS TE FRR is a commonly used switchover technology to deal with a failure. Thesolution is to create an end-to-end TE tunnel between Provider Edge (PE) devices and a bypassLabel Switched Path (LSP) for protecting a primary LSP. When the router detects that theprimary LSP is unavailable because of an intermediate node failure or link failure, the traffic isswitched to the bypass LSP.

In terms of principle, MPLS TE FRR can enable fast switchover to respond to link failures andnode failures between two PEs that serve as the start node and end node of a TE tunnelrespectively.

Nevertheless, MPLS TE FRR cannot deal with the failure of PEs that serves as the start nodeand end node on a TE tunnel. When a PE fails, the traffic can resume by end-to-end routeconvergence and LSP convergence. The time of convergence relates closely to the number ofroutes of the MPLS VPN and the number of hops of the bearer network. Generally, theconvergence takes about 5s in typical networking, longer than 1s that is required for the end-to-end traffic convergence when a node fails.

VPN FRRBased on the VPN fast route switching technology, VPN FRR sets a switchover forwardingentry that is destined for the primary PE and backup PE on a remote PE. With VPN FRR andthe technology of fast sense of PE failures, on an MPLS VPN where Costumer Edge (CE) devicesare dual-homed to PEs, the time of end-to-end service convergence is shortened and the time ofPE failure recovery cannot be affected by the number of private network routes. When a PEnode 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 matchingpolicy. 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 theinferior 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 theouter tunnel connecting the PE to the preferential node is unavailable. The PE sets a




Issue 03 (2010-03-31)

corresponding flag in the LSP tunnel status table to indicates the outer LSP is unavailable anddelivers the flag to the forwarding engine. When the forwarding engine selects a forwardingentry, it checks the LSP tunnel status corresponding to this forwarding entry. If the LSP tunnelis unavailable, the engine uses the route of a inferior priority carried in this forwarding entry toforward packets.

1.3.2 OAM (Operation Administration & Maintenance)In board sense, the Operation Administration & Maintenance (OAM) exists on every layer, link,and node of a network. With OAM, you can simplify the operation, check the networkperformance at any moment, and cut the cost of network operation. This section describes onlyMPLS OAM.

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 MPLSand 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, enablingthe following features on the MPLS user plane:

l Detecting the TE LSP connectivityl 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 MPLSlayer 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)Generally, all hosts of a LAN are configured with the same default route to the gateway, forexample, Router A in Figure 1-1. In this manner, the hosts can communicate with externalnetworks. When the gateway fails, the communication between hosts and external networks isinterrupted.

Figure 1-1 LAN default gateway

Ethernet

Gateway:10.0.0.1IP Address:10.0.0.2/24



RouterA10.0.0.1/24

Network

A common method to enhance the system reliability is to configure several gateways, but howto select routes among several gateways becomes a problem. As a type of redundancy protocol,



1-7

the Virtual Router Redundancy Protocol (VRRP) can separate physical device and logical deviceto select routes among different gateways.

On a LAN enabled with multicast or broadcast, for example, Ethernet, VRRP offers logicalgateways to ensure highly available link. This solves the problem that services are interruptedbecause of a gateway router failure, without changing the configuration of routing protocol.

1.3.4 BFD (Bidirectional Forwarding Detection)BFD is a set of entire-network applicable detection mechanisms. It is used to detect and monitorthe connectivity of a link or an IP route during forwarding packets. To improve the networkperformance, a communication failure between adjacent systems must be detected quickly andthe 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 shorttime

l Detecting any media and any protocol layer with single mechanism in real time andsupporting different detection time and costs

1.4 Networking of Reliability over an IP NetworkThis section describes the typical networking schemes of IP network reliability.

1.4.1 Failures on Intermediate Nodes or on the Link Between PEs - LDP FRR/TE FRR

1.4.2 Link Failure During Transimission

1.4.3 Failure on the Remote PE - VPN FRR

1.4.4 Failure of Downlink Interface on the PE - IP FRR

1.4.1 Failures on Intermediate Nodes or on the Link Between PEs -LDP FRR/TE FRR

Figure 1-2 Networking diagram of LDP/TE FRR application

PE1 P1 P2 P3 PE3

PE2 PE4




Issue 03 (2010-03-31)

As shown in Figure 1-2, LDP LSP serves as a public network tunnel and TE is enabled withQoS between P devices. This network deployment enhances the QoS across the entire networkand simplifies the TE deployment in changing PE devices. Without transmission devices, if afailure occurs on the link between P1 and P2, or P2 fails on a non-broadcast network, the LDPFRR 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 switchingperformed by the TE FRR/LDP FRR depends on the detection of the interface status throughsignals or optical signals. If transmission devices exist and a link fails, the router cannot detectthe interrupt of optical signals, and the switching cannot be performed. Then, another mechanismis required to detect the link between transmission devices, namely, BFD or OAM.

1.4.2 Link Failure During Transimission

OAMThe OAM is a unidirectional detection mechanism. Bidirectional OAM can be configured forbidirectional protection. The detection end of OAM sends a packet to detect the link. If the linkworks normally, the other end can receive the detection packet timely.

If the receiver cannot receive the detection packet within a specified period, a link-interruptpacket is sent through a reverse path to report the link failure to the detection end. Then, thedetection end responds to the failure with a series of actions, one of which is the switchover ofthe OAM protection group.

In an OAM protection group, a primary tunnel and a bypass tunnel are created to form aprotection group. When one tunnel of the protection group is available, the primary tunnel isavailable logically. Normally, a packet is forwarded through the primary tunnel, that is, theworking tunnel. When the primary tunnel is Down and the bypass tunnel is available, the tunnelis 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 tablewith its primary tunnel entry and bypass tunnel entry. This enables fast switchover after a failureis detected, providing high reliability for network connectivity.



1-9

Figure 1-3 Networking diagram of MPLS OAM protecting switchover

PE2

P3

PE1 P2

P1

MPLS TETunnel

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 reversechannel, advertising a failure to ingress PE1.

VRRP, BFDBFD 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 fastdetection packets through a preset path to detect the link status. If the detection packets cannotpass through the link, the packets are dropped. To avoid the jitters, the number of detectionpackets is specified. When the number of the lost detection packets reaches the set value, thelink 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 thatthe link is interrupted and reports to related modules to perform switchover.




Issue 03 (2010-03-31)

Figure 1-4 Networking diagram of BFD for VRRP

BackboneVRRPBFD forVRRP

PE1

PE2

Switch1

Switch2

As shown in Figure 1-4, PE1 and PE2 form a VRRP master and backup group, serving as thebackup for each other. The VRRP backup group monitors BFD session. For example, when PE1serves as the primary PE and the link between Switch1 and PE1 fails, the failure is fast detectedthrough BFD and reported to VRRP. The VRRP master and backup group performs switchoverfast and then PE2 becomes the primary PE.

1.4.3 Failure on the Remote PE - VPN FRR

Figure 1-5 Networking diagram of VPN FRR application

PE1 P1 P2 P3

PE2

PE3

PE4

As shown in Figure 1-5, PE3 and PE4 access the VPN. If the user network on the left of PE1needs to communicate with the user network on the right of PE3, PE1 can access the user networkon 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 forfast switchover before the primary path fails. For VPN FRR, two next hops (PEs) are reservedfor the local device to access the private network. One is the active PE and the other is the standbyPE. The active and standby PEs are configured manually.



1-11

As shown in Figure 1-5, PE1 reserves two next hops, that is, PE3 and PE4, to access the remoteVPN. 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 planeto the forwarding plane. When the active next hop becomes invalid, the standby next hopentry 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 controlplane to the forwarding plane. When the active next hop becomes invalid, the standby nexthop 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 veryshort period, which ensures high reliability.

1.4.4 Failure of Downlink Interface on the PE - IP FRR

Figure 1-6 Networking diagram of IP FRR application

PE1

PE2

CE

MPLS-VPN

Backbone

As shown in 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 PE1and 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 aretransmitted through direct route. For the other path, packets are transmitted from PE1 to PE2and then forwarded to CE.

Generally, PE accesses the Layer 3 Virtual Private Network (L3VPN). IP FRR is applied to aprivate network. Then, the private network neighbor relationship between PE1 and PE2 needsto be created, and the primary and bypass paths are created for PE1 accessing CE.




Issue 03 (2010-03-31)

2 Interface Backup Configuration

About This Chapter

This chapter describes the concepts, working mechanism, and configuration procedures of theIP address and provides configuration examples.

2.1 Introduction of Interface BackupThis section describes the principles, and concepts of the interface backup.

2.2 Configuring the Active/Standby Interface Backup

2.3 Configuring the Load Balancing Interface BackupThis section describes how to configure the load balancing interface backup.

2.4 Maintaining the Interface Backup

2.5 Configuration ExamplesThis section provides several configuration examples of interface backup.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability 2 Interface Backup Configuration


2-1

2.1 Introduction of Interface BackupThis section describes the principles, and concepts of the interface backup.

2.1.1 Interface Backup Overview

2.1.2 Characteristics of the Interface Backup Supported by the NE80E/40E

2.1.1 Interface Backup OverviewThe router plays an important role in the network. When an interface on a router fails, a keymethod to ensure the security and smooth functioning of the service is to rapidly switch theservice 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

if1if2

if3

if4LAN

Interfaces if1, if2, and if3 are backed up for each other. For example, if2 transmits services. if1and 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 standbyinterface with a higher priority to replace if2. This ensures smooth and reliable transmission ofservices.

The interface backup mechanism divides interfaces into the active interface and the standbyinterface according to their roles in the service transmission process.

Active InterfaceThe active interface undertakes service transmission and is backed up by other interfaces, suchas if2 in Figure 2-1.

Any physical interface or sub-interface like POS ,Ethernet or ATM interface serves as an activeinterface on a router. An active interface with larger bandwidth provides a higher transmissionrate.

Standby InterfaceThe standby interface does not transmit services and is often in the standby mode. The standbyinterface backs up the active interface, such as if1 and if3 in Figure 2-1.

2 Interface Backup ConfigurationHUAWEI NetEngine80E/40E Router



Issue 03 (2010-03-31)

Any physical interface (POS , AUX Ethernet or ATM interface for example) on a router servesas a standby interface.

NOTE

l An active interface is backed up by several standby interfaces. When the active interface fails, thestandby 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 activeinterfaces through the Dialer route in the Dial Control Center (DCC) configuration.

2.1.2 Characteristics of the Interface Backup Supported by theNE80E/40E

Active/Standby Mode

Figure 2-2 shows that if2 serves as the active interface.

Figure 2-2 Active/standby mode

if2

if1

if3

if4100%LAN

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 interfaceis overloaded.

l The standby interface with the highest priority takes over the work of the active interfaceand 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 routerautomatically enables an available standby interface with the highest priority. Bothinterfaces undertake the transmission together and share the load.

l When the flows of these two interfaces reach the highest threshold again, the router enablesanother available interface with the second highest priority for balancing the load amongthese interfaces, and so on.

l When the data flow of the active interface reaches the pre-defined lower limit, the routerdisables the standby interface with the lowest priority that is taking part in load balancinguntil the active interface can undertake the flow on its own.



2-3

Figure 2-3 Load-balancing mode

if2B%

A%

C%

A%+B%+C%=100%

LANif1

if3

if4

NOTE

The working mode is selected depending on configuration of the percentage threshold of load balancingby 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

2.2.1 Establishing the Configuration Task

2.2.2 Configuring a Standby Interface

2.2.3 Configuring the Active/Standby Switchover Delay

2.2.4 Checking the Configuration


Applicable Environment

The interface backup can be configured for multiple devices to improve their reliability throughstandby interfaces.

In the active/standby mode, the active interface undertakes all the services, whereas the standbyinterfaces are in the standby state and do not undertake services.

Switchover delay is an important parameter in the active/standby mode. An appropriate delaynot 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/standbyinterface

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.




Issue 03 (2010-03-31)

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


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 interfacecommand 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 standbyinterface 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

Context

To avoid frequent interface switching due to unstable interface status, the system does not switchtraffic from the active interface to the standby interface until a pre-set delay after the activeinterface changes from Up to Down.



2-5

l If the active interface is still in the Down state when the delay period expires, the systemswitches 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




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


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 standbyinterface.

----End

Example

Running the display standby state command, you can view information about the status of theactive and standby interfaces as follows:

<HUAWEI> display standby stateInterface Interfacestate Backupstate Backupflag Pri LoadstateGigabitEthernet3/0/0 UP MUP MUGigabitEthernet3/0/4 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.




Issue 03 (2010-03-31)

2.3 Configuring the Load Balancing Interface BackupThis section describes how to configure the load balancing interface backup.



2.3.3 Configuring the Percentage Thresholds for Load Balancing

2.3.4 (Optional) Configuring the Bandwidth and Flow Check Interval for the Active Interface




The interface backup can be configured for multiple devices to improve their reliability throughstandby interfaces.

In the load-balancing mode, if the flows on the active interface exceed the threshold, therouter 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 bandwidthof the active interface is preferentially used.


Before configuring the load balancing interface backup, you need to complete the followingtasks:



l Configuring IP addresses for interfaces

l Configuring static routes to the destination network segment on the active interface andstandby interfaces

NOTE

The preceding parameters are required on both the active interface and the standby interfaces. To efficientlyuse 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.



2-7

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


ContextDo as follows on the router that needs to be configured with the load balancing interface backup:

Procedure





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 foran active interface.

l An active interface can be backed up by a maximum of three standby interfaces. One standby interfacecan 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

ContextDo as follows on the router that needs to be configured with the load balancing interface backup:

Procedure





Issue 03 (2010-03-31)




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 percentageis 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. Thisstandby 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 servicesin load balancing mode.

----End

2.3.4 (Optional) Configuring the Bandwidth and Flow CheckInterval for the Active Interface

Context

Do as follows on the router that needs to be configured the load balancing interface backup:

Procedure





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 maximumavailable bandwidth.

Step 4 Run:standby timer flow-check time

The flow check interval for the active interface is configured.



2-9

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

----End


PrerequisiteThe configurations of the Load Balancing Interface Backup function are complete.

Procedurel 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

ExampleAfter the configuration, you can run the display standby flow command and the displaystandby state command.

<HUAWEI> display standby stateInterface Interfacestate Backupstate Backupflag Pri LoadstatePos 2/0/0 UP MUP MUDPos 1/0/0 UP UP BU 40Pos 3/0/0 STANDBY STANDBY BU 20Backup-flag meaning: M---MAIN B---BACKUP V---MOVED U---USED D---LOAD P---PULLED G---LOGICCHANNEL<HUAWEI> display standby flowInterfacename : Pos2/0/0Flow-interval(s) : 30LastInOctets : 5298LastOutOctets : 398807420InFlow(Octets) : 1038OutFlow(Octets) : 78717892BandWidth(b/s) : 40000000UsedBandWidth(b/s) : 20991432

As shown, POS 2/0/0 is configured as an active interface and POS 1/0/0 and POS 3/0/0 as standbyinterfaces. The bandwidth of the active interface is 40000000 bit/s. When the traffic exceeds theload-balancing limit, the percentages of upper and lower thresholds for load balancing are 50%and 30% respectively. As shown in the command output, the bandwidth in use on the activeinterface is 20991432 bit/s exceeding 40 Mbit/s by 50%. Then, the standby interface POS 1/0/0with a higher priority starts to undertake the traffic.

2.4 Maintaining the Interface Backup

2.4.1 Monitoring Working Status of the Interface Backup




Issue 03 (2010-03-31)

2.4.1 Monitoring Working Status of the Interface Backup

ContextIn routine maintenance, you can select to run the following commands in any view to view theworking status of the interface backup.

Procedurel 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

2.5 Configuration ExamplesThis section provides several configuration examples of interface backup.

2.5.1 Example for Configuring the Active/Standby Mode of Multiple Interfaces2.5.2 Example for Configuring Load Balancing on Multiple Standby Interfaces

2.5.1 Example for Configuring the Active/Standby Mode ofMultiple Interfaces

Networking RequirementsAs 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/010.1.1.1/24

HostA10.10.1.1/24

HostB10.20.1.1/24

GE4/0/010.10.1.2/24

RouterA RouterBPOS2/0/010.1.2.1/24

POS3/0/010.1.3.1/24

POS1/0/010.1.1.2/24

POS2/0/010.1.2.2/24

POS3/0/010.1.3.2/24

GE4/0/010.20.1.2/24



2-11

Configuration RoadmapThe 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 PreparationTo 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[RouterA] ip route-static 10.20.1.0 255.255.255.0 pos2/0/0[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.

<RouterB> system-view[RouterB] ip route-static 10.10.1.0 255.255.255.0 pos1/0/0[RouterB] ip route-static 10.10.1.0 255.255.255.0 pos2/0/0[RouterB] ip route-static 10.10.1.0 255.255.255.0 pos3/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 standbyinterfaces. 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] standby interface pos3/0/0 20[RouterB-Pos2/0/0] quit

After the configuration, display the state of the active/standby interfaces, and you can find thatPOS2/0/0 is UP, and POS 1/0/0 and POS 3/0/0 are STANDBY.

[RouterB] display standby stateInterface Interfacestate Backupstate Backupflag Pri LoadstatePos 2/0/0 UP MUP MUPos 1/0/0 STANDBY STANDBY BU 40Pos 3/0/0 STANDBY STANDBY BU 20 Backup-flag meaning: M---MAIN B---BACKUP V---MOVED U---USED D---LOAD P---PULLED G---LOGICCHANNEL




Issue 03 (2010-03-31)

After the Tracert test of Host B address on Host A, you can view the packets reaches thedestination through the link layer of POS 2/0/0 on Router B.

C:\> tracert 10.20.1.1Tracing route to 10.20.1.1 over a maximum of 30 hops 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.1Trace complete.

Step 3 Verify the configuration.

# Run the shutdown command on POS 2/0/0 on Router B to simulate a fault.

[RouterB] interface pos 2/0/0[RouterB-Pos2/0/0] shutdown[RouterB-Pos2/0/0] quit

# Display the state of the active and standby interfaces again, and you can find that POS 1/0/0becomes UP and POS 3/0/0 is still STANDBY.

[RouterB] display standby stateInterface Interfacestate Backupstate Backupflag Pri LoadstatePos 2/0/0 DOWN MDOWN MUPos 1/0/0 UP UP BU 40Pos 3/0/0 STANDBY STANDBY BU 20 Backup-flag meaning: M---MAIN B---BACKUP V---MOVED U---USED D---LOAD P---PULLED G---LOGICCHANNEL

After the Tracert test of Host B address on Host A, you can display the packets reaching thedestination through POS 1/0/0 of the link layer on Router B.

C:\> tracert 10.20.1.1Tracing route to 10.20.1.1 over a maximum of 30 hops 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.1Trace complete.

----End

Configuration Filesl 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#



2-13

ip route-static 10.20.1.0 255.255.255.0 Pos1/0/0 ip route-static 10.20.1.0 255.255.255.0 Pos2/0/0 ip route-static 10.20.1.0 255.255.255.0 Pos3/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 standby interface Pos3/0/0 20#interface Pos3/0/0 link-protocol ppp undo shutdown ip address 10.1.3.2 255.255.255.0#interface GigabitEthernet4/0/0 undo shutdown ip address 10.20.1.2 255.255.255.0# ip route-static 10.10.1.0 255.255.255.0 Pos1/0/0 ip route-static 10.10.1.0 255.255.255.0 Pos2/0/0 ip route-static 10.10.1.0 255.255.255.0 Pos3/0/0#return

2.5.2 Example for Configuring Load Balancing on Multiple StandbyInterfaces

Networking Requirements

As shown in Figure 2-4, Router A is connected to Router B.

The load balancing backup relationship exists among multiple interfaces on Router B. POS 2/0/0serves as the active interface, and POS 1/0/0 and POS 3/0/0 serve as the load balancing interfacesof 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 isenabled for load balancing. Standby interfaces with low priority are disabled when the traffic ofthe active interface is less than 30% of the threshold.

Configuration Roadmap

The configuration roadmap is as follows:

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 standbyinterfaces. POS 1/0/0 has a higher priority.




Issue 03 (2010-03-31)

3. Configure the threshold of the load balancing percentage and the active interfacebandwidth.

Data PreparationTo 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-4.

The configuration details are not mentioned 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[RouterA] ip route-static 10.20.1.0 255.255.255.0 pos2/0/0[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.

<RouterB> system-view[RouterB] ip route-static 10.10.1.0 255.255.255.0 pos1/0/0[RouterB] ip route-static 10.10.1.0 255.255.255.0 pos2/0/0[RouterB] ip route-static 10.10.1.0 255.255.255.0 pos3/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 standbyinterfaces with the priorities of 40 and 20 respectively.

[RouterB] interface pos 2/0/0[RouterB-Pos2/0/0] standby interface pos1/0/0 40[RouterB-Pos2/0/0] standby interface pos3/0/0 20

# 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 aboutthe status of active and standby interfaces. As shown in the command output, POS 2/0/0 is inthe Up state. POS 1/0/0 and POS 3/0/0 are in the Standby state. Also, you can run the displaystandby flow command to view traffic changes on POS 2/0/0.

<RouterB> display standby stateInterface Interfacestate Backupstate Backupflag Pri LoadstatePos 2/0/0 UP MUP MUPos 1/0/0 STANDBY STANDBY BU 40



2-15

Pos 3/0/0 STANDBY STANDBY BU 20Backup-flag meaning: M---MAIN B---BACKUP V---MOVED U---USED D---LOAD P---PULLED G---LOGICCHANNEL<RouterB> display standby flowInterfacename : Pos2/0/0Flow-interval(s) : 30LastInOctets : 2494LastOutOctets : 86086500InFlow(Octets) : 258OutFlow(Octets) : 258BandWidth(b/s) : 40000000UsedBandWidth(b/s) : 64

# 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 againand you can find that both POS 2/0/0 and POS 1/0/0 are Up.

<RouterB> display standby stateInterface Interfacestate Backupstate Backupflag Pri LoadstatePos 2/0/0 UP MUP MUDPos 1/0/0 UP UP BU 40Pos 3/0/0 STANDBY STANDBY BU 20Backup-flag meaning: M---MAIN B---BACKUP V---MOVED U---USED D---LOAD P---PULLED G---LOGICCHANNEL<RouterB> display standby flowInterfacename : Pos2/0/0Flow-interval(s) : 30LastInOctets : 5298LastOutOctets : 398807420InFlow(Octets) : 1038OutFlow(Octets) : 78717892BandWidth(b/s) : 40000000UsedBandWidth(b/s) : 20991432

----End


# 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 ip route-static 10.20.1.0 255.255.255.0 Pos2/0/0 ip route-static 10.20.1.0 255.255.255.0 Pos3/0/0#




Issue 03 (2010-03-31)

returnl 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 standby interface Pos3/0/0 20 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#interface GigabitEthernet4/0/0 undo shutdown ip address 10.20.1.2 255.255.255.0# ip route-static 10.10.1.0 255.255.255.0 Pos1/0/0 ip route-static 10.10.1.0 255.255.255.0 Pos2/0/0 ip route-static 10.10.1.0 255.255.255.0 Pos3/0/0#return



2-17

3 APS Configuration

About This Chapter

This chapter describes the basic principle, configuration procedures, and configuration examplesfor Automatic Protection Switching (APS).

3.1 APS OverviewThis section describes the principle and concepts of APS.

3.2 Configuring Single-Chassis APSThis section describes how to configure single-chassis APS.

3.3 Configuring E-APSThis section describes how to configure Efficiency APS (E-APS).

3.4 Configuration ExamplesThis section provides several configuration examples of APS.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability 3 APS Configuration


3-1

3.1 APS OverviewThis section describes the principle and concepts of APS.

3.1.1 Introduction to APS

3.1.2 APS Features Supported by the NE80E/40E

3.1.1 Introduction to APS

To protect STM-N links in the SDH hierarchy, the ITU-T defines APS for linear multiplexsections. APS implements the traffic switching and recovery in linear multiplex sectionprotection mode. When a transmission link is faulty, traffic is quickly switched to a normal linkto ensure a normal transmission.

APS is implemented through the transmission of K1 and K2 bytes in the Multiplex SectionOverhead (MSOH). K1 transmits Changeover Order (COO) signals; K2 transmits ChangeoverAcknowledgement (COA) signals.

APS has two protection modes, namely, 1+1 and 1:N. When the N is 1, the protection mode is1:1.

l In 1+1 mode, a protection interface is paired with each working interface. Normally, thereceiver only processes the traffic being received on the working link. When the workinglink is faulty, traffic is switched to the protect link on the receiver, which is calledunidirectional switchover.

l In 1:1 mode, the working link transmits high-level traffic and the protect link transmitsnothing to the receiver. When the working link is faulty, the sender switches the high-leveltraffic to the protect link and the receiver obtains the high-level traffic from the protect link.This is called bidirectional switchover.

3.1.2 APS Features Supported by the NE80E/40E

At present, the NE80E/40E supports the following APS features:

l 1+1 unidirectional mode and 1:1 bidirectional mode.

l Manual switching of APS groups.

l Forcible switching of APS groups.

l Locking of APS groups.

l APS implemented on interfaces.

l APS implemented 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 and configuringservices on the trunk.

3.2 Configuring Single-Chassis APSThis section describes how to configure single-chassis APS.

3 APS ConfigurationHUAWEI NetEngine80E/40E Router



Issue 03 (2010-03-31)


3.2.2 Configuring the Working Interface of an APS Group

3.2.3 Configuring the Protection Interface of an APS Group

3.2.4 (Optional) Configuring the Working Mode for an APS Group

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

3.2.6 Adding Members of an APS Group to a Trunk



Applicable EnvironmentAPS can be configured when the router is connected to the Radio Network Controller (RNC).

Pre-configuration TaskBefore configuring APS, complete the following tasks:

l Configure an interface on the router and ensure that the link layer protocol between therouter and the RNC is Up.

Data PreparationTo 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


ContextDo as follows on the router that requires APS:

Procedure





3-3


or

controller cpos cpos-number


NOTEOnly ATM interfaces and CPOS interfaces on LPUF-10 support APS .

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 [ peer-ip]

The interface added to the APS group is specified as the working interface.

NOTEIn the case of single-chassis APS, you needn't configure peer-ip when specifying the protection interfacefor an APS group.

----End


Context

Do as follows on the router that requires APS.

Procedure




or









Issue 03 (2010-03-31)

CAUTIONThe working and protection group must be added to the same APS group.

Step 4 Run:aps protect [ peer-ip]

The interface added to the APS group is specified as the protection interface.

NOTEIn the case of single-chassis APS, you needn't configure peer-ip when specifying the protection interfacefor an APS group.

----End

3.2.4 (Optional) Configuring the Working Mode for an APS Group

ContextDo as follows on the protection interface of an APS group.

Procedure




or



Step 3 Run:aps mode { one2one bidirection | one-plus-one unidirection }

The working mode of an APS group is configured.

----End


ContextDo as follows on the protection interface of an APS group.

Procedure




3-5



or


The protection interface view of the APS group is entered.

Step 3 Run:aps revert wtr-time

The WTR time is set for the APS group.

When setting the WTR time, note the following items:

l In the case of APS 1:1 mode, after the fault is rectified and the WTR time (one minute)expires, traffic is switched back to the working link by default.

l In the case of the APS 1+1 mode, after the fault is rectified, traffic is not switched back tothe working interface by default.

----End


ContextDo as follows separately on the working and s of an APS group.

Procedure



Step 2 Run:interface atm-trunk interface-number

An ATM-Trunk interface is created and the view of the ATM-Trunk interface is displayed.

NOTEAPS can be configured on the ATM interfaces and CPOS interfaces. There are corresponding trunkinterfaces which are ATM-Trunk and CPOS-Trunk. Take the configuration on the ATM-Trunk as anexample.

Step 3 Run:quit







Issue 03 (2010-03-31)

Step 5 Run:atm-trunk trunk-id

The interface is added to a trunk.

CAUTIONThe working and protection interfaces of an APS group must be added to the trunk with the sametrunk ID.

----End


Procedure

Step 1 Run the display aps group group-id command to view the configuration information about anAPS group.

Step 2 Run the commands below ,you can view the configuration information about Trunk interfaces.l Run the display atm-trunk trunk-idcommand to view the configuration information about

ATM-Trunk interfaces.l Run the display cpos-trunk trunk-idcommand to view the configuration information about

CPOS-Trunk interfaces.

----End

Example<HUAWEI> display aps group 1APS 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 1Interface Atm-Trunk1's state information is:Operate status: up Number Of Up Port In Trunk: 2--------------------------------------------------------------------------------PortName Status Active StatusAtm1/0/1 Up ActiveAtm1/0/2 Up Inactive

3.3 Configuring E-APSThis section describes how to configure Efficiency APS (E-APS).




3-7



3.3.4 Configuring the Working Mode for an APS Group

3.3.5 (Optional) Setting the Interval for Sending APS Negotiation Messages and the Hold Timeof an APS Connection

3.3.6 (Optional) Configuring the Authentication String for the PGP Message






When the router is connected to an RNC and the RNC is dual homed to the router, E-APS canbe configured.

Pre-configuration Task

Before configuring E-APS, complete the following tasks:

l Configure an interface on the router and ensure that the link layer protocol between therouter and the RNC is Up.

Data Preparation

To configure E-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

4 (Optional) Authentication string configured for the PGP message

5 (Optional) Interval for sending APS negotiation messages between the workinginterface and the protection interface

6 (Optional) Hold time of an APS connection





Issue 03 (2010-03-31)

ContextDo as follows on the router that requires APS:

Procedure




or






Step 4 Run:aps working [ peer-ip]

The interface added to the APS group is specified as the working interface.

NOTEIn the case of E-APS, you must configure peer-ip when specifying the working interface for an APS group.

----End


ContextDo as follows on the router that requires APS.

Procedure




or





3-9

NOTEOnly ATM interfaces,POS and CPOS interfaces on LPUF-10 support APS .



CAUTIONThe working and protection group must be added to the same APS group.

Step 4 Run:aps protect [ peer-ip]

The interface added to the APS group is specified as the protection interface.

NOTEIn the case of E-APS, you must configure peer-ip when specifying the protection interface for an APSgroup.

----End

3.3.4 Configuring the Working Mode for an APS Group

Context

Do as follows on the protection interface of an APS group.

Procedure




or


The protection interface view of the APS group is displayed.

Step 3 Run:aps mode { one2one bidirection | one-plus-one unidirection }

The working mode of an APS group is configured.

NOTETo associate E-APS with PW redundancy, you must ensure that APS is working in 1:1 bidirection mode.

----End




Issue 03 (2010-03-31)

3.3.5 (Optional) Setting the Interval for Sending APS NegotiationMessages and the Hold Time of an APS Connection

ContextDo as follows separately on the working and protection interfaces of an APS group.

Procedure




or


The working interface view 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 connectionbetween the working and protection interfaces are set.

----End

3.3.6 (Optional) Configuring the Authentication String for the PGPMessage


Procedure




or


The working interface view or the protection interface view is displayed.

Step 3 Run:



3-11

aps authenticate string

The authentication string is configured for the PGP message.

CAUTIONBefore configuring the authentication string for the PGP message on an interface, you mustspecify the interface as the working interface or the protection interface.A normal PGP negotiation can be established only when the authentication strings configuredon the protect and working interfaces are identical.

----End


Context

Do as follows on the protection interface of an APS group.

Procedure




or


The protection interface view of the APS group is entered.

Step 3 Run:aps revert wtr-time

The WTR time is set for the APS group.

When setting the WTR time, note the following items:

l In the case of APS 1:1 mode, after the fault is rectified and the WTR time (one minute)expires, traffic is switched back to the working link by default.

l In the case of the APS 1+1 mode, after the fault is rectified, traffic is not switched back tothe working interface by default.

----End





Issue 03 (2010-03-31)


ProcedureStep 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.

NOTEAPS can be configured on the ATM interfaces and CPOS interfaces. There are three corresponding trunkinterfaces which are ATM-Trunk and CPOS-Trunk. Take the configuration on the ATM-Trunk as anexample.

Step 3 Run:quit




Step 5 Run:atm-trunk trunk-id

The interface is added to a trunk.

----End


ProcedureStep 1 Run the display aps group group-id command, and you can view the configuration information

about an APS group.

Step 2 Run the commands below ,you can view the configuration information about Trunk interfaces.l Run the display atm-trunk trunk-idcommand to view the configuration information about

ATM-Trunk interfaces.l Run the display cpos-trunk trunk-idcommand to view the configuration information about

CPOS-Trunk interfaces.

----End

ExampleAfter E-APS is configured, run the display aps group group-id command on the router wherethe protection interface is located to view the configuration information about the APS group.



3-13

<HUAWEI> display aps group 1APS Group 1: APS working channel is 72.72.72.72 Atm1/0/1 protection channel 0(Inactive) PGP authentication string: 111 Bidirection, 1:1 mode, Revert time(1 minutes) KeepAlive Timer: 1(seconds), Hold Timer: 3(seconds) No Request on Both Working and Protection Side--------------------------------------------------------------------------------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 1Interface Atm-Trunk1's state information is:Operate status: up Number Of Up Port In Trunk: 1--------------------------------------------------------------------------------PortName Status Active StatusAtm1/0/1 Up Active

3.4 Configuration ExamplesThis section provides several configuration examples of APS.

3.4.1 Example for Associating PW Redundancy with APS

3.4.2 Example for Configuring TDM on the CPOS interfaces Configured with APS

3.4.1 Example for Associating PW Redundancy with APS

Networking RequirementsAs shown in Figure 3-1, PE1 is dual-homed to PE2 and PE3 through two PWs. When a faultoccurs on the network side, the switchover of LSP groups rather than PWs is performed. Whena fault occurs on the AC side, the switchover between the working interface and the protectioninterface is performed on the AC side according to APS. This leads to the switchover of PWsand thus avoids the loss of the network data.

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

GE2/0/1 G

E2/0/1

ATM1/0/2 ATM2/0/2

GE3/0/2 GE3/0/2

GE3/0/2 GE3/0/2

GE2/0/2 GE2/0/2

Loopback02.2.2.2

ATM 1/0/0

ATM 1/0/0

GE1/0/2

GE1/0/2

CE1

PE1

PE5

CE2

E-APS

Loopback03.3.3.3

Loopback01..1.1.1 ATM1/0/1 ATM2/0/1

PE2

PE3

PE4

Loopback04.4.4.4

Loopback05.5.5.5

GE1/0/2

GE1/0/2




Issue 03 (2010-03-31)

Table 3-1 Interfaces and IP address

Devices Interface No. IP Address of the Interfaces

PE1 GE2/0/1 101.1.1.1/24

GE2/0/2 102.1.1.1/24

Loopback0 1.1.1.1/32

P1 GE2/0/1 101.1.1.2/24

GE3/0/2 104.1.1.1/24


P2 GE2/0/2 102.1.1.2/24

GE3/0/2 105.1.1.1/24


PE2 GE3/0/2 104.1.1.2/24

GE1/0/2 106.1.1.1/24


PE3 GE3/0/2 105.1.1.2/24

GE1/0/2 106.1.1.2/24




1. Configure the IP address and routing protocol to make PEs routable.

2. Configure basic MPLS functions and set up the local LDP session between each PE andremote LDP session on PE1,PE2 and PE3.

3. Configure E-APS between PE2 and PE3 and single APS on CE2.

4. Configure the primary and backup PWs on PE1 to be dual homed to PE2 and PE3, andconfigure a PW on both PE2 and PE3.

Data Preparation

To complete the configuration, you need the following data:

l IP address of each interface

l MPLS LSR ID of each PE



3-15

l Parameters necessary for configuring E-APS, such as the WTR time and authenticationstring for the PGP message

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 Table 3-1. The configurationdetails are not mentioned here.

2. Configure IGP. In this example, OSPF is adopted.

# Configure PE1.

[PE1] ospf[PE1-ospf-1] area 0[PE1-ospf-1-area-0.0.0.0] network 101.1.1.1 0.0.0.255[PE1-ospf-1-area-0.0.0.0] network 102.1.1.1 0.0.0.255[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 P1.

[P1] ospf[P1-ospf-1] area 0[P1-ospf-1-area-0.0.0.0] network 101.1.1.2 0.0.0.255[P1-ospf-1-area-0.0.0.0] network 104.1.1.1 0.0.0.255[P1-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0[P1-ospf-1-area-0.0.0.0] quit[P1-ospf-1] quit

# Configure P2.

[P2] ospf[P2-ospf-1] area 0[P2-ospf-1-area-0.0.0.0] network 102.1.1.2 0.0.0.255[P2-ospf-1-area-0.0.0.0] network 105.1.1.2 0.0.0.255[P2-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0[P2-ospf-1-area-0.0.0.0] quit[P2-ospf-1] quit

# Configure PE2


# Configure PE3


# Check whether OSPF is successfully configured. Take the command output on PE1 asan example. The value of the state field is Full, indicating that the OSPF neighborrelationship is already set up.




Issue 03 (2010-03-31)

[PE1] display ospf peerOSPF Process 1 with Router ID 128.128.18.38 Neighbors

Area 0.0.0.0 interface 101.1.1.1(GigabitEthernet2/0/1)'s neighbors Router ID: 128.128.16.31 Address: 101.1.1.2 State: Full Mode:Nbr is Slave Priority: 1 DR: 101.1.1.2 BDR: 101.1.1.1 MTU: 0 Dead timer due in 39 sec Retrans timer interval: 0 Neighbor is up for 00:04:30 Authentication Sequence: [ 0 ]

Neighbors

Area 0.0.0.0 interface 102.1.1.1(GigabitEthernet2/0/2)'s neighbors Router ID: 128.128.16.31 Address: 102.1.1.2 State: Full Mode:Nbr is Slave Priority: 1 DR: 102.1.1.2 BDR: 102.1.1.1 MTU: 0 Dead timer due in 40 sec Retrans timer interval: 5 Neighbor is up for 02:40:02 Authentication Sequence: [ 0 ]

Step 2 Configure MPLS functions.1. Configure basic MPLS functions and MPLS LDP.

# Configure PE1.

[PE1] interface loopBack 0[PE1-LoopBack0] ip address 1.1.1.1 32[PE1-LoopBack0] quit[PE1] mpls lsr-id 1.1.1.1[PE1] mpls[PE1-mpls] quit[PE1] mpls ldp[PE1-mpls-ldp] quit[PE1] interface gigabitethernet 2/0/1[PE1-GigabitEthernet2/0/1] mpls[PE1-GigabitEthernet2/0/1] mpls ldp[PE1-GigabitEthernet2/0/1] quit[PE1] interface gigabitethernet 2/0/2[PE1-GigabitEthernet2/0/2] mpls[PE1-GigabitEthernet2/0/2] mpls ldp[PE1-GigabitEthernet2/0/2] quit

# 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] quit[P1] mpls ldp[P1-mpls-ldp] quit[P1] interface gigabitethernet 2/0/1[P1-GigabitEthernet2/0/1] mpls[P1-GigabitEthernet2/0/1] mpls ldp[P1-GigabitEthernet2/0/1] quit[P1] interface gigabitethernet 3/0/2[P1-GigabitEthernet3/0/2] mpls[P1-GigabitEthernet3/0/2] mpls ldp[P1-GigabitEthernet3/0/2] quit

# Configure P2.

[P2] interface loopBack 0[P2-LoopBack0] ip address 3.3.3.3 32



3-17

[P2-LoopBack0] quit[P2] mpls lsr-id 3.3.3.3[P2] mpls[P2-mpls] quit[P2] mpls ldp[P2-mpls-ldp] quit[P2] interface gigabitethernet 2/0/2[P2-GigabitEthernet2/0/2] mpls[P2-GigabitEthernet2/0/2] mpls ldp[P2-GigabitEthernet2/0/2] quit[P2] interface gigabitethernet 3/0/2[P2-GigabitEthernet3/0/2] mpls[P2-GigabitEthernet3/0/2] mpls ldp[P2-GigabitEthernet3/0/2] quit

# Configure PE2

[PE2] interface loopBack 0[PE2-LoopBack0] ip address 4.4.4.4 32[PE2-LoopBack0] quit[PE2] mpls lsr-id 4.4.4.4[PE2] mpls[PE2-mpls] quit[PE2] mpls ldp[PE2-mpls-ldp] quit[PE2] interface gigabitethernet 3/0/2[PE2-GigabitEthernet3/0/2] mpls[PE2-GigabitEthernet3/0/2] mpls ldp[PE2-GigabitEthernet3/0/2] quit

# Configure PE3

[PE3] interface loopBack 0[PE3-LoopBack0] ip address 5.5.5.5 32[PE3-LoopBack0] quit[PE3] mpls lsr-id 5.5.5.5[PE3] mpls[PE3-mpls] quit[PE3] mpls ldp[PE3-mpls-ldp] quit[PE3] interface gigabitethernet 3/0/2[PE3-GigabitEthernet3/0/2] mpls[PE3-GigabitEthernet3/0/2] mpls ldp[PE3-GigabitEthernet3/0/2] quit

# Check whether the MPLS LDP sessions are successfully set up. Take the command outputon PE1 as an example. The value of the status field is Operational, indicating that the MPLSLDP session is successfully set up.

[PE1] display mpls ldp sessionLDP Session(s) in Public Network 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 ------------------------------------------------------------------------------ 2.2.2.2:0 Operational DU Passive 0000:00:28 113/113 3.3.3.3:0 Operational DU Passive 0000:00:00 1/1 ------------------------------------------------------------------------------ TOTAL: 2 session(s) Found.

2. Configure the remote LDP session between PE1 and PE2 , PE1 and PE3.

# Configure PE1

[PE1] mpls ldp remote-peer 4.4.4.4[PE1-mpls-ldp-remote-4.4.4.4] remote-ip 4.4.4.4




Issue 03 (2010-03-31)

[PE1-mpls-ldp-remote-4.4.4.4] quit[PE1] mpls ldp remote-peer 5.5.5.5[PE1-mpls-ldp-remote-5.5.5.5] remote-ip 5.5.5.5[PE1-mpls-ldp-remote-5.5.5.5] quit

#Configure PE2

[PE2] mpls ldp remote-peer 1.1.1.1[PE2-mpls-ldp-remote-1.1.1.1] remote-ip 1.1.1.1[PE2-mpls-ldp-remote-1.1.1.1] quit

#Configure PE3

[PE3] mpls ldp remote-peer 1.1.1.1[PE3-mpls-ldp-remote-1.1.1.1] remote-ip 1.1.1.1[PE3-mpls-ldp-remote-1.1.1.1] quit

# Check whether the remote MPLS LDP sessions are successfully set up. Take thecommand output on PE1 as an example. The value of the status field is Operational,indicating that the remote MPLS LDP session is successfully set up.

[PE1] display mpls ldp session LDP Session(s) in Public Network 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 ------------------------------------------------------------------------------ 4.4.4.4:0 Operational DU Passive 0000:00:01 8/8 5.5.5.5:0 Operational DU Passive 0000:00:03 6/6 ------------------------------------------------------------------------------ TOTAL: 1 session(s) Found.

Step 3 Configure E-APS1. 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[PE2-Atm1/0/1] quit

# Configure PE3.

[PE3] interface atm 1/0/2[PE3-Atm1/0/2] undo shutdown[PE3-Atm1/0/2] aps group 1[PE3-Atm1/0/2] aps protect 4.4.4.4[PE3-Atm1/0/2] aps mode one2one bidirection[PE3-Atm1/0/2] aps revert 1[PE3-Atm1/0/2] aps timers 1 3[PE3-Atm1/0/2] quit

# Configure CE2.

<HUAWEI> system-view[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] interface atm 2/0/2[CE2-Atm2/0/2] aps group 1[CE2-Atm2/0/2] aps protect



3-19

[CE2-Atm2/0/2] aps mode one2one bidirection[CE2-Atm2/0/2] aps revert 1[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] interface atm 1/0/1[PE2-Atm1/0/1] atm-trunk 1

# Configure PE3.

[PE3] interface atm-trunk 1[PE3-Atm-Trunk1] quit[PE3] interface atm 1/0/2[PE3-Atm1/0/2] atm-trunk 1

# Configure CE2.

[CE2] interface atm-trunk 1[CE2-Atm-Trunk1] quit[CE2] interface atm 2/0/1[CE2-Atm2/0/1] atm-trunk 1[CE2-Atm2/0/1] quit[CE2] interface atm 2/0/2[CE2-Atm2/0/2] atm-trunk 1

3. Verify the configuration.

# Run the display aps group 1 command on PE2 and PE3 to view E-APS configurations.

[PE2] display aps group 1APS Group 1: Atm1/1/1 working channel 1(Active) APS protection channel is 5.5.5.5--------------------------------------------------------------------------------Group Work-Channel Protect-Channel Wtr W-State P-State Switch-Cmd Switch-Result--------------------------------------------------------------------------------1 Atm1/0/1 5.5.5.5 NA ok ok NA idle--------------------------------------------------------------------------------[PE3] display aps group 1APS Group 1: APS working channel is 4.4.4.4 Atm1/0/2 protection channel 0(Inactive) Bidirection, 1:1 mode, Revert time(1 minutes) KeepAlive Timer: 1(seconds), Hold Timer: 3(seconds) No Request on Both Working and Protection Side--------------------------------------------------------------------------------Group Work-Channel Protect-Channel Wtr W-State P-State Switch-Cmd Switch-Result--------------------------------------------------------------------------------1 4.4.4.4 Atm1/0/2 1 ok ok NA idle--------------------------------------------------------------------------------[PE2] display atm-trunk 1Interface Atm-Trunk1's state information is:Operate status: up Number Of Up Port In Trunk: 1--------------------------------------------------------------------------------PortName Status Active StatusAtm1/0/1 Up Active[PE3] display atm-trunk 1Interface Atm-Trunk1's state information is:Operate status: up Number Of Up Port In Trunk: 1




Issue 03 (2010-03-31)

--------------------------------------------------------------------------------PortName Status Active StatusAtm1/0/2 Up Inactive

Step 4 Configure PWs.

# Configure PE1.

[PE1] mpls l2vpn[PE1-l2vpn] quit[PE1] interface atm 1/0/0[PE1-Atm1/0/0] undo shutdown[PE1-Atm1/0/0] quit[PE1] interface atm 1/0/0.1 p2p

CAUTIONThe type of the ATM subinterface which will be configured with PW Redundancy must be 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 1[PE1-Atm1/0/0.1] mpls l2vc 5.5.5.5 2 secondary[PE1-Atm1/0/0.1] mpls l2vpn reroute immediately-switch[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[PE1-atm-pvc-Atm-trunk1.1-1/100] quit[PE2-Atm-Trunk1.1] mpls l2vc 1.1.1.1 1[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[PE1-atm-pvc-Atm-trunk1.1-1/100] quit[PE3-Atm-Trunk1.1] mpls l2vc 1.1.1.1 2[PE3-Atmh-Trunk1.1] quit

# Check whether the PWs are successfully set up.

[PE1] display mpls l2vc interface atm 1/0/0.1*client interface : Atm1/0/0.1 is up session state : up AC state : up VC state : up VC ID : 1 VC type : ATM 1to1 VCC destination : 4.4.4.4 local group ID : 0 remote group ID : 0 local VC label : 146434 remote VC label : 146432 local AC OAM State : up local PSN State : up local forwarding state : forwarding local status code : 0x0 remote AC OAM state : up



3-21

remote PSN state : up remote forwarding state: forwarding remote statuscode : 0x0 BFD for PW : unavailable manual fault : not set active state : active forwarding entry : exist link state : up local ATM cells : 0 remote ATM cells : 28 local VCCV : cw alert lsp-ping bfd remote VCCV : cw alert lsp-ping bfd local control word : enable remote control word : enable tunnel policy name : -- traffic behavior name : -- PW template name : -- primary or secondary : primary VC tunnel/token info : 1 tunnels/tokens NO.0 TNL type : lsp , TNL ID : 0x2000812a create time : 0 days, 0 hours, 5 minutes, 29 seconds up time : 0 days, 0 hours, 1 minutes, 11 seconds last change time : 0 days, 0 hours, 1 minutes, 11 seconds VC last up time : 2009/11/09 12:05:41 VC total up time : 0 days, 0 hours, 1 minutes, 11 seconds CKey : 5 NKey : 1

*client interface : Atm1/0/0.1 is up session state : up AC state : up VC state : up VC ID : 2 VC type : ATM 1to1 VCC destination : 5.5.5.5 local group ID : 0 remote group ID : 0 local VC label : 146435 remote VC label : 146432 local AC OAM state : up local PSN state : up local forwarding state : forwarding local status code : 0x0 remote AC OAM state : up remote PSN state : up remote forwarding state: forwarding remote status code : 0x20 BFD for PW : unavailable manual fault : not set active state : inactive forwarding entry : exist link state : down local ATM cells : 0 remote ATM cells : 28 local VCCV : cw alert lsp-ping bfd remote VCCV : cw alert lsp-ping bfd local control word : enable remote control word : enable tunnel policy name : -- traffic behavior name : -- PW template name : -- primary or secondary : secondary VC tunnel/token info : 1 tunnels/tokens NO.0 TNL type : lsp , TNL ID : 0x20008126 create time : 0 days, 0 hours, 5 minutes, 23 seconds up time : 0 days, 0 hours, 0 minutes, 35 seconds last change time : 0 days, 0 hours, 0 minutes, 35 seconds VC last up time : 2009/11/09 12:06:25 VC total up time : 0 days, 0 hours, 0 minutes, 35 seconds CKey : 6 NKey : 3

reroute policy : immediately, resume 10 s reason of last reroute : -- time of last reroute : -- days, -- hours, -- minutes, -- seconds




Issue 03 (2010-03-31)

delay timer ID : -- residual time :-- resume timer ID : -- residual time :--

The command output shows that PE1 has the primary PW and backup PW, which are in theActive and Inactive states respectively.

Step 5 Verify the configuration.1. Simulate the fault at the dual-homing access side of CE2.

# Shut down ATM 1/0/1, a member interface of the ATM-Trunk on PE2.

[PE2] interface atm 1/0/1[PE2-Atm1/0/1] shutdown

Run the display aps group command on PE3, you can view the status of protectioninterface is active.

[PE3] display aps group 1APS Group 1: APS working channel is 4.4.4.4 Atm1/0/2 protection channel 0(Active) Bidirection, 1:1 mode, Revert time(1 minutes) KeepAlive Timer: 1(seconds), Hold Timer: 3(seconds) Remote detect Signal Fail High priority on working side--------------------------------------------------------------------------------Group Work-Channel Protect-Channel Wtr W-State P-State Switch-Cmd Switch-Result--------------------------------------------------------------------------------1 4.4.4.4 Atm1/0/2 1 sf ok NA switch--------------------------------------------------------------------------------total entry: 1[PE3] display atm-trunk 1Interface Atm-Trunk1's state information is:Operate status: up Number Of Up Port In Trunk: 1--------------------------------------------------------------------------------PortName Status Active StatusAtm1/0/2 Up Active

# Run the display mpls l2vpn forwarding-info command. You can view the followinginformation: PE1 does not have the forwarding information about the primary PW and thebackup PW on PE1 becomes Active; PE2 does not have forwarding information about thePW; the PW on PE3 is in the Active state and the Admin status becomes Up.

[PE1] display mpls l2vpn forwarding-info interface atm 2/0/0.1The Main PW Forward Information :VCLABEL TNLTYPE ENTRYTYPE PWSTATE BFDSTATE ADMIN CTLWORD CC CV TNLID------------------------------------------------------------------------------ 0 Record(s) Found. The Second PW Forward Information :VCLABEL TNLTYPE ENTRYTYPE PWSTATE BFDSTATE ADMIN CTLWORD CC CV TNLID------------------------------------------------------------------------------146432 LSP SEND ACTIVE UP UP TRUE 3 a 0x20008126 1 Record(s) Found. [PE2] display mpls l2vpn forwarding-info interface atm-trunk 1.1he Main PW Forward Information :VCLABEL TNLTYPE ENTRYTYPE PWSTATE BFDSTATE ADMIN CTLWORD CC CV TNLID------------------------------------------------------------------------------ 0 Record(s) Found. The Second PW Forward Information :VCLABEL TNLTYPE ENTRYTYPE PWSTATE BFDSTATE ADMIN CTLWORD CC CV TNLID------------------------------------------------------------------------------ 0 Record(s) Found.



3-23

[PE3] display mpls l2vpn forwarding-info interface atm-trunk 1.1The Main PW Forward Information :VCLABEL TNLTYPE ENTRYTYPE PWSTATE BFDSTATE ADMIN CTLWORD CC CV TNLID------------------------------------------------------------------------------146435 LSP SEND ACTIVE UP UP TRUE 3 a 0x4008001 1 Record(s) Found.

The Second PW Forward Information :VCLABEL TNLTYPE ENTRYTYPE PWSTATE BFDSTATE ADMIN CTLWORD CC CV TNLID------------------------------------------------------------------------------ 0 Record(s) Found.

# Rectify the fault.

[PE2] interface atm 1/0/1[PE2-Atm1/0/1] undo shutdown

Run the display aps group command on PE2, you can view that the working interfacebecomes active.

[PE2] display aps group 1APS Group 1: Atm1/0/1 working channel 1(Active) APS protection channel is 5.5.5.5--------------------------------------------------------------------------------Group Work-Channel Protect-Channel Wtr W-State P-State Switch-Cmd Switch-Result--------------------------------------------------------------------------------1 Atm1/0/1 5.5.5.5 NA ok ok NA idle--------------------------------------------------------------------------------[PE2] display atm-trunk 1Interface Atm-Trunk1's state information is:Operate status: up Number Of Up Port In Trunk: 1--------------------------------------------------------------------------------PortName Status Active StatusAtm1/0/1 Up Active

Run the following commands, you can view the following information: the primary PWon PE1 becomes Active and the backup PW becomes Inactive; the Admin of the PW onPE2 becomes Up; the Admin of the PW on PE3 becomes Down.

[PE1] display mpls l2vpn forwarding-info interface atm 1/0/0.1The Main PW Forward Information :VCLABEL TNLTYPE ENTRYTYPE PWSTATE BFDSTATE ADMIN CTLWORD CC CV TNLID------------------------------------------------------------------------------146432 LSP SEND ACTIVE UP UP TRUE 3 a 0x2000812a 1 Record(s) Found.

The Second PW Forward Information :VCLABEL TNLTYPE ENTRYTYPE PWSTATE BFDSTATE ADMIN CTLWORD CC CV TNLID------------------------------------------------------------------------------146432 LSP SEND INACTIVE UP DOWN TRUE 3 a 0x20008126 1 Record(s) Found. [PE2] display mpls l2vpn forwarding-info interface atm-trunk 1.1The Main PW Forward Information :VCLABEL TNLTYPE ENTRYTYPE PWSTATE BFDSTATE ADMIN CTLWORD CC CV TNLID------------------------------------------------------------------------------146434 LSP SEND ACTIVE UP UP TRUE 3 a 0x2000800




Issue 03 (2010-03-31)

1 1 Record(s) Found.

The Second PW Forward Information :VCLABEL TNLTYPE ENTRYTYPE PWSTATE BFDSTATE ADMIN CTLWORD CC CV TNLID------------------------------------------------------------------------------ 0 Record(s) Found.[PE3] display mpls l2vpn forwarding-info interface atm-trunk 1.1The Main PW Forward Information :VCLABEL TNLTYPE ENTRYTYPE PWSTATE BFDSTATE ADMIN CTLWORD CC CV TNLID------------------------------------------------------------------------------146435 LSP SEND ACTIVE UP DOWN TRUE 3 a 0x4008001 1 Record(s) Found.

The Second PW Forward Information :VCLABEL TNLTYPE ENTRYTYPE PWSTATE BFDSTATE ADMIN CTLWORD CC CV TNLID------------------------------------------------------------------------------ 0 Record(s) Found.

----End

Configuration Filel Configuration File on PE1

# sysname PE1 # mpls lsr-id 1.1.1.1 mpls # mpls l2vpn # mpls ldp # interface Atm1/0/0 undo shutdown # mpls ldp remote-peer 4.4.4.4 remote-ip 4.4.4.4 mpls ldp remote-peer 5.5.5.5 remote-ip 5.5.5.5 undo remote-ip pwe3 # # interface Atm1/0/0.1 atm cell transfer pvc 1/100 mpls l2vc 4.4.4.4 1 mpls l2vc 5.5.5.5 2 secondary mpls l2vpn reroute immediately-switch #



3-25

interface GigabitEthernet2/0/2 undo shutdown ip address 102.1.1.1 255.255.255.0 mpls mpls ldp # interface GigabitEthernet2/0/1 undo shutdown ip address 101.1.1.1 255.255.255.0 mpls mpls ldp # interface LoopBack0 ip address 1.1.1.1 255.255.255.255 # ospf 1 area 0.0.0.0 network 101.1.1.0 0.0.0.255 network 102.1.1.0 0.0.0.255 network 1.1.1.1 0.0.0.0 # return

l Configuration File on P1# sysname P1 # mpls lsr-id 2.2.2.2 mpls # mpls l2vpn # mpls ldp # interface GigabitEthernet2/0/1 undo shutdown ip address 101.1.1.2 255.255.255.0 mpls mpls ldp




Issue 03 (2010-03-31)

# interface GigabitEthernet3/0/2 undo shutdown ip address 104.1.1.1 255.255.255.0 mpls mpls ldp # interface LoopBack0 ip address 2.2.2.2 255.255.255.255 # ospf 1 area 0.0.0.0 network 101.1.1.0 0.0.0.255 network 104.1.1.0 0.0.0.255 network 2.2.2.2 0.0.0.0 # return

l Configuration File on P2# sysname P2 # mpls lsr-id 3.3.3.3 mpls # mpls l2vpn # interface GigabitEthernet2/0/2 undo shutdown ip address 102.1.1.2 255.255.255.0 mpls mpls ldp # interface GigabitEthernet3/0/2 undo shutdown ip address 105.1.1.2 255.255.255.0 mpls



3-27

mpls ldp # interface LoopBack0 ip address 3.3.3.3 255.255.255.255 # ospf 1 area 0.0.0.0 network 3.3.3.3 0.0.0.0 network 102.1.1.0 0.0.0.255 network 105.1.1.0 0 0 0 255# return

l Configuration File on PE2# sysname PE2 # mpls lsr-id 4.4.4.4 mpls # mpls l2vpn # mpls ldp # mpls ldp remote-peer 1.1.1.1 remote-ip 1.1.1.1 undo remote-ip pwe3 # interface Atm-Trunk1 # interface Atm-Trunk1.1 p2p pvc 1/100 mpls l2vc 1.1.1.1 1 # interface GigabitEthernet1/0/2 undo shutdown ip address 106.1.1.1 255.255.255.0 # interface GigabitEthernet3/0/2 undo




Issue 03 (2010-03-31)

shutdown ip address 104.1.1.2 255.255.255.0 mpls mpls ldp # interface Atm1/0/1 undo shutdown aps group 1 aps working 5.5.5.5# atm-trunk 1 # interface LoopBack0 ip address 4.4.4.4 255.255.255.255 # ospf 1 area 0.0.0.0 network 104.1.1.0 0.0.0.255 network 106.1.1.0 0.0.0.255 network 4.4.4.4 0.0.0.0 # return

l Configuration File on PE3# sysname PE3 # mpls lsr-id 5.5.5.5 mpls # mpls l2vpn # mpls ldp # mpls ldp remote-peer 1.1.1.1 remote-ip 1.1.1.1 undo remote-ip pwe3 # interface Atm-Trunk1 #



3-29

interface Atm-Trunk1.1 p2p pvc 1/100 mpls l2vc 1.1.1.1 2 # interface GigabitEthernet1/0/2 undo shutdown ip address 106.1.1.2 255.255.255.0 # interface GigabitEthernet3/0/2 undo shutdown ip address 105.1.1.2 255.255.255.0 mpls mpls ldp # interface Atm1/0/2 undo shutdown aps group 1 aps protect 4.4.4.4 aps mode one2one bidirection aps revert 1 aps timers 1 3# atm-trunk 1 # interface LoopBack0 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 105.1.1.0 0.0.0.255 network 106.1.1.0 0.0.0.255

# return

l Configuration File on CE1# sysname CE1#interface Atm1/0/0 undo shutdown




Issue 03 (2010-03-31)

#interface Atm1/0/0.1 p2p#return

l Configuration File on CE2# sysname CE2 # interface Atm-Trunk1 #interface Atm2/0/1 undo shutdown aps group 1 aps working# atm-trunk 1 # interface Atm2/0/2 undo shutdown aps group 1 aps protect aps mode one2one bidirection aps revert 1# atm-trunk 1 #

return

3.4.2 Example for Configuring TDM on the CPOS interfacesConfigured with APS

Networking RequirementsGenerally, on a 2G RAN, one to three E1 interfaces on a BTS are connected to a BSC. Somemobile operators do not own fixed network infrastructure, and have to rent E1 lines of fixed-line network operators at a high price. By deploying TDMoPSN service, that is, TDM transparenttransmission on a 2G RAN, these mobile operators can achieve transparent transmission of 2Gservices between the BTSs and BSCs in the same city over TDM links in a Metro Ethernet (ME)network, which is both simple and cost-saving.

As shown in Figure 3-2, it is required that the BTS and PE1 should be connected through twoE1 links The BSC and PE2 should be connected through the CPOS interface ,and the CPOSinterfaces are configured with APS so as to increase reliability of data. On the channelized serialinterface of E1 links, configure the encapsulation protocol as TDM. Then, a PW is set up betweenPE1 and PE2 to transparently transmit TDM cells.



3-31

Figure 3-2 Networking diagram of configuring TDMoPSN

PE1 PE2P

BTS

BSC

CPOS3/0/1GE2/0/0GE1/0/0 GE2/0/0

GE2/0/0

E12/0/1

E12/0/22×TDM E1

PWE3 TDMTransparent Cell Transport

CPOS3/0/2

Router Interface IP Address

PE1 GE2/0/0

Loopback0

10.1.1.1/24

192.2.2.2/32

P GE1/0/0

GE2/0/0

Loopback0

10.1.1.2/24

10.2.1.1/24

192.4.4.4/32

PE2 GE2/0/0

Loopback0

10.2.1.2/24

192.3.3.3/32


1. Run the IGP protocol on the backbone network so that devices can communicate with eachother.

2. Configure basic MPLS functions on the backbone network, and configure MPLS L2VPNfunctions on PE devices. Establish the remote MPLS LDP peer relationship between PEsat both ends of the PW.

3. Configure parameters for the TDM interface.4. Configure the PW template.5. Establish MPLS L2VC connections on PEs.6. Configure APS on PE2


l L2VC IDs at both ends of the PW (must be the same)

l MPLS LSR IDs of the PEs and P router

l IP addresses of the remote peers of PEs




Issue 03 (2010-03-31)

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, and configure MPLS L2VPNfunctions on PE devices. Then, establish the remote MPLS LDP peer relationship between PEsat both ends of the PW. For detailed configurations, see the configuration file of this example.

The remote MPLS LDP peer relationship is required only for the dynamic PW.

Step 3 Configure APS.

Configure PE2

CAUTIONThe 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] controller cpos 3/0/2[PE2-Cpos3/0/2] aps group 1[PE2-Cpos3/0/2] aps protect [PE2-Cpos3/0/2] aps mode one-plus-one unidirection[PE2-Cpos3/0/2] quit[PE2] interface cpos-trunk 1[PE2-cpos-trunk1] quit[PE2] controller cpos 3/0/1[PE2-Cpos3/0/1] cpos-trunk 1[PE2-Cpos3/0/1] quit[PE2] controller cpos 3/0/2[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 ce1[PE1-E1 2/0/1] channel-set 1 timeslot-list 1-15 ts0[PE1-E1 2/0/1] quit[PE1] controller e1 2/0/2[PE1-E1 2/0/2] using ce1[PE1-E1 2/0/2] channel-set 1 timeslot-list 16-31 ts0[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 channel-set 1 timeslot-list 1-15 ts0[PE2-Cpos-trunk1] e1 2 channel-set 2 timeslot-list 16-31 ts0

Step 5 Configure the encapsulation protocol on the serial interface as TDM.

1. Configure PE1.[PE1] interface serial2/0/1:1[PE1-Serial2/0/1:0] link-protocol tdm



3-33

[PE1-Serial2/0/1:0] quit[PE1] interface serial2/0/2:1[PE1-Serial2/0/2:1] link-protocol tdm[PE1-Serial2/0/2:1] quit

2. Configure PE2.[PE2] interface trunk-serial1/1:1[PE2-Trunk-Serial1/1:1] link-protocol tdm[PE2-Serial1/1:1] quit[PE2] interface trunk-serial1/2:2[PE2-Trunk-Serial1/2:2] link-protocol tdm[PE2-Trunk-Serial1/2:2] quit

Step 6 Configuring the PW.

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] idle-code 33[PE1-pw-template-1to3] quit[PE1] interface serial2/0/1:1[PE1-Serial2/0/1:0] mpls l2vc pw-template 1to3 100[PE1] interface serial2/0/2:1[PE1-Serial2/0/2:1] 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] idle-code 33[PE2-pw-template-3to1] quit[PE2] interface trunk-serial1/1:1[PE2-Trunk-Serial1/1:1] mpls l2vc pw-template 3to1 100[PE2-Trunk-Serial1/1:1] undo shutdown[PE2-Trunk-Serial1/1:1] quit[PE2] interface trunk-serial1/2:2[PE2-Trunk-Serial1/2:2] mpls l2vc pw-template 3to1 200[PE2-Trunk-Serial1/2:2] undo shutdown[PE2-Trunk-Serial1/2:2] quit


Simulate a fault on the side of PE2 connecting to the BSC

# Run the shutdown command on CPOS3/0/1.

[PE2] controller cpos 3/0/1[PE2-Cpos3/0/1] shutdown

Run the display aps group and display cpos-trunk commands ,you can view that the status ofprotection interface CPOS3/0/2 becomes active.

[PE2] display aps group 1APS Group 1: Cpos 3/0/1 working channel 1(Inactive) Pos3/0/2 protection channel 0(Active) Unidirection, 1+1 mode, No Revert mode No Request on Both Working and Protection Side

------------------------------------------------------------------------Group Work-Channel Protect-Channel Wtr W-State P-State Switch-Cmd Switch-Result------------------------------------------------------------------------1 Cpos 3/0/1 Cpos 3/0/2 NA sf ok NA switch------------------------------------------------------------------------total entry: 1




Issue 03 (2010-03-31)

<PE2> display cpos-trunk 1Interface Cpos-Trunk1's state information is:,Operate status: up Number Of Up Port In Trunk: 2--------------------------------------------------------------------------------PortName Status Active StatusCpos3/0/1 Down InactiveCpos3/0/2 Up Active

Run the display mpls l2vc command on PEs. You can view that the status of the PW is Up ,and it has not been influenced by the fault of CPOS3/0/1.

Take the display on PE1 as an example:

<PE1> display mpls l2vc interface serial2/0/1:1*client interface : Serial2/0/1:1 is up session state : up AC state : up VC state : up VC ID : 100 VC type : CESoPSN basic mode 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 : 33 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 Filesl Configuration file of PE1:

# sysname PE1



3-35

# 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 idle-code 33#mpls ldp# mpls ldp remote-peer 192.3.3.3 remote-ip 192.3.3.3 #controller e1 2/0/1using ce1channel-set 1 timeslot-list 1-15 ts0undo shutdown#controller e1 2/0/2using ce1channel-set 1 timeslot-list 16-31 ts0undo shutdown#interface serial2/0/1:1link-protocol tdmmpls l2vc pw-template 1to3 100undo shutdown#interface serial2/0/2:1link-protocol tdmmpls l2vc pw-template 1to3 200undo shutdown#interface GigabitEthernet2/0/0 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 1area 0.0.0.0 network 192.2.2.2 0.0.0.0 network 10.1.1.0 0.0.0.255#return

l Configuration file of PE2:# sysname PE2# mpls lsr-id 192.3.3.3 mpls# mpls l2vpn#pw-template 3to1 peer-address 192.2.2.2 jitter-buffer depth 20 tdm-encapsulation-number 40 idle-code 33#mpls ldp#




Issue 03 (2010-03-31)

mpls ldp remote-peer 192.2.2.2 remote-ip 192.2.2.2# cpos-trunk 1e1 1 channel-set 1 timeslot-list 1-15 ts0code amie1 2 channel-set 2 timeslot-list 16-31 ts0#interface serial1/1:1link-protocol tdmmpls l2vc pw-template 3to1 100undo shutdown#interface serial1/2:2link-protocol tdmmpls l2vc pw-template 3to1 200undo shutdown#interface GigabitEthernet2/0/0 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 lsr-id 192.4.4.4 mpls#mpls ldp#interface GigabitEthernet1/0/0 undo shutdown ip address 10.1.1.2 255.255.255.0 mpls mpls ldp#interface GigabitEthernet2/0/0 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-37

4 VRRP Configuration

About This Chapter

This chapter describes the fundamentals of VRRP, the configurations of basic and advancedfunctions of VRRP, and VRRP maintenance and troubleshooting.

4.1 VRRP IntroductionThis section describes the fundamentals and concepts of VRRP.

4.2 Configuring the VRRP Backup GroupThis section describes basic configurations such as how to create a backup group and how toconfigure a virtual IP address and priorities of interfaces in the backup group.

4.3 Configuring VRRP to Track the Status of an InterfaceThis section describes how to configure VRRP to track the interface status to improve the systemreliability.

4.4 Configuring VRRP Fast Switchover (Common Mode)This section describes how to configure VRRP to track BFD sessions to implement fastswitchover.

4.5 Configuring VRRP Fast Switchover (Using BFD Sampling)

4.6 Configuring Ignorance of the Down of an Interface Where the mVRRP Backup Group IsConfigured

4.7 Configuring VRRP Applications in VLANIFThis section describes how to configure VRRP on the VLANIF interface.

4.8 Configuring VRRP SecurityThis section describes how to implement the VRRP authentication.

4.9 Configuring VRRP Smooth SwitchingThis section describes the application and configuration of VRRP smooth switching

4.10 Adjusting and Optimizing VRRPThis section describes how to adjust the related parameters of VRRP packets to optimize VRRP.

4.11 Configuring mVRRP Backup GroupsThis section describes how to create a VRRP backup group and configure VRRP members andmember interfaces bind to mVRRP.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability 4 VRRP Configuration


4-1

4.12 Maintaining VRRP

4.13 Configuration ExamplesThis section describes how to debug VRRP.

4 VRRP ConfigurationHUAWEI NetEngine80E/40E Router



Issue 03 (2010-03-31)

4.1 VRRP IntroductionThis section describes the fundamentals and concepts of VRRP.

4.1.1 VRRP Overview

4.1.2 VRRP Features Supported by the NE80E/40E

4.1.1 VRRP OverviewIn general, all hosts in an internal network are configured with the same default route. Internalhosts send all the packets whose destination addresses are not on the local network segment tothe default egress gateway, such as Router A in Figure 4-1. Thus, the internal hosts and externalnetworks can communicate with each other. When the egress gateway is Down, however, allthe hosts using this gateway fail to communicate with external networks.

Figure 4-1 LAN default gateway

RouterA

10.0.0.1/24



Ethernet


Network

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 RFC3768. VRRP solves the problem of route selection among egress gateways by separating thephysical devices from logical devices.

On a LAN with multicast and broadcast capabilities (like the Ethernet), VRRP uses logicalgateways to ensure high availability of transmission links. This prevents service interruptionsthat are resulted from a gateway device failure, without changing the configuration of routingprotocols.

4.1.2 VRRP Features Supported by the NE80E/40E

Master/Backup ModeIn VRRP, it is the basic mode for the backup of IP addresses. In the master/backup mode, aVRRP backup group consists of a master router and multiple backup routers. Different routershave different priorities in this backup group. The router with the highest priority serves as themaster router.



4-3

l The master router undertakes all the services in normal condition.

l The backup routers undertakes 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 groupsundertake 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 differentpriorities 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 priorityof the router is automatically adjusted. The priorities of routers in the backup group change anda new master router is elected.

VRRP Fast Switchoverl 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 fastmaster/backup switchover by tracking the BFD session status. A maximum of eight BFDsessions can be configured and the master/backup switchover is performed at millisecondlevel. The VRRP master/backup switchover is accelerated because of tracking BFDsessions.

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 trackingBFD sessions.

– Differences:

– When VRRP tracks normal BFD sessions, the status of a VRRP backup group variesaccording to its priority change. This function is similar to that of tracking interfacestatus, but it is faster. When the status of the tracked BFD session becomes Up, thepriority of the router in the backup group restores the original value. When the BFDsession is configured on a backup router, the BFD session should be on the sameinterface with the VRRP backup group.

– When VRRP tracks peer BFD sessions and link BFD sessions, the status of thebackup group is changed and its priority is unchanged.




Issue 03 (2010-03-31)

– The peer BFD session can detect faults of local and remote NPEs and the links. Itcannot distinguish whether the failure occurs locally or remotely. The link BFDsession can only detect the faults of local links or NPEs.

l On a Metro Ethernet (ME) network, Bidirectional Forwarding Detection (BFD) is usuallyused 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 BFDcannot be configured on the UPE, the links between the UPE and NPEs becomes vulnerableand you need a new link protection mechanism. Ethernet in the First Mile (EFM), a slowlink detection protocol that requires fewer resources, can just be your choice, provided thatEFM is configured on the UPE.

VRRP Fast Switchover Using BFD SamplingGenerally, the VRRP backup group implements master/backup fast switchover by tracking theBFD session status. However, this method is not applicable in some special networkenvironments or when the device does not support the BFD function. In this case, you can usethe BFD sampling mode to implement master/backup fast switchover.

NOTE

In BFD sampling mode, the NPE establishes multiple link BFD sessions directly with each CE withoutestablishing the link BFD session with the PE.

Ignorance of Interface Down of the mVRRP Backup GroupVRRP defines three status types: Initialize, Master, and Backup. On being notified that theinterface where the VRRP backup group is configured is shut down, the VRRP backup groupswitches its status to Initialize.

The mVRRP backup group is configured on two directly connected devices and Heartbeatmessages of the mVRRP backup group are transmitted over the direct link between the twodevices. When one device fails, the interface of its peer device goes Down and the status of themVRRP 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 themVRRP backup group is configured to implement VRRP fast switchover, thus switching thestatus of the mVRRP backup group to Master rather than Initialize.

Enable/Disable the Ping Function to the Virtual IP AddressTo ping through virtual IP addresses that are used in the VRRP backup group, you can monitorthe operating status of the virtual routers but the VRRP backup group may suffer the ICMPattack. In the NE80E/40E, you can run a command to enable the function to ping the virtual IPaddress.

VRRP Security FunctionsFor different security levels of networks, you can set different authentication modes andauthentication keys in the header of VRRP packets.

In a secure network, you can adopt the default configuration. That is, the router does notauthenticate the VRRP packets to be sent and received. The router considers all the receivedpackets 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 arevulnerable to attacks. In simple text authentication mode, a string of 1 to 8 characters can be



4-5

configured as the authentication key. In MD5 authentication mode, a string of 1 to 8 charactersin plain text or a string of 24 characters in encrypted text can be configured as the authenticationkey.

VRRP Smooth SwitchingOn a network where VRRP backup groups are configured, the backup router switches to be themaster router because the original master router and backup router cannot communicate whenthe original master router performs the AMB/SMB switchover. After the AMB/SMBswitchover, the original master router preempts to be the master router again because its priorityis higher than the priority of the original backup router. During the AMB/SMB switchover, thesystem is busy with packet processing. Thus, the gratuitous ARP packets sent by the masterrouter are blocked or processed abnormally, and the master router must keep sending gratuitousARP packets to refresh the MAC entries on the downstream switch. As a result, user packetsare lost during this period.

After VRRP smooth switching is configured, before the AMB/SMB switchover, the masterrouter sets the interval for sending VRRP broadcast packets to a large value and notifies thevalue to the backup router through a VRRP packet. After receiving the VRRP packet, the backuprouter learns the interval carried in the packet. This ensures the stability of VRRP backup groupsduring or after the AMB/SMB switchover. Packet loss is thus prevented.

After VRRP smooth switching is enabled, the learning function takes precedence over thepreemption function. That is, if the interval carried in the received packet is inconsistent withthe current interval and the priority carried in the received packet is lower than the currentpriority, VRRP performs the learning and timer resetting functions first, and then the preemptionfunction.

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 smoothswitching cannot take effect.

mVRRPMany VRRP backup groups run between routers for different services. If each VRRP backupgroup needs to maintain its own state machine, a large number of VRRP packets are generatedbetween 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 otherbackup group members. Then, the status of the backup group member is determined by the statusof the bound mVRRP backup group.

NOTE

For the detailed configuration of the mVRRP, refer to Chapter 9 "VPLS Convergence Configuration" inthe HUAWEI NetEngine80E/40E Router Configuration Guide - VPN.

4.2 Configuring the VRRP Backup GroupThis section describes basic configurations such as how to create a backup group and how toconfigure a virtual IP address and priorities of interfaces in the backup group.


4.2.2 Creating a Backup Group and Configuring a Virtual IP Address




Issue 03 (2010-03-31)

4.2.3 Configuring the Priority of an Interface in a Backup Group




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/backupmode is as follows:– Only one backup group exist.

– The router with the highest priority in the backup group serves as the master router andundertakes the services.

– Except for the master router, other routers in the backup group serve as the backuprouters and work in the Backup state.

– If the master router fails, backup routers select a new master router based on theirpriorities to provide routing service.

l In the load balancing mode, multiple backup groups are created to share the traffic of anetwork. One router can join different backup groups. The load balancing mode is asfollows:– 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 gateways and others use backup

group 2 as their gateways.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 supportVRRP.


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



4-7

No. Data

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 IPAddress

Context

Do as follows on each router of a backup group:

Procedurel For VRRP for IPv4, run the following commands:

1. Run:system-view


2. Run:interface interface-type interface-number


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 systemcreates this backup group. Then, when you assign another virtual IP address to thebackup group, the system adds this address into the virtual IP address list of this backupgroup.

For users who require equivalent VRRP reliability, a backup group can be configuredwith multiple virtual IP addresses. Different addresses serve different user groups.This is easy to manage and can prevent users' default gateway addresses from varyingwith the VRRP configuration. A maximum number of 16 virtual IP addresses can beconfigured for a backup group.

For a VRRP backup working in load balancing mode, you need to repeat the procedureto configure multiple backup groups on an interface. At least two backup groups arerequired on an interface. Backup groups are identified by VRIDs and their virtual IPaddresses cannot be identical.




Issue 03 (2010-03-31)

NOTE

On the NE80E/40E, a maximum number of 255 backup groups can be configured on eachinterface.

CAUTIONTo configure VRRP and static ARP simultaneously on a device, note that when VRRPis enabled on an interface such as a sub-interface for Dot1q VLAN tag termination, asub-interface for QinQ VLAN tag termination, or a VLANIF interface, you cannotuse the IP addresses mapping to static ARP entries related to these interfaces as theVRRP virtual addresses. Otherwise, incorrect host routes are generated and abnormalforwarding of the device may take place.

----End

4.2.3 Configuring the Priority of an Interface in a Backup Group

Context

In the master/backup mode, only one backup group is required. Devices have different prioritiesin this backup group. When the router with the highest priority serves as the master router andother routers are backup routers.

In the load balancing mode, two backup groups or more are required. Each router has differentpriorities in different backup groups. VRRP identifies the role of a router in a backup groupaccording to the priority. You can repeat configuring the priority of a router to ensure that themasters of VRRP backup groups are distributed on different routers.

Do as follows on the interface of each router in the backup group:


1. Run:system-view

The system view is displayed.2. Run:

interface interface-type interface-number

The interface view is displayed.3. Run:

vrrp vrid virtual-router-id priority priority-value

The priority of the router in the backup group is configured.

By default, the priority is 100. Priority 0 is reserved for special purpose. Priority 255is reserved for the IP address owner and this priority cannot be configured. A priorityranges from 1 to 254.

----End



4-9


PrerequisiteThe configurations of the VRRP Backup Group function are complete.

Procedurel Run the display vrrp [ interface interface-type interface-number [ virtual-router-id ] ]

[ brief ] command to Check the status of VRRP.

----End

ExampleIn the master/backup mode, after the configuration, you can run the display vrrp command toview the status of a VRRP backup group.

<HUAWEI> display vrrp GigabitEthernet2/0/0 | Virtual Router 1 state : Master Virtual IP : 10.1.1.111 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-vrrpConfig track link-bfd down-number : 0

In the load balancing mode, after the configuration, you can run the display vrrp command toview the status of a router in different backup groups.

<HUAWEI> display vrrp GigabitEthernet2/0/0 | Virtual Router 1 state : Master Virtual IP : 10.1.1.111 PriorityRun : 120 PriorityConfig : 120 MasterPriority : 120 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0101 Check TTL : YES Config type : normal-vrrpConfig track link-bfd down-number : 0 GigabitEthernet2/0/0 | Virtual Router 2 state : Backup Virtual IP : 10.1.1.112 PriorityRun : 100 PriorityConfig : 100 MasterPriority : 120 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0102 Check TTL : YES




Issue 03 (2010-03-31)

Config type : normal-vrrpConfig track link-bfd down-number : 0

4.3 Configuring VRRP to Track the Status of an InterfaceThis section describes how to configure VRRP to track the interface status to improve the systemreliability.


4.3.2 Configuring VRRP to Track the Status of an Interface



Applicable EnvironmentVRRP can monitor the status of the interface. That is, the backup is performed when the backupgroup is faulty, and the backup also can be performed when one interface of the router is faulty.

The methods of tracking the status of the interface are as follows:l 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.l The router with the highest priority becomes the master router and thus the master/backup

switchover of the VRRP backup group is complete.

Pre-configuration TasksBefore 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 PreparationTo 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-11

4.3.2 Configuring VRRP to Track the Status of an Interface

Context

The backup is performed when other interfaces on a router are unavailable. This feature isrequired in NAT applications.

Do as follows on the router of the tracked interface:


1. Run:system-view




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 thetracking backup group decrease by 10.

– increased value-increased: specifies the value by which the priority increaseswhen the tracked interface goes Down. The value ranges from 1 to 255. The highestpriority is 254. The value takes effect on backup routers in a VRRP backup group.

– reduced value-reduced: specifies the value by which the priority decreases whenthe tracked interface goes Down. The value ranges from 1 to 255. The lowestpriority is 1.

– When a VRRP backup group monitors both BFD sessions and interfaces, themaximum number of eight BFD sessions and interfaces can be created. Ifincreased value-increased is specified, the value of the increased VRRP backupgroup priority can exceed the priority of the master VRRP backup group only whenall the tracked BFD sessions or interfaces go Down. Otherwise, if the VRRPbackup group takes precedence of the peer because its priority increases when oneor part of tracked BFD sessions or interfaces go Down, the additional increasingof the priority is of no significance when other BFD sessions or interfaces areDown.

– To configure a VRRP6 backup group with the function of tracking the interfacestatus, ensure that an IPv4 address is assigned to the interface to be tracked. Forexample, GE 1/0/0 to be tracked is assigned an IPv6 address rather than an IPv4address. When a VRRP backup group tracks the interface, if IPv6 status on theinterface becomes Down, the routers in the VRRP backup group may fail to reduceor increase priorities to re-elect a new master router.




Issue 03 (2010-03-31)

NOTE

One router can track up to eight interfaces. When the router is the IP address owner, therouter cannot be configured to track the interface status. At present, the status of the loopbackinterface, NULL interface, CPOS interface, and AUX interface cannot be tracked.

----End


Prerequisite

The configurations of the VRRP to Track the Status of an Interface function are complete.



----End

Example

Run the display vrrp command, and you can view the Track IF field and the IF State field. TheTrack IF field indicates the type and number of the tracked interface, and the IF State fieldindicates the interface status, that is, Up or Down.

<HUAWEI> display vrrp GigabitEthernet2/0/0 | Virtual Router 1 State : Master Virtual IP : 10.1.1.111 PriorityRun : 130 PriorityConfig : 130 MasterPriority : 130 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0101 Check TTL : YES Config type : normal-vrrpConfig track link-bfd down-number : 0 Track IF : GigabitEthernet2/0/1 priority reduced : 10 IF State : UP

4.4 Configuring VRRP Fast Switchover (Common Mode)This section describes how to configure VRRP to track BFD sessions to implement fastswitchover.


4.4.2 Tracking the BFD Session Status

4.4.3 Tracking EFM Session Status




4-13


Applicable EnvironmentYou can apply VRRP to track BFD sessions or EFM. The changes of BFD sessions or EFMsessions are notified to the VRRP module to perform fast VRRP switchover.

A VRRP backup group can track the peer BFD session, link BFD session, and normal BFDsession at the same time. Moreover, the VRRP backup group can track the interface status.Generally, a VRRP backup group can only track the status of a peer BFD session or a link BFDsession, whereas the VRRP backup group can track the statuses of multiple normal BFD sessionsor interfaces.

The VRRP backup group tracks several BFD sessions. The changes of the status of BFD sessionsdo not affect each other.

When the VRRP backup group tracks normal BFD sessions and the BFD session status changes,the master/backup switchover is performed through the modification of the priority of the VRRPbackup group. When the tracked normal BFD sessions are restored, the priorities of routers inthe VRRP backup group are restored to their original values. When the VRRP backup grouptracks a peer BFD session and a link BFD session and the status of the BFD sessions changes,the status of the backup group is changed directly without the change of the backup grouppriority.

NOTE

l For the detailed information of EFM , refer to "Ethernet OAM Configuration" in the HUAWEINetEngine80E/40E Router Configuration Guide - Reliability.

l For the detailed configuration of the VRRP backup group tracking peer BFD sessions , link BFDsessions and EFM sessions, refer to Chapter 9 "VPLS Convergence Configuration" in the HUAWEINetEngine80E/40E Router Configuration Guide - VPN.

Pre-configuration TasksBefore configuring VRRP fast switchover, complete the following tasks:




l Configuring basic EFM OAM functions

l Configuring the VRRP backup group

l Configuring BFD sessions including normal BFD sessions, link BFD sessions, and peerBFD sessions

Data PreparationTo configure VRRP fast switchover, you need the following data.

No. Data

1 Backup group ID




Issue 03 (2010-03-31)

4.4.2 Tracking the BFD Session Status

ContextDo as follows on a router that needs the fast VRRP switchover:

NOTE

l When configuring fast VRRP switchover, if VRRP monitors the peer BFD session, you must configurepeer 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 cannottrack any BFD session to perform the fast switchover, and the status of the VRRP backup group shouldbe consistent with the status of the mVRRP backup group.


system-view


Step 2 Run:interface interface-type interface-number [.subinterface-number ]

The view of the interface configured with VRRP backup group is displayed.

Step 3 Run:l vrrp vrid virtual-router-id track bfd-session { session-name bfd-session-id |

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 thetracked BFD session goes Down. The value ranges from 1 to 255. The maximum value ofthe priority is 254. The value takes effect only when the status of the VRRP backup groupis Backup.reduced value-reduced: specifies the value by which the priority decreases when the trackedBFD session goes Down. The value ranges from 1 to 255. The lowest priority is 1. By default,when the tracked BFD sessions go Down, the value of the priority decreases by 10.When configuring the value by which the priority increases or decreases, especially thedefault value, ensure that the priority of a backup router in a backup group is higher than thatof a master router whose priority is changed. In this manner, the VRRP status can be switchedfast.When a VRRP backup group monitors both BFD sessions and interfaces, the maximumnumber of BFD sessions and interfaces is 8. If increased value-increased is specified, thevalue of the increased VRRP backup group priority can exceed the priority of the masterVRRP 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 isincreased when one or part of tracked BFD sessions or interfaces go Down, the additionalincreasing of the priority is of no significance when other BFD sessions or interfaces goDown.

Or, run:

l 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.



4-15

If the type of the link BFD is of any of following, you must run the process-pst commandto allow the BFD session to modify the port status table (PST). Otherwise, the link BFDsession status monitored 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

----End

4.4.3 Tracking EFM Session Status

ContextDo as follows on each router of the VRRP backup group:

Procedure





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

The VRRP backup group is configured to track EFM.

----End


PrerequisiteThe configurations of the VRRP Fast Switchover function are complete.

Procedure

Step 1 Run the display vrrp [ interface interface-type interface-number [ virtual-router-id ] ]command to Check the status of VRRP.

----End

Examplerun the display vrrp command, and you can view that the BFD session that is tracked by VRRPis Up. The command output is as follows:

<HUAWEI> display vrrp




Issue 03 (2010-03-31)

GigabitEthernet1/0/0.3 | Virtual Router 1 state : Backup Virtual IP : 192.168.1.100 PriorityRun : 120 PriorityConfig : 120 MasterPriority : 130 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Check TTL : YES Config type : normal-vrrp Config track link-bfd down-number : 0 Track BFD : 1 Priority increased : 20 BFD-Session State : Up

GigabitEthernet1/0/0.2 | Virtual Router 2 state : Backup Virtual IP : 192.168.2.254 PriorityRun : 100 PriorityConfig : 100 MasterPriority : 120 Preempt : yes Delay time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Check TTL : YES Config type : admin-vrrp Config track link-bfd down-number : 0 Track EFM : GigabitEthernet2/0/0 EFM state : up Track BFD : 2 type : peer bfd-session state : up

GigabitEthernet1/0/0.1 | Virtual Router 1 state : Master Virtual IP : 192.168.1.254 PriorityRun : 120 PriorityConfig : 120 MasterPriority : 120 Preempt : yes Delay time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Check TTL : YES Config type : admin-vrrp Config track link-bfd down-number : 0 Track BFD : 4 type : link bfd-session state : up Track BFD : 1 type : peer bfd-session state : up

4.5 Configuring VRRP Fast Switchover (Using BFDSampling)


4.5.2 Binding the Service VRRP Backup Group to the mVRRP Backup Group

4.5.3 Configuring the mVRRP Backup Group to Track the BFD Session Status

4.5.4 Setting the Threshold for VRRP Fast Switchover

4.5.5 Enabling the Association Between the mVRRP Backup Group Status and the Route




4-17


Applicable EnvironmentGenerally, the VRRP backup group implements master/backup switchover by tracking the BFDsession status. However, this method does not work in some special network environments orwhen 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 terminationof the NPE across the VPLS convergence network.

On the NPE, the mVRRP backup group and the service VRRP backup group are configured andthe 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 CErather than with the PE.

NOTE

Suppose that the CE supports the BFD function.

Thus, the mVRRP backup group can implement master/backup switchover by tracking multiplelink BFD sessions between the NPE and the CE, although it cannot track the BFD sessionbetween the NPE and the PE.




Issue 03 (2010-03-31)

Figure 4-2 Typical networking of VRRP fast switchover (using BFD sampling)

CE4

CE1

CE2

CE3

NPE1

NPE2

MPLS/IP CorePeerBFD

PE1

PE2

Link BFD

IP:10.100.1.1/24GW:10.100.1.200Inner VLAN: 110Outer VLAN: 10




Access CoreVPLS convergence network


Before configuring VRRP fast switchover using BFD sampling, complete the following tasks:


l Configuring link attributes for interfaces

l Configuring network layer attributes for interfaces to ensure network connectivity

l Configuring VRRP backup groups, including service VRRP backup groups and mVRRPbackup groups

l Configuring BFD sessions, including link BFD sessions and peer BFD sessions (It isrequired 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.



4-19

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 mVRRPBackup Group

Context

Do as follows on the device that need perform VRRP fast switchover:

Procedure




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 [.subinterface-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 receivingVRRP packets. Alternatively, it implements its state machine by directly copying the status ofthe mVRRP back group. A service VRRP backup group can be bound to only one mVRRPbackup group.

----End

4.5.3 Configuring the mVRRP Backup Group to Track the BFDSession Status

Context

Do as follows on a router that needs the fast VRRP switchover:




Issue 03 (2010-03-31)

NOTE



Procedure






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 thetracked BFD session goes Down. The value ranges from 1 to 255. The maximum value ofthe priority is 254. The value takes effect only when the status of the VRRP backup groupis Backup.reduced value-reduced: specifies the value by which the priority decreases when the trackedBFD session goes Down. The value ranges from 1 to 255. The lowest priority is 1. By default,when the tracked BFD sessions go Down, the value of the priority decreases by 10.When configuring the value by which the priority increases or decreases, especially thedefault value, ensure that the priority of a backup router in a backup group is higher than thatof a master router whose priority is changed. In this manner, the VRRP status can be switchedfast.When a VRRP backup group monitors both BFD sessions and interfaces, the maximumnumber of BFD sessions and interfaces is 8. If increased value-increased is specified, thevalue of the increased VRRP backup group priority can exceed the priority of the masterVRRP 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 isincreased when one or part of tracked BFD sessions or interfaces go Down, the additionalincreasing of the priority is of no significance when other BFD sessions or interfaces goDown.

Or, run:

l 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.If the type of the link BFD is of any of following, you must run the process-pst commandto allow the BFD session to modify the port status table (PST). Otherwise, the link BFDsession status monitored by mVRRP is not the same as the actual session status.– BFD for static LSP



4-21

– 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 doesnot establish the link BFD session with the PE; instead, the NPE establishes multiple link BFDsessions directly with each CE. By tracking the BFD session status, the NPE implements master/backup fast switchover of the mVRRP backup group.

----End


ContextDo as follows on the device that need perform VRRP fast switchover:

Procedure




The view of the interface where the mVRRP backup group is configured is displayed.

Step 3 Run:vrrp vrid 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 ofsessions in the Down state reaches or exceeds this threshold, the mVRRP backup group performsmaster/backup fast switchover.

----End

4.5.5 Enabling the Association Between the mVRRP Backup GroupStatus and the Route


Procedure






Issue 03 (2010-03-31)



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 differentstatuses of VRRP backup groups coexist. Hence, after the association between the VRRP backupgroup status and the route is enabled, it is recommended that only one VRRP backup group beconfigured 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 networksegment 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 networksegment route and remote host route of the interface where the VRRP backup group is configured.

l For other types of interfaces:

l When the status of the VRRP backup group becomes Initialize, the device deletes the networksegment 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 networksegment route of the interface where the VRRP backup group is configured.

----End


PrerequisiteAll configurations of VRRP fast switchover using BFD sampling are complete.


command to view the status of the VRRP backup group.

----End

ExampleRun the display vrrp command. The command output shows that the status of the BFD sessiontracked by the mVRRP backup group is Up and the threshold of VRRP fast switchover is 2.

[HUAWEI] display vrrp interface gigabitethernet1/0/1.1 GigabitEthernet1/0/1.1 | Virtual Router 10 State : Master Virtual IP : 10.1.1.1 PriorityRun : 120 PriorityConfig : 120 MasterPriority : 120 Preempt : YES Delay Time : 0 TimerRun : 1



4-23

TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-010a Check TTL : YES Config type : admin-vrrp Config track link-bfd down-number : 2 Track BFD : link1 type: link BFD-session state : UP Track BFD : peer1 type: peer BFD-session state : UP Track BFD : link2 type: link BFD-session state : UP Track BFD : link3 type: link BFD-session state : UP Track BFD : link4 type: link BFD-session state : UP

4.6 Configuring Ignorance of the Down of an InterfaceWhere the mVRRP Backup Group Is Configured


4.6.2 Configuring the mVRRP Backup Group

4.6.3 Binding the Service VRRP Backup Group to the mVRRP Backup Group

4.6.4 Configuring the mVRRP Backup Group to Track the BFD Session Status


4.6.6 Enabling the Association Between the mVRRP Backup Group Status and the Route



Applicable EnvironmentVRRP defines three status types: Initialize, Master, and Backup. On being notified that theinterface is shut down, the VRRP backup group switches its status to Initialize.

As shown in Figure 4-3, the CE connects to the sub-interface for QinQ VLAN tag terminationof the NPE across the VPLS convergence network.

On the NPE, the mVRRP backup group and the service VRRP backup group are configured andthe mVRRP backup group is responsible for tracking the BFD session to implement VRRP fastswitchover. 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 groupand the peer BFD session cannot be established between NPE1 and NPE2.

l The VPLS convergence network belongs to another operator, so the link BFD sessioncannot 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 backupgroup to implement VRRP fast switchover.




Issue 03 (2010-03-31)

NPE1 and NPE2 establish the mVRRP backup group and peer BFD session through a direct linkrather than the VPLS convergence network.

Thus, when the interface where the mVRRP backup group is configured goes Down, the statusof 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 throughthe 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 thereliability 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 mVRRPbackup group is configured

CE4

CE1

CE2

CE3

NPE1

NPE2

MPLS/IPCore

PeerBFD

PE1

PE2

Access Core

PW

PW

AdminVRRP

Horizontal split

PE3

VPLS convergence network


Before configuring ignorance of the down of an interface where the mVRRP backup group isconfigured, complete the following tasks:


l Configuring link attributes for interfaces

l Configuring network layer attributes for interfaces to ensure network connectivity



4-25

l Configuring VRRP backup groups, including the service VRRP backup groups and themVRRP backup group

l Configuring BFD sessions, including the link BFD sessions and the peer BFD session (Itis required to configure Link BFD sessions between the PE and each CE.)

Data PreparationTo configure ignorance of the down of an interface where the mVRRP backup group isconfigured, you need the following data.

No. Data

1 VRRP Virtual Router IDs (VRIDs) and virtual IP addresses

2 Priorities of VRRP backup groups

3 Local and remote discriminators of BFD sessions

4.6.2 Configuring the mVRRP Backup Group

ContextDo as follows on the router where the mVRRP backup group is configured:

Procedure





Step 3 Run:vrrp vrid virtual-router-id virtual-ip virtual-address

A VRRP backup group is created, and a virtual IP address is assigned to the VRRP backup group.

Step 4 Run:vrrp vrid virtual-router-id priority priority-value

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 downthe direct link between NPE1 and NPE2. Otherwise, the mVRRP backup groups on NPE1 andNPE2 both become Master, causing service interruption.




Issue 03 (2010-03-31)

In all networking environments except the scenario as shown in Figure 4-3, it is notrecommended to enable the function of ignorance of interface down of the mVRRP backupgroup. Otherwise, the state machine of the VRRP backup group is inconsistent with that definedin the RFC.

----End

4.6.3 Binding the Service VRRP Backup Group to the mVRRPBackup Group

Context

Do as follows on the device that need perform VRRP fast switchover:

Procedure





Step 3 Run:vrrp vrid virtual-router-id1 track admin-vrrp interface interface-type interface-number [.subinterface-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 receivingVRRP packets. Alternatively, it implements its state machine by directly copying the status ofthe mVRRP back group. A service VRRP backup group can be bound to only one mVRRPbackup group.

----End

4.6.4 Configuring the mVRRP Backup Group to Track the BFDSession Status

Context

Do as follows on a router that needs the fast VRRP switchover:

NOTE





4-27

Procedure






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 thetracked BFD session goes Down. The value ranges from 1 to 255. The maximum value ofthe priority is 254. The value takes effect only when the status of the VRRP backup groupis Backup.reduced value-reduced: specifies the value by which the priority decreases when the trackedBFD session goes Down. The value ranges from 1 to 255. The lowest priority is 1. By default,when the tracked BFD sessions go Down, the value of the priority decreases by 10.When configuring the value by which the priority increases or decreases, especially thedefault value, ensure that the priority of a backup router in a backup group is higher than thatof a master router whose priority is changed. In this manner, the VRRP status can be switchedfast.When a VRRP backup group monitors both BFD sessions and interfaces, the maximumnumber of BFD sessions and interfaces is 8. If increased value-increased is specified, thevalue of the increased VRRP backup group priority can exceed the priority of the masterVRRP 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 isincreased when one or part of tracked BFD sessions or interfaces go Down, the additionalincreasing of the priority is of no significance when other BFD sessions or interfaces goDown.

Or, run:

l 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.If the type of the link BFD is of any of following, you must run the process-pst commandto allow the BFD session to modify the port status table (PST). Otherwise, the link BFDsession status monitored 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

In this scenario, the NPEs establish the peer BFD session between each other but the NPE doesnot establish the link BFD session with the PE; instead, the NPE establishes multiple link BFD




Issue 03 (2010-03-31)

sessions directly with each CE. By tracking the BFD session status, the NPE implements master/backup fast switchover of the mVRRP backup group.

----End




system-view




Step 3 Run:vrrp vrid 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 ofsessions in the Down state reaches or exceeds this threshold, the mVRRP backup group performsmaster/backup fast switchover.

----End

4.6.6 Enabling the Association Between the mVRRP Backup GroupStatus and the Route



system-view




Step 3 Run:vrrp trigger route

The association between the mVRRP backup group status and the route is enabled.



4-29

At present, multiple VRRP backup groups can be configured on an interface and thus differentstatuses of VRRP backup groups coexist. Hence, after the association between the VRRP backupgroup status and the route is enabled, it is recommended that only one VRRP backup group beconfigured 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 networksegment 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 networksegment route and remote host route of the interface where the VRRP backup group is configured.

l For other types of interfaces:

l When the status of the VRRP backup group becomes Initialize, the device deletes the networksegment 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 networksegment route of the interface where the VRRP backup group is configured.

----End


PrerequisiteAll configurations of VRRP fast switchover using BFD sampling are complete.


command to view the status of the VRRP backup group.

----End

ExampleRun the display vrrp command. The command output shows that the status of the BFD sessiontracked by the mVRRP backup group is Up and the threshold of VRRP fast switchover is 2.

[HUAWEI] display vrrp interface gigabitethernet1/0/1.1 GigabitEthernet1/0/1.1 | Virtual Router 10 State : Master Virtual IP : 10.1.1.1 PriorityRun : 120 PriorityConfig : 120 MasterPriority : 120 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-010a Check TTL : YES Config type : admin-vrrp Config track link-bfd down-number : 2 Track BFD : link1 type: link BFD-session state : UP Track BFD : peer1 type: peer BFD-session state : UP Track BFD : link2 type: link




Issue 03 (2010-03-31)

BFD-session state : UP Track BFD : link3 type: link BFD-session state : UP Track BFD : link4 type: link BFD-session state : UP

4.7 Configuring VRRP Applications in VLANIFThis section describes how to configure VRRP on the VLANIF interface.


4.7.2 Configuring VRRP on VLANIF

4.7.3 (Optional) Configuring the Sending Mode of VRRP Packets in Super-VLAN



Applicable EnvironmentVLANIF supports VRRP functions.

Pre-configuration TasksBefore configuring VRRP on the VLANIF interface, complete the followings tasks:



l Configuring sub-VLAN

l Configuring super-VLAN

Data PreparationTo 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-31

4.7.2 Configuring VRRP on VLANIF

ContextDo as follows on a router on which VRRP runs on the VLANIF interface:

Procedure



Step 2 Run:interface vlanif vlan-id

The VLAN interface view is displayed.





----End

4.7.3 (Optional) Configuring the Sending Mode of VRRP Packetsin Super-VLAN

ContextDo as follows on a VRRP router that is configured with a super-VLAN:

Procedure



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




Issue 03 (2010-03-31)


PrerequisiteThe configurations of the VRRP Applications in VLANIF are complete.

Procedure

Step 1 Run the display vrrp [ interface interface-type interface-number [ virtual-router-id ] ]command to Check the status of VRRP.

----End

ExampleAfter the configuration, run the display vrrp interface vlanif command, and you can view theVRRP status on the VLANIF interface.

<HUAWEI> display vrrp interface vlanif 40 Vlanif40 | Virtual Router 1 State : Master Virtual IP : 100.1.1.111 PriorityRun : 120 PriorityConfig : 120 MasterPriority : 120 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0101 Check TTL : YES Config type : normal-vrrpConfig track link-bfd down-number : 0

4.8 Configuring VRRP SecurityThis section describes how to implement the VRRP authentication.


4.8.2 Configuring the Authentication Mode of VRRP Packets



Applicable EnvironmentIn a secure network, by default, the router considers received and sent VRRP packets real andvalid without authenticating them. In this case, you need not configure an authentication key.

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



4-33

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 localauthentication key. If they are the same, VRRP packets are valid. Otherwise, the routerdiscards the received VRRP packets and sends a Trap packet to the Network ManagementSystem (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 andcompares 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 atrap message to the network management system.

Pre-configuration TasksBefore configuring the VRRP security function, complete the following tasks:





Data PreparationTo 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

ContextDo as follows on the router that needs to be configured with an authentication mode for VRRPpackets:

Procedure






Issue 03 (2010-03-31)





Step 4 (optional) Run:vrrp vrid virtual-router-id priority priority-value


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 thebackup 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.

----End


PrerequisiteThe configurations of the VRRP Security function are complete.

Procedure

Step 1 Run the display vrrp [ interface interface-type interface-number [ virtual-router-id ] ]command to check the status of VRRP.

----End

ExampleAfter the configuration, run the display vrrp command, and you can view the mode of the packetauthentication.

<HUAWEI> display vrrp GigabitEthernet1/0/0 | Virtual Router 1 State : Master Virtual IP : 10.1.1.111 PriorityRun : 120 PriorityConfig : 120 MasterPriority : 120 Preempt : YES Delay Time : 20 TimerRun : 1 TimerConfig : 1 Auth Type : MD5 Auth key : >6M*PO438G/Q=^Q`MAF4<1!! Virtual Mac : 0000-5e00-0101 Check TTL : YES Config type : normal-vrrp



4-35

Config track link-bfd down-number : 0

According to the preceding command output, the Auth Type field displays MD5, and the Authkey field displays >6M*PO438G/Q=^Q`MAF4<1!!. That is, VRRP backup group 1 adoptsMD5 authentication, and the authentication key is >6M*PO438G/Q=^Q`MAF4<1!!.

4.9 Configuring VRRP Smooth SwitchingThis section describes the application and configuration of VRRP smooth switching


4.9.2 Configuring VRRP Smooth Switching



Applicable EnvironmentIn the network where VRRP backup groups are configured, the backup router switches to themaster router because the original master router and backup router cannot communicate in timewhen the original master router performs the AMB/SMB switchover. After the AMB/SMBswitchover, the original master router preempts to be the master router again because its priorityis higher than the priority of the original backup router.

Because the system is too busy during the switchover, the master router cannot send Hellopackets normally and the backup router cannot receive packets timely. In this case, the backuprouter preempts to be the master router. Then, the link switchover is performed and this causespacket loss.

Enabling VRRP smooth switching on a router can optimize the VRRP performance and reducethe impact on the user traffic.

Pre-configuration TasksNone.

Data PreparationTo 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

ContextDo as follows on the router of a VRRP backup group:




Issue 03 (2010-03-31)


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 VRRPsmooth switching is configured.

By default, VRRP smooth switching is enabled, and the interval carried in the VRRP packet is100 seconds.

Before running the command, you must enable the function of learning the interval for receivingVRRP 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 theinterval set by the backup router, the backup router resets the "masterdown" time after the backuprouter 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 masterrouter. As a result, two master routers exist.

l During the AMB/SMB switchover, the master router sends VRRP smooth switching packets at theconfigured interval. If the time configured by the master router for VRRP smooth switching, such as1s, is shorter than the configured interval for sending VRRP broadcast packets, such as 10s, VRRPpackets 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


PrerequisiteThe configurations of the VRRP Smooth Switching function are complete.

ProcedureStep 1 Run the display vrrp [ interface interface-type interface-number [ virtual-router-id ] ]

command to check the status of the VRRP backup group.

----End

ExampleAfter 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, andthus the user traffic is not affected. After the AMB/SMB switchover, all VRRP configurationsof the new AMB are consistent with those of the original AMB.

<HUAWEI> display vrrpEthernet2/0/0 | Virtual Router 1 State : Master



4-37

Virtual IP : 10.10.10.158 PriorityRun : 180 PriorityConfig : 180 MasterPriority : 180 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0101 Check TTL : YES Config type : normal-vrrpConfig track link-bfd down-number : 0

4.10 Adjusting and Optimizing VRRPThis section describes how to adjust the related parameters of VRRP packets to optimize VRRP.


4.10.2 Configuring the Interval for Sending VRRP Advertising Messages

4.10.3 Configuring the Preemption Delay Time of Backup Group Routers

4.10.4 Enabling the Reachability Test of the Virtual IP Address

4.10.5 Disabling a Router from Checking Number of Hops in VRRP Packets

4.10.6 Configuring the Timeout Time of Sending Gratuitous ARP Packets by the Master router




You can configure the related parameters of VRRP packets to optimize the functions of backupgroups.

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 sameinterval for sending VRRP packets, which prevents multiple backup routers from beingswitched to master routers simultaneously in one VRRP backup group.

l By configuring the preemption mode and preemption delay time of the router in the backupgroup, 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 virtualIP address to check the network connectivity.

l By prohibiting the system from checking number of hops in VRRP packets, you canimprove the compatibility of Huawei routers with different vendors' routers.


Before adjusting and optimizing VRRP, complete the following tasks:





Issue 03 (2010-03-31)


l Configuring network layer attributes for interfaces to connect to the network


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 AdvertisingMessages

Context

The master router sends VRRP advertisement packets at intervals to other backup routers. If thebackup routers do not receive VRRP advertising messages when the timer times out, the backuprouter with the highest priority becomes the master router automatically.

Do as follows on the router to adjust the interval for sending VRRP advertisement packets:


1. Run:system-view




3. Run:vrrp vrid virtual-router-id timer advertise advertise-interval

The interval for sending VRRP advertisement packets is configured.

By default, the interval for sending VRRP advertisement packets is 1 second. Whenmultiple backup groups exist, sending VRRP advertisement packets at very shortintervals may lead to frequent VRRP switchover. In this case, you can increase theinterval.

----End



4-39

4.10.3 Configuring the Preemption Delay Time of Backup GroupRouters

ContextDo as follows on the VRRP backup router of which the latency of preemption needs to beadjusted:


1. Run:system-view


interface interface-type interface-number


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, indicatingimmediate preemption. In immediate preemption mode, the backup router becomesthe new master router when its priority is higher than that of the current masterrouter. The original master router becomes a backup router. After the preemption delayperiod is set, the backup router is delayed to preempt the master router.

Run the vrrp vrid virtual-router-id preempt-mode disable command to configurerouters in the backup group with the non-preemption mode. In the non-preemptionmode, 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 higherpriorities later.

After the IP address owner recovers from a fault, it switches to be the master routerimmediately in spite of the preemption delay. The preemption delay refers to a delayperiod for the backup router to be switched to be the master router. The preemptiondelay is unavailable for the IP address owner. For the VRRP backup group that needsto support the preemption delay, the master virtual router cannot be configured as theIP address owner.

Run the undo vrrp vrid virtual-router-id preempt-mode command to restore thedefault preemption mode.

NOTEOn each router to be configured with a delay mode in a VRRP backup group, it is recommendedto configure backup routers with the immediate preemption mode (whose delay time is 0seconds) and configure the master router with the preemption mode (whose delay time isspecified). Configuring the delay time for the master router can ensure that the original primarylink has enough time to restore and work stably, and then switch back. At the same time, thebackup link works normally. If the data is switched back to the original primary link, theapplication is not affected.

----End




Issue 03 (2010-03-31)

4.10.4 Enabling the Reachability Test of the Virtual IP Address

ContextIn 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 thatserves as the default gateway.

Do as follows on the router that needs to be enabled with a reachable virtual IP address:


1. Run:system-view


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 packetsto the virtual IP address of this backup group.

Pinging a virtual address may cause ICMP attacks. To prevent this, you can run theundo vrrp virtual-ip ping enable command to disable the function of testingreachability of a virtual IP address.

----End

4.10.5 Disabling a Router from Checking Number of Hops in VRRPPackets

ContextDefined in RFC 3768, the system detects number of hops in received VRRP packets. The packetswhose number of hops is not 255 are discarded.

In certain networking environments where Huawei devices and non-Huawei devices worktogether, checking the number of hops in VRRP packets may result in discarding VRRP packetsincorrectly. 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:

Procedurel For VRRP for IPv4,

1. Run:system-view




4-41



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-checkttl command to enable the router to check TTLs in VRRP packets.

----End

4.10.6 Configuring the Timeout Time of Sending Gratuitous ARPPackets by the Master router

ContextDo as follows on the router to send gratuitous ARP packets:

Procedure



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 masterrouter sends a gratuitous ARP packet every 300 seconds (5 minutes).

Run the undo vrrp gratuitous-arp timeout command in the system view to restore the defaulttimeout period of sending gratuitous ARP packets.

Run the vrrp gratuitous-arp timeout disable command in the system view to disable the masterrouter to send gratuitous ARP packets.

----End


PrerequisiteThe configurations of Adjusting and Optimizing VRRP function are complete.



----End




Issue 03 (2010-03-31)

ExampleRun 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 theVRRP advertisement packet is modified as 20 seconds. The default interval is 1 second.<HUAWEI> display vrrp GigabitEthernet1/0/0 | Virtual Router 1 State : Master Virtual IP : 100.1.1.111 PriorityRun : 120 PriorityConfig : 120 MasterPriority : 120 Preempt : YES Delay Time : 0 TimerRun : 20 TimerConfig : 20 Auth Type : NONE Virtual Mac : 0000-5e00-0101 Check TTL : YES Config type : normal-vrrpConfig track link-bfd down-number : 0

4.11 Configuring mVRRP Backup GroupsThis section describes how to create a VRRP backup group and configure VRRP members andmember interfaces bind to mVRRP.

4.11.1 Establishing the Configuration Task4.11.2 Configuring mVRRP Backup Group4.11.3 (Optional) Configuring VRRP Backup Group Members and Binding them to the mVRRPBackup Group4.11.4 (Optional) Binding Member Interface and Management Backup Group4.11.5 (Optional) Binding the PW to the mVRRP Backup Group Through VPLS4.11.6 Checking the Configuration


Application Environment

Figure 4-4 mVRRP determines the dual-homing of the master and slave routers

NPE1

NPE2

UPE

mVRRP



4-43

As shown in Figure 4-4, when the convergence layer of the Metro Ethernet (ME) dual NPEsare deployed for high reliability. The master and standby routers are determined by mVRRPbetween NPEs.

The mVRRP backup group is actually the ordinary VRRP backup group. The difference is thatthe mVRRP backup group can be bound to other backup groups of different services. The statusof 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 backupgroup cannot be bound to other management backup groups.

According to different applications, the binding relationship of the mVRRP backup group is asfollows:

l The VRRP backup group is bound to the mVRRP backup group: UPEs are dual-homed toNPEs. VRRP is run between NPEs. The master NPE and backup NPE are determined bythe configured priority of VRRP. Multiple VRRP backup groups run between NPEs withdifferent services.If each VRRP backup group needs to maintain its own state machine, a huge number ofVRRP packets exist among NPEs. To simplify the process and decrease occupancy ofbandwidth, you can set one VRRP backup group as the mVRRP backup group. Otherbackup group members are bound to the mVRRP backup group. The master and slaverouters are determined directly by the binding relationship.

l The service interfaces are bound to the mVRRP backup group. If the UPEs are dual-homedto NPEs through two physical links. You can bind the member interfaces to the mVRRPbackup 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, theUPEs are dual-homed to NPEs through two PWs. Then, you can bind the PW and themVRRP backup group to determine the master PW and the slave PW.

Pre-configuration TasksBefore configuring mVRRP, complete the following tasks:

l Configuring physical parameters of an interface

l Configuring link attributes of interfaces

l Configuring attributes of network layer of interfaces for connectivity

Data PreparationTo 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 groupmembers

3 Priority of the mVRRP

4 Number of the member interface




Issue 03 (2010-03-31)

No. Data

5 PW peer IP address

4.11.2 Configuring mVRRP Backup Group

ContextDo as follows on each router of an mVRRP backup group:

Procedure






A backup group is created and a virtual IP address is assigned to the backup group.


The priority of the VRRP backup group is configured.

Step 5 Run:admin-vrrp vrid virtual-router-id

This VRRP backup group is configured as an mVRRP backup group.

----End

4.11.3 (Optional) Configuring VRRP Backup Group Members andBinding them to the mVRRP Backup Group

ContextDo as follows on each router on which the VRRP backup group members need to be bound toan mVRRP backup group.

Procedure





4-45

Step 2 Run:interface interface-type interface-number[.subinterface-number ]

The interface view of a VRRP member is displayed.


A backup group is created with a virtual IP address.

The status of the VRRP backup group member is determined by the mVRRP backup group.Therefore, the VRRP group member needs not a priority.

Step 4 Run:vrrp vrid virtual-router-id1 track admin-vrrp interface interface-type interface-number [ .subinterface-number ] vrid virtual-router-id2

The VRRP backup group member is bound to the mVRRP backup group.

After the VRRP backup group member is bound to the mVRRP backup group, the state machineof the VRRP backup group member becomes dependent. That is, the VRRP backup groupmember deletes the protocol timer, and no longer sends or receives packets, and implements itsstate machine by directly copying the status of the mVRRP backup group. The backup membercan be bound to only one mVRRP.

----End

4.11.4 (Optional) Binding Member Interface and ManagementBackup Group

Context

Do as follows on the routers that need to bind the member interface to the mVRRP backup group.

Procedure



Step 2 Run:interface interface-type interface-number[.subinterface-number ]

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




Issue 03 (2010-03-31)

4.11.5 (Optional) Binding the PW to the mVRRP Backup GroupThrough VPLS

Context

Do as follows on the routers that need to bind the PW to the mVRRP backup group.

Procedure



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 HUAWEINetEngine80E/40E Router Configuration Guide - VPN.

----End


PrerequisiteThe configurations of the mVRRP backup groups function are complete.

Procedurel Run the display vrrp binding admin-vrrp [ interface interface-type interface-number ]

[ vrid virtual-router-id ] command to check all binding information about the mVRRPbackup 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 mVRRPbackup group and the VRRP backup group members.

l Run the display vrrp binding admin-vrrp [ interface interface-type1 interface-number1 ] [ vrid virtual-router-id ] member-interface [ interface interface-type2



4-47

interface-number2 ] command to check the binding between the mVRRP backup groupand the member interface members.

l Run the following commands to check the binding between the mVRRP backup group andthe PW members.

– display vrrp binding admin-vrrp [ interface interface-type1 interface-number1 ][ vrid virtual-router-id ] member-pw

– display vrrp binding admin-vrrp [ interface interface-type1 interface-number1 ][ vrid virtual-router-id ] member-pw vc interface interface-type2 interface-number2

– display vrrp binding admin-vrrp [ interface interface-type1 interface-number1 ][ vrid virtual-router-id ] member-pw vsi vsi-name peer ip-address [ negotiation-vc-id vc-id1 ]

– display vrrp binding admin-vrrp [ interface interface-type1 interface-number1 ][ 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 backupgroups in the current configuration.

----End

Example

After the configuration, you can run the display vrrp binding admin-vrrp command to viewall binding information about the VRRP backup group member, interface member, and PWmember.

<HUAWEI> display vrrp binding admin-vrrpInterface: 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 Maintaining VRRP

4.12.1 Monitoring the VRRP Running

4.12.1 Monitoring the VRRP Running

Context

In routine maintenance, you can run the following command in any view to display the runningstatus of VRRP.


[ brief ] command in any view to check the current running status and parameters of VRRP.

----End




Issue 03 (2010-03-31)

4.13 Configuration ExamplesThis section describes how to debug VRRP.

4.13.1 Example for Configuring VRRP in Master/Backup Mode

4.13.2 Example for Configuring VRRP in Load Balancing Mode

4.13.3 Example for Configuring the Multi-Instance VRRP

4.13.4 Example for Configuring VRRP Fast Switchover

4.13.5 Example for Configuring VRRP Fast Switchover (Using BFD Sampling)

4.13.6 Example for Configuring Ignorance of the Down of an Interface Where the mVRRPBackup Group Is Configured

4.13.7 Example for Configuring VRRP on VLANIF Interfaces

4.13.1 Example for Configuring VRRP in Master/Backup Mode

Networking RequirementsAs 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 forHost A.

l Normally, Router A serves as the gateway. When Router A fails, Router B serves as thegateway.

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

HostB20.1.1.100/24

GE2/0/010.1.1.2/24

RouterBBackup

POS1/0/0192.168.2.1/24

POS2/0/0192.168.2.2/24

Eth3/0/020.1.1.1/24

RouterC

POS1/0/0192.168.1.2/24

POS1/0/0192.168.1.1/24

RouterAMaster

GE2/0/010.1.1.1/24

Backup group 1Virtual IP Address:10.1.1.111

Ethernet

HostA10.1.1.100/24



4-49


1. Create the backup group 1 on the GE 2/0/0 on Router A and configure Router A with thehighest priority in the backup group to be the master router. Configure the preemptionmode.

2. Create backup group 1 on the GE 2/0/0 interface on Router B and use the default priority.


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 Bwith 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 configurethe priority of Router A in this group with 120 (as the master router).

<RouterA> system-view[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

# On Router B, configure the IP address of the interface, create backup group 1 and configurethe priority of Router B in this group with the default value (as the backup router).

<RouterB> system-view[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-GigabitEthernet2/0/0] quit

Step 3 Verify the configuration.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 Ais Master. Running the display vrrp command on Router B, you can view that the RouterB is Backup.




Issue 03 (2010-03-31)

<RouterA> display vrrp GigabitEthernet2/0/0 | Virtual Router 1 state : Master Virtual IP : 10.1.1.111 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<RouterB> display vrrp GigabitEthernet2/0/0 | Virtual Router 1 state : Backup Virtual IP : 10.1.1.111 PriorityRun : 100 PriorityConfig : 100 MasterPriority : 120 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0101 Check TTL : YES Config type : normal-vrrpRunning the display ip routing-table command on Router A and Router B, you can view adirect route with the destination address being the virtual IP address on Router A, and anOSPF route to the same destination on Router B.The displays on Router A and Router B are as follows.<RouterA> display ip routing-tableRoute Flags: R - relied, D - download to fib------------------------------------------------------------------------------Routing Tables: Public Destinations : 10 Routes : 10Destination/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 10.1.1.111/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 127.0.0.0/8 Direct 0 0 D 127.0.0.1 InLoopBack0 127.0.0.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 192.168.1.0/24 Direct 0 0 D 192.168.1.1 Pos1/0/0 192.168.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 192.168.1.2/32 Direct 0 0 D 192.168.1.2 Pos1/0/0 192.168.2.0/24 OSPF 10 2 D 10.1.1.2 GigabitEthernet2/0/0<RouterB> display ip routing-tableRoute Flags: R - relied, D - download to fib------------------------------------------------------------------------------Routing Tables: Public Destinations : 10 Routes : 10Destination/Mask Proto Pre Cost Flags NextHop Interface 10.1.1.0/24 Direct 0 0 D 10.1.1.2 GigabitEthernet2/0/0 10.1.1.2/32 Direct 0 0 D 127.0.0.1 InLoopBack0 10.1.1.111/32 OSPF 10 2 D 10.1.1.1 GigabitEthernet2/0/0 20.1.1.0/24 OSPF 10 2 D 192.168.2.2 Pos1/0/0 127.0.0.0/8 Direct 0 0 D 127.0.0.1 InLoopBack0 127.0.0.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 192.168.1.0/24 OSPF 10 2 D 10.1.1.1 GigabitEthernet2/0/0 192.168.2.0/24 Direct 0 0 D 192.168.2.1 Pos1/0/0 192.168.2.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 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.



4-51

To simulate the election of the master router when Router A fails, run the shutdowncommand on the GE 2/0/0 on Router A.Running the display vrrp command on Router B to view the VRRP status, you can viewthat Router B is in the Master state. The command output is as follows:<RouterB> display vrrpGigabitEthernet2/0/0 | Virtual Router 1 state : Master Virtual IP : 10.1.1.111 PriorityRun : 100 PriorityConfig : 100 MasterPriority : 100 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0101 Check TTL : YES Config type : normal-vrrp

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 vrrpcommand to view VRRP status 20 seconds after GE 2/0/0 being Up. You can view that RouterA restores to be the master router.

----End


# sysname RouterA#interface GigabitEthernet2/0/0 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

l Configuration file of Router B# sysname RouterB#interface GigabitEthernet2/0/0 undo shutdown ip address 10.1.1.2 255.255.255.0 vrrp vrid 1 virtual-ip 10.1.1.111#interface Pos1/0/0 link-protocol ppp undo shutdown ip address 192.168.2.1 255.255.255.0#




Issue 03 (2010-03-31)

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 clock master ip address 192.168.1.2 255.255.255.0#interface Pos2/0/0 link-protocol ppp undo shutdown clock master 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.13.2 Example for Configuring VRRP in Load Balancing Mode

Networking RequirementsAs shown in Figure 4-6.

l Router A serves as the master router of group 1 and the backup router of group 2.

l Router B serves as the master router of backup group 2 and the backup router of group 1.

l Host A in the internal network takes backup group 1 as its gateway and Host C takes backupgroup 2 as its gateway to share the traffic and backup each other.



4-53

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

20.1.1.100/24

RouterBgroup 1:Backup

group 2:Master

Backup group 2Virtual IP Address:

10.1.1.112

Backup group 1Virtual IP Address:

10.1.1.111

Ethernet

HostA10.1.1.100/24

GE2/0/010.1.1.2/24

POS1/0/0192.168.2.1/24

POS2/0/0192.168.2.2/24

Eth3/0/020.1.1.1/24

HostB

RouterC

POS1/0/0192.168.1.2/24

POS1/0/0192.168.1.1/24

GE2/0/010.1.1.1/24

RouterAgroup 1:Master group 2:Backup

HostC10.1.1.101/24


1. Create two backup groups on the GE 2/0/0 interface on Router A. Router A is the masterrouter 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 backuprouter in the backup group 1 and the master in group 2.




ProcedureStep 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 group1, the default gateway of Host B as 20.1.1.1, and the default gateway of Host C as the virtual IPaddress 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 group 1 and configurethe priority of Router A in this group as 120 (as the master router). Create backup group 2 and




Issue 03 (2010-03-31)

configure the priority of Router A in this group with the default value 100 (as the backuprouter).

<RouterA> system-view[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 2 virtual-ip 10.1.1.112[RouterA-GigabitEthernet2/0/0] quit

# On Router B, configure the IP address of the interface, create backup group 1 and configurethe priority of Router B in this group with the default value 100 (as the backup router). Createbackup group 2, and configure the priority of Router B in this group with 120 (as the masterrouter).

<RouterB> system-view[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-GigabitEthernet2/0/0] vrrp vrid 2 virtual-ip 10.1.1.112[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 RouterA 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) 30 hops max,40 bytes packet 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) 30 hops max,40 bytes packet 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 themaster router in backup group 1 and the backup router in backup group 2.

<RouterA> display vrrp GigabitEthernet2/0/0 | Virtual Router 1 state : Master Virtual IP : 10.1.1.111 PriorityRun : 120 PriorityConfig : 120 MasterPriority : 120 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0101 Check TTL : YES Config type : normal-vrrp GigabitEthernet2/0/0 | Virtual Router 2 state : Backup Virtual IP : 10.1.1.112 PriorityRun : 100 PriorityConfig : 100



4-55

MasterPriority : 120 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0102 Check TTL : YES Config type : normal-vrrp

----End


# sysname RouterA#interface GigabitEthernet2/0/0 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 2 virtual-ip 10.1.1.112#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

l Configuration file of Router B# sysname RouterB#interface GigabitEthernet2/0/0 undo shutdown ip address 10.1.1.2 255.255.255.0 vrrp vrid 1 virtual-ip 10.1.1.111 vrrp vrid 2 virtual-ip 10.1.1.112 vrrp vrid 2 priority 120#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




Issue 03 (2010-03-31)

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.13.3 Example for Configuring the Multi-Instance VRRP

Networking RequirementsAs shown in Figure 4-7, there are two VPN networks: VPN RED and VPN BLUE. ConfigureMPLS 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 form backup group 1 and backup group 2. PE-Aserves as the master device, and PE-B serves as the backup device.

l CE-A uses the virtual IP address of VRRP backup group 1 as itsdefault gateway.

l CE-B uses the virtual IP address of VRRP backup group 2 as itsdefault gateway.

VPN instance thatCE belongs to

l CE-A and CE-D belong to the VPN-BLUE instances.

l CE-B and CE-C belong to the VPN-RED instances.

VPN instance thatthe interface on PEbelongs to

l The GE 1/0/0 interfaces on PE-A 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-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 protocoland MPLS

l Configure the OSPF and enable the MPLS forwarding.

l Configure default routes on CE-A and CE-B to exchange VPN routinginformation with PE-A and PE-B.

l Establish BGP peer relationship among PE-A, PE-B and PE-C totransmit all VPN routes.



4-57

Figure 4-7 Networking diagram of configuring VRRP multi-instance

Loopback1

Backup group1

Loopback1

Loopback1

Loopback1

VPN BLUE

VPN RED

GE1/0/0CE-A

GE1/0/0

GE2/0/0 POS3/0/0

POS3/0/0GE2/0/0

GE1/0/0

CE-D

PE-C

POS3/0/0

POS1/0/0

POS2/0/0

POS3/0/0GE2/0/0

GE1/0/0

GE1/0/0

CE-B

VPN BLUE

PublicNetwork

for VPN BLUE

PE-B

PE-A

Backup group2for VPN RED

HostA

HostB

HostD

GE1/0/0

GE1/0/0

CE-C

VPN RED

HostC

P

router Interface IP Address VPN-InstanceP 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-BLUEGE 2/0/0 20.1.1.1/24 VPN-REDPOS 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-BLUEGE 2/0/0 20.1.1.2/24 VPN-REDPOS 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-REDGE 2/0/0 20.2.1.1/24 VPN-BLUEPOS 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 -




Issue 03 (2010-03-31)


1. Create the backup group 1 and the backup group 2 on PE-A and PE-B.2. PE-A is the master router in the backup group 1 and PE-B is the backup router.3. PE-A is the backup router in the backup group 2 and PE-B is the master router.4. PE-A and PE-B share the traffic and back up each other.




Procedure

Step 1 Configure OSPF between PEs, or between PEs and Ps to implement the interconnection of thebackbone networks (omitted).

Step 2 Configure MPLS basic functions and MPLS LDP on the MPLS backbone network and establishLDP 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 VPNConfiguration" in the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN. Youcan 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 (asthe 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 defaultvalue (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 defaultvalue (as the backup router).

<PE-B> system-view[PE-B] interface gigabitethernet 1/0/0



4-59

[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 (asthe 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 andPE-B, you can view a route with the destination address being the virtual IP address in the VPNrouting 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-BLUERoute Flags: R - relied, D - download to fib------------------------------------------------------------------------------Routing Tables: VPN-BLUE Destinations : 3 Routes : 3Destination/Mask Proto Pre Cost Flags NextHop Interface 10.1.1.0/24 Direct 0 0 D 10.1.1.2 GigabitEthernet1/0/0 10.1.1.1/32 Direct 0 0 D 10.1.1.1 InLoopBack0 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

You can ping through the virtual IP address 10.1.1.111.

----End

Configuration Filesl Configure file of PE-A

# sysname PE-A#ip vpn-instance VPN-BLUE route-distinguisher 100:1 vpn-target 100:1 export-extcommunity vpn-target 100:1 import-extcommunity#ip vpn-instance VPN-RED route-distinguisher 200:1 vpn-target 200:1 export-extcommunity vpn-target 200:1 import-extcommunity# mpls lsr-id 1.1.1.1 mpls#mpls ldp#interface GigabitEthernet1/0/0 undo shutdown ip binding vpn-instance VPN-BLUE ip address 10.1.1.1 255.255.255.0 vrrp vrid 1 virtual-ip 10.1.1.111 vrrp vrid 1 priority 120#interface GigabitEthernet2/0/0 undo shutdown




Issue 03 (2010-03-31)

ip binding vpn-instance VPN-RED ip address 20.1.1.1 255.255.255.0 vrrp vrid 2 virtual-ip 20.1.1.111#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 route-distinguisher 100:1 vpn-target 100:1 export-extcommunity vpn-target 100:1 import-extcommunity#ip vpn-instance VPN-RED route-distinguisher 200:1 vpn-target 200:1 export-extcommunity vpn-target 200:1 import-extcommunity# mpls lsr-id 2.2.2.2 mpls#mpls ldp#interface GigabitEthernet1/0/0 undo shutdown ip binding vpn-instance VPN-BLUE ip address 10.1.1.2 255.255.255.0 vrrp vrid 1 virtual-ip 10.1.1.111#interface GigabitEthernet2/0/0



4-61

undo shutdown ip binding vpn-instance VPN-RED ip address 20.1.1.2 255.255.255.0 vrrp vrid 2 virtual-ip 20.1.1.111 vrrp vrid 2 priority 120#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 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.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.13.4 Example for Configuring VRRP Fast Switchover

Networking RequirementsAs shown in Figure 4-8, Router A, Router B, Switch A, Switch B and Universal MediumGateway (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 Bserves as the backup router.

When Router A fails or the GE link between Router A and Router B fails, VRRP switchovershould be performed in less than one second to implement fast convergence in NGN.




Issue 03 (2010-03-31)

Figure 4-8 Networking diagram of configuring VRRP fast switchover

Backup group 10Virtual IP address: 10.1.1.3/24

RouterA RouterB

SwitchA SwitchB

UMG

VLAN

GE2/0/010.1.1.1/24

POS1/0/0192.168.0.2/24

GE2/0/010.1.1.2/24

POS1/0/0192.168.0.1/24

BackboneNetwork


1. Configure BFD sessions on GE interfaces on Router A and Router B to monitor the linkRouter 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, thepriority 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 POSinterface that is directly connected to Router A and Router B in Step 1. This configuration is not coveredin this example.


l The local and remote BFD session identifier



Procedure

Step 1 Configure BFD.

# Configure a BFD session on Router A.



4-63

<RouterA> system-view[RouterA] bfd[RouterA-bfd] quit[RouterA] interface gigabitethernet 2/0/0[RouterA-GigabitEthernet2/0/0] ip address 10.1.1.1 24[RouterA-GigabitEthernet2/0/0] bfd[RouterA-GigabitEthernet2/0/0] 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> system-view[RouterB] bfd[RouterB-bfd] quit[RouterB] interface gigabitethernet2/0/0[RouterB-GigabitEthernet2/0/0] ip address 10.1.1.2 24[RouterB-GigabitEthernet2/0/0] bfd[RouterB-GigabitEthernet2/0/0] quit[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 BFDsessions 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 as160.[RouterA] interface gigabitethernet 2/0/0[RouterA-GigabitEthernet2/0/0] vrrp vrid 10 virtual-ip 10.1.1.3[RouterA-GigabitEthernet2/0/0] vrrp vrid 10 priority 160[RouterA-GigabitEthernet2/0/0] quit

# Create a backup group 10 and configure Router B to be the backup router with the priority as140.[RouterB] interface gigabitethernet2/0/0[RouterB-GigabitEthernet2/0/0] vrrp vrid 10 virtual-ip 10.1.1.3[RouterB-GigabitEthernet2/0/0] vrrp vrid 10 priority 140

# Track the BFD session on the backup router. If the BFD session is Down, the priority of RouterB increases by 40.[RouterB-GigabitEthernet2/0/0] vrrp vrid 10 track bfd-session 2 increased 40[RouterB-GigabitEthernet2/0/0] quit

Running the display vrrpcommand on Route A or Router B, you can view that Router A is themaster and Router B is the backup. You can also view the tracked BFD session and its status onRouter B.




Issue 03 (2010-03-31)

[RouterA] display vrrp GigabitEthernet2/0/0 | Virtual Router 10 state : Master Virtual IP : 10.1.1.3 PriorityRun : 160 PriorityConfig : 160 MasterPriority : 160 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0110 Check TTL : YES Config type : normal-vrrp[RouterB] display vrrp GigabitEthernet2/0/0 | Virtual Router 10 state : Backup Virtual IP : 10.1.1.3 PriorityRun : 140 PriorityConfig : 140 MasterPriority : 160 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0110 Check TTL : YES Config type : normal-vrrp Track BFD : 2 Priority increased : 40 BFD-Session State : UP


# Run the shutdowncommand on GE 2/0/0 on Router A to simulate a link fault.

[RouterA] interface gigabitethernet 2/0/0[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 Achanges to Initialize.

[RouterA] display vrrp GigabitEthernet2/0/0 | Virtual Router 10 state : Initialize Virtual IP : 10.1.1.3 PriorityRun : 160 PriorityConfig : 160 MasterPriority : 0 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0110 Check TTL : YES Config type : normal-vrrp

Running the display vrrp command on Router B, you can view that Router B becomes themaster router and the BFD session when it is Down.

[RouterB] display vrrp



4-65

GigabitEthernet2/0/0 | Virtual Router 10 state : Master Virtual IP : 10.1.1.3 PriorityRun : 180 PriorityConfig : 140 MasterPriority : 180 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0110 Check TTL : YES Config type : normal-vrrp Track BFD : 2 Priority increased : 40 BFD-Session State : DOWN

----End


# sysname RouterA# bfd#interface GigabitEthernet2/0/0 undo shutdownip address 10.1.1.1 255.255.255.0 vrrp vrid 10 virtual-ip 10.1.1.3 vrrp vrid 10 priority 160#bfd atob bind peer-ip 10.1.1.2 interface gigabitethernet2/0/0 discriminator local 1 discriminator remote 2 min-tx-interval 50 min-rx-interval 50 commit#return

l Configuration file of Router B# sysname RouterB#bfd#interface GigabitEthernet2/0/0 undo shutdownip address 10.1.1.2 255.255.255.0 vrrp vrid 10 virtual-ip 10.1.1.3 vrrp vrid 10 priority 140 vrrp vrid 10 track bfd-session 2 increased 40#bfd btoa bind peer-ip 10.1.1.1 interface gigabitethernet2/0/0 discriminator local 2 discriminator remote 1 min-tx-interval 50 min-rx-interval 50 commit#Return




Issue 03 (2010-03-31)

4.13.5 Example for Configuring VRRP Fast Switchover (Using BFDSampling)

Networking RequirementsAs shown in Figure 4-9, the CE connects to the sub-interface for QinQ VLAN tag terminationof the NPE across the VPLS convergence network.

On the NPE, the mVRRP backup group and the service VRRP backup group are configured andthe mVRRP backup group implements master/backup fast switchover by tracking the BFDsession. Between NPE1 and NPE2, the peer BFD session is established.

In this configuration example, the following restrictions are imposed on the network:l The VPLS convergence network belongs to another operator, so the link BFD session

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 theVPLS convergence network.

l NPE1 or NPE2 establishes four link BFD sessions with four CEs respectively through GE1/0/1. The mVRRP backup group is responsible for tracking the status of the four BFDsessions concurrently. When two or more link BFD sessions go Down, the mVRRP backupgroup performs master/backup fast switchover.



4-67

Figure 4-9 Typical networking of VRRP fast switchover (using BFD sampling)

CE4

CE1

CE2

CE3

NPE1

NPE2

MPLS/IP Core

#interface GigabitEthernet1/0/1.1 ip address 10.1.1.254 255.255.255.0 vrrp vrid 10 virtual-ip 10.1.1.1 admin-vrrp vrid 10#interface GigabitEthernet1/0/1.100 ip address 10.100.1.254 255.255.255.0 vrrp vrid 100 virtual-ip 10.100.1.200#interface GigabitEthernet1/0/1.101 ip address 10.101.1.254 255.255.255.0 vrrp vrid 101 virtual-ip 10.101.1.200#interface GigabitEthernet1/0/1.102 ip address 10.102.1.254 255.255.255.0 vrrp vrid 102 virtual-ip 10.102.1.200#interface GigabitEthernet1/0/1.103 ip address 10.103.1.254 255.255.255.0 vrrp vrid 103 virtual-ip 10.103.1.200#

#interface GigabitEthernet1/0/1.1 ip address 10.1.1.253 255.255.255.0 vrrp vrid 10 virtual-ip 10.1.1.1 admin-vrrp vrid 10#interface GigabitEthernet1/0/1.100 ip address 10.100.1.253 255.255.255.0 vrrp vrid 100 virtual-ip 10.100.1.200#interface GigabitEthernet1/0/1.101 ip address 10.101.1.253 255.255.255.0 vrrp vrid 101 virtual-ip 10.101.1.200#interface GigabitEthernet1/0/1.102 ip address 10.102.1.253 255.255.255.0 vrrp vrid 102 virtual-ip 10.102.1.200#interface GigabitEthernet1/0/1.103 ip address 10.103.1.253 255.255.255.0 vrrp vrid 103 virtual-ip 10.103.1.200#

PeerBFD

PE1

PE2

Link BFD

AccessAggregation

VPLS Network Core





PE3





Issue 03 (2010-03-31)

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 backupgroup 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.


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 proceduresof the BFD function of the CE as shown in Figure 4-9 and the VPLS convergence network, refer to theHUAWEI NetEngine80E/40E Router Configuration Guide - Reliability and Configuration Guide - VPN.

# Configure NPE1.

<HUAWEI> system-view[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[NPE1] interface gigabitethernet1/0/1.100[NPE1-GigabitEthernet1/0/1.100] control-vid 100 qinq-termination[NPE1-GigabitEthernet1/0/1.100] qinq termination pe-vid 10 ce-vid 101 to 200[NPE1-GigabitEthernet1/0/1.100] ip address 10.100.1.254 24[NPE1-GigabitEthernet1/0/1.100] arp broadcast enable[NPE1-GigabitEthernet1/0/1.100] quit[NPE1] interface gigabitethernet1/0/1.101[NPE1-GigabitEthernet1/0/1.101] control-vid 101 qinq-termination[NPE1-GigabitEthernet1/0/1.101] qinq termination pe-vid 10 ce-vid 201 to 300[NPE1-GigabitEthernet1/0/1.101] ip address 10.101.1.254 24[NPE1-GigabitEthernet1/0/1.101] arp broadcast enable[NPE1-GigabitEthernet1/0/1.101] quit[NPE1] interface gigabitethernet1/0/1.102[NPE1-GigabitEthernet1/0/1.102] control-vid 102 qinq-termination[NPE1-GigabitEthernet1/0/1.102] qinq termination pe-vid 10 ce-vid 301 to 400[NPE1-GigabitEthernet1/0/1.102] ip address 10.102.1.254 24[NPE1-GigabitEthernet1/0/1.102] arp broadcast enable[NPE1-GigabitEthernet1/0/1.102] quit[NPE1] interface gigabitethernet1/0/1.103[NPE1-GigabitEthernet1/0/1.103] control-vid 103 qinq-termination[NPE1-GigabitEthernet1/0/1.103] qinq termination pe-vid 10 ce-vid 401 to 500[NPE1-GigabitEthernet1/0/1.103] ip address 10.103.1.254 24[NPE1-GigabitEthernet1/0/1.103] arp broadcast enable[NPE1-GigabitEthernet1/0/1.103] quit



4-69

# Configure NPE2.<HUAWEI> system-view[HUAWEI] sysname NPE2[NPE2] interface gigabitethernet1/0/1[NPE2-GigabitEthernet1/0/1] mode user-termination[NPE2-GigabitEthernet1/0/1] undo shutdown[NPE2-GigabitEthernet1/0/1] quit[NPE2] interface gigabitethernet1/0/1.1[NPE2-GigabitEthernet1/0/1.1] control-vid 1 qinq-termination[NPE2-GigabitEthernet1/0/1.1] qinq termination pe-vid 10 ce-vid 1 to 100[NPE2-GigabitEthernet1/0/1.1] ip address 10.1.1.253 24[NPE2-GigabitEthernet1/0/1.1] arp broadcast enable[NPE2-GigabitEthernet1/0/1.1] quit[NPE2] interface gigabitethernet1/0/1.100[NPE2-GigabitEthernet1/0/1.100] control-vid 100 qinq-termination[NPE2-GigabitEthernet1/0/1.100] qinq termination pe-vid 10 ce-vid 101 to 200[NPE2-GigabitEthernet1/0/1.100] ip address 10.100.1.253 24[NPE2-GigabitEthernet1/0/1.100] arp broadcast enable[NPE2-GigabitEthernet1/0/1.100] quit[NPE2] interface gigabitethernet1/0/1.101[NPE2-GigabitEthernet1/0/1.101] control-vid 101 qinq-termination[NPE2-GigabitEthernet1/0/1.101] qinq termination pe-vid 10 ce-vid 201 to 300[NPE2-GigabitEthernet1/0/1.101] ip address 10.101.1.253 24[NPE2-GigabitEthernet1/0/1.101] arp broadcast enable[NPE2-GigabitEthernet1/0/1.101] quit[NPE2] interface gigabitethernet1/0/1.102[NPE2-GigabitEthernet1/0/1.102] control-vid 102 qinq-termination[NPE2-GigabitEthernet1/0/1.102] qinq termination pe-vid 10 ce-vid 301 to 400[NPE2-GigabitEthernet1/0/1.102] ip address 10.102.1.253 24[NPE2-GigabitEthernet1/0/1.102] arp broadcast enable[NPE2-GigabitEthernet1/0/1.102] quit[NPE2] interface gigabitethernet1/0/1.103[NPE2-GigabitEthernet1/0/1.103] control-vid 103 qinq-termination[NPE2-GigabitEthernet1/0/1.103] qinq termination pe-vid 10 ce-vid 401 to 500[NPE2-GigabitEthernet1/0/1.103] ip address 10.103.1.253 24[NPE2-GigabitEthernet1/0/1.103] arp broadcast enable[NPE2-GigabitEthernet1/0/1.103] quit

NOTE

After the IP address is assigned to a sub-interface for QinQ VLAN tag termination, it is recommended torun the arp broadcast enable command. Otherwise, the sub-interfaces for QinQ VLAN tag terminationfail to ping through each other.

# After the configuration, the sub-interfaces for QinQ VLAN tag termination in the same networksegment 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 NPE1and NPE2 as an example.

The interfaces of NPE1 and NPE2 where the mVRRP backup group is configured can pingthrough each other.[NPE1] ping 10.1.1.253 PING 10.1.1.253: 56 data bytes, press CTRL_C to break Reply from 10.1.1.253: bytes=56 Sequence=1 ttl=255 time=160 ms Reply from 10.1.1.253: bytes=56 Sequence=2 ttl=255 time=90 ms Reply from 10.1.1.253: bytes=56 Sequence=3 ttl=255 time=160 ms Reply from 10.1.1.253: bytes=56 Sequence=4 ttl=255 time=180 ms Reply from 10.1.1.253: bytes=56 Sequence=5 ttl=255 time=120 ms

--- 10.1.1.253 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 90/142/180 ms

The interfaces of NPE1 and NPE2 where the service VRRP backup group is configured can pingthrough each other.




Issue 03 (2010-03-31)

[NPE1] ping 10.100.1.253 PING 10.100.1.253: 56 data bytes, press CTRL_C to break Reply from 10.100.1.253: bytes=56 Sequence=1 ttl=255 time=90 ms Reply from 10.100.1.253: bytes=56 Sequence=2 ttl=255 time=100 ms Reply from 10.100.1.253: bytes=56 Sequence=3 ttl=255 time=190 ms Reply from 10.100.1.253: bytes=56 Sequence=4 ttl=255 time=100 ms Reply from 10.100.1.253: bytes=56 Sequence=5 ttl=255 time=90 ms


The NPE and the CE in the same network segment can ping through each other. It indicates thatthe link between the NPE and the CE works normally. Take the ping between NPE1 and CE1or between NPE2 and CE1 as an example.[NPE1] ping 10.100.1.1 PING 10.100.1.1: 56 data bytes, press CTRL_C to break Reply from 10.100.1.1: bytes=56 Sequence=1 ttl=255 time=180 ms Reply from 10.100.1.1: bytes=56 Sequence=2 ttl=255 time=160 ms Reply from 10.100.1.1: bytes=56 Sequence=3 ttl=255 time=150 ms Reply from 10.100.1.1: bytes=56 Sequence=4 ttl=255 time=150 ms Reply from 10.100.1.1: bytes=56 Sequence=5 ttl=255 time=120 ms


[NPE2] ping 10.100.1.1PING 10.100.1.1: 56 data bytes, press CTRL_C to break Reply from 10.100.1.1: bytes=56 Sequence=1 ttl=255 time=190 ms Reply from 10.100.1.1: bytes=56 Sequence=2 ttl=255 time=120 ms Reply from 10.100.1.1: bytes=56 Sequence=3 ttl=255 time=130 ms Reply from 10.100.1.1: bytes=56 Sequence=4 ttl=255 time=100 ms Reply from 10.100.1.1: bytes=56 Sequence=5 ttl=255 time=70 ms


Step 2 Configure basic VRRP functions on the sub-interfaces for QinQ VLAN tag termination of NPE1and NPE2.

# On NPE1, configure the mVRRP backup group with VRID being 10 on GE 1/0/1.1 andconfigure the service VRRP backup group on other sub-interfaces.[NPE1] interface gigabitethernet1/0/1.1[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[NPE1-GigabitEthernet1/0/1.1] quit[NPE1] interface gigabitethernet1/0/1.100[NPE1-GigabitEthernet1/0/1.100] qinq vrrp pe-vid 10 ce-vid 101[NPE1-GigabitEthernet1/0/1.100] vrrp vrid 100 virtual-ip 10.100.1.200[NPE1-GigabitEthernet1/0/1.100] quit[NPE1] interface gigabitethernet1/0/1.101[NPE1-GigabitEthernet1/0/1.101] qinq vrrp pe-vid 10 ce-vid 201[NPE1-GigabitEthernet1/0/1.101] vrrp vrid 101 virtual-ip 10.101.1.200[NPE1-GigabitEthernet1/0/1.101] quit[NPE1] interface gigabitethernet1/0/1.102[NPE1-GigabitEthernet1/0/1.102] qinq vrrp pe-vid 10 ce-vid 301[NPE1-GigabitEthernet1/0/1.102] vrrp vrid 102 virtual-ip 10.102.1.200



4-71

[NPE1-GigabitEthernet1/0/1.102] quit[NPE1] interface gigabitethernet1/0/1.103[NPE1-GigabitEthernet1/0/1.103] qinq vrrp pe-vid 10 ce-vid 401[NPE1-GigabitEthernet1/0/1.103] vrrp vrid 103 virtual-ip 10.103.1.200[NPE1-GigabitEthernet1/0/1.103] quit

# On NPE2, configure the mVRRP backup group with VRID being 10 on GE 1/0/1.1 andconfigure the service VRRP backup group on other sub-interfaces.

[NPE2] interface gigabitethernet1/0/1.1[NPE2-GigabitEthernet1/0/1.1] qinq vrrp pe-vid 10 ce-vid 100[NPE2-GigabitEthernet1/0/1.1] vrrp vrid 10 virtual-ip 10.1.1.1[NPE2-GigabitEthernet1/0/1.1] admin-vrrp vrid 10[NPE2-GigabitEthernet1/0/1.1] quit[NPE2] interface gigabitethernet1/0/1.100[NPE2-GigabitEthernet1/0/1.100] qinq vrrp pe-vid 10 ce-vid 101[NPE2-GigabitEthernet1/0/1.100] vrrp vrid 100 virtual-ip 10.100.1.200[NPE2-GigabitEthernet1/0/1.100] quit[NPE2] interface gigabitethernet1/0/1.101[NPE2-GigabitEthernet1/0/1.101] qinq vrrp pe-vid 10 ce-vid 201[NPE2-GigabitEthernet1/0/1.101] vrrp vrid 101 virtual-ip 10.101.1.200[NPE2-GigabitEthernet1/0/1.101] quit[NPE2] interface gigabitethernet1/0/1.102[NPE2-GigabitEthernet1/0/1.102] qinq vrrp pe-vid 10 ce-vid 301[NPE2-GigabitEthernet1/0/1.102] vrrp vrid 102 virtual-ip 10.102.1.200[NPE2-GigabitEthernet1/0/1.102] quit[NPE2] interface gigabitethernet1/0/1.103[NPE2-GigabitEthernet1/0/1.103] qinq vrrp pe-vid 10 ce-vid 401[NPE2-GigabitEthernet1/0/1.103] vrrp vrid 103 virtual-ip 10.103.1.200[NPE2-GigabitEthernet1/0/1.103] quit

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 briefVRID State Interface Type Virtual IP--------------------------------------------------------10 Master GE1/0/1.1 Admin 10.1.1.1100 Master GE1/0/1.100 Normal 10.100.1.200101 Master GE1/0/1.101 Normal 10.101.1.200102 Master GE1/0/1.102 Normal 10.102.1.200103 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.

[NPE2] display vrrp briefVRID State Interface Type Virtual IP--------------------------------------------------------10 Backup GE1/0/1.1 Admin 10.1.1.1100 Backup GE1/0/1.100 Normal 10.100.1.200101 Backup GE1/0/1.101 Normal 10.101.1.200102 Backup GE1/0/1.102 Normal 10.102.1.200103 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] interface gigabitethernet1/0/1.100[NPE1-GigabitEthernet1/0/1.100] vrrp vrid 100 track admin-vrrp interface




Issue 03 (2010-03-31)

gigabitethernet1/0/1.1 vrid 10 unflowdown[NPE1-GigabitEthernet1/0/1.100] quit[NPE1] interface gigabitethernet1/0/1.101[NPE1-GigabitEthernet1/0/1.101] vrrp vrid 101 track admin-vrrp interface gigabitethernet1/0/1.1 vrid 10 unflowdown[NPE1-GigabitEthernet1/0/1.101] quit[NPE1] interface gigabitethernet1/0/1.102[NPE1-GigabitEthernet1/0/1.102] vrrp vrid 102 track admin-vrrp interface gigabitethernet1/0/1.1 vrid 10 unflowdown[NPE1-GigabitEthernet1/0/1.102] quit[NPE1] interface gigabitethernet1/0/1.103[NPE1-GigabitEthernet1/0/1.103] vrrp vrid 103 track admin-vrrp interface gigabitethernet1/0/1.1 vrid 10 unflowdown[NPE1-GigabitEthernet1/0/1.103] quit

# Configure NPE2.

[NPE2] interface gigabitethernet1/0/1.100[NPE2-GigabitEthernet1/0/1.100] vrrp vrid 100 track admin-vrrp interface gigabitethernet1/0/1.1 vrid 10 unflowdown[NPE2-GigabitEthernet1/0/1.100] quit[NPE2] interface gigabitethernet1/0/1.101[NPE2-GigabitEthernet1/0/1.101] vrrp vrid 101 track admin-vrrp interface gigabitethernet1/0/1.1 vrid 10 unflowdown[NPE2-GigabitEthernet1/0/1.101] quit[NPE2] interface gigabitethernet1/0/1.102[NPE2-GigabitEthernet1/0/1.102] vrrp vrid 102 track admin-vrrp interface gigabitethernet1/0/1.1 vrid 10 unflowdown[NPE2-GigabitEthernet1/0/1.102] quit[NPE2] interface gigabitethernet1/0/1.103[NPE2-GigabitEthernet1/0/1.103] vrrp vrid 103 track admin-vrrp interface gigabitethernet1/0/1.1 vrid 10 unflowdown[NPE2-GigabitEthernet1/0/1.103] quit

NOTE

l In this configuration example, using the vrrp vrid track admin-vrrp command, you need to specifythe keyword unflowdown.

l If unspecified, when the status of the mVRRP backup group tracked by the service VRRP backup isBackup, the status of the interface where the service VRRP backup group is configured becomes Flowdown, the status of the service VRRP backup group becomes Initialize, and the status of the link BFDsession becomes Down. When the number of link BFD sessions in the Down state reaches the threshold,the status of the mVRRP backup also becomes Initialize, thus failing to implement master/backupswitchover of the mVRRP backup group.


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, State is Master and Type is Member.

[NPE1] display vrrp briefVRID State Interface Type Virtual IP--------------------------------------------------------10 Master GE1/0/1.1 Admin 10.1.1.1100 Master GE1/0/1.100 Member 10.100.1.200101 Master GE1/0/1.101 Member 10.101.1.200102 Master GE1/0/1.102 Member 10.102.1.200103 Master GE1/0/1.103 Member 10.103.1.200

On NPE2:

l For the VRRP backup group with the VRID being 10, State is Backup and Type is Admin.



4-73

l For the VRRP backup group with the VRID not being 10, State is Backup and Type isMember.

[NPE2] display vrrp briefVRID State Interface Type Virtual IP--------------------------------------------------------10 Backup GE1/0/1.1 Admin 10.1.1.1100 Backup GE1/0/1.100 Member 10.100.1.200101 Backup GE1/0/1.101 Member 10.101.1.200102 Backup GE1/0/1.102 Member 10.102.1.200103 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 theirrespective 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 sessionbetween 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[NPE1] bfd link2 bind peer-ip 10.101.1.1 interface gigabitethernet1/0/1.101 source-ip 10.101.1.254 auto[NPE1-bfd-session-link2] commit[NPE1-bfd-session-link2] quit[NPE1] bfd link3 bind peer-ip 10.102.1.1 interface gigabitethernet1/0/1.102 source-ip 10.102.1.254 auto[NPE1-bfd-session-link3] commit[NPE1-bfd-session-link3] quit[NPE1] bfd link4 bind peer-ip 10.103.1.1 interface gigabitethernet1/0/1.103 source-ip 10.103.1.254 auto[NPE1-bfd-session-link4] commit[NPE1-bfd-session-link4] quit

# 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[NPE2-bfd-session-peer1] commit[NPE2-bfd-session-peer1] quit[NPE2] bfd link1 bind peer-ip 10.100.1.1 interface gigabitethernet1/0/1.100 source-ip 10.100.1.253 auto[NPE2-bfd-session-link1] commit[NPE2-bfd-session-link1] quit[NPE2] bfd link2 bind peer-ip 10.101.1.1 interface gigabitethernet1/0/1.101 source-ip 10.101.1.253 auto[NPE2-bfd-session-link2] commit[NPE2-bfd-session-link2] quit[NPE2] bfd link3 bind peer-ip 10.102.1.1 interface gigabitethernet1/0/1.102 source-ip 10.102.1.253 auto[NPE2-bfd-session-link3] commit[NPE2-bfd-session-link3] quit[NPE2] bfd link4 bind peer-ip 10.103.1.1 interface gigabitethernet1/0/1.103 source-ip 10.103.1.253 auto[NPE2-bfd-session-link4] commit[NPE2-bfd-session-link4] quit




Issue 03 (2010-03-31)

After the previous configurations are finished and the CE is correctly configured with the BFDsession, run the display bfd configuration all command on the NPE. The command outputshows 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 Falselink1 S_AUTO_IF 8193 257 1 True Falselink2 S_AUTO_IF 8194 258 1 True Falselink3 S_AUTO_IF 8195 259 1 True Falselink4 S_AUTO_IF 8196 260 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 8193 8192 10.100.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.100 8194 8193 10.101.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.101 8195 8194 10.102.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.102 8196 8195 10.103.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.103 -------------------------------------------------------------------------------- Total UP/DOWN Session Number : 5/0

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 configurethe mVRRP backup group on GE 1/0/1.1 of NPE1 and NPE2 to implement VRRP fast switchover usingBFD sampling.

# Configure NPE1.

[NPE1] interface gigabitethernet1/0/1.1[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[NPE1-GigabitEthernet1/0/1.1] vrrp vrid 10 track bfd-session session-name link2 link[NPE1-GigabitEthernet1/0/1.1] vrrp vrid 10 track bfd-session session-name link3 link[NPE1-GigabitEthernet1/0/1.1] vrrp vrid 10 track bfd-session session-name link4 link[NPE1-GigabitEthernet1/0/1.1] vrrp vrid 10 track link-bfd down-number 2[NPE1-GigabitEthernet1/0/1.1] vrrp trigger route[NPE1-GigabitEthernet1/0/1.1] quit

# Configure NPE2.

[NPE2] interface gigabitethernet1/0/1.1[NPE2-GigabitEthernet1/0/1.1] vrrp vrid 10 track bfd-session session-name peer1 peer[NPE2-GigabitEthernet1/0/1.1] vrrp vrid 10 track bfd-session session-name link1 link[NPE2-GigabitEthernet1/0/1.1] vrrp vrid 10 track bfd-session session-name link2 link[NPE2-GigabitEthernet1/0/1.1] vrrp vrid 10 track bfd-session session-name link3



4-75

link[NPE2-GigabitEthernet1/0/1.1] vrrp vrid 10 track bfd-session session-name link4 link[NPE2-GigabitEthernet1/0/1.1] vrrp vrid 10 track link-bfd down-number 2[NPE2-GigabitEthernet1/0/1.1] vrrp trigger route[NPE2-GigabitEthernet1/0/1.1] quit

After the previous configurations, run the display vrrp interface command on the NPE. Thecommand output shows that, the allowable maximum number of the link BFD sessions in theDown state tracked by the mVRRP backup group is 2, the mVRRP backup group is bound toone 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 GigabitEthernet1/0/1.1 | Virtual Router 10 State : Master Virtual IP : 10.1.1.1 PriorityRun : 120 PriorityConfig : 120 MasterPriority : 120 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-010a Check TTL : YES Config type : admin-vrrp Config track link-bfd down-number : 2 Track BFD : link1 type: link BFD-session state : UP Track BFD : link2 type: link BFD-session state : UP Track BFD : link3 type: link BFD-session state : UP Track BFD : link4 type: link BFD-session state : UP Track BFD : peer1 type: peer BFD-session state : UP

[NPE2] display vrrp interface gigabitethernet1/0/1.1 GigabitEthernet1/0/1.1 | Virtual Router 10 State : Backup Virtual IP : 10.1.1.1 PriorityRun : 100 PriorityConfig : 100 MasterPriority : 120 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-010a Check TTL : YES Config type : admin-vrrp Config track link-bfd down-number : 2 Track BFD : link1 type: link BFD-session state : UP Track BFD : link2 type: link BFD-session state : UP Track BFD : link3 type: link BFD-session state : UP Track BFD : link4 type: link BFD-session state : UP Track BFD : peer1 type: peer BFD-session state : UP






Issue 03 (2010-03-31)







On NPE1, run the shutdown command on GE 1/0/1.100 to replicate the fault between NPE1and CE1.

[NPE1] interface gigabitethernet1/0/1.100[NPE1-GigabitEthernet1/0/1.100] shutdown[NPE1-GigabitEthernet1/0/1.100] quit

The command output shows that the BFD session between NPE1 and CE1 goes Down.

[NPE1] display bfd session all--------------------------------------------------------------------------------Local Remote PeerIpAddr State Type InterfaceName--------------------------------------------------------------------------------8192 8192 10.1.1.253 Up S_AUTO_IF GigabitEthernet1/0/1.18193 0 10.100.1.1 Down S_AUTO_IF GigabitEthernet1/0/1.1008194 8193 10.101.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.1018195 8194 10.102.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.1028196 8195 10.103.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.103-------------------------------------------------------------------------------- Total UP/DOWN Session Number : 4/1

In this configuration example, when two or more link BFD sessions go Down, the mVRRPbackup group performs master/backup fast switchover.

Currently, only one link BFD session is Down, so the mVRRP backup group does not performmaster/backup switchover.


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 Typeis Member.

[NPE1] display vrrp briefVRID State Interface Type Virtual IP



4-77

--------------------------------------------------------10 Master GE1/0/1.1 Admin 10.1.1.1100 Initialize GE1/0/1.100 Member 10.100.1.200101 Master GE1/0/1.101 Member 10.101.1.200102 Master GE1/0/1.102 Member 10.102.1.200103 Master GE1/0/1.103 Member 10.103.1.200







[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 8193 0 10.100.1.1 Down S_AUTO_IF GigabitEthernet1/0/1.100 8194 0 10.101.1.1 Down S_AUTO_IF GigabitEthernet1/0/1.101 8195 8194 10.102.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.102 8196 8195 10.103.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.103-------------------------------------------------------------------------------- Total UP/DOWN Session Number : 3/2

In this configuration example, the threshold for the number of link BFD sessions in the Downstate tracked by the mVRRP backup group is 2. That is, when two or more link BFD sessionsgo 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 isMember.

[NPE1] display vrrp briefVRID State Interface Type Virtual IP--------------------------------------------------------10 Initialize GE1/0/1.1 Admin 10.1.1.1100 Initialize GE1/0/1.100 Member 10.100.1.200101 Initialize GE1/0/1.101 Member 10.101.1.200102 Initialize GE1/0/1.102 Member 10.102.1.200103 Initialize GE1/0/1.103 Member 10.103.1.200

On NPE2:




Issue 03 (2010-03-31)




On NPE1, run the undo shutdown command on GE 1/0/1.100 and GE1/0/1.101 to replicate therecovery 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 NPE1and CE2 go 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.18193 8192 10.100.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.1008194 8193 10.101.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.1018195 8194 10.102.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.1028196 8195 10.103.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.103-------------------------------------------------------------------------------- Total UP/DOWN Session Number : 5/0

It indicates that the statuses of VRRP backup groups on NPE1 and NPE2 recover.

On NPE1:




On NPE2:




----End



4-79

Configuration Filesl Configuration file of NPE1

# sysname NPE1# bfd#interface GigabitEthernet1/0/1 undo shutdown mode user-termination#interface GigabitEthernet1/0/1.1 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 vrrp vrid 10 virtual-ip 10.1.1.1 admin-vrrp vrid 10 vrrp vrid 10 priority 120 vrrp vrid 10 track bfd-session session-name link1 link vrrp vrid 10 track bfd-session session-name link2 link vrrp vrid 10 track bfd-session session-name link3 link vrrp vrid 10 track bfd-session session-name link4 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#interface GigabitEthernet1/0/1.100 control-vid 100 qinq-termination qinq termination pe-vid 10 ce-vid 101 to 200 qinq vrrp pe-vid 10 ce-vid 101 ip address 10.100.1.254 255.255.255.0 vrrp vrid 100 virtual-ip 10.100.1.200 vrrp vrid 100 track admin-vrrp interface GigabitEthernet1/0/1.1 vrid 10 unflowdown arp broadcast enable#interface GigabitEthernet1/0/1.101 control-vid 101 qinq-termination qinq termination pe-vid 10 ce-vid 201 to 300 qinq vrrp pe-vid 10 ce-vid 201 ip address 10.101.1.254 255.255.255.0 vrrp vrid 101 virtual-ip 10.101.1.200 vrrp vrid 101 track admin-vrrp interface GigabitEthernet1/0/1.1 vrid 10 unflowdown arp broadcast enable#interface GigabitEthernet1/0/1.102 control-vid 102 qinq-termination qinq termination pe-vid 10 ce-vid 301 to 400 qinq vrrp pe-vid 10 ce-vid 301 ip address 10.102.1.254 255.255.255.0 vrrp vrid 102 virtual-ip 10.102.1.200 vrrp vrid 102 track admin-vrrp interface GigabitEthernet1/0/1.1 vrid 10 unflowdown arp broadcast enable#interface GigabitEthernet1/0/1.103 control-vid 103 qinq-termination qinq termination pe-vid 10 ce-vid 401 to 500 qinq vrrp pe-vid 10 ce-vid 401 ip address 10.103.1.254 255.255.255.0 vrrp vrid 103 virtual-ip 10.103.1.200 vrrp vrid 103 track admin-vrrp interface GigabitEthernet1/0/1.1 vrid 10 unflowdown arp broadcast enable#




Issue 03 (2010-03-31)

bfd link1 bind peer-ip 10.100.1.1 interface GigabitEthernet1/0/1.100 source-ip 10.100.1.254 auto commit#bfd link2 bind peer-ip 10.101.1.1 interface GigabitEthernet1/0/1.101 source-ip 10.101.1.254 auto commit#bfd link3 bind peer-ip 10.102.1.1 interface GigabitEthernet1/0/1.102 source-ip 10.102.1.254 auto commit#bfd link4 bind peer-ip 10.103.1.1 interface GigabitEthernet1/0/1.103 source-ip 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

l Configuration file of NPE2# sysname NPE2# bfd#interface GigabitEthernet1/0/1 undo shutdown mode user-termination#interface GigabitEthernet1/0/1.1 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.253 255.255.255.0 vrrp vrid 10 virtual-ip 10.1.1.1 admin-vrrp vrid 10 vrrp vrid 10 track bfd-session session-name link1 link vrrp vrid 10 track bfd-session session-name link2 link vrrp vrid 10 track bfd-session session-name link3 link vrrp vrid 10 track bfd-session session-name link4 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#interface GigabitEthernet1/0/1.100 control-vid 100 qinq-termination qinq termination pe-vid 10 ce-vid 101 to 200 qinq vrrp pe-vid 10 ce-vid 101 ip address 10.100.1.253 255.255.255.0 vrrp vrid 100 virtual-ip 10.100.1.200 vrrp vrid 100 track admin-vrrp interface GigabitEthernet1/0/1.1 vrid 10 unflowdown arp broadcast enable#interface GigabitEthernet1/0/1.101 control-vid 101 qinq-termination qinq termination pe-vid 10 ce-vid 201 to 300 qinq vrrp pe-vid 10 ce-vid 201 ip address 10.101.1.253 255.255.255.0 vrrp vrid 101 virtual-ip 10.101.1.200 vrrp vrid 101 track admin-vrrp interface GigabitEthernet1/0/1.1 vrid 10 unflowdown arp broadcast enable#interface GigabitEthernet1/0/1.102 control-vid 102 qinq-termination



4-81

qinq termination pe-vid 10 ce-vid 301 to 400 qinq vrrp pe-vid 10 ce-vid 301 ip address 10.102.1.253 255.255.255.0 vrrp vrid 102 virtual-ip 10.102.1.200 vrrp vrid 102 track admin-vrrp interface GigabitEthernet1/0/1.1 vrid 10 unflowdown arp broadcast enable#interface GigabitEthernet1/0/1.103 control-vid 103 qinq-termination qinq termination pe-vid 10 ce-vid 401 to 500 qinq vrrp pe-vid 10 ce-vid 401 ip address 10.103.1.253 255.255.255.0 vrrp vrid 103 virtual-ip 10.103.1.200 vrrp vrid 103 track admin-vrrp interface GigabitEthernet1/0/1.1 vrid 10 unflowdown arp broadcast enable#bfd link1 bind peer-ip 10.100.1.1 interface GigabitEthernet1/0/1.100 source-ip 10.100.1.253 auto commit#bfd link2 bind peer-ip 10.101.1.1 interface GigabitEthernet1/0/1.101 source-ip 10.101.1.253 auto commit#bfd link3 bind peer-ip 10.102.1.1 interface GigabitEthernet1/0/1.102 source-ip 10.102.1.253 auto commit#bfd link4 bind peer-ip 10.103.1.1 interface GigabitEthernet1/0/1.103 source-ip 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

l Configuration file of PE1# 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#interface GigabitEthernet1/0/0 undo shutdown ip address 200.1.34.3 255.255.255.0 mpls mpls ldp#interface GigabitEthernet1/0/1 undo shutdown#interface GigabitEthernet1/0/1.1 vlan-type dot1q 10 l2 binding vsi ldp1#




Issue 03 (2010-03-31)

interface GigabitEthernet1/0/3 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

l Configuration file of PE2# 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#interface GigabitEthernet1/0/0 undo shutdown ip address 200.1.34.4 255.255.255.0 mpls mpls ldp#interface GigabitEthernet1/0/1 undo shutdown#interface GigabitEthernet1/0/1.1 vlan-type dot1q 10 l2 binding vsi ldp1#interface GigabitEthernet1/0/4 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

l Configuration file of PE3# sysname PE3# mpls lsr-id 5.5.5.5 mpls



4-83

# mpls l2vpn#vsi ldp1 static pwsignal ldp vsi-id 100 peer 3.3.3.3 peer 4.4.4.4# mpls ldp#interface GigabitEthernet1/0/0 undo shutdown#interface GigabitEthernet1/0/0.1 vlan-type dot1q 10 l2 binding vsi ldp1#interface GigabitEthernet1/0/1 undo shutdown ip address 200.1.35.5 255.255.255.0 mpls mpls ldp#interface GigabitEthernet1/0/2 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#interface GigabitEthernet1/0/1 undo shutdown mode user-termination#interface GigabitEthernet1/0/1.100 control-vid 100 qinq-termination qinq termination pe-vid 10 ce-vid 110 ip address 10.100.1.1 255.255.255.0 arp broadcast enable#interface GigabitEthernet1/0/1.101 control-vid 101 qinq-termination qinq termination pe-vid 10 ce-vid 210 ip address 10.101.1.1 255.255.255.0 arp broadcast enable#interface GigabitEthernet1/0/1.102 control-vid 102 qinq-termination qinq termination pe-vid 10 ce-vid 310 ip address 10.102.1.1 255.255.255.0 arp broadcast enable#interface GigabitEthernet1/0/1.103




Issue 03 (2010-03-31)

control-vid 103 qinq-termination qinq termination pe-vid 10 ce-vid 410 ip address 10.103.1.1 255.255.255.0 arp broadcast enable#bfd link11 bind peer-ip 10.100.1.254 interface GigabitEthernet1/0/1.100 source-ip 10.100.1.1 auto commit#bfd link12 bind peer-ip 10.101.1.254 interface GigabitEthernet1/0/1.101 source-ip 10.101.1.1 auto commit#bfd link13 bind peer-ip 10.102.1.254 interface GigabitEthernet1/0/1.102 source-ip 10.102.1.1 auto commit#bfd link14 bind peer-ip 10.103.1.254 interface GigabitEthernet1/0/1.103 source-ip 10.103.1.1 auto commit#bfd link21 bind peer-ip 10.100.1.253 interface GigabitEthernet1/0/1.100 source-ip 10.100.1.1 auto commit#bfd link22 bind peer-ip 10.101.1.253 interface GigabitEthernet1/0/1.101 source-ip 10.101.1.1 auto commit#bfd link23 bind peer-ip 10.102.1.253 interface GigabitEthernet1/0/1.102 source-ip 10.102.1.1 auto commit#bfd link24 bind peer-ip 10.103.1.253 interface GigabitEthernet1/0/1.103 source-ip 10.103.1.1 auto commit#return

4.13.6 Example for Configuring Ignorance of the Down of anInterface Where the mVRRP Backup Group Is Configured


As shown in Figure 4-10, the CE connects to the sub-interface for QinQ termination of the NPEacross the VPLS convergence network.

On the NPE, the mVRRP backup group and the service VRRP backup group are configured andthe mVRRP backup group implements master/backup fast switchover by tracking the BFDsession.

In this configuration example, the following restrictions are imposed on the network:

l The VPLS convergence network belongs to another operator, so the link BFD sessioncannot be directly established between NPE1 and PE1 and between NPE2 and PE2.



4-85

l In the VPLS convergence network, the PW is established only between PE1 and PE3 andbetween PE1 and PE2. According to the VPLS split horizon rule, the mVRRP backup groupor 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 VRRPfast 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 BFDsessions concurrently. When two or more link BFD sessions go Down, the mVRRP backupgroup performs master/backup fast switchover.




Issue 03 (2010-03-31)

Figure 4-10 Typical networking of ignorance of the down of an interface where the mVRRPbackup group is configured

CE4

CE1

CE2

CE3

NPE1

NPE2

MPLS/IPCore

PeerBFD

PE1

PE2

Link BFD

AccessAggregation

VPLS Network Core





PE3

PW

PW

#interface GigabitEthernet1/0/1.100 ip address 10.100.1.254 255.255.255.0 vrrp vrid 100 virtual-ip 10.100.1.200#interface GigabitEthernet1/0/1.101 ip address 10.101.1.254 255.255.255.0 vrrp vrid 101 virtual-ip 10.101.1.200#interface GigabitEthernet1/0/1.102 ip address 10.102.1.254 255.255.255.0 vrrp vrid 102 virtual-ip 10.102.1.200#interface GigabitEthernet1/0/1.103 ip address 10.103.1.254 255.255.255.0 vrrp vrid 103 virtual-ip 10.103.1.200#

#interface GigabitEthernet1/0/1.100 ip address 10.100.1.253 255.255.255.0 vrrp vrid 100 virtual-ip 10.100.1.200#interface GigabitEthernet1/0/1.101 ip address 10.101.1.253 255.255.255.0 vrrp vrid 101 virtual-ip 10.101.1.200#interface GigabitEthernet1/0/1.102 ip address 10.102.1.253 255.255.255.0 vrrp vrid 102 virtual-ip 10.102.1.200#interface GigabitEthernet1/0/1.103 ip address 10.103.1.253 255.255.255.0 vrrp vrid 103 virtual-ip 10.103.1.200#

#interface Eth-Trunk 1.1 ip address 10.1.1.253 255.255.255.0 vrrp vrid 10 virtual-ip 10.1.1.1 admin-vrrp vrid 10#

#interface Eth-Trunk 1.1 ip address 10.1.1.254 255.255.255.0 vrrp vrid 10 virtual-ip 10.1.1.1 admin-vrrp vrid 10#



4-87


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 backupgroup 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.


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 proceduresof the BFD function of the CE as shown in Figure 4-9 and the VPLS convergence network, refer to theHUAWEI NetEngine80E/40E Router Configuration Guide - Reliability and Configuration Guide - VPN.

# Configure NPE1.

<HUAWEI> system-view[HUAWEI] sysname NPE1[NPE1] interface Eth-Trunk 1[NPE1-Eth-Trunk1] quit[NPE1] interface gigabitethernet1/0/2[NPE1-GigabitEthernet1/0/2] undo shutdown[NPE1-GigabitEthernet1/0/2] eth-trunk 1[NPE1-GigabitEthernet1/0/2] quit[NPE1] interface gigabitethernet2/0/1[NPE1-GigabitEthernet2/0/1] undo shutdown[NPE1-GigabitEthernet2/0/1] eth-trunk 1[NPE1-GigabitEthernet2/0/1] quit

# Configure NPE2.

<HUAWEI> system-view[HUAWEI] sysname NPE2[NPE2] interface Eth-Trunk 1[NPE2-Eth-Trunk1] quit[NPE2] interface gigabitethernet1/0/2[NPE2-GigabitEthernet1/0/2] undo shutdown[NPE2-GigabitEthernet1/0/2] eth-trunk 1[NPE2-GigabitEthernet1/0/2] quit[NPE2] interface gigabitethernet2/0/1[NPE2-GigabitEthernet2/0/1] undo shutdown[NPE2-GigabitEthernet2/0/1] eth-trunk 1[NPE2-GigabitEthernet2/0/1] quit

Step 2 Configure the sub-interface for QinQ VLAN tag termination on NPE1 and NPE2.

# Configure NPE1.




Issue 03 (2010-03-31)

[NPE1] interface eth-trunk 1[NPE1-Eth-Trunk1] mode user-termination[NPE1-Eth-Trunk1] undo shutdown[NPE1-Eth-Trunk1] quit[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[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.100[NPE1-GigabitEthernet1/0/1.100] control-vid 100 qinq-termination[NPE1-GigabitEthernet1/0/1.100] qinq termination pe-vid 10 ce-vid 101 to 200[NPE1-GigabitEthernet1/0/1.100] ip address 10.100.1.254 24[NPE1-GigabitEthernet1/0/1.100] arp broadcast enable[NPE1-GigabitEthernet1/0/1.100] quit[NPE1] interface gigabitethernet1/0/1.101[NPE1-GigabitEthernet1/0/1.101] control-vid 101 qinq-termination[NPE1-GigabitEthernet1/0/1.101] qinq termination pe-vid 10 ce-vid 201 to 300[NPE1-GigabitEthernet1/0/1.101] ip address 10.101.1.254 24[NPE1-GigabitEthernet1/0/1.101] arp broadcast enable[NPE1-GigabitEthernet1/0/1.101] quit[NPE1] interface gigabitethernet1/0/1.102[NPE1-GigabitEthernet1/0/1.102] control-vid 102 qinq-termination[NPE1-GigabitEthernet1/0/1.102] qinq termination pe-vid 10 ce-vid 301 to 400[NPE1-GigabitEthernet1/0/1.102] ip address 10.102.1.254 24[NPE1-GigabitEthernet1/0/1.102] arp broadcast enable[NPE1-GigabitEthernet1/0/1.102] quit[NPE1] interface gigabitethernet1/0/1.103[NPE1-GigabitEthernet1/0/1.103] control-vid 103 qinq-termination[NPE1-GigabitEthernet1/0/1.103] qinq termination pe-vid 10 ce-vid 401 to 500[NPE1-GigabitEthernet1/0/1.103] ip address 10.103.1.254 24[NPE1-GigabitEthernet1/0/1.103] arp broadcast enable[NPE1-GigabitEthernet1/0/1.103] quit

# Configure NPE2.

[NPE2] interface eth-trunk 1[NPE2-Eth-Trunk1] mode user-termination[NPE2-Eth-Trunk1] quit[NPE2] interface eth-trunk 1.1[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[NPE2-Eth-Trunk1.1] quit[NPE2] interface gigabitethernet1/0/1[NPE2-GigabitEthernet1/0/1] mode user-termination[NPE2-GigabitEthernet1/0/1] undo shutdown[NPE2-GigabitEthernet1/0/1] quit[NPE2] interface gigabitethernet1/0/1.100[NPE2-GigabitEthernet1/0/1.100] control-vid 100 qinq-termination[NPE2-GigabitEthernet1/0/1.100] qinq termination pe-vid 10 ce-vid 101 to 200[NPE2-GigabitEthernet1/0/1.100] ip address 10.100.1.253 24[NPE2-GigabitEthernet1/0/1.100] arp broadcast enable[NPE2-GigabitEthernet1/0/1.100] quit[NPE2] interface gigabitethernet1/0/1.101[NPE2-GigabitEthernet1/0/1.101] control-vid 101 qinq-termination[NPE2-GigabitEthernet1/0/1.101] qinq termination pe-vid 10 ce-vid 201 to 300[NPE2-GigabitEthernet1/0/1.101] ip address 10.101.1.253 24[NPE2-GigabitEthernet1/0/1.101] arp broadcast enable[NPE2-GigabitEthernet1/0/1.101] quit[NPE2] interface gigabitethernet1/0/1.102[NPE2-GigabitEthernet1/0/1.102] control-vid 102 qinq-termination[NPE2-GigabitEthernet1/0/1.102] qinq termination pe-vid 10 ce-vid 301 to 400[NPE2-GigabitEthernet1/0/1.102] ip address 10.102.1.253 24



4-89

[NPE2-GigabitEthernet1/0/1.102] arp broadcast enable[NPE2-GigabitEthernet1/0/1.102] quit[NPE2] interface gigabitethernet1/0/1.103[NPE2-GigabitEthernet1/0/1.103] control-vid 103 qinq-termination[NPE2-GigabitEthernet1/0/1.103] qinq termination pe-vid 10 ce-vid 401 to 500[NPE2-GigabitEthernet1/0/1.103] ip address 10.103.1.253 24[NPE2-GigabitEthernet1/0/1.103] arp broadcast enable[NPE2-GigabitEthernet1/0/1.103] quit

NOTE

After the IP address is assigned to a sub-interface for QinQ VLAN tag termination, it is recommended torun the arp broadcast enable command. Otherwise, the sub-interfaces for QinQ VLAN tag terminationfail 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 andNPE2 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.



According to the split horizon rule of the VPLS convergence network, the interfaces of NPE1and 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 PING 10.100.1.253: 56 data bytes, press CTRL_C to break Request time out Request time out Request time out Request time out Request time out

--- 3.3.3.3 ping statistics --- 5 packet(s) transmitted 0 packet(s) received 100.00% packet loss

The NPE and the CE in the same network segment can ping through each other. It indicates thatthe link between the NPE and the CE works normally. Take the ping between NPE1 and CE1or between NPE2 and CE1 as an example.


--- 10.100.1.1 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss




Issue 03 (2010-03-31)

round-trip min/avg/max = 120/152/180 ms

[NPE2] ping 10.100.1.1PING 10.100.1.1: 56 data bytes, press CTRL_C to break Reply from 10.100.1.1: bytes=56 Sequence=1 ttl=255 time=190 ms Reply from 10.100.1.1: bytes=56 Sequence=2 ttl=255 time=120 ms Reply from 10.100.1.1: bytes=56 Sequence=3 ttl=255 time=130 ms Reply from 10.100.1.1: bytes=56 Sequence=4 ttl=255 time=100 ms Reply from 10.100.1.1: bytes=56 Sequence=5 ttl=255 time=70 ms


Step 3 Configure basic VRRP functions on the sub-interfaces for QinQ VLAN tag termination of NPE1and 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 NPE2goes Down accordingly and the status of the VRRP backup group configured on this interface isswitched from Backup to Initialize, thus failing to implement VRRP fast switchover.

l In the scenario as shown in Figure 4-10, if NPE1 is not faulty, it is not recommended to run theshutdown command on Eth-Trunk1.1 on NPE1. Otherwise, the mVRRP backup groups on NPE1 andNPE2 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 thekeyword ignore-if-down. Otherwise, the state machine of the VRRP backup group is inconsistent withthat defined in RFC.

# On NPE1, configure the mVRRP backup group with VRID being 10 on Eth-Trunk1.1 andconfigure the service VRRP backup group on the sub-interfaces of GE 1/0/1.

[NPE1] interface eth-trunk 1.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[NPE1-Eth-Trunk1.1] quit[NPE1] interface gigabitethernet1/0/1.100[NPE1-GigabitEthernet1/0/1.100] qinq vrrp pe-vid 10 ce-vid 101[NPE1-GigabitEthernet1/0/1.100] vrrp vrid 100 virtual-ip 10.100.1.200[NPE1-GigabitEthernet1/0/1.100] quit[NPE1] interface gigabitethernet1/0/1.101[NPE1-GigabitEthernet1/0/1.101] qinq vrrp pe-vid 10 ce-vid 201[NPE1-GigabitEthernet1/0/1.101] vrrp vrid 101 virtual-ip 10.101.1.200[NPE1-GigabitEthernet1/0/1.101] quit[NPE1] interface gigabitethernet1/0/1.102[NPE1-GigabitEthernet1/0/1.102] qinq vrrp pe-vid 10 ce-vid 301[NPE1-GigabitEthernet1/0/1.102] vrrp vrid 102 virtual-ip 10.102.1.200[NPE1-GigabitEthernet1/0/1.102] quit[NPE1] interface gigabitethernet1/0/1.103[NPE1-GigabitEthernet1/0/1.103] qinq vrrp pe-vid 10 ce-vid 401[NPE1-GigabitEthernet1/0/1.103] vrrp vrid 103 virtual-ip 10.103.1.200[NPE1-GigabitEthernet1/0/1.103] quit

# On NPE2, configure the mVRRP backup group with VRID being 10 on Eth-Trunk1.1 andconfigure the service VRRP backup group on the sub-interfaces of GE 1/0/1.

[NPE2] interface eth-trunk 1.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



4-91

[NPE2-Eth-Trunk1.1] admin-vrrp vrid 10 ignore-if-down[NPE2-Eth-Trunk1.1] quit[NPE2] interface gigabitethernet1/0/1.100[NPE2-GigabitEthernet1/0/1.100] qinq vrrp pe-vid 10 ce-vid 101[NPE2-GigabitEthernet1/0/1.100] vrrp vrid 100 virtual-ip 10.100.1.200[NPE2-GigabitEthernet1/0/1.100] quit[NPE2] interface gigabitethernet1/0/1.101[NPE2-GigabitEthernet1/0/1.101] qinq vrrp pe-vid 10 ce-vid 201[NPE2-GigabitEthernet1/0/1.101] vrrp vrid 101 virtual-ip 10.101.1.200[NPE2-GigabitEthernet1/0/1.101] quit[NPE2] interface gigabitethernet1/0/1.102[NPE2-GigabitEthernet1/0/1.102] qinq vrrp pe-vid 10 ce-vid 301[NPE2-GigabitEthernet1/0/1.102] vrrp vrid 102 virtual-ip 10.102.1.200[NPE2-GigabitEthernet1/0/1.102] quit[NPE2] interface gigabitethernet1/0/1.103[NPE2-GigabitEthernet1/0/1.103] qinq vrrp pe-vid 10 ce-vid 401[NPE2-GigabitEthernet1/0/1.103] vrrp vrid 103 virtual-ip 10.103.1.200[NPE2-GigabitEthernet1/0/1.103] quit



l For the VRRP backup group with the VRID not being 10, State is Master and Type is Normal.

[NPE1] display vrrp briefVRID State Interface Type Virtual IP--------------------------------------------------------10 Master Eth-Trunk1.1 Admin 10.1.1.1100 Master GE1/0/1.100 Normal 10.100.1.200101 Master GE1/0/1.101 Normal 10.101.1.200102 Master GE1/0/1.102 Normal 10.102.1.200103 Master GE1/0/1.103 Normal 10.103.1.200


l For the VRRP backup group with the VRID not being 10, State is Master and Type is Normal.

[NPE2] display vrrp briefVRID State Interface Type Virtual IP--------------------------------------------------------10 Backup Eth-Trunk1.1 Admin 10.1.1.1100 Master GE1/0/1.100 Normal 10.100.1.200101 Master GE1/0/1.101 Normal 10.101.1.200102 Master GE1/0/1.102 Normal 10.102.1.200103 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 exchangedbetween the service VRRP backup groups of NPE1 and NPE2. Hence, the status of the service VRRPbackup 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] interface gigabitethernet1/0/1.100[NPE1-GigabitEthernet1/0/1.100] vrrp vrid 100 track admin-vrrp interface eth-trunk1.1 vrid 10 unflowdown[NPE1-GigabitEthernet1/0/1.100] quit[NPE1] interface gigabitethernet1/0/1.101[NPE1-GigabitEthernet1/0/1.101] vrrp vrid 101 track admin-vrrp interface eth-trunk1.1 vrid 10 unflowdown[NPE1-GigabitEthernet1/0/1.101] quit




Issue 03 (2010-03-31)

[NPE1] interface gigabitethernet1/0/1.102[NPE1-GigabitEthernet1/0/1.102] vrrp vrid 102 track admin-vrrp interface eth-trunk1.1 vrid 10 unflowdown[NPE1-GigabitEthernet1/0/1.102] quit[NPE1] interface gigabitethernet1/0/1.103[NPE1-GigabitEthernet1/0/1.103] vrrp vrid 103 track admin-vrrp interface eth-trunk1.1 vrid 10 unflowdown[NPE1-GigabitEthernet1/0/1.103] quit

# Configure NPE2.

[NPE2] interface gigabitethernet1/0/1.100[NPE2-GigabitEthernet1/0/1.100] vrrp vrid 100 track admin-vrrp interface eth-trunk1.1 vrid 10 unflowdown[NPE2-GigabitEthernet1/0/1.100] quit[NPE2] interface gigabitethernet1/0/1.101[NPE2-GigabitEthernet1/0/1.101] vrrp vrid 101 track admin-vrrp interface eth-trunk1.1 vrid 10 unflowdown[NPE2-GigabitEthernet1/0/1.101] quit[NPE2] interface gigabitethernet1/0/1.102[NPE2-GigabitEthernet1/0/1.102] vrrp vrid 102 track admin-vrrp interface eth-trunk1.1 vrid 10 unflowdown[NPE2-GigabitEthernet1/0/1.102] quitNPE2] interface gigabitethernet1/0/1.103[NPE2-GigabitEthernet1/0/1.103] vrrp vrid 103 track admin-vrrp interface eth-trunk1.1 vrid 10 unflowdown[NPE2-GigabitEthernet1/0/1.103] quit

NOTE

l In this configuration example, using the vrrp vrid track admin-vrrp command, you need to specifythe keyword unflowdown.

l If unspecified, when the status of the mVRRP backup group tracked by the service VRRP backup isBackup, the status of the interface where the service VRRP backup group is configured becomes Flowdown, the status of the service VRRP backup group becomes Initialize, and the status of the link BFDsession becomes Down. When the number of link BFD sessions in the Down state reaches the threshold,the status of the mVRRP backup also becomes Initialize, thus failing to implement master/backupswitchover of the mVRRP backup group.




[NPE1] display vrrp briefVRID State Interface Type Virtual IP--------------------------------------------------------10 Master Eth-Trunk1.1 Admin 10.1.1.1100 Master GE1/0/1.100 Member 10.100.1.200101 Master GE1/0/1.101 Member 10.101.1.200102 Master GE1/0/1.102 Member 10.102.1.200103 Master GE1/0/1.103 Member 10.103.1.200



[NPE2] display vrrp briefVRID State Interface Type Virtual IP--------------------------------------------------------10 Backup Eth-Trunk1.1 Admin 10.1.1.1100 Backup GE1/0/1.100 Member 10.100.1.200



4-93

101 Backup GE1/0/1.101 Member 10.101.1.200102 Backup GE1/0/1.102 Member 10.102.1.200103 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 theirstatus is normal.

NOTE

After the binding is finished, the service VRRP backup group no longer sends VRRP packets. The statusof 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 sessionbetween 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[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[NPE1] bfd link2 bind peer-ip 10.101.1.1 interface gigabitethernet1/0/1.101 source-ip 10.101.1.254 auto[NPE1-bfd-session-link2] commit[NPE1-bfd-session-link2] quit[NPE1] bfd link3 bind peer-ip 10.102.1.1 interface gigabitethernet1/0/1.102 source-ip 10.102.1.254 auto[NPE1-bfd-session-link3] commit[NPE1-bfd-session-link3] quit[NPE1] bfd link4 bind peer-ip 10.103.1.1 interface gigabitethernet1/0/1.103 source-ip 10.103.1.254 auto[NPE1-bfd-session-link4] commit[NPE1-bfd-session-link4] quit

# 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[NPE2-bfd-session-peer1] commit[NPE2-bfd-session-peer1] quit[NPE2] bfd link1 bind peer-ip 10.100.1.1 interface gigabitethernet1/0/1.100 source-ip 10.100.1.253 auto[NPE2-bfd-session-link1] commit[NPE2-bfd-session-link1] quit[NPE2] bfd link2 bind peer-ip 10.101.1.1 interface gigabitethernet1/0/1.101 source-ip 10.101.1.253 auto[NPE2-bfd-session-link2] commit[NPE2-bfd-session-link2] quit[NPE2] bfd link3 bind peer-ip 10.102.1.1 interface gigabitethernet1/0/1.102 source-ip 10.102.1.253 auto[NPE2-bfd-session-link3] commit[NPE2-bfd-session-link3] quit[NPE2] bfd link4 bind peer-ip 10.103.1.1 interface gigabitethernet1/0/1.103 source-ip 10.103.1.253 auto[NPE2-bfd-session-link4] commit[NPE2-bfd-session-link4] quit




Issue 03 (2010-03-31)

After the previous configurations are finished and the CE is correctly configured with the BFDsession, run the display bfd configuration all command on the NPE. The command outputshows 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 Falselink1 S_AUTO_IF 8193 4097 1 True Falselink2 S_AUTO_IF 8194 4098 1 True Falselink3 S_AUTO_IF 8195 4099 1 True Falselink4 S_AUTO_IF 8196 4100 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. Thecommand 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 Eth-Trunk1.1 8193 8192 10.100.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.1008194 8193 10.101.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.1018195 8194 10.102.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.1028196 8195 10.103.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.103-------------------------------------------------------------------------------- Total UP/DOWN Session Number : 5/0

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 configurethe mVRRP backup group on Eth-Trunk1.1 of NPE1 and NPE2 to implement VRRP fast switchover usingBFD sampling.

# Configure NPE1.

[NPE1] interface eth-trunk 1.1[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 bfd-session session-name link2 link[NPE1-Eth-Trunk1.1] vrrp vrid 10 track bfd-session session-name link3 link[NPE1-Eth-Trunk1.1] vrrp vrid 10 track bfd-session session-name link4 link[NPE1-Eth-Trunk1.1] vrrp vrid 10 track link-bfd down-number 2[NPE1-Eth-Trunk1.1] vrrp trigger route[NPE1-Eth-Trunk1.1] quit

# Configure NPE2.

[NPE2] interface eth-trunk 1.1[NPE2-Eth-Trunk1.1] vrrp vrid 10 track bfd-session session-name peer1 peer[NPE2-Eth-Trunk1.1] vrrp vrid 10 track bfd-session session-name link1 link[NPE2-Eth-Trunk1.1] vrrp vrid 10 track bfd-session session-name link2 link[NPE2-Eth-Trunk1.1] vrrp vrid 10 track bfd-session session-name link3 link[NPE2-Eth-Trunk1.1] vrrp vrid 10 track bfd-session session-name link4 link[NPE2-Eth-Trunk1.1] vrrp vrid 10 track link-bfd down-number 2[NPE2-Eth-Trunk1.1] vrrp trigger route[NPE2-Eth-Trunk1.1] quit



4-95

After the configuration, run the display vrrp interface command on NPE1 and NPE2. Thecommand output shows that the mVRRP backup group is bound to one peer BFD session andfour link BFD sessions and the BFD session status is Up.

[NPE1] display vrrp interface eth-trunk 1.1Eth-Trunk1.1 | Virtual Router 10 State : Master Virtual IP : 10.1.1.1 PriorityRun : 120 PriorityConfig : 120 MasterPriority : 120 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-010a Check TTL : YES Config type : admin-vrrp Config track link-bfd down-number : 2 Track BFD : link1 type : link BFD-session state : UP Track BFD : link2 type : link BFD-session state : UP Track BFD : link3 type : link BFD-session state : UP Track BFD : link4 type : link BFD-session state : UP Track BFD : peer1 type : peer BFD-session state : UP[NPE2] display vrrp interface eth-trunk 1.1Eth-Trunk1.1 | Virtual Router 10 State : Backup Virtual IP : 10.1.1.1 PriorityRun : 100 PriorityConfig : 100 MasterPriority : 120 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-010a Check TTL : YES Config type : admin-vrrp Config track link-bfd down-number : 2 Track BFD : link1 type : link BFD-session state : UP Track BFD : link2 type : link BFD-session state : UP Track BFD : link3 type : link BFD-session state : UP Track BFD : link4 type : link BFD-session state : UP Track BFD : peer1 type : peer BFD-session state : UP





[NPE1] display vrrp briefVRID State Interface Type Virtual IP--------------------------------------------------------




Issue 03 (2010-03-31)

10 Master Eth-Trunk1.1 Admin 10.1.1.1100 Master GE1/0/1.100 Member 10.100.1.200101 Master GE1/0/1.101 Member 10.101.1.200102 Master GE1/0/1.102 Member 10.102.1.200103 Master GE1/0/1.103 Member 10.103.1.200



[NPE2] display vrrp briefVRID State Interface Type Virtual IP--------------------------------------------------------10 Backup Eth-Trunk1.1 Admin 10.1.1.1100 Backup GE1/0/1.100 Member 10.100.1.200101 Backup GE1/0/1.101 Member 10.101.1.200102 Backup GE1/0/1.102 Member 10.102.1.200103 Backup GE1/0/1.103 Member 10.103.1.200




[NPE1] display bfd session all--------------------------------------------------------------------------------Local Remote PeerIpAddr State Type InterfaceName--------------------------------------------------------------------------------8192 8192 10.1.1.253 Up S_AUTO_IF Eth-Trunk1.18193 0 10.100.1.1 Down S_AUTO_IF GigabitEthernet1/0/1.1008194 8193 10.101.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.1018195 8194 10.102.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.1028196 8195 10.103.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.103-------------------------------------------------------------------------------- Total UP/DOWN Session Number : 4/1


Currently, only one link BFD session is Down, so the mVRRP backup group does not performmaster/backup switchover.


l For the VRRP backup group with the VRID being 100, State is Initialize and Type is Member.


[NPE1] display vrrp briefVRID State Interface Type Virtual IP----------------------------------------------------------10 Master Eth-Trunk1.1 Admin 10.1.1.1 100 Initialize GE1/0/1.100 Member 10.100.1.200101 Master GE1/0/1.101 Member 10.101.1.200102 Master GE1/0/1.102 Member 10.102.1.200103 Master GE1/0/1.103 Member 10.103.1.200

On NPE2:



4-97



[NPE2] display vrrp briefVRID State Interface Type Virtual IP---------------------------------------------------------10 Backup GE1/0/1.1 Admin 10.1.1.1100 Backup GE1/0/1.100 Member 10.100.1.200101 Backup GE1/0/1.101 Member 10.101.1.200102 Backup GE1/0/1.102 Member 10.102.1.200103 Backup GE1/0/1.103 Member 10.103.1.200




[NPE1] display bfd session all--------------------------------------------------------------------------------Local Remote PeerIpAddr State Type InterfaceName--------------------------------------------------------------------------------8192 8192 10.1.1.253 Up S_AUTO_IF Eth-Trunk1.18193 0 10.100.1.1 Down S_AUTO_IF GigabitEthernet1/0/1.1008194 0 10.101.1.1 Down S_AUTO_IF GigabitEthernet1/0/1.1018195 8194 10.102.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.1028196 8195 10.103.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.103-------------------------------------------------------------------------------- Total UP/DOWN Session Number : 3/2


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 isMember.

[NPE1] display vrrp briefVRID State Interface Type Virtual IP-----------------------------------------------------------10 Initialize Eth-Trunk1.1 Admin 10.1.1.1100 Initialize GE1/0/1.100 Member 10.100.1.200101 Initialize GE1/0/1.101 Member 10.101.1.200102 Initialize GE1/0/1.102 Member 10.102.1.200103 Initialize GE1/0/1.103 Member 10.103.1.200



[NPE2] display vrrp briefVRID State Interface Type Virtual IP----------------------------------------------------------10 Master Eth-Trunk1.1 Admin 10.1.1.1100 Master GE1/0/1.100 Member 10.100.1.200




Issue 03 (2010-03-31)

101 Master GE1/0/1.101 Member 10.101.1.200102 Master GE1/0/1.102 Member 10.102.1.200103 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 therecovery of the fault between NPE1 and CE1 and between NPE1 and CE2.

[NPE1] interface gigabitethernet1/0/1.100[NPE1-GigabitEthernet1/0/1.100] undo shutdown[NPE1-GigabitEthernet1/0/1.100] quit[NPE1] interface gigabitethernet1/0/1.101[NPE1-GigabitEthernet1/0/1.101] undo shutdown[NPE1-GigabitEthernet1/0/1.101] quit

The command output shows that the BFD sessions between NPE1 and CE1 and between NPE1and CE2 go Up.

[NPE1] display bfd session all--------------------------------------------------------------------------------Local Remote PeerIpAddr State Type InterfaceName --------------------------------------------------------------------------------8192 8192 10.1.1.253 Up S_AUTO_IF Eth-Trunk1.1 8193 8192 10.100.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.100 8194 8193 10.101.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.101 8195 8194 10.102.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.102 8196 8195 10.103.1.1 Up S_AUTO_IF GigabitEthernet1/0/1.103 -------------------------------------------------------------------------------- Total UP/DOWN Session Number : 5/0

It indicates that the statuses of the VRRP backup groups on NPE1 and NPE2 recoverrespectively.



[NPE1] display vrrp briefVRID State Interface Type Virtual IP--------------------------------------------------------10 Master Eth-Trunk1.1 Admin 10.1.1.1100 Master GE1/0/1.100 Member 10.100.1.200101 Master GE1/0/1.101 Member 10.101.1.200102 Master GE1/0/1.102 Member 10.102.1.200103 Master GE1/0/1.103 Member 10.103.1.200



[NPE2] display vrrp briefVRID State Interface Type Virtual IP--------------------------------------------------------10 Backup Eth-Trunk1.1 Admin 10.1.1.1100 Backup GE1/0/1.100 Member 10.100.1.200101 Backup GE1/0/1.101 Member 10.101.1.200102 Backup GE1/0/1.102 Member 10.102.1.200103 Backup GE1/0/1.103 Member 10.103.1.200

----End

Configuration Filesl Configuration file of NPE1



4-99

# sysname NPE1# bfd#interface Eth-Trunk1 mode user-termination#interface Eth-Trunk1.1 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 vrrp vrid 10 virtual-ip 10.1.1.1 admin-vrrp vrid 10 ignore-if-down vrrp vrid 10 priority 120 vrrp vrid 10 track bfd-session session-name link1 link vrrp vrid 10 track bfd-session session-name link2 link vrrp vrid 10 track bfd-session session-name link3 link vrrp vrid 10 track bfd-session session-name link4 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#interface GigabitEthernet1/0/1 undo shutdown mode user-termination#interface GigabitEthernet1/0/1.100 control-vid 100 qinq-termination qinq termination pe-vid 10 ce-vid 101 to 200 qinq vrrp pe-vid 10 ce-vid 101 ip address 10.100.1.254 255.255.255.0 vrrp vrid 100 virtual-ip 10.100.1.200 vrrp vrid 100 track admin-vrrp interface Eth-Trunk1.1 vrid 10 unflowdown arp broadcast enable#interface GigabitEthernet1/0/1.101 control-vid 101 qinq-termination qinq termination pe-vid 10 ce-vid 201 to 300 qinq vrrp pe-vid 10 ce-vid 201 ip address 10.101.1.254 255.255.255.0 vrrp vrid 101 virtual-ip 10.101.1.200 vrrp vrid 101 track admin-vrrp interface Eth-Trunk1.1 vrid 10 unflowdown arp broadcast enable#interface GigabitEthernet1/0/1.102 control-vid 102 qinq-termination qinq termination pe-vid 10 ce-vid 301 to 400 qinq vrrp pe-vid 10 ce-vid 301 ip address 10.102.1.254 255.255.255.0 vrrp vrid 102 virtual-ip 10.102.1.200 vrrp vrid 102 track admin-vrrp interface Eth-Trunk1.1 vrid 10 unflowdown arp broadcast enable#interface GigabitEthernet1/0/1.103 control-vid 103 qinq-termination qinq termination pe-vid 10 ce-vid 401 to 500 qinq vrrp pe-vid 10 ce-vid 401 ip address 10.103.1.254 255.255.255.0 vrrp vrid 103 virtual-ip 10.103.1.200 vrrp vrid 103 track admin-vrrp interface Eth-Trunk1.1 vrid 10 unflowdown arp broadcast enable#interface GigabitEthernet1/0/2 undo shutdown eth-trunk 1#




Issue 03 (2010-03-31)

interface GigabitEthernet2/0/1 undo shutdown eth-trunk 1#bfd link1 bind peer-ip 10.100.1.1 interface GigabitEthernet1/0/1.100 source-ip 10.100.1.254 auto commit#bfd link2 bind peer-ip 10.101.1.1 interface GigabitEthernet1/0/1.101 source-ip 10.101.1.254 auto commit#bfd link3 bind peer-ip 10.102.1.1 interface GigabitEthernet1/0/1.102 source-ip 10.102.1.254 auto commit#bfd link4 bind peer-ip 10.103.1.1 interface GigabitEthernet1/0/1.103 source-ip 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

l Configuration file of NPE2# sysname NPE2# bfd#interface Eth-Trunk1 mode user-termination#interface Eth-Trunk1.1 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.253 255.255.255.0 vrrp vrid 10 virtual-ip 10.1.1.1admin-vrrp vrid 10 ignore-if-down vrrp vrid 10 track bfd-session session-name link1 link vrrp vrid 10 track bfd-session session-name link2 link vrrp vrid 10 track bfd-session session-name link3 link vrrp vrid 10 track bfd-session session-name link4 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#interface GigabitEthernet1/0/1 undo shutdown mode user-termination#interface GigabitEthernet1/0/1.100 control-vid 100 qinq-termination qinq termination pe-vid 10 ce-vid 101 to 200 qinq vrrp pe-vid 10 ce-vid 101 ip address 10.100.1.253 255.255.255.0 vrrp vrid 100 virtual-ip 10.100.1.200 vrrp vrid 100 track admin-vrrp interface Eth-Trunk1.1 vrid 10 unflowdown arp broadcast enable#interface GigabitEthernet1/0/1.101 control-vid 101 qinq-termination qinq termination pe-vid 10 ce-vid 201 to 300 qinq vrrp pe-vid 10 ce-vid 201 ip address 10.101.1.253 255.255.255.0 vrrp vrid 101 virtual-ip 10.101.1.200



4-101

vrrp vrid 101 track admin-vrrp interface Eth-Trunk1.1 vrid 10 unflowdown arp broadcast enable#interface GigabitEthernet1/0/1.102 control-vid 102 qinq-termination qinq termination pe-vid 10 ce-vid 301 to 400 qinq vrrp pe-vid 10 ce-vid 301 ip address 10.102.1.253 255.255.255.0 vrrp vrid 102 virtual-ip 10.102.1.200 vrrp vrid 102 track admin-vrrp interface Eth-Trunk1.1 vrid 10 unflowdown arp broadcast enable#interface GigabitEthernet1/0/1.103 control-vid 103 qinq-termination qinq termination pe-vid 10 ce-vid 401 to 500 qinq vrrp pe-vid 10 ce-vid 401 ip address 10.103.1.253 255.255.255.0 vrrp vrid 103 virtual-ip 10.103.1.200 vrrp vrid 103 track admin-vrrp interface Eth-Trunk1.1 vrid 10 unflowdown arp broadcast enable#interface GigabitEthernet1/0/2 undo shutdown eth-trunk 1#interface GigabitEthernet2/0/1 undo shutdown eth-trunk 1#bfd link1 bind peer-ip 10.100.1.1 interface GigabitEthernet1/0/1.100 source-ip 10.100.1.253 auto commit#bfd link2 bind peer-ip 10.101.1.1 interface GigabitEthernet1/0/1.101 source-ip 10.101.1.253 auto commit#bfd link3 bind peer-ip 10.102.1.1 interface GigabitEthernet1/0/1.102 source-ip 10.102.1.253 auto commit#bfd link4 bind peer-ip 10.103.1.1 interface GigabitEthernet1/0/1.103 source-ip 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

l Configuration file of PE1# 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#interface GigabitEthernet1/0/0 undo shutdown ip address 200.1.34.3 255.255.255.0




Issue 03 (2010-03-31)

mpls mpls ldp#interface GigabitEthernet1/0/1 undo shutdown#interface GigabitEthernet1/0/1.1 vlan-type dot1q 10 l2 binding vsi ldp1#interface GigabitEthernet1/0/3 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

l Configuration file of PE2# 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#interface GigabitEthernet1/0/0 undo shutdown ip address 200.1.34.4 255.255.255.0 mpls mpls ldp#interface GigabitEthernet1/0/1 undo shutdown#interface GigabitEthernet1/0/1.1 vlan-type dot1q 10 l2 binding vsi ldp1#interface GigabitEthernet1/0/4 undo shutdown ip address 200.1.45.4 255.255.255.0 mpls mpls ldpinterface 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



4-103

#return

l Configuration file of PE3# 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#interface GigabitEthernet1/0/0 undo shutdown#interface GigabitEthernet1/0/0.1 vlan-type dot1q 10 l2 binding vsi ldp1#interface GigabitEthernet1/0/1 undo shutdown ip address 200.1.35.5 255.255.255.0 mpls mpls ldp#interface GigabitEthernet1/0/2 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# interface GigabitEthernet1/0/1 undo shutdown mode user-termination#interface GigabitEthernet1/0/1.100 control-vid 100 qinq-termination qinq termination pe-vid 10 ce-vid 110 ip address 10.100.1.1 255.255.255.0 arp broadcast enable#interface GigabitEthernet1/0/1.101 control-vid 101 qinq-termination qinq termination pe-vid 10 ce-vid 210 ip address 10.101.1.1 255.255.255.0 arp broadcast enable




Issue 03 (2010-03-31)

#interface GigabitEthernet1/0/1.102 control-vid 102 qinq-termination qinq termination pe-vid 10 ce-vid 310 ip address 10.102.1.1 255.255.255.0 arp broadcast enable#interface GigabitEthernet1/0/1.103 control-vid 103 qinq-termination qinq termination pe-vid 10 ce-vid 410 ip address 10.103.1.1 255.255.255.0 arp broadcast enable#bfd link11 bind peer-ip 10.100.1.254 interface GigabitEthernet1/0/1.100 source-ip 10.100.1.1 auto commit#bfd link12 bind peer-ip 10.101.1.254 interface GigabitEthernet1/0/1.101 source-ip 10.101.1.1 auto commit#bfd link13 bind peer-ip 10.102.1.254 interface GigabitEthernet1/0/1.102 source-ip 10.102.1.1 auto commit#bfd link14 bind peer-ip 10.103.1.254 interface GigabitEthernet1/0/1.103 source-ip 10.103.1.1 auto commit#bfd link21 bind peer-ip 10.100.1.253 interface GigabitEthernet1/0/1.100 source-ip 10.100.1.1 auto commit#bfd link22 bind peer-ip 10.101.1.253 interface GigabitEthernet1/0/1.101 source-ip 10.101.1.1 auto commit#bfd link23 bind peer-ip 10.102.1.253 interface GigabitEthernet1/0/1.102 source-ip 10.102.1.1 auto commit#bfd link24 bind peer-ip 10.103.1.253 interface GigabitEthernet1/0/1.103 source-ip 10.103.1.1 auto commit#return

4.13.7 Example for Configuring VRRP on VLANIF Interfaces


As shown in Figure 4-11, the networking requirements are as follows:

l Router A and Router B work in backup mode. Router A functions as the master and RouterB as the backup.

l Network 1 belongs to VLAN 10 and Network 2 belongs to VLAN 20. Both Router A andRouter B connect all networks through LAN switches.



4-105

l Network 1, Network 2, and Network 3 respectively correspond to the virtual IP addresses10.1.1.1, 10.1.2.1, and 100.10.1.1 of the three backup groups.

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

VLAN10

VLAN20

Network3VLAN30

GE1/0/1

GE1/0/2

GE1/0/2

GE1/0/1

Backup group 1Virtual IP Address

10.1.1.1/24


10.1.2.1/24

RouterA

RouterBSlave

GE3/0/0

GE3/0/0


100.10.1.1/24

Eth-Trunk1

Network1

Network2

Master

Both Router A and Router B are connected to Network1, Network2, and Network3 through GE1/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 GE2/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






Issue 03 (2010-03-31)

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 10and GE 1/0/2 to VLAN 20.

<RouterA> system-view[RouterA] interface gigabitethernet 1/0/1[RouterA-GigabitEthernet1/0/1] undo shutdown[RouterA-GigabitEthernet1/0/1] portswitch[RouterA-GigabitEthernet1/0/1] quit[RouterA] interface gigabitethernet 1/0/2[RouterA-GigabitEthernet1/0/2] undo shutdown[RouterA-GigabitEthernet1/0/2] portswitch[RouterA-GigabitEthernet1/0/2] quit[RouterA] interface gigabitethernet 3/0/0[RouterA-GigabitEthernet3/0/0] undo shutdown[RouterA-GigabitEthernet3/0/0] ip address 100.10.1.2 255.255.255.0[RouterA-GigabitEthernet3/0/0] quit[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] port gigabitethernet 1/0/2[RouterA-vlan20] interface vlanif20[RouterA-vlanif20] ip address 10.1.2.2 255.255.255.0[RouterA-vlanif20] quit

# Configure Router A to connect Router B through an Eth-Trunk.

[RouterA] interface eth-trunk1[RouterA-Eth-Trunk1] quit[RouterA] interface gigabitethernet 2/0/0[RouterA-GigabitEthernet2/0/0] undo shutdown[RouterA-GigabitEthernet2/0/0] eth-trunk1[RouterA-GigabitEthernet2/0/0] quit[RouterA] interface gigabitethernet 2/0/1[RouterA-GigabitEthernet2/0/1] undo shutdown[RouterA-GigabitEthernet2/0/1] eth-trunk1[RouterA-GigabitEthernet2/0/1] quit[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[RouterA-Eth-Trunk1] quit

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



4-107

# Activate the MST region configuration.

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


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 RouterA.

[RouterA] interface vlanif10[RouterA-vlanif10] vrrp vrid 1 virtual-ip 10.1.1.1[RouterA-vlanif10] vrrp vrid 1 priority 130[RouterA-vlanif10] quit[RouterA] interface vlanif20[RouterA-vlanif20] vrrp vrid 2 virtual-ip 10.1.2.1[RouterA-vlanif20] vrrp vrid 2 priority 130[RouterA-vlanif20] quit[RouterA] interface gigabitethernet 3/0/0[RouterA-GigabitEthernet3/0/0] vrrp vrid 3 virtual-ip 100.10.1.1[RouterA-GigabitEthernet3/0/0] vrrp vrid 3 priority 130[RouterA-GigabitEthernet3/0/0] quit



Run the display vrrp command on Router A and Router B to view information about the VRRPbackup groups.

[RouterA] display vrrpVlanif20 | Virtual Router 2 State : Master Virtual IP : 10.1.2.1 PriorityRun : 130 PriorityConfig : 130 MasterPriority : 130 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0102 Check TTL : YES Config type : normal-vrrp Vlanif10 | Virtual Router 1 State : Master Virtual IP : 10.1.1.1 PriorityRun : 130 PriorityConfig : 130 MasterPriority : 130 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0101 Check TTL : YES<RouterB> display vrrpVlanif20 | Virtual Router 2 State : Backup Virtual IP : 10.1.2.1 PriorityRun : 100 PriorityConfig : 100 MasterPriority : 130




Issue 03 (2010-03-31)

Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0102 Check TTL : YES Config type : normal-vrrp Vlanif10 | Virtual Router 1 State : Backup Virtual IP : 10.1.1.1 PriorityRun : 100 PriorityConfig : 100 MasterPriority : 130 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0101 Check TTL : YES Config type : normal-vrrp

# Run the shutdown command on VLANIF 10 of Router A to simulate a link fault.

[RouterA] interface vlanif10[RouterA-Vlanif10] quit

At this time, run the display vrrp command on Router A, and you can view that the status ofRouter A in back group 1 is Initialize.

[RouterA] display vrrpVlanif20 | Virtual Router 2 State : Master Virtual IP : 10.1.2.1 PriorityRun : 130 PriorityConfig : 130 MasterPriority : 130 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0102 Check TTL : YES Config type : normal-vrrp Vlanif10 | Virtual Router 1 State : Initialize Virtual IP : 10.1.1.1 PriorityRun : 130 PriorityConfig : 130 MasterPriority : 0 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0101 Check TTL : YES Config type : normal-vrrp

Run the display vrrp command on Router B, and you can view that the status of Router B inback group 1 is Master.

[RouterB] display vrrpVlanif20 | Virtual Router 2 State : Backup Virtual IP : 10.1.2.1 PriorityRun : 100 PriorityConfig : 100 MasterPriority : 130 Preempt : YES Delay Time : 0 TimerRun : 1



4-109

TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0102 Check TTL : YES Config type : normal-vrrp Vlanif10 | Virtual Router 1 State : Master Virtual IP : 10.1.1.1 PriorityRun : 100 PriorityConfig : 100 MasterPriority : 100 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0101 Check TTL : YES Config type : normal-vrrp

----End


# sysname RouterA#interface GigabitEthernet1/0/1 undo shutdown portswitch port default vlan 10#interface GigabitEthernet1/0/2 undo shutdown portswitch port default vlan 20#interface GigabitEthernet3/0/0 undo shutdown ip address 100.10.1.2 255.255.255.0 vrrp vrid 3 virtual-ip 100.10.1.1 vrrp vrid 3 priority 130#interface GigabitEthernet2/0/0 undo shutdown eth-trunk 1#interface GigabitEthernet2/0/1 undo shutdown eth-trunk 1#interface Vlanif10 ip address 10.1.1.3 255.255.255.0 vrrp vrid 1 virtual-ip 10.1.1.1 vrrp vrid 1 priority 130#interface vlanif20 undo shutdown ip address 10.1.2.2 255.255.255.0 vrrp vrid 2 virtual-ip 10.1.2.1 vrrp vrid 2 priority 130#return# interface eth-trunk1 undo shutdown port link-type trunk port trunk allow-pass vlan 10 20




Issue 03 (2010-03-31)

#stp region-configuration region-name RG1 instance 1 vlan 10 instance 2 vlan 20 active region-configuration# Return

l Configuration file of Router B# sysname RouterB#interface GigabitEthernet1/0/1 undo shutdown portswitch port default vlan 10#interface GigabitEthernet1/0/2 undo shutdown portswitch port default vlan 20#interface GigabitEthernet3/0/0 undo shutdown ip address 100.10.1.2 255.255.255.0 vrrp vrid 3 virtual-ip 100.10.1.1 vrrp vrid 3 priority 100#interface GigabitEthernet2/0/0 undo shutdown eth-trunk 1#interface GigabitEthernet2/0/1 undo shutdown eth-trunk 1# interface vlanif10 undo shutdown ip address 10.1.1.3 255.255.255.0 vrrp vrid 1 virtual-ip 10.1.1.1 vrrp vrid 1 priority 100#interface vlanif20 undo shutdown ip address 10.1.2.3 255.255.255.0 vrrp vrid 2 virtual-ip 10.1.2.1 vrrp vrid 1 priority 100#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-111

5 BFD Configuration

About This Chapter

This chapter describes the fundamentals of BFD , configurations of BFD basic functions , andBFD maintenance and provides configuration examples.

5.1 BFD IntroductionThis section describes the principles, concepts, and applications of BFD.

5.2 Configuring the One-Hop BFDThis section describes the application and the configuration of the one-hop BFD.

5.3 Configuring the BFD Passive Echo FunctionThe section describes the configuration of the BFD passive Echo function.

5.4 Configuring the Association Between the BFD Status and the Interface StatusThe section describes the application and the configuration of the association between the BFDstatus and the interface status.

5.5 Configuring the Association Between the BFD Status and the Sub-Interface StatusThe section describes the application and the configuration of the association between the BFDstatus and the sub-interface status.

5.6 Configuring the BFD to Modify the PSTThis section describes the application and the configuration of the BFD to modify the PST.

5.7 Configuring the Multi-Hop BFDThis section describes the application and the configuration of the multi-hop BFD.

5.8 Configuring the BFD Session with Automatically Negotiated DiscriminatorThe section describes the configuration and function of the BFD session with the automaticallynegotiated discriminator.

5.9 Configuring the Delay of the BFD Session to Be UpThe section describes the configuration and function of the delay of the BFD session to be up.

5.10 Adjusting BFD ParametersThis section describes how to adjust parameters of a BFD session.

5.11 Globally Configuring the Destination Port Number for the Multi-Hop BFD Control Packet

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability 5 BFD Configuration


5-1

This section describes the application of the destination port number of the multi-hop BFDcontrol packet and how to configure the destination port number globally.

5.12 Configuring the TTL GloballyThis section describes the application of the global TTL and how to configure the TTL globally.

5.13 Configuring the Interval for Sending Trap Messages

5.14 Maintaining BFD

5.15 Configuration ExamplesThis section provides several configuration examples of BFD.

5 BFD ConfigurationHUAWEI NetEngine80E/40E Router



Issue 03 (2010-03-31)

5.1 BFD IntroductionThis section describes the principles, concepts, and applications of BFD.

5.1.1 BFD Overview

5.1.2 BFD Features Supported by the NE80E/40E

5.1.1 BFD OverviewTo improve network performance, the system must be able to rapidly detect a communicationfailure, and then set up a backup channel to resume the communication.

In the current network, the following detection methods are used:

l Hardware detection signals, such as SDH alarm, are used to detect hardware faults on thelink.

l If no hardware detection signal is available to locate faults, the network often uses the Hellomessage provided by a routing protocol, which takes some time to detect a fault. Such along detection time causes loss of considerable amount of data.

l If the small scale network does not run the routing protocol, other derived detectionmechanisms are used. This may increase the difficulty in locating the interconnectionfault.To solve the preceding problems, the Bidirectional Forwarding Detection (BFD), aunified detection mechanism, is developed.

BFD is a unified detection mechanism used to rapidly detect and track the connectivity of thenetwork links or IP routing. To improve network performance, adjacent systems must be ableto rapidly detect a communication failure, and then set up a backup channel to resume thecommunication.

The BFD performs the following functions:

l Provides low-load and short-duration detection for path faults between two adjacentforwarding engines.

l Uses a single mechanism to perform real-time detection of all media or protocol layers,and supports different detection time and costs.

5.1.2 BFD Features Supported by the NE80E/40EAs a unified detection mechanism, BFD can be used by multiple protocols.

This section briefly describes the applications provided by BFD.

BFD Session Establishment Supported by the NE80E/40EBFD uses the local discriminator and remote discriminator to differentiate multiple BFD sessionsbetween the same pair of systems. According to the difference in the methods of creating thelocal discriminator and the remote discriminator, the NE80E/40E supports the following BFDsession types:l Static BFD sessions with manually specified discriminators

l Static BFD sessions with automatically negotiated discriminators



5-3

l Dynamic BFD sessions triggered by a protocol

The dynamic BFD session triggered by a protocol is implemented as follows:

l Dynamically allocating the local discriminator

l Self learning the remote discriminator

NOTE

At present, in the NE80E/40E, OSPF, BGP, IS-IS, MPLS, MPLS LDP, RSVP-TE, PWE3, and PIM candynamically trigger the establishment of BFD sessions.

When the two ends of a BFD session create discriminators in different methods, the followingmust be satisfied:

l If the static BFD session is established by manually specifying the discriminators on thelocal end, the static BFD session on the remote end must also be established by manuallyspecifying the discriminators.

l If the static BFD session is established by automatically negotiating the discriminators onthe local end, the static BFD session on the remote end can be established by automaticallynegotiating the discriminators or by configuring the dynamic BFD session.

l On the local end, if the static BFD session is established by automatically negotiating thediscriminators and by configuring the dynamic BFD session, the following principles areapplicable:

– If the dynamic BFD session and static BFD session with automatically negotiateddiscriminators share the same configurations (the source address, destination address,outgoing interface, and VPN index), the dynamic BFD session coexists with the staticBFD session with automatically negotiated discriminators.

– If the dynamic BFD session named DYN_local discriminator is configured first andthen the static BFD session with automatically negotiated discriminators is configured,the name of the dynamic BFD session is updated as the name of the static BFD session.

– Parameters of the shared session adopt the minimum values.

At present, the dynamic sessions that can coexist with static BFD sessions include BFD forOSPF, BFD for IS-IS, BFD for BGP, BFD for PIM, and BFD for RSVP-TE.

BFD Modes

The NE80E/40E supports asynchronous mode

l Asynchronous mode

Each system sends BFD Control packets based on the negotiated period. If a system doesnot receive any packet from the peer within the detection time, it sets the session to Down.

One-Hop BFD and Multi-Hop BFD

The NE80E/40E supports one-hop BFD and multi-hop BFD. This section describes the one-hopBFD.

The NE80E/40E supports the following one-hop BFDs of links:

l Layer 3 physical interface

l Ethernet sub-interface (including Eth-Trunk sub-interface)




Issue 03 (2010-03-31)

If a physical Ethernet interface has multiple sub-interfaces, the BFD session can be set upon each sub-interface and the physical Ethernet interface.

l The sub-interface for dot1q vlan tag termination and the sub-interface for qinq vlan tagtermination

l IP-Trunk– IP-Trunk link

– IP-Trunk member link

The BFD sessions can be used independently to detect the Trunk member interface and theTrunk interface at the same time.

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

The BFD sessions can be used independently to detect the trunk member interface and the trunkinterface at the same time.

NOTE

IP-Trunk and Eth-Trunk consist of member links, providing high bandwidth and reliability.

When the number of member links that are Up reaches a certain value, corresponding trunks can keep Up.

BFD for NE80E/40E can detect the trunk and its members separately for the connectivity of the entire trunkor an important member of a trunk.

l VLANIF– Ethernet member links in a VLAN

– VLANIF interface

The BFD session of the VLANIF and the BFD session of the VLANIF member are separate,and VLANIF and VLANIF members can be detected simultaneously.

Association Between the BFD Status and the Interface Status

Compared with the fault detection mechanism of the link protocol of the interface, BFD candetect the link fault faster if transmission devices exist in the directly connected link. The linkprotocol status of the Trunk interface or the VLAN interface depends on the link protocol statusof the member interfaces.

Therefore, to notify the BFD detection result to the application faster, each attribute of theinterface management module is added to the interface, namely, the BFD status. The BFD statusindicates the status of the BFD session that is bound to the interface. The system determines theinterface status according to the link status, protocol status, and BFD status. Then, the systemnotifies the interface status to the application.

The association between the BFD status and the interface status indicates that when the BFDsession status changes, the BFD status of the interface in the IFNET module is modified. In thisfunction, the one-hop BFD session is bound to the outgoing interface and uses the defaultmulticast address for detection, covering the following aspects:

l Association between the BFD status and the status of its bound interface



5-5

– When the BFD session becomes Down, the BFD status of the interface that is bound tothe BFD session also becomes Down. The interface status change is notified to theapplication on the interface.When the BFD session status of the Trunk member interface or the VLAN memberinterface becomes Down, the link protocol status of the Trunk member interface or theVLAN member interface also changes. The BFD session change accelerates the changeof the link protocol status and the route convergence of the Trunk interfaceor the VLANinterface .

NOTE

For the trunk whose member interfaces reside on different LPUs, when a BFD session is createdto detect the link between member interfaces of the trunk, you should use the process-pstcommand to associate the BFD session with the status of the interface. Otherwise, the traffic maybe lost in some situations. For example, the LPU where the member interface of the trunk residesis restarted.

– When the BFD session status is Up, the BFD status of the interface bound to the BFDsession also goes Up.

This function can notify the BFD detection result more rapidly to the application.l Association between the BFD status and the status of the sub-interface of the interface

bound to the BFD sessionThe BFD session must be bound to the main interface.– When the BFD session status goes Down, the BFD statuses of its bound interface and

all the sub-interfaces go Down. The status change is notified to the application on thesub-interface.The service configured on the sub-interface, such as RRPP can use the detection resultof the BFD session.

– When the BFD session status reverts to Up, the BFD statuses of the interface that isbound to the BFD session and all the sub-interfaces are also Up.

This function can save the session resources of the system and provide reliability for moreapplications. This function is typically used in the networking in which high reliability is requiredand a great number of services are configured on the sub-interface, such as the large-scale MANEthernet.

Changing Detection Parameters DynamicallyAfter a BFD session is set up, you can change the detection parameters, such as minimum sendinginterval, minimum receiving interval, and detecting mode. This does not affect the current statusof the session.

Binding VPN InstanceIn the NE80E/40E, a BFD session can be bound to a VPN instance. The BFD Control packetcan be thus transmitted in the specified VPN.

BFD for VRRPThe BFD detects and monitors the link or IP routes forwarding at a fast pace. So VRRP fastswitch is implemented.

NOTE

For the detailed configuration of the BFD for VRRP, refer to Chapter "VRRP Configuration."




Issue 03 (2010-03-31)

BFD for Static RoutesStatic routes do not have the detection mechanism. When the network fails, administratorinterference is needed.

With the feature of BFD for static routes, the BFD session can be used to detect the status of theIPv4 static route in the public network. The routing management system determines whether thestatic route is available according to the BFD session status.

NOTE

For the detailed configuration of BFD for static routes, refer to Chapter "IP Static Route Configuration" inthe HUAWEI NetEngine80E/40E Router Configuration Guide - IP Routing.

BFD for Routing ProtocolsBFD uses the local discriminator and the remote discriminator to distinguish different BFDsessions between two systems. IS-IS can dynamically and statically create BFD sessions; BGPand OSPF can dynamically create BFD sessions.

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

l Dynamically allocating the local discriminator

l Self learning the remote discriminator

When the routing protocol neighbor relation is established successfully, a routing protocolnotifies the establishment of a BFD session through routing management module and fast detectsthe neighbor relation of the routing protocol. Detection parameters of BFD session areconfigured by the routing protocols.

When a BFD session detects a failure, the session turns Down. BFD triggers the routeconvergence through a routing management module.

NOTE

Generally, a routing protocol based on the keepalive mechanism is contained in a Hello packet and thedetection is only at second level. BFD works at millisecond level at a detection interval of 3 x 10 ms. BFDadvertises a protocol failure within 50 ms. The route convergence speeds up.

When the neighbor is unreachable, the routing protocol notifies the BFD to delete the sessionthrough a routing management module.

BFD for Fast Reroutel BFD for LDP FRR

For the MPLS products forwarded by the software, the BFD can detect the protectedinterfaces. LDP FRR switchover is triggered when the BFD session is Down.

l BFD for IP FRR and BFD for VPN FRRFor NE80E/40E devices,the IP FRR and VPN FRR switchovers are triggered only after thedetected faults are reported to the control plane.

l BFD provides reliability to MPLS-based applications, such as VPN FRR, TE FRR, andVLL FRR for protecting services.

BFD for IS-ISIn the NE80E/40E, the statically configured BFD session is used to detect the IS-IS peerrelationship.



5-7

The BFD detects the link fault between IS-IS peer nodes, and fast reports it to IS-IS. The IS-ISfast convergence is thus triggered.

NOTE

l Because ISIS can be set up only one-hop IS-IS adjacencies, the BFD limits its operations to one-hopIS-IS adjacencies.

l For the detailed configuration of the BFD for IS-IS, refer to Chapter "IS-IS Configuration" in theHUAWEI NetEngine80E/40E Router Configuration Guide - IP Routing.

BFD for LSP

BFD can detect the failure in an MPLS LSP forwarding path on the data plane. At the same time,the format of BFD packets is constant, so the BFD packets are easily transmitted on hardwareand traverse the firewall. The advantages of BFD for LDP LSP on data plane are as follows:

l For the backward link, only the reachable IP route is required

l Fast detection

l Support large scale failure detection on LSP

To detect LDP LSP connectivity, the negotiation of BFD session is performed in two modes:

l Static establishment of the BFD session: After the local discriminator and remotediscriminator of BFD are configured manually, the BFD session is established through thenegotiation mechanism.

l Dynamic establishment of the BFD session: The BFD session is established throughnegotiation of BFD Discriminator Type Length Value (TLV) carried in LSP Ping messages.

In static mode, at present NE80E/40E, BFD is available for the following LSPs:

l Static LSP

l LDP LSP

l TE: Tunnel, static CR-LSP bound to the tunnel, and dynamic RSVP CR-LSP. BFD isavailable for the TE tunnels with signaling protocols as CE-static and RSVP-TE, and theprimary LSP bound to the TE tunnel.

In dynamic mode, BFD is available for the following forwarding paths:

l LDP LSP

l RSVP LSP

At present, the dynamic BFD session can only detect RSVP LSP, but neither detects TE LSPsbased on other signaling protocol, nor TE tunnels.

When BFD works on unidirectional link like LSP and TE, only a reachable IP route is requiredfor the backward link. The backward link can be IP, LSP, or TE tunnel.

NOTE

l For the configuration of BFD for static LSP and BFD for LDP LSP, refer to Chapter 1 "Basic MPLSConfiguration" in the HUAWEI NetEngine80E/40E Router Configuration Guide - MPLS.

l For the configuration of BFD for MPLS TE, refer to Chapter 2 "MPLS TE Configuration" in theHUAWEI NetEngine80E/40E Router Configuration Guide - MPLS.




Issue 03 (2010-03-31)

BFD for PWWith BFD, the PW link between the local and remote PEs can be fast detected for defaults. BFDsupports the VLL FRR to reduce the impact of link failure to services. The NE80E/40E supportsthe establishment of BFD for PW session in static (discriminator is configured manually) anddynamic modes.

The NE80E/40E combines VCCV ping and BFD for detecting PW connectivity dynamically.This can lead to fast switchover of upper layer services for protection.

NOTE

For the configuration of BFD for PW, refer to Chapter 7 "PWE3 Configuration" in the HUAWEINetEngine80E/40E Router Configuration Guide - VPN.

BFD for PIMThe NE80E/40E supports the dynamic creation of a BFD session between PIM neighbors, whichis used to detect the status of the link between the PIM neighbors. When a fault occurs on thelink, BFD notifies PIM of the fault.

NOTE

For the configuration of BFD for PIM, refer to the HUAWEI NetEngine80E/40E Router ConfigurationGuide - IP Multicast.

CAUTIONThe preceding BFD session is delivered to the selected LPU with the outgoing interface of LDP,TE, PIM, or a route orderly. If the outgoing interface is a logical interface with multipleinterfaces, such as an Eth-trunk interface, which has multiple sub-interfaces across differentLPUs, the BFD session select one of these LPUs randomly. When an interface board that isbound to BFD sessions but has no service interfaces is unplugged, the service may be switched.Thus, before unplugging the board, you can run the display bfd session all verbose commandto find out which sessions are bound to the board. If BFD sessions are bound to the board, youcan enter the BFD session view to shut all sessions down and then unplug the board. After this,you can create the session again.

5.2 Configuring the One-Hop BFDThis section describes the application and the configuration of the one-hop BFD.


5.2.2 Enabling the Global BFD

5.2.3 Setting Up a BFD Session




5-9


Applicable EnvironmentTo fast detect and monitor the directly-connected links, configure the one-hop BFD.

Pre-configuration TasksBefore configuring the one-hop BFD, complete the following tasks:

l Connecting each interface correctly

l Configuring IP addresses for the Layer 3 interfaces

Data PreparationTo configure the one-hop BFD, you need the following data.

No. Data

1 BFD configuration name

2 Peer IP address, local interface name, and number of the directly-connected link ofthe BFD. The default multicast address of the BFD for the physical-layer status ofthe link

3 BFD session parameters: local discriminator and remote discriminator

5.2.2 Enabling the Global BFD

ContextIf one-hop BFD detection is performed on the Layer 2 interfaces or the Layer 3 physicalinterfaces without IP addresses, such as IP-Trunk member interface and Layer 3 Eth-Trunkmember interface, the default multicast IP address is adopted.

Do as follows on the both ends of the link to be detected:

Procedure



Step 2 Run:bfd

BFD is enabled on this node and the BFD global view is displayed.

Step 3 (Optional) Run:default-ip-address ip-address

The default multicast IP address of the BFD is configured.




Issue 03 (2010-03-31)

By default, the multicast address used by the BFD is 224.0.0.184.

NOTE

If more than one BFD session exists on the BFD path, for example, the Layer 3 interface is connected bythe Layer 2 switches and is configured with BFD, you need to configure different default multicastaddresses for the devices. Thus, the devices are configured with different BFD sessions. This ensures thatBFD packets are correctly forwarded.

----End


ContextDo as follows on the both ends of the link to be detected:

Procedure



Step 2 According to the link type, run the following commands to create BFD binding:l For the 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 ]

l For the Layer 2 interface and the 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 ]

CAUTIONYou can run the command only on the physical layer 3 trunk or VLANIF member interfacesthat have no IP addresses, rather than on the physical layer 3 interfaces that have no IPaddresses.

NOTE

l When a one-hop BFD session is set up for the first time, the peer IP address and the correspondinglocal interface must be bound to the BFD session. After the one-hop BFD session is set up, you cannotmodify it.

l When the BFD configuration items are created, the system checks only the format of the IP addressrather than the correctness. The BFD session cannot be created if incorrect peer IP address or sourceIP address is bound to the session.

l When the BFD and Unicast Reverse Path Forwarding (URPF) are used together, URPF checks thesource IP address of the received packets. Therefore, when creating a BFD binding, you need source-ip to specify the source IP address of the BFD packet in case the BFD packet is incorrectly discarded.

Step 3 Configure the discriminators:l To configure the local discriminator, run:



5-11

discriminator local discr-value

l To configure the remote discriminator, run:discriminator remote discr-value

NOTE

l 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 remotedevice. The local discriminator of the local device needs to be the same as the remote discriminator ofthe remote device. Otherwise, the session cannot be correctly set up. After the local discriminator andthe remote discriminator are configured, you cannot modify it.

l For the BFD sessions to which the default multicast address is bound, the local discriminator and theremote discriminator of a BFD session cannot be the same.

Step 4 Run:commit

The configuration is committed.

NOTE

When setting up a single-hop BFD session, you must run the commit command after configuring necessaryparameters, such as local and remote discriminators; otherwise, the session cannot be set up.

----End


PrerequisiteThe configurations of the One-Hop BFD function are complete.

ContextNOTE

You can view statistics of BFD sessions and detailed information about sessions only after BFD sessionparameters are set and BFD sessions are set up.

Procedurel Run the display bfd configuration { all | dynamic | peer-ip peer-ip [ vpn-instance vpn-

instance-name ] | static [ name cfg-name ] | discriminator local discr-value }[ verbose ] command to check BFD configurations.

l Run the display bfd interface [ interface-type interface-number ] command to check BFDinterfaces.

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 tocheck the BFD session.

l Run the display bfd statistics [ slot slot-id ] command to check the global statistics of theBFD 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 tocheck statistics of the BFD session.

----End




Issue 03 (2010-03-31)

Example# After the configuration, you can run the display bfd session all verbose command to viewinformation about a BFD session.<HUAWEI> display bfd session all verbose---------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Up Name : aa--------------------------------------------------------------------- Local Discriminator : 11 Remote Discriminator : 22 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet1/2/0) Bind Session Type : Static Bind Peer Ip Address : 224.0.0.184 NextHop Ip Address : 224.0.0.184 Bind Interface : GigabitEthernet1/2/0 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 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 : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- Session Echo Tx TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ----------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

A one-hop BFD session is established and is in the Up state.

5.3 Configuring the BFD Passive Echo FunctionThe section describes the configuration of the BFD passive Echo function.

5.3.1 Establishing the Configuration Task5.3.2 Configuring the BFD Passive Echo Function5.3.3 Checking the Configuration


Applicable EnvironmentThe 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 tobe configured to be compatible with other devices.

Figure 5-1 Application scenario of the BFD passive Echo function

Single-hop BFDRouterA RouterB

RouterB Supports BFDEcho Function

RouterA Supports BFD Passive Echo Function



5-13

As shown in Figure 5-1, the passive Echo function needs to be enabled on Router A.


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 thatencapsulates the BFD Echo packet, the destination address and the source address are the IP address of theoutgoing interface of the local end. Therefore, in the ACL rule, both the source addresses of the remoteend 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

Context

Do as follows on the router that is enabled with the passive Echo function:

Procedure



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.




Issue 03 (2010-03-31)

NOTE

If the creation or modification of ACL rules takes place when the BFD session goes Up, the created ormodified ACL rules can take effective only after the BFD session goes Down or parameters of the BFDsession are modified.

----End


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 informationabout the BFD session.

----End

Example

# Display information about all the BFD sessions.

<HUAWEI> display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Up Name : aa-------------------------------------------------------------------------------- Local Discriminator : 11 Remote Discriminator : 22 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(Ethernet1/2/0) Bind Session Type : Static Bind Peer Ip Address : 224.0.0.184 Bind Interface : Ethernet1/2/0 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Enable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Disable WTR Interval (ms) : -- Local Demand Mode : Disable Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- Session Echo Tx TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0Session Description : ----------------------------------------------------------------------------------

The preceding display shows that the value of the field Session Detect Mode is AsynchronousMode Without Echo Function. This indicates that the BFD session is not enabled with thepassive Echo function. The value of the field Echo Passive is Enable. This indicates that theBFD session is enabled with the Echo function and can respond to the request of the remote endfor the Echo function. Currently, no request for the Echo function is received from the remoteend; therefore, the BFD session is in asynchronous mode that is not enabled with the Echofunction.



5-15

5.4 Configuring the Association Between the BFD Statusand the Interface Status

The section describes the application and the configuration of the association between the BFDstatus and the interface status.


5.4.2 Configuring the Association Between BFD Status and Interface Status



Applicable EnvironmentWhen a transport device exists on the link and a fault occurs on a link, the routers on both endsof the link need a long time to detect the fault. This is because although the two routers aredirectly connected, the actual physical path is segmented by the transport device.

Figure 5-2 Networking diagram of devices between the both end routers

RouterA RouterB

To solve the problem, the NE80E/40E implements the association between BFD status andinterface 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 sessionbecomes Down when it detects a fault, and the corresponding interface status becomesBFD_Down. When the interface is BFD_Down, the direct route of this interface is deleted fromthe routing table; however, the forwarding of BFD packets is not affected.

Pre-configuration TasksBefore configuring the association between BFD status and interface status, you need tocomplete the task of 5.2 Configuring the One-Hop BFD.

NOTE

Only the one-hop BFD session to which the default multicast IP address is bound can implement theassociation 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 PreparationTo configure the association between BFD status and interface status, you need the followingdata.




Issue 03 (2010-03-31)

No. Data


5.4.2 Configuring the Association Between BFD Status andInterface Status

ContextDo as follows on the NE80E/40E that needs to be configured with the association between BFDstatus and interface status:

Procedure



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 BFDsession 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



5-17

NOTE

l When the process-interface-status command and the commit command are run in succession, theBFD session may not be set up or the BFD session does not go Up through negotiation. Therefore, theBFD session does not notify the interface of the BFD status immediately, avoiding that the BFD sessionnotifies 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 statuschange. 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 isbound to the interface notifies the interface that the BFD session is Down when the NE80E/40E isrestarted, 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 whetherthe 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 canrun the shutdown and undo shudown commands to change the status of the BFD session. When theundo shutdown command is run, a timer to test the BFD session status is started. If the BFD sessiongoes Up through negotiation before the timer expires, the BFD session notifies the interface of the Upstate. Otherwise, the BFD session regards the link as failed and notifies the interface of the Down stateafter the timer expires. In this manner, the BFD session status and the interface status are in real-timesynchronization.

----End


PrerequisiteThe configurations of the Association Between the BFD Status and the Interface Status functionare complete.

Procedure

Step 1 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 the BFDsession.

----End

ExampleAfter 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-------------------------------------------------------------------------------- Local Discriminator : 22 Remote Discriminator : 11 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet2/0/0) Bind Session Type : Static Bind Peer Ip Address : 224.0.0.184 NextHop Ip Address : 224.0.0.184 Bind Interface : GigabiEthernet2/0/0 FSM Board Id : 2 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms) : 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : --




Issue 03 (2010-03-31)

Destination Port : 3784 TTL : 255 Proc interface status : Enable Process PST : Disable WTR Interval (ms) : -- Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- Session Echo Tx TmrID : -- PDT Index : FSM-0 | RCV-0 | IF-0 | TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

5.5 Configuring the Association Between the BFD Statusand the Sub-Interface Status

The section describes the application and the configuration of the association between the BFDstatus and the sub-interface status.


5.5.2 Configuring the Association Between BFD Status and Sub-Interface Status



Applicable EnvironmentIn the networking in which high reliability is required and a great number of services areconfigured on the sub-interface, you need to set up BFD sessions to verify the connectivity ofthe main interface link. In addition, you need to configure the association between the BFDstatus and the sub-interface status. Thus, you can enhance the reliability of the service on thesub-interface and save session resources.

Pre-configuration TasksBefore configuring the association between the BFD status and the sub-interface status, completethe following tasks:


l Setting up the one-hop BFD session, which is bound to the main interface and uses thedefault multicast address for detection

l Setting up the BFD session and ensuring that the BFD session is Up

Data PreparationTo configure the association between the BFD status and the sub-interface status, you need thefollowing data.

No. Data

1 Name of the BFD session



5-19

5.5.2 Configuring the Association Between BFD Status and Sub-Interface Status

ContextDo as follows on the NE80E/40E that needs to rapidly detect the link fault:

Procedure





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 BFDsession and its sub-interface also go Down.

NOTE

l When the process-interface-status command and the commit command are run in succession, theBFD session may not be set up or the BFD session does not go Up through negotiation. Therefore, theBFD session does not notify the interface of the BFD status immediately, avoiding that the BFD sessionnotifies 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 statuschange. 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 isbound to the interface notifies the interface that the BFD session is Down when the NE80E/40E isrestarted, 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 whetherthe 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 canrun the shutdown and undo shudown commands to change the status of the BFD session. When theundo shutdown command is run, a timer to test the BFD session status is started. If the BFD sessiongoes Up through negotiation before the timer expires, the BFD session notifies the interface of the Upstate. Otherwise, the BFD session regards the link as failed and notifies the interface of the Down stateafter the timer expires. In this manner, the BFD session status and the interface status are in real-timesynchronization.

----End




Issue 03 (2010-03-31)


PrerequisiteThe configurations of the Association Between the BFD Status and the Sub-Interface Statusfunction 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 informationabout the BFD session.

----End

ExampleRun the display bfd session all verbose command.

<HUAWEI> display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Up Name : aa-------------------------------------------------------------------------------- Local Discriminator : 11 Remote Discriminator : 22 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet1/2/0) Bind Session Type : Static Bind Peer Ip Address : 224.0.0.184 NextHop Ip Address : 224.0.0.184 Bind Interface : GigabitEthernet1/2/0 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Enable(Sub-If) Process PST : Disable WTR Interval (ms) : -- Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : -- Bind Application : IFNET Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- Session Echo Tx TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ----------------------------------------------------------------------------------

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 maininterface and the sub-interface.

5.6 Configuring the BFD to Modify the PSTThis section describes the application and the configuration of the BFD to modify the PST.


5.6.2 Permitting the BFD to Modify the PST



5-21




If the BFD can modify the Port State Table (PST), it modifies the corresponding entry in thePST when it detects that an interface is Down. Through the PST, other upper applicationprotocols can acknowledge whether the interface has a fault.

Currently, for the NE80E/40E, LDP FRR and IP FRR based on BFD detection need to knowthe BFD detection result through the PST.

You do not need to run the process-pst command on the applications that do not learn the BFDresults through the PST.

NOTE

l For the LDP FRR, refer to chapter "MPLS Basic Configuration"in the HUAWEI NetEngine80E/40ERouter Configuration Guide - MPLS.

l IP FRR works for the public network and for the private network. For information about the IP FRRfor the public network, refer to Chapter 10 "Routing Policy Configuration" in the HUAWEINetEngine80E/40E Router Configuration Guide - IP Routing.

l For information about the IP FRR for the private network, refer to Chapter 4 "BGP MPLS IP VPNConfiguration" in the HUAWEI NetEngine80E/40E Router Configuration Guide - VPN.


Before configuring the BFD to modify the PST, complete the task of 5.2 Configuring the One-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

Context

Do as follows on the router that learns the BFD results through the PST:

Procedure






Issue 03 (2010-03-31)



Step 3 Run:process-pst

The BFD is permitted to modify the PST.

By default, the BFD does not modify the PST.

If the BFD session on the Trunk member interface or the VLAN member interface allows BFDto modify the PST, and the main interface is configured with the BFD session, you must configurethe Wait to Recovery (WTR) for the BFD session that detects the main interface. This can preventthe BFD session on the main interface from flapping when the member interface joins or exitsfrom the main interface.

For the configuration of the WTR for the BFD session, see "5.10.3 Configuring the BFDWTR."

Step 4 Run:commit

The configurations are committed.

----End


PrerequisiteThe configurations of the BFD to Modify the PST function are complete.

Procedurel 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 tocheck the BFD session.

----End

ExampleAfter the configuration, running the display bfd session command, you can view that the fieldof "Process PST" in the command output is "Enable".

<HUAWEI> display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Up Name : test-------------------------------------------------------------------------------- Local Discriminator : 22 Remote Discriminator : 11 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet2/0/0) Bind Session Type : Static Bind Peer Ip Address : 10.100.10.2 NextHop Ip Address : 10.100.10.2 Bind Interface : GigabitEthernet2/0/0 FSM Board Id : 2 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10



5-23

Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Enable WTR Interval (ms) : -- Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- Session Echo Tx TmrID : -- PDT Index : FSM-0 | RCV-0 | IF-0 | TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

5.7 Configuring the Multi-Hop BFDThis section describes the application and the configuration of the multi-hop BFD.


5.7.2 Enabling BFD Globally





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




Issue 03 (2010-03-31)


ContextDo as follows on the router:

Procedure



Step 2 Run:bfd

The global BFD is enabled.

----End



Procedure



Step 2 Run the bfd cfg-name bind peer-ip peer-ip [ vpn-instance vpn-instance-name ] [ source-ipsource-ip ] command to configure a BFD session.

NOTE

l When a BFD session is set up for the first time, you need to bind the peer IP address to it. After theBFD 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 addressrather than the correctness. The BFD session cannot be established if incorrect peer IP address or sourceIP 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 packetin case the BFD packet is incorrectly discarded.

Step 3 Configure the discriminators.l Run:

discriminator local discr-value

The local discriminator is configured.l Run:

discriminator remote discr-value

The remote discriminator is configured.



5-25

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 remotedevice. Otherwise, the session cannot be correctly set up. After the local discriminator and the remotediscriminator are configured, you cannot modify it.

Step 4 Run:commit


NOTE

When setting up a BFD session, you must run the commit command after configuring necessaryparameters, such as local and remote discriminators; otherwise, the session cannot be set up.

----End


PrerequisiteThe configurations of the Multi-Hop BFD function are complete.

ContextNOTE

Only after the parameters of the session are set and the session is set up, you can view the information onthe session.


instance-name ] | static [ name cfg-name ] } [ verbose ] command to check BFDconfigurations.

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 ] to check theBFD 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 theBFD session.

----End

ExampleAfter the configuration, run the display bfd session all verbose command.

<HUAWEI> display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (Multi Hop) State : Up Name : atoc-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Peer Ip Address




Issue 03 (2010-03-31)

Bind Session Type : Static Bind Peer Ip Address : 10.2.1.2 Bind Interface : -- FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Enable WTR Interval (ms) : -- Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : -- -------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

You can view that a multi-hop BFD session is established. The BFD session is Up.

5.8 Configuring the BFD Session with AutomaticallyNegotiated Discriminator

The section describes the configuration and function of the BFD session with the automaticallynegotiated discriminator.



5.8.3 Configuring the BFD Session with Automatically Negotiated Discriminator




If the dynamic BFD session is adopted by the remote device, you must configure the static BFDsession with automatically negotiated discriminators on the local device to interwork with theremote device and support the static route to track BFD.


Before configuring the static BFD session with automatically negotiated discriminators,complete the following tasks:

l Correctly connecting each interface

l Correctly configuring the IP address of the Layer 3 interface

Data Preparation

To complete the configuration, you need the following data.



5-27

No. Data

1 Name of the BFD session

2 IP addresses of the local and remote ends of the link detected by BFD, and nameand number of the local interface


ContextDo as follows on the router on which the static BFD session with automatically negotiateddiscriminators is used to detect the link.

Procedure



Step 2 Run:bfd

BFD is enabled globally and the BFD view is displayed.

----End

5.8.3 Configuring the BFD Session with Automatically NegotiatedDiscriminator

ContextDo as follows on the router on which the static BFD session with the automatically negotiateddiscriminator is used to detect the link:

Perform the following step as required to configure BFD for IPv4 or VRRP for IPv6.

Procedurel For BFD for IPv4

1. Run:system-view


bfd cfg-name bind peer-ip ip-address [ vpn-instance vpn-name ] [ interface interface-type interface-number ] source-ip ip-address auto

A static BFD session with automatically negotiated discriminators is set up.

– You must specify the source IP address.




Issue 03 (2010-03-31)

– You must specify the peer IP address but cannot use a multicast IP address.

3. Run:commit


----End


PrerequisiteThe configurations of the BFD Session with Automatically Negotiated Discriminator functionare complete.

Procedurel 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 checkinformation about the BFD session.

----End

Example# After the configuration, run the display bfd session all verbose command.

<HUAWEI> display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 16385 (One Hop) State : Up Name : auto-------------------------------------------------------------------------------- Local Discriminator : 8193 Remote Discriminator : 8192 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet2/0/1) Bind Session Type : Static_Auto Bind Peer IP Address : 192.168.1.2 NextHop Ip Address : 192.168.1.2 Bind Interface : GigabitEthernet2/0/1 Bind Source IP Address : 192.168.1.1 FSM Board Id : 2 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : - Destination Port : 3784 TTL : 255 Proc Interface Status : Disable Process PST : Disable WTR Interval (ms) : - Last Local Diagnostic : No Diagnostic Bind Application : AUTO Session TX TmrID : - Session Detect TmrID : - Session Init TmrID : - Session WTR TmrID : - Session Echo Tx TmrID : - PDT Index : FSM-3010000 | RCV-0 | IF-3010000 | TOKEN-0 Session Description : ---------------------------------------------------------------------------------

Total UP/DOWN Session Number : 0/1

You can view that a BFD session with the type as Static_Auto is established. The localdiscriminator and the remote discriminator of this BFD session are 8193 and 8192 respectively,which are obtained by automatic negotiation.



5-29

5.9 Configuring the Delay of the BFD Session to Be UpThe section describes the configuration and function of the delay of the BFD session to be up.


5.9.2 Configuring the Delay of the BFD Session to Be Up



Applicable EnvironmentIn actual networking, some devices switch the traffic according to whether BFD is Up but therouting protocol becomes Up later than the interface; therefore, no route can be found when thetraffic is switched back. The traffic is thus lost. Thus, the difference between the time when therouting protocol becomes Up and the time when the interface becomes Up must be eliminated.

Pre-configuration TasksBefore configuring the delay of the BFD session to be Up, ensure that the router runs normally.

Data PreparationTo complete the configuration, you need the following data.

No. Data

1 Delay up time

5.9.2 Configuring the Delay of the BFD Session to Be Up

ContextDo as follows on the routers on which the setup of the BFD session needs to be delayed.

Procedure



Step 2 Run:bfd

BFD is enabled globally and the BFD view is displayed.

Step 3 Run:




Issue 03 (2010-03-31)

delay-up seconds

The time that the BFD session is delayed to become Up is set.

By default, the delay time is 0 seconds.

----End


PrerequisiteThe configurations of the Delay of the BFD Session to Be Up function are complete.

Procedure

Step 1 Run the display bfd statistics [ slot slot-id ] command to check statistics of BFD globally.

----End

Example# After the configuration, restart the router. After the restart, run the display bfd statisticscommand.

<HUAWEI> display bfd statisticsCurrent Display Board Number : Main ; Current Product Register type:IP Multihop Destination Port : 3784Total Up/Down Session Number : 0/1Current 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 1BFD_IF_NUM 512 1 1BFD_SESSION_NUM 8192 1 1BFD_IO_SESSION_NUM 512 1 0BFD_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 /08 /0 9 /0 10/0 11/0 12/0 13/0 14/0 15/016/0 17/0 18/0 19/0 20/0 21/0 22/0 23/024/0 25/0 26/0 27/0 28/0 29/0 30/0 31/032/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 /08 /0 9 /0 10/0 11/0 12/0 13/0 14/0 15/016/0 17/0 18/0 19/0 20/0 21/0 22/0 23/024/0 25/0 26/0 27/0 28/0 29/0 30/0 31/032/0 33/0 34/0 35/0 36/0 37/0--------------------------------------------------------------------------------BFD HA Information :--------------------------------------------------------------------------------



5-31

Core Current HA Status : NormalShell Current HA Status : Normal--------------------------------------------------------------------------------BFD for LSP Information :--------------------------------------------------------------------------------Ability of auto creating BFD session on egress : DisablePeriod of LSP Ping : 60System Session Delay Up Timer : OFF--------------------------------------------------------------------------------

You can view the field System Session Delay Up Timer in the command output. This fielddisplays the status of the current system delay Up time. OFF indicates that the system is in thenormal state; Xs indicates that after X seconds, the system recovers, and the BFD session is Up.

5.10 Adjusting BFD ParametersThis section describes how to adjust parameters of a BFD session.


5.10.2 Modifying the Detection Time

5.10.3 Configuring the BFD WTR

5.10.4 Adding the Description of a BFD Session




When a BFD session is set up, the sending interval, the receiving interval and the local detectionmultiplier can be adjusted on the basis of the network status and performance requirement.

You can also configure the Wait to Recovery (WTR) of the BFD session to avoid the frequentactive/standby switchover caused by the BFD session flapping.

Users can add the description of the BFD session to describe the link monitored by the BFDsession.

Generally, the default configuration is used.


Before adjusting BFD parameters, you need to set up a BFD session.

Data Preparation

To adjust the BFD parameters, you need the following data.

No Data


2 Interval during which local BFD packets are sent or received




Issue 03 (2010-03-31)

No Data

3 Local detection multiplier of the BFD

5.10.2 Modifying the Detection Time


Procedure





Step 3 Run:min-tx-interval interval

The sending interval is set.

By default, the minimum sending interval is 10 milliseconds.

Step 4 Run:min-rx-interval interval

The receiving interval is set.

By default, the minimum sending interval is 10 milliseconds.

Step 5 Run:detect-multiplier multiplier

The local detection multiplier is set.

By default, the local detection multiplier is 3.

Step 6 Run:commit


----End

PostrequisiteTo reduce the usage of the system resources, once the BFD session is Down, the systemautomatically adjusts the local sending or receiving interval to a random value between 1000milliseconds and 3000 milliseconds. When the BFD session is Up, the user-configured intervalis used.



5-33

NOTE

To efficiently use system resources, when detecting that the BFD session goes Down, the systemautomatically adjusts the interval for receiving and sending BFD control packets to be a random valuelarger than 10000 ms. When the BFD session goes Up, the set interval is restored.

5.10.3 Configuring the BFD WTR

ContextYou can configure the Wait to Recovery (WTR) of the BFD session to avoid the frequent active/standby switchover caused by the BFD session flapping. When the BFD session changes fromDown to Up, the BFD reports the change to the upper layer applications after the WTR timesout.

Do as follows on the router:

Procedure





Step 3 Run:wtr wtr-value

The WTR is configured.

By default, the WTR is 0, that is, it does not wait to restore.

NOTE

The BFD session is unidirectional. If the WTR is applied, you must configure the same WTR at both ends.Otherwise, when the session status changes at one end, applications at both ends know different BFDsession status.

Step 4 Run:commit


----End

5.10.4 Adding the Description of a BFD Session


Procedure

Step 1 Run:




Issue 03 (2010-03-31)

system-view




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 the BFD session.

Step 4 Run:commit


----End


PrerequisiteThe configurations of Adjusting BFD Parameters function are complete.

ContextNOTE

You can view the information on the BFD session, only when the parameters of the BFD session are setand the session is set up.


instance-name ] | static [ name cfg-name ] | discriminator local discr-value }[ verbose ] to check the BFD configuration.

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 ] to checkinformation about the BFD session.

----End

ExampleAfter the configuration, run the display bfd session all verbose command.

<HUAWEI> display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Up Name : aa-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20



5-35

Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet1/2/0) Bind Session Type : Static Bind Peer Ip Address : 10.1.1.2 NextHop Ip Address : 10.1.1.2 Bind Interface : GigabitEthernet1/2/0 FSM Board Id : 6 TOS-EXP : 6 Min Tx Interval (ms) : 500 Min Rx Interval (ms) : 500 Actual Tx Interval (ms): 500 Actual Rx Interval (ms): 500 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Enable WTR Interval (ms) : 60000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- Session Echo Tx TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : RouterA_to_RouterB-------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

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.

5.11 Globally Configuring the Destination Port Number forthe Multi-Hop BFD Control Packet

This section describes the application of the destination port number of the multi-hop BFDcontrol packet and how to configure the destination port number globally.


5.11.2 Globally Configuring the Destination Port Number




The BFD control packet is encapsulated in the UDP packet for transmission, using the sourceport in the range of 49152 to 65535 and destination port 3784 or 4784. According to the BFDdraft, 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 controlpacket. The destination port number of the multi-hop BFD control packet can be configuredglobally according to the requirements:

l To interwork with the device running the version earlier than the NE80E/40E, the devicerunning the NE80E/40E can be configured with destination port 3784 for the multi-hopBFD control packet.

l To interwork with the non-Huawei device, the device running the NE80E/40E can beconfigured with destination port 4784 for the multi-hop BFD control packet.




Issue 03 (2010-03-31)


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, youneed the following data.

No. Data

1 Name of the device

5.11.2 Globally Configuring the Destination Port Number

Context

Do as follows on each device:

Procedure



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 successfullynegotiate with the router on which destination port 4784 is used by the multi-hop BFD control packets. Atthe same time, on the router that is configured with destination port 3784, destination port 3784 isautomatically 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 undoshutdown command to restore the BFD session.

----End



5-37


PrerequisiteAll global configurations of the destination port number of the multi-hop BFD control packetare completed.

ContextNOTE

You can view information about the BFD session and its statistics only after only after BFD sessionparameters are configured and the BFD session is set up successfully.


ip [ vpn-instance vpn-instance-name ] | static } [ verbose ] [ slot slot-id ] command toview information about the BFD session.

l Run the display bfd statistics [ slot slot-id ] command to view information about statisticsof global BFD.

----End

Example<HUAWEI> display bfd session all verbose---------------------------------------------------------------------Session MIndex : 16384 (Multi Hop) State : Up Name : test--------------------------------------------------------------------- Local Discriminator : 111 Remote Discriminator : 222 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(Pos6/0/0) Bind Session Type : Static Bind Peer IP Address : 100.1.1.2 NextHop Ip Address : 100.1.1.2 Bind Interface : Pos6/0/0 FSM Board Id : 6 TOS-EXP : 6 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : - Destination Port : 3784 TTL : 254 Proc Interface Status : Disable Process PST : Disable WTR Interval (ms) : - Active Multi : 3 Last Local Diagnostic : Control Detection Time Expired Bind Application : No Application Bind Session TX TmrID : - Session Detect TmrID : - Session Init TmrID : - Session WTR TmrID : - Session Echo Tx TmrID : - PDT Index : FSM-B030000 | RCV-0 | IF-B030000 | TOKEN-0 Session Description : ----------------------------------------------------------------------------

According to the preceding command output, you can view that destination port 3784 is usedfor the multi-hop BFD control packet.

5.12 Configuring the TTL GloballyThis section describes the application of the global TTL and how to configure the TTL globally.




Issue 03 (2010-03-31)


5.12.2 Configuring the TTL Globally



Applicable EnvironmentWhen devices running different versions interwork with each other, the TTL values and detectionmodes on both ends of the BFD session are different and the BFD packets are discarded. Youcan set the TTL globally to enable Huawei devices running different NE80E/40E versions tointerwork with each other and non-Huawei devices.

Pre-configuration TasksBefore configuring the TTL globally, complete the following tasks:

l Connecting interfaces correctly

l Configuring the IP address of the Layer 3 interface correctly

Data PreparationTo configure the TTL globally, you need the following data.

No. Data

1 Name and number of each interface

5.12.2 Configuring the TTL Globally

ContextDo as follows on each device:

Procedure



Step 2 Run:bfd

BFD is enabled globally on the local node and the BFD view is displayed.

Step 3 Run:peer-ip peer-ip mask-length ttl { single-hop | multi-hop } ttl-value

The TTL of the BFD control packet is configured.



5-39

NOTE

By default, for the static BFD session, the TTL of the single-hop BFD packet is 255 and the TTL of themulti-hop BFD packet is 254. For the dynamic BFD session, the TTL of the single-hop BFD packet is 255;the TTL of the multi-hop BFD packet is 253.

----End


PrerequisiteAll global configurations of the TTL are completed.


ip [ vpn-instance vpn-instance-name ] | static } [ verbose ] [ slot slot-id ] command toview information about the BFD session.

l Run the display bfd ttl [ slot slot-id ] command to view information about the globallyconfigured TTL.

----End

ExampleAfter the configurations are successful, run the display bfd ttl command, and you can viewinformation about the global TTL.

<HUAWEI> display bfd ttl--------------------------------------------------------------------------Peer IP Mask Type Value---------------------------------------------------------------------------1.1.1.0 24 Single-hop 255---------------------------------------------------------------------------

5.13 Configuring the Interval for Sending Trap Messages5.13.1 Establishing the Configuration Task

5.13.2 Configuring the Interval for Sending Trap Messages



Applicable EnvironmentIf BFD is enabled with the SNMP trap function, the NMS can receive messages indicating thatthe BFD session is Up or Down. If the BFD session flaps, the NMS receives a large number oftrap messages. In this case, BFD trap messages need to be suppressed. You can prevent overflowof trap messages by setting the interval for sending trap messages.

Pre-configuration TasksBefore configuring the Interval for Sending Trap Messages, complete the following tasks:




Issue 03 (2010-03-31)


Data Preparation

To configure the Interval for Sending Trap Messages, you need the following data.

No. Data

1 Interval for sending trap messages

5.13.2 Configuring the Interval for Sending Trap Messages

Context

Do as follows on the router that needs to be configured with the interval for sending trapmessages:

Procedure



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 for sending trap messages is set.

By default, the interval for sending trap messages is 120s.

----End


PrerequisiteAll configurations of the interval for sending trap massages are complete.

Procedurel Run the display current-configuration configuration bfd command to view the

configuration of the BFD trap function.

----End



5-41

Example

Run the display current-configuration configuration bfd command, and you can view thatthe interval for sending trap messages is 300 seconds.

<HUAWEI> display current-configuration configuration bfd# bfd snmp-agent bfd trap-interval 300#return

5.14 Maintaining BFD

5.14.1 Clearing the BFD Statistics

5.14.2 Monitoring the Running of BFD

5.14.1 Clearing the BFD Statistics

Context

CAUTIONBFD statistics cannot be restored after you clear it. So, confirm the action before you use thecommand.

Procedure

Step 1 Run the reset reset bfd statistics { all [ slot slot-id ] | discriminator discr-value } command inthe user view to clear the BFD statistics.

----End

5.14.2 Monitoring the Running of BFD

Context

In routine maintenance, you can run the following commands in any view to display the runningof BFD.

Procedurel Run the display bfd configuration { all | static [ name cfg-name ] | dynamic | peer-ip

peer-ip [ vpn-instance vpn-instance-name ] | discriminator local discr-value }[ verbose ] command in any view to check the BFD configuration.

l Run the display bfd interface [ interface-type interface-number ] command in any viewto check the information about the interface that is enabled with BFD.




Issue 03 (2010-03-31)

l Run the display bfd session { all | static | dynamic | discriminator discr-value | peer-ippeer-ip [ vpn-instance vpn-instance-name ] } [ verbose ] [ slot slot-id ] command in anyview to check information about the BFD session.

l Run the display bfd statistics [ slot slot-id ] command in any view to check the statisticsof BFD globally.

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 inany view to check the statistics of the BFD session.

----End

5.15 Configuration ExamplesThis section provides several configuration examples of BFD.

5.15.1 Example for Configuring One-Hop BFD for Layer 3 Physical Link

5.15.2 Example for Configuring the One-Hop BFD for IP-Trunk Member Link

5.15.3 Example for Configuring One-Hop BFD for IP-Trunk

5.15.4 Example for Configuring One-Hop BFD for Layer 3 Eth-Trunk Member Link

5.15.5 Example for Configuring One-Hop BFD for Layer 3 Eth-Trunk

5.15.6 Example for Configuring One-Hop BFD for VLANIF Interfaces

5.15.7 Example for Configuring the Association Between the BFD Status and the Interface Status

5.15.8 Example for Configuring the Association Between the BFD Status and the Sub-InterfaceStatus

5.15.9 Example for Configuring Multi-Hop BFD

5.15.10 Example for Configuring the BFD for VPN Routes

5.15.1 Example for Configuring One-Hop BFD for Layer 3 PhysicalLink


As shown in Figure 5-3, the asynchronous mode of the BFD is used to detect the directlyconnected link between Router A and Router B.

Figure 5-3 Networking diagram of configuring the one-hop BFD

W

RouterA RouterB

POS1/0/010.1.1.1/24

POS1/0/010.1.1.2/24



5-43


1. Configure a BFD session on Router A to detect the directly-connected link between RouterA and Router B.

2. Configure a BFD session on Router B to detect the directly-connected link between RouterB and Router A.


l Peer IP address of the BFD

l The local interface of sending and receiving the BFD control packets

l The local discriminator and remote discriminator of the BFD session

The minimum sending interval, the minimum receiving interval, and the local detectionmultiplier of the BFD Control packet adopt the default values.

Procedure

Step 1 Configure IP addresses of the directly-connected interfaces on Router A and Router B.

# Configure the IP address of the interface on Router A.

<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] interface pos 1/0/0[RouterA-Pos1/0/0] undo shutdown[RouterA-Pos1/0/0] ip address 10.1.1.1 24[RouterA-Pos1/0/0] quit

# Configure the IP address of the interface on Router B.

<HUAWEI> system-view[HUAWEI] sysname RouterB[RouterB] interface pos 1/0/0[RouterB-Pos1/0/0] undo shutdown[RouterB-Pos1/0/0] ip address 10.1.1.2 24[RouterB-Pos1/0/0] quit

Step 2 Configure the one-hop BFD.

# Enable the BFD on Router A, set up the BFD session with Router B and bind the interface toBFD 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] discriminator local 1[RouterA-bfd-session-atob] discriminator remote 2[RouterA-bfd-session-atob] min-tx-interval 10[RouterA-bfd-session-atob] min-rx-interval 10[RouterA-bfd-session-atob] wtr 5[RouterA-bfd-session-atob] commit[RouterA-bfd-session-atob] quit

# Enable the BFD on Router B, set up the BFD session with Router A, and bind the interface tothe BFD session.

[RouterB] bfd




Issue 03 (2010-03-31)

[RouterB-bfd] quit[RouterB] bfd btoa bind peer-ip 10.1.1.1 interface pos 1/0/0[RouterB-bfd-session-btoa] discriminator local 2[RouterB-bfd-session-btoa] discriminator remote 1[RouterB-bfd-session-btoa] min-tx-interval 10[RouterB-bfd-session-btoa] min-rx-interval 10[RouterB-bfd-session-btoa] wtr 5[RouterB-bfd-session-btoa] commit[RouterB-bfd-session-btoa] quit


After the configurations, run the display bfd session all verbose command on Router A andRouter B, and you can view that a one-hop BFD session is set up and its status 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 : 2 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(Pos1/0/0) Bind Session Type : Static Bind Peer Ip Address : 10.1.1.2 NextHop Ip Address : 10.1.1.2 Bind Interface : Pos1/0/0 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- Session Echo Tx TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

----End


# 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 discriminator local 1 discriminator remote 2 min-tx-interval 10 min-rx-interval 10 wtr 5



5-45

commit#return

l Configuration file of Router B# 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 discriminator local 2 discriminator remote 1 min-tx-interval 10 min-rx-interval 10 wtr 5commit#return

5.15.2 Example for Configuring the One-Hop BFD for IP-TrunkMember Link

Networking RequirementsAs shown in Figure 5-4, an IP-Trunk that consists of two POS links exists between Router Aand Router B.

Perform the BFD on the member link POS 1/0/0.

Figure 5-4 Networking diagram of configuring one-hop BFD for IP-Trunk member link

RouterA RouterB

POS1/0/0

IP-Trunk1100.1.1.1/24

IP-Trunk1100.1.1.2/24POS2/0/0

POS1/0/0

POS2/0/0


1. Create an IP-Trunk interface.2. Configure the one-hop BFD for the member link.

Data PreparationTo configure the one-hop BFD for the member link, you need the following data:

l Peer IP address of the BFD, that is, the IP address of the IP-Trunk




Issue 03 (2010-03-31)

l Local member link interface that sends and receives BFD control packets

l Local discriminator and remote discriminator of the BFD session


Procedure

Step 1 Configure an IP-Trunk interface.

# Configure an IP-Trunk interface on Router A and set the lower threshold of the links in theUp state of the IP-Trunk to 1.

<HUAWEI> system-view[HUAWEI] sysname RouterA[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] interface pos 1/0/0[RouterA-Pos1/0/0] undo shutdown[RouterA-Pos1/0/0] link-protocol hdlc[RouterA-Pos1/0/0] ip-trunk 1[RouterA-Pos1/0/0] quit[RouterA] interface pos 2/0/0[RouterA-Pos2/0/0] undo shutdown[RouterA-Pos2/0/0] link-protocol hdlc[RouterA-Pos2/0/0] ip-trunk 1[RouterA-Pos2/0/0] quit

# Configure an IP-Trunk interface on Router B and set the lower threshold of the links in theUp state of the IP-Trunk to 1.

<HUAWEI> system-view[HUAWEI] sysname RouterB[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] interface pos 1/0/0[RouterB-Pos1/0/0] undo shutdown[RouterB-Pos1/0/0] link-protocol hdlc[RouterB-Pos1/0/0] ip-trunk 1[RouterB-Pos1/0/0] quit[RouterB] interface pos 2/0/0[RouterB-Pos2/0/0] undo shutdown[RouterB-Pos2/0/0] link-protocol hdlc[RouterB-Pos2/0/0] ip-trunk 1[RouterB-Pos2/0/0] quit

After the configurations are complete, running the display interface ip-trunk command onRouter A or Router B, you can find that the status of the IP-Trunk is Up.


[RouterA] display interface ip-trunk 1Ip-Trunk1 current state : UPLine protocol current state : UPLast line protocol up time: 2007-11-12, 10:12:19Hash arithmetic : According to flowThe Maximum Transmit Unit is 4470 bytesInternet Address is 100.1.1.1/24Link layer protocol is nonstandard HDLCPhysical is IP_TRUNK



5-47

Last 300 seconds input rate 0 bytes/sec, 0 packets/sec Last 300 seconds output rate 0 bytes/sec, 0 packets/sec Input: 0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops,0 unknownprotocol Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops-----------------------------------------------------PortName Status Weight-----------------------------------------------------Pos1/0/0 UP 1Pos2/0/0 UP 1-----------------------------------------------------The Number of Ports in Trunk : 2The 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 PING 100.1.1.2: 56 data bytes, press CTRL_C to break Reply from 100.1.1.2: bytes=56 Sequence=1 ttl=255 time=310 ms Reply from 100.1.1.2: bytes=56 Sequence=2 ttl=255 time=30 ms Reply from 100.1.1.2: bytes=56 Sequence=3 ttl=255 time=50 ms Reply from 100.1.1.2: bytes=56 Sequence=4 ttl=255 time=40 ms Reply from 100.1.1.2: bytes=56 Sequence=5 ttl=255 time=40 ms --- 100.1.1.2 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 30/94/310 ms

Step 2 Configure the one-hop BFD for the IP-Trunk.

# Configure the BFD session on Router A and Bind the member link interface POS 1/0/0 to theBFD 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] min-tx-interval 10[RouterA-bfd-session-to_Link1] min-rx-interval 10[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 POS 1/0/0 to theBFD 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] min-tx-interval 10[RouterB-bfd-session-to_Link1] min-rx-interval 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, running the display bfd session all verbose commandon Router A or Router B, you can find that a one-hop BFD session is set up and its status is Up.





Issue 03 (2010-03-31)

[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Up Name : to_link1-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(Pos1/0/0) Bind Session Type : Static Bind Peer Ip Address : 224.0.0.184 NextHop Ip Address : 224.0.0.184 Bind Interface : Pos1/0/0 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

Run the shutdown command on POS 1/0/0 of Router A to simulate the link fault.

[RouterA] interface pos 1/0/0[RouterA-Pos1/0/0] shutdown[RouterA-Pos1/0/0] quit

Running the display bfd session all verbose command and the display interface ip-trunkcommand on Router A and Router B, you can find that the status of the BFD session is Downand the status of the IP-Trunk is still Up.

[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Down Name : to_link1-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(Pos1/0/0) Bind Session Type : Static Bind Peer Ip Address : 224.0.0.184 NextHop Ip Address : 224.0.0.184 Bind Interface : Pos1/0/0 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Proc interface status : Disable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Local Demand Mode : Control Detection Time Expired Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0[RouterA] display interface ip-trunk 1Ip-Trunk1 current state : UP



5-49

Line protocol current state : UPLast line protocol up time: 2007-11-11, 11:12:19Hash arithmetic : According to flowThe Maximum Transmit Unit is 4470 bytesInternet Address is 100.1.1.1/24Link layer protocol is nonstandard HDLCPhysical is IP_TRUNK Last 300 seconds input rate 0 bytes/sec, 0 packets/sec Last 300 seconds output rate 0 bytes/sec, 0 packets/sec Input: 0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops,0 unknownprotocol Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops-----------------------------------------------------PortName Status Weight-----------------------------------------------------Pos1/0/0 DOWN 1Pos2/0/0 UP 1-----------------------------------------------------The Number of Ports in Trunk : 2The Number of UP Ports in Trunk : 1

----End


# 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 discriminator local 10 discriminator remote 20 min-tx-interval 10 min-rx-interval 10 wtr 5commit#return

l Configuration file of Router B# sysname RouterB# bfd#interface Ip-Trunk1 undo shutdown ip address 100.1.1.2 255.255.255.0#




Issue 03 (2010-03-31)

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 discriminator local 20 discriminator remote 10 min-tx-interval 10 min-rx-interval 10 wtr 5commit#return

5.15.3 Example for Configuring One-Hop BFD for IP-Trunk

Networking RequirementsAs shown in Figure 5-5, an IP-Trunk that consists of two POS links exists between Router Aand Router B.

Perform the one-hop BFD on the IP-Trunk link.

Figure 5-5 Networking diagram of configuring one-hop BFD for IP-Trunk

RouterBRouterA

POS1/0/0

IP-Trunk1100.1.1.1/24

IP-Trunk1100.1.1.2/24POS2/0/0

POS1/0/0

POS2/0/0


1. Create an IP-Trunk interface.2. Configure the one-hop BFD for IP-Trunk link.

Data PreparationTo configure the one-hop BFD for the IP-Trunk link, you need the following data:

l Peer IP address of the BFD, that is, the IP address of the IP-Trunk

l Local IP-Trunk interface that sends and receives BFD control packets





5-51

Procedure

Step 1 Configure an IP-Trunk interface.

# Create an IP-Trunk interface on Router A and set the lower threshold of the links in the Upstate of the IP-Trunk to 1.

<HUAWEI> system-view[HUAWEI] sysname RouterA[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] interface pos 1/0/0[RouterA-Pos1/0/0] undo shutdown[RouterA-Pos1/0/0] link-protocol hdlc[RouterA-Pos1/0/0] ip-trunk 1[RouterA-Pos1/0/0] quit[RouterA] interface pos 2/0/0[RouterA-Pos2/0/0] undo shutdown[RouterA-Pos2/0/0] link-protocol hdlc[RouterA-Pos2/0/0] ip-trunk 1[RouterA-Pos2/0/0] quit

# Create an IP-Trunk interface on Router B and set the lower threshold of the links in the Upstate of the IP-Trunk to 1.

<HUAWEI> system-view[HUAWEI] sysname RouterB[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] interface pos 1/0/0[RouterB-Pos1/0/0] undo shutdown[RouterB-Pos1/0/0] link-protocol hdlc[RouterB-Pos1/0/0] ip-trunk 1[RouterB-Pos1/0/0] quit[RouterB] interface pos 2/0/0[RouterB-Pos2/0/0] undo shutdown[RouterB-Pos2/0/0] link-protocol hdlc[RouterB-Pos2/0/0] ip-trunk 1[RouterB-Pos2/0/0] quit

After the configurations are complete, running the display interface ip-trunk command onRouter A or Router B, you can find that the status of the interface is Up.


[RouterA] display interface ip-trunk 1Ip-Trunk1 current state : UPLine protocol current state : UPLast line protocol up time: 2007-11-13, 10:18:19Hash arithmetic : According to flowThe Maximum Transmit Unit is 4470 bytesInternet Address is 100.1.1.1/24Link layer protocol is nonstandard HDLCPhysical is IP_TRUNK Last 300 seconds input rate 0 bytes/sec, 0 packets/sec Last 300 seconds output rate 0 bytes/sec, 0 packets/sec Input: 0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops,0 unknownprotocol Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops




Issue 03 (2010-03-31)

-----------------------------------------------------PortName Status Weight-----------------------------------------------------Pos1/0/0 UP 1Pos2/0/0 UP 1-----------------------------------------------------The Number of Ports in Trunk : 2The Number of UP Ports in Trunk : 2

The IP-Trunk interface of Router A and Router B can ping through each other.

Take the results on Router A as an example.

[RouterA] ping 100.1.1.2 PING 100.1.1.2: 56 data bytes, press CTRL_C to break Reply from 100.1.1.2: bytes=56 Sequence=1 ttl=255 time=220 ms Reply from 100.1.1.2: bytes=56 Sequence=2 ttl=255 time=30 ms Reply from 100.1.1.2: bytes=56 Sequence=3 ttl=255 time=10 ms Reply from 100.1.1.2: bytes=56 Sequence=4 ttl=255 time=30 ms Reply from 100.1.1.2: bytes=56 Sequence=5 ttl=255 time=40 ms --- 100.1.1.2 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 10/66/220 ms

Step 2 Configure the one-hop BFD for the IP-Trunk.

# Enable the BFD on Router A, configure the BFD session with Router B and bind the IP-Trunkinterface to the BFD session.

[RouterA] bfd[RouterA-bfd] quit[RouterA] bfd atob bind peer-ip 100.1.1.2 interface ip-trunk 1[RouterA-bfd-session-atob] discriminator local 10[RouterA-bfd-session-atob] discriminator remote 20[RouterA-bfd-session-atob] min-tx-interval 10[RouterA-bfd-session-atob] min-rx-interval 10[RouterA-bfd-session-atob] wtr 5[RouterA-bfd-session-atob] commit[RouterA-bfd-session-atob] quit

# Enable the BFD on Router B, configure the BFD session with Router A and bind the IP-Trunkinterface to the BFD session.

[RouterB] bfd[RouterB-bfd] quit[RouterB] bfd btoa bind peer-ip 100.1.1.1 interface ip-trunk 1[RouterB-bfd-session-btoa] discriminator local 20[RouterB-bfd-session-btoa] discriminator remote 10[RouterB-bfd-session-btoa] min-tx-interval 10[RouterB-bfd-session-btoa] min-rx-interval 10[RouterB-bfd-session-btoa] wtr 5[RouterB-bfd-session-btoa] commit[RouterB-bfd-session-btoa] quit


After the configurations are complete, running the display bfd session all verbose commandon Router A or Router B, you can find that a one-hop BFD session is set up and its status is Up.


[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Up Name : atob-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function



5-53

BFD Bind Type : Interface(Ip-Trunk 1) Bind Session Type : Static Bind Peer Ip Address : 100.1.1.2 NextHop Ip Address : 100.1.1.2 Bind Interface : Ip-Trunk 1 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Local Demand Mode : Disable Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

Run the shutdown command on the POS 1/0/0 of Router A to simulate the link fault.


Running the display bfd session all verbose command and the display interface ip-trunkcommand on Router A and Router B, you can find that the status of the BFD session and thatof the IP-Trunk interface are Up.

[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Up Name : atob-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(Ip-Trunk 1) Bind Session Type : Static Bind Peer Ip Address : 100.1.1.2 NextHop Ip Address : 100.1.1.2 Bind Interface : Ip-Trunk 1 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : Control Detection Time Expired Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0[RouterA] display interface ip-trunk 1Ip-Trunk1 current state : UPLine protocol current state : UPLast line protocol up time: 2007-11-14, 10:12:45Hash arithmetic : According to flowThe Maximum Transmit Unit is 4470 bytesInternet Address is 100.1.1.1/24




Issue 03 (2010-03-31)

Link layer protocol is nonstandard HDLCPhysical is IP_TRUNKLast 300 seconds input rate 0 bytes/sec, 0 packets/secLast 300 seconds output rate 0 bytes/sec, 0 packets/secInput: 0 packets,0 bytes, 0 errors,0 drops Output:0 packets,0 bytes, 0 errors,0 drops -----------------------------------------------------PortName Status Weight-----------------------------------------------------Pos1/0/0 DOWN 1Pos2/0/0 UP 1-----------------------------------------------------The Number of Ports in Trunk : 2The Number of UP Ports in Trunk : 1

Run the shutdown command on POS 2/0/0 of Router A to simulate the link fault.


Running the display bfd session all verbose command and the display interface ip-trunkcommand on Router A and Router B, you can find that the status of the BFD session and thatof the IP-Trunk interface are Down.

[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Down Name : atob-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(Ip-Trunk 1) Bind Session Type : Static Bind Peer Ip Address : 100.1.1.2 NextHop Ip Address : 100.1.1.2 Bind Interface : Ip-Trunk 1 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : Control Detection Time Expired Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0[RouterA] display interface ip-trunk 1Ip-Trunk1 current state : DownLine protocol current state : DownLast line protocol up time: 2007-11-15, 12:12:19Description : HUAWEI, Ip-Trunk1 Interface, Route PortHash arithmetic : According to flowThe Maximum Transmit Unit is 4470 bytesInternet Address is 100.1.1.1/24Link layer protocol is nonstandard HDLCPhysical is IP_TRUNK Last 300 seconds input rate 0 bytes/sec, 0 packets/sec Last 300 seconds output rate 0 bytes/sec, 0 packets/sec Input: 0 packets,0 bytes, 0 errors,0 drops



5-55

Output:0 packets,0 bytes, 0 errors,0 drops -----------------------------------------------------PortName Status Weight-----------------------------------------------------Pos1/0/0 DOWN 1Pos2/0/0 DOWN 1-----------------------------------------------------The Number of Ports in Trunk : 2The Number of UP Ports in Trunk : 0

----End


# 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 discriminator local 10 discriminator remote 20 min-tx-interval 10 min-rx-interval 10 wtr 5commit#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 discriminator local 20 discriminator remote 10




Issue 03 (2010-03-31)

min-tx-interval 10 min-rx-interval 10 wtr 5commit#return

5.15.4 Example for Configuring One-Hop BFD for Layer 3 Eth-Trunk Member Link

Networking RequirementsAs shown in Figure 5-6, an Eth-Trunk that consists of two GE links exists between Router Aand Router B.

Perform the BFD on the GE 1/0/0 of the member link.

Figure 5-6 Networking diagram of configuring one-hop BFD for Layer 3 Eth-Trunk memberlink

RouterA RouterB

GE1/0/0

Eth-Trunk1100.1.1.1/24

Eth-Trunk1100.1.1.2/24GE2/0/0

GE1/0/0

GE2/0/0


1. Create an Eth-Trunk interface.2. Configure the one-hop BFD for the specified member link.

Data PreparationTo configure the one-hop BFD for Layer 3 Eth-Trunk member link, you need the following data:

l Peer IP address of the BFD, that is, the IP address of the Eth-Trunk

l Local member link interface that sends and receives BFD control packets



Procedure

Step 1 Configure an Eth-Trunk interface.

# Create an Eth-Trunk interface on Router A.



5-57

<HUAWEI> system-view[HUAWEI] sysname RouterA[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-Eth-Trunk1] quit[RouterA] interface gigabitethernet 1/0/0[RouterA-GigabitEthernet1/0/0] undo shutdown[RouterA-GigabitEthernet1/0/0] eth-trunk 1[RouterA-GigabitEthernet1/0/0] quit[RouterA] interface gigabitethernet 2/0/0[RouterA-GigabitEthernet2/0/0] undo shutdown[RouterA-GigabitEthernet2/0/0] eth-trunk 1[RouterA-GigabitEthernet2/0/0] quit

# Create an Eth-Trunk interface on Router B.<HUAWEI> system-view[HUAWEI] sysname RouterB[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] interface gigabitethernet 1/0/0[RouterB-GigabitEthernet1/0/0] undo shutdown[RouterB-GigabitEthernet1/0/0] eth-trunk 1[RouterB-GigabitEthernet1/0/0] quit[RouterB] interface gigabitethernet 2/0/0[RouterB-GigabitEthernet2/0/0] undo shutdown[RouterB-GigabitEthernet2/0/0] eth-trunk 1[RouterB-GigabitEthernet2/0/0] quit

After the above configurations, running the display interface eth-trunk command on RouterA or Router B, you can find that the status of the interface is Up.

Take the display on Route A as an example.[RouterA] display interface eth-trunk 1Eth-Trunk1 current state : UPLine protocol current state : UPLast line protocol up time: 2007-11-10, 11:35:19Hash arithmetic : According to flowThe Maximum Transmit Unit is 1500 bytesInternet Address is 100.1.1.1/24IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-271e-f652Physical is ETH_TRUNK Last 300 seconds input rate 0 bytes/sec, 0 packets/sec Last 300 seconds output rate 0 bytes/sec, 0 packets/sec Input: 0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops,0 unknownprotocol Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops -----------------------------------------------------PortName Status Weight-----------------------------------------------------GigabitEthernet1/0/0 UP 1GigabitEthernet2/0/0 UP 1-----------------------------------------------------The Number of Ports in Trunk : 2The Number of UP Ports in Trunk : 2

The Eth-Trunk interfaces of Router A and Router B can ping through each other.[RouterA] ping -a 100.1.1.1 100.1.1.2 PING 100.1.1.2: 56 data bytes, press CTRL_C to break Reply from 100.1.1.2: bytes=56 Sequence=1 ttl=255 time=31 ms




Issue 03 (2010-03-31)

Reply from 100.1.1.2: bytes=56 Sequence=2 ttl=255 time=31 ms Reply from 100.1.1.2: bytes=56 Sequence=3 ttl=255 time=62 ms Reply from 100.1.1.2: bytes=56 Sequence=4 ttl=255 time=62 ms Reply from 100.1.1.2: bytes=56 Sequence=5 ttl=255 time=62 ms --- 100.1.1.2 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 31/49/62 ms

Step 2 Configure the one-hop BFD for the Layer 3 Eth-Trunk member link.

# Configure the BFD session on Router A and bind the member link interface GE 1/0/0.

[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] min-tx-interval 10[RouterA-bfd-session-to_link1] min-rx-interval 10[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] min-tx-interval 10[RouterB-bfd-session-to_link1] min-rx-interval 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, running the display bfd session all verbose commandon Route A and Route B, you can find that the one-hop BFD session is set up and its status isUp.

Take the display on Route A as an example.

[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Up Name : to_link1-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 11 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet1/0/0) Bind Session Type : Static Bind Peer Ip Address : 224.0.0.184 NextHop Ip Address : 224.0.0.184 Bind Interface : GigabitEthernet1/0/0 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : --



5-59

Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

Running the shutdown command on GE 1/0/0 of Router A to simulate the link fault, you canfind that the BFD session is in the Down state and the Eth-Trunk status is still in the Up state.

[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Down Name : to_link1-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 11 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet1/0/0) Bind Session Type : Static Bind Peer Ip Address : 224.0.0.184 NextHop Ip Address : 224.0.0.184 Bind Interface : GigabitEthernet1/0/0 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : Control Detection Time Expired Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0[RouterA] display interface eth-trunk 1Eth-Trunk1 current state : UPLine protocol current state : UPLast line protocol up time: 2007-11-23, 11:52:49Hash arithmatic : According to flowThe Maximum Transmit Unit is 1500 bytesInternet Address is 100.1.1.1/24IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc09-9722Physical is ETH_TRUNK Last 300 seconds input rate bytes/sec, 0 packets/sec Last 300 seconds output rate 0 bytes/sec, 0 packets/sec Input: 0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops,0 unknownprotocol Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops -----------------------------------------------------PortName Status Weight-----------------------------------------------------GigabitEthernet1/0/0 DOWN 1GigabitEthernet2/0/0 UP 1-----------------------------------------------------The Number of Ports in Trunk : 2The Number of UP Ports in Trunk : 1

----End





Issue 03 (2010-03-31)

# sysname RouterA# bfd#interface Eth-Trunk1 undo shutdown ip address 100.1.1.1 255.255.255.0#interface GigabitEthernet1/0/0 undo shutdown eth-trunk 1#interface GigabitEthernet2/0/0 undo shutdown eth-trunk 1#bfd to_link1 bind peer-ip default-ip interface GigabitEthernet 1/0/0 discriminator local 10 discriminator remote 11 min-tx-interval 10 min-rx-interval 10 wtr 5commit#return

l Configuration file of Router B# sysname RouterB# bfd#interface Eth-Trunk1 undo shutdown ip address 100.1.1.2 255.255.255.0#interface GigabitEthernet1/0/0 undo shutdown eth-trunk 1#interface GigabitEthernet2/0/0 undo shutdown eth-trunk 1#bfd to_link1 bind peer-ip default-ip interface GigabitEthernet 1/0/0 discriminator local 11 discriminator remote 10 min-tx-interval 10 min-rx-interval 10 wtr 5commit#return

5.15.5 Example for Configuring One-Hop BFD for Layer 3 Eth-Trunk

Networking requirements

As shown in Figure 5-7, an Eth-Trunk that consists of two GE links exists between Route Aand Route B.

Perform the BFD on the Eth-Trunk link.



5-61

Figure 5-7 Networking diagram of configuring one-hop BFD for Layer 3 Eth-Trunk

RouterA RouterB

GE1/0/0

Eth-Trunk1100.1.1.1/24

Eth-Trunk1100.1.1.2/24GE2/0/0

GE1/0/0

GE2/0/0


1. Create an Eth-Trunk interface.2. Configure the one-hop BFD for the Eth-Trunk link.

Data PreparationTo configure the one-hop BFD for the Layer 3 Eth-Trunk, you need the following data:

l Peer IP address of the BFD, that is, the IP address of the Eth-Trunk

l Local Eth-Trunk interface that sends and receives BFD control packets



Procedure

Step 1 Configure an Eth-Trunk interface.

# Create an Eth-Trunk interface on Router A and set the lower threshold of the Up links of theEth-Trunk to 1.

<HUAWEI> system-view[HUAWEI] sysname RouterA[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-Eth-Trunk1] quit[RouterA] interface gigabitethernet 1/0/0[RouterA-GigabitEthernet1/0/0] undo shutdown[RouterA-GigabitEthernet1/0/0] eth-trunk 1[RouterA-GigabitEthernet1/0/0] quit[RouterA] interface gigabitethernet 2/0/0[RouterA-GigabitEthernet2/0/0] undo shutdown[RouterA-GigabitEthernet2/0/0] eth-trunk 1[RouterA-GigabitEthernet2/0/0] quit

# Create an Eth-Trunk interface on Router B and set the lower threshold of the Up links of theEth-Trunk to 1.

<HUAWEI> system-view[HUAWEI] sysname RouterB




Issue 03 (2010-03-31)

[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] interface gigabitethernet 1/0/0[RouterB-GigabitEthernet1/0/0] undo shutdown[RouterB-GigabitEthernet1/0/0] eth-trunk 1[RouterB-GigabitEthernet1/0/0] quit[RouterB] interface gigabitethernet 2/0/0[RouterB-GigabitEthernet2/0/0] undo shutdown[RouterB-GigabitEthernet2/0/0] eth-trunk 1[RouterB-GigabitEthernet2/0/0] quit

After these configurations are complete, running the display interface eth-trunk command onRouter A or Router B, you can find that the status of the interface is Up.


[RouterA] display interface eth-trunk 1Eth-Trunk1 current state : UPLine protocol current state : UPLast line protocol up time: 2007-11-19, 12:17:09Hash arithmetic : According to flowThe Maximum Transmit Unit is 1500 bytesInternet Address is 100.1.1.1/24IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-271e-f652Physical is ETH_TRUNK Last 300 seconds input rate 0 bytes/sec, 0 packets/sec Last 300 seconds output rate 0 bytes/sec, 0 packets/sec Input: 0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops,0 unknownprotocol Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops-----------------------------------------------------PortName Status Weight-----------------------------------------------------GigabitEthernet1/0/0 UP 1GigabitEthernet2/0/0 UP 1-----------------------------------------------------The Number of Ports in Trunk : 2The Number of UP Ports in Trunk : 2

The Eth-Trunks of Router A and Router B can ping though each other.


Step 2 Configure the one-hop BFD for Layer 3 Eth-Trunk link.

# Enable the BFD on Router A, configure the BFD session with Router B and bind the Eth-Trunk to the BFD session.

[RouterA] bfd[RouterA-bfd] quit[RouterA] bfd atob bind peer-ip 100.1.1.2 interface eth-trunk 1[RouterA-bfd-session-atob] discriminator local 10



5-63

[RouterA-bfd-session-atob] discriminator remote 20[RouterA-bfd-session-atob] min-tx-interval 10[RouterA-bfd-session-atob] min-rx-interval 10[RouterA-bfd-session-atob] wtr 5[RouterA-bfd-session-atob] commit[RouterA-bfd-session-atob] quit

# Enable the BFD on Router B, configure the BFD session with Router A and bind the Eth-Trunk to the BFD session.[RouterB] bfd[RouterB-bfd] quit[RouterB] bfd btoa bind peer-ip 100.1.1.1 interface eth-trunk 1[RouterB-bfd-session-btoa] discriminator local 20[RouterB-bfd-session-btoa] discriminator remote 10[RouterB-bfd-session-btoa] min-tx-interval 10[RouterB-bfd-session-btoa] min-rx-interval 10[RouterB-bfd-session-btoa] wtr 5[RouterB-bfd-session-btoa] commit[RouterB-bfd-session-btoa] quit


After the configurations are complete, running the display bfd session all verbose commandon Router A and Router B, you can find a one-hop BFD session is set up and its status 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 : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(Eth-Trunk1) Bind Session Type : Static Bind Peer Ip Address : 100.1.1.2 NextHop Ip Address : 100.1.1.2 Bind Interface : Eth-Trunk1 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

Run the shutdown command on the GE 1/0/0 of Router A to simulate the link fault.[RouterA] interface gigabitethernet 1/0/0[RouterA-GigabitEthernet1/0/0] shutdown[RouterA-GigabitEthernet1/0/0] quit

Running the display bfd session all verbose command and the display interface eth-trunkcommand on Router A and Router B, you can find that the status of the BFD session and theEth-Trunk is still Up.[RouterA] display bfd session all verbose--------------------------------------------------------------------------------




Issue 03 (2010-03-31)

Session MIndex : 256 (One Hop) State : Up Name : atob-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(Eth-Trunk1) Bind Session Type : Static Bind Peer Ip Address : 100.1.1.2 NextHop Ip Address : 100.1.1.2 Bind Interface : Eth-Trunk1 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0[RouterA] display interface eth-trunk 1Eth-Trunk1 current state : UPLine protocol current state : UPLast line protocol up time: 2007-11-17, 10:15:34Hash arithmatic : According to flowThe Maximum Transmit Unit is 1500 bytesInternet Address is 100.1.1.1/24IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc09-9722Physical is ETH_TRUNK Last 300 seconds input rate bytes/sec, 0 packets/sec Last 300 seconds output rate 0 bytes/sec, 0 packets/sec Input: 0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops,0 unknownprotocol Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops-----------------------------------------------------PortName Status Weight-----------------------------------------------------GigabitEthernet1/0/0 DOWN 1GigabitEthernet2/0/0 UP 1-----------------------------------------------------The Number of Ports in Trunk : 2The Number of UP Ports in Trunk : 1

Run the shutdown command on the GE 2/0/0 of Router A to simulate the link fault.

Running the display bfd session all verbose command and the display interface eth-trunkcommand on Router A and Router B, you can find that status of the BFD session and that of theEth-Trunk interface become Down.

[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Down Name : atob-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(Eth-Trunk1) Bind Session Type : Static Bind Peer Ip Address : 100.1.1.2 NextHop Ip Address : 100.1.1.2 Bind Interface : Eth-Trunk1



5-65

FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : Control Detection Time Expired Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0[RouterA] display interface eth-trunk 1Eth-Trunk1 current state : DownLine protocol current state : DownLast line protocol up time: 2007-11-09, 10:45:18Hash arithmatic : According to flowThe Maximum Transmit Unit is 1500 bytesInternet Address is 100.1.1.1/24IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc09-9722Physical is ETH_TRUNK Last 300 seconds input rate bytes/sec, 0 packets/sec Last 300 seconds output rate 0 bytes/sec, 0 packets/sec Input: 0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops,0 unknownprotocol Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicasts 0 errors,0 drops-----------------------------------------------------PortName Status Weight-----------------------------------------------------GigabitEthernet1/0/0 DOWN 1GigabitEthernet2/0/0 DOWN 1-----------------------------------------------------The Number of Ports in Trunk : 2The Number of UP Ports in Trunk : 0

----End


# sysname RouterA# bfd#interface Eth-Trunk1 undo shutdown ip address 100.1.1.1 255.255.255.0#interface GigabitEthernet1/0/0 undo shutdown eth-trunk 1#interface GigabitEthernet2/0/0 undo shutdown eth-trunk 1#bfd atob bind peer-ip 100.1.1.2 interface Eth-Trunk 1 discriminator local 10 discriminator remote 20




Issue 03 (2010-03-31)

min-tx-interval 10 min-rx-interval 10 wtr 5commit#return

l Configuration file of Router B# sysname RouterB# bfd#interface Eth-Trunk1 undo shutdown ip address 100.1.1.2 255.255.255.0#interface GigabitEthernet1/0/0 undo shutdown eth-trunk 1#interface GigabitEthernet2/0/0 undo shutdown eth-trunk 1#bfd btoa bind peer-ip 100.1.1.1 interface Eth-Trunk 1 discriminator local 20 discriminator remote 10 min-tx-interval 10 min-rx-interval 10 wtr 5commit#return

5.15.6 Example for Configuring One-Hop BFD for VLANIFInterfaces

Networking RequirementsAs shown in Figure 5-8, one Ethernet link that belongs to the same VLANIF exists betweenRoute A and Router B.

NOTE

The VLAN between two directly-connected routers should apply one link.

Figure 5-8 Networking diagram of configuring one-hop BFD for VLANIF interfaces

RouterA RouterB

GE1/0/0 GE1/0/0VLANIF10: 110.1.1.1/24 VLANIF10: 110.1.1.2/24

Configuration RoadmapsThe configuration roadmap is as follows:



5-67

1. Configure the VLAN that is based on the interface.2. Configure the one-hop BFD for the VLANIF.

Data PreparationTo configure the one-hop BFD for the VLANIF, you need the following data:

l Peer IP address of the BFD, that is, the IP address of the VLANIF interface

l Local VLANIF interface that sends and receives BFD control packets



Procedure

Step 1 Configure VLAN 10.

# Configure VLAN 10 on Router A.

<RouterA> system-view[HUAWEI] sysname RouterA[RouterA] interface gigabitethernet 1/0/0[RouterA-GigabitEthernet1/0/0] undo shutdown[RouterA-GigabitEthernet1/0/0] portswitch[RouterA-GigabitEthernet1/0/0] quit[RouterA] vlan 10[RouterA-vlan10] port gigabitethernet 1/0/0[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> system-view[HUAWEI] sysname RouterB[RouterB] interface gigabitethernet 1/0/0[RouterB-GigabitEthernet1/0/0] undo shutdown[RouterB-GigabitEthernet1/0/0] portswitch[RouterB-GigabitEthernet1/0/0] quit[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,and you can view that the interface is Up.

Take the display onRouter A as an example.

[RouterA] display interface vlanif 10Vlanif10 current state : UPLine protocol current state : UPLast line protocol up time: 2007-11-23, 13:11:19Description : Vlanif10 Interface, Route PortThe Maximum Transmit Unit is 1500 bytesInternet Address is 110.1.1.1/24IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc7a-9e35




Issue 03 (2010-03-31)

Physical is VLANIF Last 300 seconds input rate 0 bits/sec, 0 packets/sec Last 300 seconds output rate 0 bits/sec, 0 packets/sec Input: 0 packets,0 bytes, 0 unicast,0 broadcast,0 multicast Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicast

The VLANIF interfaces on Router A and Router B can ping through each other.


Step 2 Configure the one-hop BFD for the VLANIF.

# Enable the BFD on Router A, configure the BFD session with Router B and bind the VLANIFinterface to the BFD session.

[RouterA] bfd[RouterA-bfd] quit[RouterA] bfd atob bind peer-ip 110.1.1.2 interface vlanif 10[RouterA-bfd-session-atob] discriminator local 10[RouterA-bfd-session-atob] discriminator remote 20[RouterA-bfd-session-atob] commit[RouterA-bfd-session-atob] quit

# Enable the BFD on Router B, configure the BFD session with Router A and bind the VLANIFinterface to the BFD session.

[RouterB] bfd[RouterB-bfd] quit[RouterB] bfd btoa bind peer-ip 110.1.1.1 interface vlanif 10[RouterB-bfd-session-btoa] discriminator local 20[RouterB-bfd-session-btoa] discriminator remote 10[RouterB-bfd-session-btoa] commit[RouterB-bfd-session-btoa] quit


After the configurations are complete, run the display bfd session all verbose command onRouter A and Router B, you can view that a one-hop BFD session is set up and its status is Up.


[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Up Name : atob-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(Vlanif10) Bind Session Type : Static Bind Peer Ip Address : 110.1.1.2 NextHop Ip Address : 110.1.1.2 Bind Interface : Vlanif10 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30



5-69

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 : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

Step 4 [RouterA] interface gigabitethernet 1/0/0[RouterA-GigabitEthernet1/0/0] shutdown[RouterA-GigabitEthernet1/0/0] quit

Run the display bfd session all verbose command on Router A and Router B, and you can viewthat the status of the BFD session goes Down.


[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 256 (One Hop) State : Down Name : atob-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(Vlanif10) Bind Session Type : Static Bind Peer Ip Address : 110.1.1.2 NextHop Ip Address : 110.1.1.2 Bind Interface : Vlanif10 FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 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 : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

----End


# sysname RouterA# vlan batch 10# bfd#interface Vlanif10 undo shutdown ip address 110.1.1.1 255.255.255.0#




Issue 03 (2010-03-31)

interface GigabitEthernet1/0/0 undo shutdown portswitch port default vlan 10#bfd atob bind peer-ip 110.1.1.2 interface vlanif 10 discriminator local 10 discriminator remote 20 commit#return

l Configuration file of Router B# sysname RouterB# vlan batch 10# bfd#interface Vlanif10 undo shutdown ip address 110.1.1.2 255.255.255.0#interface GigabitEthernet1/0/0 undo shutdown portswitch port default vlan 10#bfd btoa bind peer-ip 110.1.1.1 interface vlanif 10 discriminator local 20 discriminator remote 10 commit#return

5.15.7 Example for Configuring the Association Between the BFDStatus and the Interface Status


As shown in Figure 5-9, transmission devices exist on the link. By configuring the associationbetween the BFD status and the interface status, the status change of the BFD session betweenGE 1/0/0 of Router A and GE 1/0/0 of Router B can affect the protocol status of the interface,and can trigger the fast convergence of routes when the link between transmission devices fails.

Figure 5-9 Configuring the association between the BFD status and the interface status

RouterA RouterB

GE1/0/0GE1/0/0



1. Configure a BFD session on Router A.



5-71

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.


l Peer IP address detected by BFD

l Local interface that sends and receives BFD Control packets



Procedure

Step 1 Configure the IP address of the interface that directly connects Router A to Router B.

# Configure the IP address of the interface on Router A.

<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] interface gigabitethernet 1/0/0[RouterA-GigabitEthernet1/0/0] undo shutdown[RouterA-GigabitEthernet1/0/0] ip address 10.1.1.1 24[RouterA-GigabitEthernet1/0/0] quit

# Configure the IP address of the interface on Router B.

<HUAWEI> system-view[HUAWEI] sysname RouterB[RouterB] interface gigabitethernet 1/0/0[RouterB-GigabitEthernet1/0/0] undo shutdown[RouterB-GigabitEthernet1/0/0] ip address 10.1.1.2 24[RouterB-GigabitEthernet1/0/0] quit

Step 2 Configure the one-hop BFD detection.

# On Router A, enable BFD and configure the 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[RouterA-bfd-session-atob] discriminator local 10[RouterA-bfd-session-atob] discriminator remote 20[RouterA-bfd-session-atob] min-tx-interval 10[RouterA-bfd-session-atob] min-rx-interval 10[RouterA-bfd-session-atob] wtr 5[RouterA-bfd-session-atob] commit[RouterA-bfd-session-atob] quit

# On Router B, enable BFD and configure the 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[RouterB-bfd-session-btoa] discriminator local 20[RouterB-bfd-session-btoa] discriminator remote 10[RouterB-bfd-session-btoa] min-tx-interval 10




Issue 03 (2010-03-31)

[RouterB-bfd-session-btoa] min-rx-interval 10[RouterB-bfd-session-btoa] wtr 5[RouterB-bfd-session-btoa] commit[RouterB-bfd-session-btoa] quit

# After the configuration, run the display bfd session all verbose command on Router A andRouter B, and you can view that a one-hop BFD session is established. The session is in the Upstate. Take Router A as an example:

[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 16384 (One Hop) State : Up Name : atob-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet1/0/0) Bind Session Type : Static Bind Peer Ip Address : 224.0.0.184 NextHop Ip Address : 224.0.0.184 Bind Interface : GigabitEthernet1/0/0 FSM Board Id : 3 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Disable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-5000000|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

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[RouterA-bfd] quit[RouterA] bfd atob [RouterA-bfd-session-atob] process-interface-status[RouterA-bfd-session-atob] commit[RouterA-bfd-session-atob] quit

# Configure the association between the BFD status and the interface status on Router B.

[RouterB] bfd[RouterB-bfd] quit[RouterB] bfd btoa [RouterB-bfd-session-btoa] process-interface-status[RouterB-bfd-session-btoa] commit[RouterB-bfd-session-btoa] quit


After the configuration is complete, run the display bfd session all verbose command on RouterA and Router B, and you can view that the field Proc interface status displays Enable.

Take Router A as an example.

[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 16384 (One Hop) State : Up Name : atob--------------------------------------------------------------------------------



5-73

Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet1/0/0) Bind Session Type : Static Bind Peer Ip Address : 224.0.0.184 NextHop Ip Address : 224.0.0.184 Bind Interface : GigabitEthernet1/0/0 FSM Board Id : 3 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Enable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : No Diagnostic Bind Application :IFNET Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-5000000|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

Run the shutdown command on GE 1/0/0 of Router B to terminate the BFD session.

[RouterB] interface gigabitethernet 1/0/0[RouterB-GigabitEthernet1/0/0] shutdown[RouterB-GigabitEthernet1/0/0] quit

Run the display bfd session all verbose and display interface gigabitethernet 1/0/0 commandson Router A, and you can view that the status of the BFD session is Down, and the status of GE1/0/0 is UP (BFD status down).

[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 16384 (One Hop) State : Down Name : atob-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet1/0/0) Bind Session Type : Static Bind Peer Ip Address : 224.0.0.184 NextHop Ip Address : 224.0.0.184 Bind Interface : GigabitEthernet1/0/0 FSM Board Id : 3 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Enable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : Neighbor Signaled Session Down Bind Application : IFNET Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-5000000|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0[RouterA] display interface gigabitethernet 1/0/0GigabitEthernet1/0/0 current state : UPLine protocol current state : UP(BFD status down)Last line protocol up time: 2008-10-16 09:25:17Description : HUAWEI, GigabitEthernet1/0/0 Interface, Route PortThe Maximum Transmit Unit is 1500 bytes




Issue 03 (2010-03-31)

Internet Address is 10.1.1.1/24IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fcc7-565aThe Vendor PN is HFBR-5710LPort BW: 1G, Transceiver max BW: 1G, Transceiver Mode: MultiModeWaveLength: 850nm, Transmission Distance: 550mLoopback:none, full-duplex mode, negotiation: disable, Pause Flowcontrol:Send and Receive EnableLast physical up time : 2008-10-16 09:18:48Last physical down time : 2008-10-16 09:18:42Statistics 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: Unicast: 8622 packets, Multicast: 5293 packets Broadcast: 11 packets, Jumbo: 0 packets Lost: 0 packets, Overflow: 0 packets, Underrun: 0 packets TxPause: 0 packets Unknown Vlan: 0 packets

----End


# sysname RouterA# bfd#interface GigabitEthernet1/0/0 undo shutdown ip address 10.1.1.1 255.255.255.0#bfd atob bind peer-ip default-ip interface GigabitEthernet1/0/0 discriminator local 10 discriminator remote 20 min-tx-interval 10 min-rx-interval 10 wtr 5 process-interface-status commit#return

l Configuration file of Router B# sysname RouterB# bfd#interface GigabitEthernet1/0/0 undo shutdown ip address 10.1.1.2 255.255.255.0#bfd btoa bind peer-ip default-ip interface GigabitEthernet1/0/0 discriminator local 20 discriminator remote 10 min-tx-interval 10



5-75

min-rx-interval 10 wtr 5 process-interface-status commit#return

5.15.8 Example for Configuring the Association Between the BFDStatus and the Sub-Interface Status


As shown in Figure 5-10, in the large-scale MAN Ethernet network that has high requirementsfor reliability, a large number of services need to be configured on the sub-interface. You canset up BFD sessions to detect the connectivity of the main interface link and configure theassociation between the BFD status and the sub-interface status. This can improve the reliabilityof the service on the sub-interface and save the session resources.

Figure 5-10 Association between the BFD status and the sub-interface status

RouterA RouterB

GE1/0/0 GE1/0/0

GE1/0/0.1 GE1/0/0.1



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 sub-interface status when theBFD session on Router A is Up.

4. Configure the association between the BFD status and the sub-interface status when theBFD session on Router B is Up.

Data Preparation

To configure the association between the BFD status and the sub-interface status, you need thefollowing data:

l IP address of the main interface on the remote end detected by BFD

l Local interface that sends and receives BFD Control packets






Issue 03 (2010-03-31)

ProcedureStep 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.<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] interface gigabitethernet 1/0/0[RouterA-GigabitEthernet1/0/0] undo shutdown[RouterA-GigabitEthernet1/0/0] ip address 10.1.1.1 24[RouterA-GigabitEthernet1/0/0] quit[RouterA] interface gigabitethernet 1/0/0.1[RouterA-GigabitEthernet1/0/0.1] undo shutdown[RouterA-GigabitEthernet1/0/0.1] ip address 11.1.1.1 24[RouterA-GigabitEthernet1/0/0.1] vlan-type dot1q 10[RouterA-GigabitEthernet1/0/0.1] quit

# Configure the IP address of the interface on Router B and create the sub-interface.<HUAWEI> system-view[HUAWEI] sysname RouterB[RouterB] interface gigabitethernet 1/0/0[RouterB-GigabitEthernet1/0/0] undo shutdown[RouterB-GigabitEthernet1/0/0] ip address 10.1.1.2 24[RouterB-GigabitEthernet1/0/0] quit[RouterB] interface gigabitethernet 1/0/0.1[RouterB-GigabitEthernet1/0/0.1] undo shutdown[RouterB-GigabitEthernet1/0/0.1] ip address 11.1.1.2 24[RouterB-GigabitEthernet1/0/0.1] vlan-type dot1q 10[RouterB-GigabitEthernet1/0/0.1] quit

Step 2 Configure the one-hop BFD detection.

# On Router A, enable BFD and configure the BFD session between Router A and Router B andbind the session with the main interface.[RouterA] bfd[RouterA-bfd] quit[RouterA] bfd atob bind peer-ip default-ip interface gigabitethernet 1/0/0[RouterA-bfd-session-atob] discriminator local 10[RouterA-bfd-session-atob] discriminator remote 20[RouterA-bfd-session-atob] min-tx-interval 10[RouterA-bfd-session-atob] min-rx-interval 10[RouterA-bfd-session-atob] commit[RouterA-bfd-session-atob] quit

# On Router B, enable BFD and configure the BFD session between Router B and Router A andbind the session with the main interface.[RouterB] bfd[RouterB-bfd] quit[RouterB] bfd btoa bind peer-ip default-ip interface gigabitethernet 1/0/0[RouterB-bfd-session-btoa] discriminator local 20[RouterB-bfd-session-btoa] discriminator remote 10[RouterB-bfd-session-btoa] min-tx-interval 10[RouterB-bfd-session-btoa] min-rx-interval 10[RouterB-bfd-session-btoa] commit[RouterB-bfd-session-btoa] quit

# After the configuration is complete, run the display bfd session all verbose command onRouter A and Router B, and you can view that a one-hop BFD session is set up, and the sessionstatus is Up.

Take the display on Router A as an example.[RouterA] display bfd session all verbose



5-77

--------------------------------------------------------------------------------Session MIndex : 16384 (One Hop) State : Up Name : atob-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet1/0/0) Bind Session Type : Static Bind Peer Ip Address : 224.0.0.184 NextHop Ip Address : 224.0.0.184 Bind Interface : GigabitEthernet1/0/0 FSM Board Id : 3 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 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 : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- Session Echo Tx TmrID : -- PDT Index : FSM-5000000|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

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[RouterA-bfd] quit[RouterA] bfd atob [RouterA-bfd-session-atob] process-interface-status sub-if[RouterA-bfd-session-atob] commit[RouterA-bfd-session-atob] quit

# Configure the association between the BFD status and the sub-interface status on Router B.

[RouterB] bfd[RouterB-bfd] quit[RouterB] bfd btoa [RouterB-bfd-session-btoa] process-interface-status sub-if[RouterB-bfd-session-btoa] commit[RouterB-bfd-session-btoa] quit


# After the configuration is complete, run the display bfd session all verbose command onRouter A and Router B, and you can view that the field Proc interface status displays Enable(Sub-If).


[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 16384 (One Hop) State : Up Name : atob-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet1/0/0) Bind Session Type : Static Bind Peer Ip Address : 224.0.0.184 NextHop Ip Address : 224.0.0.184 Bind Interface : GigabitEthernet1/0/0 FSM Board Id : 3 TOS-EXP : 7




Issue 03 (2010-03-31)

Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 255 Proc interface status : Enable (Sub-If) Process PST : Disable WTR Interval (ms) : -- Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : No Diagnostic Bind Application : IFNET Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- Session Echo Tx TmrID : -- PDT Index : FSM-5000000|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

# Run the shutdown command on GE 1/0/0 of Router B to shut BFD sessions Down.

[RouterB] interface gigabitethernet 1/0/0[RouterB-GigabitEthernet1/0/0] shutdown[RouterB-GigabitEthernet1/0/0] quit

# Run the display bfd session all verbose and display interface gigabitethernet1/0/0.1commands on Router A, and you can view that the status of the BFD session is Down, and thestatus of GE1/0/0.1 is UP (Main BFD status down).

[RouterA] display bfd session all verbose--------------------------------------------------------------------------------Session MIndex : 16384 (One Hop) State : Down Name : atob-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet1/0/0) Bind Session Type : Static Bind Peer Ip Address : 224.0.0.184 Bind Interface : GigabitEthernet1/0/0 FSM Board Id : 3 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 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 : Neighbor Signaled Session Down Bind Application : IFNET Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- Session Echo Tx TmrID : -- PDT Index : FSM-5000000|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0 [RouterA] display interface gigabitethernet 1/0/0.1GigabitEthernet1/0/0.1 current state : UPLine protocol current state : UP(Main BFD status down)Last line protocol up time: 2007-11-10, 11:09:19Route Port,The Maximum Transmit Unit is 1500 bytesInternet Address is 11.1.1.1/24IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fcc7-565aEncapsulation dot1q Virtual LAN, Vlan number 1 Last 300 seconds input rate 0 bytes/sec, 0 packets/sec Last 300 seconds output rate 0 bytes/sec, 0 packets/sec Input: 0 packets,0 bytes, 0 unicast,0 broadcast,0 multicast 0 errors,0 drops



5-79

Output:0 packets,0 bytes, 0 unicast,0 broadcast,0 multicast 0 errors,0 drops

----End


# sysname RouterA# bfd#interface GigabitEthernet1/0/0 undo shutdown ip address 10.1.1.1 255.255.255.0#interface GigabitEthernet1/0/0.1 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 discriminator local 10 discriminator remote 20 min-tx-interval 10 min-rx-interval 10 process-interface-status sub-if commit#return

l Configuration file of Router B# sysname RouterB# bfd#interface GigabitEthernet1/0/0 undo shutdown ip address 11.1.1.2 255.255.255.0#interface GigabitEthernet1/0/0.1 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 discriminator local 20 discriminator remote 10 min-tx-interval 10 min-rx-interval 10 process-interface-status sub-ifcommit#return

5.15.9 Example for Configuring Multi-Hop BFD


As shown in Figure 5-11, the asynchronous mode of the BFD is used to detect the multi-hoproutes between Router A and Router C.




Issue 03 (2010-03-31)

Figure 5-11 Networking diagram of the multi-hop BFD

RouterA RouterCRouterB

POS1/0/010.1.1.1/24

POS1/0/010.1.1.2/24

POS2/0/010.2.1.1/24

POS1/0/010.2.1.2/24


1. Configure a BFD session on Router A to detect the multi-hop routes between Router A andRouter C.

2. Configure a BFD session on Router C to detect the multi-hop routes between Router C andRouter A.





Procedure

Step 1 Configure the reachable routes between Router A, Router B, and Router C.

In this example, the static route is used. The detailed configuration is not mentioned here.

Step 2 Configure the multi-hop detection between Router A and Router C.

# Configure a BFD session with Router C on Router A.

You do not need to bind the interface.

<RouterA> system-view[RouterA] bfd[RouterA-bfd] quit[RouterA] bfd atoc bind peer-ip 10.2.1.2[RouterA-bfd-session-atoc] discriminator local 10[RouterA-bfd-session-atoc] discriminator remote 20[RouterA-bfd-session-atoc] min-tx-interval 10[RouterA-bfd-session-atoc] min-rx-interval 10[RouterA-bfd-session-atoc] wtr 10[RouterA-bfd-session-atoc] commit[RouterA-bfd-session-atoc] quit

# Configure a BFD session with Router A on Router C.

You do not need to bind the interface.

<RouterC> system-view[RouterC] bfd[RouterC-bfd] quit



5-81

[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] min-tx-interval 10[RouterC-bfd-session-ctoa] min-rx-interval 10[RouterC-bfd-session-ctoa] wtr 10[RouterC-bfd-session-ctoa] commit[RouterC-bfd-session-ctoa] quit


After the configurations are complete, running the display bfd session all verbose commandon Router A and Router C, you can view that a multi-hop BFD session is set up and its status isUp.

Take the display on Router A as an example.<RouterA> display bfd session all--------------------------------------------------------------------------------Session MIndex : 256 (Multi Hop) State : Up Name : atoc-------------------------------------------------------------------------------- Local Discriminator : 10 Remote Discriminator : 20 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Peer Ip Address Bind Session Type : Static Bind Peer Ip Address : 10.2.1.2 Bind Interface : -- FSM Board Id : 1 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 254 Proc interface status : Disable Process PST : Disable WTR Interval (ms) : 600000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : -- Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : -- -------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

----End


# 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 discriminator local 10 discriminator remote 20 min-tx-interval 10 min-rx-interval 10 wtr 10 commit#




Issue 03 (2010-03-31)

ip route-static 10.2.1.0 255.255.255.0 10.1.1.2#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.2.1.1 255.255.255.0#return

l Configuration file of Router C# 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 discriminator local 20 discriminator remote 10 min-tx-interval 10 min-rx-interval 10 wtr 10 commit# ip route-static 10.1.1.0 255.255.255.0 10.2.1.1#return

5.15.10 Example for Configuring the BFD for VPN Routes

Networking RequirementsFigure 5-12 shows a networking diagram of configuring the BFD for VPN routes.

l CE1 and CE2 belong to VPN-A. They access the MPLS backbone network through PE1and 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 the VPN route between PE1 and PE2.



5-83

Figure 5-12 Networking diagram of configuring the BFD for VPN routes

POS2/0/0172.1.1.1/24GE1/0/0

10.1.1.2/24

POS1/0/0172.1.1.2/24

POS2/0/0172.2.1.1/24

POS2/0/0172.2.1.2/24

GE1/0/010.1.1.1/24

GE1/0/010.2.1.1/24

GE1/0/010.2.1.2/24

Loopback11.1.1.1/32

Loopback12.2.2.2/32

Loopback13.3.3.3/32

CE1

PE1P

PE2

CE2

AS:65410 AS:65420

AS:100MPLS Backbone

VPN-A VPN-A


1. Configure a BFD session on PE1 to detect the multi-hop path from PE1 to PE2.2. Configure a BFD session on PE2 to detect the multi-hop path from PE2 to PE1.

Data PreparationTo configure the BFD for VPN routes, you need the following data:




Procedure

Step 1 Configure the MPLS backbone network to interconnect PE1 and PE2. The configuration detailsare not mentioned here.

Step 2 Configure the VPN instance. The configuration details are not mentioned here.

Step 3 Configure the VPN route between PE1 and PE2 to be reachable. The configuration details arenot mentioned here.

After the configuration is complete, PE1 can ping through the IP address of GE 1/0/0 on PE2.

<PE1> ping -vpn-instance vpna 10.2.1.2 PING 10.2.1.2: 56 data bytes, press CTRL_C to break Reply from 10.2.1.2: bytes=56 Sequence=1 ttl=254 time=60 ms Reply from 10.2.1.2: bytes=56 Sequence=2 ttl=254 time=50 ms Reply from 10.2.1.2: bytes=56 Sequence=3 ttl=254 time=50 ms




Issue 03 (2010-03-31)

Reply from 10.2.1.2: bytes=56 Sequence=4 ttl=254 time=60 ms Reply from 10.2.1.2: bytes=56 Sequence=5 ttl=254 time=50 ms --- 10.2.1.2 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 50/54/60 ms

Step 4 Configure the detection on the VPN route between PE1 and PE2.

# On PE1, configure the BFD session between PE1 and PE2 and bind the session with the VPNinstance.

<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] min-tx-interval 10[PE1-bfd-session-1to2_vpn] min-rx-interval 10[PE1-bfd-session-1to2_vpn] wtr 5[PE1-bfd-session-1to2_vpn] commit

# On PE2, configure the BFD session between PE2 and PE1 and bind the session and the VPNinstance.

<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] min-tx-interval 10[PE2-bfd-session-2to1_vpn] min-rx-interval 10[PE2-bfd-session-2to1_vpn] wtr 5[PE2-bfd-session-2to1_vpn] commit


After the configuration is complete, run the display bfd session peer-ip command on PE1 andPE2, and you can view that a multi-hop BFD session is set up, and the session is Up.

Take 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-------------------------------------------------------------------------------- Local Discriminator : 12 Remote Discriminator : 21 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Peer Ip Address Bind Session Type : Static Bind Peer Ip Address : 10.2.1.2 NextHop Ip Address : 10.2.1.2 Bind Interface : -- Vpn Instance Name : vpna FSM Board Id : 6 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 3 Detect Interval (ms) : 30 Echo Passive : Disable Acl Number : -- Destination Port : 3784 TTL : 254 Proc interface status : Disable Process PST : Disable WTR Interval (ms) : 300000 Local Demand Mode : Disable Active Multi : 3 Last Local Diagnostic : No Diagnostic Bind Application : No Application Bind Session TX TmrID : -- Session Detect TmrID : --



5-85

Session Init TmrID : -- Session WTR TmrID : -- PDT Index : FSM-0|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------- Total UP/DOWN Session Number : 1/0

----End

Configuration Filesl Configuration file of PE1

# sysname PE1#ip vpn-instance vpna route-distinguisher 100:1 vpn-target 111:1 export-extcommunity vpn-target 111:1 import-extcommunity# mpls lsr-id 1.1.1.1 mpls#mpls ldp# bfd#interface GigabitEthernet1/0/0 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 discriminator local 12 discriminator remote 21 min-tx-interval 10 min-rx-interval 10 wtr 5 commit#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 vpna peer 10.1.1.1 as-number 65410 import-route direct#ospf 100area 0.0.0.0 network 1.1.1.1 0.0.0.0




Issue 03 (2010-03-31)

network 172.1.1.0 0.0.0.255#return

l Configuration file of PE2#sysname PE2#ip vpn-instance vpna route-distinguisher 200:1 vpn-target 111:1 export-extcommunity vpn-target 111:1 import-extcommunity# 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#interface GigabitEthernet1/0/0 undo shutdown ip binding vpn-instance vpna 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 discriminator local 21 discriminator remote 12 min-tx-interval 10 min-rx-interval 10 wtr 5 commit#bgp 100 peer 1.1.1.1 as-number 100 peer 1.1.1.1 connect-interface LoopBack1 # ipv4-family unicast undo synchronization peer 1.1.1.1 enable # ipv4-family vpnv4 policy vpn-target peer 1.1.1.1 enable # ipv4-family vpn-instance vpn1 peer 10.2.1.1 as-number 65420 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#



5-87

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#interface GigabitEthernet1/0/0 undo shutdownip address 10.1.1.1 255.255.255.0#bgp 65410 peer 10.1.1.2 as-number 100 # ipv4-family unicast import-route direct peer 10.1.1.2 enable#return

l Configuration file of CE2# sysname CE2#interface GigabitEthernet1/0/0 undo shutdownip address 10.2.1.1 255.255.255.0#bgp 65420 peer 10.2.1.2 as-number 100 # ipv4-family unicast import-route direct peer 10.2.1.2 enable#return




Issue 03 (2010-03-31)

6 GR Configuration

About This Chapter

This chapter describes the HA implementation in the NE80E/40E, the configurations of system-level GR as well as maintenance commands and provides configuration examples.

6.1 GR IntroductionThis section describes how to implement HA and related technologies.

6.2 Configuring the System-Level GRThis section describes how to configure the system-level GR.

6.3 Maintaining HAThis section describes how to monitor the working status of the HA.

6.4 Configuration ExamplesThis section provides an example for GR.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability 6 GR Configuration


6-1

6.1 GR IntroductionThis section describes how to implement HA and related technologies.

6.1.1 HA Overview

6.1.2 GR Features Supported in the NE80E/40E

6.1.1 HA OverviewIn practical network, the network may fail and the service may be interrupted because ofinevitable non-technical factors. To improve the system availability, it is feasible to improve thefault-tolerance capability of the system, speed up recovery from faults, and reduce the impactof 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 usedto assess the reliability of a device.

l MTTR: indicates the average time that a component or a device takes to recover from afailure.In broader sense, MTTR refers to spare part management, customer service, and is animportant index to evaluate equipment maintenance.The formula of MTTR is as follows:MTTR = Fault detection time + Board replacement time + System initialization time + Linkrecovery 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 the value of MTTR shouldnot be more than 5 minutes each year.

l MTBF: indicates the average time (usually in hours) when a component or a device workswithout any failure.

AMB/SMB switchover is an important method to ensure the system availability when the systemfails.

Data may be lost during AMB/SMB switchover. Most lost data can be restored smoothly throughhot standby (HSB). The lost data that cannot be restored through HSB can be restored throughGraceful Restart (GR).

Redundancy Backup

Redundancy backup for the key components in the system is an important method to improvethe 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 serviceis not interrupted.

6 GR ConfigurationHUAWEI NetEngine80E/40E Router



Issue 03 (2010-03-31)

l n+1 backup: If you need n similar components to provide services, another component isnecessary 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 mainboard, that is, two main boards.

HSBHSB 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 boardson a router.

l Standby Main Board (SMB): indicates the backup main board of the two main boards ona 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 commandsor 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 dataneeds to be synchronized on the new AMB.

The HSB can back up the static and dynamic configurations of the system from the AMB to theSMB.

The AMB and SMB communicate as shown in Figure 6-1.



6-3

Figure 6-1 Basic mechanism of HSB

AMBSMB

FIB FIB FIB FIB

FIBRIBRPA MPLS

IFnet

IPCFIBRIBRPA MPLS

IFnet

IPC

IPC IPC

GR CapabilibyNegotiation to support

Passive GRRouting / MPLS Protocol

State Sync

Socket /TCP LinkSynchronizeconfigurationand change

Heart Beat Check

Switch Fabric

DownloadFIB

IO board

Interface

Incoming Packet Outcoming Packet

When the system is restarted, the AMB backs up its static configurations on the SMB and theSMB re-execute the static configurations.

When the system runs normally, any data changes in the AMB, including static and dynamicdata changes, are backed up to the SMB. Note that the AMB can download the routinginformation from the data plane to the interface board but the SMB cannot download the routinginformation. 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 theAMB is backed up; therefore, the sessions with other routers are not affected and other routersare 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




Issue 03 (2010-03-31)

GR

In IETF, protocols related to Internet Protocol/Multiprotocol Label Switching (IP/MPLS) suchas Open Shortest Path First (OSPF), Intermediate System-Intermediate System (IS-IS), BorderGateway Protocol (BGP), Label Distribution Protocol (LDP), and Resource ReservationProtocol (RSVP) are extended to ensure that the forwarding is not interrupted when the systemis restarted. This reduces the flapping of the protocols at the control plane when the systemperforms the AMB/SMB switchover. This series of standards is called GR extension to eachprotocol. Currently, GR has been widely applied to the AMB/SMB switchover and systemupgrade.

The system can perform GR on the condition that the forwarding plane is separated from controlplane. That is, the router has a main board and an Interface board, and the Interface boardforwards 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, packetscan be forwarded in the entire system without interruption. The prerequisite to uninterruptedforwarding in the system is that the network topology and interface status do not change in theGR 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 GRcapability. The router has dual main boards, and is capable of notifying the neighbor tomaintain the adjacency during AMB/SMB switchover.

– GR Helper: indicates the neighbor of the GR Restarter. The GR Helper should be ableto identify the GR signaling, maintain the adjacency with the GR Restarter during theAMB/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 withthe 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, theGR Restarter and the GR Helper negotiate the GR capability.

– GR time: indicates the time of maintaining the undeleted routing information after theGR Helper finds that the GR Restarter becomes Down. The GR time can be regardedas 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 theGR time, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - IP Routing andHUAWEI NetEngine80E/40E Router Configuration Guide - MPLS.

The administrator and the fault can trigger the restart and AMB/SMB switchover of the GRRestarter.

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 followingdescription, 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.



6-5

Figure 6-2 Setting up sessions between the GR Helper and the GR Restarter

RouterD GR Helper

RouterA GR Restarter

RouterB

GR Helper GR Helper

RouterC

Session with GR capability

Router A serves as the GR Restarter. Router B, Router C and Router D are GR Helpersresponding to Router A. A session with the GR capability is established between the GRRestarter and each GR Helper.

2. The GR Restarter performs the AMB/SMB switchover.

Figure 6-3 AMB/SMB switchover of the GR Restarter

RouterD GRHelper

RouterA GRRestarter

RouterB

GRHelper

GRHelper

RouterC

Session with GR capability

The administrator restarts the GRrestarter,or the GR restarter itself fails

When the GR Helpers find that the GR Restarter fails, they maintain the adjacency withthe GR Restarter and retain the routing information related to the GR Restarter before theGR time times out.

3. After the SMB is started, the GR Restarter sends signals to the neighbors.




Issue 03 (2010-03-31)

Figure 6-4 GR Restarter sending signals to the neighbors after the AMB/SMB switchover

RouterD GR Helper


RouterB

GR Helper GR Helper

RouterC

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

GR restarter gets topology informationor routes from neighbors

RouterD GR Helper


RouterB

GR Helper GR Helper

RouterC

After the GR Restarter obtains the topology information from its neighbors, it recalculatesthe routing table and triggers the aging of the old routes.Thus, the GR Restarter completes the AMB/SMB switchover during which packetforwarding is not interrupted.



6-7

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 notneed great modifications to theexisting software.

l It does not need to back up theprotocol status information.

l Few data needs to be backed upfrom the AMB to the SMB. The dataincludes configurationmodification, updated messagesand events, interface status change,and topology information androuting information from neighborsafter restart.

l During the switchover, there is littleprobability of service interruption.

l Normally, the network convergesrapidly.

l Interoperability: Some of the GRspecifications are still drafts and theimplementation varies with vendors.

l Concurrent collapse: If a GR routerand its neighbor(s) collapseconcurrently, GR cannot worknormally.

l Long convergence time: When a GRrouter in the Down state cannotrecover again, its neighbors assumethat the GR Restarter will restart, sothe neighbors do not delete therelated routing and topologyinformation before the Recoverytimer times out. Compared with thecommon network in which therouters do not have the GRcapability, this network takes alonger period to converge.

l Dependence of the recovery processon neighbor routers: Neighboringrouters must support the GRcapability, because GR is not "self-contained".

HSB l The AMB/SMB switchover on theHSB router does not affect theservice forwarding and routingprocess.

l The routing information andtopology information are not lostand the protocol session is notinterrupted during the switchover.

l The switchover between the AMBand SMB is self-contained.

l The neighbour routers do not needto have the GR capability.

l There is no problem ofcompatibility.

l The switchover does not affect theneighbors.

l The network convergence is fasterthan the network with GR routers.

l More difficult to implement thanGR: More information, including theprotocol status, the session, the route,the policy, and the update, needs tobe backed up.

l Usage of more communicationchannel bandwidth: The HSB needsto support the TCP backup betweenthe AMB and the SMB.

l Dependence on the hot backup of theBGP/LDP session on the TCPconnection. If you do not expect theneighbors to be aware of theswitchover, you must back up thecontinuously changing TCP linkstatus from the AMB to the SMB.




Issue 03 (2010-03-31)

6.1.2 GR Features Supported in the NE80E/40EThe NE80E/40E integrates the redundancy backup, GR, and HSB technologies to implementthe system-level GR. When the router performs the AMB/SMB switchover, the forwarding isnot interrupted and the impact on the service is reduced; thus, HA of the device is ensured.

Currently, the following protocols in the NE80E/40E support the GR capability:

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

The NE80E/40E integrates the advantages of the GR and the HSB to implement the HA asfollows:

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 thestatus 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 helpof the neighbouring routers.

The HA feature that integrates dual main control boards, GR, and HSB is called system-levelGR. The function of the system-level GR is to decrease the impact of the AMB/SMB switchoveron 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 theGR process of other routers.

6.2 Configuring the System-Level GRThis section describes how to configure the system-level GR.


6.2.2 (Optional) Configuring the Default Slot Number for the SMB

6.2.3 Enabling the Automatic Synchronization of the AMB/SMB Configuration

6.2.4 Enabling the Force AMB/SMB Switchover

6.2.5 (Optional) Restarting the SMB




6-9


Applicable EnvironmentThe 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 manuallytriggers the AMB/SMB switchover.

To ensure that services are not affected during the switchover, configure informationsynchronization between AMB and SMB. So far, there are two modes: automatic and manual.

Pre-configuration TasksBefore 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 theHUAWEI NetEngine80E/40E Router Configuration Guide - MPLS.

Data PreparationTo 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

ContextIf both main boards are available, the system determines which one is to be the SMB when therouter restarts. Set the default slot number of the SMB using the command mentioned in thissection.

Do as follows on the GR Restarter:

Procedure



Step 2 Run:slave default slot-number




Issue 03 (2010-03-31)

The default slot number for the SMB is configured.

----End

6.2.3 Enabling the Automatic Synchronization of the AMB/SMBConfiguration

ContextDo as follows on the GR Restarter:


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 automaticallyupdates the configuration on the SMB to synchronize the configurations on the AMB and theSMB.

By default, the automatic synchronization of configuration data between AMB and SMB isenabled.

To disable the automatic synchronization of configuration data between AMB and SMB, runthe undo slave auto-update config command.

----End

6.2.4 Enabling the Force AMB/SMB Switchover

ContextDo as follows on the GR Restarter:


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.



6-11

To disable the force AMB/SMB switchover, run the slave switchover disable command.

----End

6.2.5 (Optional) Restarting the SMB

ContextDuring the on-line software upgrade, the SMB software is upgraded when the AMB worksnormally. Then, the SMB must be restarted. After the SMB is ready, the AMB/SMB switchovercan be performed.

Do as follows on the GR Restarter:

Procedure



Step 2 Run:slave restart

The SMB is restarted.

----End


PrerequisiteThe configurations of the System-Level GR function are complete.

Procedure

Step 1 Run the display switchover state [ slot-number ] command to check the status of AMB andSMB.

----End

6.3 Maintaining HAThis section describes how to monitor the working status of the HA.

6.3.1 Monitoring the Running of HA

6.3.1 Monitoring the Running of HA

ContextIn routine maintenance, you can run the following command in any view to display the runningof HA.




Issue 03 (2010-03-31)

Procedure

Step 1 Run the display switchover state [ slot-id ] command in any view to display the backup statusof the AMB and the SMB according to the specified slot ID.

----End

6.4 Configuration ExamplesThis section provides an example for GR.

6.4.1 Example for Configuring the System-Level GR

6.4.1 Example for Configuring the System-Level GR

Networking RequirementsFigure 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 betweenRouter 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, andsupport 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; andOSPF GR is enabled on Router C.

When Router B performs the AMB/SMB switchover triggered by the system fault or theadministrator, it is required that the service is not interrupted, that is, the current network serviceis not affected.

Figure 6-6 Networking diagram of configuring the system-level GR

GE1/0/010.1.4.1/24

POS2/0/010.1.1.1/24

RouterA

AS 65008POS2/0/0

10.1.1.2/24RouterB

POS1/0/010.1.2.1/24

POS1/0/010.1.2.2/24

GE2/0/010.1.3.1/24

RouterC

AS 65009


1. Enable BGP GR on Router A; enable OSPF GR and BGP GR on Router B; enable OSPFGR on Router C; configure GR parameters.



6-13

2. Configure the synchronization of the AMB/SMB configuration on Router B.



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 RouterB. 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 theconfiguration 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> system-view[RouterB] slave default 17

# Enable the force AMB/SMB switchover on Router B.

<RouterB> system-view[RouterB] slave switchover enable

# Enable the automatic synchronization of the AMB/SMB configurations.

<RouterB> system-view[RouterB] slave auto-update config[RouterB] quit




Issue 03 (2010-03-31)

<RouterB> save


# Perform the force AMB/SMB switchover on Router B.

[RouterB] slave switchoverCaution!!! Confirm switch slave to master[Y/N]?y

# Running the display fib command on Router C and Router A, you can view that the forwardingentry related to Router B still exists. The forwarding is not interrupted and the servicetransmission is not affected.

<RouterC> display fib FIB Table: Total number of Routes : 9Destination/Mask Nexthop Flag TimeStamp Interface TunnelID127.0.0.1/32 127.0.0.1 HU t[42] InLoop0 0x0127.0.0.0/8 127.0.0.1 U t[42] InLoop0 0x010.1.2.2/32 127.0.0.1 HU t[561] InLoop0 0x010.1.2.0/24 10.1.2.2 U t[561] Pos1/0/0 0x010.1.2.1/32 10.1.2.1 HU t[561] Pos1/0/0 0x010.1.3.1/32 127.0.0.1 HU t[578] InLoop0 0x010.1.3.0/24 10.1.3.1 U t[578] GE1/0/0 0x03.3.3.3/32 127.0.0.1 HU t[724] InLoop0 0x010.1.4.0/24 10.1.2.1 DGU t[1422] Pos1/0/0 0x0<RouterA> display fib FIB Table: Total number of Routes : 10Destination/Mask Nexthop Flag TimeStamp Interface TunnelID127.0.0.1/32 127.0.0.1 HU t[28] InLoop0 0x0127.0.0.0/8 127.0.0.1 U t[28] InLoop0 0x010.1.4.1/32 127.0.0.1 HU t[28] InLoop0 0x010.1.4.0/24 10.1.4.1 U t[28] GE1/0/0 0x010.1.1.1/32 127.0.0.1 HU t[444] InLoop0 0x010.1.1.0/24 10.1.1.1 U t[444] Pos2/0/0 0x010.1.1.2/32 10.1.1.2 HU t[444] Pos2/0/0 0x010.1.2.0/24 10.1.1.2 DGU t[1402] Pos2/0/0 0x010.1.3.0/24 10.1.1.2 DGU t[1402] Pos2/0/0 0x01.1.1.1/32 127.0.0.1 HU t[2060] InLoop0 0x0

----End


# sysname RouterA#interface GigabitEthernet1/0/0 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 peer 10.1.1.2 as-number 65009 # ipv4-family unicast



6-15

undo synchronization network 10.1.4.0 255.255.255.0 peer 10.1.1.2 enable#return

l Configuration file of Router B# 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 peer 10.1.1.1 as-number 65008 # ipv4-family unicast undo synchronization import-route ospf 100 peer 10.1.1.1 enable ##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

l Configuration file of Router C# sysname RouterC#interface GigabitEthernet2/0/0 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




Issue 03 (2010-03-31)

7 Ethernet OAM Configuration

About This Chapter

This chapter describes the basic principles and the implementations of the Ethernet OAM. Italso provides configuration examples.

7.1 Ethernet OAM OverviewThis section describes the background and functions of Ethernet OAM, and the Ethernet OAMfunctions supported by the NE80E/40E.

7.2 Configuring Basic EFM OAMThis section describes how to configure basic EFM OAM.

7.3 Configuring EFM OAM Link MonitoringThis section describes how to configure EFM OAM link monitoring.

7.4 Testing the Packet Loss Ratio on the Physical LinkThis section describes the method of testing the packet loss ratio on the link by configuringremote loopback and sending testing packets.

7.5 Associating EFM OAM with an InterfaceThis section describes how to associate EFM OAM with an interface.

7.6 Configuring Basic Ethernet CFMThis section describes how to configure basic Ethernet CFM.

7.7 Configuring Related Parameters of Ethernet CFMThis section describes how to Configure Related Parameters of Ethernet CFM.

7.8 Fault Verification on the EthernetThis section describes the method of testing the connectivity on the Ethernet through 802.1agMAC ping or MAC ping, and the method of detecting the connectivity on the PBB-TE tunnelthrough PBB-TE MAC ping.

7.9 Locating the Fault on the EthernetThis section describes the method of locating the connectivity fault on the Ethernet through802.1ag MAC trace or MAC trace, and the method of locating the connectivity fault on the PBB-TE tunnel through PBB-TE MAC trace.

7.10 Associating Ethernet CFM with an Interface

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability 7 Ethernet OAM Configuration


7-1

This section describes how to associate Ethernet CFM with an interface.

7.11 Associating EFM OAM with Ethernet CFMThis section describes how to associate EFM OAM with Ethernet CFM.

7.12 Associating Ethernet CFM with VPLS

7.13 Associating Ethernet OAM with MPLS OAM or BFDThis section describes how to associate Ethernet OAM with MPLS OAM or BFD.

7.14 Configuring Ethernet CFM and 1+1 Protection of Multicast VLANsThis section describes how to configure Ethernet CFM and 1+1 Protection of Multicast VLANs.

7.15 Maintaining Ethernet OAMThis section describes how to clear statistics of error CCMs, and how to monitor the runningstatus of Ethernet OAM.

7.16 Configuration ExamplesThis section provides several configuration examples of Ethernet OAM.

7 Ethernet OAM ConfigurationHUAWEI NetEngine80E/40E Router



Issue 03 (2010-03-31)

7.1 Ethernet OAM OverviewThis section describes the background and functions of Ethernet OAM, and the Ethernet OAMfunctions supported by the NE80E/40E.

7.1.1 Introduction to Ethernet OAM

7.1.2 Ethernet OAM Supported by the NE80E/40E

7.1.1 Introduction to Ethernet OAM

Background

The Ethernet has developed as the major Local Area Network (LAN) technology because itfeatures easy implementation and low cost. Recently, along with the applications of GigabitEthernet and the later 10-Gigabit Ethernet, Ethernet has been extended to the Metropolitan AreaNetwork (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) isalways required for the Ethernet. The lack of the OAM mechanism prevents Ethernet fromeffectively functioning as the Internet Service Provider (ISP) network. In this manner, EthernetOAM is becoming a trend.

Functions

Ethernet OAM has the following functions:

l Fault management

– Ethernet OAM can detect the network connectivity by sending detection messagesregularly or through manual triggering.

– Ethernet OAM can locate faults on the Ethernet by using means similar to the PacketInternet Groper (ping) and traceroute tools on IP networks.

– Ethernet OAM can work with the Automatic Protection Switching (APS) to triggerprotection switching when detecting connectivity faults. This ensures serviceinterruption 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 duringthe transmission of packets. It also collects statistics on various kinds of traffic.Performance management is implemented at the access point of users. By using theperformance management tools, the ISP can monitor the network status and locate faultsthrough the Network Management System (NMS). The ISP checks whether the forwardingcapacity of the network complies with the Service Level Agreement (SLA) signed withusers.

Ethernet OAM improves network management and maintenance capabilities on the Ethernetand guarantees a steady network.



7-3

7.1.2 Ethernet OAM Supported by the NE80E/40E

EFM OAM

Ethernet in the First Mile (EFM) defined in IEEE 802.3ah specifies the physical layerspecifications and Ethernet OAM of the Ethernet for user access networks. It is used to detectthe 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 EFMOAM, the interface and the remote interface send and respond with a slow protocol frame,that is, an OAM Protocol Data Unit (OAM PDU) to determine whether the EFM OAMconfigurations on both interfaces match. This is called OAM discovery. If the EFM OAMconfigurations on both interfaces match, the two interfaces enter the EFM OAM Detectstate. In the Detect state, the two interfaces send OAM PDUs regularly to maintainadjacencies. In normal situations, the interval for sending OAM PDUs is 1 second.

l Link monitoring

Link monitoring is a mechanism for an interface to notify the peer of the fault by sendingthe event notification OAM PDU when the interface detects the errored frame event, erroredcode event, or errored frame seconds event.

– The errored frame event means that the number of errored frames detected on aninterface reaches or exceeds the specified threshold within a set period.

– The errored code event means that the number of errored codes detected on an interfacereaches or exceeds the specified threshold within a set period.

– The errored frame seconds summary event means that the number of errored frameseconds detected on an interface reaches or exceeds the specified threshold within a setperiod.

An errored frame second is a one-second interval during which at least one errored frameis detected.

l Fault notification

When a link event about a fault occurs on the local interface, the local interface notifies thepeer of the fault through OAM PDUs. 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.

– OAM PDUs time out.

– Errors transmitted by the OAM management module.

After receiving OAM PDUs, the peer records the event carried in OAM PDUs to the logand reports it to the NMS.

l Remote loopback

When the local interface sends non-OAM PDUs to the peer, instead of forwarding non-OAM PDUs based on their destination MAC addresses, the peer loops back non-OAM




Issue 03 (2010-03-31)

PDUs to the local interface. This is called remote loopback. Remote loopback can be usedto locate faults and test link performance.

The working mode of EFM OAM is an attribute of the interface enabled with EFM OAM. Theworking mode of EFM OAM on an interface is active or passive. OAM discovery and remoteloopback are initiated only by the interface in active mode.

Ethernet CFMConnectivity Fault Management (CFM) defined in IEEE 802.1ag specifies the OAM functionsof 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 Standard802.1ag-2007. Table 7-1 shows the differences between these two versions.

Table 7-1 Differences between IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007

Feature IEEE 802.1ag Draft7

IEEE Standard802.1ag-2007

Remarks

Maintenance Domain Supported Supported Thefeaturesandconfigurationssupported by802.1ag Draft 7and Standard802.1ag-2007are the same.

Default MD Not supported Supported -

MaintenanceAssociation

Supported Supported The featuresandconfigurationssupported by802.1ag Draft 7and Standard802.1ag-2007are the same.

Maintenanceassociation End Point




7-5



Remarks

Remote Maintenanceassociation End Point


MaintenanceassociationIntermediate Point

Supported Supported The MIPgenerationrules in both802.1ag Draft 7and Standard802.1ag-2007are classifiedinto the sametypes, that is,default,explicit, andnone. Thedifferencebetween theMIPgenerationrules in802.1ag Draft 7and Standard802.1ag-2007,however, is asfollows:l According

to 802.1agDraft 7, theMIP iscreated onthe basis oftheinterface.

l Accordingto Standard802.1ag-2007, the MIP iscreated onthe basis ofthe MD ordefault MD.




Issue 03 (2010-03-31)



Remarks

Maintenance Point Supported Supported The featuresandconfigurationssupported by802.1ag Draft 7and Standard802.1ag-2007are the same.

l Basic concepts– MD

A Maintenance Domain (MD) refers to the network or a part of the network where CFMis performed. Devices in an MD are managed by a single ISP.

– Default MDAccording to IEEE Standard 802.1ag-2007, each device can be configured with onedefault MD. The default MD must be of a higher level than all MDs to which MEPsconfigured on the local device belong. In addition, the default MD must be of the samelevel as the high-level MD. The default MD transmits high-level CCMs and createsMIPs to reply LTR packets.

– MAA Maintenance Association (MA) is part of an MD. An MD can be divided into one ormultiple MAs. On the NE80E/40E, each MA is associated with a VLAN or a VSI.Ethernet CFM maintains the connectivity of each MA separately.

– MEPA 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 localMEPs. For the other devices in the same MA, their MEPs are called the RemoteMaintenance association End Points (RMEPs).

CAUTIONl 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.

– MIPA Maintenance association Intermediate Point (MIP) is an intermediate point within anMA.According to IEEE 802.1ag Draft 7, MIPs reside on the interfaces of the device and areautomatically generated on the basis of the interface.According to IEEE Standard 802.1ag-2007, MIPs are automatically generated on thebasis of the MD or default MD.



7-7

The MIP is automatically generated.l Connectivity check

Ethernet CFM divides the network into one MD or multiple MDs. Each MD is furtherdivided into one MA or multiple MAs. Ethernet CFM can detect the connectivity betweenMEPs within an MA by exchanging Continuity Check Messages (CCMs) periodicallybetween MEPs.

l Fault verification– 802.1ag MAC ping

Similar to ping, 802.1ag MAC ping works by sending test packets and waiting for areply to test whether the destination device is reachable. 802.1ag MAC ping is initiatedby a MEP and destined for a MEP or MIP within an MA.

– GMAC pingGMAC ping works similarly to 802.1ag MAC ping. A MEP, however, is not requiredto 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 thesource device, the intermediate device, and the destination device.

– PBB-TE PingThe Provider Backbone Bridging-Traffic Engineering (PBB-TE) ping operation isperformed 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 andwaiting for a reply to test the path between the local device and the destination deviceand to locate faults. 802.1ag MAC trace is initiated by a MEP and destined for a MEPor MIP within an MA.

– GMAC traceGMAC trace works similarly to 802.1ag MAC trace. A MEP, however, is not requiredto initiate GMAC trace. The destination node does not need to be a MEP or a MIP. Thatis, GMAC trace can be implemented without configuring the MD, MA, or MEP on thesource device, the intermediate device, and the destination device. All the intermediatedevices can respond with a Linktrace Reply (LTR).

– PBB-TE MAC tracePBB-TE MAC trace locates the connectivity fault on the PBB-TE tunnel. PBB-TE MACtrace is initiated by one end of the PBB-TE tunnel and destined for the other end.

Fault Associationl Association between EFM OAM and an interface

When EFM OAM is associated with the current interface and detects a link fault throughthe current interface, no other packets except EFM protocol packets can be forwarded onthe interface and Layer 2 and Layer 3 services are blocked. Therefore, the association ofEFM OAM and the current interface may greatly affect services. When the current interfacedetects the link fault recovery through EFM OAM, all packets can be forwarded on theinterface and Layer 2 and Layer 3 services are unblocked.Before configuring the association between EFM OAM and an interface, ensure that theEFM OAM protocol on both ends of the link is in the detect state.

l Association between Ethernet CFM and an interface




Issue 03 (2010-03-31)

When a MEP detects a connectivity fault between the MEP and a specified RMEP withinthe same MA, the OAM management module performs the restart function, that is, shutsdown 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 modulesends fault messages to the device at the other end through the PBB-TE tunnel to whichthe SI that EFM OAM associates with is bound.

l Association between Ethernet CFM and the PBB-TE SIWhen the Ethernet CFM module detects a connectivity fault, the OAM managementmodule sends fault messages to the device at the other end through the PBB-TE tunnel towhich the SI that Ethernet CFM associates with is bound.

l Association between Ethernet CFM and EFM OAMWhen the Ethernet CFM module detects a fault in an MA, the OAM management modulesends 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 faultmessages 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 CFMWhen the Ethernet CFM module detects a fault in an MA, the OAM management modulesends 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)When the Ethernet CFM module detects a fault in an MA, the OAM management modulesends fault messages to BFD at the other side through the binding relationship. When BFDdetects 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) OAMWhen the Ethernet CFM module detects a fault in an MA, the OAM management modulesends fault messages to MPLS OAM through the binding relationship. When MPLS OAMdetects a fault, the OAM management module sends fault messages to the MA through thebinding relationship.– Ethernet CFM sends fault messages to MPLS OAM.

– MPLS OAM sends fault messages to Ethernet CFM.

l Association between EFM OAM and BFDWhen the EFM OAM module detects a fault, the OAM management module sends faultmessages to BFD at the other side through the interface. When BFD detects a fault, BFDsends fault messages to EFM OAM through the interface.– EFM OAM sends fault messages to BFD.

– BFD sends fault messages to EFM OAM.



7-9

– EFM OAM and BFD perform bidirectional transmission of fault messages.

l Association between EFM OAM and MPLS OAMWhen the EFM OAM module detects a fault, the OAM management module sends faultmessages to MPLS OAM through the interface. When MPLS OAM detects a fault, theOAM 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 ExtensionGenerally, a CE accesses an IP network by connecting the two PEs in master/slave mode. Thiscan ensure the reliability of IP services. To be specific, the CE usually accesses the two PEs ina Router Redundancy Protocol (VRRP) backup group. The VRRP access, however, is originallydesigned for PC terminals, and therefore cannot guarantee the carrier-class reliability andperformance.

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 Layer2 networks, such as Provider Backbone Transport-Traffic Engineering (PBT-TE), TransportMPLS (T-MPLS), and Virtual Private LAN Service (VPLS), is currently supported on variousvendors' devices.

An EFM OAM extension Protocol Data Unit (PDU) carries the flag bit that indicates the linkstate. The router that receives the PDU can control the status of the access link according to theflag bit. By associating EFM OAM extension with interfaces or static routes, you can controlthe traffic flow and achieve the primary/bypass link failover, which can ensure the carrier-classreliability in network access.

l As shown in Figure 7-1.

Figure 7-1 Networking diagram of EFM OAM extension for VRRP

interface IPVLANIF/VPLSinterface IP

IP/MPLS

VRRP

Master linkSlave link

SoftX

RouterA RouterB

link detectionby EFM OAM

extension

UNI interface

link detectionby EFM OAM

extension




Issue 03 (2010-03-31)

Router A functions as the master router and Router B functions as the backup router. TheSoftX uses two interface boards, namely, a master interface board and a slave interfaceboard, to respectively connect both routers. On the master and slave interface boards, theinterfaces that are respectively connected to Router A and Router B are configured withthe same IP address. Normally, the IP address of the interface on the master interface boardis valid.The SoftX is dual homed to the gateways, that is, Router A and Router B. A VRRP backupgroup is configured on VLANIF interfaces. The virtual IP address of the VRRP backupgroup 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 inreduce 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 thefollowing 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 needto 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 VC interfaces into the same virtual switching instance(VSI).

– Configure the VRRP backup group on Layer 3 VE (L3VE) interfaces, and bind theL3VE 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 masterlink and slave link based on EFM OAM extension and all devices can achieve EFM OAMextension for VRRP.Generally, the SoftX decides the link status based on relevant calculations, and thenadvertises the link status information to the downstream interfaces of both routers bysending EFM OAM extension PDUs.As just mentioned, the VRRP backup group is configured to track the traffic of thedownstream 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 VRRPpriority 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 RouterB is increased, and Router B becomes the master router. This can ensure the consistencybetween the VRRP master/slave status and the master/slave status of the downstreaminterfaces.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. TheSoftX then performs the master/slave failover, and sends the PDU indicating the link-upstate to Router B. The VRRP priority of Router B is thus increased, and Router B becomesthe master router. This can ensure the consistency between the master/slave status of theSoftX and the master/slave status of both routers.



7-11

– Link Failover Between Downstream Interfaces: If a fault on the master link is detectedby EFM OAM extension, the SoftX performs the master/slave failover and sends thegratuitous ARP packet and EFM OAM extension PDU to Router B.

1. If Router B receives the gratuitous ARP packet earlier than the EFM OAMextension 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. RouterA 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 toRouter B, and Router B then forwards the traffic to the SoftX according to itsMAC 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 linkto the master link. The downstream traffic is thus directly forwarded by RouterB.

– 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 tothe backup link. Therefore, the upstream and downstream traffic throughRouter A is blocked.

2. If Router B receives the PDU indicating the link-up state earlier than the gratuitousARP 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 switchedinto the master link. Then Router B forwards the upstream and downstreamtraffic, 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 VRRPlink to the backup link. At the same time, Router A blocks its downstreaminterface. After the SoftX learns the gratuitous ARP packets sent by Router B,the SoftX establishes a route to Router B. Then the downstream traffic isforwarded by Router B.

When the faulty link between Router A and the SoftX recovers, the SoftX stillnotifies Router A of keeping the current slave state. Therefore, no gratuitous ARPpacket 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 downstreamtraffic and upstream traffic are forwarded by Router B.

l Figure 7-2 shows EFM OAM extension for static routes.




Issue 03 (2010-03-31)

Figure 7-2 Networking diagram of EFM OAM extension for static routes

interface IPinterface IP

IP/MPLS

VRRP

Master linkSlave link

SoftX

RouterA RouterB

UNIinterface

Link detectionperformed by

EFM OAMextension

Link detectionperformed by

EFM OAMextension

Trafficbefore the

failover

Trafficafter thefailover

Router A functions as the master router and Router B functions as the backup router. TheSoftX uses two interface boards, namely, a master interface board and a slave interfaceboard, to respectively connect both routers.

On the master and slave interface boards, the interfaces that are respectively connected toRouter A and Router B are configured with the same IP address. On Router A and RouterB, 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 isconfigured 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. Thedownstream interfaces of both routers are Ethernet interfaces.

EFM OAM extension is enabled on the SoftX, and the SoftX advertises the link-statusinformation to both routers; EFM OAM extension for static routes is enabled on bothrouters. 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 Bis performed. After route convergence is completed, the upstream and downstream trafficflows through the new master link.

– Link Failover Between Downstream Interfaces:

When the master link fails, the SoftX performs the link failover, and sends the PDUindicating the link-up state to Router B. After receiving the PDU, Router B changesto the master router, and advertises the static route destined for the service IP addresson 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 addresson the SoftX.

When the faulty link between the SoftX and Router A recovers, the SoftX still notifiesRouter A of keeping the current backup state. Therefore, the traffic is not switched fromRouter B to Router A, and Router A does not advertise any route.



7-13

– 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 anddownstream traffic is forwarded by Router B.

7.2 Configuring Basic EFM OAMThis section describes how to configure basic EFM OAM.


7.2.2 Enabling EFM OAM Globally

7.2.3 Configuring the Working Mode of EFM OAM on an Interface

7.2.4 (Optional) Setting the Maximum Size of an EFM OAMPDU

7.2.5 Enabling EFM OAM on an Interface




As shown in Figure 7-3, you can perform the configuration task to detect the connectivitybetween two directly connected devices.

Figure 7-3 Diagram of configuring EFM OAM

Interface 1(Active)

Interface 2(Passive)

EFM OAM


None.

Data Preparation

To configure EFM OAM, you need the following data.

No. Data

1 (Optional) Maximum size of an EFM OAM PDU




Issue 03 (2010-03-31)

7.2.2 Enabling EFM OAM Globally

ContextDo as follows on the devices at both ends of the link:

Procedure



Step 2 Run:efm enable

EFM OAM is enabled globally.

By default, EFM OAM is disabled globally.

----End

7.2.3 Configuring the Working Mode of EFM OAM on an Interface

ContextNOTE

The working mode of EFM OAM on the interface can be configured only after EFM OAM is enabledglobally and before EFM OAM is enabled on the interface. The working mode of EFM OAM on theinterface cannot be modified after EFM OAM is configured on the interface.

Do as follows on the devices at both ends of the link:

Procedure




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. Theinterface 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 OAM PDU sentfrom the interface in active mode. If both interfaces are configured to work in active mode, you



7-15

can implement link detection. If both interfaces are configured to work in passive mode, OAMdiscovery fails.

----End

7.2.4 (Optional) Setting the Maximum Size of an EFM OAMPDU


Procedure





Step 3 Run:efm packet max-size size

The maximum size of an EFM OAM PDU is set.

By default, the maximum size of an EFM OAM PDU on an interface is 128 bytes.

EFM OAM PDUs that exceed 128 bytes are discarded as invalid packets.

If the maximum size of an EFM OAM PDU on both interfaces of the link is configureddifferently, the two interfaces negotiate and determine the value during the OAM discoveryprocess. The smaller maximum size of an EFM OAM PDU set on the local interface and thepeer is selected.

----End

7.2.5 Enabling EFM OAM on an Interface


Procedure








Issue 03 (2010-03-31)

Step 3 Run:efm enable

EFM OAM is enabled on the interface.

By default, EFM OAM on an interface is disabled.

----End


Prerequisite

The configurations of the EFM OAM function are complete.

Procedurel 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 } commandto 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 localinterface 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 ErrCodeNotification: disable ErrCodePeriod: 1 ErrCodeThreshold: 1 ErrFrameNotification: disable ErrFramePeriod: 45 ErrFrameThreshold: 1 ErrFrameSecondNotification: disable ErrFrameSecondPeriod: 60 ErrFrameSecondThreshold: 1 TriggerIfDown: disable Remote MAC: 00e0-fc7f-724f Remote EFM Enable Flag: enable Remote Mode: passive Remote MaxSize: 128

Run the display efm session command. If the EFM OAM protocol on the interface is in theDetect state, it means that the configuration succeeds. The two interfaces succeed in negotiationand enter the Detect state.

<HUAWEI> display efm session interface gigabitethernet2/0/1 Interface EFM State Loopback Timeout -------------------------------------------------------------------- GigabitEthernet2/0/1 detect --



7-17

7.3 Configuring EFM OAM Link MonitoringThis section describes how to configure EFM OAM link monitoring.


7.3.2 (Optional) Detecting Errored Frames of EFM OAM

7.3.3 (Optional) Detecting Errored Codes of EFM OAM

7.3.4 (Optional) Detecting Errored Frame Seconds of EFM OAM




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 remoteOAM 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

7.3.2 (Optional) Detecting Errored Frames of EFM OAM

Context

When an interface is enabled to detect errored frames, the NE80E/40E generates an erroredframe event and notifies the peer, if the number of errored frames reaches or exceeds thethreshold within a set period.

Do as follows on the devices at one end or both ends of the link:




Issue 03 (2010-03-31)

Procedure





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

7.3.3 (Optional) Detecting Errored Codes of EFM OAM

ContextWhen an interface is enabled to detect errored codes, the NE80E/40E generates an errored codeevent and notifies the peer, if the number of errored codes reaches or exceeds the threshold withina set period.


Procedure





Step 3 Run:efm error-code period period



7-19

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

7.3.4 (Optional) Detecting Errored Frame Seconds of EFM OAM

ContextAn errored frame second is a one-second interval during which at least one errored frame isdetected. It specifies the seconds when errored frames are deteced.

When an interface is enabled to detect errored frame seconds, the NE80E/40E generates anerrored frame seconds summary event and notifies the peer, if the number of errored frameseconds reaches or exceeds the threshold within a set period.


Procedure





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:




Issue 03 (2010-03-31)

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


PrerequisiteThe configurations of the EFM OAM Link Monitoring function are complete.

Procedure

Step 1 Run the display efm { all | interface interface-type interface-number } command to checkinformation about EFM OAM on an interface.

----End

ExampleRun the display efm command. You can view information about link monitoring on theinterface. For example:

<HUAWEI> display efm interface gigabitethernet1/0/0 Item Value ---------------------------------------------------------- Interface: GigabitEthernet1/0/0 EFM Enable Flag: enable Mode: active OAMPDU MaxSize: 128 ErrCodeNotification: enable ErrCodePeriod: 1 ErrCodeThreshold: 1 ErrFrameNotification: enable ErrFramePeriod: 45 ErrFrameThreshold: 1 ErrFrameSecondNotification: enable ErrFrameSecondPeriod: 60 ErrFrameSecondThreshold: 1 TriggerIfDown: disable RemoteMAC 00e0-fc7f-7258 Remote EFM Enable Flag enable Remote Mode passive Remote MaxSize 128

7.4 Testing the Packet Loss Ratio on the Physical LinkThis section describes the method of testing the packet loss ratio on the link by configuringremote loopback and sending testing packets.


7.4.2 Enabling EFM OAM Remote Loopback

7.4.3 Sending Test Packets

7.4.4 Checking the Statistics on Returned Test Packets



7-21

7.4.5 (Optional) Manually Disabling EFM OAM Remote Loopback




CAUTIONThe forwarding of service data is affected after EFM OAM remote loopback is enabled. So,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 7-4, enable EFM OAM on Router A and Router B and enable remoteloopback on GE 1/0/1 on Router A. Send test packets from Router A to Router B. You can getthe packet loss ratio on the link by observing the receiving of test packets on Router A.

Figure 7-4 Diagram of testing the packet loss ratio on the link

(Active)GE2/0/1

(Passive)

Test packets

Test packets data flow

EFM OAMRouterA RouterB

GE1/0/1

Pre-configuration TasksBefore testing the packet loss ratio on the link, complete the following tasks:


Data PreparationTo 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 sendingrate of test packets




Issue 03 (2010-03-31)

7.4.2 Enabling EFM OAM Remote Loopback

ContextDo as follows on the device with an active interface on the link:

Procedure





Step 3 Run:efm loopback start [ timeout timeout ]

Remote loopback is initiated by 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 toremain 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 protocolsrunning on the local interface and the peer are in the Detect state.

Step 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

7.4.3 Sending Test Packets


Procedure





7-23

Step 2 Run:test-packet start [ mac mac-address ] [ vlan vlan-id ] interface interface-type interface-number [ -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 oftest packets sent is 5.

The outbound interface for the test packets is the interface that connects the link to be tested.

----End

PostrequisiteThe parameter in this command cannot be modified when test packets are being sent.

Press Ctrl+C to stop sending test packets.

7.4.4 Checking the Statistics on Returned Test Packets


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

7.4.5 (Optional) Manually Disabling EFM OAM Remote Loopback





Issue 03 (2010-03-31)

Procedure





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 longtime. To prevent this, EFM OAM remote loopback on the NE80E/40E can be automaticallydisabled 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


PrerequisiteThe 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 tocheck the status of the EFM OAM protocol on an interface.

----End

ExampleRun the display efm session command on the device with an active interface on the link. If theEFM OAM protocol on the active interface is in the loopback (control) state, which indicatesthat the active interface initiates remote loopback, it means that the configuration succeeds.

<RouterA> display efm session interface gigabitethernet 1/0/1 Interface EFM State Loopback Timeout ---------------------------------------------------------------------- GigabitEthernet1/0/1 Loopback(be controlled) 20

Run the display efm session command on the device with a passive interface on the link. If theEFM OAM protocol on the passive interface is in the loopback (be controlled) state, whichindicates that the passive interface responds to remote loopback, it means that the configurationsucceeds.

<RouterB> display efm session interface gigabitethernet 2/0/1 Interface EFM State Loopback Timeout ---------------------------------------------------------------------- GigabitEthernet2/0/8 Loopback(be controlled) --



7-25

Run the display efm session command on any of the devices on the link after remote loopbackis automatically or manually disabled, you can view that the EFM OAM protocol status on theinterface is no longer loopback (control) or loopback (be controlled).

<RouterA> display efm session interface gigabitethernet 1/0/1 Interface EFM State Loopback Timeout ---------------------------------------------------------------------- GigabitEthernet2/0/8 Detect --

7.5 Associating EFM OAM with an InterfaceThis section describes how to associate EFM OAM with an interface.


7.5.2 Associating EFM OAM with an Interface




As shown in Figure 7-5, EFM OAM is enabled on Router A and Router B. EFM OAM isassociated with GE 1/0/1 on Router A. When the EFM OAM module on Router A detects aconnectivity fault between Router A and Router B, no other packets except EFM protocol packetscan 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 canbe forwarded on the interface and Layer 2 and Layer 3 services are unblocked.

Figure 7-5 Diagram of associating EFM OAM with an interface

EFM OAM

The interface associated with EFM OAM

GE1/0/1 GE2/0/1RouterA RouterB


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.




Issue 03 (2010-03-31)

No. Data

1 Type and number of an interface

7.5.2 Associating EFM OAM with an Interface

Context


Procedure





Step 3 Run:efm trigger if-down

EFM OAM is associated with the interface.

By default, an interface is not associated with EFM OAM.

The efm trigger if-down command is valid in the interface view only after EFM OAM is enabledon the interface with the efm enable command.

When EFM OAM is associated with the current interface and detects a link fault through thecurrent interface, no other packets except EFM protocol packets can be forwarded on theinterface and Layer 2 and Layer 3 services are blocked. Therefore, the association of EFM OAMand the current interface may greatly affect services. When the current interface detects the linkfault recovery through EFM OAM, all packets can be forwarded on the interface and Layer 2and Layer 3 services are unblocked.

Before configuring the association between EFM OAM and an interface, ensure that the EFMOAM 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 efmtrigger if-down command in the interface view to restore services.

----End


Prerequisite

The configurations of Associating EFM OAM with an Interface function are complete.



7-27

Procedure

Step 1 Run the display efm { all | interface interface-type interface-number } command to check theEFM OAM configuration information on an interface.

----End

ExampleRun the display efm command. If the item "TriggerIfDown" is displayed as "enable", it meansthat the configuration succeeds.

<HUAWEI> display efm interface gigabitethernet1/0/1Item Value ---------------------------------------------------- Interface: GigabitEthernet1/0/1 EFM Enable Flag: enable Mode: active OAMPDU MaxSize: 128 ErrCodeNotification: disable ErrCodePeriod: 1 ErrCodeThreshold: 1 ErrFrameNotification: disable ErrFramePeriod: 1 ErrFrameThreshold: 1 ErrFrameSecondNotification: disable ErrFrameSecondPeriod: 60 ErrFrameSecondThreshold: 1 TriggerIfDown: enable TriggerMacRenew: disable Remote MAC: 0018-8200-0001 Remote EFM Enable Flag: enable Remote Mode: passive Remote MaxSize: 128

7.6 Configuring Basic Ethernet CFMThis section describes how to configure basic Ethernet CFM.


7.6.2 Switching IEEE 802.1ag Versions

7.6.3 Enabling Ethernet CFM Globally

7.6.4 Creating an MD

7.6.5 (Optional) Creating the Default MD

7.6.6 Creating an MA

7.6.7 Creating a MEP

7.6.8 Creating an RMEP

7.6.9 (Optional) Setting the Rule for Creating a MIP

7.6.10 Enabling CC Detection

7.6.11 (Optional) Creating a VLAN





Issue 03 (2010-03-31)


Applicable EnvironmentYou can perform the configuration task to implement the following functions on the Ethernet:

l Automatic end-to-end connectivity detection

l Automatic connectivity detection on directly connected links

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 aremanaged 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 andgenerates MIPs to reply LTR packets.

l MAs are classified based on different SIs. An MA is associated with a VLAN. A VLANgenerally maps to an SI. When the MA is classified, fault detection in connectivity can becarried 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 needto 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.

Pre-configuration TasksNone.

Data PreparationTo 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

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 bridge MAC address of the device on which the RMEPresides

6 Rule for creating a MIP

7 Interval for a MEP sending or detecting CCMs in an MA



7-29

No. Data

8 (Optional) ID of the specified VLAN

7.6.2 Switching IEEE 802.1ag Versions

ContextBy default, IEEE 802.1ag Draft 7 is enabled on the device. Do as follows on each NE80E/40Ethat requires IEEE Standard 802.1ag-2007:

Procedure



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 Standard802.1ag-2007. IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007 cannot be enabled at the same timeon a network.

----End

7.6.3 Enabling Ethernet CFM Globally

Context

Do as follows on the router that requires Ethernet CFM:

Procedure



Step 2 Run:cfm enable

Ethernet CFM is enabled globally.

By default, Ethernet CFM on the router is disabled globally.

----End




Issue 03 (2010-03-31)

7.6.4 Creating an MD

Context


Procedure



Step 2 Run:cfm md md-name [ format { no-md-name | dnsname-and-mdname | mac-address | md-name } ] [ level level ]

An MD is created and the MD view is displayed.

Parameters format, no-md-name, dnsname-and-mdname, and mac-address can be used onlyon 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 levelMD or a higher-level MD. The 802.1ag packets from a higher-level MD can be transmitted through a lower-level MD.

----End

7.6.5 (Optional) Creating the Default MD

Context

Do as follows on each NE80E/40E device that requires Ethernet CFM:

Procedure



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.



7-31

NOTE

The default MD must be of a higher level than all MDs to which MEPs configured on the local devicebelong. In addition, the default MD must be of the same level as the high-level MD. The default MDtransmits high-level CCMs and generates MIPs to reply LTR packets.

----End

7.6.6 Creating an MA

ContextDo as follows on the NE80E/40E that requires Ethernet CFM:

Procedure



Step 2 Run:cfm md md-name

The MD view is displayed.

Step 3 Run:ma ma-name

An MA is created and the MA view is displayed.

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 associatedwith 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 directlyconnected devices, the MA is not required to be associated with a VLAN. Otherwise, the MAmust be associated with a VLAN.

----End

PostrequisiteAn 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.




Issue 03 (2010-03-31)

7.6.7 Creating a MEP

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 theinterface on which the MEP resides must be added to the VLAN. The inward-facing MEPthen broadcasts the OAMPDUs in the VLAN associated with the MA. That is, theinwarding-facing MEP sends the OAMPDUs out through all the interfaces excluding theinterface 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 aVLAN. However, if the MA is associated with a VLAN, the interface on which the MEPresides must be added to the VLAN. The outward-facing MEP sends out the OAMPDUsthrough 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 MEPcannot coexist.

l Only one outward-facing interface-based MEP can be created. Multiple inward-facinginterface-based MEPs can be created. However, only one inward-facing interface-basedMEP can be created on an interface.

l Only one VLAN-based MEP can be created.

CAUTIONl 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






The MA view is displayed.



7-33

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

Postrequisitel 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.

7.6.8 Creating an RMEP

ContextIf you need to detect the connectivity between a device and an RMEP, you need to create theRMEP first.

Do as follows on the edge devices of an MA:

Procedure







Step 4 Run:remote-mep mep-id mep-id [ mac mac-address ]

An RMEP in the current MA is created.

----End

Postrequisitel If you need to create multiple RMEPs in an MA, repeat Step 4.




Issue 03 (2010-03-31)

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.

7.6.9 (Optional) Setting the Rule for Creating a MIP

ContextCurrently, IEEE 802.1ag has two versions, that is, IEEE 802.1ag Draft 7 and IEEE Standard802.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.



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 [ format { no-md-name | dnsname-and-mdname | mac-address | md-name } ] [ level level ]The MD view is displayed.Or, run:cfm default md [ level level ]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 automaticallyaccording to the rule.



7-35

The level of a MIP depends on the level of the MD generating the MIP and the level generationrule.

----End

7.6.10 Enabling CC Detection

Context

Do as follows on the edge devices on which MEPs reside within MAs:

Procedure







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 CCMsin the MA cannot be modified. If you want to modify the interval for sending or detecting CCMsin 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.




Issue 03 (2010-03-31)

When the local device is enabled to receive CCMs from an RMEP, and if connectivity faults aredetected between the local device and the RMEP through CC detection, the local device promptsalarms of RMEP connectivity.

If mep-id mep-id is not specified, all the MEPs in the MA are enabled to receive CCMs fromall the RMEPs.

----End

Postrequisitel 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.

7.6.11 (Optional) Creating a VLAN

Context

Do as follows on each device:

Procedure



Step 2 Run:cfm default md [ level level ]

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


Prerequisite

The configurations of the Ethernet CFM function are complete.

Procedurel Run the display cfm md [ md-name ] [ | { begin | include | exclude } regular-

expression ] command to check the configuration information about an MD.l Run the display cfm ma [ md md-name [ ma ma-name ] ] [ | { begin | include | exclude }

regular-expression ] 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.



7-37

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 ] commandto 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-name | 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 incorrectconfigurations of the specified error type.

l Run the display cfm mp-info [ interface { interface-name | 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 andVLAN or VSI.

----End

ExampleThe output of the display cfm md command on the device running IEEE 802.1ag Draft 7 isdifferent 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 informationabout the MD and the MD level is displayed, it means that the MD is created successfully.

<HUAWEI> display cfm mdThe total number of MDs is 2MD-Name Level--------------------------------------------------md2 7md3 3

Run the display cfm md command on the device running IEEE Standard 802.1ag-2007. Ifinformation about the name of the MD, MD name format, MD level, MIP generation rule, andsender 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 : mdcustomer MD Name Format : md-name Level : 1 MIP Create-type : default SenderID TLV-type : SendIdDefer MA list : MA name : macustomer Interval : 20 Vlan ID : 400 VSI Name : --

Run the display cfm ma command. If information about the MA is displayed, it means that theconfiguration is successful.

<HUAWEI> display cfm ma<HUAWEI> display cfm ma md md1The total number of MAs is 2: MD Name : md1 MD Name Format : md-name Level : 7




Issue 03 (2010-03-31)

MIP Create-type : none SenderID TLV-type : SendIdDefer MA Name : ma1 Interval : 10ms Priority : 4 Vlan ID : 7 VSI Name : -- MEP Number : 2 RMEP Number : 3 MD Name : md1 MD Name Format : md-name Level : 7 MIP Create-type : none SenderID TLV-type : SendIdDefer MA Name : ma2 Interval : 10ms Priority : 5 Vlan ID : 8 VSI Name : -- MEP Number :1 RMEP Number : 4

Run the display cfm mep command. If information about the MEP is displayed, it means thatthe configuration is successful.

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 : -- Interface Name : GigabitEthernet2/0/1 CCM Send : enabled Direction : outward

Run the display cfm remote-mep command. If information about the RMEP is displayed, itmeans that the configuration is successful.

<HUAWEI> display cfm remote-mepThe 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 : -- CCM Receive : enabled Trigger-If-Down : disabled



7-39

CFM Status : up

Run the display mip create-type command. If the MIP generation rule is correct, it means thatthe configuration is successful.

<HUAWEI> display mip create-type interface gigabitethernet1/0/1Interface 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 thatthe configuration is successful.

<HUAWEI> display cfm mipInterface Name Level----------------------------------- GigabitEthernet2/0/8 0

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 isdisplayed, it means that the configuration is successful.

<HUAWEI> display cfm default mdLevel MIP Create-type SenderID TLV-type VLAN List----------------------------------------------------------------------------------------7 default SendIdDefer 100 to 200 2049

Run the display cfm error-info command. If information about the incorrect configuration ofthe specified error type is displayed, it means that the configuration is successful.

<HUAWEI> display cfm error-info interface gigabitethernet1/0/2 error-type cfm-leakThe 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 specifiedinterface and VLAN or VSI is displayed, it means that the configuration is successful.

<HUAWEI> display cfm mp-info interface gigabitethernet1/0/1 level 6 inward vlan 300MD Name : md1MD Name Format : md-nameLevel : 6MA Name : ma1MEP ID : 10VLAN ID : 300VSI Name : --Interface Name : gigabitethernet1/0/1CCM Send :enableDirection : inwardMAC Address : 0018-8247-b977-----------------------------------------------------The total number of MPs is 1.The number of MEPs is 1. The number of MIPs is 0.




Issue 03 (2010-03-31)

7.7 Configuring Related Parameters of Ethernet CFMThis section describes how to Configure Related Parameters of Ethernet CFM.


7.7.2 (Optional) Configuring the RMEP Activation Time

7.7.3 (Optional) Configuring the Anti-Jitter Time During Alarm Restoration

7.7.4 (Optional) Configuring the Anti-Jitter Time During Alarm Generation


Application EnvironmentIf 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 timeAfter 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 MEPconfiguration is performed after the CC is performed. In this case, if the local MEP doesnot receive any CCMs from the RMEP in three consecutive sending intervals, the localdevice 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 thefunction of receiving CCMs from a certain RMEP, the local device can receive CCMs atthe set RMEP activation time. That is, the activation time for receiving CCMs from theRMEP is the time reserved for configuring the RMEP.At the set RMEP activation time, if the local MEP does not receive any CCMs in threeconsecutive sending intervals, this means that a connectivity fault occurs between the localMEP and the RMEP. In addition, the local device displays the alarm of the RMEPconnectivity fault.

l Anti-jitter time during alarm restorationAll 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 timerexpires, the alarm is notified to the device. When the RMEP detects that the alarm isrestored, the alarm restoration timer is activated. After the timer expires, the alarmrestoration event is notified to the device.If the RMEP frequently detects the alarm and alarm restoration signals, this means thatalarm flapping occurs.



7-41

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 MIPgeneration 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

7.7.2 (Optional) Configuring the RMEP Activation Time

Context

Do as follows on each edge device in an MA:

Procedure







Step 4 Run:active time time

The RMEP activation time is configured.

----End




Issue 03 (2010-03-31)

7.7.3 (Optional) Configuring the Anti-Jitter Time During AlarmRestoration


Procedure







Step 4 Run:alarm finish time time

The anti-jitter time during alarm restoration is configured.

----End

7.7.4 (Optional) Configuring the Anti-Jitter Time During AlarmGeneration


Procedure







Step 4 Run:



7-43

alarm occur time time

The anti-jitter time during alarm generation is configured.

----End

7.8 Fault Verification on the EthernetThis section describes the method of testing the connectivity on the Ethernet through 802.1agMAC ping or MAC ping, and the method of detecting the connectivity on the PBB-TE tunnelthrough PBB-TE MAC ping.


7.8.2 (Optional) Implementing 802.1ag MAC Ping

7.8.3 (Optional) Implementing Gmac ping



To manually detect the connectivity between two devices, you can send test packets and waitfor a reply to test whether the destination device is reachable. There are the following scenariosbased 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.1agMAC ping to test the connectivity between MEPs at the same maintenance level or betweenMEPs and MIPs at the same maintenance level.

l For the network where the MD, MA, and MEP are not configured, you can implementGmac 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 residesor 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




Issue 03 (2010-03-31)

No. Data

4 (Optional) VLAN to which the destination node belongs

5 (Optional) Name of the PBB-TE tunnel

7.8.2 (Optional) Implementing 802.1ag MAC Ping

Context

Do as follows on the router with a MEP at one end of the link to be tested:

Procedure







Step 4 Run:ping mac-8021ag { 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-idcan be selected. If remote-mep mep-id mep-id is selected, the RMEP must already be createdwith the remote-mep command and the bridge MAC address of the device on which theRMEP resides must be specified.

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



7-45

7.8.3 (Optional) Implementing Gmac ping

Context

Perform Step 1 and Step 2 on the routers at both ends of the link to be tested. Perform Step 3 onany of the routers.

Procedure



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 ] *

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 MEPor a MIP. Gmac ping can be implemented without configuring the MD, MA, or MEP on thesource 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 enabledwith IEEE 802.1ag Draft 7 and the peer is enabled with IEEE Standard 802.1ag-2007, the localdevice cannot ping through the peer device when the ping mac command is run to detectconnectivity of the link between the local and peer devices.

----End

7.9 Locating the Fault on the EthernetThis section describes the method of locating the connectivity fault on the Ethernet through802.1ag MAC trace or MAC trace, and the method of locating the connectivity fault on the PBB-TE tunnel through PBB-TE MAC trace.


7.9.2 (Optional) Implementing 802.1ag MAC Trace

7.9.3 (Optional) Implementing Gmac trace




Issue 03 (2010-03-31)



To locate the connectivity fault between two devices, you can send test packets and wait forreply packets to test the path between the local device and the destination device and to locatefaults. 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.1agMAC trace to locate the connectivity fault between MEPs at the same maintenance levelor between MEPs and MIPs at the same maintenance level.

l For the network where the MD, MA, and MEP are not configured, you can implementGmac 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-TEtunnel.


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 residesor 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

7.9.2 (Optional) Implementing 802.1ag MAC Trace

Context

Do as follows on the router with a MEP at one end of the link to be tested:



7-47

Procedure







Step 4 Run:trace mac-8021ag { mac mac-address | remote-mep mep-id mep-id } [ interface interface-type interface-number | -t timeout | ttl ttl ] *

The connectivity fault between the router 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-idcan be selected. If remote-mep mep-id mep-id is selected, the RMEP must already be createdwith the remote-mep command and the bridge MAC address of the device on which theRMEP 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

7.9.3 (Optional) Implementing Gmac trace

ContextYou 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




Issue 03 (2010-03-31)


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


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 aMEP or a MIP. Gmac trace can be implemented without configuring the MD, MA, or MEPon 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 isenabled with IEEE 802.1ag Draft 7 and the peer device is enabled with IEEE Standard802.1ag-2007, the faulty node cannot be located when the trace mac command is run todetect connectivity of the link between the local and peer devices.

----End

7.10 Associating Ethernet CFM with an InterfaceThis section describes how to associate Ethernet CFM with an interface.


7.10.2 Associating Ethernet CFM with an Interface



Applicable EnvironmentAfter Ethernet CFM is associated with an interface, when a MEP detects a connectivity faultbetween the MEP and a specified RMEP within the same MA, the OAM management moduleshuts down and then turns on the interface on which the MEP resides so that the other modulescan sense the fault.



7-49

Figure 7-6 Diagram of associating Ethernet CFM with an interface (1)

The interface associated with Ethernet CFM


Ethernet CFM


The interface associated with Ethernet CFM


Ethernet CFM

RouterCGE2/0/1 GE1/0/1

Ethernet CFM is used to detect a directly connected link shown in Figure 7-6, or a multi-hoplink shown in Figure 7-7. Configure Ethernet CFM on Router A and Router B; associate EthernetCFM with GE 1/0/1 on Router A. When the CFM OAM module on Router A detects aconnectivity fault between Router A and Router B, the OAM management module shuts downGE 1/0/1 and then starts it so that the other interfaces on Router A can sense the fault.


Ethernet CFMGE1/0/1

GE1/0/3

GE1/0/2GE1/0/1

GE1/0/2

GE1/0/3

RouterA RouterBLink1Link2Link3

Aggregation group instatic LACP mode

Active linkInactive link MEPs in MA1

MEPs in MA2MEPs in MA3

Configure the link aggregation group in static LACP mode on Router A and Router B. EnableEthernet 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 theinterfaces of the same link are configured within the same MA. MEPs on the interfaces alongthe same link belong to the same MA. MEPs on the interfaces on different links belong todifferent MAs. Ethernet CFM detects the link connectivity by exchanging CCMs between MEPsof 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 andRouter B shut down and then turn on their GE 1/0/1 interfaces respectively. In this manner, the




Issue 03 (2010-03-31)

LACP module senses the connectivity fault on Link 1 and switches the service data forwardedon Link 1 to the inactive Link 3. This implements protection switching in no more than 50 msto achieve carrier-class reliability.


RouterA RouterB

GE1/0/1

GE1/0/2

GE1/0/1

GE1/0/2

Eth-Trunk1 Eth-Trunk1

RouterC

RouterD

Active linkInactive link

Aggregation group in 1:1active/standby mode

GE2/0/1

GE2/0/1

GE2/0/2

GE2/0/2

MEPs in MA1MEPs in MA2MEPs in MA3MEPs in MA4

Ethernet CFM Ethernet CFM

Ethernet CFMEthernet CFM

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. AssociateEthernet 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 EthernetCFM module detects the fault and notifies the OAM management module of the fault. The OAMmanagement module shuts down and then starts GE 1/0/1. This allows the link aggregation groupto sense the fault and switch the service data to the inactive link. The procedure for processingconnectivity faults on the other links is similar to that for processing the link fault between RouterA and Router C. This implements protection switching in no more than 50 ms to achieve carrier-class reliability.

Pre-configuration TasksBefore associating Ethernet CFM with an interface, complete the following tasks:

l Configuring the link aggregation group


Data PreparationTo 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



7-51

7.10.2 Associating Ethernet CFM with an Interface

ContextDo as follows on the NE80E/40E configured with the link aggregation group in static LACPmode:

Procedure




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 interfaceis configured with outward-facing MEPs before you use the cfm md md-name ma ma-nameremote-mep mep-id mep-id trigger if-down command.

An interface can be associated with an RMEP only. You need to delete the current configurationsto modify the mapping between the interface and the RMEP.

If multiple member interfaces exist in the link aggregation group, you should repeat Step 2 andStep 3 to associate Ethernet CFM with all the member interfaces.

----End


PrerequisiteThe 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 ] ] ] commandto check detailed information about an RMEP.

----End

ExampleRun the display cfm remote-mep command. If the "Trigger If-down" field for the RMEP isdisplayed as "enable", it means that the configuration succeeds.

<HUAWEI> display cfm remote-mep




Issue 03 (2010-03-31)

The total number of RMEPs is 2The status of RMEPS : 2 up, 0 down-------------------------------------------------- MD Name : md1 Level : 4 MA Name : ma1 RMEP ID : 50 Vlan ID : 10 VSI Name : -- MAC : 0000-0121-0222 CCM Receive : enabled Trigger-If-Down : enabled CFM Status : up MD Name : md2 Level : 7 MA Name : ma1 RMEP ID : 30 Vlan ID : -- VSI Name : -- MAC : -- CCM Receive : enabled Trigger-If-Down : enabled CFM Status : up

7.11 Associating EFM OAM with Ethernet CFMThis section describes how to associate EFM OAM with Ethernet CFM.


7.11.2 Associating Ethernet OAM with Ethernet OAM




IEEE 802.3ah is designed for the last mile of the Ethernet to detect the direct link between a CEand a PE. IEEE 802.1ag is designed for a group of services or some specific network devices todetect 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 7-10, EFM OAM or Ethernet CFM runs between CE1 and PE1, and betweenCE2 and PE2; Ethernet CFM runs between PE1 and PE2. Configure the association betweenEthernet OAMs. When a fault occurs on the link between CE1 and PE1, Ethernet CFM sendsalarms of the fault to CE2.

Figure 7-10 Diagram of associating Ethernet OAM with Ethernet OAM

CE1 PE1 PE2 CE2



7-53

Pre-configuration TasksBefore associating Ethernet OAM with Ethernet OAM, complete the following tasks:



Data PreparationTo 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

7.11.2 Associating Ethernet OAM with Ethernet OAM

ContextDo as follows on the CEs:

Procedure



Step 2 Run the following command as required.l Run:

oam-bind cfm md md-name ma ma-name efm interface interface-type interface-numberThe bidirectional transmission of fault messages between EFM OAM and Ethernet CFM isconfigured.

l Run:oam-bind ingress efm interface interface-type interface-number egress cfm md md-name ma ma-nameEFM 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-name2Ethernet CFM at one side is configured to send fault messages to Ethernet CFM at the otherside.




Issue 03 (2010-03-31)

l Run:oam-bind cfm md md-name1 ma ma-name1 cfm md md-name2 ma ma-name2The bidirectional transmission of fault messages between Ethernet CFMs at both sides isconfigured.

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 functionalmodules is deleted.

l If an MA or MD is deleted, the association between Ethernet CFM and other functional modules isdeleted.

----End


PrerequisiteAfter the preceding configuration, when Ethernet OAM running between CE1 and PE1detectsfaults, Ethernet CFM notifies Ethernet OAM running between CE2 and PE2 of the fault.

7.12 Associating Ethernet CFM with VPLS


7.12.2 Configuring Ethernet CFM Based on the VPLS Between the PEs

7.12.3 Configuring Ethernet CFM Between the CE and Local PE

7.12.4 Configuring Ethernet CFM Between the CE and Peer PE



Applicable EnvironmentAs shown in Figure 7-11, VPLS runs between PE1 and PE2; CEs, CEs and PEs, and PEs belongto different MAs. CFM OAM runs between CEs and between CEs and PEs. CCMs are exchangedto 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 theconnectivity of the VPLS network.

Figure 7-11 Figure 6-11 Networking diagram of associating Ethernet CFM with VPLS

VPLSCE1 PE1 PE2 CE2

802.1ag 802.1ag



7-55


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

7.12.2 Configuring Ethernet CFM Based on the VPLS Between thePEs

ContextNOTE

l If 802.1ag MAC trace needs to be implemented to locate the connectivity fault between the PEs, youcannot 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 2 Run:cfm md md-name[ level level ]

An MD is created and the MD view is displayed.





Issue 03 (2010-03-31)

An MA is created and the MA view is displayed.

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:mep ccm-send [ mep-id mep-id ] enable

The MEPs are enabled to send CCMs.

Step 8 Run:remote-mep ccm-receive [ mep-id mep-id ] enable

The local MEP is enabled to receive CCMs from the RMEP within the same MA.

----End

7.12.3 Configuring Ethernet CFM Between the CE and Local PE

Procedurel 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 beoutward-facing.

1. Run:system-view


cfm md md-name [ level level ]

An MD is created and the MD view is displayed.3. Run:

ma ma-name

An MA is created and the MA view is displayed.4. Run:

map vsi vsi-name

The MA is associated with a VSI.5. Run:

mep mep-id mep-id interface { interface-type interface-number | interface-type interface-number. subnumber } outward



7-57

An outward-facing MEP is created.6. Run:

remote-mep mep-id mep-id[ mac mac-address ]

An RMEP in the MA is created.7. Run:

mep ccm-send [ mep-id mep-id ] enable

The MEPs are enabled to send CCMs on a MEP.8. Run:

remote-mep ccm-receive [ mep-id mep-id ] enable

The local MEP is enabled to receive CCMs from the RMEP in a same MA.l Do as follows on the CEs:

NOTE

The MA configured on the CE must be associated with a VLAN and the type of the MEP must beoutward-facing.

1. Run:system-view


cfm md md-name [ level level ]

An MD is created and the MD view is displayed.3. Run:

ma ma-name

An MA is created and the MA view is displayed.4. Run:

map vlan vlan-id

The MA is associated with a VLAN.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:

remote-mep mep-id mep-id [ mac mac-address ]

An RMEP in the MA is created.7. Run:

mep ccm-send [ mep-id mep-id ] enable

The MEPs are enabled to send CCMs on a MEP.8. Run:

remote-mep ccm-receive [ mep-id mep-id ] enable

The local MEP is enabled to receive CCMs from the RMEP in a same MA.

----End




Issue 03 (2010-03-31)

7.12.4 Configuring Ethernet CFM Between the CE and Peer PE

ContextThe configuration is similar to that in7.12.3 Configuring Ethernet CFM Between the CE andLocal 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 beoutward-facing.

l The rule for creating the MIP needs to be configured on transit nodes.


PrerequisiteAfter the preceding configuration, run the display cfm mep command and the display cfmremote-mep command on CE1, PE1, PE2, and CE2. You can view that the configuration ofEthernet CFM succeeds. Ethernet CFM can fast detect faults between the PEs and between theCEs and PEs, and can notify the NMS of the faults.

7.13 Associating Ethernet OAM with MPLS OAM or BFDThis section describes how to associate Ethernet OAM with MPLS OAM or BFD.


7.13.2 Configuring Ethernet OAM Functions

7.13.3 Associating Ethernet OAM with MPLS OAM or BFD



Applicable EnvironmentAs shown in Figure 7-12, CEs access PEs in dual-homing mode. PEs communicate through theMPLS network. To implement the end-to-end link detection, you can configure MPLS OAM orBFD on the MPLS Label Switch Path (LSP) or Virtual Leased Line (VLL) between PEs. EthernetOAM runs between CEs and PEs. When detecting faults, MPLS OAM or BFD at the core sidenotifies Ethernet OAM of the faults through PEs and the traffic is switched to the backup pathbetween CEs.



7-59

Figure 7-12 Diagram of associating Ethernet OAM with MPLS OAM or BFD

MPLS Core

PE1

CE1

PE2

CE2

PE3 PE4

MPLS OAM / BFD802.3ah 802.3ah


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

2 Name of an MD and an MA

3 IP addresses of interfaces on each equipment, names of tunnel interfaces, and tunnelIDs

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

7.13.2 Configuring Ethernet OAM Functions

Context

Configure Ethernet OAM to run between CEs and PEs. For details, see "Configuring EFMOAM" and "Configuring Ethernet CFM."




Issue 03 (2010-03-31)

7.13.3 Associating Ethernet OAM with MPLS OAM or BFD

Context

Do as follows on the PEs:

Procedure



Step 2 Run:oam-mgr

The OAM management view is displayed.

Step 3 Run the following command as required.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 isconfigured.

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 efm interface md-name ma ma-name egress mpls oam 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.



7-61

l Run:oam-bind ingress efm interface interface-type interface-number egress mpls oam 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


PrerequisiteAfter the preceding configuration, when MPLS OAM or BFD enabled between PE1 and PE2detects faults, EFM OAM and CFM notify CE1 of the faults and then traffic is switched to thebypass tunnel for CE1.

7.14 Configuring Ethernet CFM and 1+1 Protection ofMulticast VLANs

This section describes how to configure Ethernet CFM and 1+1 Protection of Multicast VLANs.

ContextFor details, refer to the chapter "Layer 2 Multicast Configuration" in the the HUAWEINetEngine80E/40E Router Configuration Guide - Device Management IP Multicast.

7.15 Maintaining Ethernet OAMThis section describes how to clear statistics of error CCMs, and how to monitor the runningstatus of Ethernet OAM.

7.15.1 Clearing the Statistics on Error CCMs

7.15.2 Monitoring the Running Status of Ethernet OAM

7.15.1 Clearing the Statistics on Error CCMs

Context

CAUTIONStatistics on Error CCMs cannot be restored after you clear it. So, confirm the action before youuse the command.




Issue 03 (2010-03-31)

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

7.15.2 Monitoring the Running Status of Ethernet OAM

ContextIn routine maintenance, you can select to run the following commands in any view To check therunning status of Ethernet OAM.

Procedurel 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 onthe device.

l Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] commandin any view to check information about a MEP.

l Run the display cfm mip [ interface interface-type interface-number | level level ]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 ] ] ]command in any view to check information about an RMEP.

l Run the display efm session { all | interface interface-type interface-number } commandin any view to check information about the EFM OAM session between the specifiedinterface and the peer.

----End

7.16 Configuration ExamplesThis section provides several configuration examples of Ethernet OAM.

7.16.1 Example for Configuring EFM OAM

7.16.2 Example for Testing the Packet Loss Ratio on the Link

7.16.3 Example for Configuring Ethernet CFM

7.16.4 Example for Configuring the Default MD for Ethernet CFM

7.16.5 Example for Associating Ethernet CFM with an Interface

7.16.6 Example for Associating EFM OAM with Ethernet CFM

7.16.7 Example for Configuring VPLS Ethernet CFM

7.16.8 Example for Associating EFM OAM with MPLS OAM

7.16.9 Example for Configuring EFM OAM Extension for VRRP



7-63

7.16.10 Exmaple for Configuring EFM OAM Extension for Static Routes

7.16.1 Example for Configuring EFM OAM

Networking RequirementsAs shown in Figure 7-13, a user network is connected to an ISP network through Router A andRouter 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 andRouter 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 GE2/0/1. When the number of errored frames, errored codes, and errored frame seconds exceedthe corresponding threshold, Router B generates alarms.

Figure 7-13 Diagram of configuring EFM OAM

Usernetwork

ISP networkRouterB

GE2/0/1GE1/0/1

RouterA


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.


l The period for detecting errored frames on GE 2/0/1 on Router B is five seconds and thethreshold is five.

l The period for detecting errored codes on GE 2/0/1 on Router B is five seconds and thethreshold is five.

l The period for detecting errored frame seconds on GE 2/0/1 on Router B is 120 secondsand the threshold is five.




Issue 03 (2010-03-31)

Procedure

Step 1 Enable EFM OAM globally.

# Enable EFM OAM globally on Router A.

<HUAWEI> system-view[HUAWEI] sysname RouterA[RouterA] efm enable

# Enable EFM OAM globally on Router B.

<HUAWEI> system-view[HUAWEI] sysname RouterB[RouterB] efm enable

Step 2 Configure EFM OAM on GE 1/0/1 on Router A to work in passive mode.[RouterA] interface gigabitethernet 1/0/1[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 frameseconds.

# Configure GE 2/0/1 on Router B to detect the errored frames.

[RouterB] interface gigabitethernet 2/0/1[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[RouterA-GigabitEthernet1/0/1] quit

# Enable EFM OAM on GE 2/0/1 on Router B.

[RouterB-GigabitEthernet2/0/1] efm enable[RouterB-GigabitEthernet2/0/1] quit


# Run the display efm session command. If the EFM OAM state on the interface is Detect, itmeans that the configuration succeeds. EFM OAM is correctly configured on Router A andRouter B, and GE 2/0/1 and GE 1/0/1 succeed in negotiation and enter the Detect state. Forexample, the EFM OAM state on GE 2/0/1 on RouterB is displayed as follows:

[RouterB] display efm session interface gigabitethernet 2/0/1 Interface EFM State Loopback Timeout -------------------------------------------------------------------- GigabitEthernet2/0/1 detect --



7-65

# Run the display efm command. If the EFM OAM configuration information on GE 2/0/1 onRouter B is displayed, it means that the configuration succeeds. The displayed information is asfollows:

[RouterB] display efm interface gigabitethernet 2/0/1 Item Value ------------------------------------- Interface: GigabitEthernet2/0/1 EFM Enable Flag: enable Mode: active OAMPDU MaxSize: 128 ErrCodeNotification: enable ErrCodePeriod: 5 ErrCodeThreshold: 5 ErrFrameNotification: enable ErrFramePeriod: 5 ErrFrameThreshold: 5 ErrFrameSecondNotification: enable ErrFrameSecondPeriod: 120 ErrFrameSecondThreshold: 5 TriggerIfDown: disable Remote MAC: 0010-0010-0010 Remote EFM Enable Flag: enable Remote Mode: passive Remote MaxSize: 128

----End


#sysname RouterA# efm enable#interface GigabitEthernet1/0/1 efm mode passive efm enable#return

l Configuration file of Router B#sysname RouterB# efm enable#interface GigabitEthernet2/0/1 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




Issue 03 (2010-03-31)

7.16.2 Example for Testing the Packet Loss Ratio on the Link

Networking RequirementsAs shown in Figure 7-14, a user network is connected to an ISP network through Router A andRouter B. Router A acts as the CE device. Router B acts as the UPE device. The link betweenRouter A and Router B is newly established. The ISP needs to test the packet loss ratio on thelink on Router B before using the link.

Figure 7-14 Diagram of testing the packet loss ratio on the link

Usernetwork

ISP networkRouterB

GE2/0/1GE1/0/1

RouterA


1. Enable EFM OAM on Router A and Router B. Configure EFM OAM on GE 1/0/1 on RouterA 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.


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.

<HUAWEI> system-view[HUAWEI] sysname RouterB[RouterB] efm enable

# Enable EFM OAM globally on Router A.

<HUAWEI> system-view[HUAWEI] sysname RouterA



7-67

[RouterA] efm enable

# Configure EFM OAM on GE 1/0/1 on Router A to work in passive mode.

[RouterA] interface gigabitethernet 1/0/1[RouterA-GigabitEthernet1/0/1] efm mode passive

# Enable EFM OAM on GE 1/0/1 on Router A.

[RouterA-GigabitEthernet1/0/1] efm enable[RouterA-GigabitEthernet1/0/1] quit

# Enable EFM OAM on GE 2/0/1 on Router B.

[RouterB] interface gigabitethernet 2/0/1[RouterB-GigabitEthernet2/0/1] efm enable[RouterB-GigabitEthernet2/0/1] quit

# Verify the configuration.

Run the display efm session command. If the EFM OAM protocol on the interface is in theDetect state, it means that the configuration succeeds. EFM OAM is correctly configured onRouter A and Router B, and GE 2/0/1 and GE 1/0/1 succeed in negotiation and enter the Detectstate. 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 Interface EFM State Loopback Timeout -------------------------------------------------------------------- GigabitEthernet2/0/1 detect --

Step 2 Configure EFM OAM remote loopback.

# Enable remote loopback on Router B.

[RouterB] interface gigabitethernet 2/0/1[RouterB-GigabitEthernet2/0/1] efm loopback start[RouterB-GigabitEthernet2/0/1] quit


Run the display efm session command on Router B. If the EFM OAM protocol on GE 2/0/1 isin the loopback (control) state, that is, GE 2/0/1 initiates remote loopback, it means that theconfiguration succeeds. The displayed information is as follows:

[RouterB] display efm session interface gigabitethernet2/0/1Interface EFM State Loopback Timeout----------------------------------------------------------------------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 isin the loopback (be controlled) state, that is, GE 1/0/1 responds to remote loopback, it meansthat the configuration succeeds. The displayed information is as follows:

[RouterA] display efm session interface gigabitethernet1/0/1Interface EFM State Loopback Timeout----------------------------------------------------------------------GigabitEthernet1/0/1 Loopback(be controlled) --

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--------------------------------------------------------




Issue 03 (2010-03-31)

PacketsSend : 5 PacketsReRouterAive : 5 PacketsLost : 0 BytesSend : 320 BytesReRouterAive : 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] interface gigabitethernet 2/0/1[RouterB-GigabitEthernet2/0/1] efm loopback stop[RouterB-GigabitEthernet2/0/1] quit

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 manuallydisabled, you can view that the status of the EFM OAM protocol on the interface is no longerloopback (control) or loopback (be controlled). For example, the EFM OAM status on GE 2/0/1on RouterB is displayed as follows:

[RouterB] display efm session interface gigabitethernet2/0/1Interface EFM State Loopback Timeout----------------------------------------------------------------------GigabitEthernet2/0/1 Detect --

----End


#sysname RouterA# efm enable#interface GigabitEthernet1/0/1 efm mode passive efm enable#return

l Configuration file of Router B#sysname RouterB# efm enable#interface GigabitEthernet2/0/1 efm enable#return



7-69

7.16.3 Example for Configuring Ethernet CFM


The Ethernet shown in Figure 7-15 is managed by two ISPs. ISP 1 manages Router A, RouterB, and Router D. ISP 2 manages Router C, Router E, Router F, Router G, Router H, and RouterI. It is required that connectivity detection be implemented on the network.

Figure 7-15 Diagram of configuring Ethernet CFM

MD1

MD2

RouterA

RouterB

RouterCRouterD

RouterE

RouterF

RouterGRouterH

RouterIGE1/0/0

GE1/0/1

GE1/0/2

GE1/0/0

GE1/0/0

GE1/0/1

GE1/0/2

GE1/0/0

GE1/0/1

GE1/0/1GE1/0/2 GE1/0/0

MD1MEP of MA1MEP of MA2

MD2MEP of MA3

GE1/0/1

VLAN3VLAN3VLAN2

VLAN2

VLAN2



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 VLAN2.




Issue 03 (2010-03-31)

4. Create MA 2 within MD 1 on all the routers except Router E and Router I. Associate MA2 with VLAN 3.

5. Create MD 2 at level 4 on Router A, Router B, Router C, and Router D. Create MA 3 withinMD 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 isnot mentioned here.

Step 2 Create MD 1.

# Create MD 1 on Router A.

<RouterA> system-view[RouterA] cfm enable[RouterA] cfm md md1 level 6

# Create MD 1 on Router B, Router C, Router D, Router E, Router F, Router G, Router H, andRouter I.

The detailed configuration is not mentioned here. The configuration is similar to that on RouterA.

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.


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] ma ma2[RouterA-md-md1-ma-ma2] map vlan 3[RouterA-md-md1-ma-ma2] quit[RouterA-md-md1] quit



7-71

# Create and configure MA 2 on Router B, Router C, Router D, Router F, Router G, and RouterH within MD 1.


Step 5 Create MD 2 on Router A, Router B, Router C, and Router D. Create and configure MA 3 withinMD 2.

# Create MD 2 on Router A. Create and configure MA 3 within MD 2.

[RouterA] cfm md md2 level 4[RouterA-md-md2] ma ma3[RouterA-md-md2-ma-ma3] map vlan 4[RouterA-md-md2-ma-ma3] quit[RouterA-md-md2] quit

# Create MD 2 on Router B, Router C, and RouterD. Create and configure MA 3 within MD 2.


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[RouterE-md-md1-ma-ma1] remote-mep mep-id 2

# Configure an RMEP on RouterH in MA 1 within MD 1.

[RouterH-md-md1-ma-ma1] remote-mep mep-id 1[RouterH-md-md1-ma-ma1] remote-mep mep-id 3

# 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




Issue 03 (2010-03-31)

[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.

[RouterH-md-md1-ma-ma2] remote-mep mep-id 2

# 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[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[RouterA-md-md2-ma-ma3] remote-mep mep-id 3

# Configure an RMEP on Router C in MA 3 within MD 2.

[RouterC-md-md2-ma-ma3] remote-mep mep-id 1[RouterC-md-md2-ma-ma3] remote-mep mep-id 3

# 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.


----End


#



7-73

sysname RouterA#vlan batch 2 to 4#cfm enable#interface GigabitEthernet1/0/0 portswitch port trunk allow-pass vlan 2 to 4#interface GigabitEthernet1/0/1 portswitch port trunk allow-pass vlan 2 to 4#interface GigabitEthernet1/0/2 portswitch port trunk allow-pass vlan 2 to 4# 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 remote-mep ccm-receive mep-id 3 enable#return

l Configuration file of Router B# sysname RouterB#vlan batch 2 to 4#cfm enable#interface GigabitEthernet1/0/0 portswitch port trunk allow-pass vlan 2 to 4#interface GigabitEthernet1/0/1 portswitch port trunk allow-pass vlan 2 to 4#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

l Configuration file of Router C# sysname RouterC#vlan batch 2 to 4#




Issue 03 (2010-03-31)

cfm enable#interface GigabitEthernet1/0/0 portswitch port trunk allow-pass vlan 2 to 4#interface GigabitEthernet1/0/1 portswitch port trunk allow-pass vlan 2 to 4#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 mep ccm-send mep-id 2 enable remote-mep mep-id 1 remote-mep ccm-receive mep-id 1 enable remote-mep mep-id 3 remote-mep ccm-receive mep-id 3 enable#return

l Configuration file of Router D# sysname RouterD#vlan batch 2 to 4#cfm enable#interface GigabitEthernet1/0/0 portswitch port trunk allow-pass vlan 2 to 4#interface GigabitEthernet1/0/2 portswitch port trunk allow-pass vlan 2 to 4# 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 3 interface gigabitethernet 1/0/0 inward mep ccm-send mep-id 3 enable remote-mep mep-id 1 remote-mep ccm-receive mep-id 1 enable remote-mep mep-id 2 remote-mep ccm-receive mep-id 2 enable#return

l Configuration file of Router E# sysname RouterE#vlan batch 2#cfm enable#



7-75

interface GigabitEthernet1/0/0 portswitch port trunk allow-pass vlan 2#interface GigabitEthernet1/0/1 portswitch port trunk allow-pass vlan 2# cfm md md1 level 6 ma ma1 map vlan 2 mep mep-id 3 interface gigabitethernet 1/0/1 inward mep ccm-send mep-id 3 enable remote-mep mep-id 1 remote-mep ccm-receive mep-id 1 enable remote-mep mep-id 2 remote-mep ccm-receive mep-id 2 enable#return

l Configuration file of Router F# sysname RouterF#vlan batch 2 to 3#cfm enable#interface GigabitEthernet1/0/0 portswitch port trunk allow-pass vlan 2#interface GigabitEthernet1/0/1 portswitch port trunk allow-pass vlan 2 to 3#interface GigabitEthernet1/0/2 portswitch port trunk allow-pass vlan 3# 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#interface GigabitEthernet1/0/0 portswitch port trunk allow-pass vlan 3#interface GigabitEthernet1/0/2 portswitch port trunk allow-pass vlan 3# cfm md md1 level 6 ma ma2 map vlan 3 mep mep-id 2 interface gigabitethernet 1/0/0 inward mep ccm-send mep-id 2 enable remote-mep mep-id 1




Issue 03 (2010-03-31)

remote-mep ccm-receive mep-id 1 enable#return

l Configuration file of Router H# sysname RouterH#vlan batch 2 to 3#cfm enable#interface GigabitEthernet1/0/0 portswitch port trunk allow-pass vlan 2 to 3#interface GigabitEthernet1/0/1 portswitchport trunk allow-pass vlan 3#interface GigabitEthernet1/0/2 portswitch port trunk allow-pass vlan 2# cfm md md1 level 6 ma ma1 map vlan 2 mep mep-id 2 interface gigabitethernet 1/0/2 inward mep ccm-send mep-id 2 enable remote-mep mep-id 1 remote-mep ccm-receive mep-id 1 enable remote-mep mep-id 3 remote-mep ccm-receive mep-id 3 enable ma ma2 map vlan 3 mep mep-id 1 interface gigabitethernet 1/0/1 inward mep ccm-send mep-id 1 enable remote-mep mep-id 2 remote-mep ccm-receive mep-id 2 enable#return

l Configuration file of Router I# sysname RouterI#vlan batch 2#cfm enable#interface GigabitEthernet1/0/0 portswitch port trunk allow-pass vlan 2#interface GigabitEthernet1/0/1 portswitch port trunk allow-pass vlan 2# cfm md md1 level 6 ma ma1 map vlan 2 mep mep-id 1 interface gigabitethernet 1/0/1 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 remote-mep ccm-receive mep-id 3 enable#return



7-77

7.16.4 Example for Configuring the Default MD for Ethernet CFM


As shown in Figure 7-16, Router B and Router C are managed by ISP1, and Router A, RouterD, Router E, and Router F are managed by ISP2. To enable the CFM function, you can configurethe default MD on the device configured with an MD of a low level.

Figure 7-16 Networking diagram of configuring the default MD for Ethernet CFM

GE1/0/1

GE1/0/2

MEP of MA1MEP of MA2MIP

RouterA RouterD

RouterE

RouterFGE1/0/3

GE1/0/1

GE1/0/2

RouterB

RouterC

GE1/0/1GE1/0/2

GE1/0/1

GE1/0/3

VLAN2

VLAN3

VLAN3

VLAN2



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 withVLAN 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 andRouter C. (MA1 is associated with VLAN 2.)

Create and configure MA2 within MD1 on all the devices except for Router B andRouter C.. (MA2 is associated with VLAN 3.)




Issue 03 (2010-03-31)

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.


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.NOTEBy 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> system-view[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]:yInfo: 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 asthe configurations on Router A, and are not mentioned here.

NOTEAll the devices on the network must be enabled with either IEEE 802.1ag Draft 7 or IEEE Standard802.1ag-2007. IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007 cannot be enabled at the same timeon a network.

Step 2 Create a VLAN and add related interfaces to the VLAN. The configuration is not mentionedhere.

Step 3 Create MD1.

# Create MD1 on Router A.

<RouterA> system-view[RouterA] cfm enableInfo: Enable the CFM successfully![RouterA] cfm md md1 level 6[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 onRouter A, and are not mentioned here.

Step 4 Create MD2.

# Create MD2 on Router B.



7-79

<RouterB> system-view[RouterB] cfm enableInfo: 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 notmentioned here.

Step 5 Create the default MD and associate the default MD with VLAN 2 and VLAN 3 on Router Band Router C.

# Create the default MD and associate the default MD to VLAN 2 and VLAN 3 on Router C.

<RouterB> system-view[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.


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> system-view[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.


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.

[RouterA] cfm md md1[RouterA-md-md1] ma ma1[RouterA-md-md1-ma-ma1] map vlan 2[RouterA-md-md1-ma-ma1] quit

# 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.

[RouterA-md-md1] ma ma2[RouterA-md-md1-ma-ma2] map vlan 3[RouterA-md-md1-ma-ma2] quit[RouterA-md-md1] quit

# Create MA2 within MD1 on Router D and Router E.




Issue 03 (2010-03-31)

The configurations on Router D and Router E are the same as the configurations on Router A,and are not mentioned here.

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.

[RouterA-md-md1-ma-ma1] remote-mep mep-id 1

# 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.

[RouterA-md-md1-ma-ma2] remote-mep mep-id 2

# Create and configure an RMEP in MA2 within MD1 on Router E.

[RouterE-md-md1-ma-ma2] remote-mep mep-id 1

Step 11 Enable the CCM transmission function.

# Enable the function of sending CCMs on all MEPs of Router A.

[RouterA-md-md1-ma-ma2] mep ccm-send enable

# Enable Router A with the function of receiving CCMs from the RMEP.

[RouterA-md-md1-ma-ma2] remote-mep ccm-receive enable

# Enable the function of sending CCMs on all MEPs of Router E and Router F, and enable thefunction 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,and are not mentioned here.


After the preceding configurations are successful and the network converges, run the followingcommands to verify the configuration. Take the display on Router B and Router A as an example:



7-81

l Run the display cfm default md command on Router B. You can view that the default MDat Level 6 is configured and associated with VLAN 2 and VLAN 3. You can also view thatthe MIP generation rule is set to default.[RouterB] display cfm default mdLevel MIP Create-type SenderID TLV-type VLAN List----------------------------------------------------------------------------------------6 default SendIdDefer 2 to 3

l Perform the 802.1ag MAC trace operation on Router A. You can view that the 802.1ag MACtrace operation is successful and no connectivity fault occurs between Router A andRouter E<RouterA> system[RouterA] cfm md md1[RouterA-md-md1] ma ma1[RouterA--md-md1-ma-ma1] trace mac-8021ag mac aa99-6600-5600Tracing 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 2 5522-1101-5503 gigabitethernet1/0/1 IngOK RlyFDB Forwarded gigabitethernet1/0/2 EgrOk No 3 2234-6432-3344 gigabitethernet1/0/2 IngOK RlyFDB Forwarded gigabitethernet1/0/3 EgrOk No 4 4323-5332-5522 gigabitethernet1/0/3 IngOK RlyFDB Forwarded gigabitethernet1/0/1 EgrOk No 5 aa99-6600-5600 gigabitethernet1/0/1 IngOK RlyHit Not Forwarded Yes Info: Succeed in tracing the destination address aa99-6600-5600.

----End


# sysname RouterA# vlan batch 2 to 3# cfm version standard cfm enable# interface GigabitEthernet1/0/1 undo shutdown portswitch port trunk allow-pass vlan 2# interface GigabitEthernet1/0/2 undo shutdown portswitch port trunk allow-pass vlan 3# interface GigabitEthernet1/0/3 undo shutdown portswitch port trunk allow-pass vlan 2 to 3




Issue 03 (2010-03-31)

# cfm md md1 level 6 ma ma1 map vlan 2 mep mep-id 2 interface gigabitethernet 1/0/1 inward mep ccm-send mep-id 2 enable remote-mep mep-id 1 remote-mep ccm-receive mep-id 1 enable ma ma2 map vlan 3 mep mep-id 1 interface gigabitethernet 1/0/2 inward mep ccm-send mep-id 1 enable remote-mep mep-id 2 remote-mep ccm-receive mep-id 2 enable#return

l Configuration file of Router B# sysname RouterB#vlan batch 2 to 3#cfm version standardcfm enable#interface GigabitEthernet1/0/1 undo shutdown portswitch port trunk allow-pass vlan 2 to 3#interface GigabitEthernet1/0/3 undo shutdown portswitch port trunk allow-pass vlan 2 to 3# cfm md md2 level 4 # cfm default md level 6 mip create-type defaul vlan 2 to 3#return

l Configuration file of Router C# sysname RouterC#vlan batch 2 to 3#cfm version standardcfm enable#interface GigabitEthernet1/0/1 undo shutdown portswitch port trunk allow-pass vlan 2 to 3#interface GigabitEthernet1/0/2 undo shutdown portswitch port trunk allow-pass vlan 2 to 3# cfm md md2 level 4 # cfm default md level 6 mip create-type defaul vlan 2 to 3#



7-83

returnl Configuration file of Router D

# sysname RouterD#vlan batch 2 to 3#cfm version standardcfm enable#interface GigabitEthernet1/0/1 undo shutdown portswitch port trunk allow-pass vlan 2 to 3#interface GigabitEthernet1/0/2 undo shutdown portswitch port trunk allow-pass vlan 2 to 3#interface GigabitEthernet1/0/3 undo shutdown portswitch port trunk allow-pass vlan 2 to 3# 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 version standardcfm enable#interface GigabitEthernet1/0/1 undo shutdown portswitch port trunk allow-pass vlan 3#interface GigabitEthernet1/0/2 undo shutdown portswitch port trunk allow-pass vlan 3# cfm md md1 level 6 ma ma2 map vlan 3 mep mep-id 2 interface gigabitethernet 1/0/2 inward mep ccm-send mep-id 2 enable remote-mep mep-id 1 remote-mep ccm-receive mep-id 1 enable#return

l Configuration file of Router F# sysname RouterF#vlan batch 2#cfm version standard




Issue 03 (2010-03-31)

cfm enable#interface GigabitEthernet1/0/1 undo shutdown portswitch port trunk allow-pass vlan 2#interface GigabitEthernet1/0/3 undo shutdown portswitch port trunk allow-pass vlan 2# cfm md md1 level 6 ma ma1 map vlan 2 mep mep-id 1 interface gigabitethernet 1/0/1 inward mep ccm-send mep-id 1 enable remote-mep mep-id 2 remote-mep ccm-receive mep-id 2 enable#return

7.16.5 Example for Associating Ethernet CFM with an Interface

Networking RequirementsAs shown in Figure 7-17, a user network is connected to an ISP network through Router A andRouter B. Router A acts as the CE device. Router B acts as the UPE device. It is required thatthe following be achieved:

l The bandwidth for the user network to access the ISP network is 2000 Mbit/s and an inactivelink that serves as a backup is provided.

l When the active link between the user network and the ISP network fails, the LACP moduleon the interface can sense the fault within 50 ms and stop forwarding data on the activelink.



7-85

Figure 7-17 Diagram of associating Ethernet CFM with an interface

RouterB

GE1/0/1GE1/0/2

GE1/0/1

GE1/0/3

GE1/0/2GE1/0/3

RouterA

ISP network

Link aggregation group instatic LACP mode

Active linkInactive link

Usernetwork 1


1. Configure the link aggregation group with three member interfaces on Router A and RouterB 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 sensethe connectivity fault within 50 ms, set the interval for sending and detecting CCMs to 10ms within each MA.

3. Associate Ethernet CFM with all the member interfaces of the aggregation groups in staticLACP mode on Router A and Router B.


l The number of the aggregation groups in static LACP mode on Router A and Router B is2.

l The three member interfaces of the aggregation group in static LACP mode on Router Bare 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 Aare GE 1/0/1, GE 1/0/2, and GE 1/0/3.




Issue 03 (2010-03-31)

ProcedureStep 1 Configure the aggregation group in static LACP mode.

The detailed configuration is not mentioned here. For details, refer to the HUAWEINetEngine80E/40E Router Configuration Guide - LAN and MAN Access.

Step 2 Configure Ethernet CFM.

# Enable Ethernet CFM globally on Router A.

[RouterA] cfm enable

# Create the MD, MA, MEP, and RMEP on Router A.

[RouterA] cfm md md1[RouterA-md-md1] ma ma1[RouterA-md-md1-ma-ma1] ccm-interval 10[RouterA-md-md1-ma-ma1] mep mep-id 2 interface gigabitethernet 1/0/1 outward[RouterA-md-md1-ma-ma1] remote-mep mep-id 1[RouterA-md-md1-ma-ma1] mep ccm-send enable[RouterA-md-md1-ma-ma1] remote-mep ccm-receive enable[RouterA-md-md1-ma-ma1] quit[RouterA-md-md1] ma ma2[RouterA-md-md1-ma-ma2] ccm-interval 10[RouterA-md-md1-ma-ma2] mep mep-id 4 interface gigabitethernet 1/0/2 outward[RouterA-md-md1-ma-ma2] remote-mep mep-id 3[RouterA-md-md1-ma-ma2] mep ccm-send enable[RouterA-md-md1-ma-ma2] remote-mep ccm-receive enable[RouterA-md-md1-ma-ma2] quit[RouterA-md-md1] ma ma3[RouterA-md-md1-ma-ma3] ccm-interval 10[RouterA-md-md1-ma-ma3] mep mep-id 6 interface gigabitethernet 1/0/3 outward[RouterA-md-md1-ma-ma3] remote-mep mep-id 5[RouterA-md-md1-ma-ma3] mep ccm-send enable[RouterA-md-md1-ma-ma3] remote-mep ccm-receive enable[RouterA-md-md1-ma-ma3] quit[RouterA-md-md1] quit

# Enable Ethernet CFM globally on Router B.

[RouterB] cfm enable

# 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] ma ma2[RouterB-md-md1-ma-ma2] ccm-interval 10[RouterB-md-md1-ma-ma2] mep mep-id 3 interface gigabitethernet 1/0/2 outward[RouterB-md-md1-ma-ma2] remote-mep mep-id 4[RouterB-md-md1-ma-ma2] mep ccm-send enable[RouterB-md-md1-ma-ma2] remote-mep ccm-receive enable[RouterB-md-md1-ma-ma2] quit[RouterB-md-md1] ma ma3[RouterB-md-md1-ma-ma3] ccm-interval 10[RouterB-md-md1-ma-ma3] mep mep-id 5 interface gigabitethernet 1/0/3 outward[RouterB-md-md1-ma-ma3] remote-mep mep-id 6[RouterB-md-md1-ma-ma3] mep ccm-send enable[RouterB-md-md1-ma-ma3] remote-mep ccm-receive enable[RouterB-md-md1-ma-ma3] quit[RouterB-md-md1] quit[RouterB] quit



7-87


Run the display cfm mep command and the display cfm remote-mep command. If informationabout 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 md1The total number of MEPs is 3 MD Name : md1 Level : 0 MA Name : ma1 MEP ID : 1 Vlan ID : -- VSI Name : -- Interface Name : GigabitEthernet1/0/1 CCM Send : enabled Direction : outward MD Name : md1 Level : 0 MA Name : ma2 MEP ID : 3 Vlan ID : -- VSI Name : -- Interface Name : GigabitEthernet1/0/2 CCM Send : enabled Direction : outward MD Name : md1 Level : 0 MA Name : ma3 MEP ID : 5 Vlan ID : -- VSI Name : -- Interface Name : GigabitEthernet1/0/3 CCM Send : enabled Direction : outward[RouterB] display cfm remote-mep md md1The total number of RMEPs is 3The status of RMEPS : 3 up, 0 down -------------------------------------------------- MD Name : md1 Level : 0 MA Name : ma1 RMEP ID : 2 Vlan ID : -- VSI Name : -- MAC : -- CCM Receive : enabled Trigger-If-Down : disabled CFM Status : up MD Name : md1 Level : 0 MA Name : ma2 RMEP ID : 4 Vlan ID : -- VSI Name : -- MAC : -- CCM Receive : enabled Trigger-If-Down : disabled CFM Status : up MD Name : md1 Level : 0 MA Name : ma3 RMEP ID : 6 Vlan ID : -- VSI Name : -- MAC : -- CCM Receive : enabled Trigger-If-Down : disabled CFM Status : up




Issue 03 (2010-03-31)

Step 3 Associate Ethernet CFM with the member interfaces of the aggregation group in static LACPmode.

# 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[RouterA-GigabitEthernet1/0/1] quit[RouterA] interface gigabitethernet1/0/2[RouterA-GigabitEthernet1/0/2] cfm md md1 ma ma2 remote-mep mep-id 3 trigger if-down[RouterA-GigabitEthernet1/0/2] quit[RouterA] interface gigabitethernet1/0/3[RouterA-GigabitEthernet1/0/3] cfm md md1 ma ma3 remote-mep mep-id 5 trigger if-down[RouterA-GigabitEthernet1/0/3] quit

# Associate Ethernet CFM with the member interfaces of Eth-Trunk 2 on Router B.

[RouterB] interface gigabitethernet1/0/1[RouterB-GigabitEthernet1/0/1] cfm md md1 ma ma1 remote-mep mep-id 2 trigger if-down[RouterB-GigabitEthernet1/0/1] quit[RouterB] interface gigabitethernet1/0/2[RouterB-GigabitEthernet1/0/2] cfm md md1 ma ma2 remote-mep mep-id 4 trigger if-down[RouterB-GigabitEthernet1/0/2] quit[RouterB] interface gigabitethernet1/0/3[RouterB-GigabitEthernet1/0/3] cfm md md1 ma ma3 remote-mep mep-id 6 trigger if-down[RouterB-GigabitEthernet1/0/3] quit


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 onRouter B is displayed as follows:

[RouterB] display cfm remote-mep md md1The total number of RMEPs is 3 MD Name : md1 Level : 0 MA Name : ma1 RMEP ID : 2 Vlan ID : -- VSI Name : -- MAC : -- CCM Receive : enabled Trigger-If-Down : enabled CFM Status : up MD Name : md1 Level : 0 MA Name : ma2 RMEP ID : 4 Vlan ID : -- VSI Name : -- MAC : -- CCM Receive : enabled Trigger-If-Down : enabled CFM Status : up MD Name : md1 Level : 0 MA Name : ma3 RMEP ID : 6 Vlan ID : -- VSI Name : -- MAC : -- CCM Receive : enabled Trigger-If-Down : enabled CFM Status : up

----End



7-89


# sysname RouterA# cfm enable#interface Eth-Trunk2 portswitch mode lacp-static#interface GigabitEthernet1/0/1 eth-trunk 2 cfm md md1 ma ma1 remote-mep mep-id 1 trigger if-down#interface GigabitEthernet1/0/2 eth-trunk 2 cfm md md1 ma ma2 remote-mep mep-id 3 trigger if-down#interface GigabitEthernet1/0/3 eth-trunk 2 cfm md md1 ma ma3 remote-mep mep-id 5 trigger if-down# cfm md md1 ma ma1 ccm-interval 10 mep mep-id 2 interface GigabitEthernet1/0/1 outward mep ccm-send mep-id 2 enable remote-mep mep-id 1 remote-mep ccm-receive mep-id 1 enable ma ma2 ccm-interval 10 mep mep-id 4 interface GigabitEthernet1/0/2 outward mep ccm-send mep-id 4 enable remote-mep mep-id 3 remote-mep ccm-receive mep-id 3 enable ma ma3 ccm-interval 10 mep mep-id 6 interface GigabitEthernet1/0/3 outward mep ccm-send mep-id 6 enable remote-mep mep-id 5 remote-mep ccm-receive mep-id 5 enable#return

l Configuration file of Router B# sysname RouterB# lacp priority 100# cfm enable#interface Eth-Trunk2 portswitch mode lacp-static max bandwidth-affected-linknumber 2#interface GigabitEthernet1/0/1 eth-trunk 2 lacp priority 2000 cfm md md1 ma ma1 remote-mep mep-id 2 trigger if-down#interface GigabitEthernet1/0/2 eth-trunk 2 lacp priority 2000 cfm md md1 ma ma2 remote-mep mep-id 4 trigger if-down#




Issue 03 (2010-03-31)

interface GigabitEthernet1/0/3 eth-trunk 2 cfm md md1 ma ma3 remote-mep mep-id 6 trigger if-down# cfm md md1 ma ma1 ccm-interval 10 mep mep-id 1 interface GigabitEthernet1/0/1 outward mep ccm-send mep-id 1 enable remote-mep mep-id 2 remote-mep ccm-receive mep-id 2 enable ma ma2 ccm-interval 10 mep mep-id 3 interface GigabitEthernet1/0/2 outward mep ccm-send mep-id 3 enable remote-mep mep-id 4 remote-mep ccm-receive mep-id 4 enable ma ma3 ccm-interval 10 mep mep-id 5 interface GigabitEthernet1/0/3 outward mep ccm-send mep-id 5 enable remote-mep mep-id 6 remote-mep ccm-receive mep-id 6 enable#return

7.16.6 Example for Associating EFM OAM with Ethernet CFM


As shown in Figure 7-18, configure EFM OAM to run between Router A and Router B, andbetween Router C and Router D; configure Ethernet CFM to run between Router B and RouterC. This implements end-to-end link detection. When a fault occurs on the link between RouterA and Router B, Ethernet CFM is triggered to send alarms of the fault to Router D.When a faultoccurs on the link between Router C and Router D, Ethernet CFM is triggered to send alarmsof the fault to Router A.

Figure 7-18 Diagram of associating EFM OAM with Ethernet CFM

RouterA RouterB RouterC RouterDGE2/0/0 GE1/0/0

GE2/0/0

GE2/0/0 GE1/0/0

GE2/0/0

GE1/0/0

GE1/0/0

VLAN10 VLAN10



1. Create a VLAN and add interfaces to the VLAN.



7-91

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 Router A.

[RouterA] efm enable[RouterA] interface gigabitethernet 1/0/0[RouterA-GigabitEthernet1/0/0] efm mode passive[RouterA-GigabitEthernet1/0/0] efm enable[RouterA-GigabitEthernet1/0/0] quit

# Configure RouterB.

[RouterB] efm enable[RouterB] interface gigabitethernet 1/0/0[RouterB-GigabitEthernet1/0/0] efm enable[RouterB-GigabitEthernet1/0/0] quit

Step 3 Configure Ethernet CFM to run between Router B and Router C.

# Configure Router B.

[RouterB] cfm enable[RouterB] cfm md md1[RouterB-md-md1] ma ma1[RouterB-md-md1-ma-ma1] map vlan 10[RouterB-md-md1-ma-ma1] mep mep-id 1 interface gigabitethernet 2/0/0 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] return

# Configure Router C.

[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] remote-mep mep-id 1[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.

# Configure Router C.

[RouterC] efm enable[RouterC] interface gigabitethernet 1/0/0[RouterC-GigabitEthernet1/0/0] efm enable[RouterC-GigabitEthernet1/0/0] quit

# Configure Router D.

[RouterD] efm enable[RouterD] interface gigabitethernet 1/0/0[RouterD-GigabitEthernet1/0/0] efm mode passive




Issue 03 (2010-03-31)

[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 runningbetween Router B and Router C.

[RouterB] oam-mgr[RouterB] oam-bind cfm md md1 ma ma1 efm interface gigabitethernet 1/0/0

# Associate Ethernet CFM running between RouterB and RouterC with EFM OAM runningbetween Router C and Router D.

[RouterC] oam-mgr[RouterC] 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 Bdetects faults, Ethernet CFM notifies EFM OAM running between Router C and Router D ofthe faults.

----End


# sysname RouterA# vlan batch 10#efm enable#interface GigabitEthernet1/0/0 portswitch port trunk allow-pass vlan 10 efm mode passive efm enable#interface GigabitEthernet2/0/0 portswitch port trunk allow-pass vlan 10#return

l Configuration file of Router B# sysname RouterB#vlan batch 10#efm enable#cfm enable#interface GigabitEthernet1/0/0 portswitch port trunk allow-pass vlan 10 efm enable#interface GigabitEthernet2/0/0 portswitch port trunk allow-pass vlan 10# cfm md md1



7-93

ma ma1 map vlan 10 mep mep-id 1 interface gigabitethernet 2/0/0 outward 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

l Configuration file of Router C# sysname RouterC#vlan batch 10#efm enable#cfm enable#interface GigabitEthernet2/0/0 portswitch port trunk allow-pass vlan 10 efm enable#interface GigabitEthernet1/0/0 portswitch port trunk allow-pass vlan 10# cfm md md1 ma ma1 map vlan 10 mep mep-id 2 interface gigabitethernet 1/0/0 outward 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

l Configuration file of Router D# sysname RouterD# vlan batch 10#efm enable#interface GigabitEthernet1/0/0 portswitch port trunk allow-pass vlan 10 efm mode passive efm enable#interface GigabitEthernet2/0/0 portswitch port trunk allow-pass vlan 10#return




Issue 03 (2010-03-31)

7.16.7 Example for Configuring VPLS Ethernet CFM

Networking RequirementsAs shown in Figure 7-19, Martini VPLS runs on the backbone network and LDP is used assignaling to create Pseudo Wires (PWs). Configure VPLS Ethernet CFM on PEs to fast detectVPLS connectivity between PEs.

Figure 7-19 Diagram of configuring VPLS Ethernet CFM

Loopback13.3.3.3/32

Loopback11.1.1.1/32

Loopback12.2.2.2/32GE2/0/0

100.1.1.1/30GE2/0/0100.1.1.2/30

GE3/0/0100.2.1.1/30

GE2/0/0100.2.1.2/30

GE3/0/0100.3.1.1/30

GE3/0/0100.3.1.2/30

GE1/0/0.110.1.1.1/24

GE1/0/0.1

GE1/0/0.110.1.1.2/24

GE1/0/0.1

GE1/0/0.1

GE1/0/0.110.1.1.3/24

PE2PE1

PE3

CE1 CE2

CE3


1. Run the Interior Gateway Protocol (IGP) on the backbone network. routers across thebackbone network then can communicate.

2. Configure the routing protocols on the backbone network to enable communicationbetween 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.




7-95


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 theMEP resides, and type of the MEP

ProcedureStep 1 Assign an IP address to each interface.

# Configure PE1.

<HUAWEI> system-view[HUAWEI] sysname PE1[PE1] interface loopback 1[PE1-LoopBack1] ip address 1.1.1.1 32[PE1-LoopBack1] quit[PE1] interface gigabitethernet 2/0/0[PE1-GigabitEthernet2/0/0] ip address 100.1.1.1 30[PE1-GigabitEthernet2/0/0] undo shutdown[PE1-GigabitEthernet2/0/0] quit[PE1] interface gigabitethernet 3/0/0[PE1-GigabitEthernet3/0/0] ip address 100.2.1.1 30[PE1-GigabitEthernet3/0/0] undo shutdown[PE1-GigabitEthernet3/0/0] quit

# Configure PE2.

<HUAWEI> system-view[HUAWEI] sysname PE2[PE2] interface LoopBack 1[PE2-LoopBack1] ip address 2.2.2.2 32[PE2-LoopBack1] quit[PE2] interface gigabitethernet 2/0/0[PE2-GigabitEthernet2/0/0] ip address 100.1.1.2 30[PE2-GigabitEthernet2/0/0] undo shutdown[PE2-GigabitEthernet2/0/0] quit[PE2] interface gigabitethernet 3/0/0[PE2-GigabitEthernet3/0/0] ip address 100.3.1.1 30[PE2-GigabitEthernet3/0/0] undo shutdown[PE2-GigabitEthernet3/0/0] quit

# Configure PE3.

<HUAWEI> system-view[HUAWEI] sysname PE3[PE3] interface loopback 1[PE3-LoopBack1] ip address 3.3.3.3 32[PE3-LoopBack1] quit[PE3] interface gigabitethernet 2/0/0[PE3-GigabitEthernet2/0/0] ip address 100.2.1.2 30[PE3-GigabitEthernet2/0/0] undo shutdown[PE3-GigabitEthernet2/0/0] quit[PE3] interface gigabitethernet 3/0/0[PE3-GigabitEthernet3/0/0] ip address 100.3.1.2 30[PE3-GigabitEthernet3/0/0] undo shutdown[PE3-GigabitEthernet3/0/0] quit

Step 2 Configure the IGP on the MPLS backbone network. The Open Shortest Path First (OSPF) isused as the IGP protocol in this example.

NOTE

When configuring OSPF, advertise the 32-bit addresses of loopback interfaces on PEs.




Issue 03 (2010-03-31)

# 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] network 100.1.1.0 0.0.0.3[PE1-ospf-1-area-0.0.0.0] network 100.2.1.0 0.0.0.3[PE1-ospf-1-area-0.0.0.0] quit[PE1-ospf-1] quit

# Configure PE2.


# Configure PE3.


After the preceding configuration, PE1 and PE2, PE1 and PE3 can learn IP addresses ofloopback1 interfaces from each other through OSPF.

Take the display on PE1 as an example.

[PE1] display ip routing-tableRoute Flags: R - relied, D - download to fib------------------------------------------------------------------------------Routing Tables: Public Destinations : 12 Routes : 13Destination/Mask Proto Pre Cost Flags NextHop Interface 1.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 2.2.2.2/32 OSPF 10 2 D 100.1.1.2 GigabitEthernet2/0/0 3.3.3.3/32 OSPF 10 2 D 100.2.1.2 GigabitEthernet3/0/0 100.1.1.0/30 Direct 0 0 D 100.1.1.1 GigabitEthernet2/0/0 100.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 100.1.1.2/32 Direct 0 0 D 100.1.1.2 GigabitEthernet2/0/0 100.3.1.0/30 OSPF 10 2 D 100.1.1.2 GigabitEthernet2/0/0 OSPF 10 2 D 100.2.1.2 GigabitEthernet3/0/0 100.2.1.0/30 Direct 0 0 D 100.2.1.1 GigabitEthernet3/0/0 100.2.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 100.2.1.2/32 Direct 0 0 D 100.2.1.2 GigabitEthernet3/0/0 127.0.0.0/8 Direct 0 0 D 127.0.0.1 InLoopBack0 127.0.0.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0

Step 3 Enable basic MPLS functions and LDP on the MPLS backbone network.

# Configure PE1.

[PE1] mpls lsr-id 1.1.1.1[PE1] mpls[PE1-mpls] quit[PE1] mpls ldp[PE1-mpls-ldp] quit[PE1] interface gigabitethernet 2/0/0 [PE1-GigabitEthernet2/0/0] mpls[PE1-GigabitEthernet2/0/0] mpls ldp[PE1-GigabitEthernet2/0/0] quit[PE1] interface gigabitethernet 3/0/0



7-97

[PE1-GigabitEthernet3/0/0] mpls[PE1-GigabitEthernet3/0/0] mpls ldp[PE1-GigabitEthernet3/0/0] quit

# Configure PE2.

[PE2] mpls lsr-id 2.2.2.2[PE2] mpls[PE2-mpls] quit[PE2] mpls ldp[PE2-mpls-ldp] quit[PE2] interface gigabitethernet2/0/0[PE2-GigabitEthernet2/0/0] mpls[PE2-GigabitEthernet2/0/0] mpls ldp[PE2-GigabitEthernet2/0/0] quit[PE2] interface gigabitethernet3/0/0[PE2-GigabitEthernet3/0/0] mpls[PE2-GigabitEthernet3/0/0] mpls ldp[PE2-GigabitEthernet3/0/0] quit

# Configure PE3.

[PE3] mpls lsr-id 3.3.3.3[PE3] mpls[PE3-mpls] quit[PE3] mpls ldp[PE3-mpls-ldp] quit[PE3] interface gigabitethernet 2/0/0 [PE3-GigabitEthernet2/0/0] mpls[PE3-GigabitEthernet2/0/0] mpls ldp[PE3-GigabitEthernet2/0/0] quit[PE3] interface gigabitethernet 3/0/0[PE3-GigabitEthernet3/0/0] mpls[PE3-GigabitEthernet3/0/0] mpls ldp[PE3-GigabitEthernet3/0/0] quit

After the preceding configuration, LDP sessions are set up between PEs. Run the display mplsldp 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 3.3.3.3:0 Operational DU Passive 000:00:02 9/9 ------------------------------------------------------------------------------ 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-ipcommand to create remote LDP sessions between PEs.

Step 4 Enable MPLS L2VPN on PEs.

# Configure PE1.

[PE1] mpls l2vpn[PE1-l2vpn] quit

# Configure PE2.


# Configure PE3.




Issue 03 (2010-03-31)


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[PE1-vsi-ldp1-ldp] peer 3.3.3.3

# 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.

<HUAWEI> system-view[HUAWEI] sysname 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.

<HUAWEI> system-view[HUAWEI] sysname CE2[CE2] interface gigabitethernet 1/0/0.1



7-99

[CE2-GigabitEthernet1/0/0.1] vlan-type dot1q 10[CE2-GigabitEthernet1/0/0.1] ip address 10.1.1.2 24[CE2-GigabitEthernet1/0/0.1] undo shutdown[CE2-GigabitEthernet1/0/0.1] quit

# Configure CE3.

<HUAWEI> system-view[HUAWEI] sysname CE3[CE3] interface gigabitethernet 1/0/0.1[CE3-GigabitEthernet1/0/0.1] vlan-type dot1q 10[CE3-GigabitEthernet1/0/0.1] ip address 10.1.1.3 24[CE3-GigabitEthernet1/0/0.1] undo shutdown[CE3-GigabitEthernet1/0/0.1] quit

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 Tunnel ID : 0x6002000, Interface Name : GigabitEthernet1/0/0.1 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 Tunnel ID : 0x6002000, *Peer Ip Address : 3.3.3.3 PW State : up Local VC Label : 23552 Remote VC Label : 23552 PW Type : label Tunnel ID : 0x6002003,

Hosts attached to CE1, CE2, and CE3 can ping through each other.

Take CE1 as an example.

[CE1] ping 10.1.1.2 PING 10.1.1.2: 56 data bytes, press CTRL_C to break Reply from 10.1.1.2: bytes=56 Sequence=1 ttl=255 time=50 ms Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=255 time=1 ms Reply from 10.1.1.2: bytes=56 Sequence=3 ttl=255 time=1 ms Reply from 10.1.1.2: bytes=56 Sequence=4 ttl=255 time=1 ms Reply from 10.1.1.2: bytes=56 Sequence=5 ttl=255 time=1 ms --- 10.1.1.2 ping statistics ---




Issue 03 (2010-03-31)

5 packet(s) transmitted 5 packet(s) received 0.00% packet lossround-trip min/avg/max = 1/10/50 ms[CE1] ping 10.1.1.3 PING 10.1.1.3: 56 data bytes, press CTRL_C to break Reply from 10.1.1.3: bytes=56 Sequence=1 ttl=255 time=1 ms Reply from 10.1.1.3: bytes=56 Sequence=2 ttl=255 time=1 ms Reply from 10.1.1.3: bytes=56 Sequence=3 ttl=255 time=1 ms Reply from 10.1.1.3: bytes=56 Sequence=4 ttl=255 time=1 ms Reply from 10.1.1.3: bytes=56 Sequence=5 ttl=255 time=1 ms --- 10.1.1.3 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/1/1 ms

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 30[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] remote-mep mep-id 3[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.


# Configure PE3.



After the preceding configuration, run the display cfm mep command and the display cfmremote-mep command on PE1, PE2, and PE3. You can view that the configuration of EthernetCFM succeeds. Ethernet CFM can fast detect faults between PEs of VSIs and notify the NMS.

Take PE1 as an example.



7-101

[PE1] display cfm mep md md1The total number of MEPs is 2 MD Name : md1 Level : 0 MA Name : ma1 MEP ID : 2 Vlan ID : -- VSI Name : -- Interface Name : GigabitEthernet1/0/1.1 CCM Send : enabled Direction : inward MD Name : md1 Level : 0 MA Name : ma1 MEP ID : 3 Vlan ID : -- VSI Name : -- Interface Name : GigabitEthernet1/0/1.1 CCM Send : enabled Direction : inward[PE1] display cfm remote-mep md md1The total number of RMEPs is 2The status of RMEPS : 2 up, 0 down-------------------------------------------------- MD Name : md1 Level : 0 MA Name : ma1 RMEP ID : 2 Vlan ID : -- VSI Name : -- MAC : -- CCM Receive : enabled Trigger-If-Down : disabled CFM Status : up MD Name : md1 Level : 0 MA Name : ma1 RMEP ID : 3 Vlan ID : -- VSI Name : -- MAC : -- CCM Receive : enabled Trigger-If-Down : disabled CFM Status : up

----End


# 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#interface GigabitEthernet1/0/0




Issue 03 (2010-03-31)

undo shutdown#interface GigabitEthernet1/0/0.1 undo shutdown vlan-type dot1q 10 l2 binding vsi ldp1#interface GigabitEthernet2/0/0 undo shutdown ip address 100.1.1.1 255.255.255.252 mpls mpls ldp#interface GigabitEthernet3/0/0 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 30 map vsi ldp1 mep mep-id 1 interface gigabitethernet 1/0/0.1 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 remote-mep ccm-receive mep-id 3 enable#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

l Configuration file of PE2# 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#interface GigabitEthernet1/0/0 undo shutdown#interface GigabitEthernet1/0/0.1 undo shutdown vlan-type dot1q 10 l2 binding vsi ldp1#interface GigabitEthernet2/0/0 undo shutdown ip address 100.1.1.2 255.255.255.252



7-103

mpls mpls ldp#interface GigabitEthernet3/0/0 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 30 map vsi ldp1 mep mep-id 2 interface gigabitethernet 1/0/0.1 inward mep ccm-send mep-id 2 enable remote-mep mep-id 1 remote-mep ccm-receive mep-id 1 enable remote-mep mep-id 3 remote-mep ccm-receive mep-id 3 enable#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

l Configuration file of PE3# 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#interface GigabitEthernet1/0/0 undo shutdown#interface GigabitEthernet1/0/0.1 undo shutdown vlan-type dot1q 10 l2 binding vsi ldp1#interface GigabitEthernet2/0/0 undo shutdown ip address 100.2.1.2 255.255.255.252 mpls mpls ldp#interface GigabitEthernet3/0/0 undo shutdown ip address 100.3.1.2 255.255.255.252 mpls mpls ldp#interface LoopBack1




Issue 03 (2010-03-31)

ip address 3.3.3.3 255.255.255.255#cfm md md1 ma ma1 ccm-interval 30 map vsi ldp1 mep mep-id 3 interface gigabitethernet 1/0/0.1 inward mep ccm-send mep-id 3 enable remote-mep mep-id 1 remote-mep ccm-receive mep-id 1 enable remote-mep mep-id 2 remote-mep ccm-receive mep-id 2 enable#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

l Configuration file of CE1# sysname CE1#interface GigabitEthernet1/0/0 undo shutdown#interface GigabitEthernet1/0/0.1 undo shutdown vlan-type dot1q 10 ip address 10.1.1.1 255.255.255.0#return





7-105

7.16.8 Example for Associating EFM OAM with MPLS OAM

Networking RequirementsOn the provider network shown in Figure 7-20, NPEs and P are connected through Ethernetlinks; 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 UPE1and NPE1 to EFM OAM running between NPE2 and UPE2.

Figure 7-20 Diagram of associating EFM OAM with MPLS OAM

UPE1 UPE2NPE1 NPE2

P

Loopback11.1.1.1/32

Loopback12.2.2.2/32

Loopback13.3.3.3/32

Loopback14.4.4.4/32

GE 1/0/0100.1.1.1/30

GE 1/0/0100.1.1.2/30

GE 2/0/0100.2.1.1/30

GE 2/0/0100.2.1.2/30

GE 3/0/0100.3.1.1/30 GE 3/0/0

100.4.1.1/30

GE 1/0/0100.3.1.2/30 GE2/0/0

100.4.1.2/30

GE 1/0/0100.5.1.2/30

GE 1/0/0100.5.1.1/30

Loopback15.5.5.5/32


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.


l IP addresses of the interface on the routers, name of tunnel interfaces, and tunnel ID

l Type of the sent detection packets




Issue 03 (2010-03-31)

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 shownin Figure 7-20. 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 IGPprotocol 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-GigabitEthernet1/0/0] undo shutdown[NPE1-GigabitEthernet1/0/0] quit[NPE1] interface gigabitethernet 2/0/0[NPE1-GigabitEthernet2/0/0] isis enable 1[NPE1-GigabitEthernet2/0/0] undo shutdown[NPE1-GigabitEthernet2/0/0] quit[NPE1] interface gigabitethernet 3/0/0[NPE1-GigabitEthernet3/0/0] isis enable 1[NPE1-GigabitEthernet3/0/0] undo shutdown[NPE1-GigabitEthernet3/0/0] quit[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] interface gigabitethernet 1/0/0[P-GigabitEthernet1/0/0] isis enable 1[P-GigabitEthernet1/0/0] undo shutdown[P-GigabitEthernet1/0/0] quit[P] interface gigabitethernet 2/0/0[P-GigabitEthernet2/0/0] isis enable 1[P-GigabitEthernet2/0/0] undo shutdown[P-GigabitEthernet2/0/0] quit[P] interface loopback 1[P-LoopBack1] isis enable 1[P-LoopBack1] quit

# Configure NPE2.



7-107

[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 gigabitethernet 1/0/0[NPE2-GigabitEthernet1/0/0] isis enable 1[NPE2-GigabitEthernet1/0/0] undo shutdown[NPE2-GigabitEthernet1/0/0] quit[NPE2] interface gigabitethernet 2/0/0[NPE2-GigabitEthernet2/0/0] isis enable 1[NPE2-GigabitEthernet2/0/0] undo shutdown[NPE2-GigabitEthernet2/0/0] quit[NPE2] interface gigabitethernet 3/0/0[NPE2-GigabitEthernet3/0/0] isis enable 1[NPE2-GigabitEthernet3/0/0] undo shutdown[NPE2-GigabitEthernet3/0/0] 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] interface gigabitethernet 1/0/0[UPE2-GigabitEthernet1/0/0] isis enable 1[UPE2-GigabitEthernet1/0/0] undo shutdown[UPE2-GigabitEthernet1/0/0] quit[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 anexample.

[UPE1] display ip routing-tableRoute Flags: R - relied, D - download to fib------------------------------------------------------------------------------Routing Tables: Public Destinations : 10 Routes : 10Destination/Mask Proto Pre Cost Flags NextHop Interface 1.1.1.9/32 Direct 0 0 D 127.0.0.1 InLoopBack0 2.2.2.9/32 ISIS 15 10 D 100.1.1.2 GigabitEthernet1/0/0 3.3.3.9/32 ISIS 15 20 D 100.1.1.2 GigabitEthernet1/0/0 4.4.4.9/32 ISIS 15 20 D 100.1.1.2 GigabitEthernet1/0/0 5.5.5.9/32 ISIS 15 30 D 100.1.1.2 GigabitEthernet1/0/0 100.1.1.0/24 Direct 0 0 D 100.1.1.1 GigabitEthernet1/0/0 100.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 100.2.1.0/24 ISIS 15 20 D 100.1.1.2 GigabitEthernet1/0/0 100.3.1.0/24 ISIS 15 20 D 100.1.1.2 GigabitEthernet1/0/0 100.4.1.0/24 ISIS 15 30 D 100.1.1.2 GigabitEthernet1/0/0 100.5.1.0/24 ISIS 15 30 D 100.1.1.2 GigabitEthernet1/0/0 127.0.0.0/8 Direct 0 0 D 127.0.0.1 InLoopBack0 127.0.0.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0

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




Issue 03 (2010-03-31)

[NPE1] interface gigabitethernet 2/0/0[NPE1-GigabitEthernet2/0/0] mpls[NPE1-GigabitEthernet2/0/0] mpls te[NPE1-GigabitEthernet2/0/0] mpls rsvp-te[NPE1-GigabitEthernet2/0/0] quit[NPE1] interface gigabitethernet 3/0/0[NPE1-GigabitEthernet3/0/0] mpls[NPE1-GigabitEthernet3/0/0] mpls te[NPE1-GigabitEthernet3/0/0] mpls rsvp-te[NPE1-GigabitEthernet3/0/0] quit

# 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] interface gigabitethernet 1/0/0[P-GigabitEthernet1/0/0] mpls[P-GigabitEthernet1/0/0] mpls te[P-GigabitEthernet1/0/0] mpls rsvp-te[P-GigabitEthernet1/0/0] quit[P] interface gigabitethernet 2/0/0[P-GigabitEthernet2/0/0] mpls[P-GigabitEthernet2/0/0] mpls te[P-GigabitEthernet2/0/0] mpls rsvp-te[P-GigabitEthernet2/0/0] quit

# 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[NPE2] interface gigabitethernet 2/0/0[NPE2-GigabitEthernet2/0/0] mpls[NPE2-GigabitEthernet2/0/0] mpls te[NPE2-GigabitEthernet2/0/0] mpls rsvp-te[NPE2-GigabitEthernet2/0/0] quit[NPE2] interface gigabitethernet 3/0/0[NPE2-GigabitEthernet3/0/0] mpls[NPE2-GigabitEthernet3/0/0] mpls te[NPE2-GigabitEthernet3/0/0] mpls rsvp-te[NPE2-GigabitEthernet3/0/0] 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



7-109

[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 tunnelTunnel2/0/0 current state : UPLine protocol current state : UPDescription : Tunnel2/0/0 InterfaceThe Maximum Transmit Unit is 1500 bytesInternet Address is unnumbered, using address of LoopBack1(2.2.2.2/32)Encapsulation is TUNNEL, loopback not setTunnel destination 3.3.3.3Tunnel protocol/transport MPLS/MPLS, ILM is available,primary tunnel id is 0x1002001, secondary tunnel id is 0x0The 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




Issue 03 (2010-03-31)

After the preceding configuration, you can use the command to view the parameters and statusof MPLS OAM on the ingress NPE1 and egress NPE2. The command output shows that theingress 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 : 256Lsp signal status : Up Oam select board : 1Lsp establish type : Rsvp lsp Enable-state : --Lsp incoming Label : 3 Auto-protocol : EnableLsp ingress lsr-id : 2.2.2.2 Auto-overtime (s) : 300Lsp tnl-id/lsp-id : 100/1 Ttsi/lsr-id : 2.2.2.2Lsp Incoming-int GigabitEthernet2/0/0 Ttsi/tunnel-id : 100oam detect information: oam backward information:------------------------------------ ----------------------------------Type : FFD Tunnel name : Tunnel2/0/0Frequency : 100 ms Share attribute : PrivateDetect-state : Start Lsp signal status : UpDefect-state : Non-defect Bdi-frequency : Detect-freqAvailable state : AvailableUnavailable time (s): 0-------------------------------------------------------------------------Total Oam Num: 1Total Start Oam Num: 1Total Defect Oam Num: 0Total Unavaliable Oam Num: 0

Step 7 Configure EFM OAM on UPEs and NPEs.

# Configure UPE1.

[UPE1] efm enable[UPE1] interface gigabitethernet 1/0/0[UPE1-GigabitEthernet1/0/0] efm enable[UPE1-GigabitEthernet1/0/0] quit

# Configure NPE1.

[NPE1] efm enable[NPE1] interface gigabitethernet 1/0/0[NPE1-GigabitEthernet1/0/0] efm enable[NPE1-GigabitEthernet1/0/0] quit

# Configure UPE2.

[UPE2] efm enable[UPE2] interface gigabitethernet 1/0/0[UPE2-GigabitEthernet1/0/0] efm enable[UPE2-GigabitEthernet1/0/0] quit

# Configure NPE2.

[NPE2] efm enable[NPE2] interface gigabitethernet 1/0/0[NPE2-GigabitEthernet1/0/0] efm enable[NPE2-GigabitEthernet1/0/0] quit

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 asan example.

[UPE2] display efm session interface gigabitethernet 1/0/0



7-111

Interface EFM State Loopback Timeout -------------------------------------------------------------------- GigabitEthernet1/0/0 detect --

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 interface gigabitethernet 1/0/0

NOTE

When you create static LSPs, MPLS OAM instances created accordingly record LSR ID and tunnel IDonly, if lsr-id and tunnel-id are specified. In this manner, you must specify lsr-id and tunnel-id whenassociating Ethernet OAM with MPLS OAM.


After the preceding configuration, when EFM OAM running between UPE1 and NPE1 detectsfaults, the faults can be sent to EFM OAM running between UPE2 and NPE2 through MPLSOAM.

----End

Configuration Filesl Configuration file of UPE1

# sysname UPE1#efm enable#isis 1 is-level level-2 network-entity 00.0005.0000.0000.0001.00#interface GigabitEthernet1/0/0 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

l Configuration file of NPE1# sysname NPE1#efm enable#mpls lsr-id 2.2.2.2 mpls mpls te mpls rsvp-te mpls oam




Issue 03 (2010-03-31)

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#interface GigabitEthernet1/0/0 undo shutdown ip address 100.1.1.2 255.255.255.252 isis enable 1 efm enable#interface GigabitEthernet2/0/0 undo shutdown ip address 100.2.1.2 255.255.255.252 isis enable 1 mpls mpls te mpls rsvp-te#interface GigabitEthernet3/0/0 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 ip address unnumbered interface LoopBack1 tunnel-protocol mpls te 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#interface GigabitEthernet1/0/0



7-113

undo shutdown ip address 100.3.1.2 255.255.255.252 isis enable 1 mpls mpls te mpls rsvp-te#interface GigabitEthernet2/0/0 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

l Configuration file of NPE2# 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#interface GigabitEthernet1/0/0 undo shutdown ip address 100.5.1.1 255.255.255.252 isis enable 1 efm enable#interface GigabitEthernet2/0/0 undo shutdown ip address 100.2.1.2 255.255.255.252 isis enable 1 mpls mpls te mpls rsvp-te#interface GigabitEthernet3/0/0 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#interface Tunnel3/0/0




Issue 03 (2010-03-31)

ip address unnumbered interface LoopBack1 tunnel-protocol mpls te destination 2.2.2.2 mpls te tunnel-id 200 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#interface GigabitEthernet1/0/0 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

7.16.9 Example for Configuring EFM OAM Extension for VRRP

Networking RequirementsAs shown in Figure 7-21.



7-115

Figure 7-21 Networking diagram of configuring EFM OAM extension for VRRP

CE1(SoftX)

PE1

PE2MPLS

backbone

VPNA

GE1/0/0Vlanif10:

10.1.1.1/24

GE3/0/0

GE2/0/0Vlanif10:

10.1.1.1/24

GE3/0/0

GE2/0/0100.3.1.1/24

GE2/0/0100.3.1.2/24

POS1/0/0100.1.1.1/24

POS1/0/0

100.2.1.1/24

POS1/0/0100.1.1.2/24

POS2/0/0

100.2.1.2/24

Loopback11.1.1.1/32

Loopback12.2.2.2/32

Loopback13.3.3.3/32

Loopback14.4.4.4/32

PE3

AS:100

Vlanif1010.1.1.2/24

10.1.1.3/24

EFM OAM Extension

VRRPVlanif10

Loopback14.4.4.4/32

EFM OAM Extension

The master interface board of CE1 is connected to the master router, and the slave interfaceboard of CE1 is connected to the backup router. The interfaces on the master interface boardand slave interface board that are connected to PE1 and PE2 are configured with the same IPaddress.

Normally, the IP address of the interface on the master interface board is valid. The SoftX isdual 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, aVLAN. Then the downstream interfaces (configured as a Layer 2 interfaces) of the two PEs areadded into the VLAN. Based on EFM OAM extension, the SoftX can detect the faults on thelinks connecting the SoftX to PE1 and PE2.


1. Configure Intermediate System to Intermediate System (IS-IS) between PEs to implementinterworking 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.




Issue 03 (2010-03-31)


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 backuprouters

ProcedureStep 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] interface gigabitethernet 2/0/0[PE1-GigabitEthernet2/0/0] portswitch[PE1-GigabitEthernet2/0/0] quit[PE1] interface gigabitethernet 3/0/0[PE1-GigabitEthernet3/0/0] portswitch[PE1-GigabitEthernet3/0/0] quit[PE1-vlan10] port gigabitethernet 2/0/0[PE1-vlan10] port gigabitethernet 3/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] interface gigabitethernet 2/0/0[PE2-GigabitEthernet2/0/0] portswitch[PE2-GigabitEthernet2/0/0] quit[PE2] interface gigabitethernet 3/0/0[PE2-GigabitEthernet3/0/0] portswitch[PE2-GigabitEthernet3/0/0] quit[PE2-vlan10] port gigabitethernet 2/0/0[PE2-vlan10] port gigabitethernet 3/0/0[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] interface gigabitethernet 2/0/0[CE1-GigabitEthernet2/0/0] portswitch[CE1-GigabitEthernet2/0/0] quit[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 thebackbone network.

# Configure PE1.

[PE1] interface loopback 1



7-117

[PE1-LoopBack1] ip address 2.2.2.2 32[PE1-LoopBack1] quit[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] network-entity 10.0000.0000.0001.00[PE1-isis-1] quit

# Configure PE2.

[PE2] interface loopback 1[PE2-LoopBack1] ip address 3.3.3.3 32[PE2-LoopBack1] quit[PE2] interface pos 1/0/0[PE2-Pos1/0/0] ip address 100.2.1.1 24[PE2-Pos1/0/0] isis enable[PE2-Pos1/0/0] quit[PE2] isis 1[PE2-isis-1] is-level level-1-2[PE2-isis-1] network-entity 10.0000.0000.0002.00[PE2-isis-1] quit

# Configure PE3.

[PE3] interface loopback 1[PE3-LoopBack1] ip address 4.4.4.4 32[PE3-LoopBack1] quit[PE3] interface pos 1/0/0[PE3-Pos1/0/0] ip address 100.1.1.2 24[PE3-Pos1/0/0] isis enable[PE3-Pos1/0/0] quit[PE3] interface pos 2/0/0[PE3-Pos2/0/0] ip address 100.2.1.2 24[PE3-Pos2/0/0] isis enable[PE3-Pos2/0/0] quit[PE3] isis 1[PE3-isis-1] is-level level-1-2[PE3-isis-1] network-entity 10.0000.0000.0003.00[PE3-isis-1] quit

Step 3 Configure basic MPLS functions and MPLS Label Distribution Protocol (LDP) on the MPLSbackbone network and set up LDP LSPs.

# Configure PE1.

[PE1] mpls lsr-id 2.2.2.2[PE1] mpls[PE1-mpls] quit[PE1] mpls ldp[PE1-ldp] quit[PE1] interface pos 1/0/0[PE1-Pos1/0/0] mpls[PE1-Pos1/0/0] mpls ldp[PE1-Pos1/0/0] quit

# Configure PE2.

[PE2] mpls lsr-id 3.3.3.3[PE2] mpls[PE2-mpls] quit[PE2] mpls ldp[PE2-ldp] quit[PE2] interface pos 1/0/0[PE2-Pos1/0/0] mpls[PE2-Pos1/0/0] mpls ldp[PE2-Pos1/0/0] quit




Issue 03 (2010-03-31)

# Configure PE3.

[PE3] mpls lsr-id 4.4.4.4[PE3] mpls[PE3-mpls] quit[PE3] mpls ldp[PE3-ldp] quit[PE3] interface pos 1/0/0[PE3-Pos1/0/0] mpls[PE3-Pos1/0/0] mpls ldp[PE3-Pos1/0/0] quit[PE3] interface pos 2/0/0[PE3-Pos2/0/0] mpls[PE3-Pos2/0/0] mpls ldp[PE3-Pos2/0/0] quit

After the preceding configuration, LDP sessions are set up between PEs. Run the display mplsldp 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] ip vpn-instance vpna[PE2-vpn-instance-vpna] route-distinguisher 100:2[PE2-vpn-instance-vpna] vpn-target 111:1 both[PE2-vpn-instance-vpna] quit[PE2] interface vlanif 10[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] interface gigabitethernet 3/0/0[PE1-GigabitEthernet3/0/0] efm enable[PE1-GigabitEthernet3/0/0] efm trigger if-down[PE1-GigabitEthernet3/0/0] quit

# Configure PE2.

[PE2] efm enable[PE2] interface gigabitethernet 3/0/0[PE2-GigabitEthernet3/0/0] efm enable[PE2-GigabitEthernet3/0/0] efm trigger if-down[PE2-GigabitEthernet3/0/0] quit

Step 6 Configure the static routes on PE1 and PE2 that are destined for CE1, and import the static routesto 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



7-119

[PE1-bgp-vpna] import-route direct[PE1-bgp-vpna] import-route static[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.1.1.1[PE2] bgp 100[PE2-bgp] ipv4-family vpn-instance vpna[PE2-bgp-vpna] import-route direct[PE2-bgp-vpna] import-route static[PE2-bgp-vpna] quit

# Configure CE1. Configure the virtual IP address of the VRRP backup group as the gatewayaddress.

[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] peer 4.4.4.4 as-number 100[PE1-bgp] peer 4.4.4.4 connect-interface loopback 1[PE1-bgp] ipv4-family vpnv4[PE1-bgp] peer 3.3.3.3 enable[PE1-bgp] peer 4.4.4.4 enable[PE1-bgp] quit

# Configure PE2.


# Configure PE3.


Step 8 Configure the VRRP backup group on PE1 and PE2 to track the traffic of the downstreaminterface.

# Configure PE1.

[PE1] interface vlanif 10[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




Issue 03 (2010-03-31)

# Configure PE2.

[PE1] interface vlanif 10[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 thebackup interface. The command output shows that the protocol status of the backup interface isDOWN (EFM down). That is, the backup interface is blocked, and cannot forward traffic.

[PE2] display interface GigabitEthernet 3/0/0GigabitEthernet3/0/0 current state : UPLine protocol current state : DOWN (EFM down)Description: GigabitEthernet3/0/0 InterfaceSwitch Port,PVID : 10,The Maximum Transmit Unit is 1500Internet protocol processing : disabledIP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-0003-0003The Vendor Name is AGILENT , The Vendor PN is HFCT-5710LTransceiver BW: 1G, Transceiver Mode: Single ModeWaveLength: 1310nm, Transmission Distance: 10kmLoopback:none, full-duplex mode, negotiation: disable, Pause Flowcontrol:Receive Enable and Send Enable

Last physical up time : 2008-12-27 19:40:57Last physical down time : 2008-12-27 19:40:56Statistics last cleared:2008-12-2717: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: Unicast: 6176 packets, Multicast: 9627 packets 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: Unicast: 21 packets, Multicast: 9144 packets 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 ofPE2 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 Vlanif10 | Virtual Router 1 State : Master Virtual IP : 10.1.1.111 PriorityRun : 40 PriorityConfig : 100 MasterPriority : 100 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0101 Check TTL : YES



7-121

Config type : normal-vrrp Track IF : GigabitEthernet3/0/0 priority reduced : 60 IF State : Up[PE2] display vrrp Vlanif10 | Virtual Router 1 State : Backup Virtual IP : 10.1.1.111 PriorityRun : 40 PriorityConfig : 100 MasterPriority : 100 Preempt : YES Delay Time : 0 TimerRun : 1 TimerConfig : 1 Auth Type : NONE Virtual Mac : 0000-5e00-0101 Check TTL : YES Config type : normal-vrrp Track IF : GigabitEthernet3/0/0 priority reduced : 60 IF State : DOWN

----End


# sysname PE1# vlan 10#ip vpn-instance vpna route-distinguisher 100:1 vpn-target 111:1 export-extcommunity vpn-target 111:1 import-extcommunity# 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 virtual-ip 10.1.1.111 vrrp vrid 1 track interface GigabitEthernet3/0/0 reduced 60 ip binding vpn-instance vpna #interface Pos1/0/0 link-protocol ppp ip address 100.1.1.1 255.255.255.0 mpls mpls ldp#interface GigabitEthernet2/0/0 undo shutdown portswitch port default vlan 10 #interface GigabitEthernet3/0/0 undo shutdown portswitch port default vlan 10 #interface LoopBack1 ip address 2.2.2.2 255.255.255.255#




Issue 03 (2010-03-31)

bgp 100 peer 4.4.4.4 as-number 100 peer 4.4.4.4 connect-interface LoopBack1 peer 3.3.3.3 as-number 100 peer 3.3.3.3 connect-interface LoopBack1 # ipv4-family unicast undo synchronization 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 # ipv4-family vpn-instance vpna import-route directimport-route static# ip route-static vpn-instance vpna 1.1.1.1 255.255.255.255 10.1.1.1#return

l Configuration file of PE2# sysname PE2# vlan 10#ip vpn-instance vpna route-distinguisher 100:1 vpn-target 111:1 export-extcommunity vpn-target 111:1 import-extcommunity# 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 virtual-ip 10.1.1.111 vrrp vrid 1 track interface GigabitEthernet3/0/0 reduced 60 ip binding vpn-instance vpna #interface Pos1/0/0 link-protocol ppp ip address 100.1.1.1 255.255.255.0 mpls mpls ldp#interface GigabitEthernet2/0/0 undo shutdown portswitch port default vlan 10 #interface GigabitEthernet3/0/0 undo shutdown portswitch port default vlan 10 #interface LoopBack1 ip address 3.3.3.3 255.255.255.255#bgp 100 peer 4.4.4.4 as-number 100



7-123

peer 4.4.4.4 connect-interface LoopBack1 peer 2.2.2.2 as-number 100 peer 2.2.2.2 connect-interface LoopBack1 # ipv4-family unicast undo synchronization 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 # ipv4-family vpn-instance vpna 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

l Configuration file of PE3# 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 peer 2.2.2.2 as-number 100 peer 2.2.2.2 connect-interface LoopBack1 peer 3.3.3.3 as-number 100 peer 3.3.3.3 connect-interface LoopBack1 # 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

l Configuration file of CE1# sysname CE1#




Issue 03 (2010-03-31)

efm enable#interface GigabitEthernet1/0/0 undo shutdown portswitch port default vlan 10 #interface GigabitEthernet2/0/0 undo shutdown portswitch port default vlan 10#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

7.16.10 Exmaple for Configuring EFM OAM Extension for StaticRoutes


Figure 7-22 shows the networking requirements:

Figure 7-22 Networking diagram of configuring EFM OAM extension for static routes

CE1(SoftX)

PE1

PE2MPLS

backbone

VPNA

GE1/0/010.1.1.1/24

GE3/0/0

GE2/0/010.1.1.1/24

GE3/0/0

GE2/0/0100.3.1.1/24

GE2/0/0100.3.1.2/24

POS1/0/0100.1.1.1/24

POS1/0/0

100.2.1.1/24

POS1/0/0100.1.1.2/24

POS2/0/0

100.2.1.2/24

Loopback11.1.1.1/32

Loopback12.2.2.2/32

Loopback13.3.3.3/32

PE3

AS:100

10.1.1.2/24

10.1.1.2/24

EFM OAM Extension

Loopback14.4.4.4/32

EFM OAM Extension

The master interface board of CE1 (SoftX) is connected to the master router, and the slaveinterface board of CE1 is connected to the backup router. The interfaces on the master interfaceboard and slave interface board that are connected to PE1 and PE2 are configured with the sameIP address.

Normally, the IP address of the interface on the master interface board is valid. The SoftX isdual homed to the gateways, that is, PE1 and PE2.



7-125

On PE1 and PE2, static routes destined for CE1 are configured, and EFM OAM extension forstatic 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.


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 thebackbone network.

# Configure PE1.

[PE1] interface loopback 1[PE1-LoopBack1] ip address 2.2.2.2 32[PE1-LoopBack1] quit[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] interface pos 20/0[PE1-Pos2//0] ip address 100.3.1.1 24[PE1-Pos2/0/0] isis enable[PE1-Pos20/0] quit[PE1] isis 1[PE1-isis-1] is-level level-1-2[PE1-isis-1] network-entity 10.0000.0000.0001.00[PE1-isis-1] quit

# Configure PE2.

[PE2] interface loopback 1[PE2-LoopBack1] ip address 3.3.3.3 32[PE2-LoopBack1] quit[PE2] interface pos 1/0/0[PE2-Pos1/0/0] ip address 100.2.1.1 24[PE2-Pos1/0/0] isis enable[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] isis enable




Issue 03 (2010-03-31)

[PE2-Pos2/0/0] quit[PE2] isis 1[PE2-isis-1] is-level level-1-2[PE2-isis-1] network-entity 10.0000.0000.0002.00[PE2-isis-1] quit

# Configure PE3.

[PE3] interface loopback 1[PE3-LoopBack1] ip address 4.4.4.4 32[PE3-LoopBack1] quit[PE3] interface pos 1/0/0[PE3-Pos1/0/0] ip address 100.1.1.2 24[PE3-Pos1/0/0] isis enable[PE3-Pos1/0/0] quit[PE3] interface pos 2/0/0[PE3-Pos2/0/0] ip address 100.2.1.2 24[PE3-Pos2/0/0] isis enable[PE3-Pos2/0/0] quit[PE3] isis 1[PE3-isis-1] is-level level-1-2[PE3-isis-1] network-entity 10.0000.0000.0003.00[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 theLoopback1 route from each other.


[PE1] display ip routing-tableRoute Flags: R - relay, D - download to fib------------------------------------------------------------------------------Routing Tables: Public Destinations : 29 Routes : 30

Destination/Mask Proto Pre Cost Flags NextHop Interface

1.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 3.3.3.3/32 ISIS 15 10 D 100.3.1.2 GigabitEthernet2/0/0 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 GigabitEthernet3/0/0 10.1.1.2/32 Direct 0 0 D 127.0.0.1 InLoopBack0 10.1.1.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0 127.0.0.0/8 Direct 0 0 D 127.0.0.1 InLoopBack0 127.0.0.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0127.255.255.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0 100.1.1.0/24 Direct 0 0 D 100.1.1.1 POS1/0/0 100.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 100.1.1.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0 100.2.1.0/24 ISIS 15 20 D 100.3.1.2 GigabitEthernet2/0/0 ISIS 15 20 D 100.1.1.2 POS1/0/0 100.3.1.0/24 Direct 0 0 D 100.3.1.1 GigabitEthernet2/0/0 100.3.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 100.3.1.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0255.255.255.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0

Step 2 Configure basic MPLS functions and MPLS LDP on the MPLS backbone network and set upLDP LSPs.

# Configure PE1.

[PE1] mpls lsr-id 2.2.2.2[PE1] mpls[PE1-mpls] quit



7-127

[PE1] mpls ldp[PE1-ldp] quit[PE1] interface pos 1/0/0[PE1-Pos1/0/0] mpls[PE1-Pos1/0/0] mpls ldp[PE1-Pos1/0/0] quit[PE1] interface pos 2/0/0[PE1-Pos2/0/0] mpls[PE1-Pos2/0/0] mpls ldp[PE1-Pos2/0/0] quit

# Configure PE2.


# Configure PE3.


After the preceding configuration, LDP sessions are set up between PEs. Run the display mplsldp session command. The command output shows that the LDP session status isOperational.


[PE1] display mpls ldp session

LDP Session(s) in Public Network ------------------------------------------------------------------------------ Peer-ID Status LAM SsnRole SsnAge KA-Sent/Rcv ------------------------------------------------------------------------------ 3.3.3.3:0 Operational DU Passive 000:02:22 572/572 4.4.4.4:0 Operational DU Passive 000:02:21 566/566 ------------------------------------------------------------------------------ TOTAL: 2 session(s) Found. 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] 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




Issue 03 (2010-03-31)

[PE1] interface gigabitethernet 3/0/0[PE1-GigabitEthernet3/0/0] ip binding vpn-instance vpna[PE1-GigabitEthernet3/0/0] ip address 10.1.1.2 24[PE1-GigabitEthernet3/0/0] quit

# Configure PE2.

[PE2] ip vpn-instance vpna[PE2-vpn-instance-vpna] route-distinguisher 100:2[PE2-vpn-instance-vpna] vpn-target 111:1 both[PE2-vpn-instance-vpna] quit[PE2] interface gigabitethernet 3/0/0[PE2-GigabitEthernet3/0/0] ip binding vpn-instance vpna[PE2-GigabitEthernet3/0/0] ip address 10.1.1.2 24[PE2-GigabitEthernet3/0/0] quit

# Configure CE1. Note that the IP addresses of the interfaces on the master and slave interfaceboards are the same.

[CE1] interface gigabitethernet 1/0/0[CE1-GigabitEthernet1/0/0] ip address 10.1.1.1 24[CE1-GigabitEthernet1/0/0] quit[CE1] interface gigabitethernet 2/0/0[CE1-GigabitEthernet2/0/0] ip address 10.1.1.1 24[CE1-GigabitEthernet2/0/0] quit

After the configuration, run the display ip vpn-instance verbose command on PEs. Thecommand output shows the configurations of VPN instances. In addition, you can find that PE1and 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.1PING 10.1.1.1: 56 data bytes, press CTRL_C to break Reply from 10.1.1.1: bytes=56 Sequence=1 ttl=255 time=5 ms Reply from 10.1.1.1: bytes=56 Sequence=2 ttl=255 time=2 ms Reply from 10.1.1.1: bytes=56 Sequence=3 ttl=255 time=2 ms Reply from 10.1.1.1: bytes=56 Sequence=4 ttl=255 time=2 ms Reply from 10.1.1.1: bytes=56 Sequence=5 ttl=255 time=2 ms


Step 4 Enable EFM OAM extension between PE1 and CE1, and between PE2 and CE1.

# Configure PE1.

[PE1] efm enable[PE1] interface gigabitethernet 3/0/0[PE1-GigabitEthernet3/0/0] efm enable[PE1-GigabitEthernet3/0/0] quit

# Configure PE2.



7-129

[PE2] efm enable[PE2] interface gigabitethernet 3/0/0[PE2-GigabitEthernet3/0/0] efm enable[PE2-GigabitEthernet3/0/0] quit

# Configure CE1.

[CE1] efm enable[CE1] interface gigabitethernet 1/0/0[PE2-GigabitEthernet1/0/0] efm enable[PE2-GigabitEthernet1/0/0] quitinterface gigabitethernet 2/0/0[PE2-GigabitEthernet2/0/0] efm enable[PE2-GigabitEthernet2/0/0] quit

Step 5 Configure the static routes on PE1 and PE2 that are destined for CE1. Then configure EFMOAM 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] ipv4-family vpn-instance vpna[PE1-bgp-vpna] import-route direct[PE1-bgp-vpna] import-route static[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] ipv4-family vpn-instance vpna[PE2-bgp-vpna] import-route direct[PE2-bgp-vpna] import-route static[PE2-bgp-vpna] quit

Step 6 Set up MP-IBGP peer relationships between PE1, PE2, and PE3.

# Configure PE1.


# Configure PE2.


# Configure PE3.




Issue 03 (2010-03-31)


After the configuration, run the display bgp peer command on the PEs. The command outputshows that peer relationships are set up between the PEs and the status of the peer relationshipsis 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 03.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 outputshows that the static route exists in the routing table of each PE.

[PE2] display ip routing-table vpn-instance vpnaRoute Flags: R - relay, D - download to fib------------------------------------------------------------------------------Routing Tables: vpna Destinations : 8 Routes : 8


1.1.1.1/32 Static 60 0 RD 10.1.1.1 GigabitEthernet3/0/0 10.1.1.0/24 Direct 0 0 D 10.1.1.2 GigabitEthernet3/0/0 10.1.1.2/32 Direct 0 0 D 127.0.0.1 InLoopBack0 10.1.1.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0 10.2.1.0/24 BGP 255 0 RD 3.3.3.9 GigabitEthernet2/0/0 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/0255.255.255.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0



1.1.1.1/32 BGP 255 0 RD 1.1.1.1 GigabitEthernet3/0/0 10.1.1.0/24 BGP 255 0 RD 1.1.1.1 GigabitEthernet2/0/0 10.2.1.0/24 Direct 0 0 D 10.2.1.2 GigabitEthernet3/0/0 10.2.1.2/32 Direct 0 0 D 127.0.0.1 InLoopBack0 10.2.1.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0 10.3.1.0/24 BGP 255 0 RD 4.4.4.4 POS1/0/0



7-131

10.3.1.2/32 BGP 255 0 RD 4.4.4.4 POS1/0/0255.255.255.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0

If the master/slave failover occurs on the interface boards of CE1, the gateway of CE1 alsochanges from PE1 to PE2. The routing information is displayed as follows:



1.1.1.1/32 BGP 255 0 RD 3.3.3.9 GigabitEthernet3/0/0 10.1.1.0/24 Direct 0 0 D 10.1.1.2 GigabitEthernet3/0/0 10.1.1.2/32 Direct 0 0 D 127.0.0.1 InLoopBack0 10.1.1.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0 10.2.1.0/24 BGP 255 0 RD 3.3.3.9 GigabitEthernet2/0/0 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/0255.255.255.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0[PE2] display ip routing-table vpn-instance vpnaRoute Flags: R - relay, D - download to fib------------------------------------------------------------------------------Routing Tables: vpna Destinations : 8 Routes : 8


1.1.1.1/32 Static 60 0 RD 10.2.1.1 GigabitEthernet3/0/0 10.1.1.0/24 BGP 255 0 RD 1.1.1.1 GigabitEthernet2/0/0 10.2.1.0/24 Direct 0 0 D 10.2.1.2 GigabitEthernet3/0/0 10.2.1.2/32 Direct 0 0 D 127.0.0.1 InLoopBack0 10.2.1.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0 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/0255.255.255.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0

----End


# sysname PE1# efm enable#ip vpn-instance vpna route-distinguisher 100:1 vpn-target 111:1 export-extcommunity vpn-target 111:1 import-extcommunity# mpls lsr-id 2.2.2.2 mpls#mpls ldp#isis 1 network-entity 10.0000.0000.0001.00#




Issue 03 (2010-03-31)

interface GigabitEthernet3/0/0 ip binding vpn-instance vpna 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 peer 4.4.4.4 as-number 100 peer 4.4.4.4 connect-interface LoopBack1 peer 3.3.3.3 as-number 100 peer 3.3.3.3 connect-interface LoopBack1 # ipv4-family unicast undo synchronization 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 # ipv4-family vpn-instance vpna 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

l Configuration file of PE2# sysname PE2# efm enable#ip vpn-instance vpna route-distinguisher 100:2 vpn-target 111:1 export-extcommunity vpn-target 111:1 import-extcommunity# mpls lsr-id 3.3.3.3 mpls#mpls ldp#isis 1 network-entity 10.0000.0000.0002.00#interface GigabitEthernet3/0/0 ip binding vpn-instance vpna ip address 10.2.1.2 255.255.255.0 efm enable#interface Pos1/0/0



7-133

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 peer 4.4.4.4 as-number 100 peer 4.4.4.4 connect-interface LoopBack1 peer 2.2.2.2 as-number 100 peer 2.2.2.2 connect-interface LoopBack1 # ipv4-family unicast undo synchronization 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 # ipv4-family vpn-instance vpna 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

l Configuration file of PE3# 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 peer 2.2.2.2 as-number 100 peer 2.2.2.2 connect-interface LoopBack1 peer 3.3.3.3 as-number 100




Issue 03 (2010-03-31)

peer 3.3.3.3 connect-interface LoopBack1 # 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

l Configuration file of CE1# sysname CE1# efm enable#interface GigabitEthernet1/0/0 ip address 10.1.1.1 255.255.255.0 efm enable#interface GigabitEthernet2/0/0 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



7-135

8 Configuring ISSU

About This Chapter

This section describes the concepts, working mechanism, configuration procedures, andmaintenance commands of ISSU, and provides configuration examples.

8.1 IntroductionThis section describes the concept, modes, and system requirements of ISSU.

8.2 Implementing ISSUThis section describes how to implement ISSU.

8.3 Maintaining ISSUThis section describes how to monitor ISSU.

8.4 Configuration ExamplesThis section describes examples for configuring ISSU.

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability 8 Configuring ISSU


8-1

8.1 IntroductionThis section describes the concept, modes, and system requirements of ISSU.

8.1.1 Introduction to ISSU

8.1.2 ISSU Supported by the NE80E/40E

8.1.1 Introduction to ISSU

ISSU OverviewIn-Service Software Upgrade (ISSU) provides the mechanism in which current serviceforwarding is not interrupted to the maximum extent during upgrade or rollback of softwareversion on the device.

ISSU reduces service interruption time as possible during software upgrade, thus increasingdevice reliability; it also minimizes the impact of upgrade failure on the system through rollback.

Requirements on the SystemTo implement the ISSU on a single device, the system should meet the following requirements:

l The software version running in the system supports ISSU.

l The main boards support 1:1 redundancy backup and the interface board supports dualprocesses. A new process for the new version is created on the interface board because theinterface board does not support 1:1 backup. During ISSU, the new process replaces theold process, which implements the switch of forwarding planes. During ISSU, the SMB isupgraded to the new version, and a new process is created on the interface board. Then, theSMB and the new process of the interface board replace the AMB and the old process ofthe interface board respectively. Finally, the original AMB is upgraded to the new versionand thus ISSU of the whole device is complete.

l The system supports the Graceful Restart (GR). When the device is being reset andperforming master/slave switch, its neighbors can forward and receive packets accordingto the routing table before switch. After being reset, the device obtains routing informationfrom its neighbors. In this manner, service interruption can be minimized and thus networkflapping caused by large-scale route recalculation is avoided.

l The configuration data of different versions before master/slave switch can be synchronizedbetween the AMB and the SMB. ISSU synchronizes the configuration data of the AMBand the SMB by restoring configurations. That is, the AMB saves a temporary configurationfile, through which the SMB restores the configurations.

8.1.2 ISSU Supported by the NE80E/40E

ISSU ModeNE80E/40E supports two ISSU modes:

l Lossless ISSUIn this mode, the configurations and data of the old AMB are synchronized with the newAMB; the configurations and data of the old process on the interface board are synchronized

8 Configuring ISSUHUAWEI NetEngine80E/40E Router



Issue 03 (2010-03-31)

with the new process on the interface board. This upgrade mode requires a higherperformance of the system.

l Lossy ISSUIn this mode, the configurations of the old AMB are synchronized with the new AMB; theconfigurations of the old process on the interface board are synchronized with the newprocess on the interface board; however, the dynamic data is not synchronized.

NOTE

In lossless or lossy ISSU, the interface board that does not support ISSU is commonly reset. In this way,the interface board is commonly reset at the ISSU plane switch phase.

Two Hybrid Modes Supported by ISSUTwo hybrid modes supported by ISSU are as follows:l Lossy ISSU and lossless ISSU are simultaneously performed.

l Lossy ISSU and fast-startup ISSU are simultaneously performed.

LPUs Supporting ISSUThe following LPUs support ISSU: the LPUE, LPUF, LPUH, LPUI, and LPUK.

ISSU ProcessThe ISSU process is as follows:

1. ISSU resets the SMB based on the new version and creates a new process based on the newversion on the interface board. In this manner, the new process on the interface board andthe SMB form a new forwarding plane and control plane.

2. Data synchronization and configuration restoration are performed between the AMB andthe SMB and between the new process and old process on the interface board.

3. The old control plane and forwarding plane are replaced with the new control plane andforwarding plane. Then, ISSU is complete.

8.2 Implementing ISSUThis section describes how to implement ISSU.


8.2.2 (Optional) Configuring ISSU Precheck

8.2.3 (Optional) Configuring the Length of the ISSU Rollback Timer

8.2.4 Implementing ISSU




8-3


Application EnvironmentISSU ensures the reliability of upgrades, reduces service interruption time, and relieves theimpact of upgrade on users.

Before ISSU, ensure that the current version of the system supports ISSU. During ISSU, it isrecommended that you not make any change on hardware.

Ensure that the control terminal of the router is connected to the AMB and SMB on the network.

Pre-configuration TasksBefore implementing ISSU, complete the following tasks:

l Powering on the router or switch and starting it normally

l Configuring GR

l Downloading resource files of the new version to the AMB and SMB. For the configurationprocedures of downloading resource files, refer to the chapter "Upgrade and Maintenance"in the HUAWEI NetEngine80E/40E Router Configuration Guide - Basic Configuration

Data PreparationTo implement ISSU, you need the following data.

No. Data

1 Length of the ISSU rollback timer

8.2.2 (Optional) Configuring ISSU Precheck

ContextBefore implementing ISSU, you can run the issu precheck command to perform precheck.

ISSU precheck contains hardware compatibility check and software compatibility check.

l Hardware compatibility check, also called resource check, is performed to determinewhether the interface board supports ISSU.

l ISSU software compatibility check is performed to determine the ISSU modes supportedby each module.

ISSU precheck has little impact on the system and does not cause the SMB to reset, and thuscan be used in non-ISSU phases.

Do as follows on the device on which ISSU is performed:

Procedure

Step 1 Run:




Issue 03 (2010-03-31)

issu precheck system-software system-file

The ISSU precheck is performed.

After ISSU precheck is complete, the system automatically provides the precheck result.

----End

8.2.3 (Optional) Configuring the Length of the ISSU RollbackTimer

Context


Procedure

Step 1 Run:issu timer rollback time

The length of the ISSU rollback timer is set.

When the system enters the ISSU check phase, the ISSU rollback timer is automatically activatedand its length is 120 minutes by default.

----End

8.2.4 Implementing ISSU

Context

During implementing ISSU, follow the prompts and interactive information of the system.


Procedure

Step 1 Run:issu check system-software system-file paf paf-file license license-file

ISSU is checked.

Once the command is run, the system has entered the ISSU check phase. ISSU check is performedto obtain the ISSU modes supported by the system and provides the check result in promptinformation. ISSU check has the following impact on the system:

l The SMB is reset on the basis of the new version and then becomes the new AMB.

l The system view cannot be entered.

l The ISSU rollback timer is activated. ISSU must be finished before the timer expires.Otherwise, ISSU may fail.

For the interactive information and description during ISSU check, refer to Table 8-1.



8-5

Table 8-1 Description of the issu check command output

Interactive information Description

Warning: The value of the ISSUrollback timer is 120 minutes. Thesystem will begin the ISSU upgrade.Continue? [Y/N]:

Warning: The length of the ISSU rollback timer is120 minutes. The system will start ISSU.Continue? [Y/N]l If you enter y, the system starts ISSU and

performs ISSU check.l If you enter n, the system aborts the running of

the issu check command and then quits ISSU.

Warning: The slave board will berebooted and check the softwarecompatibility. Continue? [Y/N]:

Warning: The SMB will be reset and then thesystem will check software compatibility.Continue? [Y/N]l When you enter y, the SMB will be reset on the

basis of the new version. The process lasts abouttwo minutes in normal situations. After the SMBis reset, the system checks softwarecompatibility.

l If you enter n, the system aborts the running ofthe issu check command and then quits ISSU.

NOTEWhen the R versions are the same, the preceding promptis displayed.

Warning: The slave board will berebooted and generate the configurationfile. Continue? [Y/N]:

Warning: The SMB will be reset and then thesystem will generate a configuration file.Continue? [Y/N]l When you enter y, the SMB will be reset on the

basis of the new version. The process lasts abouttwo minutes in normal situations. After the SMBis reset, the old AMB (that is, the SMB beforereset) generates a configuration file.

l If you enter n, the system aborts the running ofthe issu check command and then quits ISSU.

NOTE

l When the R versions are different, the precedingprompt is displayed.

l When ISSU is performed between different Rversions, the system supports the ISSU lossy modeonly. After the SMB is reset, the system skipssoftware compatibility check, and instead the oldAMB (that is, the SMB before reset) generates aconfiguration file.

Step 2 Run:issu start

ISSU is started.

If you need to abort ISSU, run the Step 4 command.




Issue 03 (2010-03-31)

For the interactive information and description during ISSU startup, refer to Table 8-2.

Table 8-2 Description of the issu start command output


Info: The lossless ISSU process willstart. Continue? [Y/N]:

Info: Lossless ISSU will start. Continue? [Y/N]l If you enter Y, the system starts ISSU in lossless

mode.l If you enter N, the system aborts the running of

the issu start command and waits for the nextoperation.– If you need to continue ISSU, run the issu

start command according to the promptbefore the ISSU rollback timer expires.

– If you need to abort ISSU, run the issuabort command.

– If you do not run the issu start or issuabort command before the ISSU rollbacktimer expires, the system rolls back and quitsISSU.

Step 3 (Optional) Run:issu common-reboot slot slot-id

The board is set to common reset mode.

If you consider the registration time of the new process or the configuration restoration time onan interface board to be over long, you can set the interface board to common reset mode. Theinterface board that is commonly reset does not create any new process or back up data. It is notcommonly used.

Step 4 (Optional) Run:issu abort

ISSU is aborted.

l If you need to abort ISSU, follow this step instead of Step 5 and Step 6.

l If you need to continue ISSU, skip this step and follow Step Step 5.

For interactive information and description during ISSU check, refer to Table 8-3.



8-7

Table 8-3 Description of the issu abort command output


Warning: The ISSU upgrade will beaborted, and the system will roll backto old version. Continue? [Y/N]:

Warning: The ISSU will be aborted, and the systemwill roll back to the old version. Continue? [Y/N]l If you enter y, the ISSU is aborted, and the system

will roll back to the old version.l If you enter n, the system aborts the running of the

issu abort command and continues ISSU.

Warning: The ISSU will be aborted,the system will be rolled back to theold version, and the new AMB willbe rebooted. This operation will take10 minutes. Continue? [Y/N]:

Warning: The ISSU upgrade will be aborted, thesystem will roll back to the old version, and the newAMB will be reset on the basis of the old version. Theprocess lasts 10 minutes. Continue? [Y/N]l If you enter y, the ISSU upgrade is aborted, the

system will roll back to the old version, and the newAMB will be reset on the basis of the old version.

l If you enter n, the system aborts the running of theissu abort command and continues ISSU.

Step 5 Run:issu slave-switchover [ force ]

The planes are switched.

NOTE

During the ISSU plane switch, the Telnet connection may be terminated. This indicates a normal situationand you need to wait for 30 seconds. After 30 seconds, you can press Enter to re-log in to the device thatperforms ISSU.

Step 6 Run:issu confirm

ISSU is confirmed.

NOTE

If you check the status of the AMB and SMB after the ISSU plane switch is complete, you can find thatthe new AMB is still in the slave state. This is because the hardware switch has not finished yet. After yourun the issu confirm command to confirm the ISSU operation and the old AMB restarts with the newversion, check the status of the AMB and SMB. At this time, you can find that both ISSU plane switch andhardware switch are complete and the status of the new AMB becomes Master.

----End


Prerequisite

All configurations of ISSU are complete.




Issue 03 (2010-03-31)

Procedurel Run the display issu timer rollback command to view the length of the ISSU rollback

timer.l Run the display issu module [ slot slot-id ] command to view the modules that supports

ISSU.l Run the display issu check-result [ slot slot-id ] command to view the result of ISSU

check.l Run the display issu backup state [ slot slot-id ] command to view the status of ISSU

backup.l Run the display issu backup-result [ state { resource-prepare | backup-prepare |

backup1 | backup2 | backup3 | smooth | smooth-over } ] [ slot slot-id ] command to viewthe result of ISSU backup.

l Run the display issu recover-configuration command to view the commands that fail torestore configurations.

l Run the display issu switch-result { check | prepare | age } [ slot slot-id ] command toview the result of ISSU switch check, switch preparation, and the cause of switch failure.

l Run the display issu state command to view which ISSU phase the system passes.

----End

ExampleRun the display issu timer rollback command to view the length of the ISSU rollback timer.

<HUAWEI> display issu timerThe length of the rollback timer is 60 minutes. There are 31 minutes left.

Run the display issu module [ slot slot-id ] command to view the modules that supports ISSU.

<HUAWEI> display issu module----------------------------------------------------------- Slot ModuleId ModuleName ----------------------------------------------------------- 9 0x41470000 AAA 9 0x40E90000 ND 9 0x40E00000 FIB6 9 0x41270000 RPR 9 0x416E0000 ARP 9 0x40A40000 CHDLC 9 0x400F0000 DHCPS 9 0x400D0000 DHCPR 9 0x404A0000 PPP ... ...... ...... 7 0x70120000 RM 7 0x70170000 OSPF 7 0x70180000 BGP 7 0x70290000 L3VPN 7 0x702B0000 TNLM 7 0x70320000 L3VPN V6 7 0x70140000 RIP -----------------------------------------------------------

Run the display issu check-result [ slot slot-id ] command to view the result of ISSU check.

<HUAWEI> display issu check-resultSystem upgrade type : losslessSystem maximum down time : 500s Interface board compatibility:---------------------------------------------------------Slot Type SupportStatus MaxDownTime(s)



8-9

Reason ---------------------------------------------------------4 LPU ISSU 5null6 LPU fast-reboot 500not enough memory7 LPU common-reboot 500configured to common-reboot by user---------------------------------------------------------

Run the display issu backup state [ slot slot-id ] command to view the status of ISSU backup.

<HUAWEI> display issu backup stateMain board backup status: real-time backupInterface board backup status

Run the display issu backup-result [ state { resource-prepare | backup-prepare | backup1| backup2 | backup3 | smooth | smooth-over } ] [ slot slot-id ] command to view the result ofISSU backup.

<HUAWEI> display issu backup-resultSystem backup-result:

--------------------------------------------State Result--------------------------------------------resource-prepare successbackup-prepare successbackup1 successbackup2 successbackup3 failsmooth -smooth-all-over --------------------------------------------Interface board backup-result:

-----------------------------------------------------------------Slot State Result1 resource-prepare success1 backup-prepare success1 backup 1 success 1 backup2 fail1 smooth -1 smooth-all-over -2 resource-prepare success2 backup-prepare success2 backup 1 success 2 backup 2 success 2 smooth -2 smooth-all-over ------------------------------------------------------------------

Run the display issu recover-configuration command to view the result of ISSU configurationrestoration.

<HUAWEI> display issu recover-configuration---------------------------------------------------------------Slot ViewName Command Reason---------------------------------------------------------------9 System-view display bgp peer parse failure9 Interface Ethernet 1/0/0 display this run failure---------------------------------------------------------------

Run the display issu switch-result { check | prepare | age } [ slot slot-id ] command to viewthe result of ISSU switch and switch preparation, and the cause of switch failure.




Issue 03 (2010-03-31)

<HUAWEI> display issu switch-result check---------------------------------------------------------Slot Type Result---------------------------------------------------------2 new RTP success 2 old RTP success18 old AMB success 4 old RTP success4 new RTP success ---------------------------------------------------------

Run the display issu state command to view which ISSU phase the system passes.

HUAWEI display issu state------------------------------------------------Phase State------------------------------------------------1.ISSU check finished2.ISSU start finished3.ISSU switchover finished4.ISSU confirm -------------------------------------------------The cancel ISSU command : issu abort.

8.3 Maintaining ISSUThis section describes how to monitor ISSU.

8.3.1 Monitoring the Running Status of ISSU

8.3.1 Monitoring the Running Status of ISSU

ContextIn routine maintenance, you can run the following command in any view to display the runningof ISSU.

Procedurel Run the display issu timer rollback command in the user view to view the length of the

ISSU rollback timer.l Run the display issu module [ slot slot-id ] command in the user view to view the modules

that supports ISSU.l Run the display issu check-result [ slot slot-id ] command in the user view to check the

result of ISSU check.l Run the display issu backup state [ slot slot-id ] command in the user view to check the

status of ISSU backup.l Run the display issu backup-result [ state { resource-prepare | backup-prepare |

backup1 | backup2 | backup3 | smooth | smooth-over } ] [ slot slot-id ] command in thethe user view to view the result of ISSU backup.

l Run the display issu recover-configuration command in the user view to view the resultof ISSU configuration restoration.



8-11

l Run the display issu switch-result { check | prepare | age } [ slot slot-id ] command inthe user view to view the result of ISSU switch check, switch preparation, and the causeof switch failure.

----End

8.4 Configuration ExamplesThis section describes examples for configuring ISSU.

8.4.1 Example for Implementing ISSU

8.4.1 Example for Implementing ISSU

Networking RequirementsISSU can be performed on a single device in any networking environment.


1. Perform ISSU precheck to check whether the interface board supports ISSU and ISSUmodes supported by each module.

2. Set the length of the ISSU rollback timer.3. Perform ISSU feasibility check.4. Start ISSU.5. Switch planes.6. Confirm ISSU.


l System software, PAF file, and License file of the new version

l Length of the ISSU rollback timer

Procedure

Step 1 Perform ISSU precheck.<HUAWEI> issu precheck system-software VRPV500R007.ccSystem Upgrade Type : losslessSystem Maximum Down Time : 500s Interface board compatibility:-------------------------------------------------------------------Slot Type SupportStatus MaxDownTime(s) Reason -------------------------------------------------------------------4 LPU ISSU 5 null6 LPU fast-reboot 500 not enough memory




Issue 03 (2010-03-31)

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

Step 2 Set the length of the ISSU rollback timer to 240 minutes.<HUAWEI> issu timer rollback 240Info: Please complete the ISSU upgrade within 240 minutes. Otherwise, the system will roll back to the old version.

Step 3 Perform ISSU check to determine ISSU mode.<HUAWEI> issu check system-software VRPV500R007.cc paf paf.txt license license.txtWarning: The value of the ISSU rollback timer is 240 minutes. The system will begin the ISSU upgrade. Continue? [Y/N]:yInfo: The system is comparing compatibility IDs...Info: The system is checking the hardware compatibility...Warning: Some boards do not support ISSU, and have been configured to upgrade in common reboot mode. The detailed information can be viewed by using the display command (display issu check-result). Warning: The slave board will be rebooted and check the software compatibility. Continue? [Y/N]: yInfo: The slave board is rebooting in VRPV500R007...Info: The new AMB is registered.Info: The system is checking the specification compatibility...Info: The system is checking the software compatibility...Info: The system is generating the configuration file...Info: The system supports Lossless ISSU.The following operations can be done: 1. View detailed information about ISSU check result by using the command (display issu check-result). 2. The ISSU rollback timer can be configured before ISSU start by using the command (issu timer rollback).The default value of the timer is 120 minutes. 3. To start ISSU, run the command (issu start). Otherwise, the system will roll back to the old version after the ISSU timer times out. 4. To roll back the system to the old version immediately, run the command (issu abort).

Step 4 Start ISSU.<HUAWEI> issu startInfo: The lossless ISSU process will start. Continue? [Y/N]: yInfo: The system will start Lossless ISSU upgrade.Info: The system is busy with the operation of coping configuration file...Info: The operation of coping configuration file is complete.Info: The system is busy with resource preparation...Info: The resource preparation is complete.Info: The system is busy with preparation for batch backup...Info: The preparation for batch backup is complete.Info: The system is busy with phase 1 batch backup...Info: Phase 1 batch backup is complete.Info: The system is busy with configuration recovery of the new AMB...Info: Configuration recovery of the new AMB is complete.Info: The system is busy with phase 2 batch backup...Warning: Some errors occurred in the phase 2 of the batch backup. The top error level: Affect ISSU Upgrade. Detailed information can be obtained by using the command (display issu backup-result) in the old AMB.Info: Phase 2 batch backup is complete.Info: Configuration of interface boards is recovering...Info: Configuration recovery of interface boards is complete.Info: The system is busy with phase 3 batch backup..Info: Phase 3 batch backup is complete.Warning: Some errors occurred. The top error level: Affect ISSU Upgrade. Detail information can be got by the command (display issu recover-configuration) in the new AMB.Info: The system is in real-time backup phase. Please check the backup status before performing the ISSU switchover (Command: display issu backup state; issu switchover).

Step 5 Switch planes.<HUAWEI> issu switchoverInfo: The system will check the ready mode of all modules first. Please wait...Info: The system is performing ISSU switchover on the forwarding plane...



8-13

Info: Forwarding plane switch check starts...Error: Slot 7 new RTP switchover check is incorrect. This board will be set common-reboot.Info: Forwarding plane switch check is complete.Info: Forwarding plane switch starts...Info: Slot 7 forwarding plane switch fail. This board will be rebooted immediately.Info: Slot 7 forwarding plane switch succeeded.Info: Slot 7 New Procedure forwarding plane switch succeeded.Info: Forwarding plane switch is complete.Info: Data smoothing starts...Info: Data smoothing is complete.Info: Aging starts...Info: The aging of slot 7 succeeded.Info: Aging is complete.Info: The switchover is complete. Please confirm the operation of the ISSU upgrade (Command: issu confirm).

NOTE

During the ISSU plane switch, the Telnet connection may be terminated. This indicates a normal situationand you need to wait for 30 seconds. After 30 seconds, you can press Enter to re-log in to the device thatperforms ISSU.

Step 6 Confirm ISSU on the new AMB.<HUAWEI> issu confirmInfo: The old AMB (slot 9) will be rebooted in the new version. This operation will take 10 minutes. After that, ISSU will be complete normally.

NOTE

If you check the status of the AMB and SMB after the ISSU plane switch is complete, you can find thatthe new AMB is still in the slave state. This is because the hardware switch has not finished yet. After yourun the ISSU confirm command to confirm the ISSU operation and the old AMB restarts with the newversion, check the status of the AMB and SMB. At this time, you can find that both ISSU plane switch andhardware switch are complete and the status of the new AMB becomes Master.

Step 7 Check whether the software version of the current system is correct to further confirm ISSU.<HUAWEI> display startupMainBoard: Configured startup system software: cfcard:/VRPV500R007.cc Startup system software: cfcard:/VRPV500R007.cc Next startup system software: cfcard:/VRPV500R007.cc Startup saved-configuration file: cfcard:/vrpcfg.cfg Next startup saved-configuration file: cfcard:/vrpcfg.cfg Startup paf file: cfcard:/paf.txt Next startup paf file: cfcard:/paf.txt Startup license file: cfcard:/license.txt Next startup license file: cfcard:/license.txt Startup patch package: cfcard:/$_patchstate_a Next startup patch package: cfcard:/$_patchstate_aSlaveBoard: Configured startup system software: cfcard:/VRPV500R007.cc Startup system software: cfcard:/VRPV500R007.cc Next startup system software: cfcard:/VRPV500R007.cc Startup saved-configuration file: cfcard:/vrpcfg.cfg Next startup saved-configuration file: cfcard:/vrpcfg.cfg Startup paf file: cfcard:/paf.txt Next startup paf file: cfcard:/paf.txt Startup license file: cfcard:/license.txt Next startup license file: cfcard:/license.txt Startup patch package: cfcard:/$_patchstate_a Next startup patch package: cfcard:/$_patchstate_a

----End




Issue 03 (2010-03-31)

Configuration FilesNone



8-15

A Glossary

This appendix collates frequently used glossaries in this document.

Numerics

802.1 ag MAC Trace Similar to traceroute or tracert, 802.1ag MAC trace works bysending test packets and waiting for a reply to test the path betweenthe local device and the destination device and to locate faults.802.1ag MAC trace is initiated by a MEP and destined for a MEPor MIP at the same maintenance level within any MA.

802.1ag MAC Ping Similar to ping, 802.1ag MAC ping works by sending test packetsand waiting for a reply to test whether the destination device isreachable. 802.1ag MAC ping is initiated by a MEP and destinedfor 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 MEPforwards received CCMs at a higher level but drops CCMs at alower 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

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability A Glossary


A-1

Ethernet OAM at theLink Level

Ethernet OAM at the link level, such as Ethernet in the First MileOAM (EFM OAM) defined in IEEE 802.3ah, provides thefollowing functions for the link between the two directly connecteddevices: Link connectivity check, Link monitoring, Remote failureindication, Remote loopback.

Ethernet OAM at theNetwork Level

Ethernet OAM at the network level, such as Ethernet ConnectivityFault Management (CFM) defined in IEEE 802.1ag, provides thefollowing functions for the network: Fault detection, Faultnotification, 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 canbe divided into one or multiple MAs.

MD The Maintenance Domain (MD) refers to the network or the partof the network for which connectivity is managed by CFM. Thedevices in an MD are managed by a single ISP.

MEP A Maintenance association End Point (MEP) is an end point withinan MA.

MEP Database There is a MEP database on each device enabled with EthernetCFM. Each MEP database contains the local MEPs and RMEPs.

MIP A Maintenance association Intermediate Point (MIP) is anintermediate 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

O

OAMPDU OAM Protocol Data Unit

A GlossaryHUAWEI NetEngine80E/40E Router


A-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

R

RMEP For the other devices in the same MA, their MEPs are called theRemote 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 EFMOAM

The working mode of EFM OAM is an attribute of the interfaceenabled with EFM OAM. EFM OAM has two working modes:active mode and passive mode.

WTR Wait To Restore

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability A Glossary


A-3

B Acronyms and Abbreviations

This appendix collates frequently used acronyms and abbreviations in this document.

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

M

MPLS TE FRR MultiProtocol Label Switching Traffic Engineering Fast Reroute

MTBF Mean Time Between Failure

HUAWEI NetEngine80E/40E RouterConfiguration Guide - Reliability B Acronyms and Abbreviations


B-1

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

B Acronyms and AbbreviationsHUAWEI NetEngine80E/40E Router


B-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-03-31)

Date post:	20-Apr-2015
Category:	Documents
Upload:	mamidz
View:	46 times
Download:	0 times

Configuration Guide - Reliability(V600R001C00_03)[1]

Documents